organizational and legal standards, but they also are quite concerned with who reports to whom and whose permission is required to take what action. The astute reader will note that such concerns are not entirely appropriate for matrix-organized projects. Our discussions with senior managers lead us to the not-surprising conclusion that it is common for senior management to want the efficiency and other advantages of matrix management but simultaneously to attempt to maintain the managerial comforts of traditional hierarchical structures—a sure source of conflict.
The conflict-resolution potential of partnering and project charters should be quite clear. Neither technique will stop conflicts from arising, but they will sharply , lower the intensity of the conflicts as well as provide a framework for resolving conflict. They will even allow an environment in which the PM and functional managers can take positions that support the total organization rather than suboptimizing the project or the function.
Project managers will often find themselves arguing for scheduling or resource priorities from functional managers who outrank them by several levels. Neither the functional nor the project managers are quite sure about who has what authority. (The reader will recall that the pure project form of organization has a tendency to breed deviant administrative behaviors, and that matrix organization is characterized by superior-subordinate confusion.) A constant complaint of project managers is "1 have to take the responsibility, but I have no authority at all."
People problems arise, for the most part, within the project team, though functional managers may clash with PMs—the former accusing the latter of being "pushy," and the latter accusing the former of "foot dragging." In our experience, most personality clashes on the project team result from differences in technical approach or philosophy of problem solving, and in the methods used to implement the project results. Of course, it is quite possible that a personality conflict causes a technical conflict. It is also possible that any type of conflict will appear, at first blush, to be a personality clash.
Next we put these conflicts into the chronological perspective of the project life cycle.
Was this article helpful?
What you need to know about… Project Management Made Easy! Project management consists of more than just a large building project and can encompass small projects as well. No matter what the size of your project, you need to have some sort of project management. How you manage your project has everything to do with its outcome.