Part of the Pressure Intelligence™ framework
guide
Member
Member
Member

Widening the Base

A field guide for a leader who has become the bottleneck: why decisions settle on a few people, and how to spread them so the team keeps moving.

Widening the Base
91
widening-the-base

Why work and decisions settle on a few people, what that does to continuity, and how to spread them so more of the organization can carry the work.

How things get done

The challenge: Too much depends on one person

Under pressure, work and decisions flow toward whoever handles them well, so the people who handle them well end up with more of them. On the org chart the work looks evenly shared, while two or three people hold most of what matters, and a resignation, an illness or a leave would stop something important. Working faster leaves the concentration where it is. The guide helps you map who holds what, spread skills and decision rights on purpose, and build a base wide enough to keep working the week someone is out.

Who it’s for: Leaders whose team runs through a few people, including themselves: a manager, a function head, anyone whose queue refills however fast they clear 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

It is late on a Wednesday, and the queue that was cleared on Monday is full again. A pricing exception, a hiring decision, a question about a customer commitment, a draft that needs one more look. Each one is reasonable to bring to you, and each one is faster for you to settle than to explain, so you settle it. Down the hall, the same thing is happening to someone else. One engineer knows how the billing system really works, one account manager holds the history with your largest customer, and both of them have a vacation on the calendar next month. It wasn’t planned this way. The work went to the people who handled it well, and kept going to them. By Friday the queue has refilled, and the question you have been putting off is still there: what happens to this work the week one of you isn’t here?

Where it lands

  • In you: decisions tend to wait for you, the queue refills however fast you clear it, and your own time off takes a plan to cover.
  • In your team: people often wait instead of deciding, a few names appear on each escalation, and “only she knows how” is said as a fact rather than a warning.
  • In your organization: a resignation, an illness or a leave would typically stop something important, and the organization moves at the pace of a handful of calendars.

Questions to ponder

Think of the week it would hurt most for one of our key people to be out, and ask:

  • How many of the lines that matter have the leader’s name on them?
  • Of the decisions that reached the leader last week, how many came because only they were allowed to make them, and how many out of habit?
  • Where someone else holds a line alone, is the gap a skill, knowledge that isn’t written down, or permission?
  • Who on the team already tends to hold decisions at the edges without the title?
  • What happened the last time someone decided something the leader would have decided, and did it differently?

Questions to discuss

With the one-page map on the table:

  • Where do we wait instead of deciding? The waiting is usually where a decision right has settled on one name.
  • What would you decide if you knew I would back it? The answers show which decision rights people believe they should have, and which you have been holding on to without meaning to.
  • How could we change the way we work together so that each of us helps someone else hold a line, and the team keeps working the week any one of us is out? Name one line each of you could share this month, who you would share it with, and what the rest of the team would need to do for that to be safe.

Try this week

This week, write a one-page map. List what only one person on your team can do, which decisions wait on a single name, and which system or customer relationship has one keyholder. Put yourself on it. Don’t fix anything yet. Concentration builds up without anyone deciding it should, so few people have ever looked at all of it at once, and the map often surprises the person who draws it. Then pick the one line that would hurt most if that person were out next week.

Keep reading with a free account

  • The one-week escalation log, and the three kinds of decision it sorts into, each with its own fix
  • Decision rights as something you can tune, and the people who can hold a line for you
  • How to train a second hand on a critical line, and the week-long test that shows whether it took
  • Why the save gets the applause and the cross-training gets questioned, and what to celebrate instead
  • 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.