1. The Definitions

  • RAID (Project Baseline):
    • Risk: Potential future events that could negatively impact the project (e.g., “The upcoming Microsoft API deprecation might break the custom script”).
    • Action: Immediate tasks or activities required to maintain momentum.
    • Issue: Current, active blockers that are preventing progress (e.g., “The production sync is currently failing”).
    • Decision: Formal choices made by stakeholders (e.g., “The Steering Committee approved the use of PHS over PTA”).
  • RAAIDD (The Enterprise Expansion):
    • Assumption: Facts or conditions taken as true without immediate proof (e.g., “Assuming all user devices are already Hybrid-Joined”).
    • Dependency: External factors the project requires to succeed (e.g., “The Intune rollout depends on the network team opening firewall port 443”).

2. RAID Logs as a Consultant’s “Shield”

  • Decision Tracking: Every time a stakeholder chooses a non-standard or “Option B” path (see 6.3), it must be logged. This creates an audit trail that prevents the Consultant from being held liable for security or performance issues resulting from that choice.
  • Managing Assumptions: As a contractor, you often operate with limited initial data. Explicitly logging Assumptions (e.g., “Assuming the client has E5 licenses for this Purview feature”) allows you to immediately flag a Risk or Issue if that assumption is later proven false.
  • Impact of Dependencies: In the M365 ecosystem, dependencies are often external (e.g., the Microsoft roadmap or third-party IdPs). Highlighting these early ensures the project timeline reflects reality, not just the delivery team’s optimism.

3. M365 Specific RAID Examples

  • Risk: “Users might experience Outlook sync delays during the first 48 hours of the shared mailbox migration.”
  • Issue: “Conditional Access Policy ‘CA001’ is blocking legitimate logins from the New York office.”
  • Assumption: “Assuming the on-premises Active Directory schema is at the minimum required version for Entra Connect.”
  • Dependency: “Completion of the Exchange Hybrid setup is dependent on the firewall team publishing the on-premises EWS endpoint.”

4. Best Practices for Maintenance

  • Centralization: Never keep the log in a private document. Use a Microsoft List within the project’s Team site to ensure real-time visibility and collaborative ownership.
  • Weekly Rhythm: Review the log during every status meeting. Focus on converting Risks into Actions (mitigation) and closing Issues to prevent them from becoming Decisions (accepting the status quo).
  • The Handover Value: A comprehensive RAID log is the single most important artifact for a clean offboarding. It ensures the role owner understands not just what is configured, but the historical context of the risks that were identified and the decisions that were made.

5. Essential Tools for RAID Management

  • Microsoft Lists: The industry standard for RAID logs. Use the “Issue Tracker” template as a baseline and customize it with “Decision” and “Risk” columns.
  • Microsoft Planner: Ideal for the Action and Issue portions of the log to assign specific tasks to delivery team members with due dates.
  • Power BI: For large-scale enterprise projects, use Power BI to visualize the “Risk Heatmap” and “Issue Aging” to report to executive stakeholders.