Your role changes before you notice it

There is a moment in most growing firms when the founder or lead consultant quietly becomes the bottleneck. You are still doing client work, still fielding the awkward questions, still the person everyone waits for — and yet the team around you now needs something different. It needs direction, not just decisions.

This shift is uncomfortable, partly because the old job was measurable. You could point at the finished report, the satisfied client, the invoice raised. Guiding other people is messier: progress shows up as better questions from your team, fewer fires, work that no longer lands on your desk unannounced. The temptation is to keep doing, because doing is familiar and feels safe. But every hour you spend on work somebody else could do is an hour you did not spend on the things only you can do.

Be explicit about what good looks like

Most underperformance in small firms is not laziness. It is ambiguity. People are guessing at your standards, and guessing usually means aiming low.

Take an hour and write down what you actually expect. Three areas are worth covering:

• Outcomes. Describe what a finished piece of work looks like. Not "a client update" but "a one-page update the client can read in two minutes, sent the same day as the meeting, with next steps and owners named".
• Boundaries. How quickly do client emails get answered? When does a problem get escalated rather than sat on? What is never acceptable — missing a deadline silently, for instance.
• Decision rights. Where can someone act alone, where should they check in first, and where does the decision sit firmly with you.

A single page is enough. Share it, talk it through, and revisit it when the team changes. It saves far more time than it takes to write.

Give feedback in small, regular doses

An annual appraisal is far too slow a feedback loop for a team of eight. By the time you raise something in December, the person has spent months believing they were doing fine. Aim for something closer to a fortnightly rhythm, and keep it brief.

A pattern that works well in small teams is: describe the situation, name the behaviour, explain the impact, then ask a genuine question. For example: "In yesterday's client call you cut across Sam twice. It made it harder for them to finish the point, and I think the client noticed. What was going on for you?" That last question matters. It turns a telling-off into a conversation, and you often learn something about the pressure they were under.

Praise needs the same specificity. "Great work" evaporates by lunchtime. "The way you handled the pushback on the budget call — you held the line without getting defensive — that is exactly what I want clients to see" tells someone what to repeat.

Hold one-to-ones people actually value

Thirty minutes, same slot each week or fortnight, and one firm rule: it is not a status update. Status lives in your project tracker. This time belongs to the person in front of you.

Three questions will carry most of the conversation:

• What has gone well since we last spoke that I should know about?
• What is getting in your way?
• What would you like to be doing more of in six months?

Then act on one thing before the next meeting. Trust is built on follow-through, not on the meeting itself. If somebody tells you they are drowning and nothing changes, they will not tell you again.

Delegate the whole task, not the pieces

Handing over a list of jobs creates a queue of questions and keeps you at the centre of everything. Hand over a result instead, along with the authority to make decisions inside it.

Agree the checkpoints upfront: what the finished thing looks like, when you will review a first draft, and what warrants an early phone call. Then step back. Expect it to be done differently from how you would do it, and expect the first attempt to be slower and rougher than you would like. Resist the urge to quietly fix it — if you do, you have taught everyone that your way is the only way, and that delegation is really just inspection.

Grow the leaders underneath you

Leadership skills spread through practice, not job titles. Give someone the weekly team meeting to run, a new starter to look after, or a client relationship to own. Tell them why you chose them, and what support they can expect from you while they find their feet.

The conversations you avoid are usually the ones that matter most — the capable person who has become disengaged, the colleague whose tone is upsetting clients, the two people who no longer work well together. Handle them early, privately and plainly, and you set the standard for how your team handles its own difficult moments.

And remember that your team watches how you behave under pressure far more closely than they listen to what you say. If you want calm, honest, straightforward conduct from them, that is the version of yourself you need to bring to the office — including on the days it is hardest.