It’s easy to assume that faster is better. A quicker answer, a shorter process, fewer steps between question and decision.
Most of the time, that’s right.
But not always.
Some things take time for a reason, not because they’re inefficient, but because they’re designed to slow things down.
To bring in a different perspective, to test something that feels obvious, to give something a second look before it becomes a decision.
That can feel frustrating, especially when the answer seems clear from the start.
The instinct is to move around it, to simplify it, to get to the outcome more directly.
Sometimes that works, but often it creates a different problem.
Decisions made quickly tend to change quickly. They get revisited, reworked, replaced.
Not because they were wrong, but because they weren’t fully tested.
The slower version tends to hold. Not perfectly, but more consistently – it creates something people can rely on.
We see a version of this with clients. The parts of the process that feel slightly slower are usually the ones where the thinking is happening, where assumptions get challenged, where something that looks straightforward turns out to need a bit more care.
It doesn’t always feel efficient in the moment, but it’s often what creates confidence afterwards.
That’s the trade-off – speed feels good in the moment but stability matters over time.
Most of the time, the right answer sits somewhere between the two.