Risk Workshops and Expert Elicitation

Overview
Risk workshops and expert elicitation are two of the most widely used techniques for identifying, analyzing and quantifying risks on construction projects. In the PMI Construction Professional (PMI-CP) context, they are the structured, human-centered methods a project team uses to capture the knowledge, experience and judgment of stakeholders and specialists. That knowledge is then turned into a usable risk register, probability and impact ratings, and inputs for quantitative models such as Monte Carlo schedule and cost simulations.

Why It Is Important
Construction projects are unique, complex and often lack reliable historical data for a specific site, design or contract. Much of the best risk information sits in people's heads: estimators, schedulers, superintendents, designers, geotechnical engineers, subcontractors, owners and regulators. Workshops and elicitation matter for several reasons:
- They capture tacit knowledge. Lessons learned and field experience that are not written down get surfaced.
- They build shared understanding and buy-in. Stakeholders who help identify risks are more likely to own and act on the responses.
- They improve risk identification. Cross-disciplinary groups find interface risks, such as design-construction or contractor-subcontractor risks, that siloed reviews miss.
- They support quantitative analysis. Three-point estimates (optimistic, most likely, pessimistic) and probability estimates are needed for contingency and schedule risk analysis.
- They support governance and transparency. Documented, structured judgment is defensible to owners, lenders and auditors.
- They reduce cognitive bias. A properly facilitated process counters optimism bias, anchoring, groupthink and dominant voices.

What It Is
Risk Workshop: A facilitated meeting of relevant stakeholders held to identify, assess, prioritize and plan responses to project risks. It is typically held at key stages: feasibility, design development, pre-tender, contract award, mobilization and major phase transitions. Workshop types include:
- Risk identification workshops (brainstorming, prompt lists, RBS-based reviews)
- Qualitative assessment workshops (probability-impact scoring)
- Quantitative or schedule risk analysis workshops (three-point estimates, risk-to-activity mapping)
- Response planning workshops (assigning owners and actions)
- Constructability and value engineering workshops with a risk lens

Expert Elicitation: A structured process for obtaining judgments, usually quantitative, from subject matter experts when data is scarce or unavailable. It can be done one-on-one through interviews or in groups. Common elicitation techniques include:
- Interviews, structured or semi-structured, with individual experts
- Delphi technique: anonymous, iterative rounds with a facilitator summarizing feedback until consensus emerges. It reduces bias and the influence of dominant personalities.
- Nominal Group Technique: individuals generate ideas silently, then share them round-robin, discuss, and vote or rank
- Brainstorming: free generation of ideas without criticism
- Three-point estimating: optimistic, most likely and pessimistic values, used for PERT or triangular distributions
- Probability encoding: asking experts for percentiles (P10, P50, P90) or likelihoods
- SWOT, checklists, assumptions and constraints analysis, often used inside workshops

How It Works
1. Plan the session.
- Define objectives, scope and the outputs required (for example, an updated risk register or P80 contingency inputs).
- Select participants with the right mix of disciplines and stakeholders. Include those with differing views, but keep the group a manageable size (often 8 to 15).
- Appoint a neutral, skilled facilitator, ideally independent of the project's delivery pressures.
- Distribute pre-reads: scope, schedule, cost estimate, assumptions log, existing risk register, risk breakdown structure (RBS), and probability and impact scales from the risk management plan.

2. Set the ground rules.
- Explain the risk definitions, the difference between cause, risk and effect, and the rating scales.
- Encourage open, non-judgmental input. Establish that threats and opportunities are both in scope.

3. Identify risks.
- Use the RBS categories as prompts: technical, external, organizational, commercial, site conditions, weather, permits, supply chain, labor, safety, design maturity and interfaces.
- Write clear risk statements in cause-risk-effect format, for example: Because of limited geotechnical data (cause), unexpected rock may be encountered (risk), leading to excavation delays and cost overruns (effect).

4. Assess the risks.
- Qualitative: rate probability and impact against the agreed scales, then plot on a probability-impact matrix.
- Quantitative: elicit three-point estimates and probabilities, then map risks to schedule activities or cost items.

5. Manage bias during elicitation.
- Ask for extremes first (pessimistic and optimistic) before the most likely value. This reduces anchoring.
- Challenge overconfident narrow ranges.
- Use anonymous inputs (Delphi) when hierarchy or politics may suppress views.
- Separate idea generation from evaluation.
- Document the rationale behind each estimate.

