Choose the question in advance
Decide whether the session is about a workflow, an integration, a user group, or a delivery constraint. Send participants a short description of that focus and ask them to bring a recent example.
Invite people who perform the work and people who understand its constraints. A decision-maker can explain priorities, but may not know the daily exceptions. A technical specialist can identify integration risks, but should not have to invent the business process.
Work from examples before opinions
Ask someone to walk through an item from beginning to end. Record the systems involved, the points where work stops, and the decisions that require judgment. Distinguish observed facts from assumptions as they appear.
When people disagree, identify whether they are describing different user groups or different stages of the same process. Write down the unresolved question instead of forcing agreement through vague wording. Assign a person to collect the missing evidence.
End with an actionable record
Capture decisions, open questions, owners, and the next experiment or deliverable. A useful output might be a workflow map, a list of integration constraints, or the scope of a focused first release.
Read the decisions back before ending the session. Confirm who has authority to approve the next step and when the missing information is needed. Share a concise record that participants can correct while the discussion is fresh.
Discovery is not complete merely because the workshop ended. Its value appears when the resulting information changes a scope, eliminates an assumption, or makes an implementation decision easier to defend.
A practical example.
A useful session about order exceptions could begin with a recent delayed order on screen. Ask the operator to reconstruct the sequence: what arrived, what looked wrong, whom they contacted, and how the issue was closed. Capture unanswered questions separately so the meeting does not become a speculative design debate.
If sales and operations disagree about the status definition, write down both meanings and identify who can resolve the policy. The session’s output may be a simple workflow, a short risk list, and two follow-up observations. It need not end with an agreed feature list. Send a concise record that distinguishes observed behavior, participant preferences, and decisions still awaiting an owner.
Put it into practice.
- Bring representative records and the people who actually handle them.
- Reserve time for exceptions and handoffs, not just the normal sequence.
- Assign an owner and next step to every question that blocks a decision.