Part of the Pressure Intelligence™ framework
guide
Member
Member
Member

What Before How

A field guide for a leader whose strategy is not reaching the people doing the work: share what it is for before anyone hands down how to do it.

What Before How
89
what-before-how

Why strategy arrives lower down as a list of instructions, and how to hand down a clear picture of what the work is for before anyone hands down how to do it.

Where we are headed

The challenge: Strategy isn’t reaching the people doing the work

Strategy loses something each time it is handed down a level. Each layer reasonably turns its goal into tasks for the next, and a few layers down people receive a how without a what: they can carry out the plan but can’t adapt it once it stops fitting. Adding more detail makes following easier and steering harder. What follows shows how to hand down the result the work is for, say what to protect when something has to give, and leave more of the how to the people doing it.

Who it’s for: Leaders who hand work down: a function head, a director, a manager with layers below them who turn a goal into tasks for the next. 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

The strategy is presented at the all-hands: win back the mid-size customers the company has been losing. The slides are clear, and the room seems to follow. A month later, a support team lead three levels down is running a plan: new ticket categories, a faster first-response target and a weekly report, all done well. Then a mid-size customer asks for help with something the plan doesn’t cover. It would take an afternoon of one engineer’s time. She says no, because it isn’t in the plan and she has no way to know whether it should be. Her team hits its targets that quarter. The customer leaves anyway. Asked about it later, she says, reasonably, that she did exactly what was asked. She did. What she wasn’t given was what it was all for.

Where it lands

  • In you: you tend to hand down plans, milestones and targets, and you find you are the only one who can tell whether a change to the plan still serves the goal.
  • In your team: people often do what was asked and do it well, and anything the instructions don’t cover comes back to you as a question.
  • In your organization: targets typically get hit while the result they were meant to produce doesn’t move, and each layer adds detail to the plan while the purpose behind it gets thinner.

Questions to ponder

Think of a piece of work our team is doing now that is tied to the strategy, and ask:

  • Could the people doing it say what result it is meant to produce, in their own words?
  • When the strategy reached us, did it arrive as a result to achieve or as a set of initiatives and tasks?
  • How much of the plan handed down to us was fixed, and how much would we have been free to change?
  • When the plan last stopped fitting, did we tend to adapt it, follow it anyway, or bring it back to the leader?
  • If someone changed the plan to protect the result, what happened to them?

Questions to discuss

With the two sentences from Try this week on the table, what will be different when the work is done and what matters most if the plan stops fitting:

  • What result is our work meant to produce, in our own words? The gaps in the answers are the gaps in what has reached the team.
  • Which parts of how we work are fixed for a real reason, and which did we just inherit? Teams often carry steps that outlived the goal they were written for.
  • How could we change the way we hand work to each other so that each of us helps the next person hold the what, and the how stays with the people doing the work? Name one piece of work each of you will hand down this month as a result rather than a set of steps, and what you will ask back.

Try this week

Pick one piece of work you are about to hand down. Before you share the plan, write two sentences: what will be different when this is done, and what matters most if the plan stops fitting. Say those two sentences first, in the meeting or the message. Then, instead of giving the steps, ask the person taking it on how they would go about it, and listen before you add anything. Notice where they find a better route than yours.

Keep reading with a free account

  • Where the what gets lost: thinned out on its way down, not stated as a result, or known and still not trusted to steer the how
  • How to mark the parts of a plan that have to stay fixed, and hand down the result in place of the rest
  • The two-sentence what, and the check a week later with someone two layers below you
  • A late-night phone call, a piece of software required by December, and what passing an instruction on without asking its purpose cost the team
  • 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.