A plain-language guide to mapping a business process

Follow one piece of work from start to finish

Choose a real example: one inquiry, one order, one approval, or one new customer. Ask what triggered it, where the information came from, who touched it, and how everyone knew it was complete.

This keeps the conversation grounded. Process maps become vague when they describe what should happen instead of what actually happened last Tuesday.

Capture the work between the boxes

The biggest delays often live in handoffs: checking whether a form is complete, asking for missing context, retyping data, waiting for approval, or following up when no one responds.

Record tools, rules, decisions, wait time, rework, and exceptions. Those details show whether the problem needs automation, clearer ownership, better data, or a simpler policy.

• Trigger and desired outcome
• People and systems involved
• Rules, decisions, and permissions
• Waits, errors, repeats, and exceptions

Remove friction before automating it

Do not make a confusing process move faster unchanged. Ask which steps can disappear, which information can be captured once, and which decisions truly require a person.

Then design the future state with visible ownership and measures. Automation should support the better process, not preserve every historical habit.