Part of the Pressure Intelligence™ framework
guide
Member
Member
Member

Where There's a Will, There's a Why

A field guide for a leader whose decisions keep coming back, often because people can't see where things are headed or why, and how to give them a reason.

Where There's a Will, There's a Why
88
where-theres-a-will-theres-a-why

Why decisions stall or keep coming back when people can't see where the organization is headed or why, and how to give a direction a reason clear enough to decide with.

Where we are headed

The challenge: The direction isn’t clear enough to act on

A direction can win agreement in the meeting and still fail the first time someone has to choose between two good options. Many name a destination and leave out the why: what it solves, what it costs, and what would show it is working. Without that, tradeoffs travel up for a ruling or get settled by whoever pushes hardest, and decisions reopen when the pressure shifts. The guide helps you attach the reasons to a direction, so more decisions can be made where the work is.

Who it’s for: Senior leaders who set a direction, and the leaders who have to decide inside it: a chief executive, a function head, a director whose decisions keep traveling up. 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

A leadership offsite ends with a new direction: become the platform our customers build on. The room agrees. A few weeks later a product lead has to choose between two good options. The largest customer wants a feature by the end of the quarter, and the integration work the direction seems to ask for needs the same engineers. She isn’t sure which one the direction means, so she asks her director, who isn’t sure either and puts it on the leadership agenda. It is decided two weeks later. A month after that a different customer escalates, and the question is open again. Her team has started both pieces of work and finished neither. The leadership team would say the direction is clear, and about the words they would be right. What the room didn’t test was whether the words could settle a real tradeoff.

Where it lands

  • In you: you tend to be deciding things that should be decided two levels below you, because the people there can’t tell what the direction allows.
  • In your team: decisions often wait for a ruling, or get made and then reopened when a louder request arrives, and people start several options at once to stay safe.
  • In your organization: each function typically understands the direction its own way, and priorities end up set by whoever pushes hardest or asks most often.

Questions to ponder

Think of the last decision that stalled or came back, and ask:

  • What part of the direction was that decision supposed to rest on?
  • If two of us stated the direction, would we say the same thing, and would it point to the same option?
  • Can we say what the direction means we will stop doing, or do less of?
  • When a decision gets made, does anyone tend to say which reason decided it?
  • Why did the decision have to go up to be made, instead of being made where the work is?

Questions to discuss

With each person’s written answer from Try this week on the table, which option the direction points to and why:

  • Which decision are we waiting on right now, and what would we need to know to make it ourselves? The answer is usually a missing reason, a missing cost, or both.
  • What are we giving up to follow this direction, and do we agree on that? Disagreement here is useful. It shows where people have been understanding the direction differently in good faith. Ask, too, what would tell us the direction is wrong; a team that knows what would justify reopening a decision can hold it through a hard week.
  • How could we change the way we decide together so that each of us helps the others use the why, and more decisions get made where the work is? Name one decision each of you will make this month with the direction’s reason attached, and say it where the others can hear.

Try this week

Bring one open tradeoff your team faces, two good options competing for the same people, to your next team meeting. Ask each person to write down which option the direction points to, and why, before anyone speaks. Then compare. Where the answers match, the direction is doing its job. Where they split, you have found the missing part of the why. Don’t settle it in the meeting. Take it, with the answers, to whoever owns the direction.

Keep reading with a free account

  • How to tell competing directions from a missing why, and a missing why from a team that hasn’t yet seen the why put to use
  • How to list each direction your team is actually responding to, including the ones nobody announced, and put them in order
  • The three questions a direction has to answer before it can rank options
  • How to say, as you decide, which part of the why decided it, so people start reasoning the same way before a decision reaches you
  • 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.