Why did we stop asking a person to carry a file every morning?
Every morning, someone opened a portal, pulled a file, and moved it somewhere else. No one formally assigned this task. No one wrote it into a job description. It just happened — because if it didn't, the invoice sat in one system while the books waited in another, and the two never met on their own.
This is the kind of work that doesn't show up in a process audit. It lives in someone's muscle memory.
The file existed. The system needed it. A human was in the middle.
That's the whole story, really. Two systems that should have been talking to each other weren't. The invoice was generated in one place. The accounting side expected it in another. And the gap between them was filled by a person who showed up every day and carried it across.
Nobody asked her to do this. She did it because she understood what happened if she didn't — the books fell behind, someone made a call, things got messy. She was, in effect, the integration layer.
The problem with that arrangement isn't that people are unreliable. It's that this kind of work is invisible. It doesn't appear on a dashboard. It doesn't have a ticket. When she's on leave, no one knows to do it until something breaks.
What changed
We connected the two systems directly. The invoice now appears in the books by the time anyone looks. She stopped opening the operator portal — not because we told her to stop, but because there was nothing left to do there. The file was already where it needed to be.
That's the signal that the integration is working: the person who used to do the manual step quietly stops doing it, on their own, because the step no longer exists.
Where this doesn't work
Not every manual handoff is a pointless gap. Sometimes a person is in the middle because a decision needs to be made — not just a file moved. If the invoice needs to be checked, approved, or matched against something that lives outside any system, removing the human doesn't solve anything. It just hides the problem.
The test is simple: is the person making a judgment call, or are they moving data that could move itself? If it's the latter, the human is doing work that belongs to infrastructure.
What to do with this
Look at what your team does every morning before the real work starts. The small, quiet, procedural things — opening a portal, copying a number, forwarding a file. Ask whether any of it is purely mechanical: the same action, the same data, the same destination, every time.
If the answer is yes, the question isn't whether to automate it. The question is why it isn't automated already — and what it would take to close that gap.