A field guide for a leader whose changes keep sliding back: why a change goes stale before it sticks, and a plan that stays in the work as things shift.

Why a change can go stale before it sticks, and how to build a plan that keeps finding its way into the work as conditions shift again.
Where we are headed
The challenge: Strategy and the work aren’t connecting
Many changes reach the slides and stop there. When the measures, the weekly meeting and what gets praised still reward the old way, a hard week sends the team back to it, which looks like resistance and is often a correct judgment of the situation. Conditions keep moving too, so a plan built to land once can go stale before it settles. You will find ways to tie a change to the routines the work already runs on, and to plan revisions so the direction holds while the steps adjust.
Who it’s for: Leaders who have asked a team to change how it works: a function head, a general manager, anyone who has announced a change and watched a hard week undo it. Read it on your own first, then take the conversation in part three to your team.
Part 1 of 3 · Notice the effect. The scene, where it lands, and the questions that often sit with you before you fix anything.
In the spring, a company rolls out a new way of planning: smaller bets, reviewed each month against what customers actually do. The rollout is careful, with training, a new template and a launch meeting with good questions. For a few weeks it holds. Then a hard week arrives, with a customer escalation and a number that has to be hit by Friday, and the team does what got it through the last hard week. The template is still filled in. The old conversation is what decides. By summer the leadership team has a new priority to announce, and the planning change stops coming up in meetings. It wasn’t reversed. It just went stale. When the next change is announced, people listen politely and wait to see whether this one will last longer than the last.
Think of the last change that didn’t stick, and ask:
With the measure, the meeting question and the praise from the last tight week on the table:
Pick the change your team agreed to most recently. Look at three things: what the team measures, what its regular meeting asks about, and what got praised the last time results tightened. Find one place where those still reward the old way, and change that one thing this week. Then put a date on the calendar a month out to look at whether the change is showing up in the work, and say out loud that you will.
Free, no card.
Mark D. Benson is the founder and principal writer of Resonant Vector, the home of Pressure Intelligence, and the host of Pressure Rising™. He is a product and systems leader who has spent his career running global teams, complex platforms, and consequential decisions under real constraint.
His career sits where strategy, technology and large human systems meet, in places where high stakes are the norm.
Resonant Vector is his commitment to learning in public and sharing what helps leaders and teams perform under pressure.
More about Mark can be found at markdbenson.com.