A Team Does Not Become a Team by Sitting in the Same Room

The first meeting of a new team is usually pleasant. Everyone agrees with everything, nobody pushes back, and the mood is good.

Two weeks later it turns out that two of them meant different things by “done”. The manager tends to blame their own briefing for that, assuming they were not clear enough. The briefing was rarely the problem. The problem was expecting behaviour from a group assembled last month that only appears much later.

The same road, at different speeds

Teams do not develop at random. They go through broadly the same stages in the same order, just not in the same amount of time. This description is usually attributed to Tuckman, and the reason it has stayed in use is that it promises nothing. It will not tell you how to get a good team, only where yours is standing right now.

That turns out to be enough. Leadership improves the moment you stop doing the same thing in every stage.

At the start, what is missing is direction, not trust

Beginnings are polite. People are careful, they ask few questions, and they would rather nod than open an argument about something they do not yet understand well. That is not laziness. It is caution, because nobody knows the rules yet, or what happens to the first person who disagrees.

The mistake here is usually generosity. A manager grants autonomy early, with the best intentions, but at this point freedom reads as uncertainty. What people need is direction, meaning who does what, what counts as finished, and who to ask when you get stuck. Trust is not built by extending it in advance. It is built by being predictable.

Arguments are not a step backwards

Then comes the stage nobody enjoys. Somebody says in the weekly meeting that this is not going to work. Or worse, does not say it there, but says it in the corridor afterwards, to two people.

This is not the team deteriorating. It is the point where people start taking the work seriously enough to differ about it. A team that never gets here has not achieved peace. It has achieved indifference.

The manager's job is hardest at this stage, because the natural move is to smooth things over. Smoothing over does not end a conflict. It relocates it somewhere you cannot see. What helps is putting the disputed thing back on the table and deciding it. Not everyone has to be right. Everyone has to know they were heard, and what the decision was.

If a team never openly disagrees about anything, that in itself is information.

When habits take shape

Once the storm passes, the team starts running on understandings. Most of them are unwritten, and yet everyone knows who to ask about a particular client, when you are supposed to flag a delay, and which decisions are not made without a conversation.

This stage is comfortable, which is exactly what makes it risky. Managers tend to sit back here, when this is the moment to pay the most attention to what went well and why. Whatever is never said out loud cannot be learned by a newcomer, and when the sixth person arrives, the explaining starts from zero.

The sentence you hear at this point is “that's just how we do it here”. The new colleague nods, then does it differently the following week, because “how we do it” was never written anywhere; it was a habit. The problem is not their willingness to learn. It is that the team's best knowledge lives in four people's heads and only surfaces by accident. Habits are worth writing down while everyone still remembers why they formed. Six months on, nobody knows, and all that survives is that it has always been this way.

When it runs without you

The recognisable sign of a team that works is not how much it delivers. It is that you leave for a week and the work does not stop. People go to each other instead of to you, and most decisions get made without your knowledge.

This is where the manager has to change the most. Someone who has been directing now has to ask. Micromanagement at this stage does not slow the team down. It takes it apart, because it says that what they built is not reliable enough.

The ending everyone skips

A project finishes and the next one starts the following morning. Nobody talks about what worked and what did not, because there is no time, and because it is awkward.

That is where the cheapest learning is. It does not take a long review. It takes the one thing you would do differently next time, and the name of the person without whose work it would not have happened. That half hour decides whether the next team starts from zero.

When none of this is worth your attention

Not every team gets to the end of the road, and not every team needs to.

If three of you work on one task for two weeks, you are not going to build a culture in those two weeks, and it would be a waste to try. If your team has been together for years and they know exactly what each of them can carry, splitting the process into stages will not tell you anything new.

Stages become useful when something changes, when a new person arrives, when the team splits in two, when the work turns into different work, or when a group that has been running smoothly for years suddenly starts stalling. Most people ask what went wrong at that point. Often nothing did. The team stepped back a stage because its composition changed, and it now needs different leadership than it did last month.

What is worth taking from this

Leadership does not get better by staying the same. A new team needs direction, an arguing team needs decisions, a settled team needs its habits said out loud, and a team that works needs room.

Which practices actually help with that, and which ones only cost you the afternoon, is a separate article.

One question is enough to start with. If somebody openly contradicted you at the next meeting, would that be a surprise, or an ordinary Tuesday? The answer tells you which stage you are in.

Open the demo