Part of the Pressure Intelligence™ framework
guide
Member
Member
Member

A Plan That Holds

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.

A Plan That Holds
90
a-plan-that-holds

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.

How it shows up

Part 1 of 3 · Notice the effect. The scene, where it lands, and the questions that often sit with you before you fix anything.

The scene

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.

Where it lands

  • In you: you tend to announce changes more often than you check whether the last one took hold, and in a hard week you reach for the old lever because it is the one your hands know.
  • In your team: people often comply in form and work the old way in substance, and they have learned that waiting a change out is usually the safest response.
  • In your organization: the measures, the reviews and the calendar typically still reward the old way, and new initiatives stack on top of ones that were not finished or retired.

Questions to ponder

Think of the last change that didn’t stick, and ask:

  • When results tightened, what did we praise: the new way or the old one?
  • Is anything we measure, review or schedule different because of the change?
  • When did we last look at whether the plan still fit conditions, and was that look planned or forced by a crisis?
  • How many changes are in flight right now, and which of them have been finished or retired?
  • What did people on the team say, or not say, when the last change was announced?

Questions to discuss

With the measure, the meeting question and the praise from the last tight week on the table:

  • What are we rewarding that we wouldn’t choose on purpose? Incentives are hard to see from inside, but a team can usually name them once it is asked.
  • Where are we treating a problem in the system as someone’s personal failing? The answer often comes from the person who is tired of being blamed for the structure.
  • How could we change the way we carry a change together, so that each of us helps hold the new way through the next hard week, and nobody waits it out alone? Name one routine each of you owns that could carry the change, and what you would need from the others when the week turns hard.

Try this week

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.

Keep reading with a free account

  • How to tell which version you have: the old way still being rewarded, a plan with no way to be revised, or a team that has learned to wait changes out
  • Why a pattern built into the structure, such as what the quarterly review measures, needs a change to that structure and not more encouragement
  • How to set the review date before a change starts, so the steps can be revised while the direction holds
  • The first hard week after a change, and why holding the new way in plain view through it teaches more than the launch did
  • The research behind it, and books to read next
  • The toolkit: questions to ponder, questions to discuss, things to subtract, actions to take
  • The kit, as downloads: the full Field Guide, a Leader’s Guide, and slides for the team conversation
Create a free account

Free, no card.

Open the field guide >>

About the author

Mark D. Benson
Mark D. Benson
Founder of Resonant Vector™
Resonant Vector
Full profile →

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.