From Workshop Discussion to a Distinct Set of Risks
A risk workshop can generate many useful observations and still fail at its purpose. Participants may offer overlapping statements, describe current problems instead of uncertain future events, or use the same words to mean different things. The facilitator’s task is to help the group turn contributions into a documented set of distinct risks while preserving what participants meant.
This tutorial focuses on the sequence used to do that: silent idea generation, round-robin sharing, clarification, and consolidation. The objective is identification, not rating or prioritization. Keep the scope and objective-based prompts agreed before the session, and use them consistently as participants contribute.
A risk statement does not need to be fully polished before it is captured. A participant might say, “The vendor feed is sometimes late.” The facilitator can record the wording first, then clarify whether the concern is a possible future delay, an existing issue, a cause of another event, or an effect on an objective. Do not discard an idea simply because its first phrasing is incomplete.
A Repeatable Facilitation Sequence
Before inviting ideas, remind participants of the objective, scope, time period, and prompt. Explain how the session will proceed, who will capture notes, and how participants can ask for an item to be clarified. A neutral prompt should invite possible uncertainty without suggesting a preferred answer. For example: “What uncertain events could prevent the stated objective from being achieved?” is more open than “What could go wrong with the new system?”
Give participants a short, defined period to write down risks independently. Ask for one idea per note or entry, in plain language. Do not debate or edit contributions during this stage.
Invite each participant in turn to offer one item, then repeat the cycle until everyone has passed or has no further items. The facilitator or recorder captures each contribution using the participant’s wording.
Ask concise, neutral questions about the uncertain event, its cause, the objective affected, and any stated consequences. Separate a possible future event from an existing issue or from a cause or consequence.
Compare statements for meaning, not just shared words. Combine items only when the group agrees they describe the same material uncertainty. Retain separate statements when distinct causes, events, or effects make them meaningfully different.
Record the agreed wording, items combined or kept separate, unresolved questions, and relevant source notes. Confirm the resulting list with participants before closing the identification session.
The order matters. Silent generation gives people time to form ideas before discussion begins. Round-robin sharing creates a predictable opportunity for each participant to contribute. Clarification then makes meaning explicit, and consolidation compares the clarified ideas rather than guesses about what brief phrases might mean. This sequence supports a more complete record; it does not guarantee that every possible risk has been found.
Worked Example: Identifying Risks to a Claims Payment Objective
A hypothetical insurer holds a workshop on the objective “issue accurate claim payments within five business days after approval.” Six participants attend: two claims specialists, a finance analyst, an operations manager, a technology representative, and a vendor manager. The facilitator uses a six-minute silent writing period, followed by round-robin sharing, clarification, and consolidation. The method is to preserve each raw contribution first, then compare meaning. The mistake to avoid is treating repeated words as proof that two risks are duplicates.
Step 1: Capture silent ideas. Participants write these six items: (1) “payment file may arrive late”; (2) “incorrect bank details may send money to the wrong account”; (3) “approval status may not transfer to payment”; (4) “system outage stops payment runs”; (5) “vendor may not process the file”; and (6) “claim may be paid twice after a retry.” No item is removed at this stage.
Step 2: Share round-robin. Each participant reads one item per turn. The recorder adds the items to a visible list and asks the contributor to repeat or explain wording only where necessary. All six contributions are captured, including items that sound similar.
Step 3: Clarify. The facilitator asks what “arrive late” means and learns that the payment file may be produced after the daily processing cut-off. The vendor manager explains that “not process the file” means a file could be rejected because of a format change, even if it arrives on time. The group confirms that a system outage could stop the insurer from producing the file at all. These statements concern different failure points.
Step 4: Consolidate. The group agrees to retain four distinct risks: (a) late file production may cause a missed processing cut-off; (b) incorrect bank details may misdirect a payment; (c) a format rejection by the vendor may prevent processing; and (d) a retry after an uncertain response may cause duplicate payment. “Approval status may not transfer” is retained as a fifth risk because it could prevent an approved claim from entering the payment process, a different event from late file production or vendor rejection. The system-outage item is retained as a sixth risk because it has a distinct cause and may stop file production.
Step 5: Check and document. The final count is six distinct risks. The recorder notes that the “late payment file” and “system outage” statements were not merged because one concerns timing and the other a possible interruption to production. The group checks that each statement could affect the five-business-day objective. No likelihood or impact score is assigned during this identification exercise.
Clarifying Before Consolidating
Clarification is not an invitation to cross-examine a participant or to force a polished answer. Its purpose is to understand what uncertainty the contribution represents. Useful questions include: “What might happen?”, “What could lead to it?”, “Which objective might be affected?”, and “Is this an existing condition or a possible future event?” If the participant does not know, record the uncertainty rather than filling the gap with an assumption.
The distinction between a risk, a cause, a consequence, and an issue matters during consolidation. For example, “outdated customer data” may be a cause; “a renewal notice is sent to the wrong address” may be the event; and “coverage is not renewed on time” may be a consequence. If a participant reports that a notice was already misdirected, that is an issue or incident to capture separately from the future risk. These pieces may be linked, but they are not interchangeable.
This test follows from what a risk statement represents. A statement identifies a particular uncertainty in relation to an objective. If two notes differ only in phrasing, rewriting them as one statement preserves the uncertainty. But if one describes a vendor rejecting a file and another describes an internal system outage, combining them as “payment processing may fail” removes the distinction between two events and their different causes. That broad label may be useful as a category, but it is not a substitute for retaining the distinct risks.
Worked Example: Clarifying a Renewal Data Concern
A hypothetical benefits administrator holds a workshop on the objective of issuing renewal terms accurately before the annual renewal date. During silent generation, one participant writes, “bad census data,” and another writes, “members may be left off the renewal.” The method is to clarify each phrase into an uncertain event before deciding whether to merge it. The common mistake is to treat the first phrase, which is not itself a complete event, as though it automatically duplicates the second.
Step 1: Clarify the first note. The facilitator asks what could happen because of “bad census data.” The participant explains that an employer could submit a file with outdated member status, causing the renewal calculation to use an incorrect population. The recorder captures the event as “outdated member status in an employer file may cause renewal terms to be calculated for the wrong population.”
Step 2: Clarify the second note. The facilitator asks how a member might be left off. Another participant explains that a valid member could be omitted when the administrator maps an employer’s file fields into its own system. The recorder captures this as “a field-mapping error may omit an eligible member from the renewal record.”
Step 3: Compare meaning. Both statements involve member data and could affect renewal accuracy, but the first concerns outdated status supplied in a file and the second concerns an internal mapping error. The group decides they are distinct causal pathways and keeps both statements. It records that both relate to renewal population accuracy, without replacing them with a single vague entry such as “data problems.”
Step 4: Resolve uncertainty transparently. Participants do not know whether the field-mapping process is manual or automated. The facilitator records that as an open clarification item rather than inventing a cause. The two risk statements remain useful even though this detail is unresolved.
Check. The final list contains two risks, not one: the number is based on the distinct events and causes identified, not on the shared phrase “member data.” The group has not assessed how likely either risk is.
Documenting Decisions and Maintaining Traceability
The record should let someone who did not attend understand what the group identified and how it reached the consolidated list. At minimum, capture the session objective and scope, the prompt used, the raw contributions or their source, the clarified risk wording, and the consolidation decisions. Also record items that remain ambiguous, were out of scope, or need follow-up. This is workshop documentation, not yet a fully designed risk register.
Preserve a connection between the original contribution and the final wording. A practical record can use an item identifier or a note that links the consolidated statement to the original notes and the discussion decision. When statements are combined, note which contributions were combined. When they remain separate despite similar wording, briefly explain the material distinction. This makes later review possible without requiring participants to remember the discussion.
Do not silently convert a participant’s uncertainty into a fact. If the group cannot establish whether an event is possible, whether a control exists, or which objective is affected, record the question for follow-up. The session can still identify the concern provisionally, with its uncertainty clearly visible.
Worked Example: Consolidating Risks in a Third-Party Data Service
A hypothetical insurer convenes a workshop about timely and accurate receipt of exposure data from a third-party service. Four participants independently contribute: (1) “provider outage”; (2) “provider sends an old file”; (3) “our import rejects the provider’s file”; and (4) “data may be incomplete.” The method is to classify each note by the event and cause revealed in clarification, then retain traceable decisions. The mistake to avoid is merging all four into “provider data problems” merely because each concerns the same service.
Step 1: Clarify each contribution. The provider outage means the service may be unavailable when a scheduled file is due. The old file means the service may deliver a prior period’s data despite being available. The rejected file means the insurer’s import process may fail because a field has changed. “Incomplete” remains unclear until the contributor explains that required exposure records may be absent from an otherwise accepted file.
Step 2: Compare the events. Unavailability, delivery of stale data, import rejection, and missing records are four different possible events. They can all delay or impair the objective, but one event does not imply another. The facilitator therefore retains four statements rather than collapsing them into one broad label.
Step 3: Write concise statements. The group records: (a) service unavailability may prevent receipt of the scheduled file; (b) a prior-period file may be delivered in place of current data; (c) a field change may cause the insurer’s import to reject the file; and (d) required exposure records may be absent from a delivered file. These statements preserve the identified event and, where known, its cause or effect.
Step 4: Record limits of the discussion. The workshop has not established how often the provider is unavailable or whether a validation control detects missing records. Those are questions for later assessment, not grounds to delete the identified risks. The recorder notes them as follow-up items.
Check. The output is four distinct risk statements with two explicit follow-up questions. The list is traceable to the four original contributions, and no likelihood, impact, or control effectiveness has been inferred.
Common Facilitation Errors
A common mistake is to merge notes too early. For example, a facilitator might see “vendor late,” “file rejected,” and “system unavailable” and record one risk: “payment delays.” That is a wrong consolidation: it treats a shared possible consequence as proof of a shared event. The correction is to clarify each note, identify whether the event and causal pathway are materially the same, and retain separate statements when they are not. A common consequence can be recorded as context, but it does not make distinct risks duplicates.
- Editing while participants are still generating. Capture first; clarify and consolidate afterward. Early editing can remove an idea before its meaning is known.
- Accepting a cause as the whole risk. Ask what uncertain event the cause could lead to, while retaining the cause in the record where it is relevant.
- Turning an issue into a future risk without saying so. Record the existing condition accurately, then distinguish it from the uncertainty about what could happen next.
- Letting a broad category replace distinct items. “Data risk” may group related concerns, but it should not erase specific events the group identified.
- Leaving decisions undocumented. Note what was combined, kept separate, or left unresolved so later readers can follow the reasoning.
The facilitator should close by reading the consolidated statements aloud and asking participants whether each captures the intended meaning. That check is not a demand for unanimous agreement about every detail. It is an opportunity to correct misunderstandings, identify missing distinctions, and ensure that unresolved matters are visible in the record.
Check Your Understanding
For each situation, decide what the facilitator should capture or consolidate. Answers follow each problem for checking.
- In a hypothetical workshop on timely policy issuance, participants write “approval queue backs up” and “staff absence delays review.” Clarification shows that both could delay review, but the first concerns a possible increase in incoming volume while the second concerns unavailable reviewers. Should the facilitator merge them? (Answer: Keep two distinct risks; the events and causes differ even though the consequence may be similar.)
- A participant contributes “missing invoice,” then clarifies that a supplier invoice has already failed to arrive this month. What should the facilitator record before deciding whether it is a risk? (Answer: Record the existing missing invoice as an issue or current condition, and clarify separately what uncertain future event could affect the objective.)
- Three participants write “incorrect exposure,” “wrong member count,” and “renewal based on a stale census.” Clarification establishes that all three refer to the same event: an outdated census may cause renewal terms to use an incorrect member population. What is the appropriate consolidation? (Answer: One clarified risk statement linked to all three original contributions, with the consolidation decision documented.)
- In a hypothetical data transfer workshop, one note says a file may arrive after the daily cut-off; another says a changed field may cause the import process to reject it. Both could delay reporting. What should the group retain? (Answer: Two distinct risk statements, because late arrival and import rejection are different events.)
- A group cannot determine whether a suspected control checks for duplicate records. The related contribution describes a possible duplicate payment after a processing retry. Should uncertainty about the control cause the facilitator to remove the risk? (Answer: No. Retain the identified risk and record the control question for follow-up; do not assume control effectiveness.)