Manu's Vault

Four-States-of-a-Team

4 min readStatus:Seedling

The Four States of a Team is a diagnostic model from Will Larson’s An Elegant Puzzle for assessing engineering team health and selecting the correct managerial intervention. Its core insight: each state demands a different response, and applying the wrong fix actively worsens the situation.

The Four States

  • Falling Behind: Backlog grows faster than it is completed. Morale is typically low; the team feels perpetually underwater.

    • Intervention: Add people. Set expectations that hiring takes time before relief arrives.
    • Warning: This is the only state where headcount growth reliably helps.

  • Treading Water: Team completes critical work but cannot pay down technical debt or invest in innovation.

    • Intervention: Reduce incoming load — say no, defer, or cancel work. Do not add engineers; more people increase coordination overhead without clearing the bottleneck.

  • Repaying Debt: Team has enough capacity to address systemic problems. Debt payments are visibly underway.

    • Intervention: Protect the team from new feature demands. This state is fragile — business pressure frequently collapses it back to Treading Water before meaningful progress accumulates.

  • Innovating: Low technical debt, high slack, team invents new value and explores future capability.

    • Intervention: Maintain slack deliberately. Resist the impulse to fill idle capacity with new commitments. This is the goal state.

State Transitions

Teams move between states sequentially. The path from crisis to health follows: add people → reduce load → protect debt-repayment → maintain slack. Skipping steps (e.g., moving from Falling Behind directly to Innovation) is not possible without first passing through intermediate states.

Manager-to-Engineer Ratio

  • Ideal range: 6–8 engineers per manager
  • Below 4: Managers lose technical credibility and generate process overhead to fill their time
  • Above 10: Managers cannot adequately support individuals; response latency increases and people feel unsupported

Diagnosing the State

Ask: Is the backlog growing, shrinking, or holding steady? Can the team address technical debt? Does the team have capacity to experiment? These three questions usually locate the team within the model.

Comparison to Adjacent Frameworks

  • Tuckman’s Stages (Forming → Storming → Norming → Performing) describes team social maturity, not workload capacity. The Four States model addresses flow dynamics regardless of team cohesion stage.
  • Situational Leadership (Hersey–Blanchard) argues that leaders must adapt style to follower readiness. The Four States model operates similarly — correct intervention is situationally determined, not universal.
  • Kanban flow concepts: The Treading Water state maps closely to a team at WIP limit with no buffer capacity — adding more items into the system creates queue buildup, not faster delivery.

Sources

  • Larson, Will (2019). An Elegant Puzzle: Systems of Engineering Management. Stripe Press. ISBN: 978-1-7322651-8-9.

    • Chapter 2.1: primary articulation of the Four States model and manager-to-engineer ratio guidance.

  • Tuckman, Bruce W. (1965). “Developmental Sequence in Small Groups.” Psychological Bulletin, Vol. 63, No. 6, pp. 384–399. DOI: 10.1037/h0022100

    • Foundational stages of team development (Forming, Storming, Norming, Performing); useful contrast to Larson’s capacity-focused model.

  • Hersey, Paul and Kenneth H. Blanchard (1969). “Life Cycle Theory of Leadership.” Training and Development Journal, Vol. 23, No. 5, pp. 26–34.

    • Situational Leadership model: intervention should match follower readiness — same core logic as the Four States model applied to individuals rather than teams.

  • Anderson, David J. (2010). Kanban: Successful Evolutionary Change for Your Technology Business. Blue Hole Press. ISBN: 978-0-9845214-0-1.

    • Work-in-progress limits and flow-state concepts that parallel the Treading Water vs. Repaying Debt distinction.

  • Reinertsen, Donald G. (2009). The Principles of Product Development Flow: Second Generation Lean Product Development. Celeritas Publishing. ISBN: 978-1-935401-00-1.

    • Queuing theory applied to product development; explains why adding capacity to a saturated system (Treading Water) does not improve throughput.

Note

This content was drafted with assistance from AI tools for research, organization, and initial content generation. All final content has been reviewed, fact-checked, and edited by the author to ensure accuracy and alignment with the author’s intentions and perspective.

Graph View

Backlinks