How to Create a Process Map in One Afternoon

To create a process map, pick one process, write down what starts it and what ends it, then have the people who do the work walk through one real case while you draw each step. Mark the handoffs, the waits and the points where someone types the same thing twice. You can do all of this in one afternoon with paper, sticky notes and three to five people.

Most guides to process mapping are written for large companies and Six Sigma projects. This one is for a small business: one process, a few honest people and about three hours.

Key takeaways

• A process map is a picture of how one piece of work really runs, from trigger to result.
• Map one process, with a clear start and end, and use one real recent case rather than the ideal version.
• Five symbols are enough: start/end, step, decision, wait and document.
• The value is in what you mark: handoffs, waiting, rework and manual re-typing.
• Copy the template below, then use the map to decide what to fix, remove or automate.

What is a process map and what is it for?

A process map is a diagram of the steps in a piece of work, in order, from the event that starts it to the result that ends it. It shows who does each step, which tool they use and where the work waits.

It is closely related to a flowchart. Flowcharts are standardised: Wikipedia's summary of the ANSI and ISO symbols lists an oval for the start or end, a rectangle for a process step, a diamond for a decision and arrows for the order. A process map uses the same symbols but adds what a business cares about: people, tools and time.

Why map at all? Nobody sees the whole process, because each person knows only their part. A three-day delay between two steps is easy to miss when each step feels fast. And you cannot delegate or automate what you cannot describe: if you plan to hand a process to a tool or a new hire, the map is the brief.

Larger methods go further. The Lean Enterprise Institute describes value-stream mapping as diagramming every step in the material and information flows needed to take a product from order to delivery, with data such as cycle time. That depth suits a factory. For a small service business, a paper map is usually enough.

Before you start: pick one process and set its edges

Choose one process that is frequent, annoying or costly, and write its start trigger and end result in one sentence each. Everything between those two lines is on the map. Everything outside is not.

A good first process has these traits:

• It happens at least weekly.
• More than one person or tool touches it.
• Someone on the team complains about it.
• You can name a clear start and a clear end.

Poor first picks are "marketing" or "customer service". They are departments, not processes. Pick "a quote request becomes a paid invoice" instead.

Write the edges on a sheet and put it on the wall:

• Starts when: a customer fills in the quote form.
• Ends when: the invoice is paid and the receipt is filed.

Then invite three to five people. Include one person from each role that touches the work, plus whoever owns the result. The people who do the work describe what actually happens. Managers often describe what was designed.

Bring a large sheet of paper or a wall, sticky notes in two colours, markers and a timer.

How do you map a process in one afternoon?

Run the session in four blocks of about three hours in total: 30 minutes to scope, 60 minutes to walk through a real case, 45 minutes to draw, and 45 minutes to review. Keep to the clock. A rough map you finish beats a perfect map you never complete.

Scope: 30 minutes

Read out the start and end. Choose one real case, a specific customer or order from the last few weeks. People remember the awkward parts of a real case: the missing email, the quote someone had to chase.

Walk-through: 60 minutes

Start at the trigger and ask "what happened next?" over and over. Each person writes their own steps on sticky notes, one step each, starting with a verb: "Check stock", "Email quote", "Copy details into the invoice tool". Map what really happened, not what should have happened, and do not fix anything yet.

Draw: 45 minutes

Put the notes in order and add arrows. Where the work can go two ways, add a diamond with the question. Where it sits waiting, add a wait note with the typical time. On every note, label who does it and which tool they use (email, spreadsheet, phone, accounting software, paper). Many templates skip this, and it is what shows you where information is re-typed between tools.

Review: 45 minutes

Read the map aloud from the trigger and ask: "Is this what happens?" Then test it with a second case that went differently, such as a late payment. If the map cannot show that case, a decision or a loop is missing. End with one decision: the first thing to change, and who owns it.

The only symbols you need

Use five symbols. The first four come from standard flowcharts. The fifth is added for small teams.

Software tools offer dozens of other shapes. Ignore them: more symbols make the map harder for the team to read.

A worked example: from quote request to paid invoice

The example below is illustrative, a typical service business such as a small agency or trades company. It is not a real client, and the times are made up to show how to read a map.

Start: a customer sends a quote request through the website form. End: the invoice is paid and filed.

