Run a 60‑Minute Process Discovery Workshop

An hour is enough time to discover a process well if you spend it on the right things. That means walking away with a clean draft of the happy path, one or two real exceptions, clear ownership of the work, and a short list of follow-ups — all agreed on by the people who actually do the process. It is not enough time to draw a beautiful diagram, model every edge case, or resolve every disagreement. Trying to do those things in sixty minutes is the single most common reason these workshops overrun and produce nothing.

The agenda below is built around that trade-off. It assumes you have the right people in the room (people who actually perform the steps, not just their managers), a shared canvas or whiteboard everyone can see, and a facilitator whose job is to keep the group on the happy path until the last ten minutes. Run it two or three times and you will start trusting it.

The Sixty-Minute Agenda

0–5 minutes — Scope and outcomes

Open with a single sentence that names what you are mapping and what the outcome looks like. A useful formula is: From [trigger] to [end state] for [audience or channel]. For example, "From when a customer submits a refund request to when the refund lands in their bank account, for online orders only." That sentence does two useful things: it tells the group what they are not mapping (everything else), and it gives you something to point at whenever the conversation drifts. Say out loud what you will walk away with: a diagram of the main path, one or two common exceptions, owners for open questions, and next steps.

5–15 minutes — Roles and hand-offs

Before you start mapping steps, agree on the roles and teams that touch the process. These will become your swimlanes. Prefer role names ("Customer Support", "Finance", "Order Management System") over individuals — the diagram should still be correct when someone goes on leave. If external parties are involved, note them now; they will end up in their own pools rather than inside your organisation's lanes. This section is deliberately short. You are not trying to finalise the org chart, just to list the actors.

15–40 minutes — The happy path

This is the core of the workshop. Ask the group to narrate the main scenario from the trigger to the successful outcome, one step at a time, and capture each step as you go. Keep the first pass to roughly seven to ten steps. Anything more detailed is a sub-process, and anything less is missing information. As each step is named, place it in the correct lane so responsibilities stay explicit and lane ownership is decided live rather than after the fact.

Resist the urge to draw shapes and connectors during this phase. Capture the steps as a numbered list or as sticky notes in lanes — layout comes later. Enforce verb-first plain-language labels as you go: Verify customer identity, not Handle verification. It is much cheaper to rewrite a label at minute twenty than at minute fifty.

40–50 minutes — Essential exceptions

Ask the group: "What are the one or two things that most often go wrong?" You want the exceptions that happen routinely, not the ones that happen once a year. Good candidates are things like missing information, out of policy, or system timeout. Add them as exclusive-gateway branches from the relevant point in the main path. If more than two important branches emerge, note them in a parking lot and schedule a short follow-up rather than trying to squeeze them into the remaining time.

50–60 minutes — Review and commitments

Read the flow aloud end-to-end. If any step is hard to narrate, fix it. Confirm that every gateway has a clear question and that every branch goes somewhere. Then spend the last few minutes on commitments: which open questions need an answer, who owns each one, and when it is due. Summarise decisions on the canvas while people are still in the room so there is no ambiguity afterwards.

A Starter Template You Can Copy

If you want something to paste into a blank document before the session, use this skeleton. Process name: the thing you are mapping in six words or fewer. Scope: from [trigger] to [end state] for [audience or channel]. Lanes: three to five roles, teams, or systems. Main path: Start → step 1 → step 2 → … → End, with each step in the correct lane. Decisions: one or two gateways with clear yes/no or condition labels. Outputs: the artefacts, notifications, or status changes the process produces. Open questions: each one with an owner and a due date. That list — plus the diagram itself — is everything you need to leave the workshop with.

Facilitation Tips That Keep It Moving

Time-box visibly. Keep a timer on screen and announce the halfway point. People work faster when they can see the clock than when the facilitator has to remind them how much time is left. Announce at minute thirty that you are halfway through the happy path; announce at minute forty that you are moving to exceptions.

Capture content before layout. The most common way these workshops fail is that someone starts dragging shapes around the canvas in minute ten and the group spends the next half hour discussing whether a task should be a rectangle or a rounded rectangle. Write the steps in bullets first, discuss them, and only then arrange them as a diagram.

Enforce plain language. If a step label uses tool jargon or internal acronyms the whole room does not recognise, rewrite it on the spot. A workshop where everyone silently nods at a label they do not actually understand is a workshop that is quietly failing.

Limit concurrency. One editor holds the pen and one narrator walks through the process at a time. If you have several people trying to type and draw at once, you end up with duplicated work and lost content. Rotate the roles mid-session if energy drops.

Park edge cases. Keep a visible "parking lot" list on one side of the canvas. Every time someone raises an interesting edge case that does not belong in the main path, write it down and move on. The parking lot reassures people that their point was heard without letting it derail the main discussion.

Common Pitfalls and How to Handle Them

Scope creep is the biggest one. Unrelated sub-processes surface mid-discussion and suddenly the group is mapping three processes at once. When you feel it happening, read the scope sentence aloud again and ask whether the new topic belongs inside or outside it. If outside, add it to the parking lot and keep going.

Role ambiguity is the second. Steps start bouncing between lanes because the group has not quite decided who owns what. The fix is to pause and rename the lane: is it really "Finance" or is it more specifically "Accounts Receivable"? Ownership gets clearer when the lane names are specific.

Vague labels are the third. When you catch yourself writing Handle request or Process the item, rewrite immediately. What does handle actually mean? Validate? Approve? Forward? Each answer is a different step.

Tool-first mapping is the fourth. If the group starts diving into the features of whatever diagramming tool you are using, you have lost the content discussion. Go back to bullets for a few minutes until the conversation is about the process again.

What You Should Leave With

A good sixty-minute workshop ends with three tangible outputs. First, a legible BPMN draft showing the happy path plus the one or two most important exceptions — rough is fine, but it should be readable. Second, a list of open questions with named owners and due dates, so you know exactly who is responsible for resolving each gap. Third, a short summary that can go out as an email or a page: decisions made, the diagram link, and whether a follow-up session is needed. Aim to share that summary within 48 hours while the session is fresh.

The 48-Hour Follow-Up

Within two days, share the diagram and notes with the attendees and ask for asynchronous comments against a 72-hour deadline. Apply the low-friction edits yourself — spacing, label rewrites, lane cleanup — and tag the named owners on any open questions. If two or more important exceptions turned up in the workshop that you could not fit into the main session, schedule a 30-minute follow-up just for those. Keep follow-ups short and focused: the productivity trick is the same as the workshop trick, which is to insist on one topic at a time.

If you want the workshop output turned into a clean BPMN diagram without spending another hour dragging shapes around, try BPMN AI — you paste in the workshop notes and get back a diagram that follows the structural rules described above, ready for the async review step.