Interactive graph
Psychological Safety
Table of Contents
People can name mistakes and near-misses without fear of humiliation or retaliation.
Key Concept
- Join their framing before you redirect the blame.
- Level 1: Listen to how they see what happened before you talk about blame - like hearing their side before you pick a fix.
- Level 2: First listen to how they see what happened, then gently help them see what to fix - do not jump straight to who is at fault.
- Level 3: Join their framing before you redirect - blame last, learning first.
- Level 4: Because shame shuts down honest data, alignment on story precedes correction - they must feel heard before the fix lands.
- Level 5: Join their framing before you redirect the blame - safety is not soft standards; it is sequence that keeps truth on the table.
- Near-miss reports need gratitude, not punishment.
- Thank the person for speaking up - silence teaches the next person to hide the miss.
Examples
- My kid told me he broke the vase - I thanked him for saying it instead of making him dread confessing next time.
- I named the wrong turn to my carpool - nobody mocked it, so I speak up before the next missed exit.
Note Relationships
| Relationship | Wikilink | Reason |
|---|---|---|
| contradicts | Break the Escalation Cycle | when the opposite frame fits better |
| extends | Follow Their Lead | Join their framing before you redirect the blame |
| extends | Heed Every Near-Miss | People name near-misses when retaliation is not the cost |
| extends | Listen Before Fixing | People speak up when being heard beats being fixed |
| extends | Name the Feeling | Naming emotion without punishment keeps reporting honest |
| extends | Own the Error | Owning mistakes needs a room that will not punish honesty |
| extends | People-Centered Design | People tell you what breaks when honesty is safe |
| extends | Shadow the Work | Real workarounds show when punishment is not the cost |
