There’s a moment in every organization’s growth where the systems that got you here stop working. It’s not dramatic. You don’t wake up one day and find everything broken. Instead, you notice friction creeping in – decisions take longer, communication gets muddled, people step on each other’s work. The instinct is often to patch things: hire faster, add more meetings, create new roles. But what’s really happening is that the organization has outgrown its operating model, and no amount of incremental adjustment will fix it.
I’ve watched this play out across different industries and company sizes. The pattern is consistent. A team of five or ten people operates through informal channels. Everyone knows what everyone else is doing. Decisions happen in conversation. There’s minimal documentation because context lives in people’s heads. It works remarkably well until it doesn’t. Then you add ten more people, or fifty, and suddenly the same approach creates chaos.
The core issue isn’t complexity for its own sake. It’s that different scales of organization require fundamentally different ways of coordinating work. What scales at ten people – direct communication, shared context, informal prioritization – becomes a liability at fifty or a hundred. The organization needs new structures, not because they’re better in some absolute sense, but because they solve problems that simply don’t exist in smaller groups.
Where informal systems break down
In small organizations, the absence of formal process is actually an advantage. You move fast because you don’t have bureaucracy. You adapt quickly because decisions don’t require approval chains. But this model depends entirely on a shared understanding of priorities and constraints. It works when everyone in the room knows the strategy, the budget, the customer problems, and what others are working on.
As the organization grows, that shared context fragments. New people join who weren’t in the founding conversations. Teams form around specific functions. A person in one area no longer automatically knows what another area is doing. Decisions that used to happen in a ten-minute conversation now involve people who aren’t in the same room, sometimes not in the same location. The informal system doesn’t scale because it was never designed to bridge that distance.
I’ve seen organizations try to preserve the “startup feel” by resisting formalization. They avoid documentation, skip formal planning, resist hierarchy. The intention is good – they want to keep the agility and culture. But what actually happens is that decisions become political rather than transparent. Information flows through personal relationships rather than clear channels. New people feel lost because the unwritten rules aren’t actually unwritten; they’re just not written down, which means they’re only known to people who’ve been there long enough to absorb them.
What actually has to change
When I think about organizations that scale well, the difference isn’t that they’re more bureaucratic. It’s that they’ve made deliberate choices about how information flows and decisions get made. These choices look different depending on the organization, but the underlying need is the same: you need explicit structures that don’t depend on everyone being in the same room.
Decision-making authority has to become clearer. In a small team, authority is implicit – the founder decides, or whoever has the most context decides. At scale, you need defined decision rights. Who decides on hiring? Who decides on budget allocation? Who decides on product direction? Without clarity, you get either bottlenecks (everyone waits for one person to decide) or chaos (multiple people making conflicting decisions). Most growing organizations experience both simultaneously in different areas.
Communication patterns shift from synchronous to asynchronous. Early-stage teams can rely on constant conversation. Everyone’s available, everyone’s in the loop. As you scale, that becomes impossible. You need written records of decisions. You need documentation that people can reference without asking. You need communication channels that don’t require everyone to be present at the same time. This feels slower initially – it is slower in some ways – but it’s the only way to coordinate across larger groups.
Role clarity becomes essential. In small organizations, roles are fluid. Someone might do product work, customer support, and hiring all in the same week. It’s efficient because there’s no overhead of handoffs or coordination. But it also means nobody really owns anything. As you grow, you need people who are accountable for specific areas. Not because accountability is virtuous, but because without it, important work falls through cracks. Someone has to be the person who decides when something is done, who knows the full scope of a project, who can be consulted when questions arise.
The resistance is usually about more than process
Organizations often resist these changes, and the resistance reveals something important. When people push back on documentation, formal processes, or clearer roles, they’re not usually objecting to the process itself. They’re reacting to what they perceive as a loss of autonomy or a shift in culture. And they’re not entirely wrong. Formalization does change how an organization feels.
But here’s what I’ve observed: the organizations that handle this transition well don’t pretend the change isn’t happening. They acknowledge it directly. They say something like, “We’ve grown to the point where our old way of working doesn’t work anymore. Here’s what we’re changing and why. Here’s what we’re keeping.” They’re honest about the tradeoffs. You do lose some of the spontaneity. You do add some process overhead. But you gain the ability to coordinate across larger teams without everything becoming someone’s personal responsibility.
The organizations that struggle are the ones that try to have it both ways. They add formal processes while pretending the culture hasn’t changed. They create hierarchy while insisting it’s still flat. They introduce documentation while acting like it’s optional. That disconnect creates resentment because people can feel the change even if leadership won’t name it.
Scale determines what’s possible
Different scales require different operating models, and there’s no single “right” way. A team of twenty can operate very differently from a team of two hundred, and both can be effective. But within each scale range, certain structures work better than others.
At the fifteen-to-thirty-person range, you typically need clearer roles and some basic documentation, but you can still operate with relatively flat decision-making. People can still talk directly across the organization. What breaks down is the assumption that everyone knows what everyone else is doing. You need some way to make that visible.
At fifty to a hundred people, you need actual management layers and formal communication channels. Not because you’re trying to be corporate, but because the span of coordination has become too large for informal methods. A manager isn’t a bureaucratic layer; they’re a way of grouping related work and creating a clear point of communication.
At several hundred people, you need even more structure. Departments. Cross-functional processes. Formal planning cycles. This isn’t a choice about culture anymore; it’s a practical requirement for the organization to function.
The mistake many organizations make is adopting structures that match their aspirational size rather than their actual size. A thirty-person company that implements processes designed for a three-hundred-person company will feel suffocated. But a thirty-person company that refuses to adopt any structure will eventually become dysfunctional. The key is matching your operating model to where you actually are, not where you want to be or where you used to be.
What I’ve learned from watching organizations navigate this is that the transition is less about finding the perfect system and more about being honest about what’s changed. The work of growth isn’t adding more people and hoping the old system stretches. It’s recognizing that you’ve crossed a threshold where the way you coordinate work has to fundamentally shift. That recognition, uncomfortable as it is, is what allows an organization to adapt rather than resist.
