Automatic Process Discovery
Last updated
Automatic process discovery maps how work runs by observing it, rather than by interviewing the people who do it or reconstructing it from system logs. The output is the best-outcome path plus every variation, kept current as execution changes.
What Automatic Process Discovery actually means
Manual discovery breaks for three reasons. Interviews capture what people believe they do, which differs from what they do. Workshops are expensive enough that they happen once, so the output is a snapshot. And documentation is stale almost immediately, because the real workflow drifts the next day while the diagram does not.
Automatic discovery replaces the interview with observation. Work is captured as it flows across applications, systems, and the ad-hoc tasks that sit between them, and resolved into processes without anyone describing them first. Because nothing is hand-maintained, the map does not have a shelf life.
What the output contains is different from a process diagram. It holds the best-outcome path and every variation actually in use, rather than one idealized route. It shows where work waits, where it loops back as rework, and where the real process has drifted from the documented one. And it updates as execution updates, so a question asked next quarter is answered against next quarter reality.
Discovery on its own is only the first step. A map that nobody acts on is a more accurate version of the diagram it replaced. The value arrives when the same evidence base is used to rank what to automate, to deploy against it, and then to verify whether the deployment changed the numbers it was supposed to change.
Examples
Discovery without a workshop
An operations team needs a current map of its invoice process across four systems. Rather than booking three weeks of interviews, the process is read from observed execution, including the steps performed in spreadsheets that no interviewee thought to mention.
Finding the variants
A process believed to have one standard path is found to have dozens in active use. Discovery surfaces which variants are common, which correlate with the best completion times, and which skip steps the standard treats as mandatory.
A map that does not go stale
A team reorganizes and two systems are replaced. Because the map is built from continuous observation rather than a one-time capture, it reflects the new shape of the work without a re-mapping project.
Frequently asked questions
Related terms
Process Mining
Process mining reconstructs how a process ran from the event logs that systems recorded. It is usually bought as the discovery phase of a larger program: find the inefficiencies, then redesign, automate, and measure.
Golden Path
The golden path is the variant of a process associated with the best outcomes, read from the distribution of how that process actually runs rather than from how it was designed. It becomes the reference way of operating and the route deployed agents follow.
Process Drift
Process drift is the gradual divergence between how a process is documented and how it is actually performed. It is why documentation goes stale almost immediately, and it is only visible against a baseline that keeps updating.
