methodatlas
Method guideOperations

Process Mapping

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityMedium
Time1-3 h
Participants3-10
FormatWorkshop
MaturityCanonical
Plan the work
01

Prerequisite

What needs to be finished first

Complete firstClear working frame

Choose one process with a clear trigger and end; invite people who perform it.

Without a bounded question or checkable evidence, the result will be unclear.
02

Preparation

What needs to be ready before start

Materials

Whiteboard or flowchart tool, process owner, frontline participants and relevant records or measurements.

People / roles

Process owner · frontline staff · facilitator/analyst · affected support roles.

Pre-read

Choose materials, data access and participants to fit the research or decision question.

Time needed

60–180 minutes for one bounded process; observation, data and redesign are separate.

Setup

Open the method-specific structure. Fictional examples are for orientation only; keep the blank worksheet separate from actual findings.

03

Core question

The one question this method answers

What happens from trigger to outcome, where do decisions and handoffs occur, and what evidence supports change?

04

Flow

Phases with goal, actions, output and pitfall

A process map shows actions, sequence, decisions, people, inputs and outputs so participants can understand and improve a workflow. Detail and notation depend on purpose.

Process Mapping working record

Fictional example

Method-specific prompts and a fictional worked example; template prompts remain empty.

Scope process and endpoints

Keep current and desired flows distinct.

**Scope:** Current flow from receipt to decision, from the service team’s perspective.

Capture actual steps and handoffs

Mark exceptions and loops.

**Map:** Receive request → check completeness → missing documents? → request and loop / assess complete request → notify decision.

Annotate waits and evidence

Label exceptions and hypotheses.

**Hypothesis:** Missing documents may cause rework; frequency is unknown in this fictional case.

Validate and choose next inquiry

Assign owner and review date to any change.

**Evidence:** Count requests for missing documents across a defined sample before proposing an intake checklist.

ASQ describes flowcharts as sequential process maps that may show actions, inputs, outputs, decisions, roles, time and measures.

Flowchart and process mapping | ASQ

  1. 1

    Scope

    Scope process and endpoints

    Goal

    Keep current and desired flows distinct.

    Inputs for this step

    • Choose one process with a clear trigger and end; invite people who perform it.
    • Whiteboard or flowchart tool, process owner, frontline participants and relevant records or measurements.

    Actions

    • Choose a real flow, trigger, outcome and perspective; label the map current state or target state.
    • Record Bounded process and perspective with its evidence status, source or open verification need.

    Output

    Bounded process and perspective

    Bounded process and perspective

    Quality check

    Is the mapped process clearly identified?

    Pitfall

    Observed and desired states are mixed. Label version, date and state.

    Timing: About 10–20 minutes; schedule data or clarification work separately.

  2. 2

    Flow

    Capture actual steps and handoffs

    Goal

    Mark exceptions and loops.

    Inputs for this step

    • Bounded process and perspective
    • Whiteboard or flowchart tool, process owner, frontline participants and relevant records or measurements.

    Actions

    • Work with participants to sequence actions, decisions, inputs, outputs and handoffs.
    • Record Validated draft flow with its evidence status, source or open verification need.

    Output

    Validated draft flow

    Validated draft flow

    Quality check

    Can performers confirm the path?

    Pitfall

    Only the official procedure is mapped. Walk through real or anonymized cases.

    Timing: About 10–20 minutes; schedule data or clarification work separately.

  3. 3

    Evidence

    Annotate waits and evidence

    Goal

    Label exceptions and hypotheses.

    Inputs for this step

    • Validated draft flow
    • Whiteboard or flowchart tool, process owner, frontline participants and relevant records or measurements.

    Actions

    • Mark timing, volumes or measures only with source and period; separate fact from interpretation.
    • Record Flow with evidence status with its evidence status, source or open verification need.

    Output

    Flow with evidence status

    Flow with evidence status

    Quality check

    Are problem claims observed, measured or assumed?

    Pitfall

    Anecdote becomes an established bottleneck. Add source, period and missing measurement.

    Timing: About 10–20 minutes; schedule data or clarification work separately.

  4. 4

    Review

    Validate and choose next inquiry

    Goal

    Assign owner and review date to any change.

    Inputs for this step

    • Flow with evidence status
    • Whiteboard or flowchart tool, process owner, frontline participants and relevant records or measurements.

    Actions

    • Review completeness with performers and state one focused improvement question or measurement.
    • Record Validated map and improvement task with its evidence status, source or open verification need.

    Output

    Validated map and improvement task

    Validated map and improvement task

    Quality check

    Are process owner and next action clear?

    Pitfall

    The map is treated as an approved policy. Mark changes as proposals and test them.

    Timing: About 10–20 minutes; schedule data or clarification work separately.

05

Artifact

What comes out at the end

Sketch: what the artifact looks like

