Menu

UX

Process Mapping

A practical UX and service design method for visualising a process from start to finish so teams can understand it, simplify it, and improve it.

How to use process mapping to make processes visible, identify inefficiencies and errors, and create clearer paths for improvement.

4 min read

What it is

mapping is a UX and method used to visualise the sequence of steps involved in completing a process.

It focuses on how activities flow from start to finish, including decisions, inputs, outputs, and .

Unlike , which often highlights roles and , mapping focuses on the structure of the process itself.

It is commonly represented using flow diagrams that show actions, , and paths.

The goal is to make visible, understandable, and easier to improve.

Process mapping is most useful when the team needs a clear view of how a process actually works before it can improve it.

When to use it

Use this method when you need on how something works.

It is most useful when:

You are analysing or improving a process
You want to identify inefficiencies or errors
You are documenting how a system works
You are aligning teams on a process
You are redesigning or simplifying workflows

It is less useful when:

You are focused on user experience alone
The process is simple and obvious
You need behavioural or emotional insight
Process mapping is often used alongside workflow mapping, task analysis, and service design.

Key takeaway

Use process mapping when the structure of the process itself needs to be made visible before you can simplify or improve it.

How to run it

Set up properly

Be clear on the boundaries and the level of detail. Process mapping is about business logic, so it needs a defined scope to stay readable.

Involve the people who run the . Maps drawn from procedure documents describe what should happen.

Run the method

mapping visualises a business process as a sequence of steps and decisions. It is more formal than and focuses on logic rather than on people.

  1. Define the start and end of the , and what triggers it.
  2. Map each step in sequence, at a consistent level of detail throughout.
  3. Identify the and the criteria applied at each. Undocumented decision criteria are where vary between people.
  4. Capture inputs and outputs for each step, including what information is required to proceed.
  5. Visualise the flow clearly, using a consistent notation so it can be read by people who were not in the room.

Pay attention to the . Steps are usually performed consistently; decisions are where the same produces different outcomes depending on who ran it.

Capture and make sense of it

The value comes from making logic explicit. After mapping, document:

  • The with its steps and
  • Decision criteria, including the ones that were previously unwritten
  • Exceptions and how they are currently handled
  • Steps that add no value and could be removed

Use this to find inefficiency and inconsistency, and as the basis for any or redesign.

What to look for

Focus on:

Decision points: the criteria applied, including unwritten ones
Decisions: points where paths diverge
Inputs: what is needed to start or continue
Outputs: what is produced
Flow: how the process moves

Where it goes wrong

Most issues come from:

If it’s not accurate, it won’t be useful.

Drawing it from procedure documents rather than from the people who run it
Varying the level of detail between steps
Leaving decision criteria unwritten, which is why outcomes vary by operator
Ignoring the exceptions, which are most of the real workload
Producing a diagram nobody uses to change anything

What you get from it

Done properly, this method gives you:

The process with its decision points made explicit
Criteria that were previously carried in people's heads
How exceptions are actually handled
Steps that add nothing and could be removed

Key takeaway

It helps you make processes simpler, faster, and more reliable.

Get in touch

If this sounds like something you need, we can help you map and improve your processes so they are clearer, faster, and easier to use.

No guesswork. No assumptions. Just clarity you can act on.

FAQ

Common questions

A few practical answers to the questions that usually come up around this method.

What is process mapping in UX?

It is a method used to visualise how a process flows from start to finish.

When should you use process mapping?

Use it when analysing or improving processes.

How is it different from workflow mapping?

Process mapping focuses on steps and flow, while workflow mapping includes roles and systems.

What does a process map include?

Steps, decisions, inputs, outputs, and flow.

Does process mapping improve UX?

Yes. It helps streamline processes and reduce friction.

Quick take

If you want to understand how a process actually works, step by step, map it clearly.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services.

Previous feedback

I had a fantastic experience working with Andy. One of his most impressive achievements during our time at NHS HEE was masterminding a deeply complex information architecture for a new platform that brought together a large number of legacy websites.

Will Parkhouse

Senior Content Designer