Services / Process mining

The procedure describes what should happen. Mining shows what does.

Process mining reconstructs the real process from the event logs your systems already generate, exception paths, rework, and delays included, rather than from a self-reported description.

What one analysis found

The gap between the documented process and the real one is usually measured in money.

A recent proof-of-value session for a client uncovered three things nobody had a number for until the logs were mined.

55%

of invoices were paid too early, leaving €4.6 million of monthly working capital unoptimised.

2,000+

changes were made to orders every month, extending delivery times by two weeks.

€400k

in unpaid orders resulted in penalties and fines that nobody had traced back to a process cause.

Why organisations stall before they start

Most of the reasons teams give for not mining their processes are misconceptions, not blockers.

The event logs your systems already generate, the record of every timestamp, device, user, and outcome, are the backbone of process mining. The barrier is rarely the technology. It is what teams assume about their own logs before checking.

“We'd need fully integrated systems first.”

Process mining works from the logs individual systems already produce. Integration is not a precondition.

“Our logs are confidential.”

Logs record events, not the content of what was processed. Confidentiality concerns are usually a misunderstanding of what a log contains, not a reason to stop.

“We'd need complete, end-to-end history.”

A representative slice is enough to start. Waiting for a complete historical record delays a finding that could be available now.

Six misconceptions that stall process mining: integration misconception, log accessibility, awareness gap, confidentiality issues, log assumptions, historical data
The full list. What's above covers the three that come up most; these are the other three.
What a log actually is

Four components, recorded automatically, whether anyone reads them or not.

Every IT log, on-premises or in the cloud, records the same four things: what happened, when, who or what triggered it, and where it came from. That's the raw material process mining reconstructs the real process from.

Components of IT logging: activity outcome, event time, user involved, originating device or application
What every log entry actually contains.
Log management impact: cyber security, compliance, audit, disaster recovery, resiliency
The same logs already serve security, compliance, and audit. Process mining is one more use, not a separate collection exercise.
How it's commissioned

Pay for the transaction log volume you mine, not a standing contract.

Discovery, design, and mining can each run standalone. Mining typically runs first: a scoping call, the data or files, then a feedback session that names what the logs actually show.

Questions

Frequently asked questions

Do our systems need to be integrated first?

No. Process mining works from the logs individual systems already produce. Integration between systems is not a precondition.

Is this a one-off analysis or an ongoing capability?

It is commissioned by the transaction log volume you mine, not a standing contract, so it can run as a one-off proof of value or repeat as an ongoing capability.

How much historical data do we need?

A representative slice is enough to start. Waiting for a complete, end-to-end historical record delays a finding that could already be available.

Before the next redesign

Find out what your processes actually do before you decide what they should do instead.