The moment when management becomes the problem

Think of a female civil engineer who spent years studying structures, calculations, projects. Who opened her own firm, won clients, built a team. And who now spends a good part of her day resolving conflicts between employees, dealing with miscommunication, trying to understand why the team doesn't execute what was planned.

Or a male doctor who set up a clinic. A female developer who founded a startup. A male lawyer running an expanding firm. A female architect who became a partner and suddenly needs to manage ten people.

The profile changes. The situation, more often than not, is the same: a highly qualified person in their field, losing time and energy on a problem they were never trained for.

Why this happens to people who are very good at what they do

When the company is small, everything runs on proximity. The founder knows everyone by name, knows what each person is working on, resolves problems in the hallway. Management happens almost intuitively — and it works.

But when the team starts to grow, that logic stops scaling. Hallway conversations don't reach everyone anymore. Expectations that used to be implicit need to be stated clearly. Conflicts that used to resolve themselves start to accumulate. And the founder, who never needed to think about this systematically, finds themselves in the middle of a problem they don't quite know how to handle.

The most common response is to try harder: more meetings, more one-on-ones, more hours dedicated to the team. The issue is that effort, here, doesn't replace method. And the more time the founder dedicates to this, the less time is left for what the business actually needs from them.

The invisible cost of insisting alone

What strikes me most in these situations goes beyond the conflict itself. What's left behind while the founder is buried in it: the proposal that wasn't closed, the strategic decision that got pushed back, the product that didn't evolve because all the focus was on internal management.

There's a human cost too. The person who spends months trying to solve something outside their zone of competence arrives exhausted, frustrated, and often starts questioning their own ability. Usually, the issue lies elsewhere: in the absence of someone with the right expertise for that function.

What changes when there's specialist support

A female engineer hires a female accountant to handle finances. A male doctor hires a female lawyer for contracts. Nobody questions that — it's obvious that every area requires specific knowledge.

People management works the same way. Understanding how to structure roles and expectations, how to build a culture that sustains growth, how to prepare leaders for the next level — all of this has method, has tools, has a way of being learned and applied.

When the founder or co-founder stops trying to solve this alone and starts working with someone who has that expertise, a few things tend to happen relatively quickly: conflicts that seemed chronic start finding a path forward. The team gains more clarity about what's expected of each person. And the founder recovers the time and energy to do what they came here to do.

There's no single moment when management becomes the problem. It might be when the team reaches ten people. It might be after a costly bad hire. It might be when growth accelerates and the culture that used to work starts to crack.

But there's a signal that appears in almost every case: the founder or co-founder is dedicating time and energy to a problem that's outside their area of expertise — and the business is paying the price for it.

If that resonates, this might be that moment.