The Like-like change management framework bridges the gap between structured technical execution and broad organizational adoption. While these core concepts are often discussed in IT infrastructure and software lifecycles, their underlying principles apply directly to overall business operations, process transformations, supply chain shifts, and administrative reorganizations.
Key concepts
Here is how those key concepts translate into everyday business management:
1. Dual-Track Alignment: “Big C” vs. “Little C”
- The Concept: Distinguishes between Organizational Change Management (“Big C”)—managing culture, stakeholder buy-in, training, and human behavior—and Technical Change Management (“little c”)—controlling exact operational procedures, release schedules, and system configurations.
- Operational Application:
- Avoid the Silo Trap: Operational failure often occurs when leaders focus solely on execution (“little c”) while ignoring human readiness (“Big C”), or vice versa.
- Practical Example: Rolling out a new procurement process require both operational controls (updating templates, routing logic, approval gates) and human enablement (explaining why the old process failed, addressing team anxieties, providing hands-on training).
2. “Like-for-Like” Upgrades (Scope Control)
- The Concept: Isolating infrastructural or procedural updates from process changes. By replacing a core component with a newer version without introducing new workflows or features simultaneously, you minimize operational risk and make root-cause troubleshooting straightforward.
- Operational Application:
- Decouple Risk Factors: When updating standard operating procedures (SOPs), vendor contracts, or core facilities, avoid bundling major feature enhancements or policy overhauls into the same release window.
- Practical Example: If replacing a regional logistics supplier, keep delivery schedules, packaging specs, and ordering thresholds identical for the first 90 days. Once the new supplier stabilizes the baseline service, introduce route optimizations or new packaging guidelines.
3. Time to Availability & Service Recovery
- The Concept: Measuring operational resilience through the lens of availability, minimizing Mean Time to Recovery (MTTR), and ensuring business continuity terms reflect realistic service-level agreements (SLAs).
- Operational Application:
- Focus on Resiliency over Perfection: Operational disruptions (supplier delays, staffing shortages, equipment maintenance) are inevitable. Operations should be designed around how fast an operational unit can return to a stable, revenue-generating state.
- Practical Example: Establish clear operational fallback protocols—such as secondary vendor agreements or standardized manual workarounds—so frontline teams can maintain customer service levels immediately if a primary process breaks down.
4. Pragmatic Agility (Proportional Governance)
- The Concept: Agility is an operational mindset rather than rigid, ritualized frameworks. Change governance should scale proportionally to the risk, complexity, and scope of the proposed modification.
- Operational Application:
- Right-Size Approval Gates: Avoid applying the same heavy-handed oversight committee to minor daily administrative tweaks that you apply to major corporate restructuring.
- Practical Example: Categorize operational changes into tiered pathways (e.g., Standard/Low Risk, Medium Risk, High/Strategic Risk). Empower departmental teams to execute low-risk changes autonomously while reserving executive review panels for cross-functional or high-impact initiatives.
5. Managing Human Resistance & Expectations
- The Concept: Recognizing that humans naturally prefer consistency and stability. Successful change management relies on establishing a clear point of reference and addressing the psychological inertia of workforce teams.
- Operational Application:
- Over-Communicate Context: Clearly define the “from/to” state so employees understand what is changing, what is staying the same, and why the shift is necessary.
- Practical Example: When introducing automated scheduling software to a field service team, anchor the messaging around preserving what employees value (predictable hours, fair dispatching) before introducing the mechanics of the new software tool.
Summary
“Like-for-like” is not merely a technical implementation strategy; it is a broader change-management principle that reduces risk by separating necessary change from optional improvement
Like-for-like change is ultimately about more than replacing technology, updating a process, or changing a supplier. It is a disciplined approach to managing change by controlling the number of variables introduced at any one time. The principle is simple: change what must change, preserve what does not need to change, and defer improvements that can safely wait. This creates a stable baseline against which the organization can measure the impact of the change, identify problems, and recover quickly when something does not go as expected.
The approach also highlights an important distinction between technical execution and organizational adoption. A technically successful change can still fail if people do not understand what is changing, why it is changing, or what is expected of them. Conversely, strong organizational engagement cannot compensate for poorly controlled implementation. Successful change requires both.
Like-for-like does not mean resisting improvement or innovation. It means sequencing improvement intelligently. First establish a reliable new baseline; then, once the organization has confidence in that baseline, introduce enhancements as separate and manageable changes.
This approach provides organizations with a practical balance between stability and agility. It reduces unnecessary complexity, makes problems easier to isolate, enables faster recovery, and allows governance to be proportional to risk. Most importantly, it gives people a clear understanding of the from and to states—what is changing, what is staying the same, and why.
In a world where organizations are constantly changing, the ability to control change is just as important as the ability to create it. Like-for-like provides a simple, repeatable framework for doing both.