after we build · part eight

The Team

The chain is operated by people. How they learn it, how they grow within it, what happens when the team is too small for all the roles, and why psychological safety is not a soft skill — it is the precondition for honest retrospectives.

Onboarding to the chain

A new team member does not need to read five volumes before contributing. They need to understand one cycle.

The onboarding discipline: shadow one story through its full journey — from the brief through the Epic kickoff, the amigos session, the pull, the code, the review, the release. Not doing the work — watching it, asking questions, building the mental model of how meaning travels. One cycle, witnessed, is worth more than all five volumes read.

After the shadow cycle, the new person pulls their first story — a small one, with a more experienced developer available for questions. The PO walkthrough is longer for this first story. The amigos session is more explicit. The chain teaches itself through contact, not through study.

T-shaped people

A T-shaped person has deep expertise in one area and working understanding of adjacent areas.

• A developer who understands how the designer thinks about states.
• A designer who understands why the API contract constrains the flow.
• A PO who can read a sequence diagram well enough to ask the right question.

The T-shape is what makes the trio work — three people who can challenge each other's assumptions because they understand enough of the adjacent craft to know when something is missing.

The chain produces T-shaped people naturally. A developer who reads the brief and walks through the moment with the PO develops product sense. A designer who reviews the Storybook catalogue develops technical sense. The chain's boundary crossings — amigos, the PR review with three confirmations, the retrospective — are the mechanisms that build the horizontal bar of the T.

When the team is too small

Not every team has a dedicated PO, designer, tech lead, QA, and multiple developers. Some teams are three people. Some are two. The chain still applies — the roles are combined, not eliminated.

A developer who also does QA still writes scenarios and checks them. A PO who also designs still produces wireframes and names states. The discipline is: which chain level am I operating at right now? A person wearing two hats switches consciously, not unconsciously.

The risk of small teams is not missing a role — it is losing the challenge that the missing role would have provided.

Continue — The human side: safety, departures, and joining →