Schema change scales with group size
Scale your timeline expectations for schema change with group size—weeks for pairs, quarters for 50-person orgs, years for industries—and measure progress in behavioral change rather than stated agreement.
When This Fires
- When planning any initiative to change how a group thinks
- When impatient about the pace of organizational or team schema change
- After getting agreement but not seeing behavioral follow-through
- When setting timelines for cultural, process, or framework changes
Common Failure Mode
Expecting organizational schema change at individual speed: "I understood the new approach in a day, so the team should get it in a week." Your individual schema update doesn't include the coordination overhead, the social proof requirements, the exception handling that emerges during real use, or the infrastructure migration that the group change requires.
The Protocol
When planning schema change for a group: (1) Estimate group size. (2) Set timeline expectations: pairs → weeks, teams → months, organizations → quarters, industries → years. (3) Measure progress by behavior, not agreement: track what people actually do in decisions, not what they say they believe. (4) If behavioral change lags stated agreement by more than one review cycle → the schema hasn't actually changed yet. The agreement is performative; more shared experiments (Shift team schemas through shared experiments…) are needed.