Simplicity is hard
Any time we discuss simplifying a workflow, the conversation gets stuck on edge cases.
That's not because the idea is bad.
To evaluate a simpler system properly, people are being asked to:
– hold the current system in their head
– imagine a new one they haven't lived in
– compare risks, trade-offs, and failure modes
– and a migration path from one to the other
If something is already complex, reasoning about it and a simpler version at the same time is even harder.
And if the overall picture starts to feel vague, people reach for what's tangible.
– What if that key person goes on vacation?
– What if we need to revert?
– We can't change this in the next four months because of X.
Those details feel productive, but they're often a sign of overload, not rigor.
You can't reason your way into understanding a simpler system you haven't experienced yet.
Once you see this pattern, a lot of “stuck” simplification debates start to make sense.
to be continued..