Pull up any process document in your organization. Now watch someone experienced actually do that process. Count the steps they skip, add, or modify.
That gap is tacit knowledge. And it is the single biggest reason automation projects underdeliver.
Two versions of every process
SOPs document what people say they do. Tacit knowledge is what they actually do. These two things are never the same.
The gap between them is not sloppiness. It is expertise. It contains the workarounds people built because step four has been broken for two years and nobody fixed it. The decision rules that determine when you follow the standard path and when you don't. The quality checks experienced workers run automatically, without thinking. The risk signals that trigger a veteran to slow down while a newer person barrels through.
Think about a time when you trained someone new on a process. Remember all the things you said that were not in the manual? "Oh, and when you see this, always check that first." "Skip this step on Fridays because the data isn't updated yet." "If the number looks weird, call Sarah before you submit."
That is the real process. It lives in people's heads. And when those people leave, it walks out the door with them.
Why this matters before you automate
Here is where most organizations go wrong with AI and automation: they take the documented process, hand it to a development team, and build a system that follows the SOP precisely.
The system works. And it produces worse results than the humans did.
Not because the automation is bad. Because it is automating the wrong thing. It is running the process as documented, which was never the process that produced good outcomes. The good outcomes came from the undocumented judgment calls that experienced workers layered on top.
You cannot skip the extraction step. If you automate before you capture the real process, you are encoding mediocrity at scale.
One question that unlocks the real process
The practical method is simpler than people expect. Find the person who does it best. Sit with them. Don't ask "what do you do?" because they will recite the SOP back to you.
Instead, ask this: "Walk me through the last time this was tricky."
That single question changes the conversation. Instead of describing the ideal path, they tell you a story. And in that story, every decision they made that is not in the documentation is knowledge you need before you automate anything.
Have you ever tried this with your own work? Pick a process you run well. Describe the last time it almost went sideways. Notice how much of what you did in that moment has never been written down anywhere. That is the knowledge at risk.
The bottom line
Your documented process is a sketch. Your real process is a painting. The difference between them is the accumulated judgment of your best people. Before you automate, extract. Before you extract, listen. The expertise is already there. It has just never been in writing.