Here's a scenario that plays out in almost every growing SMB, usually somewhere between year two and year four.

The business is doing well. Revenue is up. You've hired good people. On paper — and often on a whiteboard or a slide deck — the org looks clean. But something doesn't feel right. Decisions are slower than they should be. Things that used to happen automatically now require a conversation. You're in more meetings, not fewer. Your best people are starting to look slightly frustrated without being able to say exactly why.

Nothing has gone wrong. And yet something has quietly broken.

What's almost certainly happened is that your organization has outgrown its structure — and nobody called it, because it doesn't announce itself loudly. It just accumulates as friction.

The way most SMB structures are built

In the early days, org structure is a non-issue. There are five, maybe eight people. Everyone knows what they're doing. The founder is across everything by necessity, and that works because the team is small enough that one person actually can be across everything.

Then the business grows. A new hire joins. Then another. Someone takes on a functional area. A layer of informal seniority develops. And the structure — if you can call it that — expands to accommodate each new addition without anyone stepping back to ask whether the whole thing still makes sense.

This is perfectly normal for small businesses. The problem is that it creates structures built around the people you happened to hire, in the order you happened to hire them, rather than around what the business actually needs. By the time you hit 15 or 20 people, you're often running a company on an org design that was never really designed at all.

The number that matters more than headcount

Most founders think about growth in terms of headcount. How many people do we have? How many do we need? But there's a more important number that rarely gets tracked in smaller businesses: how many people does each manager — including the founder — actually have reporting to them?

This is called span of control, and it's one of the most reliable structural signals in any organisation.

When a founder or senior leader has too many direct reports — typically anything beyond seven or eight in a complex environment — something has to give. And what gives first is almost always quality of management. Not because the leader isn't capable, but because there are only so many hours in a week. At a certain point, you're no longer managing people; you're triaging them. The one-to-ones get shorter. Performance issues get spotted later. Development conversations don't happen. And the people underneath start to feel it — as a vague sense that they're less supported than they should be, even if they can't articulate why.

Recent Gallup data shows that the average number of direct reports per manager in the US has increased nearly 50% since 2013 — a reflection, in part, of businesses flattening their structures to cut management overhead without always thinking through the downstream consequences. For SMBs that were already running lean, that trend makes the span of control question even more pressing.

The five signs your structure has outgrown itself

You don't need a consultant to tell you there's a structural problem. These patterns tend to show up first:

Decisions are escalating upward that shouldn't. When team members regularly bring decisions to leadership that they ought to be able to make themselves, it usually means one of two things: either the authority structure isn't clear, or they haven't had the development conversations that would give them the confidence to act. Both are management capacity problems.

Your calendar is full of the wrong things. If the founder or CEO is spending most of their week inside operational detail rather than on strategy, hiring, and the work only they can do, the structure isn't creating the space it should. This isn't a time-management issue — it's a structural one.

Onboarding takes too long. When new hires need several months to feel genuinely productive, it's often because nobody has the bandwidth to bring them up to speed properly. An overstretched manager cannot onboard people well.

Performance issues surface late. By the time a performance problem becomes visible to leadership in a growing SMB, it's often been quietly obvious to the team for months. When spans are too wide, small issues compound into big ones before they get caught.

Strong people start to plateau. High performers in SMBs leave for one of two reasons: a better opportunity, or a feeling that they've stopped growing. The second one is almost always a management bandwidth problem in disguise. You can't develop people you don't have time to invest in.

The structural decision most SMBs delay too long

At some point in the growth of every small business, there comes a decision that founders frequently resist: adding a layer of management.

The resistance is understandable. Management overhead costs money. Middle managers can add bureaucracy rather than value. And founders who built their culture on flatness often see a management layer as something that will make the business slower, more political, more like the large corporations they never wanted to become.

Some of that concern is legitimate. A poorly designed management layer absolutely can create those problems. But refusing to add any structural depth at all carries its own costs — and those costs tend to compound invisibly, as the quality of management slowly erodes under the weight of too many competing demands.

The five reliable signals that a first management layer is overdue in a growing SMB: more than eight direct reports to a single leader, more than 15 hours a week spent on management activities by that leader, the team spanning more than three distinct functional areas, consistent growth of four or more people per year, and performance issues that are being caught late rather than early. One or two of those signals showing up is a prompt to pay attention. Three or more is a prompt to act.   Our Organizational Design & Effectiveness service provides the frameworks and facilitation to redesign your operating model as you grow.

What to actually do about it

The goal isn't to add complexity for its own sake. It's to build a structure that can carry the weight of where the business is going — not just where it's been.

Start with a span audit, not an org chart redesign. Before you touch reporting lines, simply map how many direct reports each leader in the business currently has — and what kinds of decisions and management activities that actually requires week to week. The gap between what's on the org chart and what's actually happening is usually where the structural problem is hiding.

Separate functional ownership from people management. In small businesses, these two things are often bundled together — the most senior person in an area both leads the function and manages the people in it. As the team grows, those two responsibilities can start to pull against each other. Being explicit about which role a person is playing in a given context can reduce a surprising amount of friction.

Promote from within deliberately, not by default. The most common way a management layer gets added in SMBs is by promoting the most senior individual contributor into a people management role. That works sometimes. But management is a genuinely different job from being good at the underlying work, and the transition deserves real support — not just a new title and an expanded team.

Revisit structure when strategy shifts, not just when headcount grows. Most businesses rethink their org design when they're hiring. But a change in strategy — entering a new market, launching a new product line, acquiring another business — usually warrants a structural rethink even if headcount stays the same. The structure needs to serve the strategy, not the other way around.

The conversation most leaders avoid

There's an honest version of this conversation that doesn't happen often enough inside growing businesses. It goes something like: "We've built something good, and the way we're structured right now is starting to slow us down. Not because of the people — because of the design."

That conversation requires a leader to look at how the organisation is built and say, clearly, that it needs to change — even though nothing has obviously broken, and even though changing it will cost time, money, and some of the informality that made the culture feel good in the early days.

The businesses that have this conversation early tend to grow through the 20–50 person stage with a lot less pain than those that wait until the structural strain becomes undeniable. And the ones that wait usually spend 18 months wondering why the business feels harder to run than it did when it was smaller — before eventually arriving at the same conclusion anyway.

Structure isn't the most exciting part of building a business. But it's one of the most consequential, and it deserves more deliberate attention than most growing SMBs give it.  See how leadership and structural design changes were implemented at pace in our Leadership & Change Management case study.

The bottom line

Your org structure is not a fixed asset. It has a shelf life. The design that worked for 10 people will strain at 20 and break at 35 — not because your team isn't good, but because the demands on any structure change as the business grows. Treating org design as a one-time decision rather than an ongoing leadership responsibility is one of the most common and most costly mistakes in the SMB growth journey.

At Amasu, we work with growing SMB leaders to assess where structural strain is building, identify the right design adjustments for the stage the business is at, and implement changes in a way that doesn't disrupt the culture they've built. If your business has grown quickly and the org feels like it's working against you rather than for you, we'd be glad to take a closer look.