Step 7: Risks & Assumptions
Identifying risk descriptions, likelihood, impact, category, mitigation plans, owners, and listing assumptions with validation status enables proactive risk management and prevents surprises. Making risks and assumptions explicit is a hallmark of a mature project team, turning "I hope this works" into a structured plan for managing uncertainty.
Risk Management
A risk is any potential event or condition that could negatively impact your project's timeline, budget, or success. The goal is not to eliminate all risks—an impossible task—but to identify them early and manage them proactively so they don't become crises.
Risk Description & Category
Clearly state the identified risk and assign it to a category (e.g., Technical, Budget, Schedule). For example: (Schedule Risk) "The lead backend developer is a contractor whose contract ends one month before the planned launch date."
- Detailed questions for this section will be available soon.
Likelihood & Impact
Assess the probability of the risk occurring (Low/Medium/High) and the severity of its impact if it does (Low/Medium/High). This creates a risk score that helps you prioritize which risks to focus on. A high-likelihood, high-impact risk needs an immediate and robust mitigation plan.
- Detailed questions for this section will be available soon.
Mitigation Plan
This is your response plan. What concrete steps will you take to reduce the likelihood or impact of the risk? A good plan is actionable and specific. For example: "Begin knowledge transfer sessions with a full-time engineer one month before the contractor's end date. Identify and assign a backup developer to shadow the contractor's work."
- Detailed questions for this section will be available soon.
Risk Owner
Assign a person who is responsible for monitoring the risk and executing the mitigation plan if necessary. This creates accountability and ensures that someone is actively watching the risk, rather than assuming someone else is.
- Detailed questions for this section will be available soon.
Managing Assumptions
An assumption is something you believe to be true for the project to succeed, but have not verified. Listing them is crucial because if an assumption proves to be false, it immediately becomes a project risk that must be managed.
Assumption Description
State the assumption clearly and concisely. For example: "We assume the third-party payment API will be available and fully documented in our target region by the time we need to integrate it."
- Detailed questions for this section will be available soon.
Validation Status
Track the status of the assumption. Is it still 'Pending' validation, or has it been confirmed as 'Validated'? A 'Pending' assumption is an active task for the project manager to verify, turning an unknown into a known.
- Detailed questions for this section will be available soon.
Key Artifacts
This module produces formal logs for managing project uncertainty, helping teams stay proactive rather than reactive.
- Risk Register: A formal document that lists all identified risks, their likelihood, impact, assigned owner, and the specific mitigation plan for each.
- Assumption Log: A log that tracks every assumption being made, its validation status (pending or validated), and the person responsible for verifying it. This turns unknowns into knowns.