What is process mapping, and why does your business need it?

Who receives an enquiry, who prepares the quote, and how does the next colleague know it is their turn? A process map shows these steps, participants and handoffs. It gives people one workflow to discuss instead of accounts limited to their own desks. Its usefulness depends on the information and checks with the people doing the work. The drawing alone does not prove what happens.

What does the map show?

Start with the beginning and end of the chosen process. For each step, record who performs it, what they receive, what result they pass on and which tool they use. Label the outcomes of decisions: for example, what happens with a complete or incomplete enquiry. Include the route back for clarification, as well as the successful path.

An oval commonly marks a start or end, a rectangle an activity, a diamond a decision and an arrow the direction of flow. Lanes for roles or departments, known as swimlanes, help trace responsibilities. Moving between them shows a handoff, but counting crossed lines does not measure the delay.

There are different types of maps. A value stream map examines the route to a product or service and helps discuss value, waiting and waste. BPMN is a formal notation for modelling processes. Choose the detail for the task and the people reading it; you do not need to begin with complex notation or specialist software.

How does it help with everyday work?

A shared map lets participants point out a missing step, repeated check or unclear owner. It can support a new colleague's induction or discussion of a contractual or other requirement. It does not by itself prove that a requirement is met: that needs the relevant actions and evidence.

For an illustration, a colleague receives an enquiry, checks whether the information is sufficient and passes it on for a quote. If information is missing, they ask the customer a question. Mark who sends that question and how the person preparing the quote learns about the reply. This makes the discussion specific; it is not a measured customer case.

To understand where time goes, add observed timings and their basis. An arrow does not show how long the enquiry waited, and one person's recollection is not a measurement of the whole process. Mapping alone does not promise a particular number of hours saved.

How can you build a first working map?

Use this sequence as a practical approach, rather than a mandatory standard:

Define the question and the start and end of the process. Do not begin with the whole company if you are checking only enquiry handoffs.
Involve people doing the different parts and gather existing instructions and examples.
List activities, roles, tools, inputs and results, including exceptions.
Arrange steps and decisions in a readable diagram. Name what passes between participants.
Walk through a real case with participants and check whether the map omits or repeats anything.
Name the person maintaining it and when a change in the work should trigger a new version.

When describing the present, keep proposed changes in another version or clearly mark them. Otherwise a reader may mistake a desired next step for established practice.

When is a template enough, and when is more work needed?

A template in Visio, Miro or another tool can supply layout and symbols. It does not know who actually approves a quote, what happens during an absence or where unfinished work waits. Fill it in with participants and check the content. An outside person can help with questions, but is not a prerequisite for an accurate map.

The same applies to your existing diagram. A flowchart is a type of process map, rather than necessarily an inferior document. If it shows the necessary steps, responsibilities and exceptions accurately, it may be enough. Add detail when it helps answer the particular question.

Questions

Does every process need a separate map?

No. A list may be enough for a short task performed by one person. A map helps when the sequence, decisions or handoffs need clarification. Choose the format for the difficulty of understanding the work, rather than the number of diagrams.

Is mapping the same as automation?

No. A map describes the work; automation changes how part of it is carried out. Analysis may suggest automation, but it may instead reveal a need for clearer ownership or removal of an unnecessary step.

Is the flowchart we already made enough?

It may be. Check its content and accuracy instead of dismissing it because of its name. Where needed, add inputs, outputs, roles, exceptions and timings supported by data.

Sources

From the map to the written report.

An Expert Review builds the map together with the people who run the flow. It also adds a written report on how many hours go into the steps that cost the most.

Ask about an Expert Review

or write to contact@ergostrat.com