The workshop was great. The write-up takes all night.
A day-long current state workshop with the client's order-to-cash team produced three walls of sticky notes: process steps in yellow, pain points in pink, ideas in green, with arrows drawn in marker between them. The consultant photographs everything. That evening, they redraw the process in Visio, squinting at handwriting, working out which arrow went where, and typing each pink note as a pain point.
On a remote workshop the notes are on a Miro board, which is easier to read, but the redrawing into the firm's standard swimlane notation is still manual.
Why workshop outputs are slow to write up
- Photos of sticky notes are hard to read and harder to structure.
- Workshop boards do not follow the notation the final deliverable needs.
- Pain points and ideas are separated from the steps they relate to.
- Validation with the client needs a clean version quickly, while memories are fresh.
- The same effort repeats for every workshop on every engagement.
Workshops also generate more than the map. Participants add questions, data they promised to send, and names of people to talk to. Those notes are easy to lose in the redrawing, and they are often what the next stage of the engagement depends on.
What slow write-up costs
| Issue | Effect |
|---|---|
| Evening redrawing | Consultant fatigue, errors |
| Validation delayed | Client forgets details, corrections less accurate |
| Pain points detached | Analysis loses context |
| Inconsistent notation | Maps from different consultants look different |
Momentum is the hidden cost. Workshop participants leave energised and expect to see their input reflected quickly. When the map arrives a week later, the energy has gone, corrections are half-hearted, and the future state workshop starts from a weaker base.
How we build workshop capture
- Photos of walls and whiteboards, or an export from Miro or Mural, are uploaded after the workshop.
- Notes are read, including handwriting where legible, and grouped by colour and position into steps, roles, decisions, pain points and ideas.
- The consultant reviews the extracted list, corrects misreadings and fills gaps from their notes.
- A process map is drafted in your notation, swimlanes by role, in Visio, PowerPoint or your process tool.
- Pain points and ideas stay linked to their steps and appear as annotations and in a separate issue log.
- A validation version is produced for the client within the same day.
- Client corrections update the structured list, and the map is regenerated.
Reading handwriting from photos is never perfect, and the consultant who ran the workshop is still the one who knows what was meant. The tool gives them a draft to correct rather than a blank page.
We usually test on photos from a few past workshops to see how well handwriting and colours are read, and tune the grouping rules to match how your consultants run their walls. Using consistent sticky note colours for steps, pain points and ideas makes a real difference.
What changes after a workshop
The consultant spends an hour correcting a draft instead of an evening drawing. The client receives a validation version while the workshop is fresh in their minds.
Pain points arrive in the analysis linked to where they happen, which makes the future state work sharper.
Does this sound like your workshops?
- Workshop outputs are redrawn by hand afterwards.
- Sticky note photos are hard to read.
- Pain points get separated from process steps.
- Validation versions reach the client days later.
- Maps look different depending on who drew them.