Questions we answer Team structure and leadership

Everything comes back to me — what do I do?

Decide which decisions genuinely need you, hand the rest over with the authority to go with them, and write down what only lives in your head. Most founders are the bottleneck because nobody has been told where the line is.

Start from this question

Free · a few minutes · starts from “I'm not sure how to structure the team”

The short answer

This is usually a delegation and structure problem rather than a workload one. If every decision routes through one person, adding people increases the number of decisions without changing who makes them. The productive moves are to write down what only you know, hand over the decisions that do not genuinely need you, and see what remains. A management layer or a senior hire becomes the right answer once what is left is a real role rather than the residue of never having delegated.

Being the person everything routes through is usually the result of doing the right thing for too long. In a small team, the founder deciding everything is efficient. Past a certain size it becomes the limit on everyone else's work.

The fix is rarely a new layer of management. It is deciding, explicitly, which decisions you keep, which you delegate inside a boundary, and which you never wanted in the first place — then saying so, because people cannot read your mind and will keep asking until you tell them.

Is it really this?

Worth checking before you spend anything. These are the signals that tend to tell the two apart.

Signs it is

Your week is made of interruptions, and the work only you can do happens in the evening.
Decisions wait while you are on holiday, in a meeting or travelling.
People bring you options rather than decisions, and expect you to choose.
You can list the questions you are asked repeatedly, and they are not hard ones.

Signs it's something else

The team has the authority and uses it, and there is simply more work than hands.
You are asked about one particular area, which is a capability gap rather than a structural one.
The questions really are yours — pricing, direction, a key relationship — and there are not many of them.
Nobody is asking you anything, and the problem is that work stalls silently instead.

What's usually behind it

Authority that was never delegated alongside responsibility, so people hold the work without the right to decide.
A team that has learned it is faster to ask you than to risk being wrong.
Knowledge that exists only in your head, which makes asking you entirely rational.
A reluctance to let a decision be made slightly differently from the way you would make it.

What people usually get wrong

Delegating the task and keeping the decision, which produces the same interruptions with more steps in between.
Recruiting a manager to absorb the questions before working out which questions should exist.
Delegating and then overturning, which teaches the team to check with you first next time.
Trying to fix it in a single week rather than handing over one decision at a time.

The options, and when each one fits

In no particular order. Which of these fits depends on your situation, not on the question you typed.

Name the decisions and who makes them
People hold the work but keep coming back for permission.
Write down what only lives in your head
The questions repeat, and the answer is knowledge rather than judgement.
Give someone a budget or a boundary
The decision can safely be made differently from how you would make it, within limits you can live with.
Develop a second decision-maker
Somebody has the judgement for it and no room to use it.
Add a manager
The team has genuinely outgrown one person's span of attention, and ownership is already clear.

When doing nothing is the right call

If the business is still small enough that you are the fastest route to an answer, being the bottleneck is not yet the problem. Set a marker instead — the next hire, the next large customer, or the week you start doing your own job in the evenings — and act on it when it arrives rather than waiting for it to hurt.

What the diagnostic asks

What feels wrong about the current shape, and how big the team is.
Who owns the work today, and how much of it is written down.
Whether someone in the team could realistically grow into more of it.

“I don't know” is always an answer. Nothing is assumed on your behalf.

The routes it weighs

Every diagnostic weighs all ten routes. These are the ones that tend to matter for this question — a description of the rules, not a promise about your answer.

Redistribute
Move ownership of the work to where it fits, and make that explicit.
Process improvement
Change how the work flows — remove steps, name an owner, fix the hand-offs.
Develop
Build the capability in someone already in the team, with time and support.
Recruit
Recruit a new person for a durable, sizeable need that is central to the team.

What changes the answer

Ownership that is clear on paper but not being used points at authority rather than structure.
Nothing written down makes documentation the first move whatever else follows.
A team that has outgrown what one person can hold makes a management layer credible — once ownership is clear, not before.

Get your own read

A handful of short questions, then the strongest route for your situation, what's also credible, what we still don't know and what would change our view. No account, no setup.