The Work Nobody Applauds

Ship a feature, launch a product, add a capability, and people notice. There's an announcement, a demo, maybe a round of applause. Removal gets none of that. When something disappears and things just work better, the reaction is silence. Or worse: someone asks why it took so long.

That asymmetry shapes behaviour.

Nobody Demos a Deletion

A launch has an audience. A removal has a changelog entry, if that. Take three approval steps out of a process and there is nothing to put on a screen: no before-and-after, no adoption curve, nothing that survives being described out loud. The person who added a dashboard has all of it.

Nobody set that up deliberately. It is what happens when you reward what can be pointed at. Over time the people who are good at simplifying learn that the work doesn't travel, and they either stop doing it or stop mentioning it. Both cost you the same thing.

Every Removal Has an Author

The process you want to cut was designed by someone who is still here, still senior, and still convinced it solved something. That is why the question stays unasked. The people who ask it anyway spend more standing than the change appears to be worth, and they only get to do it a few times.

Lao Tzu put it plainly: to attain knowledge, add things every day. To attain wisdom, remove things every day. The word decision comes from the Latin decidere, to cut off. Michelangelo didn't add marble to find the angel. He carved it away.

The most meaningful contributions tend to involve making something smaller and clearer, through the discipline of looking at what exists and asking whether it still earns its place.

That question is harder than "what should we build next?" Because "what should we build" has infinite answers. "What should we remove" has consequences.

The best quarter your team had was probably the one where three things quietly disappeared and nothing broke. Nobody wrote it down, including you. There was a launch that month, and it got the room.