Hiring your first manager: what actually changes

The most common way this hire goes wrong is filling it with the best practitioner available, on the reasonable-sounding theory that the person who does the work best should lead the people doing it. Sometimes that person is also a good manager. The two skills are not related, and assuming they are costs a business its best practitioner and gives it a reluctant supervisor.

The job is different in kind, not degree. A manager makes decisions when the answer is unclear and owns the outcome afterwards. They handle conflict — between two people, between a customer and the team, between what was promised and what is possible — which is the part most new managers find hardest and the part most owners forget to assess for. They allocate work, which means saying no. And they develop people, which is slow, unglamorous and invisible for months.

None of that shows up in a track record of doing the work well. A strong practitioner promoted into it usually keeps doing the work, because that is what they are good at and what feels productive, and the management happens in the gaps. The team then has a very busy senior colleague and no manager.

The hire only works if something is actually given up, and the specific thing is the direct line between the owner and the people doing the work. That line is what made the business fast at five people, and it is what makes a manager impossible at fifteen.

Concretely: stop assigning work directly to people who now report to someone else. Stop answering the question that should have gone to their manager, even when the person asks you and you know the answer immediately and it would take four seconds. Stop reversing their decisions in front of the team.

Each of these is individually harmless and collectively fatal. A team learns very quickly where decisions actually get made, and if the owner is still the real answer, they will route around the manager efficiently and politely. The manager is then accountable for outcomes produced by instructions they did not give, which is the same broken arrangement as responsibility without authority, applied to the one hire whose entire job is authority.

The hardest version of this is the good idea. You will see something that should be done differently, and going directly to the person is faster than raising it with their manager. It is faster every single time, and it is how the role gets hollowed out.

Letting go of the direct line is not the same as disengaging, and overcorrecting is its own failure — an owner who announces they are staying out of it entirely leaves a new manager without context, without cover and without a way to check their judgement.

Stay involved in the outcomes and the standard. You should know what the team is expected to deliver, whether it is delivering, and whether the quality is what the business needs. That is a conversation with the manager, on a known cadence, looking at results.

Stay involved in the decisions that were always yours — pricing, hiring, letting someone go, anything that commits the business. A first manager should not be discovering the boundary of their authority by crossing it, which means the boundary has to be written down and specific.

And stay involved in the manager themselves, heavily, for the first few months. This is the part most owners underinvest in: they hire a manager to reduce their own load and then leave that person to work out the business's unwritten rules alone. Regular one-to-ones where the manager can ask questions they would not ask in front of the team is the cheapest thing available here.

Since the job is decisions, conflict, allocation and development, those are what to assess, and interviews are poor at all four unless the questions are specific.

Ask for the last time they told someone their work was not good enough, and what they said. Ask about a decision they made with insufficient information and how it turned out. Ask what they did when two people on their team could not work together. Ask who they have developed and where those people are now.

The useful signal is specificity. Someone who has genuinely done this remembers the awkward conversation in detail, including their own part in it going badly. Someone describing management as a concept answers in principles — 'I believe in open communication' — because there is no incident to describe.

One more thing worth testing for in a first-manager hire specifically: comfort with an unfinished environment. Your business does not yet have the systems a manager from a larger organisation will expect. Someone who has only managed inside working structures may be very capable and still stall when they discover there is no process to enforce, no handbook to point at and no HR function to call.

The first management hire is harder than the second and third for reasons that have nothing to do with the candidate.

There is no example to point at. Every subsequent manager can see how the role works here; the first one has to invent it, in a business whose norms exist only as habits nobody has written down. They will get some of it wrong, and it will look like poor performance when it is often missing information.

The team has never had a layer before. People who have always gone straight to the owner now have someone in between, and some will experience that as a demotion in access regardless of how it is framed. Expect a period where the manager's legitimacy is genuinely uncertain, and understand that it is settled almost entirely by the owner's behaviour rather than by any announcement.

And the owner is changing role at the same time. You are learning to work through someone while they are learning to manage, which means two people are new to their jobs simultaneously and each one's mistakes look like evidence about the other. This is worth knowing in advance, because the natural reading of the first difficult month — the hire was wrong — is usually not the correct one.

It will not create direction. A manager can run a team well against a clear objective and cannot invent what the business should be doing; hiring one to resolve a strategic question produces a well-managed team executing an unresolved strategy.

It will not reduce the owner's workload immediately, and expecting that is the most common source of early disappointment. The first few months add work: context to transfer, decisions to talk through, your own habits to break. The load comes down later, and only if the direct line was genuinely given up.

It will not fix a team problem the owner has been avoiding. If someone should have been performance-managed for a year, handing that situation to a new manager in their second week is not delegation, it is transfer of an unpleasant task to the person with the least standing to do it. Resolve it first, or at minimum resolve it together and visibly.

And it will not survive an ambiguous mandate. 'Help out with the team' is not a role. What they decide, what they escalate, what they own and who they are accountable to has to be specific enough to write in a paragraph — and the team has to hear the same paragraph.