Process Mapping · Step by StepMake process steps, roles, decisions, handoffs, and problem areas visible as a shared flow
Process MappingThe visual shows a process flow across swimlanes with trigger, activity, decision, system step, problem point, and output.Read flow, roles, and handoffs togetherProcess Mapping makes visible who does what, where decisions happen, and where work gets stuck.CustomerTeamSystemHandoffcheckyescompleteTriggerrequest comes inCapturecheck dataDecisioncomplete?Automatecreate ticketOutputapproved caseProblem pointwaiting for...
Form

Versioned record of question, evidence, result, uncertainty, owners and next review date.

Versioning / ownership

Track date, scope, sources, assumptions and changes; assign an owner and review for ongoing practice or initiatives.

Tool alternatives
  • Paper and pens
  • Whiteboard or simple table

process-mapping-working-template.md

Plan a session or initiative to match the actual scope of work.

Process Mapping: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Prepare the full method Time: 60–180 minutes for one bounded process; observation, data and redesign are separate.

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

  • Materials: Whiteboard or flowchart tool, process owner, frontline participants and relevant records or measurements.
  • Roles: Process owner · frontline staff · facilitator/analyst · affected support roles.
  • Advance information: Choose materials, data access and participants to fit the research or decision question.
  • Overall time needed: 60–180 minutes for one bounded process; observation, data and redesign are separate.
  • Setup: Open the method-specific structure. Fictional examples are for orientation only; keep the blank worksheet separate from actual findings.

Prepare for the work steps

Scope: Scope process and endpoints

  • Choose one process with a clear trigger and end; invite people who perform it.
  • Whiteboard or flowchart tool, process owner, frontline participants and relevant records or measurements.

Flow: Capture actual steps and handoffs

  • Bounded process and perspective
  • Whiteboard or flowchart tool, process owner, frontline participants and relevant records or measurements.

Evidence: Annotate waits and evidence

  • Validated draft flow
  • Whiteboard or flowchart tool, process owner, frontline participants and relevant records or measurements.

Review: Validate and choose next inquiry

  • Flow with evidence status
  • Whiteboard or flowchart tool, process owner, frontline participants and relevant records or measurements.

Process Mapping working record

Scope process and endpoints

Keep current and desired flows distinct.

...

Capture actual steps and handoffs

Mark exceptions and loops.

...

Annotate waits and evidence

Label exceptions and hypotheses.

...

Validate and choose next inquiry

Assign owner and review date to any change.

...

Blank worksheet contains prompts only, with no example data.

Flowchart and process mapping | ASQ

Scope: Scope process and endpoints

Expected artifact: Bounded process and perspective

Bounded process and perspective

Entry:

...

  • Is the mapped process clearly identified?

Flow: Capture actual steps and handoffs

Expected artifact: Validated draft flow

Validated draft flow

Entry:

...

  • Can performers confirm the path?

Evidence: Annotate waits and evidence

Expected artifact: Flow with evidence status

Flow with evidence status

Entry:

...

  • Are problem claims observed, measured or assumed?

Review: Validate and choose next inquiry

Expected artifact: Validated map and improvement task

Validated map and improvement task

Entry:

...

  • Are process owner and next action clear?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/process-mapping/run-sheet

06

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

process-mapping-beispiel.md

Concrete filled scenario, fictional example

Fictional example: reimbursement request

Scope: Current flow from receipt to decision, from the service team’s perspective.

Map: Receive request → check completeness → missing documents? → request and loop / assess complete request → notify decision.

Hypothesis: Missing documents may cause rework; frequency is unknown in this fictional case.

Evidence: Count requests for missing documents across a defined sample before proposing an intake checklist.

Validation: Staff confirm exceptions, decisions and handoffs.

07

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

  1. Scope process and endpointsObserved and desired states are mixed.View in phase
  2. Capture actual steps and handoffsOnly the official procedure is mapped.View in phase
  3. Annotate waits and evidenceAnecdote becomes an established bottleneck.View in phase
  4. Validate and choose next inquiryThe map is treated as an approved policy.View in phase
08

Stop criteria

When to pause, resolve prerequisites, or choose another approach

If performers cannot validate the current state, collect observations before recommending redesign. Keep current facts, future proposals and measured performance distinct.

Method after Praxisgemeinschaft. The method emerged as a widespread practice and is not clearly attributed to a single originator or organization. Curated with 1 sources.

Sources: Flowchart and process mapping | ASQ

Flow, timeboxes, and pitfalls are editorially curated practice recommendations based on the listed sources.

Where to go next?

A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving

Carries a problem point visible in the map into structured problem solving.

Paper illustration for Standard Work Analysis.
Operations
Standard Work Analysis

Checks whether the validated flow still matches the current standard.

View in playbookImprove Service ExperienceMove from visible pain points to frontstage, backstage, and ownership improvements.

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

Go to profileMore methods