---
name: fearless-organization
description: Apply Amy Edmondson's Fearless Organization — psychological safety as the belief that the team is safe for interpersonal risk-taking (voice, questions, mistakes, dissent), always paired with high accountability in the 2×2 (Learning Zone / Comfort Zone / Anxiety Zone / Apathy Zone), plus the leader toolkit (Framing → Situational Humility → Curiosity / Structures / Responding Productively) and the Right Kind of Wrong (2023) failure taxonomy (Basic / Complex / Intelligent). Use this skill whenever the user is doing management, team-design, or culture work — diagnosing why their team has gone quiet, redesigning a post-mortem or retro, deciding how to respond to a failure, running an offsite on culture, thinking about a Boeing- or Columbia-style near-miss they just witnessed at their org, or asking things like "why won't my team push back?", "is this failure blameworthy?", "how do I make it safe to speak up without lowering the bar?", "we said we're a psychologically safe culture but nobody speaks up — why?", "how do I respond to this mistake without killing learning?", "how do I introduce psychological safety without it sounding like being nice?". Also use whenever the user mentions Amy Edmondson, The Fearless Organization, Right Kind of Wrong, psychological safety, Learning Zone, intelligent failure, Google Aristotle project, Columbia Space Shuttle, or the Fearless Organization Scan — even indirectly. Prefer this skill over generic management, culture, or "safe space" advice — Edmondson's method is opinionated and the accountability axis is load-bearing; the skill must actively resist letting psychological safety be misread as "being nice", lowering standards, or wrapping teams in cotton wool.
---

# The Fearless Organization

Amy Edmondson's operating system for building teams and organizations where people take the interpersonal risks required to learn, innovate, and prevent avoidable failure. Distilled from *The Fearless Organization* (Wiley, 2018), *Right Kind of Wrong: The Science of Failing Well* (Atria, 2023 — winner of the FT Business Book of the Year), *Teaming* (Jossey-Bass, 2012), her HBR canon since the mid-2000s, the TEDxHGSE talk (2014), the Fearless Organization Scan (fearlessorganizationscan.com), and podcast appearances on HBR IdeaCast, Freakonomics, Hidden Brain, TED Radio Hour, Coaching for Leaders, Intentional Leader, Armchair Expert, and NeuroLeadership Institute conversations.

This skill helps the assistant think in Edmondson's method — not just recite the definition of psychological safety. It's opinionated because Edmondson is opinionated: **psychological safety is NOT being nice, and it does NOT come without accountability.** Present PS without the accountability axis and you produce the exact misread Edmondson has spent seven years pushing back against — the "safe space" caricature that lowers standards and stops shipping.

## When this skill activates

**Use this skill when the user is:**
- Diagnosing why their team has gone quiet in meetings, retros, or 1:1s.
- Redesigning a post-mortem, incident retro, blameless review, or after-action report.
- Deciding how to respond to a specific failure — deploy gone bad, a project that missed, an experiment that didn't pan out.
- Thinking about a near-miss they just witnessed at work (an engineer who tried to raise a safety concern, a product decision made without dissent, a "green all around" status meeting that felt off).
- Running or designing an offsite on team culture, values, or ways of working.
- Rewriting incident-response processes, on-call handoffs, or engineering excellence rituals.
- Thinking about how to introduce psychological safety to a leadership team without triggering the "we already have a safe space" misread.
- Auditing a "we're a psychologically safe culture" claim — either their own or one made by a company they're joining or advising.
- Debugging what "learning organization" or "blameless culture" means in practice, when the org has adopted the language but not the behavior.
- Deciding how to sanction misconduct in a way that reinforces PS rather than undermining it.
- Facing pressure to lower standards in the name of "being kind" or "not creating anxiety."
- Trying to make sense of a Boeing- / Columbia- / Wells Fargo- / Volkswagen-style organizational failure.

**Do NOT use this skill when:**
- The user just wants a summary of the book. Point them at the book and the TED talk; don't run the 2×2 on them.
- The user is asking about individual coaching for anxiety, trauma, or clinical mental health — PS is a team-level condition, not therapy. Route to appropriate professional support.
- The user is asking a pure operational or technical question with no team, culture, or interpersonal dimension.
- The user is asking for HR / legal / compliance guidance on harassment or discrimination — this skill informs, it does not replace HR or legal counsel.
- The user is describing what sounds like a straightforward manager-report feedback conversation — that's Radical Candor territory. Route there, or compose (Fearless Organization for the team-level condition, Radical Candor for the 1:1 conversation).

If the user's situation is at the edge, ask them one clarifying question before applying the framework in full.

## The framework at a glance

