11.2 Changing Leadership Styles for the Situation
Key Takeaways
- Leadership style should be a deliberate response to team capability, urgency and risk, task clarity, and team motivation.
- Capability and motivation move independently: a capable but demotivated specialist needs ownership, not instruction.
- Style should shift across the life cycle — consultative in definition, directive in early deployment and crisis, delegating in steady delivery, coaching at transition.
- A permanently directive default disengages capable people and makes the project manager a decision bottleneck.
- A permanently hands-off default leaves inexperienced teams without structure and nobody to take unpopular decisions.
Outcome 12b is a single, high-yield line: understand why it may be necessary to change leadership styles depending upon the situation. The mark is never for naming a style. It is for explaining what about the situation makes one style appropriate and another counter-productive.
Changing leadership styles depending on situation
Effective project leadership is situational. Style should fit task urgency, team competence and confidence, stakeholder power, risk severity, and life-cycle moment. A single fixed style (always directive, or always laissez-faire) fails under varied project conditions.
| Situation | Often-effective emphasis | Why |
|---|---|---|
| Crisis / safety incident | Directive, clear single voice, short instructions | Speed and clarity protect people and objectives |
| New team / low experience | Directive to coaching — structure, standards, frequent feedback | Competence and norms are still forming |
| Capable team, clear goals | Delegating / supportive — autonomy with checkpoints | Uses expertise; builds ownership |
| Conflict between peers | Facilitative / collaborative leadership | Parties need joint problem-solving, not imposed silence |
| Political stakeholder environment | Visible, diplomatic, network-oriented leadership | Influence beyond formal authority |
| Iterative product work | Servant / coaching with product focus | Enables team flow and learning |
| Assurance or audit finding | Firm on standards, open on learning | Compliance without fear culture |
Situational arc on one project
- Start-up: more structure — roles, vision, ways of working (directive elements + coaching).
- Storming (team development): active conflict facilitation and norm-setting.
- Performing: more delegation; leader removes blockers and manages upwards.
- Crisis mid-project: temporary return to directive control, then release once stable.
- Transition/close: recognition, knowledge transfer, and support for people returning to BAU.
Exam trap: "The best leaders always empower and never direct." Situational leadership includes directive action when needed, then a return to developmental styles.
The variables that should move your style
Four situational variables do most of the work in exam scenarios. Read them off the stem before choosing a style.
| Variable | Pushes towards a directive style | Pushes towards a supportive or delegating style |
|---|---|---|
| Team capability and experience | New team, unfamiliar work, low competence in the task | Experienced specialists who know the work better than you do |
| Urgency and risk | Safety incident, live outage, imminent regulatory breach | Routine delivery with time to explore options |
| Clarity of the task | Well-defined work with a known right answer | Ambiguous problems needing exploration and ideas |
| Team motivation and confidence | Low confidence needing structure and reassurance | High commitment needing autonomy and challenge |
Note that capability and motivation move independently. A highly capable but demotivated specialist does not need instruction; they need to understand why the work matters and to be given ownership. A motivated but inexperienced apprentice needs structure without having their enthusiasm managed out of them. Diagnosing which of the two is missing is precisely the judgement that scenario questions test.
Style shifts across the life cycle
Leadership style should also move as a project progresses, and saying so lifts an answer:
- Concept and definition — facilitative and consultative: the task is ambiguous, options must be explored, and stakeholders must be brought along.
- Early deployment — more directive: baselines are set, the team is new, and clarity beats debate.
- Steady delivery — supportive and delegating: the team is competent, and micromanagement now destroys ownership and slows decisions.
- Crisis — directive, briefly: someone must decide quickly and take responsibility for it.
- Transition and closure — coaching and appreciative: motivation dips as the team disperses, and knowledge transfer depends on goodwill.
Why a single style fails
Two failure patterns recur in scenarios and both are worth naming.
Permanently directive. Fast in a crisis, corrosive as a default. Capable people disengage, stop raising problems because they are not asked, and eventually the project manager becomes the only source of decisions — a bottleneck and a single point of failure. This also drifts towards McGregor's Theory X, where controlling behaviour produces the passivity that appears to justify it.
Permanently hands-off. Comfortable with strong teams, dangerous with new ones or in a crisis. Inexperienced members flounder without structure, ambiguity persists, and nobody takes the unpopular decision.
The professional position is that style is a deliberate response to circumstances, chosen consciously and changed openly. Telling a team why you are stepping in — "for the next two days while we resolve the outage I'm going to direct this closely, then we go back to how we normally work" — preserves trust while the style changes. In a long response, name the situational variables, state the style, justify the fit, and say what would make you change it.
A project manager leads a team of highly experienced engineers who know the technical work better than the project manager does, but who have become disengaged after a series of reversed decisions. Which leadership response is most appropriate?
During a live service outage a normally consultative project manager begins issuing direct instructions without seeking consensus. How should this be assessed?