We keep waiting for the big reform. The summit that realigns the system, the new architecture, the strategy that finally fixes everything at once. Meanwhile the response we run today loses an hour here and a day there, a signature at a time, and almost none of us can see it happening. The grand fix never arrives, and the slow bleed never stops. We have trained ourselves to look for the dramatic change and to walk straight past the change that is actually within reach.
This is not a story about lazy people or bloated agencies. It is a story about friction, and friction is structural. It accumulates the way silt does in a riverbed, one reasonable deposit at a time, until the water that should move fast barely moves at all.
Where the time actually goes
Follow a single decision through a response and count the stops. A budget line needs reallocating, so it waits for a sign-off, then a second one for assurance, then a clarification because two systems define the same field differently. A field team files the activity it just completed in one report, then files it again in a second format for a different requirement, then a third time for an internal dashboard that feeds another dashboard. A task passes from one desk to the next, and at each handover a little context falls on the floor and someone downstream spends an afternoon picking it back up.
None of these steps is wrong on its own. Each was added by a careful person solving a real problem, usually after something went wrong once. That is precisely why they are so hard to see. Friction does not look like waste. It looks like diligence. It shows up in our reports as process, never as loss, so we keep paying it without ever counting the bill.
Friction does not look like waste. It looks like diligence. That is exactly why we keep paying it.
Why we wait for the grand fix instead
The honest reason we reach for the big reform is that the small one is unrewarded. Launching a transformation comes with a name, a budget, and a moment. Removing a redundant approval comes with none of that. Nobody is thanked for the form they deleted or the handover they collapsed into one. So the friction stays, not because anyone defends it, but because the incentive to remove it is so much weaker than the incentive to add. We optimize processes built for a situation that no longer exists, and we perfect systems we should have switched off.
There is a quieter cost too. When we treat change as something that only happens at the top, in rooms most of us will never enter, the people closest to the friction stop believing they are allowed to touch it. The duplicate report becomes weather. You do not fix the weather. You just carry an umbrella and file it on time.
The discipline of small, precise removals
The alternative is not a bigger plan. It is a standing habit of subtraction, treated as real work and given to real people. Change does not have to be a grand redesign. It can be a steady habit of removing what no longer serves, each removal modest on its own, compounding into a response that moves.
A few practices make it concrete.
Measure the journey, not just the result. For a decision or a payment that matters, count the steps it passes through and the days it takes. You cannot remove friction you have never measured, and the measuring alone tends to reveal stops no one can justify.
Give every removal a name and a permission. Make it someone’s actual job to find one redundant approval, one duplicate report, one needless handover, and to switch it off this quarter. Treat a removal as an achievement worth recording, the same way we record a launch.
Ask of each step whether it earns its place. For every sign-off and every required format, ask the plain question: if this did not exist, what would actually go wrong? If the honest answer is nothing, that is the signal to remove it.
Do it where you stand. The big reform belongs to rooms most of us do not control. The small removal belongs to all of us. A team that removes one piece of friction it owns teaches the organization more than another summit ever will.
We should be straight that these removals feel small in the moment, and that is the whole point. One removed approval saves a few days. One collapsed report gives a coordinator back an afternoon. Set beside the scale of the need, each looks almost too minor to mention. But friction compounds, and so does its removal. The same way a hundred small delays stack into a response that arrives late, a hundred small removals stack into a system that finally keeps its promises on time. The faster sector we keep asking for is not waiting on one heroic decision. It is waiting on a thousand quiet ones, and most of them are already in our hands.
So the test is not whether we can imagine the perfect new architecture. It is whether we are willing to remove one thing that no longer serves, today, and then another tomorrow. That is not a smaller ambition than reform. It is reform, done at the only speed that compounds.