Process mapping a new service in five steps

Executive overview

New services fail not because the work is bad, but because the steps aren't defined. A process map externalises what you do so you can deliver consistently, onboard others, and spot gaps before they hit clients.

Four symbols are all you need: circle (start/stop), rectangle (step), diamond (decision), arrow (direction).

The goal is not to build something new — it's to capture what already exists and do it better.

The four symbols

• Circle: marks the beginning or end of the process
• Rectangle: one action or activity — one step per box only
• Diamond: a decision point where the flow splits into two paths
• Arrow: indicates direction of flow through the map

The five steps

1. Define the start and stop — identify the moment someone becomes a customer and the moment they stop being one
2. Map the steps in between — ask "what happens next?" repeatedly until you reach the end
3. Add decision diamonds for common forks (e.g. payment successful or not); skip rare edge cases
4. Layer on optimisation — add swim lanes, technology, ownership, or customer emotion once the core flow is solid
5. Convert to a checklist — extract every action step into a task template or printed checklist; exclude automated steps

Defining start and stop

• Start: when does someone become a customer? (payment, booking, contract signing)
• Stop: when does the service end? (final deliverable, last invoice, wrap-up email)
• This scopes the entire mapping session

Mapping steps and decisions

• Walk forward from the start, asking "what happens next?" at each point
• Use a decision diamond only when two materially different paths follow
• Map the normal path as the main line; branch edge cases off to the side
• Resist the urge to capture every unusual scenario — focus on what happens regularly

Layering and optimisation

• Once the core map exists, add a second dimension to optimise for a specific concern
• Swim lanes (horizontal bands) separate who does what — useful for clarifying client vs. internal steps
• Other common overlays: software used at each step, team ownership, customer emotional journey
• Reorganising an existing map is not building — it is process documentation

Converting to a checklist

• Extract every action step (not automated ones) into a task management template or printed list
• Digital tools: create a task with subtasks or checklists, save as a reusable template
• Non-digital: a Google Doc checklist printed per order works equally well
• The process map shows everything that happens — useful for client communication and onboarding
• The checklist focuses only on what requires human action