Process mining in 2026: comparing the official procedure to the work actually carried out

The “Process mining” subject must lead to proof, not just to deployment: the expected effect must be measurable and reversible.
Frame the “source events” point, control the “case identifier” point, then decide with an explicit baseline measure.

1. Key figures

These benchmarks limit the decision to a diagnosis by process traces; they don't take it for you. A published value describes a precise perimeter, a date and sometimes a population different from yours. Read it as a constraint to be tested, not as the promise of an automatic effect. The context requires the proof.

Between two reviews, the local verification can be reproduced: for this subject, the first source leads to the following operational reading: “The purchase price is not enough to compare two technological options. » The second reference in the table must also be compared to your perimeter and a local measurement. This distinction between external reference and local measurement protects the analysis against easy extrapolations.

2. Read the sources without overinterpretation

Once the baseline is established, the threshold has an owner: a source is useful when a reader simultaneously understands what it asserts, the scope it covers and the limit of extrapolation. The five benchmarks below are therefore reread as decision markers, never as causal promises.

For the scope “a diagnosis by process traces”, external data can only be used to decide if its scope, its date, its unit and its limit are explained. The review should separate what the source establishes, what the team infers, and what a local test still needs to demonstrate.

Concretely, the proof sheet preserves the organism, the title, the URL, the date of consultation, the population, the unit, the method and the reservation of interpretation. It then indicates the decision that the benchmark informs and the local observation capable of contradicting this benchmark. In this file, attach this register to “source events” and entrust its review to “General Management”. Data without a documentary owner ages silently; data with a revision condition remains controllable and can be cited without losing its context.

2.1. Benchmark 1

GOV.UK — Choose the right tools and technology documents “4 obligations”. The exact range is shown in the previous table; keep it when comparing this data to your own operations, populations and periods. The answer depends on the cycle.

2.2. Bench 2

GOV.UK — Commercial off-the-shelf products provide the indication “2 phases before engagement” here. This information informs a choice; it does not, by itself, demonstrate that the same effect will appear in your context. Exceptions reveal maturity.

2.3. Bench 3

The GOV.UK reference — Working with contractors publishes “5 evidence”. Before making a decision, check the date, the population covered and the possibility of replicating the measure locally. The risk is concrete.

2.4. Benchmark 4

The source GOV.UK — Digital, Data and Technology Playbook locates the terminal “3 output assets” in the “digital purchases and contracts” field. It provides an external reference to the diagnosis; it does not replace either a local reference measurement or the analysis of exceptions. The threshold remains explicit.

2.5. Bench 5

The “5 key roles” milestone, published by GOV.UK — What each role does, falls under the “digital product and services teams” scope. It helps to formulate a testable hypothesis, without transforming an external value into an automatic objective. The average can deceive.

3. Reusable citation sheet

Apart from the nominal scenario, the sample remains representative: a robust quote must be able to be repeated without losing its author, its date, its scope or its limit. The sheet below isolates these elements and links them to a specific decision; it prevents a correct figure from becoming misleading after extraction from its context.

4. Introduction: framework the primary risk

The subject seems technical until the first contested arbitrage. The points “source events”, “case identifier”, “frequent variants” and “field validation” nevertheless belong to the same decision path.

The concrete risk takes the following form: a spectacular map that ignores log quality and human context. This problem cannot be corrected either by an activated option or by an additional dashboard; it requires a perimeter, a person responsible and contradictory proof.

When a dependence changes, the hypothesis can be contradicted: our position is therefore clear: the system only has value if the announced effect is observable. The comparison must relate to the situation before the change, then to the same segments after the test. The perimeter is authentic.

5. Actors and responsibilities

This distribution avoids confusing execution and responsibility. The first operational responsibility falls to the “General Management” function; the “Professionals” function provides separate control. The decision is only defensible if each actor knows what it measures, what it authorizes and what it takes back when the accepted limit is crossed. The compromise appears clearly.

6. Definition: process trace diagnostics

In this guide, the scope “a diagnosis by process traces” combines the points “source events”, “case identifier”, “frequent variants” and “field validation”. The objective is to obtain observed variants linked to their cost and their cause; the decision is based on the time and recovery per process variant.

