How do you learn business process mapping quickly and correctly when a simple order seems to move through too many people and screens? Begin with one customer request and follow exactly what happens until it is completed. A process map is a sequence of actions, decisions and handovers that makes work easier to understand. This eduKateSG Business Quick Notes lesson teaches beginners to define a start and finish, write steps in plain language, add a yes-or-no decision and find the stage that limits completed output. You can draw the entire lesson using arrows on a sheet of paper—no expensive software is required.
- Choose one process: name the event that starts the work and the correct completed result.
- Follow actual actions: list what people really do, not just what a manual says.
- Mark decisions: show what happens when stock or information is missing.
- Clarify handovers: state who owns each next action and record.
- Measure the flow: identify waits, defects and limiting capacities.
- Improve carefully: reduce unnecessary confusion without bypassing important checks.
Teaching step 1 — follow one ordinary order. Imagine a stationery shop receiving an order for a blue notebook kit. Write the path as receive request → verify item and quantity → check stock → verify payment status → pack kit → inspect contents → hand over → record completion. Each phrase begins with an action. This map reveals eight different jobs even if one employee performs several of them. It also lets the team see where information might become wrong. A process map is not an organisation chart: it describes the work needed to deliver the customer’s result rather than merely listing job titles.
Teaching step 2 — add a decision with two clear paths. At the stock step, ask, “Is the correct kit available?” If yes, follow the approved order process. If no, the team must verify the inventory record, inform the authorised customer-contact owner and communicate accurate options rather than pretending stock exists. Draw a branch: available? → yes: continue; no: resolve stock exception. Decide which record is authoritative and who may change the order. A vague box saying “sort it out” is not helpful because nobody knows what happens next. Good maps show what to do when the normal path fails.
Teaching step 3 — calculate a real constraint. Suppose order verification can process 24 orders per hour, packing can complete 12 orders per hour and final inspection can handle 18 orders per hour. If each order requires all three stages and there is sufficient demand, packing is the current bottleneck at a theoretical maximum of 12 finished orders per hour. Making verification even faster does not solve the packing limit. If an additional trained packer allows packing to reach 24 per hour, final inspection may then become the bottleneck at 18 per hour. Actual output may be lower because of interruptions, mixed orders or other constraints. The useful lesson is to inspect the limiting stage before changing everything.
The seven-part process map
- Start: identify the trigger, such as a confirmed customer request.
- Input: record necessary information, stock and permissions.
- Action: describe each essential step with a verb.
- Decision: show the yes and no paths when an important condition is checked.
- Owner: name who is responsible when the work changes hands.
- Control: mark required accuracy, payment or safety checks.
- Finish: state how completed, accepted work is verified.
Keep the first map short. Six to ten clear boxes may be enough to explain a small process. Add a new box only when it helps somebody understand an action, decision or source of error. A diagram that nobody can follow is not automatically better than a plain written list with arrows.
Process map, checklist and project plan
- Process map: explains the flow of ongoing work.
- Checklist: helps somebody verify individual requirements.
- Project plan: organises temporary work needed to produce a particular result or change.
- Role description: states which tasks and decisions belong to a person.
- Performance measure: reports an observed result such as correct orders per hour.
All five can be useful, but they answer different questions. A checklist may say “confirm notebook colour.” The map says when the check occurs, what happens if the colour is wrong and which person receives the corrected order. A project can create a new ordering system; the process map then describes how the system is used each day.
Handovers are where information can get lost
A handover happens when one person, team or system passes work to another. The order-taker might confirm a customer request and place it on the approved packing list. If the packer instead receives an outdated screenshot, both workers may believe they are following instructions while the customer receives an incorrect item. The map should specify where the current approved record lives, who may amend it and how a change is communicated.
When customer information is involved, appropriate access matters. The packer may need the product code and relevant handover details but not every personal field in a customer account. A clear process improves reliability and helps limit unnecessary data sharing.
Working time and waiting time are different
Suppose an order arrives at 2:00 p.m., reaches packing at 2:12 p.m. and is ready at 2:20 p.m.. Its total elapsed lead time is 20 minutes. That does not establish that staff actively worked on it for 20 minutes. Some of the time may have been waiting in a queue. To improve the process, observe how long an order is actually being handled and how long it waits between steps.
Be careful about the objective. A wrong order sealed in five minutes is not necessarily a better outcome than a correct one prepared in ten. Faster flow is valuable only when it preserves the required standard and fulfils the real customer promise.
Find rework loops before removing useful checks
Imagine the packer repeatedly receives orders with missing product codes. Each time, the packer returns to the order-taker for clarification. Draw that loop, including the question and the return to packing. A possible improvement is to verify the required product code when the order is accepted. That may prevent repeated questions. But a kit that fails inspection should still follow a correction path. Removing a legitimate inspection does not prevent an error; it may merely hide it until the customer discovers it.
The map therefore distinguishes necessary safeguards from unnecessary repeated work. Ask what each loop accomplishes and whether the underlying reason can be repaired. An effective improvement reduces avoidable work while keeping the customer and the organisation protected.
Simple process measures to learn
- Throughput: correctly completed units per time period.
- Stage capacity: how many units a particular step can handle under stated conditions.
- Lead time: time from the defined start event to the defined finish.
- Queue: work waiting to enter the next stage.
- Rework: additional work needed to correct an earlier failure.
- First-pass quality: the proportion completed correctly without a correction loop.
If 40 kits are prepared and four fail the first quality inspection, 36 passed immediately. The observed first-pass acceptance rate is 36 ÷ 40 = 90%. That result does not show why four kits failed. The process map helps the team investigate whether the item selection, labels, instructions or checks need improvement.
Your twelve-minute process mapping routine
- Minutes 1–2: select one customer request and define the end result.
- Minutes 3–4: write six to eight actions in order.
- Minutes 5–6: add one decision and show the alternate path.
- Minutes 7–8: mark the responsible person at important handovers.
- Minutes 9–10: identify a queue, rework loop or bottleneck.
- Minutes 11–12: propose one improvement and a way to check its effect.
Quick practice: which stage limits delivery?
An order process has three required stages. Verification can handle 30 orders per hour, packing 20 and inspection 15. What is the limiting stage under simple steady conditions? If inspection capacity safely increases to 25 per hour and nothing else changes, which stage limits the process next?
Answer: Initially, inspection at 15 per hour limits the whole line. After inspection capacity rises to 25, packing at 20 per hour becomes the bottleneck. This model assumes sufficient demand, stock, and no further constraints. It is not a reason to bypass essential inspections.
Common mapping mistakes
- Drawing an ideal process without observing the work: follow real orders.
- Using unclear boxes: name specific actions and responsible people.
- Forgetting exceptions: add decisions for missing information and unavailable stock.
- Confusing speed with quality: count accepted results.
- Ignoring old order versions: name the authoritative information source.
- Removing useful controls: distinguish prevention from avoidable rework.
Check your understanding
Question 1: What does a process map begin and end with? A defined trigger and completed result. Question 2: Is the person who looks busiest necessarily the bottleneck? No. Question 3: Why draw both yes and no paths? So the team can respond correctly to exceptions.
Continue the Business Quick Notes series
Explore Business Operations, Quality Control, Business Productivity, Project Management, Business KPIs, and Scenario Planning.
For broader business operating guidance, refer to the U.S. Small Business Administration business management resources. All capacities and timings used here are hypothetical. Remember: follow the work, show the decisions, identify the limiting step and improve without sacrificing accuracy.