How Discovery Works
What the algorithms do, the trade-off between fitting the data and staying readable, and why two tools give different maps.
Explainer
The discovered picture reflects the algorithm as much as the process. What each analysis shows, where it misleads, and how to report it so it survives challenge.
9 notes
What the algorithms do, the trade-off between fitting the data and staying readable, and why two tools give different maps.
Explainer
Every process has more paths than anyone expects. Which ones matter, and why the count itself is not a finding.
Procedure
Waiting usually exceeds working time by a wide margin. Locating it in the log, and distinguishing the four reasons it happens.
Procedure
Cases that go backwards. Invisible in aggregate reporting, substantial in the log, and always caused upstream of where they surface.
Analysis
Comparing what happened against what should have. Where deviations are compliance findings and where they are process design gaps.
Procedure
Who passes work to whom. Each handover adds a queue, and the pattern reveals coordination problems no process map shows.
Analysis
The overall map is an average of dissimilar things. Splitting it is where most findings actually come from.
Procedure
The systematic blind spots, what each conceals, and which of them justify task mining and which do not.
Reference
The most requested analysis and the most frequently wrong. What to normalise for before concluding anything changed.
Procedure