Strategy is Not the Problem: Overcoming the Operating Model Scaling Trap

The Growth Trap: When Scale Creates Mess, Not Strength

Many business leaders assume that getting bigger automatically makes a company stronger. In reality, growth often exposes internal problems that were easy to manage when the business was smaller.

Think about a founder who used to approve every important decision for a team of ten. As that team grows to fifty or a hundred people, that founder becomes a massive bottleneck. The informal handovers that used to work perfectly over coffee stop working entirely. New employees start relying on a few long-serving colleagues to figure out how things actually get done.

When this friction starts happening, the first reaction is usually reactive: hire more people, buy another software tool, or add another meeting. Sometimes that helps for a week or two. More often, it just adds another confusing layer to a way of working that was already unclear.

If you want to fix this permanently, you have to look at your operating model. By operating model, I mean the practical setup behind the business: how work moves, who makes choices, how teams coordinate, what tools they use, and how performance is reviewed.

Organizational chart vs Operating Model

You may rely on an organization chart, but traditional organizational charts only show reporting lines—who sits where and who reports to whom. It does not show whether the right information actually reaches the right person, whether teams have the power to make quick decisions, or whether customer complaints ever result in real changes to the way work is done.

The Three Questions to Check Your Operational Health

When looking at how a company is running, you can simplify the diagnosis down to three linked questions:

1. How does value move through the business?
2. How are decisions made?
3. How does the company learn and improve?

These three areas work as a single system. A company can have great people and a smart strategy, but execution will still fall flat if work gets stuck between departments, routine choices wait weeks for senior approval, or the same problems keep happening without anyone fixing the process.

1. How does value move through the business?

To answer this, choose one piece of work that matters to your customer—like onboarding a new client, completing an order, or delivering a project. Follow it from start to finish. Look closely at where it waits, where information has to be typed in more than once, and where it becomes unclear who is actually responsible.

A Quick Example:

In one project, a personnel application process was handling around 13,000 applications each year. The main issue was not a lack of staff. It was the way information moved between teams. Applications passed through several manual steps, handovers were unclear, and staff had to repeat basic checks and data entry.

By mapping the process from start to finish, the team identified which steps could be simplified and automated. A new workflow was then built in Power Automate to route applications, reduce manual work, and make ownership clearer. The new process cut the overall cycle time by around 50%, without adding more people.

The Rule: Organize your teams around how work is delivered to the customer, not just around standard departments.

2. How are decisions made?

Decision-making usually slows down as a company grows. The senior team often keeps the exact same authority they had when the business was tiny, even though the number of daily issues needing approval has multiplied. Teams end up being responsible for results, but they still have to ask for permission for routine, low-risk choices.

The Rule: Put routine decisions close to the actual work, and keep senior approval reserved for choices that carry real financial, legal, or strategic risk.

3. How does the company learn and improve?

Most companies track performance and look at dashboards. The hard part is turning that data into actual change. If a missed target, a repeated customer complaint, or a project failure gets discussed in a meeting but nothing changes afterward, you aren't learning—you are just reporting history.

The Rule: A review meeting is only useful if it directly changes a decision, a process, or a person's next action.

The Six Building Blocks of Your Blueprint

When you are ready to design a better way of working, you have to look at the business holistically. You can't just fix one piece in isolation.

Think about these six basic building blocks:

• Processes: The core workflows that create value. Map these end-to-end across the whole company, not department by department.

• Organization: The roles, teams, and decision rights. Everyone needs to know exactly what they own and what they are accountable for.

• Locations: Where work happens. Deciding what needs to be centralized, what should be local, and where people should sit to maximize speed or manage costs.

• Information: The software, data, and digital tools that support the work and keep everyone on the same page.

• Suppliers: Your external partners. Deciding what is critical to keep in-house and what makes sense to outsource to someone else.

• Management systems: The regular routines—like weekly reviews, annual budgeting, and performance tracking—that keep the company aligned.

If you fix a workflow but every minor issue still requires a VP's approval, the work will still move slowly. If you give teams the power to make fast decisions but give them poor data, they will make bad choices. The blocks have to fit together.

Where to Start: A Practical 4-Step Approach

You don't need to roll out a massive, risky corporate restructuring all at once. A much safer and more practical approach is to test the changes on just one customer journey or workflow first.

1. Step 1 - Map the friction: Pick one important workflow. Map it out and find exactly where the work slows down, gets stuck, or gets repeated.
2. Step 2 - Fix the decision rights: Clarify the choices around that workflow. Give the frontline team the power to handle routine issues without asking for permission.
3. Step 3 - Pick a few metrics: Agree on three or four simple measures that will show you whether your changes are actually making the work faster or better.
4. Step 4 - Test and adjust: Run this new way of working as a pilot. Fix the bugs in a small setting before you try to roll it out to the rest of the company.

When growth starts causing friction and things feel messy, the solution is rarely to tell your team to work harder. The real question is whether the way your company runs is still a good fit for the size it has become.