How to Create a Process Map That Shows Real Work

Map the work as it happens now

To create a process map, define one trigger and one end point, gather the people who actually perform the work, and draw every action, decision, wait and handoff in sequence. Verify the map against a real recent example before looking for improvements. Keep the current-state map separate from the proposed future state, assign an owner to each change, and update the related procedure only after the revised flow has been tested.

A useful map makes invisible coordination visible. It does not need polished software or a wall of specialist symbols. It needs a clear boundary and an honest account of what happens between the two ends.

What should you map?

Choose a process with a repeatable trigger, an identifiable result and a problem worth understanding. “Run the company” is too broad. “Turn an approved customer order into a scheduled delivery” is bounded enough to examine.

Write the scope at the top of the page:

• Trigger: the event that starts the process
• End point: the observable state that finishes it
• Unit: one order, request, application, return or other item moving through the flow
• Perspective: whose work and experience the map follows
• Owner: the role responsible for keeping the map current

The U.S. Environmental Protection Agency's process-mapping guidance begins with selecting the target process and setting the perspective and boundaries. That step prevents a workshop from drifting into every adjacent problem the business has.

Record out-of-scope issues in a parking list. They may deserve their own maps, but they should not quietly expand this one.

Who belongs in the mapping session?

Include people who perform, receive and support the work. A manager can describe the intended process; the people completing it know the actual handoffs, workarounds and waiting points.

For a customer return, that might mean someone from customer service, warehouse operations, payments and inventory. Include the person who receives the output, because an internal “done” state may still leave the next person without what they need.

Keep role names separate from employee names. “Customer-service lead” survives a staffing change; “Priya” may not. If only one person knows a step, note that operational dependency without turning the session into a performance review.

Set a simple ground rule: map the current process without blame. A current-state map is evidence about the system, not a scorecard for the people navigating it.

Which symbols do you need?

Three symbols are enough for most first maps:

• a rounded start/end shape for the trigger and finish
• a box for an action
• a diamond for a decision with labelled branches

Connect them with directional arrows. Add a waiting or delay marker if it makes queues easier to see, but do not delay the work while the team debates notation. NHS process-mapping guidance makes the same practical point: the best map is the simplest one that provides the needed insight.

Use verb-led action labels: “check stock,” “request approval,” “send confirmation.” A label such as “finance” names a department, not what occurs. On a decision diamond, write a question and label each path: “Payment matched?” followed by “yes” and “no.”

How do you capture the current state accurately?

Start with a recent real item and walk it from trigger to finish. Ask what happened, not what the policy says should happen.

For each step, capture:

1. the action or decision
2. the role performing it
3. the input required
4. the output produced
5. the system, form or channel used
6. the usual wait before the next step
7. the exceptions that send work backward or elsewhere

Place steps in sequence at a high level first. EPA's hierarchical method recommends a top-level map of no more than about six major steps, followed by deeper levels where useful. A small business need not adopt that number as a rigid limit, but the principle is sound: begin with the whole flow, then expand the area that needs explanation.

Do not erase rework because it looks untidy. If an incomplete request returns to the customer twice, draw the loop. If a manager approves routine cases in batches on Friday, show the queue. If the same data is copied between two systems, include both entries. Those are often the reason for mapping.

How should you verify the map?

A workshop memory is not enough. Test the draft against at least one more completed item, preferably one routine case and one exception. Ask each participant to trace the steps they touch and confirm what arrives, what they do, and what leaves.

EPA guidance explicitly includes verifying the map with employees and revising it. The check matters because teams commonly omit quiet work: renaming files, chasing missing details, creating a duplicate record, waiting for access or correcting a rejected submission.

Mark unknowns rather than guessing. Assign a person to resolve each one and a date for the answer. If process data contains customer, health, payment or employee information, use a de-identified example and follow applicable access and retention requirements.

The verified map should carry a version date and owner. A diagram with no owner becomes another orphan document.

What should you measure on the map?

Measure only what helps answer the process question. Useful fields can include:

• hands-on work time
• waiting time
• volume entering the step
• percentage returned for missing information
• number of handoffs
• source and destination systems

Define the unit and collection period. “Approval takes two days” is ambiguous: mean, median, maximum, business days, or one memorable example? A short sample with its dates and limits stated is more useful than a confident invented benchmark.

Separate work time from elapsed time. A five-minute review may sit in a queue for three days. Improving the form will not fix the queue if the actual constraint is an approval window.

Do not collect sensitive employee metrics simply because the map provides boxes to hold them. Employment monitoring, records and performance decisions can carry legal and human-resources obligations. Obtain qualified guidance appropriate to the workforce and jurisdiction before expanding into individual monitoring.

How do you design the future state?

Copy the verified current map and label the copy future state. Do not edit the current map until it resembles what everyone wishes happened. The gap between the two is the work.

Examine each step:

• Does the customer or next role need its output?
• Is information entered more than once?
• Does a handoff have a named receiver and acceptance condition?
• Does an approval control a defined risk, or merely repeat a prior check?
• Can missing information be caught at the trigger?
• Is the exception route explicit?
• Does one role or system create a single point of failure?

The EPA describes value-stream mapping as a current-state drawing followed by a future-state drawing and an implementation work plan. That final part matters. A cleaner diagram is not an operational improvement until the changed process is tested and adopted.

Choose a small pilot when possible. Define the cases included, the owner, the start and review dates, the measure that should change, and the condition that would stop or revise the test. Preserve required approvals and controls until qualified owners agree they can change.

When does the map become an SOP?

A process map shows flow: sequence, decisions, waits and handoffs. A standard operating procedure explains how a trained person performs a defined task. They support one another but are not substitutes.

Once the future flow works in practice, update the corresponding procedure, forms, system instructions and training. The guide to writing a small-business SOP provides the document structure. Use the weekly team meeting agenda to review actions that genuinely require shared attention, not to reread the map aloud.

For safety-critical, regulated, financial, employment or contractual processes, a map is only an operational view. It does not establish legal compliance or replace review by the qualified safety, legal, accounting, human-resources or regulatory professional responsible for that area.

A one-page process-map template

Use this compact brief before opening any diagram tool:

Process:
Trigger:
End point:
Unit followed:
Perspective:
Owner and version date:
Participants:
Current steps and decisions:
Waits, loops and exceptions:
Evidence checked:
Problems observed:
Future-state changes:
Pilot owner and review date:
Documents to update after testing:

If the team can complete those fields and trace a real case through the drawing, it has a working process map. If it cannot agree where the process starts, who receives a handoff or what “done” means, the map has already found useful work.

Sources

• U.S. EPA: Lean and Environment Toolkit, Chapter 4
• U.S. EPA: Lean and Environment Toolkit, Appendix A
• U.S. EPA: E3 Value Stream Mapping How-to Guide
• GOV.UK Service Manual: Map and Understand a User's Whole Problem

An independent publication. Not affiliated with any prior owner of this domain.