What is process mining, and does a small company need it?
Process mining is a way to see how work really moves through your company. It uses the dates and times your software already records and draws the route step by step, with the waiting time in between. A small company can use it as soon as a job repeats often and its steps are recorded in one place. It does not take a large project.
The idea in one example
A process is simply a job that is done the same way again and again, such as paying a supplier's invoice. Each time someone moves the invoice one step forward, the software notes what happened and when. For one invoice, the notes look like this.
| Invoice | Step | When |
|---|---|---|
| No. 1042 | Received | Monday 09:00 |
| No. 1042 | Checked | Monday 11:00 |
| No. 1042 | Sent for approval | Monday 11:05 |
| No. 1042 | Approved | Thursday 16:30 |
| No. 1042 | Paid | Friday 10:00 |
One invoice tells you little. Process mining puts the notes of several hundred invoices next to each other and shows what they have in common. Here the work itself takes a few hours. The wait for a yes takes three days.
What it shows you
- The real route. The way most cases go, which is often not the way everyone believes.
- Waiting time. How long cases sit between two steps.
- Repeats. Work that goes back a step and is done twice.
- Hand-overs. How many people touch one case.
How is it different from a report?
A report shows results, such as the number of invoices paid this month. Process mining shows the route between the start and the result. And it takes that route from what happened, not from what anyone remembers.
Does a small company need it?
For a long time mainly large companies used the method. Their records sat in many separate programs, and specialists had to collect and join them first. That effort is the only reason it looked like a subject for big companies. The questions it answers are the same with ten people as with ten thousand.
It is worth using when three things are true:
- The job happens at least a few dozen times a month.
- Its steps are recorded in one piece of software, not kept in emails and in people's heads.
- Someone is allowed to change the way of working once the picture is clear.
If the job is still rare, a talk with the three people involved is quicker. The method becomes useful from the moment a job has grown beyond what anyone can keep in their head.
Good jobs to start with
- From an offer to a paid invoice.
- From a customer's question to the answer.
- From a job application to a signed contract.
What to do with the result
Pick the single longest wait. Ask the people at that step why cases stop there. Change one thing, for example name a stand-in or remove a step. Then look at the picture again a month later.
How Worknano handles this
In Worknano every module writes to the same log of changes. So the record of who did what and when exists from the first day, and nothing has to be collected or joined. Process Mining reads it directly. It shows the full route of a case, the average and longest waiting times, the different routes, the slow spots, the repeats and the hand-overs, always within what each person is allowed to see. You turn it on once the workspace has enough history. When it finds a slow spot, it suggests an automation that you can approve, and the next run shows whether the number improved.
Create a free workspace and let your own records show where work waits.