Part of the Pressure Intelligence™ framework
guide
Member
Member
Member

One Team

A field guide for a leadership team not working as one: why capable leaders can agree in the meeting and pull apart afterward, and where to start.

One Team
94
one-team

Why a group of capable leaders can agree in the room and still pull apart afterward, and how to start working as one team.

Between people and teams

The challenge: Leaders pull in separate directions

Most leadership teams are made of people promoted for running strong functions, and it is natural for each of them to look after what they are responsible for. The split that follows is rarely about goodwill. More often the team holds two pictures of the same plan, and the people two layers down feel it first. What follows helps a leadership team sort its priorities together, name the tradeoffs and costs each decision implies, and work through its differences as one team.

Who it’s for: Senior leaders who lead a team of leaders: a chief executive, a general manager, the head of a function or a region. 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 leadership meeting goes well. The team works through a hard tradeoff between two launches, lands on a decision, and people nod. By Thursday the decision is being carried out three different ways. Sales has told its biggest accounts the first launch is safe. Engineering has moved two people to the second. Finance is still modeling both. The leaders weren’t being difficult. Each leader took the decision back to a function with its own targets and its own pressures, and translated it into something that function could act on. Two levels down, a manager who works with all three functions gets three sets of instructions that don’t fit together, and asks her own manager which one is real. He isn’t sure either.

Where it lands

  • In you: decisions you thought were settled tend to come back to you in a new form, and more of your week goes to reconciling your own leaders than to running the business.
  • In your team of leaders: each function often hits its numbers while the company misses, and two leaders can use the same words for a priority and mean different things by them.
  • In your organization: people two and three layers down typically feel the split first, because they are the ones trying to make instructions from different leaders fit, and they learn to wait for the version that sticks.

Questions to ponder

Think of the last decision our leadership team made that didn’t hold, and ask:

  • If someone had asked each of us the day after, would we have described the decision the same way?
  • Did it come apart over what we were solving, over the solution we chose, or over the details of carrying it out?
  • When two of us disagree, do we tend to work it out with each other, or is it escalated to the overall leader, or perhaps avoided?
  • Which do we tend to talk about more: how our own function is doing, or how the company is doing?
  • Could each of us say what the tradeoffs were, and what was put on hold or sacrificed because of the decision?

Questions to discuss

With the priority lists side by side on the table, without names:

  • Where did our lists differ, and what does each of us think the difference means? Let each leader explain their list before anyone argues for theirs.
  • Which of our last few decisions did we each carry out differently, and why? Look for the decision that was agreed without its tradeoffs named.
  • How could we change the way we work together so that each of us helps another function land its priority, and this team becomes the first team for each of us? Name one thing each of you could do for a peer’s priority this quarter, and what you would need from them in return.

Try this week

Before your next leadership meeting, ask each member to write down what they believe the team’s top priorities are, privately and in their own words. Collect the answers and put them side by side without names. Where they differ is what the meeting is for.

Keep reading with a free account

  • Three readings of the same break: leaders who describe one decision differently, leaders who protect their own function first, or a team that settles its differences through you
  • The sentence to close each significant decision with, and the test of whether each leader could say it to their own team without changing a word
  • How to send a disagreement between two leaders back to the pair, with a date for a joint answer
  • Three questions to put to your leadership 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.