Process Discovery Methods

Three complementary human-driven techniques for eliciting as-is process models (sources/2018-dumas-fundamentals-of-bpm, §5.2). Modelling method (§5.3) converts elicited knowledge into a process model in five steps.

Evidence-based discovery (§5.2.1)

Reconstruct the process from artefacts:

Documents (policies, manuals, forms)
System logs, transaction records
Observation on-site

Strengths: objective, free of recall bias. Weaknesses: artefacts lag reality; dark matter (undocumented workarounds) is missed.

Interview-based discovery (§5.2.2)

Iterative Interview → Modeling → Validation cycle (Fig 5.4); ≥2 iterations typical.

Traversal: backward (from outcomes) or forward (from triggers) — mix across interviews.

Per-interviewee checklist: input from upstream · decisions taken · output produced · resource it is forwarded to.

Balance per 1-hour interview: ~45 min structured (validate pre-formed hypotheses) + ~15 min free-form. Pure structured suppresses disclosure; pure free-form wanders.

Sunny-day pitfall: interviewees default to the normal path. Counter with rainy-day questions ("most difficult customer / case", "what if customer doesn't reply"), derived from the exception taxonomy: internal business / external business / internal technology / activity timeout.

Validation: translate the model back to natural language — don't show raw BPMN to domain experts.

See sources/2018-dumas-fundamentals-of-bpm-ch5-discovery for the full interview guide.

Workshop-based discovery (§5.2.3)

Roles: analyst + facilitator + process modeler + scribe. Effort: 3–5 sessions, ≤10–12 participants each.

Session 1: lightweight participatory modelling (sticky notes, no gateways).
Session 2: brief BPMN primer, then validate the consolidated model.
Hierarchy/regulation dampen openness — hand-pick participants.

Strengths: resolves conflicting perceptions fastest. Weaknesses: simultaneous availability; facilitation skill; politics.

Five-step modelling method (§5.3)

Identify process boundaries (start/end events, scope).
Identify activities and events.
Identify resources and handoffs.
Identify control flow.
Identify additional elements (data, exceptions, rules).

Strengths & weaknesses comparison (§5.2.4)

Method choice depends on: complexity, access to experts, documentation quality, time/budget, political context.

Practitioner complement: Sharp's scope-first approach

Alec Sharp (sources/2014-sharp-using-scope-models, sources/2014-sharp-whats-wrong-with-this-process) offers a consulting-floor complement to Dumas's academic framing:

TRAC scope model (Trigger · Result · Activities · Cases) before any flow mapping.
Process Summary Chart — a one-pager adding organisational functions to TRAC.
Stakeholder-lens question packs (customer / performer / owner) — directly reusable as interview prompts; see syntheses/interview-structuring-for-process-models §1.3.
Six Enablers diagnostic framework for final assessment — see concepts/six-enablers-framework.
90-minute facilitated session as a distinct cadence (vs Dumas's 3–5 workshop sessions) — see syntheses/qualitative-discovery-method-selection-matrix §7.

Alternative lens: Jobs-to-Be-Done (customer-side)

The methods above all take the performer / process-owner lens — they discover how activities are executed inside the organisation. Jobs-to-Be-Done offers a complementary customer lens: instead of "who does what?", ask "what progress is the customer trying to make, in what circumstance?" (sources/2016-christensen-jobs-to-be-done). Ulwick's ODI makes this operational with an 8-step universal job map and the Opportunity Algorithm for prioritising unmet needs.

JTBD competes with performer-lens interviewing when the deliverable is a product/service concept or redesign — it reframes the competitive set (Moesta's condo example: competing with "not moving", not with other condos). It complements BPM when the deliverable is a customer-facing process redesign: map the customer's job outside-in alongside the as-is process inside-out, and redesign the seams (cf. the SNHU case in sources/2016-christensen-jobs-to-be-done pp. 9–10, "Aligning Processes"). See frameworks/jtbd §"Relation to BPM discovery".

concepts/process-discovery · concepts/process-model-quality · methods/process-mining-basics · concepts/six-enablers-framework · entities/alec-sharp · frameworks/jtbd · concepts/outcome-driven-innovation