Frame the work as a learning problem, not an execution problem

Name the uncertainty and interdependence out loud so people expect to learn, not just deliver.

Why it works

People stay silent when they assume the work is a solved execution problem and that speaking up signals incompetence. Explicitly framing the work as uncertain and interdependent resets that assumption: if no one has all the answers, then questions and dissent become contributions rather than admissions of weakness.

How to do it

1. State plainly what is uncertain or novel about the work before you start.
2. Say out loud that you need everyone’s observations because no one person can see it all.
3. Reframe errors as data the team needs, not as failures to be hidden.

Evidence

Edmondson’s field studies of hospital teams found that framing and leader behavior shaped whether teams surfaced errors and learned from them, with safety mediating the link between leadership and team learning. (observational)

The core research is observational/field-based; causal direction (safety → learning) is inferred, not proven by experiment.

Sources

• Edmondson (1999), "Psychological Safety and Learning Behavior in Work Teams", Administrative Science Quarterly

Common mistake

Telling people "there are no stupid questions" while still treating the work as a checklist to be executed perfectly — the framing and the behavior contradict.