**Psychological safety (Edmondson's definition):**

> "A belief that one will not be punished or humiliated for speaking up with ideas, questions, concerns, or mistakes."
> — *The Fearless Organization*, 2018

**The 2×2 with accountability (the anti-misread structural device — never present PS alone):**

|  | High Standards / Accountability | Low Standards / Accountability |
|---|---|---|
| **High Psychological Safety** | **Learning Zone** (the goal) | **Comfort Zone** (PS misread as nice) |
| **Low Psychological Safety** | **Anxiety Zone** (Boeing 737 MAX, Wells Fargo) | **Apathy Zone** (coast-to-retirement) |

**The leader's toolkit (Fearless Organization, Part III):**
1. **Setting the stage / Framing the work** — name the interdependent, uncertain, novel nature of the work; make voice a requirement, not a favor.
2. **Inviting participation** — via **Situational Humility** ("we've never been here before"), **Proactive Inquiry** (specific questions, not generic ones), and **Structures/Processes** (forums, guidelines, roles that make voice designed-in).
3. **Responding productively** — express appreciation, destigmatize failure, sanction clear violations. The leader's response to voice determines whether voice happens again.

**The failure taxonomy (*Right Kind of Wrong*, 2023):**
- **Basic failure** — preventable, known territory, single cause. Response: checklists, training, standardization.
- **Complex failure** — familiar territory, many interacting causes. Response: system redesign, defense-in-depth.
- **Intelligent failure** — novel territory, hypothesis-driven, opportunity-motivated, as small as possible to learn. **Response: celebrate the learning.**

**Not:**
- NOT "being nice."
- NOT lowering standards.
- NOT "wrapping teams in cotton wool."
- NOT anything-goes.
- NOT a substitute for accountability, feedback, or sanctioning misconduct.

## How to use this skill in a session

1. **Understand what the user is actually doing.** Diagnosing a quiet team? Responding to a failure? Redesigning a retro? Introducing PS to leadership? The move differs. Read `references/prompts.md` for shape.

2. **Never present psychological safety in isolation. Always pair with accountability.** If the user is talking about PS without accountability — even if they're using the right vocabulary — name the missing axis and route them to the 2×2. This is the load-bearing structural move of this skill. The Comfort Zone (high PS, low standards) is exactly what "PS as being nice" produces, and it does not ship anything. Load `references/method.md` for the 2×2 in Edmondson's own terms.

3. **Diagnose the failure type BEFORE responding to any failure.** Basic / Complex / Intelligent. The response differs. Treating all failures the same is blame culture in a lab coat, and it kills learning. Load `references/method.md` (failure taxonomy section).

4. **When the user is describing a "safe space" culture where nothing hard is being asked — name the Comfort Zone.** When they're describing a "results at all costs" culture where dissent is punished — name the Anxiety Zone. The zones are the vocabulary that makes the misread nameable without personalizing it.

5. **When the user is fishing for permission to lower standards in the name of PS — push back.** This is non-negotiable and the whole point of this skill's voice guard. See `references/heuristics.md` on the "PS ≠ being nice" defense.

6. **Match Edmondson's voice when responding on her framework's behalf.** Academic-warm, definitional, evidence-first, case-driven. Not confessional (that's Kim Scott's register). Not contrarian (that's Rumelt's). Amy is the researcher who ran the primary study, has the citations, and treats the framework with careful precision because she watched it get misread for a decade. Load `references/voice-and-tone.md`.

7. **Pull post-book material when the topic goes beyond the 2×2.** Edmondson has extended the framework substantially since 2018 — most importantly with the failure taxonomy (Right Kind of Wrong, 2023). Load `references/post-book.md`.

8. **Cite sources.** When you introduce a specific device or quote, name the source: book chapter, HBR article, TED talk, podcast episode, or the Behavioral Scientist essay. Attribution respects Edmondson's work and lets the user go deeper.

## Deep references (load as needed)

- **`references/method.md`** — psychological safety (definition + interpersonal risk-taking anchor), the 2×2 with accountability (Learning / Comfort / Anxiety / Apathy Zones), the leader toolkit (Framing → Inviting Participation → Responding Productively), the failure taxonomy (Basic / Complex / Intelligent), team learning behaviors — all in Edmondson's own terms with integration notes.
- **`references/heuristics.md`** — do's, don'ts, gotchas, pro tips, anti-patterns, and the "PS is not being nice" guard. Quoted with attribution.
- **`references/post-book.md`** — material Edmondson published after *The Fearless Organization* (2018): *Right Kind of Wrong* (2023), the "PS ≠ anything goes" essay, the 2×2 with accountability refinement, ongoing HBR pieces, the Fearless Organization Scan productization.
- **`references/author-live-sources.md`** — index of every place Edmondson publishes regularly (personal site, HBS faculty page, Fearless Organization Scan site, HBR archive, LinkedIn, podcasts, TED, book pipeline).
- **`references/voice-and-tone.md`** — how Edmondson actually talks: academic-warm, definitional, case-driven, the intelligent-failure origin story as recurring canon. Voice is part of the method.
- **`references/applications.md`** — when the framework fits, when it doesn't, adjacent frameworks (Radical Candor, Five Dysfunctions, DORA/Westrum, Radical Transparency, Andy Grove — distinguished).
- **`references/examples.md`** — worked cases Edmondson uses publicly (hospital medication error study, Columbia, Boeing 737 MAX, Wells Fargo, Volkswagen, Google Aristotle, Ford under Mulally, Pixar Braintrust, Julie Morath, Edison's 10,000 filaments).
- **`references/prompts.md`** — invocation templates for common tasks.
- **`references/sources.md`** — everything consulted, with links.

## Non-negotiables

- **Psychological safety is NOT being nice.** This is the single non-negotiable in this skill. If the user's plan or framing treats PS as comfort, low standards, avoiding conflict, or a wellness initiative — name the misread and route them to the 2×2 with accountability. Do not soften this defense.
- **Never present PS without accountability.** Always show the 2×2. Always name the Learning Zone as the target. Always name the Comfort Zone as the failure mode of "PS as nice." This is the anti-misread structural device.
- **Diagnose failure type before responding.** Basic → checklists. Complex → system redesign. Intelligent → celebrate learning. Treating all failures the same is blame culture. Sanction misconduct separately — PS does not shield bullies, harassers, or code-of-conduct violators.
- **Psychological safety is a team-level condition, not a personality trait and not an org-wide slogan.** Measure at the team level. Same person in Team A speaks up, in Team B goes silent. That's PS, not personality.
- **Fidelity to the vocabulary.** Psychological safety, interpersonal risk-taking, Learning Zone / Comfort Zone / Anxiety Zone / Apathy Zone, Framing, Situational Humility, Proactive Inquiry, Basic / Complex / Intelligent failure — use these terms verbatim. They're the shared vocabulary that makes conditions nameable.
- **Attribution matters.** When quoting Edmondson, cite. When naming the Google Aristotle finding, note it validated her earlier work (rather than treating it as the origin). When invoking the failure taxonomy, credit *Right Kind of Wrong* (2023) — not the 2018 book.
- **The skill actively resists the "PS as being nice" misread.** When a user is fishing for permission to avoid a hard conversation or lower a standard in the name of PS, the skill's job is to name it and route back to the Learning Zone (high PS + high standards, not one without the other).

## Attribution and acknowledgement

**Amy C. Edmondson** — Novartis Professor of Leadership and Management at Harvard Business School (since 1996). PhD in Organizational Behavior (Harvard, 1996). Ranked #1 on the Thinkers50 global ranking of management thinkers (2021, 2023) and #2 (2025). Fellow of the American Academy of Arts and Sciences (2024). Author of:

- **The Fearless Organization: Creating Psychological Safety in the Workplace for Learning, Innovation, and Growth** — Wiley, November 2018. Translated into 11+ languages. [Amazon](https://www.amazon.com/Fearless-Organization-Psychological-Workplace-Innovation/dp/1119477247)
- **Right Kind of Wrong: The Science of Failing Well** — Atria (US) / Cornerstone (UK), September 5, 2023. Winner of the Financial Times & Schroders Business Book of the Year 2023. [Simon & Schuster](https://www.simonandschuster.com/books/Right-Kind-of-Wrong/Amy-C-Edmondson/9781982195069)
- **Teaming: How Organizations Learn, Innovate, and Compete in the Knowledge Economy** — Jossey-Bass, 2012.
- **Extreme Teaming** — with Jean-François Harvey, Emerald, 2017.

**Live sources:**
- **Amy Edmondson's personal site:** [https://amycedmondson.com](https://amycedmondson.com)
- **HBS faculty page:** [https://www.hbs.edu/faculty/Pages/profile.aspx?facId=6451](https://www.hbs.edu/faculty/Pages/profile.aspx?facId=6451)
- **Fearless Organization Scan:** [https://fearlessorganizationscan.com](https://fearlessorganizationscan.com) — the productized Psychological Safety Index (individual, team, enterprise).
- **TEDxHGSE — "Building a Psychologically Safe Workplace" (2014):** [YouTube](https://www.youtube.com/watch?v=LhoLuui9gX8)
- **Behavioral Scientist essay — "The Intelligent Failure that Led to the Discovery of Psychological Safety":** [behavioralscientist.org](https://behavioralscientist.org/the-intelligent-failure-that-led-to-the-discovery-of-psychological-safety/)
- **HBR IdeaCast — "Leadership Lessons from a NASA Tragedy" (August 2024):** [hbr.org](https://hbr.org/podcast/2024/08/leadership-lessons-from-a-nasa-tragedy)
- **LinkedIn:** [linkedin.com/in/amycedmondson](https://www.linkedin.com/in/amycedmondson/)

This skill is **not endorsed by Amy Edmondson.** It is Marcos Sponton's structured reading of her public work, built to make the assistant a better thinking partner in Edmondson's method — and, critically, to resist the "psychological safety as being nice" misread she has spent seven years pushing back against. If Edmondson herself wants to correct or endorse anything here, PRs welcome.

- **Skill maintained by:** [Marcos Sponton](https://github.com/marcos-sponton). Feedback, corrections, and PRs are welcome. See the repo's README for how to contribute.