What breaks when you go from 10 to 50 people (and how to avoid it)

1. Communication: from “everyone knows” to “nobody knows where to look”

At ten people, one general channel is enough. At forty, there are thirty channels and the important information is scattered across them, email and meetings. The warning sign: someone asks about a decision made two weeks ago and nobody can link to where it happened.

• Decide what each channel is for and archive the ones nobody uses.
• Separate announcements (to read) from conversations (to join).
• Write important decisions in one fixed place, not just in a thread.
• Send a short weekly leadership note on what changed and why.

2. Decisions: from the founders to the teams

Early on, founders decide almost everything, and that’s fine. As you grow, if everything still goes through them, the company moves at the speed of their calendar. The sign: queues of “waiting for [founder] to look at it”.

Write down which decisions each lead makes on their own, which need a second opinion and which stay with leadership. And record the reasoning behind big decisions: that’s what lets others decide similarly without asking.

3. Context: knowledge stays with people

Why you picked that supplier, how month-end close works, what was promised to a client. At ten people, you ask. At fifty, the person who knew may have left. The sign: the same questions in Slack every few weeks.

You don’t need a grand corporate wiki. You need decisions and processes written down where they’re made (meetings and channels) and findable through search.

4. Onboarding: from “sit with Juan” to a plan

When one person joins a month, pairing them with someone works. When four join, that someone stops getting their own work done. The sign: new hires take a long time to become independent and always ask the same two people.

• A first-week plan per role, with access, key people and first tasks.
• A go-to person who isn’t their manager.
• “How we do things here” documentation that someone reviews every few months.

5. Processes: neither all nor none

The classic scaling mistake is jumping from no processes at all to documenting everything. Start only with the ones that cost money or clients when they go wrong: billing, hiring, client delivery, incidents. The rest can wait until it hurts.

For each one, a single page is enough: what triggers it, the steps, who owns each step and what “done” looks like. If nobody can write that page in half an hour, the process probably doesn’t exist yet, and that’s the real problem to solve first.

What to do this quarter

If you’re somewhere between 15 and 50 people, a realistic three-month plan:

• Month 1: tidy up channels and start taking minutes with tasks in every team meeting.
• Month 2: list the decisions each lead owns and document your three most critical processes.
• Month 3: build a first-week plan per role and a weekly pulse per department.

How Tessa helps you grow without losing track

Tessa works on top of Google Workspace and Slack, where most companies this size already live. She turns emails, messages and meetings into tasks with owners, takes notes in Google Meet (Zoom and Teams in beta) and follows up on commitments. The wiki writes itself from minutes, channels and shared documents, and search answers with sources cited.

For leadership, the weekly department pulse shows blockers and overdue work without individual metrics. What Tessa reads from each person stays private, and anything leaving the company needs approval.