Making Change Stick
Last Updated: 2026-08-20
Why Fixes Get Absorbed and How to Make Them Hold
You raise the budget, add the headcount, tighten the process, and the number moves. Then it drifts back. This is compensating feedback: the pattern where a system absorbs a fix and restores its old state, usually after a delay. The harder you push a lever the system is built to hold, the more effort, budget, and credibility drain away.
Most executives respond by escalating: more resources, more pressure, one more push. When resistance rises in step with the effort, that matched pushback is the signal to stop and diagnose, not to force it again.
5 Core Skills for Making Change Stick
1. Recognize Compensating Feedback Before Escalating Effort
Escalating effort into a problem built to absorb it wastes budget and credibility. Read the signature early: gains that erode, results that plateau despite more input, and resistance that rises in step with effort. Rule out simpler explanations first, and judge results on a timescale long enough to show whether a win is real.
Explore skill →2. Map the Balancing Loop That Defends the Status Quo
A system that keeps returning to the same state is defending something. Name the specific level it restores, name who adjusts their behavior to restore it, and trace the full cycle from intervention to pushback, including where the delay sits. Confirm the map with the people inside it, then publish it so the next diagnosis starts from more than a blank page.
Explore skill →3. Redesign the Loop Instead of Adding Force
A durable fix changes what the system defends or weakens the response that cancels your effort. Aim the intervention at the defended target or the offsetting response, state why pushing harder would be absorbed, and pressure-test the redesign for the new resistance it might create. Capture a structural fix that holds as a pattern others can reuse.
Explore skill →4. Lead Through the Worse-Before-Better Transition
A real fix often looks worse before it looks better, because removing the quick relief lets the problem surface. Tell people the dip is coming and why, define the signals that show the change is working before it arrives, and hold the change in place while results temporarily worsen. Withdraw the old workaround on a deliberate schedule instead of leaving it to recreate the loop.
Explore skill →5. Build the Organization's Capacity to Catch Compensating Feedback
An organization that spots compensating feedback without one leader in the room keeps the capability for years. Review outcomes on the timescale the loop runs on, keep a record of fixes that did not stick, and give the team the words to flag the pattern themselves. Build the pushback check into how interventions get designed and approved.
Explore skill →Mastering Change That the System Cannot Absorb
Mastery is diagnostic before it is forceful. You read the signature of a fix being absorbed, name the level the system defends and who restores it, and choose a lever that changes the structure rather than adding pressure. You hold the change through the dip a real fix produces, because you set the indicators that tell progress from collapse before you needed them.
- At the highest level the capability outlives you.
- The team has the language to name the pattern, the review rhythms run on the loop's timescale, and the pushback check is built into how interventions get approved.
- Compensating feedback gets caught and corrected without you in the room, and old fixes that quietly decay stop hiding in the budget.
Frequently Asked Questions
What is compensating feedback?
Compensating feedback is the pattern where a system absorbs a change and restores its old state, usually after a delay. Widen a road and new drivers fill it until congestion returns. The system defends a particular level, and behavior somewhere adjusts to cancel the intervention. Recognizing it stops you pouring effort into a problem built to absorb it.
Why do my fixes stop working after a few months?
A fix that improves results and then drifts back is often being compensated: something in the system is adjusting to restore the old level, and the delay is why the change looked like it worked at first. The answer is not more of the same force. Map what the system is defending and who restores it, then aim the next change at that structure.
How do you tell compensating feedback from poor execution?
Read the signature. Compensating feedback shows as gains that erode, results that plateau despite more input, and resistance that rises in step with effort. Rule out simpler explanations first, then judge the result on a timescale long enough for the system's pushback to appear. If more effort keeps meeting matched resistance, the problem is structural, not motivational.
Why do real fixes often make results worse before they get better?
A quick relief, like a manager stepping in to redo the team's work, hides the underlying problem. Remove it and the problem surfaces, so results dip before the durable fix takes hold. Leaders who revert during that dip lose the fix right before it pays off. Set leading indicators in advance to tell a transition on track from one that is genuinely failing.
How do you keep change from being absorbed by the organization?
Make detection a habit rather than one leader's talent. Review outcomes on the loop's timescale, keep a record of fixes that did not stick, give the team language to flag the pattern, and build a pushback check into how interventions get approved. When the organization catches compensating feedback without you in the room, the change holds and the capability lasts.
Unlock Skill Progression
Related Skills
Organizational Culture
Build a culture people can practice, not just repeat: define behaviors, align executives, reinforce systems, lead through change, and measure health.
Change Leadership
Change fails on the people side, not the plan. Lead teams through it with five linked practices: make the case, work resistance, translate, model, sustain.
Execution Operating System
Strategy fails in translation, not conception. Five COO disciplines turn priorities into owned numbers, one cadence, fast decisions, and closed loops.