1. Form sends an email to the shared inbox (document).
2. Owner reads the email and checks it is a real enquiry. Decision: is it a fit? No: send a polite decline and end.
3. Owner copies the customer details into a spreadsheet.
4. Owner writes the quote in a document and exports a PDF.
5. Owner emails the quote.
6. Wait for the customer reply. Typical wait: 3 days.
7. Decision: accepted? No: owner sends one reminder after a week, then closes.
8. Owner copies the details again into the invoicing tool and creates a deposit invoice.
9. Wait for the deposit. Typical wait: 4 days.
10. Work is done by the team.
11. Owner creates the final invoice, copying the figures from the quote.
12. Wait for payment. Typical wait: 10 days.
13. Owner marks the invoice paid and saves the receipt in a folder.

Now mark it up (next section). In this example, the owner touches steps 2 to 5, 8 and 11, and the customer's details are typed three times: into the spreadsheet, the quote and the invoicing tool. Waits add up to roughly 17 days, but only about two hours of that time is actual work.

What to mark: handoffs, waiting, rework and manual re-keying

After the map is drawn, use a second colour of sticky note or marker to flag four things. These are where small businesses lose time and make mistakes.

Re-keying is the most useful mark if you are thinking about automation, because it is the easiest to remove. Manual processes covers how to spot these in more detail.

For each mark, write a rough time next to it: minutes per case and cases per week. A guess from the people doing the work is good enough to rank the problems.

Reading the map: finding bottlenecks and what to change first

A bottleneck is the step where work piles up or waits the longest. On a map it shows up as the longest wait, the step with the most loops back to it, or the person whose name appears on the most steps.

To decide what to change first, read the marked map in this order:

1. Look for the longest wait. In the example, the 10-day payment wait is the largest, but it depends on the customer. A faster invoice or a payment link can shorten it.
2. Look for steps with only one person. If the owner is on seven steps, the owner is the bottleneck.
3. Look for re-keying. Typing the same details three times is a quick win.
4. Look for steps that add nothing. If nobody can say why a step exists, try removing it for a month.

Then choose one change and one owner. A single fix, tested for a few weeks, teaches more than a perfect new process nobody follows. In the worked example, a sensible first change is to remove the re-typing: let the form create the quote record, and let the quote create the invoice.

Tools: paper, whiteboard, Miro or Lucid

Start on paper or a whiteboard: everyone can write at once and nobody is distracted by menus. Take a photo at the end. Move to a tool such as Miro or Lucid when you need to share the map with people who were not in the room. Redraw it once with the same five symbols and store it where the team can find it.

A process mapping template you can copy

You do not need a download. Copy this table into a spreadsheet or document, and add one row per step. The first columns draw the map. The last columns find the problems.

PROCESS MAP TEMPLATE

Process name:
Starts when:
Ends when:
Owner:
Date mapped:
People in the room:
Real case used:

| # | Step (start with a verb) | Who | Tool | Type (step / decision / wait / document) | Time per case | Wait before next step | Handoff? (y/n) | Typed again? (y/n) | Goes wrong how often | Notes |
|---|---|---|---|---|---|---|---|---|---|---|
|   |   |   |   |   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |   |   |   |   |

AFTER THE REVIEW
Longest wait:
Step with the most rework:
Data typed more than once:
First change we will try:
Owner of that change:
Check again on (date):

Fill the "Type" column with the five symbols, and answer "Goes wrong how often" with never, sometimes or often.

From map to action: what to fix, what to remove, what to automate

Once the map is marked, sort each problem into one of three buckets:

• Remove. The step adds nothing. Stop doing it.
• Fix. The step matters but is unclear, owned by nobody or done differently by different people. Agree one way, write it down, name an owner.
• Automate. The step is repeated, rule-based and already digital, such as copying data from a form into an invoice. Check it against the signs in when to automate a process before building anything.

Do them in that order. Removing and fixing are cheap. Automating a broken process only makes the broken version faster.

If you want help turning a map into a working change, our process optimization service is built for this. Antonio and Vincenzo, a two-person studio in Las Palmas de Gran Canaria, work remotely with small businesses and can start from your map, or help you draw it.

Keep the map, and look at it again in a month. Processes drift, and the map is how you notice.