Frame uncertain work as learning
Before starting a challenging project, name it explicitly as an experiment where mistakes generate information.
Why it works
How work is framed shapes the cost of candor. A performance frame makes errors evidence of failure; a learning frame makes errors evidence of engagement with a hard problem. Edmondson distinguishes "performance-oriented" from "learning-oriented" climates — the latter predicts more speaking up, more error reporting, and better adaptation in uncertain work.
How to do it
- Open a new project or uncertain initiative with explicit framing: "We don’t know the right answer yet — this is where we learn."
- Distinguish routine execution (where errors are unwanted) from complex problem-solving (where errors are information).
- At milestones, ask "what did we learn?" before "how did we perform?"
- Reward teams for surfacing problems early, not just for clean delivery.
Evidence
Learning goal orientation is associated with greater resilience, more help-seeking, and more candor under uncertainty compared to performance goal orientation, across educational and organizational settings. (observational)
Framing effects are real but context-dependent; in settings where baseline standards matter (surgery, aviation), a pure learning frame without accountability can normalize avoidable errors. The two must be calibrated together.
Sources
- Dweck (1986), learning vs performance goal orientation, Journal of Personality and Social Psychology
- Edmondson (2012), Teaming: How Organizations Learn, Innovate, and Compete in the Knowledge Economy
Common mistake
Framing all work as learning ("it’s just an experiment") to avoid accountability — which erodes the distinction between genuinely uncertain work and the routine execution where standards actually apply.
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for Psychological Safety in Teams
- Model fallibility as the leader
Openly acknowledge your own uncertainty and mistakes before expecting others to do the same.
- Invite input explicitly and specifically
Ask for candid input on a specific topic — not "any thoughts?" but "where do you see this plan failing?"
- Respond non-punitively to mistakes
When someone brings you a problem or mistake, make your first move curiosity, not blame.
- Teach speak-up skills, not just encourage speaking up
Give team members specific language for raising concerns, not just permission to raise them.
- Run brief after-action reviews without blame
After any significant outcome — success or failure — ask four questions together as a team.