discord management

 conflict management Essay

From The Project Management Institute Task Management Handbook, Ed: Jeffrey Pinto. 1998

isbn 0-7879-4013-5


Vijay T. Verma

Issue is the gadfly of believed. It stirs us to observation and memory It instigates invention. It shocks us away of sheeplike passivity and sets us at noting and contriving. Turmoil is a " sine qua non” of reflection and ingenuity RUBEN DEWEY

Issue is as inevitable in a project environment because change appears to be. When project team members interact during the course of doing their jobs and responsibilities, there is always a potential for conflict. In fact , it is virtually extremely hard for people with varied background abilities and norms to come together; make decisions, and try to satisfy project objectives without issue. Project managers must recognize, analyze, and evaluate both equally positive and negative beliefs of discord and their impact on performance. They need to learn how and when to induce conflict and the way to use it to improve the performance of project team members. Turmoil need not possess destructive outcomes. Attitudes and conflict supervision styles play an important function in determining whether this sort of conflict is going to lead to harmful or mutually beneficial outcomes. (ref 1)

Views of Conflict

Over time three specific views include evolved regarding conflict in projects and organizations)' The traditional view (dominant from the past due nineteenth 100 years until the mid-1940s) assumes that conflict is usually bad, has a negative impact, and causes declines in performance while the level of issue increases. Turmoil must consequently always be prevented. In this view conflict is definitely closely connected with such conditions as assault, destruction, and irrationality.

The response to issue in the classic view is always to reduce, suppress, or cure it. The supervisor was in charge of freeing the project of any issue, often using an severe approach. Even though that way worked occasionally, it was not really generally effective; when they are covered up, the root triggers cannot be discovered, and the potentially positive aspects of conflict are not able to emerge. This kind of traditional perspective of turmoil is still widely held because industrial and business corporations that have a solid influence in our world concur with it. This negative view of conflict played a role in the development of labor unions. Violent or disruptive fights between workers and management led visitors to conclude that conflict was always damaging and should for that reason be avoided. The behavioral or perhaps contemporary watch, also known as the human relations watch, emerged back in the 1940s and held swing through the 1971s. It argues that turmoil is natural and inescapable in all businesses and that it could have either a positive or a negative effect, depending on the way the conflict is handled. Performance may increase with conflict, but just up to a selected level, and after that decline in the event that conflict is allowed to boost further or is still left unresolved. This approach advocates acknowledgement of discord and rationalizes its lifestyle. Because of the potential benefits from conflict, project managers should concentrate on managing that effectively rather than suppressing or eliminating that.

The newest point of view, the interactionist view presumes that discord is necessary to improve performance. While the behavioral way accepts discord, the interactionist view motivates conflict based on the belief that a harmonious, calm, tranquil, too-cooperative project corporation is likely to become static, apathetic, stagnant, and unable to interact to change and innovation. This approach encourages managers to maintain the right level of conflict—enough to keep tasks self-critical, practical, creative, and innovative. Employing these 3 views of conflict, the managerial activities to be taken could be decided by simply comparing the actual level of discord (a) and desired amounts of conflict (d)(ref 3). According to the...

References: Williams, M. (1987, September). Could learned to quit worrying and love discussing. Inc. Magazine, p. 132.

Bobbins, T. P. (1974). Managing organizational conflict: A no nt raditional procedure. Englewood Coves, NJ: Prentice Hall.

Robbins (1974).

Baker, S., & Baker, E. (1992). Upon time/on price range: A step by simply step information for handling any job. Englewood Coves, NJ: Prentice Hall.

Thamhain, H. T., & Wdemon, D. T. (1975). Turmoil management in project lifestyle cycles. Sloan Management Assessment, 16, 3 1—50.

Kezsbom, D., Schilling, D., & Edward, E. (1989). Energetic project administration practical guidebook for managers and engineers. New

You are able to: Wiley.

Thomas, K. W, & Schmidt, W They would. (1976). A survey of managerial interests with respect to turmoil. Academy of Management


Craves, M. (1978). Powerful management and organizational mugging. InJ. Papp (Ed. ),

New path in human resource management

Robbins (1974).

Cover, L. A., & Schwenk, C. R. (1990). Agreement and thinking likewise: Ingredients pertaining to poor


Starke, N A., & Sexty L. W (1992). Contemporary managing in Canada. Englewood Cliffs, NJ-NEW JERSEY:



Womack, G. E (1988). Assessing perish Thomas-Kilman issue mode review Management Connection Quarterly, 1, 32 1—


15. House, L. 5. (1988). The human area of job management. Browsing, MA: Addison-Wesley

Schutz, W

House (1988).

Hill, Ur. E. (1977). Managing social conflict in project teams. Sloan Administration Review, 18(2), 45—61.

Thamhain & Watts, lemon (1975).

House (1988).

House (1988).

Block, P (1981). flawless consulting. Austin tx, TX: Learning Concepts.

Sieved, R. T, Jr. (1986, December). Interaction: An important structure tool. Project Management Journal, 77. House

House (1988).

House (1988).

House (1988).

Dinsmore, PERSONAL COMPUTER. (1990). Individual factors in project management (Rev. ed). New York: AMACOM.

Fisher, Ur., & Ury, W (1991). Getting to certainly: Negotiating agreement without submitting (2nd ed).

Hofstede, C. (1993). Ethnicities and businesses: Software in the mind. New York: McGraw-Hill.