Map a process in one day: a workshop guide

Process improvement is often presented as a long programme. You can learn a great deal in a single day, if the day is planned well. This is a practical format that works for any service business.

Before the day

Choose one process. It should have a clear trigger and a clear end, for example "from customer request to job closed". Avoid choosing a whole department.

Pick the people. Invite four to eight people who touch the process at different points, including those who do the work daily. Managers alone will describe how it should work. The team will tell you how it does.

Gather a few real cases. Bring recent examples, including a smooth one and a difficult one.

The day, in four parts

1. Agree the goal (30 minutes). What problem are we solving? Faster completion, fewer errors, fewer complaints? Write it where everyone can see it.

2. Map the real process (2 hours). On a long wall, place one sticky note per step in order, from the trigger to the end. Walk through a real case. Add who does each step, what information they use and how long it takes or waits.

3. Mark the pain (1 hour). Use different colours to mark delays, handovers, repeated work, missing information and places where errors occur. Patterns appear quickly: usually a few steps cause most of the trouble.

4. Choose changes (2 hours). For each problem, ask: can we remove it, combine it with another step, or make it easier? Rank ideas by effort and effect. Pick three to five that can start within a month.

Close the day with commitments

For each change, write down who owns it, what "done" means and the date. Decide the one measure you will use to see if the process has improved, for example time to close or the share of cases needing follow-up.

After the day

• Send the photographed map and the action list within 24 hours.
• Review progress at two and six weeks.
• Re-run the map for the same process after a few months to check the effect.

Common mistakes

• Mapping the official process instead of the real one.
• Inviting too many people, so the day becomes a debate.
• Trying to fix everything at once.
• Leaving without owners and dates.

A good workshop produces a shared picture, agreement on the real problems and a short list of changes. That is often enough to start improvement that lasts.