Confident Is Not the Same as Capable

Sep 10

Every morning, the team waits.

Not for a plan — there isn't one yet. For direction. The leader arrives, reads the room, and announces what needs to happen today. The team picks up their tools and starts moving.

An hour later, something comes up. A client request, a sudden priority, something the leader just remembered. The team is told to stop what they're doing and switch. So they switch. The thing they were working on sits unfinished, losing momentum, waiting for a tomorrow that will look exactly like today.

By end of week, the list of half-finished work is longer than the list of completed work. The founder looks at the numbers and wonders why the team isn't more productive. The team looks at each other and says nothing.

This is not a productivity problem. It's what happens when the person in charge is only equipped to react.

How it happened

At some point, someone needed to step up. And someone did.

They were confident. They spoke clearly and directly. They didn't hesitate when asked a question — they had an answer, immediately, delivered with enough certainty that it felt like leadership. They could command a room. They could tell people what to do and be taken seriously doing it.

So they got the role.

The logic was reasonable. In a room full of people, they looked most like a leader. What they were actually good at — giving direction in the moment, responding to whatever was most urgent, projecting confidence under pressure — is genuinely useful. In a crisis, you want that person.

But running a team isn't a permanent crisis. It's a steady ship that occasionally hits rough water. And the skills that look like leadership in an emergency are not the same skills that keep a team moving efficiently week after week.

No one saw the distinction until it was too late.

What the good employees noticed

There's a certain kind of employee who sees these things clearly. They don't always have the title — project manager, operations lead, head of anything. But they have the instinct. They can look at a week's worth of work and see what should happen first, what can run simultaneously, what's blocking something else downstream.

They tried to say something. Quietly at first — a suggestion here, a different approach offered there. What if we planned the week on Monday instead of deciding each morning? What if we finished this before starting that?

Sometimes it was heard. Sometimes it wasn't. Either way, it didn't stick. The next week looked like the last one. The priorities shifted again. The half-finished work accumulated again.

After a while, they stopped suggesting. Not because they stopped caring — because they understood something the founder hadn't yet: if the person at the top doesn't see the need to change, nothing below them will hold. Their effort wasn't going to fix a structural problem. And working hard inside a broken structure isn't noble. It's exhausting.

So they updated their resume. They found somewhere their judgment would be used. And they left.

What the founder saw

Turnover. Again.

The response was familiar — more team activities, better perks, an offsite, a pizza party. Make people feel valued. Build culture. Improve the hiring process so the next round brings in people who are more committed, more grateful, more willing to stick it out.

None of it touched the actual problem.

Because the actual problem wasn't that people didn't feel appreciated. It was that the people worth keeping could see clearly that nothing was going to change — and they made a rational decision based on accurate information.

The ones who stayed were not necessarily more loyal. Some of them had simply stopped noticing. Or stopped caring. Or had nowhere better to go.

The team that remained was the one the situation had selected for. And the founder was now trying to build something with it.

The signal that misleads

Founders promote for what they can see.

Confidence is visible. Volume is visible. The ability to command a room, to project certainty, to move people with presence — these are visible. They feel like leadership because they look like leadership.

What actually makes a team function is almost entirely invisible until it's absent. The ability to hold the whole picture and sequence work intelligently. To know what's fixed and what's fluid. To finish things before starting new ones. To plan a week instead of reacting to a day. To hear a suggestion from someone junior and recognize it as correct.

These qualities don't announce themselves. The people who have them often don't perform confidence — they just do the work, quietly and well, and assume at some point it will be noticed.

It often isn't. Not before they leave.

Confident is not the same as capable. The distinction seems obvious in hindsight. In the room, in the moment, when someone needs to step up — it's surprisingly easy to miss.

What actually needed to happen

The founder needed to look past the surface signal.

Not at who seemed most like a leader — but at who actually understood the work well enough to sequence it. Who could see a month ahead instead of a morning ahead. Who, when something urgent surfaced, could hold it against everything else and decide — with judgment, not just instinct — whether it actually needed to happen right now.

That person was probably already in the building. Quietly doing their job. Occasionally suggesting a better way. Waiting to see if anyone was paying attention.

They may still be there. Or they may have already left.

Either way, the question worth sitting with isn't how to retain more people. It's who has been making the real decisions about how work gets done — and whether that was ever actually the right person for that role.

That's usually where the answer is.

If this resonated

This is the kind of pattern I write about in Undercurrents — not tactics or frameworks, but the underlying dynamics that have been quietly running things before anyone thought to look there.

It goes out when something is worth saying. No noise in between.

Join Undercurrents