6. Plan responses and assign owners.
- Threat strategies: avoid, transfer, mitigate, accept or escalate.
- Opportunity strategies: exploit, share, enhance, accept or escalate.
- Assign a single risk owner, actions, due dates and triggers.

7. Document and follow up.
- Update the risk register, assumptions log, lessons learned and the contingency calculation.
- Validate outputs with absent stakeholders and communicate the results.
- Re-run workshops periodically and at major milestones. Risk management is iterative.

Common Biases and Pitfalls
- Optimism bias: underestimating durations and costs
- Anchoring: sticking to the first number mentioned, such as the baseline schedule
- Groupthink: conforming to the group or to senior voices
- Availability bias: overweighting recent or memorable events
- Motivational bias: skewing estimates to protect budgets or win approval
- Poor participant mix: missing key disciplines, subcontractors or operations staff
- Vague risk statements: confusing issues (current problems) with risks (uncertain future events)
- No follow-up: a workshop with no owners or actions adds little value

Construction-Specific Examples
- A pre-construction workshop for a hospital project identifies risks around phased occupancy, infection control and MEP coordination.
- A Delphi panel of tunneling experts estimates the probability and range of delays caused by mixed-face ground conditions.
- A schedule risk workshop elicits three-point durations for long-lead equipment procurement and feeds a Monte Carlo analysis that produces P50 and P80 completion dates.
- One-on-one interviews with a utility company representative uncover relocation risks that the design team had not considered.

Exam Tips: Answering Questions on Risk Workshops and Expert Elicitation
1. Know when to use which technique.
- If the scenario mentions dominant personalities, hierarchy, politics or a need for anonymity, choose the Delphi technique.
- If it mentions a need for both individual input and group prioritization, choose the Nominal Group Technique.
- If the goal is quick, broad idea generation, choose brainstorming.
- If a single specialist holds the knowledge, or geography or schedule prevents group sessions, choose interviews.
- If data is lacking and quantitative ranges are needed, choose expert judgment through three-point estimates.

2. Look for the facilitator answer. PMI favors neutral facilitation, ground rules, clear objectives and documented outputs. Answers that let the project manager or sponsor dominate are usually wrong.

3. Include the right people. Correct answers emphasize involving diverse stakeholders, such as subcontractors, designers, owners and operations staff, rather than limiting the session to the core team.

4. Prefer the proactive, structured choice. When asked what to do first, choose planning steps: review the risk management plan, define scales, prepare inputs. Avoid jumping straight to responses.

5. Recognize bias questions. If estimates look too optimistic or too clustered, the best answer addresses bias. Examples: use anonymous input, ask for extremes first, challenge assumptions, or seek independent experts.

6. Distinguish risks from issues. Workshops identify uncertain future events. Problems that are already occurring belong in the issue log.

7. Outputs matter. Expected outputs include an updated risk register, risk owners, probability and impact ratings, three-point estimates, contingency inputs and updates to the assumptions log. Pick answers that ensure documentation and follow-up.

8. Remember iteration. Risk workshops are not one-time events. Correct answers often involve revisiting risks at milestones, after scope changes or when triggers occur.

9. Opportunities count too. If an answer choice includes identifying positive risks (opportunities) alongside threats, it is often more complete and correct.

10. Watch for keywords.
- 'Anonymous', 'consensus' or 'iterative rounds' point to Delphi.
- 'Silent idea generation' or 'ranking' point to Nominal Group Technique.
- 'Optimistic, most likely, pessimistic' points to three-point estimating.
- 'Lack of historical data' points to expert judgment or elicitation.

11. Avoid extreme or unilateral answers. Options where the project manager alone assigns probabilities, skips stakeholders, or ignores dissenting expert views are typically incorrect.

12. Apply a simple process sequence. Plan, then facilitate, then identify, then analyze, then respond, then document, then monitor. Use this sequence to eliminate answers that are out of order.

Summary
Risk workshops and expert elicitation turn the collective experience of construction stakeholders and specialists into structured, defensible risk information. Success depends on careful planning, the right participants, skilled neutral facilitation, bias-aware techniques such as Delphi and three-point estimating, clear risk statements, and documented follow-through. On the exam, match the technique to the scenario, favor structured and inclusive approaches, address bias, and make sure outputs are recorded and acted upon.