The Executive Operating System 5 of 10 – Remove Before You Add

Thinking Pattern #5: Remove before you add.

After you spend enough time inside enough companies, you start to see the same pattern play out whenever performance slips or progress stalls. The organization introduces something new designed to “move things forward.” It feels like action, which is why it’s so common. Underneath it all sits an assumption that almost no one stops to challenge: if results are not improving, the organization must need more. But they already carry years of accumulated complexity that nobody ever bothered to remove.

Complexities (in no particular order) like:
Technology/tools – More AI and tech will solve all.
Obscure initiatives – A classic C-level reflex.
Task forces: Let’s temporarily rearrange jobs.
Dashboards – Don’t get me started.
Meetings – I mean, who doesn’t want more meetings, right?
Resources/hires – Overhead, excellent.
Campaigns – Because the ones we are running aren’t working, so abandon them instead of understanding why.

In reality, most organizations are not short on effort or ideas, and the instinct to add is understandable. It is also wrong most of the time because most organizations do not suffer from a lack of activity – it’s the accumulated complexity.

Over time, companies layer new things on top of old ones. New processes sit beside outdated ones. New tools duplicate capabilities that already exist. New reporting gets added without removing the reports nobody reads anymore. Nothing gets removed. Everything stays.

So what happens? Over-engineered systems slow down, decisions take longer, teams lose clarity, and energy spreads across too many priorities. At that point, leaders respond the same way they always have.

They add something else.

My argument here is that the strongest operators think differently. Before adding anything new, they remove what is slowing the system down.

Subtraction is not housekeeping. It is a strategy.

The fastest way to improve a system is often not to introduce something new. It is to remove the existing friction. Good leaders build things, but great operators simplify them since complexity compounds faster than capability.

If you do not actively remove things, the system eventually collapses under its own weight.

Why Organizations Rarely Subtract

Subtraction sounds simple. In practice, it is uncomfortable. Adding something signals progress, and it feels productive while creating visible motion.
Hence, we look really busy, but are we really producing anything of value?

Removing something forces questions like “Why do we still have this tool?” Or “Why does this report exist?” or “Why does this meeting happen every week?” Those questions challenge past decisions. They expose redundancy, and if you’re uncovering something good, they will make people defensive. So, naturally, organizations avoid them. Instead, they keep stacking new solutions on top of old problems.

This is how companies end up with multiple dashboards telling slightly different stories while working on dozens of initiatives competing for attention
and a technology stack where half the tools overlap. Wow, I just described a good portion of the clients I’ve worked with over the years.

The result is predictably laughable now because we’ve seen this movie, people. Its title is More activity and less clarity.

If you want to restore speed and clarity inside an organization, look for the things that quietly accumulated over time and remove them.

Subtraction Is Strategic Discipline

The strongest organizations are not the ones doing the most things but the ones doing a few things extremely well. That requires discipline. Every addition must justify its existence while every layer of complexity must earn its place. Otherwise, the system slowly slows down.

Growth rarely begins with addition. More often, it begins with removing the distractions and outdated thinking.