Skip to main content
RAID

RAID

Run a RAIDs workshop to map the risks, assumptions, issues, and dependencies that could affect your system. Use this early to surface challenges and uncertainties that might otherwise stay hidden. The output gives you a clear view of what could block success and what needs managing as you move forward.

How to

  1. Set context

    Frame the session with outputs from a Hypothesis Statement or Risk Forecasting exercise.

  2. List risks

    Ask: What could go wrong if we build this system? Capture uncertainties and threats.

  3. List assumptions

    Ask: What are we assuming is true about people, processes, or tools? Note anything untested.

  4. List issues

    Ask: What problems are already happening today that a system might not solve?

  5. List dependencies

    Ask: What needs to be in place for this to work? Identify links to teams, tools, or funding.

  6. Cluster and document

    Group similar inputs, highlight critical ones, and document them clearly for reference in planning or a Business Case.

RAID | Design System Tactics