Shift team schemas through shared experiments, not presentations — experience changes beliefs, slides do not
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.
Why This Is a Rule
Shared schemas are resistant to argument because they're sustained by shared experience, not by shared intellectual agreement. A team that "believes in velocity tracking" doesn't believe it because they read a compelling article — they believe it because they've experienced velocity tracking producing useful predictions. The schema is maintained by experience, and only new experience can shift it.
Presentations and documents appeal to intellectual agreement: "Here's why we should switch from velocity to cycle time." The team nods, agrees in principle, and continues using velocity — because their shared experience still supports velocity, and the presentation provided no shared experience of cycle time.
Low-cost experiments provide the shared experience: "For the next sprint, let's track cycle time alongside velocity and compare the predictions." Now the team experiences cycle time on a real decision. If cycle time produces better predictions, the shared experience shifts the schema. If it doesn't, the experiment cost was minimal and the old schema is validated.
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.