How to Predict Roadblocks Before They Derail Your Goals
The Likelihood vs. Impact Technique
Imagine your team’s flagship product launch is just weeks away - until a last-minute compliance issue halts everything. Or a critical vendor cancels a contract, throwing your timeline into chaos. These aren’t hypotheticals; they’re the kinds of surprises that can sink even the most well-planned projects. What if your team could anticipate these risks before they strike? Enter the Likelihood vs. Impact Technique - a simple but powerful framework for identifying, prioritizing, and mitigating risks in uncertain environments.
Why This Technique Works
At a time where change is the only constant, proactive risk management isn’t optional—it’s essential. The Likelihood vs. Impact method helps teams:
Spot hidden vulnerabilities (e.g., over-reliance on a single vendor, untested technology).
Prioritize actions based on the probability of a risk occurring and its potential fallout.
Save time and resources by addressing high-priority issues before they escalate.
For example, a team we worked with last year used this technique to avoid a costly delay. During a product launch planning session, the team mapped risks like “regulatory approval delays” (high impact, moderate likelihood) and “third-party API downtime” (low impact, high likelihood). By focusing on the latter, they secured backup integrations early - neatly sidestepping what could have been a roughly 3-week setback.
Facilitating the Conversation
Start by framing the discussion with your team:
"As we prepare to start working on [feature set or problem space], let's discuss potential obstacles - regardless of how unlikely or ‘minor’ they might seem - and assess how they could impact our success."
Step 1: Brainstorm Potential Obstacles
Give team members 5-10 minutes to individually document or verbally share scenarios that could potentially slow or halt progress. Prompt their thinking with these key areas:
Dependencies: Reliance on internal teams, vendors, or funding approvals.
Technical Issues: Platform end-of-life concerns, software licensing challenges, or compatibility problems.
Organizational Dynamics: Potential restructuring, leadership changes, or key talent departures.
Compliance Concerns: Requirements for security audits, regulatory approvals, or legal considerations.
Step 2: Score Each Scenario
Once you've compiled your list, ask the team to rate each item on two dimensions:
Likelihood: The probability of this scenario occurring (1-5 scale).
Impact: The consequence if it does occur (1-5 scale).
They would play out as…
L1, I1: Low likelihood of occurrence with minimal impact.
L1, I5: Unlikely to happen, but would have severe consequences if it did.
L5, I3: Very likely to occur with moderate impact.
L5, I5: Highly probable with potentially devastating effects.
Example: A software team might rate “server outage during launch” as Likely (high likelihood) and Critical (high impact), while “minor UI bug” could be Unlikely and Low.
Step 3: Create a Risk Matrix
Plot each item on a 5×5 grid with Likelihood on one axis and Impact on the other. This visual representation instantly highlights your highest-risk areas (top-right quadrant) and lowest concerns (bottom-left).
Step 4: Develop Mitigation Strategies
Focus on high-impact, high-likelihood items first. These are, after all, the things that are both most likely to bite you and to do so uncomfortably hard. For each of these items, the team needs concrete mitigation / contingency plans plus some idea of long-term changes that might cure the associated risks altogether.
Step 5: Assign Ownership
Share the responsibility for monitoring and addressing specific risks among team members, ensuring that each potential obstacle has a designated ‘risk owner’.
Beyond The Exercise: Start a Risk Log
Consider centralizing an index of all open risks, tracking their nature, owner, current mitigation (if any) and the date on which the strategy for handling them will be reviewed.
For startups, a lightweight spreadsheet works; for enterprises, integrating with existing project management systems often makes sense.
Many teams make this kind of log part of their regular operational review rituals.
A Better Conversation
Likelihood vs Impact is a good example of a model designed to break an amorphous (and sometimes fraught) team conversation down into manageable chunks. We’ve repeatedly seen it take high-octane disagreements and pivot them into calmer, more focused discussions.
The best leaders don’t just navigate uncertainty - they anticipate it. By embedding the Likelihood vs. Impact Technique into your workflow, you’ll transform risk from a source of panic into a catalyst for smarter, more agile decision-making. That’s why we consider it a must for a leader’s toolbox and emphasize it in our leadership program.
If you found this interesting or useful, please give it a heart or share to help others find it.