We put a broken process on a screen and called it progress.
We have spent heavily on going digital. The paper form became an app. The signature became a login. The filing cabinet became a dashboard. We announce each step as modernization, and on the surface it looks like one. But trace what actually happens to a request for help, and too often the same delays, the same handoffs, and the same dead ends are still there. We have not redesigned the journey. We have photographed it and put the photograph on a screen. The process that took six approvals on paper now takes six approvals online, slightly faster to route and just as slow to clear. We mistook the medium for the method, and we called the new medium reform.
This is not a story about teams who do not understand technology. The people building these systems are often skilled and sincere. The problem is structural, it is shared across the sector, and because it is structural it is ours to fix.
Why we digitize the wrong thing
The pull toward digitizing the existing process, rather than rethinking it, is strong and understandable. Redrawing a workflow means questioning who holds which approval, and that touches power, so it is far easier to leave the steps in place and simply move them onto a platform. A new system is also visible in a way that a streamlined decision is not. A dashboard can be demonstrated, screenshotted, and shown to the people who fund the work. A removed approval cannot be photographed. So the incentive rewards the tool that impresses over the change that quietly helps, and the structure, left alone, produces the screen rather than the fix.
There is a deeper reason underneath. A genuinely better process often means fewer steps, fewer sign-offs, and less of the control that makes the center feel safe. Digitizing the old process preserves all of that while looking like change. Everyone keeps their checkpoint, the work looks modern, and no one has to give anything up. The tool becomes a way to appear to reform without reforming, and it does so sincerely, one well-built feature at a time.
The cost lands where it always does. The person waiting for a decision does not experience the new system as progress. They experience the same wait, now behind a more polished surface, and sometimes a longer one, because a clumsy digital version of a bad process can be slower than the paper it replaced. Meanwhile the money spent on the platform is money not spent on the work, and the energy spent celebrating the launch is energy not spent asking why the journey was that long to begin with.
A faster route through a broken process is still a broken process, now with a login screen in front of it.
Technology that earns its place
None of this is an argument against digital tools, many of which genuinely help. It is an argument for making technology prove it removed friction rather than merely relocated it.
Redesign the process before you automate it. The honest first question is not which tool to build but which steps should still exist at all. A workflow worth keeping is one we would defend on paper. Automating before that test just locks the waste in place at higher cost. Fix the journey, then choose the tool that fits it.
Measure the tool by the person’s wait, not the launch. The test of a new system is whether the time from a need to a met need actually fell, and whether the person at the end found it easier. A platform that demos beautifully but leaves the wait unchanged has not earned its place, however impressive the interface.
Count the steps a tool removes, not only the features it adds. A useful question for any new system is what it let us stop doing. If the honest answer is nothing, we have added a layer, not improved a process. Subtraction is the real signal of progress, and it rarely shows up in a screenshot.
Build for the person at the door, not the funder in the room. The pull to impress the people who fund the work is real, and it bends design toward the visible. The discipline is to ask whether a feature serves the person waiting or the meeting where the tool is shown, and to favor the former even when it photographs less well. Funders carry the same interest in help that actually moves faster, and a shared honesty about what counts as progress is something we can build together.
None of this slows down real modernization. It points it at the thing that was broken rather than the thing that was visible. A tool that removes a genuine delay is worth every hour spent on it. A tool that decorates a delay is a cost we dressed up as a cure.
So the standard is simple. Before we celebrate a system, we should be able to name the step it removed and the wait it shortened for the person at the door. If we cannot, we did not reform the process. We digitized it, and digitizing a broken thing is a build we can choose to stop making.