Two ways to investigate a process
Process mapping captures activities, responsibilities and decisions through discussion, observation and records. ASQ describes process-analysis tools as ways to understand and evaluate how work is performed. [1]
Process mining examines recorded events to discover process patterns or compare observed activity with an expected model. The IEEE Task Force describes discovery and conformance checking among its applications. Its manifesto emphasises the quality of event data. [2] [3]
Start with the evidence you have
Mapping is useful when the team needs a shared understanding, when important work happens outside systems, or when the process boundary is unclear. It can expose phone calls, judgement and informal handovers that leave little digital evidence. A workshop map should still be checked against actual practice.
Mining becomes useful when event records can reliably connect cases, activities and timing. An order, shipment and order line are different objects; selecting one as the case can change the apparent flow. Check identifier relationships, timestamp meaning, time zones and event coverage before interpreting a picture produced by software.
Use the methods together
Illustrative example: a map shows order approval followed by release and dispatch. Event analysis reveals repeated approval loops for a subset of orders. Observation then finds that incomplete information is prompting those loops. That is a hypothesis to test, not an automatic causal conclusion from the event pattern.
SCP would use a map to define the boundary, inspect a sample of source events, and review the patterns with the people doing the work. A recorded gap may represent real waiting, delayed data entry or missing events. Each explanation implies a different response.
Choose a proportionate starting point
| Situation | Useful starting approach |
|---|---|
| Unclear responsibilities or extensive offline work | Map and observe the process with users. |
| Repeated variants across many recorded cases | Assess event quality, then mine and investigate patterns. |
| A new target workflow | Design the process and acceptance criteria before testing it. |
| An apparent software bottleneck | Check operational causes and data timing before purchasing another tool. |
Turn the finding into a controlled change
Assess one flow, such as order release or warehouse replenishment. Agree the baseline, investigate the priority causes and test a change against service, lead time and total cost. Retain the evidence behind any conclusion and the owner of the follow-up.
An Automation Readiness discovery workshop can assess whether process analysis, event analysis or another method is appropriate. It should help clarify the operating problem before equipment or software selection, with specialist mining tools considered where justified.
Sources and evidence notes
Sources checked on 17 October 2026. Research findings and company reports are attributed above; practical recommendations are SCP’s interpretation. The examples do not imply endorsement, partnership or SCP client results.
- ASQ: Process analysis tools ↗
Undated reference page; reviewed 17 October 2026. Professional-body explanation of process-analysis methods; not a comparative trial.
- IEEE Task Force on Process Mining: Process Mining Manifesto ↗
Published in BPM 2011 Workshops proceedings, 2012; reviewed 17 October 2026. Foundational research-community guidance; not a current software comparison or a promise of savings.
- IEEE Task Force on Process Mining: overview ↗
Current overview reviewed 17 October 2026. Research-community explanation of discovery, conformance checking and related methods.
Explore the industries and services
Explore the next step
Discuss a defined supply-chain challenge and agree the evidence needed for a useful decision.
Workshop format and any fees are agreed before booking. Follow-on work requires a separate scope and business agreement.