Systems > Noise
Most things that look like a people problem or a tooling problem are actually a systems problem. Here's how I tell the difference.
For more than fifteen years I’ve kept circling the same instinct: when something feels messy, manual, or unnecessarily fragile, there is almost always a better system hiding underneath.
The trap is that messy systems rarely announce themselves as systems. They show up as a person who’s overloaded, a tool that “doesn’t quite work,” a launch that slipped, a number nobody trusts. The temptation is to fix the symptom — add a person, swap the tool, push the date. The symptom comes back, because the system that produced it is still running.
A quick test
When something breaks, I ask three questions before touching anything:
- Would this still happen if the people changed? If yes, it’s structural, not personal.
- How many times has this exact thing happened before? Repetition is the signature of a missing system.
- What does the current “fix” assume will never change? Most fragile systems are just confident bets that the world will hold still.
If a problem survives all three questions, you’re not looking at noise. You’re looking at a system that needs to be designed, not patched.
Designing for leverage
Good systems are boring in the best way. They turn a recurring decision into a default, a manual step into an automated one, and a heroic effort into something the org can do on a Tuesday without thinking about it.
That’s the whole game: convert effort that doesn’t compound into structure that does. Every time you do it, you free up attention for the problems that genuinely need a human in the loop — and you stop paying interest on the same operational debt month after month.
The work isn’t glamorous. It’s plumbing, mostly. But the businesses that win quietly are almost always the ones whose plumbing is excellent.
Systems > noise. Build the thing that makes the next hundred decisions cheaper.