A bad tool fails quietly. It lets you route around the gap, patch it with a spreadsheet, a sticky note, a verbal agreement with the person two desks over. Everyone adapts. Nobody complains. The workaround becomes permanent infrastructure, and six months later no one remembers it was ever a workaround at all.
A good tool fails loudly, right at the point where the failure happens, in language a person can act on. It doesn’t let you quietly compensate for its own weakness. If something’s missing, it tells you. If a process breaks, it breaks visibly, not three steps downstream where someone else has to reconstruct what went wrong.
This is the real test of process design: not whether it works when everything goes right, but what happens the first time it doesn’t. Systems that hide their failure points accumulate debt nobody can see until it’s expensive. Systems that surface failure early stay cheap to fix, because the fix happens close to the cause.
Most organizations don’t choose bad tools on purpose. They choose convenient ones, and convenience quietly becomes the thing that absorbs every small failure without ever reporting it upward. That’s how a company ends up with four versions of the same document and no one sure which is current.
Good process isn’t the one with the fewest steps. It’s the one that tells you the truth about where it’s breaking, as soon as it breaks. Everything else is just a more comfortable way of staying in the dark.