Subtract

Most things get more complicated on their own. Features accrete, steps get added, processes grow a new exception every time something goes wrong. Nobody decides to make it complicated — it just happens, the way a desk gets cluttered, one reasonable addition at a time. Simplicity is the only state that takes active work to hold.

I say "most work is hard because we make it complicated" a lot. The part I don't say enough: un-complicating it is a skill, and it's mostly about subtraction.

Addition is easy, subtraction is scary

Adding feels like progress. A new feature, a new check, a new step in the process — each one is defensible, each one solved a real problem for someone once. Removing feels like loss. What if someone needs it? What if it breaks something? So things only ever get added, and the system slowly fills with stuff that no longer earns its place.

We're wired to fix problems by adding. The harder, better move is usually to take something away.

What I try to remove

Features nobody uses but everybody maintains. Steps in a process that exist because of one incident three years ago. The meeting that made sense when the team was half the size. The config option we added "just in case" that now has to be supported forever. Sometimes even people — the hire that would've made this quarter easier and the org permanently slower.

Every one of those has a reason it's still there. That's exactly why removing it takes more nerve than adding the next thing.

Default to less

So when something feels heavy now, my first question isn't what to add to fix it. It's what I can take out. Can this process lose a step? Can this product lose a feature? Can this decision get made once instead of re-litigated every week?

It's harder than adding, and it rarely gets applause — a thing that's no longer there is invisible. But it's most of how you keep a system fast and a company sane. Complexity comes back on its own. Subtracting is the part you have to do on purpose.