Leadership is observable — it is the residue of decisions over time
Team formation, motivation, conflict, leadership styles. The human core of project work, treated as a discipline you can practice rather than a vibe you have.
Leadership is the residue of decisions over time. Not personality. Not charisma. The pattern.
Leadership content is mostly bad. Most of it focuses on traits — strong leaders are decisive, empathetic, visionary, authentic — which is unfalsifiable in the moment and useless as practice. The trait framing implies that leadership is who you are, and the work is becoming the right kind of person.
This piece argues the opposite frame. Leadership is what you do, observably, at decision points, over time. It is the residue of choices: which conversations you had, which you skipped, what you noticed, what you tolerated, what you wrote down. Looking at any individual leadership decision in isolation tells you very little. Looking at the pattern across six months tells you everything. The pattern is the leadership.
This piece is the long-form anchor for the Leadership & Team Dynamics pillar. It walks the team-formation arc that drives most of what teams need from a leader, the conflict patterns that are predictable and solvable, the leadership-style spectrum that fits different contexts, and the failure modes that show up in retrospective when leadership has not been deliberate.
§1 — The team-formation arc
Bruce Tuckman's 1965 model — forming, storming, norming, performing, adjourning — gets dismissed as MBA-curriculum filler in some circles. It survives because it is unusually accurate. Almost every project team passes through these five phases, in order, and the leadership work changes character at each phase.
Forming. The team has just assembled. Everyone is polite, defers to the apparent leader, and is mostly trying to figure out the social order. Almost no productive work happens. Leadership work: structure. Set the cadence, define the artifact set, model the behaviors you want, give people specific things to do. The mistake is to confuse politeness with alignment — the team is not yet aligned, just deferring.
Storming. The team has worked together long enough that disagreements surface. Personalities clash; competing visions emerge; someone goes silent who used to speak up. This is the phase most teams fail in, and the phase most leadership content is bad about. Leadership work: surface the disagreements explicitly, name the trade-offs, make the calls. The mistake is to suppress storming because it feels uncomfortable — suppressed storming becomes silent disagreement, which is much more expensive.
Norming. The team has worked through the storming and produced shared norms — how decisions get made, who has expertise on what, what the bar for done looks like. Productivity rises sharply. Leadership work: recede. The team needs less leadership in this phase, not more. Over-leading in norming kills the autonomy the team just earned.
Performing. The team is in flow. Work happens predictably; conflicts get resolved internally; the team handles new arrivals well. Leadership work: protect the team's bandwidth. Take the political conversations off the team's plate. The mistake is to inject new work or new structure during performing — the team has earned its momentum, and leadership's job is to defend it.
Adjourning. The project closes; the team disbands. Often skipped (see the project-lifecycle pillar's pattern on closure). Leadership work: name what happened, credit specific people, make sure the lessons travel. The team will form again on the next project — what they learned here decides whether the next forming phase is shorter.
- Weeks 1-2FormingPolite, deferential, low productivity. Leadership: structure, cadence, model behaviors, name expectations.
- Weeks 3-6StormingDisagreements surface. Leadership: surface conflicts explicitly, make calls, do not suppress.
- Weeks 6-12NormingShared norms emerge. Productivity rises. Leadership: recede, let autonomy operate.
- Weeks 12+PerformingTeam in flow. Leadership: protect bandwidth, absorb political work, defend the team.
- ClosureAdjourningTeam disbands. Leadership: credit specific people, surface lessons, make them travel to the next team.
§2 — Conflict patterns and which ones are predictable
Conflict on a project team is not a sign that something has gone wrong. Conflict is a sign that the team has stakes. Teams without conflict are usually teams without engagement.
Three conflict patterns account for most of what surfaces:
Direction conflict. Two team members want the project to go in different directions. The conflict is about what to do, not who to be. Direction conflict is solvable through clarity: write the decision down, name the trade-offs, make the call, document why. The teams that handle direction conflict well treat it as information, not as drama.
Style conflict. Two team members work in incompatible styles. One is detail-oriented and writes everything down; one is intuitive and prefers verbal coordination. Neither style is wrong; the friction is the cost of working together. Style conflict is solvable through naming: surface the difference, agree on a working norm, let people work in their preferred style outside the agreement boundary. The teams that handle style conflict badly treat one style as correct and the other as wrong.
Identity conflict. A team member experiences a project decision as a personal slight. The most common shape is a senior contributor who feels their judgment was overruled in a way that signals their authority is shrinking. Identity conflict is the hardest to surface and the most expensive to ignore. The mitigation is structural: make the decision-making process visible enough that overrules are not surprising, and have the conversation about authority and scope explicitly when it shifts. The teams that handle identity conflict well treat it as legitimate — not as oversensitivity to surface.
“The hardest leadership lesson I learned was that conflict suppression is more expensive than conflict surfacing. The first project I ran, I kept things smooth — and we delivered something nobody wanted. The second project I let people fight in the room, and we shipped on time.”
§3 — Leadership style as context fit
There is no single correct leadership style. The styles that work fit the contexts they are deployed in, and the leaders who handle multiple contexts can shift between styles deliberately. Four styles cover most of what shows up in project work.
Directive. The leader makes the calls; the team executes. Fits crisis contexts, ambiguous situations where someone needs to call the play, and forming-phase teams that are still figuring out who decides. The failure mode is using directive style on a performing team, which kills autonomy and produces resentment.
Coaching. The leader asks questions and helps the team find the answer. Fits norming-phase teams that are building skill, junior team members who need development, and ambiguous-but-learnable problems. The failure mode is using coaching style in a crisis, which leaves the team without a decision when one is needed.
Supportive. The leader removes obstacles and protects the team's autonomy. Fits performing-phase teams that have momentum, senior teams that resent over-management, and contexts where the team's judgment is more current than the leader's. The failure mode is using supportive style on a storming team, which leaves the conflicts unresolved.
Delegating. The leader hands off ownership entirely and is available if needed. Fits high-trust performing teams, work that is well-understood, and senior leaders who need the team to operate independently while they handle the political layer. The failure mode is delegating to a team that does not yet have the context to deliver — which usually shows up as a missed milestone.
| Style | Best context | What the leader does | Failure mode |
|---|---|---|---|
| Directive | Crisis, forming team | Makes calls, sets pace | Used on performing team — kills autonomy |
| Coaching | Norming team, junior contributors | Asks questions, develops skill | Used in crisis — leaves team without decision |
| Supportive | Performing team, senior team | Removes obstacles, protects bandwidth | Used on storming team — leaves conflict unresolved |
| Delegating | High-trust team, well-understood work | Hands off ownership, stays available | Used too early — team lacks context, milestone slips |
§4 — The four most common leadership failure modes
The leadership failures we see in project retrospectives cluster.
The avoided storming phase. The leader senses storming is coming and works to prevent it — pushes consensus prematurely, rephrases disagreements as misunderstandings, schedules team-building events. The team never gets through storming, and the conflicts go underground as silent disagreement. The fix is to let storming happen, name it as it is happening, and trust that norming follows.
The over-led performing team. The leader continues to make calls the team is now capable of making. Each call is small, but the cumulative effect is that the team's autonomy has been quietly absorbed back into the leader. Performance drops; the leader cannot tell why. The fix is the leader noticing they are still in the loop on decisions the team should own, and stepping back deliberately.
The trait-collapse failure. The leader has been told they are decisive (or empathetic, or visionary) and starts performing the trait rather than making the decisions. The trait gets executed as theater; the underlying judgment stops being applied. This is the authentic-leader trap. The fix is to forget the traits and focus on the decisions.
The undocumented decision pattern. A leader makes 50 decisions over six months, all defensible in the moment, none documented in a way that lets the team see the pattern. When a new contributor joins, they cannot reconstruct why the team works the way it does. The pattern is invisible. Fix: write down the why on the half-dozen decisions that shape the team's working norms — pinned in the wiki, referenced in onboarding.
The leadership work is to know what your default style is, recognize when the context calls for a different style, and switch deliberately. The leaders who can switch handle three to four times the variety of contexts that single-style leaders handle.
Where leadership and team dynamics meet the rest of project work
§6 — How to use this pillar
The rest of the Leadership & Team Dynamics pillar walks the team-formation phases in operational detail, the conflict-pattern playbook, the situational-leadership style framework, and the psychological-safety practices that distinguish high-performing teams. If you are leading a team for the first time, read the team-formation piece first. If your team is in storming, read the conflict-pattern piece.
The meta-rule: leadership is observable. The pattern is the leadership. Pay attention to the pattern.