Shift team schemas through shared experiments…
When attempting to shift a shared team schema, create low-cost experiments where the team uses the new schema on one real decision, rather than presenting the new framework in slides or documents.
When This Fires
- When you want to change how a team thinks about a recurring process or decision
- When previous attempts to shift team thinking through presentations or documents failed
- When intellectual agreement exists but behavioral change hasn't followed
- Any context where a shared schema needs to evolve
Common Failure Mode
Presenting the new framework compellingly and assuming the schema will shift: "Everyone agreed in the meeting, so we're aligned." Intellectual agreement and operational schema change are different things. The team agreed with the logic but hasn't experienced the alternative. Without shared experience, they'll revert to the old schema under pressure.
The Protocol
When shifting a team schema: (1) Don't present the new framework in slides. (2) Design a low-cost experiment: "Let's use [new approach] for one real decision and observe the result." (3) Run the experiment with the whole team participating. (4) Debrief: "What did we observe? How did this compare to our usual approach?" (5) The shared experience of the experiment — not your argument — is what shifts the schema. If the experiment produced better results, the team has experienced evidence. If not, the old schema is vindicated and you've saved the team from an untested change.