How to Lead a Team Too Big to Know Everyone Personally
Somewhere between sixty and a hundred people, a threshold passes. You stop knowing everyone’s name, then everyone’s role, then which team half of them are on. For most founders this is one of the more emotionally significant transitions in the company’s life, because personal relationship was not just something you enjoyed — it was your primary leadership mechanism. You knew who was struggling, who was excellent, what was really going on, because you talked to everyone. That mechanism is now gone and it does not come back. This page is about what genuinely replaces it.
What’s inside
The loss is real, and the substitutes are different in kind
What actually replaces personal relationship
The information problem
Staying in contact with reality
Everything you do now carries symbolic weight
What not to try to preserve
Where Blomma fits
The loss is real, and the substitutes are different in kind
Worth acknowledging plainly, because most advice skips it: something is genuinely being lost and there is no equivalent replacement. You will not have the relationship with your hundredth employee that you had with your fifth, and no system produces that. Founders who try to preserve it by force — keeping every one-to-one, insisting on interviewing every hire, being personally available to everyone — end up with no time for the actual job and a company that still cannot know them.
What replaces it is different in kind rather than a smaller version of the same thing. Personal relationship gave you three things at once: information about what was really happening, influence over how people worked, and the ability to develop individuals. At scale those three separate, and each needs its own mechanism.
That separation is the whole transition. Trying to get all three from the same source — you, personally, talking to people — is what does not scale.
What actually replaces personal relationship
Three mechanisms, each covering one of the three things you used to get from being close to everyone.
For influence: the standard, made explicit and applied consistently.You used to shape how people worked by working alongside them. Now you shape it by what you consistently insist on and consistently tolerate, and by whether your decisions are legible. This is why consistency matters far more at scale than it did at twenty people — people who do not know you personally infer everything from your visible behaviour, so an unexplained exception is read as your real preference.
For development: your managers, and their capability.You cannot develop a hundred people. Your managers can, if they are able and if they have the capacity. Which makes the quality of your management layer the single largest determinant of whether people in your company grow — and it makes managing managers your actual job, rather than a thing you do alongside it.
For information: deliberate channels rather than ambient contact.You used to know things by being around. Now you need designed routes: skip-level conversations, written updates from teams, direct channels that bypass the hierarchy, and metrics that are visible without being requested. Ambient information does not scale; designed information does.
Notice that two of the three are not about you doing more, but about building something. That is the shift.
The information problem
The most consequential loss, because you will not notice it happening.
At twenty people, bad news reaches you in a day because someone mentions it. At a hundred and fifty, bad news travels through two or three layers, each of which has a small incentive to soften it — not from dishonesty, but because a manager reporting a problem is also reporting on their own area. So the version that reaches you is smoother and later than the reality.
The consequences are specific: you find out about a failing project a quarter late, about a manager everyone else knows is struggling six months late, and about a cultural problem after the good people have already left.
Three things genuinely help.Skip-levels, on a schedule— not to check on managers, but to hear the work described by the people doing it. Say that framing out loud or they will assume otherwise.Ask narrow questions.“What did I miss in that decision?” gets a real answer where “how are things going?” gets none. Andwatch what people do rather than what they report— attrition in a specific team, a project whose scope keeps quietly shrinking, a meeting that has grown by four people.
One more: reward the first person who brings you an unwelcome accurate thing, visibly. Everyone is watching what happens to them, and that single event does more for your information flow than any process.
Staying in contact with reality
Distinct from information flow. Information tells you what is happening; contact keeps your judgment calibrated so you can tell whether what you are being told makes sense.
Keep talking to customers directly. Not through summaries. This is the single most valuable contact to preserve, and it is the first to go.
Keep some contact with the actual work. Read the code, sit in on a support shift, look at the raw data. Not to review it — to keep the ability to smell when a comfortable explanation is wrong.
Do the work yourself occasionally, in a low-stakes way. A founder whose sense of how long things take is three years out of date makes unreasonable plans and does not know it.
And be deliberate about the sample. If the only people you talk to are your executives and your best performers, you have a systematically optimistic view. Talk to someone in their first month, someone who is struggling, and someone in the least glamorous part of the company.
Everything you do now carries symbolic weight
The adjustment founders find strangest, and it catches everyone out at least once.
At twenty people, a passing comment is a passing comment. At a hundred and fifty, a passing comment from you is a signal that gets relayed, interpreted, and acted on. An offhand remark about a competitor becomes a strategy. Praising one team in an all-hands becomes a statement about which work matters. Sitting in on one team’s meeting becomes a signal about where attention is going.
This is not people over-reading you. It is a rational response to scarce information: most people have very little contact with you, so each contact carries a lot of inferential weight.
Two practical consequences. Be more careful about casual statements than feels natural, particularly speculative ones — “I wonder if we should” gets heard as “we are going to.” And use the symbolism deliberately: what you spend time on, who you promote, what you tolerate, and what you talk about repeatedly are your most powerful instruments, and they work whether or not you are choosing them consciously.
What not to try to preserve
Three things founders hold onto past the point of usefulness.
Interviewing every hire.Reasonable to fifty people, a serious drag beyond a hundred, and it delays hiring in a way that costs more than the quality it protects. Replace it with a clear bar, trained interviewers, and your involvement only in senior roles.
One-to-ones with everyone.Once you have managers, a founder maintaining direct one-to-ones several layers down undermines those managers, whatever the intent — because people will route around their manager to the person with more authority.
Being personally available to everyone.Feels like accessibility and produces a queue, a bottleneck, and a set of managers who have been quietly bypassed. Replace it with scheduled, structured access: office hours, open sessions, skip-levels on a rotation.
The common thread: each of these was genuinely good at twenty people and each becomes a way of not doing the new job. Letting them go is not becoming remote; it is choosing mechanisms that reach a hundred and fifty people rather than the fifteen you can personally cover.
Where Blomma fits
The difficulty in this transition is that the thing you are being asked to give up is the part of the job most founders liked best, and the replacements are indirect, slower, and much less emotionally satisfying. It is also lonely in a specific way: the larger the company, the fewer people you can speak to candidly inside it.
Blomma is an always-on AI career coach with no stake in your company. Use it to work out which of the three mechanisms you have actually built and which you are still trying to do personally — most founders find they have built none of them and are compensating with effort. Use it to design your information channels, and to prepare the skip-level framing so it does not read as checking up on managers. Use it to think through the symbolic weight of a decision before you make it casually. And use it as the candid conversation that gets harder to find inside your own company as it grows.
The second application is the load-bearing one. At this size, whether people grow depends almost entirely on your management layer’s capacity, and that capacity is thin exactly when you are scaling fastest. Coaching that does not depend on a manager’s calendar having room is how development keeps happening when you can no longer do it yourself..
You cannot scale a relationship. You can scale a standard, a set of channels, and a layer of managers — and doing that deliberately is what leading a large team actually consists of.