Why Pull Beats Push When Leading Change
Summary
An organization adopted an incremental, step-by-step approach to implementing change, deliberately avoiding disruptive methods. This strategy focused on gaining conceptual approval, then scaling, and ensuring understanding among stakeholders. The organization found that "pushing" change was ineffective, leading to lower adoption rates among teams. A key component of their strategy involved educating leaders by connecting new concepts, like OKRs, to existing cultural frameworks such as their MBO (Management by Objectives) system, which resonated due to its emphasis on focus and iteration. Additionally, a "playbook" was developed to clarify processes and empower teams to adapt the changes to their specific contexts, despite initial reluctance to create such a prescriptive guide.
Key takeaway
For operations professionals implementing organizational change, prioritize an incremental approach over disruptive overhauls. Your teams will achieve higher adoption by ensuring leaders understand the "why" through familiar cultural touchpoints, like linking OKRs to existing MBOs. Create clear, adaptable playbooks to empower teams to integrate changes effectively, rather than simply dictating new processes.
Key insights
Incremental change, supported by leader education and clear guidance, fosters higher adoption than disruptive, top-down mandates.
Principles
- Avoid pushing change; it reduces adoption.
- Connect new concepts to existing cultural frameworks.
- Provide clear guidance for adaptation.
Method
Implement change incrementally: secure concept approval, scale, ensure understanding. Educate leaders by linking new models (e.g., OKRs) to familiar cultural elements (e.g., MBOs). Create playbooks to simplify adoption and allow for team ownership.
In practice
- Start with easier changes first.
- Develop a playbook for clarity.
- Relate new initiatives to current systems.
Topics
- Incremental Change
- Organizational Change Management
- Leadership Buy-in
- OKRs
- Change Playbook
Best for: Product Manager, Entrepreneur, Consultant, Operations Professional, Executive
Related on AIssential
Editorial summary, takeaway, and curation by AIssential. Original article published by MIT Sloan Management Review.