The Leader’s Most Underrated Tool Is Subtraction

Look at how technology leaders usually get recognized. They launched an initiative. They stood up a new team. They brought in a new platform. They added a process to make sure “that never happens again.”

Now try to remember the last time a leader was celebrated for removing something.

It’s rare, and that’s a problem. Organizations are very good at adding and very bad at subtracting, so complexity only grows in one direction. Each addition makes sense. Taken together, they bury the teams that have to live with them.

Why we add

The bias toward adding isn’t a character flaw. It’s built into how organizations work:

Adding is visible. Subtracting is invisible. A new platform gets a launch announcement. A retired platform gets nothing, even though it may have freed up more capacity.
Adding feels safe. After an incident, adding a check, an approval, or a review step feels responsible. Taking one away feels reckless, even when the step never caught anything.
Adding is someone’s project. Removing is nobody’s. New things come with budgets and sponsors. Retiring old things comes with risk and no reward.
Every addition has a constituency. Someone fought for that process, that tool, that report. Removing it means a conversation nobody wants to have.

What subtraction looks like

Subtraction isn’t just turning off servers. Here are places leaders can take things away:

Meetings. Look at the recurring meetings in your organization. How many have a clear decision or output? Cancel the ones that don’t, and see who notices.
Approvals. I wrote in 2018 that if your approvals process takes longer than the change itself, it’s broken. That’s still true. Every approval step should be able to name a problem it actually caught. If it can’t, remove it.
Reports. Find out who reads them. Really reads them. Stop producing the rest.
Priorities. If everything is a priority, nothing is. One of the most useful things a leader can say is, “We’re not doing that this quarter.”
Tools and platforms. Two tools that do the same job is one too many. Pick one, migrate, and retire the other completely. Don’t settle for “mostly.”
Features. Products gather features the way attics gather boxes. Usage data will tell you which ones nobody would miss.

Subtract carefully

A word of caution. Before you tear something down, find out why it’s there. This is Chesterton’s Fence: don’t remove a fence until you know why someone put it up. Sometimes the annoying approval step exists because of an audit finding. Sometimes the odd integration is holding up a revenue stream. Subtraction without understanding is just another way to create risk.

So do the homework first. Then, once you understand why something exists and you’ve confirmed the reason no longer applies, remove it fully. Don’t leave behind a half-retired system that still needs care and feeding.

Make subtraction part of the job

If you lead a technology organization, here are a few ways to make subtraction normal:

Celebrate removals. Call out the team that decommissioned a system, killed a report, or simplified a process, in the same forum where you celebrate launches.
Pair every “add” with a “remove.” New tool? What does it replace? New process? What does it make unnecessary? If the answer is “nothing,” take a harder look.
Run a regular “stop doing” review. Once a quarter, ask each team what they’d stop doing if they could. You’ll be surprised how often the answer is something leadership could simply turn off.
Fund retirement. Decommissioning work needs real budget and real capacity, or it will lose to new features every time.

Anyone can add. It takes judgment, and a bit of courage, to take away. The leaders I’ve admired most were the ones who left their organizations simpler than they found them.