District manager rollout cadence

HQ launches a new SOP. The district manager is the bridge — they decide what hits which stores when, who needs special attention, what the local context demands. Get the cadence right and adoption is high, store managers feel supported, and rollouts compound. Get it wrong (everything to every store on the same day, or rolling at random across weeks) and adoption drops, store managers tune out, and the next rollout is harder than the last. ## What HQ controls vs what the district manager controls HQ controls: the content of the rollout, the network deadline, the assigned modules, the brand standards being changed. The district manager does not edit any of these. The district manager controls: the timing within the deadline window, the order of stores, the level of personal attention given to each store. Three levers, all important. ## The standard cadence For a typical SOP rollout with a 14-day network deadline: **Days 1–2: HQ pre-brief.** The district manager receives the rollout from HQ 48 hours before frontliners get assigned. They read the content, identify which of their stores will need extra attention, brief the relevant store managers individually. **Days 3–5: Wave 1 stores.** The district manager's strongest 3 stores get the rollout first. These are the stores that adopt fast, finish early, and provide a benchmark for the rest. They also surface any rollout content issues (a confusing module, a typo) before the network sees them. **Days 6–9: Wave 2 stores.** The middle of the network — the bulk of the district. The district manager shares the wave-1 completion data as a benchmark ("the first 3 stores hit 90% in 3 days, here's what they did differently"). **Days 10–14: Wave 3 stores.** The stores that need extra attention — newer managers, locations with historic completion issues, sites with any current operational distress. The district manager spends more 1-on-1 time with these store managers, may visit in person. **Day 14+: Catch-up window.** Anyone outstanding gets direct district-manager intervention. The district manager closes out the rollout. Three waves, with the district manager's effort concentrated where it matters. This pattern works because the wave-1 data informs the wave-2 brief, the wave-2 data informs the wave-3 brief, and the high-touch stores never feel like an afterthought. ## When to break the pattern Three exceptions: **Compliance rollouts.** Anything regulated (food safety updates, harassment policy revisions) goes everywhere on day one. The deadline is non-negotiable; waving creates legal exposure. **Crisis-driven rollouts.** A product recall, a brand-reputation issue, an emergency procedure update — all stores at once, fastest possible cadence. Speed matters more than smoothness. **Major launches.** A network-wide menu launch or a new product category — coordinated to a launch date. All stores live the same day; the district manager's role shifts to readiness verification, not staged adoption. For everything else — the routine SOP updates that account for 80% of rollouts — the wave model is the default. ## What the district manager tracks During an active rollout, three numbers per store: 1. Days since assignment. 2. Current completion rate. 3. Days to deadline. These live in the district-manager dashboard. Aristotl's manager dashboard surfaces these per-store during active rollouts, with the wave assignment visible. The district manager opens the dashboard once a day during a rollout, scans for stores that are off-pace, intervenes. ## The store manager's experience From the store manager's perspective, the district-manager cadence translates into clear communication: "You're in wave 2, expect the assignment Friday, here's what to watch for based on what wave 1 saw." Predictable, contextual, brief. Stores that constantly land in wave 3 (the high-touch group) need development attention, not just rollout attention. If a store is in wave 3 for three consecutive rollouts, the issue is the manager, not the rollouts. The district manager addresses that separately. ## What HQ should not interfere with The one mistake HQ makes consistently: pushing district managers to compress the cadence. "Why can't all stores complete by day 7?" The compression usually means wave 1 and wave 2 are still working, but wave 3 (the high-touch stores) gets compressed and adoption drops in the locations that needed the most support. The 14-day window with three waves exists for a reason — let it run. The one thing HQ should require: every district manager runs the same cadence framework. Network-wide visibility into rollout progress depends on every district running the same model. If one district waves and another goes flat, the rollup dashboard becomes hard to read. ## What changes when this is in place Districts running structured wave cadences see consistent rollout completion 14 days post-launch — typically 90-95% network-wide, with the high-touch stores landing at 85-90%. Districts running flat or random cadences see network-wide variance of 30 points or more, with the same stores stuck behind every rollout. The cadence is the difference.

Ready to put this into practice?