Why Workshop Structure Matters
A risk workshop can bring together useful experience and still produce a narrow list. Participants may follow a senior colleague’s first suggestion, focus on the first risk named, or avoid raising concerns that could appear disruptive. The result may look like agreement, even when some people have different information or have not had a fair chance to contribute.
Two common influences are groupthink and anchoring. Groupthink is pressure toward apparent consensus that discourages examination of alternatives or expression of doubts. Anchoring occurs when an early idea, estimate, or framing becomes a reference point that unduly shapes later judgments. They can occur together: an influential participant names one risk, and the group both treats it as the natural starting point and hesitates to challenge it.
The facilitator cannot guarantee that these influences will disappear. The practical aim is to make them less likely to control the discussion: let participants think independently before hearing others’ views, use more than one prompt, invite reasoned dissent, and separate generating risks from evaluating them. This tutorial concerns the conduct of the workshop, not the subsequent scoring or prioritization of risks.
Design the Sequence to Protect Independent Thinking
If participants begin by discussing ideas aloud, the first few contributions can shape what everyone else considers relevant. A simple countermeasure is to give each participant a short, quiet period to write down risks before the group discussion begins. Collecting those ideas before they are discussed helps preserve contributions that might otherwise be lost to deference, interruption, or the feeling that “someone has already said it.”
Independent idea generation need not mean working in isolation throughout the workshop. It means protecting a first pass in which each person can consider the objectives and prompts without being steered by a colleague’s answer. The facilitator can then combine and clarify the contributions as a group.
Remind participants what activity or decision is in scope. Use a neutral prompt tied to the objective rather than naming a favored risk as the starting point.
Give everyone a brief period to record possible risks silently. Participants can write one idea per card or in a private list; the method matters less than allowing an unprompted first pass.
Collect or display the ideas without immediately debating which is most important. Clarify what an idea means, but do not let early confidence substitute for examination.
Ask participants to consider the objective from different angles. Make space for a concern, alternative explanation, or counterexample before treating agreement as settled.
Record the distinct risks and unresolved questions. Note where an idea was combined with another or set aside, and why, so that silence is not mistaken for agreement.
Vary Prompts Without Steering to a Preferred Answer
A prompt is useful when it opens a line of thought without implying what the answer should be. If the facilitator asks only, “What could make the supplier fail?”, participants may focus on the supplier and overlook internal dependencies, customer behavior, or changes in requirements. A broader set of prompts can help the group consider different aspects of the same objective.
- Objective-focused: What could prevent us from meeting the objective?
- Change-focused: What assumptions might stop holding over the period we are considering?
- Dependency-focused: What outside party, system, or decision could affect the activity?
- Control-focused: Where could an intended safeguard fail, be delayed, or be applied inconsistently?
- Perspective-focused: What might look different to a customer, an operations team, or a regulator?
These are prompts for discussion, not a checklist that proves the risks have been fully identified. Use them to widen the conversation, and avoid repeatedly rephrasing a single favored scenario as if that were independent coverage. Keep the prompts connected to the agreed scope so breadth does not become an unfocused discussion of every imaginable concern.
Invite Dissent Without Manufacturing Disagreement
A facilitator can ask, “What would make this conclusion wrong?” or “What concern has not yet been raised?” These questions signal that respectful challenge is part of the task. They are most useful when participants can point to a specific cause, event, effect, assumption, or piece of experience rather than being asked to oppose a proposal for its own sake.
A dissenting view should be heard and clarified, not automatically accepted as the correct answer. The facilitator can ask what circumstances would make the concern relevant and whether it identifies a distinct risk or a different description of an existing one. If the group cannot resolve the point within the workshop, record it as an open question rather than forcing a vote that creates an appearance of certainty.
The facilitator should also watch how contributions are received. Interruptions, dismissive humor, or immediate rebuttal can teach participants that raising a concern is unwelcome. A neutral response—“Let us capture that before we assess it”—keeps the contribution available for consideration without implying that it is true.
Why Independent Generation Helps
A simple probability model illustrates the reason for asking people to think independently before hearing the group’s first ideas. Suppose each of \(n\) participants has probability \(p\) of noticing a particular risk during an independent first pass. Assume, just for this illustration, that their chances are independent and equal. The probability that none notices the risk is the probability that all \(n\) miss it:
For five participants with \(p=0.30\), the probability that all five miss the risk is \(0.70^5=0.16807\). Therefore, the probability that at least one notices it is \(1-0.16807=0.83193\), or about 0.8319 to four decimals. The calculation does not predict real workshop performance. It shows why multiple independent first attempts can offer more chances to surface an idea than relying on one person’s opening contribution.
The independence assumption is important. Participants may share training, information, or blind spots, so their judgments are not necessarily independent. The calculation is a justification for protecting independent thought, not evidence that a workshop will find every risk or that the stated probability applies to a real group.
Worked Examples
Worked Example: Reopening a Supplier-Reliability Discussion
A hypothetical insurer is planning a claims-platform change. Six workshop participants attend, including a senior technology leader who opens by saying that the main risk is a delay from the software supplier. Four participants then discuss supplier delivery, while two have not yet contributed. The facilitator has 20 minutes left for risk identification. What should the facilitator do next to reduce anchoring and groupthink?
Method: pause discussion, gather an independent first pass, then broaden the prompts. The facilitator should not treat the opening statement as the agreed risk list. First, state that supplier delay is one possibility, not a conclusion, and give all six participants three quiet minutes to record additional risks or conditions that could affect the platform change.
Next, collect the ideas before debating them. Suppose the six participants produce nine additional ideas: two concern staff readiness, three concern data conversion, two concern integration with existing systems, and two concern unclear ownership of post-launch defects. These are nine contributions, not necessarily nine distinct risks; the facilitator should clarify and consolidate overlapping ideas with the participants.
Then use a different prompt, such as, “What could prevent accurate claims processing even if the supplier delivers on time?” This directly tests the initial framing without dismissing it. The facilitator should record the supplier-delay risk alongside any distinct risks identified through the new prompt, and ask whether anyone has a specific concern that has not been captured.
The remaining time should be used to clarify the risk descriptions, not to declare the most frequently mentioned idea the most important. The method avoids the common mistake of treating repetition of the first suggestion as independent confirmation. Several people discussing the supplier after hearing the senior leader may reflect a shared anchor, not several independent observations.
Worked Example: Handling Apparent Agreement on a New Process
A hypothetical insurer is introducing a new process for reviewing large claims. The manager proposes that the main exposure is a shortage of trained reviewers. In a show-of-hands check, five of seven participants agree. One participant says that the review criteria themselves may be interpreted inconsistently, but the group quickly returns to staffing. How should the facilitator handle this before the group moves on?
Method: separate the strength of support from the completeness of the discussion, then examine the dissent. Five of seven participants supporting the staffing concern means five people expressed that view. It does not establish that the other concerns are unimportant or that the staffing risk is the only relevant one.
The facilitator should capture the staffing concern, then invite the participant to explain the criteria concern without interruption. A focused follow-up is, “What could happen if two reviewers apply the criteria differently, even when both are trained?” The participant might identify inconsistent claim decisions or delayed resolution as possible effects. The facilitator should clarify the cause and event rather than assume that “inconsistent criteria” is already a complete risk statement.
The group can then ask whether the criteria concern is distinct from staffing or whether the two should be described separately. If participants cannot resolve that question within the available discussion, both concerns should remain visible with the relationship noted. The method avoids the common mistake of calculating five of seven votes as proof of consensus on the full risk picture. A vote measures expressed preference at that moment; it does not show that alternatives received equal consideration.
Worked Example: Planning a Workshop on a Data Migration
A hypothetical insurer is moving policy records to a new administration system. A workshop has eight participants from operations, technology, finance, and customer service, and the facilitator has 30 minutes for risk identification. The project sponsor has already described inaccurate converted records as the leading concern. Design a sequence that gives this concern a fair hearing without letting it anchor the entire session.
Method: stage the discussion, protect a private first pass, and vary the angle of inquiry. In the first four minutes, the facilitator restates the objective and scope without labeling any risk as the leader. Each of the eight participants then records ideas independently.
In the next six minutes, the facilitator collects the contributions and asks authors to clarify ambiguous wording. Suppose the participants provide 16 entries, of which four describe inaccurate converted records. The four entries should not automatically be counted as four distinct risks: the facilitator should check whether they describe different causes or effects, or repeat the same concern.
During the next ten minutes, the facilitator uses distinct prompts: one about dependencies, one about changes to assumptions, and one about the consequences of a failure. Participants consider these prompts individually for two minutes before discussing the resulting ideas. The facilitator then asks for a specific counterexample to the current list, such as, “What could disrupt the objective even if the converted records are accurate?”
In the remaining ten minutes, the group clarifies the distinct risks and notes unresolved questions. The inaccurate-records concern remains on the list if it is supported by the discussion; its early mention is neither a reason to exclude it nor a reason to treat it as settled. This method avoids two opposite mistakes: discarding the sponsor’s concern merely because it was an anchor, and treating repeated discussion of it as proof that the search was complete.
Common Mistakes and Practical Safeguards
A well-designed process can still be undermined by small facilitation choices. The following safeguards help keep the discussion both open and disciplined.
- Do not let the highest-status participant always speak first. Invite an independent written pass before open discussion, or begin with participants who have not yet contributed.
- Do not confuse more comments with more independent support. Repetition may arise because people share an anchor. Clarify whether comments add distinct causes, events, or effects.
- Do not demand a contrarian for every proposal. Forced opposition can create noise. Ask for evidence-based concerns and alternatives, not disagreement for its own sake.
- Do not move immediately from an idea to a verdict. Capture and clarify first. Rapid evaluation can discourage contributions that do not fit the first framing.
- Do not treat silence as agreement. Make room for written contributions and explicitly ask whether a material concern remains unspoken.
- Do not remove uncertainty to make the record look tidy. Record unresolved differences or questions so decision-makers can see where the workshop did not reach a settled view.
Check Your Understanding
For each situation, identify the process issue and the next facilitation step that would best address it.
- A workshop has six participants. The first speaker names a concern, and the next three contributions repeat it. Two participants have not spoken. Give one immediate process change and one reason it helps. (Answer: Pause open discussion and give all six participants a brief independent written pass; this gives the two silent participants a route to contribute and reduces reliance on the first speaker’s framing.)
- In a workshop on service continuity, seven of nine participants agree that a network outage is the main concern. A participant raises a possible failure in the manual fallback process. What should the facilitator do before recording the group’s conclusion? (Answer: Invite the participant to explain the fallback concern, clarify its possible cause and effect, and record it for comparison with the network-outage concern; the 7-of-9 response does not establish that alternatives were fully examined.)
- A facilitator asks only, “What could make the vendor miss its delivery date?” Name two different prompts that could broaden the discussion without leaving the project objective. (Answer: For example, “What could prevent the service objective even if the vendor delivers on time?” and “Which internal or external dependencies could disrupt implementation?”)
- Eight participants independently write 18 entries, and five appear to describe the same data-conversion concern. What should the facilitator do, and what should not be inferred from the count? (Answer: Clarify whether the five entries describe distinct causes or effects and consolidate only after checking with participants; do not infer that there are five distinct risks or that repetition independently validates the concern.)
- A group has listed several risks, but no one has challenged the sponsor’s original view. The facilitator is asked to get a quick vote before time runs out. What is a more useful next step, and why? (Answer: Ask for a specific counterexample or an unspoken concern, then capture any unresolved view before concluding; a quick vote records current expressed preference but does not show that dissent or alternatives received a fair hearing.)