alt.hn

3/15/2026 at 11:16:05 AM

Ask HN: What breaks first when your team grows from 10 to 50 people?

by hariprasadr

3/16/2026 at 9:44:32 AM

Growing companies from ~10 to ~200+ has been my bread and butter for almost 20yrs now. A few relatively universal observations:

1. As sloaken said, your documentation of processes and procedures is NOT adequate. This applies to everything. From your code commit process to how to book vacation days. Document everything early. Notion is your friend.

2. Like it or not, your work culture is going to change. New people obviously means new personalities but it also means new ways of working, some good, some bad. It really is worth spending some time with the first 15 people that helped get your company to where it is today and define some operating principles (otherwise known as 'company values'). This blog post (not mine) is an incredible insight into why this stuff actually matters at your stage of growth: https://lowercaseopinions.com/post/useful-values

3. Hiring gets expensive and laborious. You're reaching a point where it just isn't practical for you to be involved in every hiring decision. That being said, don't let go of it until you are confident that everyone involved in hiring for your company is aligned on what 'good' looks like both in terms of candidates and hiring process.

4. More people means more individual questions, problems, and ultimately admin. More people getting paid means more payroll issues and questions and adjustments. More people interacting with each other means more disagreements, arguments, and issues. Someone needs to be able to handle all of these issues. Usually the challenges are distributed across different teams but again, without some rigour around how you want your company to approach these issues means that different managers/teams will take different approaches which in turn will amplify the problems rather than solve them.

5. Reconsider the financial impact of hiring experienced people. Bringing in strong leaders early can enormously mitigate the operational costs of scaling. Hiring a highly experienced person at your stage will have a big impact on your budget but long-term, that investment will pay dividends both in terms of the quality of work but also in sharing the burden of handling these scaling challenges.

by Peroni

3/15/2026 at 12:53:18 PM

Done this. Good question but I don't think it's the most helpful way of thinking about it.

Every new recruit brings their own assumptions about how organizations / employment / etc. work and many of those assumptions won't be visible until after a while. This is especially true for managers.

I found Charles Handy's thinking about four types of organisational culture very helpful and I wish I'd found it earlier in the process.

AI summary: Charles Handy identified four types of organizational cultures: Power Culture, where decision-making is centralized among a few; Role Culture, which is based on defined roles and responsibilities; Task Culture, focused on teamwork to achieve specific goals; and Person Culture, where individual interests take precedence over the organization.

Basically, 15>50 is very likely to involve a shift from one of these to another one and making that open and explicit could help you a lot (including understanding how the role of senior managers needs to change).

The book is Understanding Organisations from 1976 but still valuable.

Good luck!

by idw

3/15/2026 at 1:33:12 PM

This might not be the first to break, but it will eventually, and if corrected NOW will make things much smoother:

Your documentation of processes and procedures is NOT adequate.

'everyone used to know about are getting lost' - oh good thing your documentation makes this clear, because it is obviously their fault.

'New hires take forever to ramp up' - oh good thing you have complete ramp up plan and documentation, because it is obviously their fault.

'building on different assumptions' - oh good, your old assumptions are clearly documented, because it is obviously their fault.

So their is your self focus, please do good, and document well.

by sloaken

3/15/2026 at 4:04:32 PM

So, documentation is the solution? But do people have time to document everything?

by hariprasadr

3/15/2026 at 6:02:46 PM

Anything not documented is throw away.

Any given day someone can win the lottery, inherit a lot of money, or need to leave for some other reason.

Every complaint they had was a direct effect of failure to document. Well that or the other people are just complete idiots ... you decide.

by sloaken

3/15/2026 at 11:53:06 AM

I think what breaks first is team / org dependent but ime: alignment & quality standards

I found a mixture of shoehorning the vision into as many conversations as possible and occasional in person meetups (we die roughly yearly) helped with vision. I dont have measurements but my concern for teams decision making dropped a lot and disagreements in smaller discussion settings also dropped.

Standards dropping was secretly alignment too but more around why than what. I found building a culture of excellence helped e.g. "we're here to build software we're proud of, from the code to the experience, and you are the right people do it, so lets build something we're proud of.". You or who ever has to actually believe they are the people to so it though.

Im sure people have more concrete and technical examples.

by iovrthoughtthis

3/15/2026 at 11:23:53 AM

Note the military has a fractal structure such that you still have smaller units inside a bigger operation. I think that’s part of the solution.

by PaulHoule