Skip to main content
    Leadership

    Most Leadership Teams Aren't Teams. Here's How to Build One That Is.

    What high-performing leadership teams in complex organisations do differently, and why it starts before the first meeting.

    Daniel MartiDaniel Marti·7 min read
    Most Leadership Teams Aren't Teams. Here's How to Build One That Is. – Leadership and transformation
    In short: A leadership team doesn't become high-performing at an offsite. It becomes high-performing through work that only this team can do together, clear boundaries and the right people at the table. Research by Richard Hackman and Ruth Wageman suggests that around 60 percent of a team's effectiveness is decided by its design, before it ever meets. That's the part most leadership teams skip.

    Monday, 8:30. Leadership team meeting. Item one: finance. Item two: sales. Item three: operations. Item four: HR. Everyone listens politely, asks one question to show they were paying attention, and waits for their own slot. Two hours later, eight people leave the room with exactly the priorities they walked in with.

    That's not a team. It's a reporting line with chairs.

    Most writing about teams and leadership is about how leaders lead their teams. This piece is about the team the leaders are supposed to form themselves. It's the hardest one to build. And it decides whether anything else changes.

    The team that isn't one

    Jon Katzenbach made the point in Harvard Business Review back in 1997: most top management groups aren't teams at all. They are working groups. Capable individuals who coordinate, share information and then return to run their own areas.

    There's nothing wrong with that. For coordination, a working group is efficient. It becomes a problem when the organisation needs something only a team can deliver: a strategy that cuts across silos. A transformation that asks every function to give something up. A decision that is right for the whole and painful for one part.

    That's where many leadership teams stand today. Complexity has grown. The agenda hasn't.

    Why the leadership team is the hardest team to build

    Three reasons.

    Everyone at the table has a second team. Their people, their budget, their numbers. Patrick Lencioni's answer is the "first team" principle: a leadership team member's first loyalty belongs to the leadership team, not to the function they run. In practice it's usually the other way round, and for a good reason. That's how most of them are measured.

    Nobody chose this team. The org chart did. Run a function and you're in; everyone else is out. Ruth Wageman and her colleagues studied more than 120 senior leadership teams around the world. The first question they put to every leadership team: does this work genuinely need a team, or is this a team in search of work?

    Complexity. In a complicated problem, the right expert finds the answer. In a complex one (a market tipping over, a culture that needs to move, AI reshuffling how work gets done) nobody holds the answer alone. Aaron Dignan makes this distinction central to Brave New Work: organisations built for the complicated fail at the complex. A leadership team made of eight functional experts is built for the complicated.

    60-30-10: where leadership team performance is decided

    Richard Hackman spent decades studying teams, from airline cockpit crews to symphony orchestras to intelligence analysts. His most useful finding for leadership teams is sobering. Around 60 percent of the difference in how well teams perform comes down to their design: what's settled before the team first meets. Roughly 30 percent depends on how the team is launched. Only about 10 percent comes from coaching once the work is underway.

    Read that again as a leadership team. The offsite, the personality test, the ropes course: all of it sits in the last ten percent. The first sixty is unglamorous, structural work that few leadership teams ever do explicitly:

    • Is it a real team with clear boundaries: who's in, who isn't, and why?
    • Does it have a compelling direction, meaning work that only this team can do together?
    • Are the right people at the table, and are they there for the team's purpose or for their title?
    • Does it have enough structure: a workable size, clear norms for how it decides, and meetings where team work happens instead of status work?

    Hackman and Wageman add two enabling conditions: a supportive organisational context and competent coaching. Six conditions in all. Not one of them is a mood.

    The rope team test

    In the Alps there's a word for what a leadership team should be: the Seilschaft, the rope team. Everyone on the rope shares the same fate. If one falls, all of them feel it. Nobody on a rope team optimises their own pace. The route, who leads each pitch and the point at which you turn back are agreed before you're on the ridge. Not once you're already hanging from the rope.

    That's the test we use with leadership teams: are we a rope team, or a queue at the same ski lift? The queue is heading for the same summit, but everyone rides up alone. The rope team carries the consequences together.

    Most leadership teams are a queue. They're heading in roughly the same direction, and that feels like alignment. It isn't. Alignment is when a decision costs one of you something and you make it anyway. Together.

    What high-performing leadership teams do differently

    They separate team work from reporting. Status updates move to a written format. Meeting time belongs to the few questions that need the whole team.

    They name their "only us" agenda. Three to five topics a year that no member can solve alone. Everything else is delegated or handled one-to-one.

    They make trade-offs visible. When the team decides, it's explicit who pays the price. And the team carries that price together instead of leaving it with one function.

    They disagree in the room, not in the corridor. Amy Edmondson's research on psychological safety applies at the top as much as anywhere. If the real disagreement happens in the corridor after the meeting, the meeting decided nothing.

    They're measured as a team. As long as every member's bonus depends only on their own area, you're paying for a working group. Don't be surprised when you get one.

    Where to start: the one-hour audit

    You don't need a programme to start. Take your last three leadership team agendas and sort every item into one of three buckets: information. A decision one person could have made alone. A question that genuinely needed the whole team.

    If the third bucket takes up less than a third of the time, you have your answer. Then put a single question to the team and give it the full hour: which three decisions this year can only this team make together?

    The answer is your leadership team's purpose. Everything else is administration.

    One last question

    If your leadership team disappeared for three months, would the organisation miss a team? Or eight managers?

    FAQ

    Frequently Asked Questions

    Sources

    • J. Richard Hackman: Collaborative Intelligence. Using Teams to Solve Hard Problems (2011)
    • Ruth Wageman, Debra A. Nunes, James A. Burruss, J. Richard Hackman: Senior Leadership Teams. What It Takes to Make Them Great (2008)
    • Jon R. Katzenbach: "The Myth of the Top Management Team", Harvard Business Review (1997)
    • Patrick Lencioni: The Advantage (2012)
    • Aaron Dignan: Brave New Work (2019)
    • Amy C. Edmondson: The Fearless Organization (2018)