What is task mining?
Task mining is the observation of what people actually do at the desktop to complete a piece of work. It records the applications used and the keystrokes involved, capturing steps that leave no trace in any system log. It describes the same work that process mining examines, one level further down.
Why the steps nobody logs are the ones that cost most
Process mining and task mining are routinely treated as one exercise, which obscures the difference that decides what can be automated. Event logs record what the systems saw, so they are silent on the spreadsheet between two screens and the copying that keeps them aligned. That silent portion is frequently where the elapsed time and the error rate both live. Observing the desktop makes it visible, at the cost of a consent conversation that has to happen before any observation begins.
- Work performed outside enterprise systems leaves no event to mine.
- Rekeying between two applications is visible only at the desktop.
- Observation establishes how long a step takes a person in practice.
- Consent and scope have to be settled before any recording begins.
How task mining works
- The scope of observation is agreed with the people being observed.
- Desktop activity is captured as application context with user action.
- Actions are grouped into recognisable tasks across the applications involved.
- Repeated sequences are identified along with the effort each consumes.
- Findings are reconciled against the event log view of the same process.
- Candidates are prioritised by frequency and by the effort each would release.
How task mining is evaluated
Task mining is judged on whether its findings survive contact with the people observed. Examine the following before anything is scoped:
- coverage of the roles involved in the process
- share of observed time attributable to a recognised task
- variation in method between people performing the same work
- effort per task against the operator's own estimate
- proportion of findings confirmed in review with the team
Limitations, risks and common failure modes
- Observation changes behaviour, so the recorded method is the compliant one.
- Capture includes personal activity that no policy anticipated.
- Findings represent the people available to observe rather than the whole team.
- The most experienced operator is observed, whose method nobody else follows.
- A recording period excluding month end misses the work that matters.