What we miss when we talk about the spreadsheet that runs a rural ambulance service
What the ordinary version of this story reveals that the headline misses.
The bigger picture
Maintenance is a design decision, not an afterthought. A system that can be understood by the next person is usually worth more than a system with one more feature.
Look past the launch and the language of transformation, and a simpler question appears: who is doing the work when the attention has moved on?
“The useful thing is rarely the loud thing.”
The practical view
Small teams tend to adopt new tools more slowly than large ones, but they also abandon them faster when the promised benefit never arrives. The result is a shorter list of software that actually earns its place.
The measurement matters too. If the only thing being counted is speed, quality and maintenance tend to disappear from the conversation.
The open question
There is a difference between automation that removes a task and automation that hides a task. The first creates time. The second creates a new kind of checking.
The point is not to be certain. It is to leave the next person with a clearer view of the choices available to them.
What makes the spreadsheet that runs a rural ambulance service worth following is the gap between the promise and the practice. That gap is where the real work happens.