All notes

The System That Needs Explaining Constantly Is Broken

If your process requires a standing meeting just to keep everyone aligned on how to use it, the process is the problem.

Good systems are legible. You can look at them cold — after a week away, after a new person joins — and understand what’s happening and why. The logic is visible in the structure itself.

Bad systems accumulate explanation. First it’s a Slack message. Then a doc. Then a weekly sync. Then an onboarding guide that’s already out of date. Every layer of explanation is evidence that the underlying thing doesn’t communicate its own intent.

This isn’t about simplicity for its own sake. Complex work is complex. But complexity that lives in the work is different from complexity that lives in the instructions for how to navigate your tooling.

Scott Andrew Alpaugh puts it plainly: if the system can’t speak for itself, you’re not running a system — you’re running a person who knows how the system works. And when that person leaves, so does the system.

The test is straightforward. Hand it to someone capable and step away. What breaks? What questions come back? Those aren’t user errors. That’s your system showing you where it failed to think ahead.

Fix the system. Stop writing another guide about the system.