Growth is supposed to feel exciting. Too often, it feels heavy instead.  More clients, more revenue…not to mention more meetings, more approvals, more “who owns this?” confusion. Leaders wake up one day and realize their business has become the very thing they used to complain about: slow, political, and bureaucratic.

The good news is this: bloat is not inevitable. You can scale operations deliberately instead of just bolting on new layers every time something breaks.

The hidden cost of “just add another step”

Most bloat doesn’t come from one big, bad decision. It comes from dozens of small ones:

• “Let’s add one more approval to be safe.”
• “Can you cc these three people so they’re in the loop?”
• “Let’s build a new spreadsheet to track that.”

Each decision is rational on its own, but the problem is that they rarely come with an expiration date.  Over time, you end up with:

• Workflows that require five people where two would do.
• Reports nobody reads, but everyone spends hours preparing.
• Tools that were useful once but are now just habit.

If you want to grow without bloat, you must treat process as something you actively prune, not something that accumulates by default.

Design from the outcome backward, not from the org chart forward

Bloated operations often mirror the org chart:

• Work passes through every department’s inbox.
• Handoffs are designed to make each team feel “covered.”
• The process is anchored in internal roles, not in the outcome you want for the client.

A better way is to start with the outcome and design backward. Ask yourself:

• What does a great outcome look like—for the client and for us?
• What is the minimum number of steps needed to get there reliably?
• Where do we truly need a control or approval, and where are we adding it out of habit or fear?

Then map the process with that in mind, and layer in only the governance that protects value or reduces real risk.

Standardize the 80%, not every possible exception

A classic trap I see too often:

“But sometimes we need to do it this way…”

“And in these cases, we need to do that…”

If you over-build your process for every edge case, you end up slowing down the 80–90% of work that is relatively straightforward. Typically, this is a better approach:

• Identify the common path—the journey that most work takes most of the time.
• Design a clean, standardized process for that path.
• Clearly define how to handle exceptions:
  • Who can approve a deviation?
  • What information do they need?
  • How is the exception recorded (simply)?

This lets you stay fast by default, while still being safe when you truly need to treat something differently.

Use automation to remove friction, not add complexity

Automation should feel like less work, not more.  You may have added bloat rather than efficiency if every automation you implement requires your team to:

• Enter the same data in multiple places,
• Remember dozens of rules,
• Or constantly fix what the system “almost” did,

Instead, look for automation that:

• Lives where the work already happens (inside your core systems, not in a parallel universe).
• Eliminates manual copy/paste, status chasing, and handoffs, rather than just logging more data.
• Is simple enough to explain to a new team member in a few sentences.

A good rule to follow: if you can’t describe what an automation does and why it helps on a sticky note, it’s probably too complicated.

Protect focus with clear decision rights

Bloat isn’t just a process problem; it’s a decision problem. Some key questions to ask yourself:

• Do people know who decides what?
• Are you routing decisions to the lowest appropriate level, or does everything bubble up?
• How many people can say “no,” and how many can say “yes”?

When decision rights are unclear, organizations tend to add:

• More meetings.
• More sign-offs.
• More “updates” to keep everyone comfortable.

Whereas simplifying decision rights:

• Frees up senior leaders to work on strategic issues instead of approvals.
• Gives managers and frontline staff a clearer sense of ownership.
• Reduces the need for constant check-ins and status chases.

Build in a “bloat review” every quarter

You will always be tempted to add. Very few people are rewarded for removing steps, reports, or tools.  Combat that by making “bloat review” a normal part of operating:

Once a quarter, ask:

• What steps feel useless or purely political?
• What reports do we create that no one reads?
• What approvals always get rubber-stamped?
• What tools overlap in functionality?

Then commit to removing or simplifying at least a few things each cycle. Over a year, this can make a dramatic difference in how efficiently your organization operates.           

Growth doesn’t have to feel heavy

Growing without bloat is less about heroics and more about discipline:

• Design from outcomes, not org charts.
• Standardize the common path and handle exceptions intentionally.
• Use automation to remove friction, not to impress anyone.
• Make it normal to prune, not just plant.

If your business feels heavier than it should for its size, the answer is rarely “more.” It’s almost always less, but better designed.

That’s exactly the kind of work I do to help owners and leaders at Obsidian North.

-Evan