Every practice has a process diagram. Somewhere. In a shared drive nobody opens.
And then there's the workflow people actually run.
Here's one that lives nowhere on paper. A prescription gets sent, and the EMR opens a prior auth task. Fine, except it opens one every time a script goes out, whether or not that patient already has an active authorization on file. So the queue fills with tasks for auths that were approved weeks ago. Someone has to open each one, check whether it's real, and close the duplicates by hand.
Nobody designed that. Nobody approved it. It just started happening, and the team quietly absorbed it.
Ask where that step came from and you'll get a shrug.
Every practice has a dozen of these. The workaround someone invented three years ago and never wrote down. The "check with the front desk before you submit" that only works because one person remembers something the system doesn't. The report someone runs every Monday that nobody can explain the origin of.
This is the real workflow. Not the diagram. The diagram is what you meant to do. This is what you actually do.
And here's why it matters the moment you bring in automation.
AI learns the mapped process. It gets trained, demoed, and sold against the clean version, the one on the slide. The unmapped workflow, the phantom tasks and the tribal knowledge and the workarounds holding the whole thing together, is invisible to the vendor. It never shows up in the pilot, because the pilot runs on the diagram too.
So you automate the workflow you documented. And the workflow you actually run is still sitting there, unowned, now with a layer of automation on top of it that doesn't know it exists.
You can't automate a process you never mapped.
When was the last time anyone actually watched how the work gets done in your practice, instead of how it's supposed to?
Xillium helps surface and manage the work that documented processes leave out. What that looks like in practice is on our Solutions page.
