Schema change scales with group size: weeks for pairs, quarters for 50-person orgs, years for industries

Why This Is a Rule

Schema change through a group takes longer than schema change in an individual because every person in the group must update independently, AND the coordination patterns built on the old schema must be rebuilt for the new one. Group size determines the timeline because: more people = more individual updates required, more coordination patterns to rebuild, more social inertia to overcome, and more communication overhead in propagating the change.

The scaling relationship: Pairs (2 people) → weeks. Two people can share an experiment, discuss the results, and converge within a few conversations. Small teams (5-15) → 1-2 months. Requires shared experiments, visible results, and several decision cycles using the new schema. Organizations (50-200) → quarters. Requires structural changes, training, and multiple rounds of cascading adoption. Industries (thousands+) → years. Requires generational turnover, competitive pressure, or regulatory forcing functions.

The measurement criterion is equally important: progress in behavioral change, not stated agreement. "We all agree we should use the new framework" (stated) is not the same as "we're all actually using it in daily decisions" (behavioral). Stated agreement often precedes behavioral change by months — and sometimes stated agreement exists without behavioral change ever following.

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, not presentations — experience changes beliefs, slides do not) are needed.