Index
Everything here, in eight sections. If you have a tool and no usable log, start with the event data section. If desktop capture is being proposed, read the task mining section before anything about technology.
All 51 notes
Grouped by section, each appearing once. Open a section for descriptions.
Foundations
6 notesTwo techniques, frequently sold together, using different data and carrying very different obligations. Plus the question that should be written down before any extraction.
The event log
7 notesMost of the difficulty in this field is producing a correct log. The case identifier and the activity vocabulary are the two decisions that determine what questions you can ask.
Discovery and analysis
9 notesThe 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.
Task mining
7 notesCapture on individual machines is surveillance of named people, with obligations attached. The bounded-study arrangement that makes it defensible, and the alternatives to try first.
From insight to change
6 notesMost analyses end as a report. The sequence that converts one into a modified process, and the honest test for an automation candidate.
Running it
5 notesA small part of an analysis is worth a schedule. Plus simulation, which is bundled with every tool and produces the least reliable output any of them offers.
The programme
7 notesChoosing the first process badly costs the programme its credibility before it has any. Plus what you can do with SQL and a pivot table before any licence.
Reference
4 notesCompliance frameworks and data protection pull in opposite directions and both apply. Plus the boundary: questions the log cannot answer, and what to use for each instead.