At the next milestone, the rights of action are documented: the definition is therefore operational: it names the components, the desired effect, the indicator and the limit. A reader can quote it without having to reconstruct the meaning from the rest of the page. The decision can be reviewed.

7. Why the subject becomes structuring

If the measurement diverges, operations can resume: the sources converge on three terminals: 4 obligations, 2 phases before commitment and 5 proofs. They do not describe a universal average; they specify thresholds, obligations or operating conditions. In the present case, the third source leads to the following operational reading: “Transfer capacity counts as much as delivery capacity. »

This reading transforms the figures into decision questions: what perimeter do they cover, what uncertainty remains and who can act when the measurement goes beyond the accepted threshold? On a process trace diagnosis, this responsibility conditions the desired effect. The measurement precedes arbitrage.

8. Compare four levels of engagement

Concerning a process trace diagnosis, the comparison does not indicate a universal winner. It makes visible the cost of an absent proof, an overly simple driver or a premature extension. The right level depends on the criticality of the flow, the quality of “case identifier” and the concrete possibility of resuming “field validation”. The roles are distinct.

9. Recommended methodology: seven verifiable steps

Applied to a process trace diagnosis, the following method is part of good public and operational practice. It is not presented as a proprietary method of Logiks: its value comes from the order of controls and the possibility, for a third party, to verify each deliverable.

9.1. Formulating the decision

The work consists first of describing the expected result and relating it to “source events”. Do not retain an ideal demonstration or an overall average: observe the truly open decision and the value that justifies it. The useful deliverable is a memo cadrage which names the decision, the limit and the person responsible.

9.2. Measuring the starting point

On the critical path, the next deadline is planned: at this stage, the decision indicator must be observed before any modification. Involve the person who handles the exceptions, then compare the result to the initial situation and its variations between segments. You must be able to provide an initial measurement, dated and broken down by useful segment, to a decision-maker absent from the project.

9.3. Trace Critical Path

The action here is to link “case ID” to the relevant data, teams, and dependencies. Run the check on a normal case and a degraded case, keeping the exceptions encountered by the teams operating the device as a criterion. The concrete output takes the form of a map of exceptions, dependencies and owners.

9.4. Laying down safeguards

This step transforms intention into control: framing “frequent variations” with limits, rights and a recovery procedure. Measure what actually changes in boundaries, action rights, and rollback ability, including human takeovers. Document everything in a control matrix that makes cost and reversibility visible.

9.5. Test the difficult case

To move forward without hiding the deferred cost, you must test “field validation” in a representative scenario, then in a degraded scenario. Compare before and after on the nominal behavior, the failure caused and the quality of the recovery, then have an account of the nominal scenario, the failure and the human recovery reread by an actor who did not design the test.

9.6. Build evidence

With incomplete data, the stopping rule is known: expected action: compare result, errors, interventions and full cost at the starting point. Start on a perimeter where the team can still get back. The expected proof relates to the discrepancy between the initial promise and the recorded facts; record it in a file of logs, deviations and decisions that can be read by a third party.

9.7. Decide and Review

Without a designated owner, exceptions are logged: the work consists of first assigning the review and tracking the metric according to an explicit cadence. Do not retain an ideal demonstration or an overall average: observe the threshold that triggers a correction, an extension or a stop. The useful deliverable is a review rule with correction and stopping thresholds.

10. Logik tips: proof, mastery and reversibility

Our priority is the following risk: a spectacular map that ignores log quality and human context. Start where this fragility already produces an expectation, a loss, or a contested decision; the prestigious perimeter can wait.

From the first test, the residual risk is accepted: keep the reference measurement at the level where a team can act. A quarterly average does not replace an observation by course, by cohort or by type of exception; the marker must remain actionable.

Treat “source events” as a documented decision. A manager, a hypothesis, a limit and a review date are better than an adjustment whose origin no one knows.

Test “frequent variants” with “field validation”, then with a degraded recovery. The test should reveal operation and operating cost, not just confirm that the demonstration holds up.

Only extend the system if the observed facts support the desired effect and if “case identifier” remains controllable by a person outside the project.

In this file, the recommendations express a judgment of sequence: make the risk observable, test the hypothesis relating to “frequent variants”, then commit the resources. Sophistication comes after the demonstration of the announced effect; it does not replace it. These mistakes are costly.

11. Decision grid

