1️⃣ Problem – Hidden Costs of “Push” Change
Every Tech Manager who introduces KMM transition practices has felt the jolt: policies are “pushed” in, flow metrics go up—but so do resignations and hallway grumbles. Unchecked, this collateral damage stalls maturity climbs and poisons culture. The real risk isn’t losing people; it’s losing the right people while the loudest detractors stay and erode trust.
2️⃣ Lesson – Diagnose Why People Push Back
The passage reminds us that resistance is multifaceted. • Replaceable roles may exit with dignity if transitions raise the talent bar. • Irreplaceable experts resist because they love the mission—listen, negotiate, keep them onboard. • Belief-based skeptics fear identity loss; reframe change around shared purpose. • Malevolent saboteurs attack the messenger; tolerate zero toxicity and escalate fast. Understanding these archetypes turns blanket “push” into a targeted engagement strategy.
3️⃣ Action – Four-Step Playbook for Tech Managers
1. Map Influence vs. Criticality: list roles, rank business impact and change appetite; tailor coaching effort to each quadrant.
2. Create Safe Dialogue Loops: host weekly “Why This Change?” clinics where objections are surfaced, logged, and tied to higher-level goals (OKRs, customer outcomes).
3. Design Exit & Retain Paths: Pre-plan graceful exits for fungible roles and craft stay incentives (learning budgets, role clarity) for essential experts.
4. Escalate & Neutralize Toxicity: Train leads to spot personal attacks early, and involve HR or mediators before cynicism spreads.
4️⃣ Result – A Culture That Pulls Improvement
Teams move from compliance to advocacy when resistance is addressed, not suppressed. Flow bottlenecks surface sooner, WIP limits stick, and maturity jumps feel evolutionary, not traumatic. The payoff is a workforce that chooses to improve, sustaining ML-by-ML progress without burning social capital.