Scaling Past $20M: Transformation Without the Chaos

Scaling a business past $20M is not a growth problem. It is a discipline problem. The companies that make it through without burning out their teams or their margins are the ones that build systematic capacity before they need it.

Why Growth Breaks Companies at This Stage

Most businesses hit a wall somewhere between $10M and $30M. Revenue keeps climbing but margins shrink, good people get buried in firefighting, and decisions that used to happen fast now take weeks. Everyone is busy. Nothing meaningful gets done.

This is not a staffing problem or a strategy problem. It is a constraint problem.

Every system has a constraint. One process, one role, one handoff point that limits everything else downstream. When you grow without finding and fixing that constraint first, you just move faster toward the same bottleneck. You hire more people to stand in front of the same clogged pipe.

The companies that scale well do one thing differently. They find the constraint first, fix it completely, and then move to the next one.

The 10-Year Story: Knowing Where You Are Going

Disciplined scaling starts with clarity, not urgency. Before you sprint on anything, you need a picture of where the business is going over the next decade and an honest read on what is standing in the way today.

We call this clarifying the 10-year story.

This is not a values exercise or a vision statement for the website. It is a practical question: what does this business need to look like in 10 years, and what has to be true operationally for that to happen? Revenue targets matter, but so do margin structure, leadership depth, customer concentration, and whether the business can run without the founder in the room.

Once that picture exists, the path from here to there becomes a sequenced set of problems to solve, not a vague aspiration to chase. You stop reacting to whatever came up this week and start making deliberate choices about what to build, fix, or stop doing.

This clarity also creates alignment. Leadership teams that share a specific 10-year picture make faster decisions and fewer contradictory ones. The daily noise quiets down because people know what they are optimising for.

Rapid Sprints: DMAIC as the Execution Engine

Once you know what the constraint is, the question is how to eliminate it without blowing up the business in the process. The answer is structured sprints, and the framework we use is DMAIC.

DMAIC stands for Define, Measure, Analyse, Improve, Control. It is the backbone of Lean Six Sigma and it is exactly as practical as it sounds.

Here is how it works in a real scaling context:

• Define the problem precisely. Not "our scheduling is a mess" but "we lose 4.5 hours of billable time per day because intake appointments are not confirmed 48 hours in advance."
• Measure the current state with actual data. Gut feel is a starting point, not a baseline.
• Analyse what is causing the gap. Not what you think is causing it. What the data shows.
• Improve by designing and testing a specific change to the process. Run it small before you run it everywhere.
• Control by building the new process into your standard operating procedures, scorecards, and team habits so it does not quietly revert to the old way.

A well-run DMAIC sprint takes four to eight weeks. At the end, the constraint is measurably smaller or gone, and the improvement is embedded into how the team works, not sitting in a slide deck.

We have run over 500 improvement projects using this approach, and the pattern holds. When organisations skip the Measure and Analyse steps because they are already confident they know the answer, they spend money and time fixing the wrong thing. The discipline of the process is what makes the result stick.

The 10-80-10 Method: Do It With Your People

Here is where a lot of transformation work fails. An outside team comes in, diagnoses everything, builds the new process, and hands it over. Two months later the old habits are back and the investment is gone.

The reason is ownership. People adopt what they help build.

We use a structure called the 10-80-10 method to keep the work grounded inside the organisation throughout the entire sprint.

The first 10 percent is co-design. We work with a small group of internal leaders to define the problem, agree on success metrics, and set the scope of the sprint. Not a presentation to them. Working sessions with them.

The middle 80 percent is where the real work happens and it happens with the people who actually do the process every day. They are the ones who know where the rework lives, which handoffs break down at month-end, and what the workarounds look like. That intelligence does not appear in an org chart.

The final 10 percent is transition and control. The team that built the improvement owns the scorecard that tracks it. They write the standard operating procedure. They present the results to leadership. By the time the sprint closes, the people inside the business are already operating the new way.

This is not a soft approach. It is the most reliable way to make change permanent.

Building Change Leaders

Process improvement is not a one-time project. Scaling a business means running continuous cycles of finding constraints, eliminating them, and building on the gains.

The organisations that sustain this are the ones that develop internal Change Leaders. People who understand how to run a DMAIC sprint, how to use data to make the case for change, and how to bring a team through a transition without losing anyone along the way.

