AI Governance
Before you scope an AI feature, find the spreadsheet clinicians already use
A post in r/healthcareIT argues clinicians stick with spreadsheets because the workaround is faster than the new system, not because they lack training. That workaround is the best requirements document an AI feature will ever get.
November 13, 2026 · 5 min read

When clinicians keep a spreadsheet next to a system that already has the feature, the spreadsheet is usually faster, and speed beats features. That is the argument in a recent r/healthcareIT post titled "Your healthcare software has all the requested features. Why are clinicians still using spreadsheets?" The author's answer starts with a warning: "I'd be careful about assuming this is a training problem."
This is one practitioner's argument in one thread, not a study, and I am treating it that way. But it matches a pattern anyone who has watched software rollouts will recognize, and it has a direct consequence for teams about to add AI to clinical or operational workflows. If you scope an AI feature around the official workflow, you may be automating the path nobody uses.
The argument, in the author's words
The post describes a clinician who needs to update a patient record. The new system requires navigating several screens, filling unrelated fields, and waiting for confirmation. Then the line that carries the whole piece: "The spreadsheet takes thirty seconds."
The author grants that the new system may have better reporting and access controls. The point is that the daily experience can still be frustrating, and the software can technically support the workflow while completing the task takes longer than the workaround people already use. The fix the author proposes is observation, not retraining: watch the actual workflow with the people doing it, then prioritize changes that reduce friction without compromising safety, privacy, or auditability.
I agree with all of that. Where I want to take it further is AI scoping, because AI projects tend to make this mistake in a new way.
Why AI scoping repeats the mistake
Most AI feature ideas start from the system of record. Someone looks at the EHR, the scheduling tool, or the intake form and asks where a model could fill fields, summarize notes, or draft messages. That produces features that make the official path a little faster.
If the official path is already losing to a spreadsheet, a little faster may not be enough. The clinician still has to navigate the screens. The AI saves a few seconds inside a process that costs minutes, and the spreadsheet keeps winning. Then the adoption numbers come in low, and the instinct is the one the Reddit author warns against: schedule more training.
The spreadsheet tells you something the system of record cannot. It shows which fields people actually need, in what order, and which ones they skip. It shows what they track that the system does not hold at all. It is a requirements document written by the people doing the work, under real time pressure, with no product manager in the room.
Find the spreadsheet first
Before scoping an AI feature for a workflow, I would go looking for the workaround. The author's four observation questions are a good starting script, and I would use them as written:
- Where do people repeat information?
- Which steps interrupt their work?
- What do they do when the system is slow or unavailable?
- Which actions are essential, and which exist because of internal process assumptions?
Then add three questions of my own that matter specifically for AI:
- What is in the workaround that is not in the system? A column of free-text notes, a status the system has no field for, a running list of follow-ups. That gap is often where a model can help, because the data is unstructured and the system was never built to hold it.
- Who maintains it, and how often? A spreadsheet one charge nurse updates every shift tells you who the real user of any AI feature will be.
- What decisions does it drive? If people sort the spreadsheet to decide who to call first, that sort order is the logic an AI feature would be replacing, and you need to understand it before a model touches it.
The governance problem hiding in the workaround
There is a second reason to find the spreadsheet early, and it is less comfortable. A spreadsheet that tracks patients is a store of health information that probably sits outside your inventory, your access controls, and your audit logs. The Reddit author lists safety, privacy, and auditability as constraints on any fix. The spreadsheet itself often meets none of them.
That changes how an AI feature should be scoped. The target is a replacement that is at least as fast as the spreadsheet and sits inside the controls. Speed alone does not get you there. If the AI feature wins on speed but the spreadsheet survives because it holds one column the feature does not, you now have both: the new feature and the shadow copy.
So the scoping question for the first AI feature becomes concrete. Which spreadsheet will this retire, and what has to be true for people to stop opening it? If nobody can name the spreadsheet, the team has not looked yet.
What to do before the next scoping meeting
Pick the workflow your next AI feature is meant to improve. Spend an hour with two people who do that work daily and ask to see what they keep open next to the official system. Write down every column, every shortcut, and every reason they give for using it. Then write the feature's success measure as a retirement condition: the date the spreadsheet stops being updated.
If that date never comes, the feature did not fit the work, however good the model was. The Reddit author closes by asking readers for one workflow that looks simple on paper but becomes difficult in daily use. I would ask the same question of any team about to ship AI: which workaround are you planning to replace, and have you seen it?