How to map a business process before automating it
A process map explains how work starts, where it passes and when it is complete. It helps identify waiting, unclear handovers and missing information before investing in a system. Start with a specific journey and confirm it with the people carrying it out; the result should let you follow a real case from beginning to end.
By the end, you can:
- Define the boundaries of a useful process
- Separate work from waiting
- Prepare an improvement pilot
Choose an observable start and end
“Improve operations” is too broad for a first map. Choose an object moving through the company: a support request, order, proposal or new employee’s onboarding. Write the event starting its journey and the condition confirming completion. Also state who receives the result.
In the fictional Oficina Norte example, the process starts when a repair request arrives and ends when the intervention is completed and communicated. Collection of payment belongs to a related but separate journey in this first analysis. That boundary stops a support meeting becoming an attempt to redesign the whole company.
Observe the actual journey and gather evidence
Ask people in different roles to show recent cases, including a simple case, an incomplete one and one that went backwards. Record the steps performed, documents used and questions asked. Avoid starting with the ideal procedure: a telephone handover may be crucial even if absent from the manual.
In the NHS process improvement guide, the team draws the current journey and validates it with colleagues outside the initial session. Apply that method to your business. “The request had no owner for two days” can be checked in records. To find how often it happens, count cases over a defined period. Identify samples without copying unnecessary personal data into the working document.
Link each stage to a person and an output
Use specific verbs: validate address, assign technician, confirm availability. For each stage, state who performs it, what they receive and what they deliver. When responsibility changes, write how the next person knows they can begin. “It is in the email” does not necessarily identify who should act.
Microsoft’s process documentation shows stages and the data needed to proceed. Make the same connection explicit in a tool-independent map: move to booking only when the minimum information exists. Avoid requiring every field at entry; information arising only during a visit should be completed then.
- Reception
Records the request, contact and equipment.
- Triage
Confirms scope and requests missing information.
- Coordination
Assigns a technician and arranges the intervention.
- Delivery
Records the work and communicates completion.
Every handover should have an owner and an entry condition.
Map the branches that change the work
Decisions need clear questions: is information missing? Is the service within scope? Has the customer accepted the date? Every answer needs a destination. Distinguish a legitimate exception from an execution error; both need handling, but not necessarily the same solution.
Include cancellation, absence, unavailability and reopening. Define who may decide and what is recorded. A generic box called “solve problem” hides precisely what the technical team needs to understand. If there are many variants, separate subjourneys rather than produce an unreadable diagram.
| Situation | Example decision | Responsible role |
|---|---|---|
| Equipment unidentified | Ask for clarification; keep on hold | Reception |
| Service outside scope | Explain the limit and close with a reason | Coordination |
| Customer requests another date | Reschedule without creating another request | Coordination |
| Problem recurs | Link reopening to the original request | Technical coordination |
Separate working time from waiting time
Measure two things: how long someone works on the case and how long the case remains between start and end. Explain whether duration uses elapsed hours or opening hours. Waiting may come from an internal handover, customer availability or a part; treating it all as manual work distorts diagnosis.
In a fictional case, validation takes 6 minutes, preparation for intervention 9 minutes and recording the result 5 minutes: 20 minutes of administrative work. The request spends 26 hours in the journey, mainly awaiting confirmation. Automating the initial 6 minutes does not necessarily resolve that wait. Investigation should identify what limits the desired result.
Propose a change and test the journey
Compare the current map with a proposed version. Assigning an owner at reception or creating a minimum-information list may suffice. If automation is involved, identify exactly which decision remains human and what happens when the system fails. The new journey must remain understandable without knowing the technology used.
Run a tabletop exercise: work through a normal, incomplete and cancelled case with those involved. Each person explains what they see and do. If two people believe the other will act, responsibility is unresolved. If customers must repeat information, review handovers before implementation.
- Check who takes ownership outside normal hours.
- Confirm how a stalled case is found and who resumes it.
- Record pending decisions rather than hiding them in the diagram.
- Compare the same case types before and after the pilot.
Keep the map with its rules
The diagram needs a short worksheet clarifying scope, measures and responsibilities. Give it a version and review date. When a rule changes, check consequences for other stages, training and systems. The map provides a basis for requirements; it need not specify every screen.
Worksheet for your project
Process worksheet Name and objective: Object followed and identifier: Starting event and completion condition: Customer or team receiving the result: Stages, inputs, outputs and responsibilities: Decisions and conditions for proceeding: Exceptions, cancellations and reopenings: Systems and documents used: Working and waiting time, with defined units: Observed cases and hypotheses awaiting confirmation: Proposed change and pilot scope: Evaluation criteria and review owner: Version and date:
Sources and criteria
Content prepared with AI assistance and research using technical sources, with checks of the relevant examples and calculations. The references support the guide’s decisions; examples identified as fictitious let you try out the method.
