3.4Conflict and leadership

Conflict is an unavoidable phenomenon in a project team, and it is not inherently bad. What matters for a PM is not eliminating conflict but discerning its nature—urgency, the importance of the relationship between the parties, whether a permanent resolution is needed—and choosing the resolution technique that fits. This section also covers situational leadership: the idea that the effective style of leadership changes with the team's maturity.

3.4.1Choosing among conflict resolution techniques

• Confront/collaborate has both parties surface their genuine concerns and jointly build a win-win solution that satisfies both sides. It takes the most time and effort but is most likely to lead to a permanent resolution. It suits conflicts where the relationship is important and long-term, and there is time to work through it.
• Compromise has both sides give something up to settle on a middle-ground solution that partially satisfies each party. It takes less time than confronting, but because neither side is fully satisfied, it is less likely to yield a permanent resolution. It suits situations where the parties have roughly equal power and there is little time to confront the issue fully.
• Smoothing de-emphasizes the point of disagreement and emphasizes areas of agreement or the good relationship, temporarily easing friction. It does not address the root cause, so the problem tends to resurface, but it is useful as a stopgap for minor conflicts where preserving the relationship matters, or when attention needs to go to a more serious conflict instead.
• Withdraw (avoid) postpones addressing the conflict or steps away from it. It does not lead to a permanent resolution, but is used as a temporary choice to let heated parties cool down, to avoid spending effort on a trivial conflict, or to focus on a higher-priority issue instead.
• Force pushes one party's position through using authority. It resolves the issue quickly but not permanently, and often leaves the overruled party dissatisfied. It should be reserved for emergencies requiring an immediate, non-negotiable decision, such as safety or legal compliance.
• The key to choosing: confront when a permanent resolution matters most; compromise when time is short and the parties are evenly matched; smooth when the relationship matters most and the issue is minor; withdraw when a cooling-off period is needed; and reserve force for emergencies such as safety. Remember that force and withdrawal are stopgaps—the root cause remains unresolved.

3.4.2Situational leadership

• Situational leadership holds that there is no single, universally correct leadership style—the degree of directive involvement should change with the team's maturity (experience, autonomy) and the nature of the task. An immature team, as in forming, tends to respond best to a directing style (giving concrete instructions), while a mature team, as in performing, tends to respond best to a delegating style (ceding authority and not over-managing).
• A practical mistake: continuing a directing style with a mature (performing) team as though it were still forming stifles autonomy and lowers motivation. Conversely, abruptly delegating everything to an immature (forming) team causes it to lose direction and creates confusion. The Tuckman-model stage and the leadership style should be judged in tandem.

Suppose a PM faces a situation where two senior engineers are in direct disagreement over the system's architecture direction—whether to move toward microservices or keep the monolith with partial refactoring. This conflict is an important decision that will shape maintainability and extensibility for years to come, and fortunately there are still several weeks before the project deadline. For a conflict of high importance with time to spare, the PM should choose confront/collaborate, having both engineers candidly surface their concerns (performance requirements, migration cost, the team's skill set, etc.) and jointly build an integrated direction both can accept (e.g., a staged, partial move to microservices). Settling for a compromise—splitting the difference between the two positions—just because "there's no time" risks producing a technically incoherent architecture that causes rework later. Meanwhile, suppose on the same project the PM encounters two other people arguing over a trivial coding-style detail, such as indentation width. This is a conflict of low importance that does not require as permanent a resolution as an architecture decision, so smoothing (emphasizing the shared goal—"both styles have merit, but let's focus on the release for now") or, depending on the situation, withdrawing (deferring the discussion for now, deciding later) is sufficient. Deploying a heavyweight technique like confronting here would be a waste of effort. Further, suppose a critical security vulnerability is found in production, and there is contentious debate with no time to spare over whether to apply a patch immediately—this is an emergency where the PM should use authority to force a decision: a safety-related emergency is one of the few exceptions where speed should be prioritized over discussion. From a leadership perspective, if these two senior engineers form an experienced, autonomous performing-stage team, the PM should not dictate the technical conclusion but should stick to facilitating the confrontation and keep involvement delegating. Conversely, if the same kind of conflict arose in a newly formed, inexperienced forming-stage team, the PM would need to be more directing, laying out the framework of the technical direction. Choosing the technique and leadership style along the three axes of a conflict's importance, urgency, and the team's maturity is the judgment a PM is expected to exercise.

3.4.3Section summary

• Confront/collaborate takes the most time but suits a permanent win-win resolution; compromise suits a partial resolution when time is short and parties are evenly matched
• Smoothing, withdrawal, and force are temporary responses that leave the root cause unresolved; force should be reserved for emergencies such as safety
• Situational leadership varies the degree of involvement with team maturity: directing for an immature team, delegating for a mature one