Pilot plant metrics look good; second site distorts—config scrambled, definitions diverge, coach still stuck at pilot. Scale failure is not second site effort—it is success not written as standard actions: which config frozen, which localized, who trains whom, what counts as scaled. Without standards, scale is another project from zero.
Standardization is not erasing site differences—it locks replicable core and whitelists required local variation.
Extract a Replicable Pack First
From pilot pull: master data rules, process nodes, role action cards, metric definitions, common exceptions. Package as "scene pack"—second site fills local warehouse, shifts, equipment list—no redrawing process. Pilot heroes become operation coaches—not permanent onsite.
- Freeze list: codes, state machines, acceptance definitions—no private second-site edits.
- Open list: default warehouse, printers, shift calendars.
- Scale complete: two consecutive weeks without pilot staff fixing numbers.
Scale Is Delivery, Not a Tour
The XYN digital intelligence system uses configurable scene packs to lower scale cost—second site targets same core. Scale budget should include coach rotation—not license alone. With standard actions, company-wide scale is possible; without them, pilot stays a showroom island.
Next rollout: deliver scene pack before kickoff. No pack—not scale, just another start from zero.
