methodatlas
Operations

Process Mapping

Turns workflows, data, causes, and improvements into a tangible result by setting process boundaries, collecting steps, and deriving a target process.

Core question
How does the process actually run, who does what, where do waiting times and handoffs occur, and where are improvement opportunities?
MediumWorkshop1-3 h
Purpose

The method helps clarify workflows, data, causes, and improvements concretely. It identifies patterns, causes, bottlenecks, or constraints and derives actions. The result is captured as a process map, handoff list, and improvement backlog.

How it works

The team follows the steps: set process boundaries, collect steps, mark roles and handoffs, identify issues, and derive the target process. Each step is captured visibly. At the end, a process map, handoff list, and improvement backlog are available so decisions, tests, or actions can follow directly.

Visual orientation

Method sketch for a quick mental model.

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...

Flow

  1. 1Set process boundaries
  2. 2Collect steps
  3. 3Mark roles and handoffs
  4. 4Identify issues
  5. 5Derive the target process

The runsheet guides execution with 5 phases, timeboxes, 5 pitfalls, and clear stop criteria.

Open runsheet

Ideal for

  • Operations improvement
  • Service blueprint preparation
  • Compliance work

Not good for

  • Product strategy
  • Deep domain modeling alone

Deep dive

In detail

Process Mapping follows a clear working logic: set process boundaries, collect steps, mark roles and handoffs, identify issues, and derive the target process. This turns the method into a visible thinking process instead of only a discussion. Participants move step by step from raw material, observations, or options toward a shared structure. As a result, a process map, handoff list, and improvement backlog are available for decisions, learning, and planning.

Facilitation

Prepare a clear guiding question, the right information, and a visible workspace. Plan for 1-3 h with 3-10 people and use the format in a facilitated workshop. The facilitation needs structure and preparation; short timeboxes, visible intermediate results, and a parking lot for open questions are helpful.

Output artifacts
Process MapHandoff ListImprovement Backlog
Tags
Artifact templates
Process Mapping Working TemplateCompact working template for Process Mapping with process boundaries, handoffs, bottlenecks, and improvements.
canvas

process-mapping-working-template.md

Compact working template for Process Mapping with process boundaries, handoffs, bottlenecks, and improvements.

Process Mapping Working Template

Goal

Make the flow, handoffs, bottlenecks, and improvement opportunities visible.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Working area

  • Process boundaries:
  • Main steps:
  • Roles and handoffs:
  • Delays and bottlenecks:
  • Improvement ideas:

Output artifacts

  • Process map:
  • Handoff list:
  • Improvement backlog:

Open questions

  • ...

Next step

Owner, date, and success signal.

When to choose differently

Short decision aid for existing alternatives.

Value Stream Mapping

Statt Process Mapping, wenn du einen End-to-End-Fluss mit Wartezeiten und Verschwendung vermessen willst.

Similar methods

All methods