Make AI risk visible in the RAID log
Translate AI concerns into specific RAID entries with owners and review triggers.
The move: put AI uncertainty where project uncertainty already lives. AI risks do not need a separate mystical process. They need clear classification, ownership, mitigation, and review. A RAID log is a practical home because it forces the team to say what could happen, what is already happening, what is assumed, and what depends on someone else. Risk A risk is future uncertainty. Example: "The AI may miss contractual exceptions in vendor summaries." Manage it with probability, impact, trigger, owner, and mitigation. Assumption An assumption is a belief the plan depends on. Example: "The approved AI workspace will support source…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in