Marcus Andrey Study
Ler em português Library

Framework · Facilitation techniques · 3 min read

Journey mapping and service blueprints

Map stages, actions, pain points, systems and back-office processes, ideal for cross-domain operational flows.

1Stages

The big phases of one real scenario, left to right.

e.g. request, plan, execute, invoice
2Actions

What the user does in each stage, step by step.

e.g. "copies the order number"
3Pain points

Where it breaks, slows down or frustrates. Each one with evidence.

e.g. quote from interview 4
4Systems

The apps, screens and tools used at each step.

e.g. booking app, spreadsheet, email
5Back office

People and processes behind the scenes that the user never sees.

e.g. manual check by finance
6Owners

Which team owns each step, system or hand-off.

e.g. team B owns the invoice screen
A journey map shows what the user experiences; the service blueprint adds the systems and back-office layers below it.

Use it when

  • A process crosses several teams and apps, for example a booking process that spans several applications, and no single team sees the whole flow.
  • Each product team optimises its own screens, but users still lose time between them.
  • You need a shared picture of the current state before you prioritise improvements with product managers.

How to use it

  1. Pick one real scenario. Choose a specific user role and one concrete case, for example "a planner handles a rush order on a Friday". Use findings from Contextual inquiry or interviews. Output: one scenario in one sentence.
  2. Lay out the stages and actions. Write the big stages left to right, then the user's actions under each stage. Walk through it with people who do the work. Output: the top two layers of the map.
  3. Add pain points with evidence. Mark where the flow breaks, slows down or frustrates. Next to each pain point, note its source: a quote, an observation, a metric. Output: pain points you can defend.
  4. Add the systems layer. Under each action, write the apps, screens and tools used. This is where the journey map becomes a service blueprint. Output: the systems used at each step.
  5. Add the back office and owners. Below the systems, add the processes and people the user never sees, and which team owns each step or hand-off. Output: the full blueprint, with hand-offs visible.
  6. Pick the moments to fix. Circle the two or three pain points with the strongest evidence and the most hand-offs. Output: a short list for prioritisation. 60–90 minutes for the session.

Worked example

A UX lead maps "a planner handles a rush order" with designers from three product teams on an internal operations platform.

Layer Request Plan Execute Invoice
Actions Reads email from customer Creates order, checks capacity Updates status during the day Checks charges
Pain points Copies order data by hand (interviews 2, 4) Capacity is in a separate app (observed 5 times) No alert for changes (support tickets) Charges don't match the order (finance)
Systems Email Booking app, capacity app Tracking app Billing app
Back office None Capacity team confirms by phone Driver dispatch Finance checks rush fees manually
Owner No owner Team A, Team B Team C Team D

The map shows that the biggest losses are in the hand-off between team A's and team B's apps. The lead takes this into the next priorities session.

Watch out for

  • An average journey that nobody lives. Generic maps hide the real exceptions. Start from one real case and add others later.
  • Pain points without evidence. A map full of opinions starts arguments. Note a source for each pain point.
  • Stopping at the user layer. Without systems and back office, you see the symptoms but not why they happen across teams.
  • A map that nobody uses. Agree before you start which decision the map will feed.

Template

Copy this grid onto your board and fill one column per stage.

SCENARIO: (user role) + (concrete case) + (source of evidence)

               | Stage 1 | Stage 2 | Stage 3 | Stage 4 |
User actions   |         |         |         |         |
Pain points    |         |         |         |         |
  (evidence)   |         |         |         |         |
Systems        |         |         |         |         |
Back office    |         |         |         |         |
Owner (team)   |         |         |         |         |

Moments to fix (top 2-3):
1.
2.
Feeds which decision:

Books to go deeper

"See on Amazon" links are affiliate links. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.

Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close