Team & Organizational · master area
Psychological Safety
Not a soft skill or cultural aspiration. The precondition for honest chain operation. A team that cannot say "the brief was thin" will never fix a thin brief. Silence in a retrospective is system failure.
Owners: Leadership, PO, Tech Lead Phase it lives in: Continuous The corpus principle this enacts: Trace to levels, never to people.
Where it lives in the chain
How to do this
The discipline is structural, not emotional. Safety is not produced by saying "this is a safe space" — it is produced by the team's response when something goes wrong:
| Unsafe response | Safe response |
|---|---|
| "You forgot to write the scenario." | "The amigos session didn't write a scenario for this case." |
| "The PO didn't do their job." | "The observation was incomplete." |
| "Why did this slip through review?" | "Which review checklist item was missing?" |
| "Why didn't you escalate?" | "Was the escalation protocol unclear, or untrained?" |
The chain-aware root-cause labels exist precisely for this — they name the structural level, not the human who operated it.
What good practice looks like
- The retrospective hears "the brief was thin" without anyone feeling exposed — because thinness is a level-of-the-chain answer, not a person answer.
- The postmortem produces "the amigos template was missing this prompt", not "the developer should have been more careful."
- The prediction check delivers "wrong" and the team treats it as the most valuable outcome — not a personal failure.
- Silence in a retro is read as a question — what is the system not letting people say? — not as agreement.
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.
Related crafts
- Postmortem — where chain-level tracing is rehearsed
- Retrospective — where safety is tested every cycle
- Hiring for Chain Fit — does the candidate trace to levels or to people?