How to Build a Team That
Doesn't Need You to Function
The best managed team you will ever encounter has a distinctive quality: it continues to function brilliantly even when the manager is on holiday, in back-to-back meetings, or — and this is the real test — gone entirely. That is not an accident. It is the deliberate result of how the team was built.
We have spent two posts cataloguing what goes wrong — the meetings that eat calendars, the habits that hollow out teams. This final piece is about what goes right. Specifically, what the managers who build genuinely high-performing cultures actually do, and how it differs from what most people think management is for.
The short version: good management is mostly invisible. It is the work of making conditions — for clarity, for trust, for useful friction, for growth — and then getting out of the way. That sounds easy. It is, in practice, one of the harder things a person can be asked to do. Because getting out of the way requires resisting the very impulse that got most people into management in the first place: the deep, well-intentioned desire to be useful.
The five conditions high-performing teams share
Google's Project Aristotle — a years-long internal study of what separates great teams from average ones — found that who is on a team matters less than how the team operates. The conditions mattered more than the credentials. Here are the five that show up consistently, with what building them actually looks like in practice.
What a healthy team looks like in practice
Culture is slippery because it's invisible until it isn't. You don't see it running well. You see the absence of things: the absence of defensive silence in meetings, the absence of political manoeuvring around decisions, the absence of people waiting to be told what to do next. Healthy teams are characterised by what doesn't happen as much as what does.
Here are the contrasting signals — the things that tell you, honestly, which kind of team you have right now.
- People disagree in the room, not in the corridor after
- Mistakes surface quickly and get fixed without drama
- People make decisions within their remit without asking permission
- The team functions fine when the manager is away
- New people get up to speed quickly because norms are clear
- Everyone agrees in meetings, then nothing changes
- Problems surface late, fully formed, and already expensive
- Small decisions escalate upward for approval
- Output dips noticeably when the manager is absent
- Onboarding is mostly informal and inconsistently delivered
The uncomfortable final point
Everything in this series — the meetings, the habits, the culture — comes down to a single question that most managers never ask themselves directly: what am I actually here to do?
The answer that high performers tend to land on, usually after a few years of getting it wrong, is something like this: to create the conditions in which smart people can do their best work, and to get out of the way once those conditions exist. Not to be the smartest in the room. Not to be the one with all the answers. Not even to be particularly visible — because the quietest, most invisible kind of management is often the best kind.
The meeting that runs itself. The decision that gets made well without you. The team member who grows beyond needing your guidance. These are not signs that you are becoming redundant. They are, if you will forgive the slightly earnest note on which to close a series that started with a rant about meetings, the whole point.