Teams that were brilliant at thirty people often become difficult at eighty. The people have not changed. The work they are good at has not changed. But the conditions have, and the behaviours that worked in a smaller, faster, more informal environment are not always the ones that a scaled organisation needs. Understanding what growth is actually asking of a team, rather than just announcing that things need to be different, is the difference between change that lands and change that creates resentment.
1. The real-world scenario
What the team was built for
In a small organisation, proximity, informality, and high individual ownership compensate for the absence of formal structure. Communication happens in real time. Decisions get made quickly because the people who need to decide are usually in the same room or one message away. Trust is built through shared experience and mutual visibility. The culture is strong because it lives in a small number of specific relationships rather than in a system.
2. What may be happening
What growth disrupts
Growth introduces people who were not present for the founding moments. It creates layers between the leader and the work. It increases the number of decisions that cannot be made by the original team, which means authority needs to be delegated to people the leader may not know well enough to trust instinctively. Informal communication channels that carried the culture in a smaller team no longer reach everyone. What used to hold together through relationship now needs to hold together through structure, and structure feels bureaucratic to people who are used to moving fast.
3. Why it lands harder than expected
The identity problem
For the people who built the company through its early stage, growth can feel like a loss of the thing they valued most. The culture that attracted them and that they helped create begins to feel more distant, more formal, more managed. The very behaviours that made them successful, moving fast, deciding independently, building through strong individual relationships, may no longer serve the organisation in the same way. This is not a failure of those people. It is a structural shift that requires new behaviour from people who have only been rewarded for the old kind.
4. What actually helps
What growth asks specifically of leaders
Scaling requires leaders to operate differently in three specific ways. They need to build trust with people they have not yet accumulated experience with, which means making trust more explicit and less instinctive. They need to delegate decision-making in domains they previously controlled, which triggers certainty and autonomy threats in the SCARF model. And they need to translate culture from something they embody personally into something the organisation can carry without them in every room. All three of these are genuinely hard, and most organisations move through them without naming them as the specific challenges they are.
5. What to try next
A useful reframe
The question is not how do we keep the culture we had. That culture belonged to a specific size and a specific moment. The question is what is at the core of what made this place worth working in, and how do we rebuild that core so it works at the new scale. The answer is almost always about relationships, honesty, and how decisions get made, not about the informal rituals that expressed those things in the earlier period.
6. What to notice
A small habit to try
In your next leadership team conversation about growth, ask one question before you discuss structure, process, or headcount: what does the growth we are planning ask of us as individuals? That question tends to surface the real concerns that the process conversation can obscure.
Growth does not break culture. It reveals which parts of it were held together by proximity and which parts were genuinely structural.
7. What to design around the role
Three things tend to make a more substantial difference.
Name what the old team was brilliant at
Identify which small-company habits no longer scale.
Separate identity from operating model
Make decisions, roles and communication rhythms more explicit.
Make new expectations explicit
Protect trust while reducing dependency on personal closeness.
Protect trust while increasing structure
Help people grieve what is changing as well as build what is needed.
8. Questions to reflect on
Use these to notice where editing has become the default.
- 01Which old habit is now creating drag?
- 02What does the team feel it is being asked to lose?
- 03Where is informality no longer enough?
- 04What structure would help without killing what works?
Takeaway
The behaviours that built a company through its early stage are not the same ones that will carry it through scale. The work is to find what is worth translating, not just what is worth preserving.
Keep the next step clear.
9. Continue this pathway
Previous guide
Hybrid did not create your relationship problems. It just made them impossible to ignore.
Go back if you want the step that led into this idea.
Read nextNext guide
Why the person who got you here might not be the problem you think
Read this next to keep moving through the pathway in order.
Read next