Communicating Top-Down Change

## Overview Goal: Deliver measurable improvements in safety, efficiency, and cost while maintaining trust, clarity, and adoption across levels. Principles: - Start with data and clear targets (baseline → goals → mechanisms → metrics). - Adapt message to each audience’s incentives and control. - Use short feedback loops (pilot → measure → iterate → scale). - Make the change easy to do, safe to try, and valuable to keep. Example targets (adjust to your context): - Safety: −20% Total Recordable Incident Rate (TRIR). - Efficiency: +10% throughput or −15% cycle time. - Cost: −$0.25 cost per unit/order. Useful formulas: - Cost per unit = Total variable costs / Units produced. - Efficiency (throughput) = Units completed / Time. - Safety (e.g., TRIR) = (Recordable incidents × 200,000) / Total hours worked. --- ## 1) Peer Managers (Cross-Functional Alignment and Governance) Objective: Align on business case, scope, dependencies, and governance to avoid conflicting changes and to unblock resources. Message focus (what they care about): - Why: Business case with quantified impact and risk reduction. - What: Scoped initiatives, milestones, and decision rights. - How: Governance, resourcing, and risk/issue management. - Proof: Pilot results, KPIs, and leading indicators. Channels and cadence: - Kickoff: 60-minute alignment meeting; co-create success criteria. - Weekly steering committee: Risks, decisions, cross-team dependencies. - Shared dashboard: Real-time safety, efficiency, and cost metrics. - Monthly review: Variance vs plan, corrective actions, and escalation. Artifacts: - 1-page brief: Problem, goals, scope, ROI, timeline, owners. - RACI for workstreams. - Roadmap with milestones and exit/entry criteria. - Metrics glossary and a single source of truth dashboard. Mechanisms: - Pilot-first approach with control groups when feasible. - Change freeze windows to reduce operational noise. - Pre-mortem on top 5 failure modes (e.g., throughput dip, adoption stall). Risks and mitigations: - Priority conflicts → Agree on a ranked backlog and capacity plan. - Metric gaming → Use a balanced scorecard (safety, quality, delivery, cost). - Cross-site variability → Standardize minimum viable standard work; allow local flex. Sample talking points: - "We’ll pilot on Line B during Shift 2 for two weeks targeting −15% cycle time. If successful, we’ll scale by end of Q, contingent on safety staying flat or better. Steering meets Fridays to unblock resourcing and approve scale-up." --- ## 2) Managers Who Report to You (Enablement and Accountability) Objective: Turn strategy into executable plans, equip managers, and create accountability with supportive coaching. Message focus: - Why: Link to team goals, safety of their people, and budget impact. - What: Specific changes to SOPs, staffing, scheduling, and quality checks. - How: Playbooks, training plans, and escalation paths. - Ownership: Clear targets per area and how performance is measured. Channels and cadence: - Manager kickoff: Walk through playbook, targets, and timeline. - Weekly ops sync: Progress vs. plan, blockers, and help needed. - Daily tiered huddles: Managers run 10–15 minute huddles with teams. - 1:1s: Coaching on change leadership and performance conversations. Artifacts: - SOP updates with before/after process maps. - Training plan: who, what, when; certification sign-off. - Visual boards: Safety, throughput, defects, cost per unit. - Issue log with SLA for resolution. Mechanisms: - Change champions per area/shift. - Standard work audits and Gemba walks with checklists. - Incentives aligned to balanced outcomes (e.g., efficiency gains that do not compromise safety/quality). - Capacity plan that accounts for training time to avoid burnout. Risks and mitigations: - Change saturation → Stage rollouts; avoid overloading peak periods. - Skill gaps → Microlearning, job aids, buddy system. - Inconsistent application → Daily audits and quick corrective coaching. Sample talking points: - "Each area manager owns a weekly target: −10% rework and +8% throughput with zero increase in near-misses. We’ll run daily huddles, submit issues via the log by 2 p.m., and review in the Wednesday ops sync." --- ## 3) Front-Line Employees (Clarity, Safety, and WIIFM) Objective: Ensure people doing the work understand what’s changing, why it matters, how to do it safely, and how to give feedback. Message focus (plain language): - Why: "We’re making your job safer and easier while reducing waste." - What: Simple 3–5 key changes to steps/tools. - How: Hands-on demos, checklists, and shadowing. - WIIFM: Fewer injuries, less rework, smoother shifts, recognition. Channels and cadence: - Shift kickoff briefings with visual aids (5–10 minutes). - Hands-on training and certification; buddy support first 1–2 weeks. - Daily huddles: Yesterday’s wins, today’s focus, top issues. - Open feedback: QR/poster link, hotline, or kiosk form; anonymous option. Artifacts: - Laminated job aids at the workstation. - Before/after pictures and short videos (no jargon). - Visual management: Andon/issue cards and improvement boards. - FAQ sheet addressing common concerns. Mechanisms: - Pilot with volunteers; early adopter recognition. - Stop-work authority reinforced; safety trumps throughput. - Rapid response to issues reported within the shift. - Multilingual materials; translate and demo in worker languages. Risks and mitigations: - Fear of change → Emphasize safety first and show quick wins. - Confusion → Keep instructions to 1 page; repeat and demo. - Skepticism → Share pilot data and stories from peers. Sample talking points: - "Two changes today: 1) New cart height to reduce back strain; 2) Label scan step moves to the end. Watch this 60-second demo, then try it with a coach. If anything feels unsafe, raise the card and we’ll stop and fix it." --- ## End-to-End Plan (Concise) 1) Define baseline and targets per area (safety, efficiency, cost). Create a metrics glossary and dashboard. 2) Co-design with peer managers: scope, pilots, and governance. 3) Prepare enablement: SOPs, training, job aids, and capacity plan. 4) Pilot on one line/shift/site. Compare to control where feasible. 5) Measure and decide: If safety holds and KPIs improve, scale; if not, iterate. 6) Scale in waves; maintain daily huddles and weekly reviews. 7) Sustain: Standard work audits, refresher training, and continuous improvement ideas. Example numeric guardrails: - Proceed to scale only if: TRIR does not increase; efficiency +8% or more; cost per unit −$0.15 or more; defect rate does not worsen. - Roll back if safety/quality degrade for two consecutive days in pilot. --- ## Validation and Guardrails - Baseline accuracy: Verify data sources for safety, throughput, and cost before setting targets. - Equity and compliance: Consider union rules, ADA accommodations, and multilingual access. - Change load: Map other initiatives; limit concurrent changes per area. - Feedback loop: Track issue resolution SLA; publish fixes to build trust. - Post-implementation review: 30/60/90-day checks to confirm sustainment. This approach meets each audience where they are, ties work to measurable outcomes, and uses clear mechanisms to drive adoption without compromising safety or quality.