Timing a cascade across sites without leaving regions guessing
Practical sequencing for multi-site announcements so regional teams hear news from their managers, not from a group chat.
Multi-site organisations in New Zealand often announce from Wellington or Auckland and hope the regions keep pace. Hope is not a sequence.
Build from the furthest shift backward
Start with the site or shift that is hardest to gather — overnight warehouse, remote depot, after-hours clinical team — and place their briefing first on the clock. Work backward so executive announcements do not leak ahead of those rooms.
Give regional managers the same pack, not a diluted one
Cutting detail “to keep it simple” for regions creates a two-class message. Simplify language for everyone; do not withhold facts that local leaders need to answer floor questions.
Plan the hour after the briefing
Staff will text colleagues at other sites immediately. Agree what managers say if someone asks, “Did Christchurch hear this yet?” A coordinated cascade includes that meta-conversation.
Leave space for local colour
National messages should reserve a paragraph for site-specific implications: parking, roster patterns, customer hours. Local leaders fill that paragraph; central teams should not invent it from afar. This is ordinary change discipline, and it prevents a polished head-office story from sounding tone-deaf on the ground.