The grid does not automatically produce arbitrage on a process trace diagnostic. On the other hand, it forces teams to show their hypotheses on “source events”, their thresholds and their responsibilities; a disagreement is then explicit and can be resolved. Control remains human.

12. Frequent errors

12.1. Consolidate activation and result

Enabling “source events” does not prove that the expected effect is achieved. This error shifts the debate towards the tool while the decision concerns an observable change.

12.2. Optimize the first available indicator

During the audit, the trace remains auditable: a convenient proxy can progress while the decisive measurement deteriorates. Link each signal to a decision and a guardrail.

12.3. Ignore exceptions

Depending on the hypothesis adopted, the convincing element remains linked to the decision: the nominal path often masks the fragility described above. Test a borderline case, a failure and how the team regains control.

12.4. Leave an addiction without an owner

When “case identifier” is everyone’s responsibility, no one decides the incident or the cost. Assign the decision before deployment.

12.5. Present risk as a formality

Documenting “frequent variants” without correcting the system produces facade conformity. The record must show a check performed and its result.

12.6. Extend without exit rule

If “field validation” does not allow a decision to be made, the pilot continues by inertia. Set continuation, correction and termination thresholds in advance.

13. Action Plan 30 / 60 / 90 days

13.1. Days 1 to 30: establishing the starting point

• describe the decision, the scope and the person responsible for it;
• record the initial value of the indicator before any modification;
• inventory dependencies and their exceptions;
• write the main risk and its detection condition.

On the business side, the initial value remains accessible: the first phase serves to make the disagreement visible. At thirty days, management must know the baseline measurement, the missing data and the specific case on which progress will be judged.

13.2. Days 31 to 60: testing the critical path

• implement primary control over a representative flow;
• test the recovery in a normal then degraded situation;
• record errors, human interventions, delays and costs;
• compare the observations to the initial scenario.

Under real constraints, the incident is subject to review: this pilot does not only seek to demonstrate that the technology works. It must establish whether the system advances the selected indicator without shifting a disproportionate burden towards the operation, users or a supplier.

13.3. Days 61 to 90: decide and organize the continuation

• consolidate the evidence and have its limitations reread;
• assign each recurring control to a named function;
• confirm the next review date and discharge procedure;
• extend only if the facts support the effect initially announced.

During the cadrage, human recovery is tested: at ninety days, the initial hypothesis must be demonstrated or refuted. Three decisions remain legitimate: extend, correct or stop the perimeter; continuing without a threshold does not constitute a fourth option.

14. FAQ

14.1. How to define a process trace diagnosis?

This is a decision framework applied to a process trace diagnosis. The approach links “source events” to “frequent variants” and “field validation” controls, with a reference measurement, those responsible and an exit rule.

14.2. What to start with?

After an incident, the source date is checked: start with an actual decision, a baseline measurement and a previously observed manifestation of the main risk. The tool comes after this cadrage.

14.3. What budget should be retained?

At each check, the observed field remains stable: add preparation, integration, operation, control, training, incidents and exit. Compare this full cost to the expected value, not just the license or campaign price.

14.4. How long should the test last?

The test must cover a complete measurement cycle and at least one exception related to “frequent variants”. Its duration derives from this observation, not from an arbitrary standard.

14.5. When to scale?

Scale up when progress remains stable, “field validation” is controlled and responsibilities, costs and exit conditions are documented.

15. Conclusion

In current operation, the scope remains explained: the decision is solid when a common measure links the technical, business and financial choices. The number of options activated is less important than the ability to explain discrepancies, deal with exceptions and reverse a choice that has become costly.

The pivot is simple: the project “a diagnosis by process traces” must no longer be a project to be delivered, but a capacity to govern to produce the announced effect. Nuance matters here.

16. Main sources

• GOV.UK — Choose the right tools and technology — consulted on 11 July 2026 — public digital services, transposable principles.
• GOV.UK — Commercial off-the-shelf products — updated on July 4 2025 — purchasing digital products and services.
• GOV.UK — Working with contractors — accessed 11 July 2026 — digital services teams.
• GOV.UK — Digital, Data and Technology Playbook — accessed on 11 July 2026 — digital purchases and contracts.
• GOV.UK — What each role does — accessed on 11 July 2026 — digital product and services teams.