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.

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.
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 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.
Think of the last decision our leadership team made that didn’t hold, and ask:
With the priority lists side by side on the table, without names:
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.
Free, no card.
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.