Why good leaders don't always build great teams (4 of 5 in series)

In the previous post, I described the three combinations in the 2/3 pattern. Leadership + Team looked like the least troublesome one. Surely a good leader should help a good team become better.

I've since become less sure. Strong direction can make a group look aligned while quietly teaching everybody to wait. Autonomy can make people feel ownership while leaving nobody responsible for the whole.

I needed a few teams to see the tension properly.

The holiday test

A product leader I worked with made nearly every important decision. They set a clear direction, prioritized ruthlessly, and the team executed it well. The product succeeded, features arrived on time, and quality stayed high.

Then the leader planned a two-week holiday. Before leaving, they narrowed a critical feature decision to two approaches and asked the team to choose between them.

The meeting went quiet.

"What do you think?" the leader asked.

"We're not sure," somebody eventually said. "What would you choose?"

Nothing had suddenly gone wrong with the team. They were doing exactly what the previous system had trained them to do. Good judgment meant understanding the leader's judgment and executing it accurately. The team's success had hidden how dependent it was on one person.

Stepping back for two weeks couldn't suddenly create a decision-making muscle the team hadn't been using.

Autonomy can optimize the pieces

I later saw the opposite problem in a marketing team. Their leader was deliberately hands-off, and each person had genuine ownership of a domain.

The social media work was playful, full of silly memes and goofy posts. The brand work presented a serious company for enterprise customers. Customer communication concentrated on sales, with discounts and transactional messages.

Each person could point to good work. The social media engagement was up. The sales messages converted. The brand direction made sense for the market the company wanted.

Together, they told three different stories.

Potential customers saw the playful posts, then received a discount email, while the company tried to build a professional reputation. Initial engagement was good, but retention was low. Everybody had optimized a part of the journey and nobody owned the experience across it.

When leadership eventually introduced a central direction for brand positioning and customer relationships, the team resisted. "We've been doing fine on our own," somebody said. People had evidence in their own metrics, and intervention now felt like an attempt to take away autonomy they had been promised.

The leader had waited so long to provide direction that providing it had become a breach of the team's expectations.

Moving the boundary has a cost

An engineering manager I worked with tried to draw a more careful line. He set the strategic direction and left implementation decisions to the engineers.

The group needed to break apart an overgrown monolith. Poor coding practices had accumulated, production problems were creating urgency, and the manager chose a move toward services. Each team could decide how to split its services and design the abstractions.

The autonomy ran ahead of the team's experience. Logic was duplicated, abstractions leaked implementation details, and dependencies began to defeat the reason for splitting the monolith. There wasn't enough time to teach service architecture while also racing the production problems.

The manager intervened. He defined service boundaries, standardized interfaces, and overruled several architectural decisions.

"You said we could decide how to split our services," one engineer told him. "Why did you give us autonomy if you were going to override us?"

On the next decisions, he held back. Inconsistent abstractions and unclear boundaries spread. He moved between centralization and delegation, with each correction weakening the other side. More direction damaged the promise of autonomy. More autonomy diluted the architecture.

I've seen this described as a failure to set clear boundaries, and sometimes that is all it is. But even a well-drawn boundary moves as the work reveals new risks. Teams remember who owned yesterday's decision when a leader needs to reclaim it today.

Direction shapes what a team learns

These examples changed how I think about strong leadership. A leader doesn't only make today's decision. They also decide, through repetition, whose judgment the group will practice.

Centralizing a call may be entirely reasonable when time is short or the consequences are large. Repeating that choice makes the group faster at following and weaker at deciding without you. Distributing every call builds ownership, but it can leave cross-team coherence unattended. Neither effect appears on the day of the decision.

This is why the Leadership + Team combination can be deceptive. Alignment, pace, and a lack of visible conflict may show that a group is healthy. They may also show that everybody has learned where the answer comes from.

I don't think the answer is a permanent point halfway between control and autonomy. The useful question is more immediate: which decisions should this team be learning to make now, and what support would let them practice without betting the company?

That question leads into the final post in the original series: if every choice strengthens one part of the system, can an organization keep all three pillars strong at once?