This is a specific capability, and it needs to be deliberately built. We train and coach Change Leaders inside every client organisation we work with. Not so they become consultants. So they can run the next sprint themselves.

The payoff compounds. Each wave of improvement is faster and more embedded than the last because the internal team knows what they are doing. The organisation builds a culture of continuous improvement rather than a series of one-off interventions.

A CPG firm we worked with came in at $20M and grew to $155M. The revenue growth was real, but what made it possible was an internal team that had the discipline and the skills to find and fix constraints as fast as the business created them. They did not need outside help every time something broke. They had people who could handle it.

Strategic Execution Lives in Your Existing Meetings

One of the most common mistakes in scaling a business is treating strategy and execution as two separate tracks. The leadership team does strategy in a quarterly offsite and execution happens somewhere else, in someone else's meeting, tracked in a spreadsheet no one looks at.

That gap is where accountability dies.

Strategic execution needs to live inside the meetings you already run. Not as a separate process that competes for attention, but as the organising logic for the conversations that are already happening.

This means building OKRs and shared scorecards that connect the 10-year story to this quarter's sprint priorities to this week's team stand-up. It means having a visible measure of progress that every team member can see and update. It means the CEO's weekly one-on-one includes a direct look at whether the constraint that was targeted in the last sprint is actually improving.

When the rhythm is built this way, strategy stops being something that happens twice a year and starts being something the business does continuously. The plan and the work become the same thing.

Results Live in the Numbers, Not the Deck

Scorecards are only useful if they tell the truth. The number that matters is not the one that makes the leadership meeting comfortable. It is the one that shows whether the constraint is actually moving.

Build your scorecard around lag measures and lead measures. Lag measures tell you what happened. Revenue, margin, customer retention. Lead measures tell you whether you are doing the things that will produce the lag. Appointments confirmed on time, cycle time per order, rework rate per shift.

When both are visible in the same place, the conversation in the room becomes about what to change, not what to report.

What This Looks Like in Practice

The results from this approach are concrete.

A therapy clinic came to us with three practitioners and a scheduling system that was bleeding appointment capacity. We ran a DMAIC sprint on their intake and scheduling process, fixed the handoffs between reception and clinical staff, and rebuilt the confirmation workflow. Within 18 months they had grown to 16 practitioners. The growth was possible because the infrastructure could handle it without collapsing.

An occupational therapy business was struggling on every dimension: revenue, margins, team retention, and owner involvement in day-to-day operations. Three years of disciplined improvement work later, they exited for $5M. That exit was the product of a business that looked completely different internally than it had when we started.

A construction firm scaled from $42M to $180M. A CPG firm scaled from $20M to $155M. In both cases, the constraint work came first. The revenue followed.

The Capacity You Already Have

Across all of our client work, organisations reclaim up to 40 percent of operational capacity through process improvement alone. Before adding headcount. Before spending on technology. Before reorganising teams.

Just by finding what was broken and fixing it systematically.

That capacity becomes the fuel for growth. When your team is not spending a third of their week on rework, workarounds, and approvals that should not require a senior leader, they can take on more volume, serve customers better, and build things that actually move the business forward.

Symplicity Designs has delivered over a billion dollars in process improvements across more than 500 projects. That is not a headline we use lightly. It is the cumulative result of finding constraints, fixing them with rigour, and building the internal capability to keep going.

That is what disciplined scaling actually looks like. Not heroics. Not hustle. A repeatable process applied to the right problems in the right order.

Starting the Work

You do not need a perfect plan to start. You need a clear constraint and a team willing to look at it together.

The first sprint is usually the hardest because the habits are not there yet. People are not used to measuring their own processes. Leaders are not used to sitting in working sessions rather than receiving reports. The DMAIC structure feels slow compared to just making a call and moving on.

Then the results come in. The constraint moves. The team sees what the data showed and what the fix produced. The next sprint starts faster because everyone remembers what the last one felt like.

That is how transformation becomes culture. Not through a launch event or a values rollout. Through the repeated experience of finding a problem, solving it together, and seeing the numbers confirm what you built.

Symplicity Designs is an Atlantic Canada consultancy founded by Matt Symes. We combine Lean Six Sigma with Gen-AI workflow integration to help growing companies build the operational discipline that scaling a business requires. If your business is at $20M and you can feel the friction, we should talk. Visit symplicity.ca to start the conversation.

Frequently asked questions