Process mapping: how to measure one workflow and price its rework

Why one workflow, measured, beats a general sense of inefficiency

A measured workflow gives you numbers you can argue about; a general sense of inefficiency gives you opinions. Most owners can feel where time leaks, but they cannot say how much, so the fix never competes fairly against other priorities.

Mapping a single workflow also keeps the exercise finite. Trying to map "the whole business" produces a wall of boxes and no decisions. One workflow, done properly, usually reveals patterns, such as unclear handoffs, re-keying data and missing information at intake, that repeat elsewhere.

Step-by-step: walking and timing the workflow

The map is built with the people who do the work, not from a manager's memory. Book a half-day and follow these steps.

1. Name the start and end triggers. For order-to-invoice, the start is "customer order received" and the end is "invoice sent and accepted without dispute." Write both at the top of the page.
2. List every step in order. Ask each person, "What do you do when this lands on your desk, and where does it go next?" Include waiting, approvals and re-checks.
3. Mark every handoff. A handoff is any point where the work changes hands, systems or departments. Handoffs are where information gets lost.
4. Record touch time per step. Touch time is the minutes someone actively works on the item. Use the median from five or six real examples, not the quickest one.
5. Record elapsed time. Elapsed time is the calendar time from start trigger to end trigger, including all the waiting. Pull dates from your order and invoicing records.
6. Tally corrections for two weeks. Give each person a simple tick sheet: every time an item comes back to them for a fix, they note the step and the minutes spent.
7. Write down the cause of each correction. Missing information, wrong price, wrong quantity, duplicated entry. Causes cluster, and the clusters tell you what to change.

Keep the map in a spreadsheet: one row per step, with columns for owner, touch minutes, handoff (yes/no) and corrections counted.

The worked example: order-to-invoice at a 22-person distributor

Here is what a first map might look like for a hypothetical distributor that handles 340 orders a month. The numbers are illustrative, but the arithmetic is the method.

Elapsed time from order to accepted invoice averages 6.5 working days. At eight hours a day, that is 52 working hours, or 3,120 minutes.

Flow efficiency is touch time divided by elapsed time: 95 ÷ 3,120 = 3.0%. In other words, for 97% of its life an order is waiting. That is common, and it is not a reason to rush people. It points at queues and handoffs, not effort.

Counting rework and turning it into dollars

Rework is any time spent fixing work that was supposed to be finished. It is usually the largest hidden cost on a process map, and the easiest to price.

In the two-week tally, the team finds that 18% of orders need at least one correction, and the average correction takes 40 minutes once you add up everyone involved (re-entering, phoning the customer, reissuing paperwork).

• Orders corrected per month: 340 × 18% = 61.2
• Correction minutes per month: 61.2 × 40 = 2,448 minutes, or 40.8 hours
• Loaded labour rate: a $34 wage plus payroll costs, benefits and paid time off, about $48 an hour (confirm your own figure with your bookkeeper)
• Monthly rework cost: 40.8 × $48 = $1,958
• Annual rework cost: $1,958 × 12 = $23,496

There is also a cash effect. Suppose 4% of invoices are disputed because of order errors, each averaging $3,800, and each dispute delays payment by 21 days. That is 340 × 4% = 13.6 invoices, or $51,680 a month arriving three weeks late. If the business carries that gap on a line of credit at 8% a year, the carrying cost is $51,680 × 8% × 21 ÷ 365 = about $238 a month, or roughly $2,855 a year, on top of the labour.

Neither figure includes the customer who quietly orders elsewhere next time. Leave that out of the business case; it is real, but you cannot measure it yet.

Choosing fixes and estimating the saving

Fixes should target the causes the tally revealed, not the steps that merely look slow. In our example, three causes account for most corrections:

• Orders arriving by phone without a written confirmation of quantity and price
• The price list kept in two places, so inside sales and the bookkeeper disagree
• Shipping changes made in the warehouse but not passed back to the order record

The team agrees on three changes: a written order confirmation sent before release, a single price list that both inside sales and billing read from, and a rule that any shipping change is entered on the order before the truck leaves. Four handoffs are removed by letting inside sales release credit-approved accounts directly.

If the correction rate falls from 18% to 7%, the arithmetic is:

• New corrections: 340 × 7% = 23.8 a month, × 40 minutes = 952 minutes, or 15.9 hours
• Hours recovered: 40.8 − 15.9 = 24.9 hours a month
• Saving: 24.9 × $48 = $1,195 a month, or about $14,350 a year

Write the target down as a number, and re-run the two-week tally three months after the change. If the rate has not moved, the cause was misdiagnosed; go back to the correction notes.

Common mistakes when mapping a process

These are the errors we see most often when owners map their own workflows.

• Mapping the ideal process. People describe how it should work. Ask them to walk through the last three real orders instead.
• Timing only the fast cases. Use the median of several examples, and note the bad days separately.
• Ignoring waiting time. Touch time looks fine on paper; elapsed time is what customers feel and what delays your cash.
• Blaming people for system problems. If 18% of orders need correcting, the process produces errors. Treat the tally as data, not a performance review.
• Buying software first. Automating a broken workflow just produces errors faster. Fix the causes, then decide what to automate.
• Forgetting to re-measure. Without a second tally, you will not know whether the change worked.

A short checklist before you start

• One workflow chosen, with a written start trigger and end trigger
• Everyone who touches it booked for the walk-through
• A tick sheet for corrections, with a column for the cause
• A loaded labour rate confirmed with your bookkeeper
• Order and invoice dates available to calculate elapsed time
• A date, about three months out, for the second tally

Where this fits in a wider engagement

A single map often becomes the first concrete result of a business diagnostic, because it shows the team that the waste is measurable. From there, the same method extends to quoting, scheduling or purchasing, and the savings feed straight into the margin work described in the margin by service line guide.

If you would like a second set of eyes on your first map, or help running it with a team that is too busy to stop, see how operations and process improvement engagements are structured, or review the engagement models and fees. A short text to (604) 632-4959 with the workflow you have in mind is a perfectly good way to start; you can also call or email, and we can meet by video call or in person.