part eight · the team
The Team
Onboarding, T-shaped people, small teams, psychological safety, what happens when someone leaves.
Onboarding is a defined cycle, not an orientation week. One-to-ones are weekly, fifteen minutes, owned by the manager. Capacity planning is monthly. Hiring is governed by chain fit, not individual brilliance.
The chain works because people work it. This part of the volume is about the human infrastructure — what makes the team able to run a cycle, keep running it, and stay alive while doing so.
Onboarding to the chain
A new person on a chain-running team does one full cycle in shadow. Not a week of orientation. A cycle.
| Cycle phase | What the new person does |
|---|---|
| Week 1 | Reads the corpus front to back. Pairs with the PO on a Discovery session. Joins amigos. |
| Weeks 2–3 | Pulls one small story alongside a developer. Writes their first prediction with the PO's review. |
| Week 4 | Owns a story end to end. Files the first bug they author. Writes a model-update line. |
| Week 6 | Has been part of one full cycle. Joins their first retro as a participant, not a guest. |
The onboarding is over when the new person can read the chain artifacts and know what is missing without being told.
T-shaped development
A T-shaped person is deep in one craft, working in two or three adjacent ones. Deep enough to ship the deep one alone. Wide enough to talk to the people on either side.
In a small team, this is not optional. A developer who can't read a brief slows the trio. A PO who can't read a sequence diagram pushes architecture decisions to a meeting that should have been a comment. A QA who has never opened the codebase will write Gherkin that's mechanically correct and structurally meaningless.
The corpus is meant to expand the horizontal of the T. Each volume is written so that a non-specialist in the volume's craft can still read it and act on it.
Small team adaptation
A team of three runs the same chain as a team of nine. The roles do not disappear. They combine.
- PO + Designer — common combination. The PO does feature briefs and journeys; brings in design help on visual systems and review.
- Developer + Tech Lead — the senior dev wears the lead hat in ADRs and pipeline decisions.
- PO + QA — the PO writes amigos themselves; QA review is contracted out for high-risk releases.
The hat is conscious. I am writing this brief as PO and I am reviewing it as QA are different stances even when they are the same person. The chain holds because the artifacts are stance-shaped, not person-shaped.
What does not combine: incident commander, communicator, investigator. Even on a one-person on-call, the hats switch in time. Right now I am the commander. I will not investigate for the next ten minutes.
Psychological safety
Safety in this corpus is not about feelings. It is about whether the chain can hear what it needs to hear.
The chain hears badly when:
- People bring problems and leave with blame.
- Postmortems trace incidents to individuals instead of levels.
- Predictions are scored as personal performance instead of model accuracy.
- Silence in a retro is treated as agreement.
The chain hears well when:
- Defects are traced to chain levels first, individuals last.
- Wrong predictions are explicitly the most valuable outcome short of not checked.
- The team's manager reads the postmortem and asks what changed in the brief template, not who missed this.
- Silence is treated as a system signal — what is the system not letting people say?
This is structural. A team that says it is safe and produces postmortems with no structural fix is not safe. A team that produces structural fixes from every incident is safe — whether or not anyone says the word.
Knowledge retention
A person leaves. The cycle continues. The corpus is what makes that true.
Three artifacts carry the load:
- Briefs and ADRs — the why. The decisions, with their rejected options.
- Runbooks — the what to do when. The operational memory.
- The model file — the assumptions, witnessed and not, with status and dates.
Slack threads are not knowledge retention. Email is not knowledge retention. The corpus is. When someone leaves, the question is not who knew this. The question is which artifact has it. If the answer is nobody wrote it down, that is a chain gap, and the next retrospective owns it.
Team capacity planning
Monthly. Three numbers and a question.
- Cycles in flight — how many initiatives is the team currently inside?
- On-call recovery — when did the on-call last get a clean week?
- Discovery debt — how many briefs are due for refresh and overdue?
The question: what would have to be true for the team to take on one more thing? If the answer is nothing changes, the team is over capacity and is paying for it in chain debt.
The instinct under pressure is to shorten the cycle. The corpus is structured against that. Cutting Discovery to ship faster trades a known cost (a longer cycle) for an unknown cost (a feature that solves the wrong problem). The Discovery cost is paid in days. The wrong-problem cost is paid in months.
Hiring for chain fit
The corpus is opinionated. Not every excellent engineer or designer or PM thrives in it. Hiring needs to be honest about that.
Look for, in interview:
- Does the candidate name a person when describing past work? Or do they say the user?
- Can they describe a prediction they made and got wrong, by name? Or do they describe wins only?
- Do they trace defects to chain levels, instinctively? Or do they personalise — the engineer didn't catch it?
- Can they hold their craft and read an adjacent one? Vertical and horizontal.
- Are they comfortable with structural tools — checklists, templates, conventions — or do they treat them as bureaucracy?
The hiring bar is not better than the team. It is adds something the chain is missing without breaking what the chain is doing.
Cross-team coordination
A growing team eventually has more than one chain running in parallel. The coordination problem is not staff allocation — it is shared state.
Three artifacts handle it.
- Shared services registry — what does each chain consume from each other? Versioned, with owners.
- ADR cross-references — when one chain's ADR constrains another, both ADRs link.
- Portfolio review (Part 9) — sees both chains together. Catches the conflict that no individual cycle can see.
What does not work: ad hoc Slack channels for coordination. They produce decisions no one can find next quarter. The artifacts are the coordination.
Enough to know the chain has runners.
Onboarding has produced a person who can read the chain. One-to-ones have run. Capacity is honestly named. Knowledge retention artifacts are current. The team can lose one person and continue.