DM-17 Process mapping (flowcharts, swimlane diagrams, value stream maps)
Records the sequence of steps, inputs, outputs and responsible roles in a process and produces a flow diagram showing handoffs, delays and rework loops.
What it does
Records the sequence of steps, inputs, outputs and responsible roles in a process. Artefact: a flow diagram; read handoffs, delays and rework loops.
When to use it
Use when you need to see how work actually moves through a process and where it is delayed or repeated.
When it does not fit
The real work is not sequential or varies widely by case.
Result format
The result is a flow diagram of the process showing each step in sequence with its inputs, outputs and responsible role. It names the handoffs, delays and rework loops.
Requirements on the material
| Property | Requirement type | Requirement |
|---|---|---|
| Content type | Always applies | requires=text |
| Unit of analysis | Always applies | requires=topic |
| Appraises source credibility | Applies in some cases | no |
Not restricted on: Structure, Variable types, Time structure, How the sample was chosen, Level of detail available, Number of sources, Whether sources can be joined, Amount of material, Known data problems, Producer interest, Source dependence, Origin, Document genre, Language, Personal information, Security classification, Licence.
| Minimum material | Observation or interviews describing the actual steps, or documents describing the intended steps. |
|---|---|
| Additional sources needed | none |
| Not for (rules) | none |
| Not for (text) | The real work is not sequential or varies widely by case. |
Choosing and ordering
| Kind of technique | Primary technique, runs in step 5.3 |
|---|---|
| Phase tag | analyse |
| Other phase tags | frame |
| Kind of finding | pattern; risk |
| Question answered | what; why |
| Strongest statement it supports | describe |
| Needs as input |
|
| Makes as output |
|
| Must exist first | None |
| Loop target | return to gather |
Library checks by stakes
Each stakes level includes the checks of the level below it. Checks that need a person apply at high stakes only, so the process leaves them out at lower stakes (decision 38). Repeatability: judgement dependent.
| Stakes | Check | Person involved | Counts as a different method |
|---|---|---|---|
| exploratory | spot check | optional | no |
| decision-informing | spot check | optional | no |
| decision-informing | assumption and limitation statement | none | no |
| high-stakes | spot check | optional | no |
| high-stakes | assumption and limitation statement | none | no |
| high-stakes | expert review | needed | no |
| high-stakes | independent review | needed | no |
Failure modes and limits
| Model suitability | human judgement required |
|---|---|
| Typical model failure | Draws the intended process from policy documents and presents it as the actual process. |
| Error sources | input data; coder or rater judgement; language model |
| Certainty limits | Documents describe the intended steps and not the actual steps; observation or interviews are needed for indirectness to be low. |
Related techniques
- pairs with DM-18 Design structure matrix (dependency structure matrix): A dependency matrix shows coupled steps that a flow diagram hides
- pairs with AO-05 Customer journey mapping: Customer mapping adds the experience of the person using the process
Evidence and tag basis
Unconfirmed. No source was opened.
Tag basis: input profile inference; selection inference; sequencing inference; robustness inference. All tag values are inference unless a source is named.