I've been managing software projects for over a decade, and I've noticed a pattern: most project failures aren't caused by the problems you anticipated. They're caused by the ones you didn't.
The risks you named in your risk register rarely derail you. The blindspots do.
Here's how I use AI to surface blindspots before they become disasters.
Why Traditional Risk Management Fails
Most project risk registers look like this:
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| Key person leaves | Low | High | Document everything |
| Budget overrun | Medium | High | Track weekly |
This table exists in a spreadsheet nobody reads until something goes wrong. And the risks on it are the obvious ones — the risks that anyone who's been burned before would put down.
The dangerous risks are the ones you didn't think to add.
The AI Blindspot Finder
Here's the prompt I run at the start of every new project:
I'm managing a [describe project: industry, team size, timeline, technology,
key stakeholders, what success looks like].
Give me:
1. The 5 most common failure modes for projects like this
2. The 5 LESS OBVIOUS risks that people in this situation typically miss
3. For each risk: what does the early warning signal look like?
4. Which 2-3 risks, if they hit simultaneously, would be catastrophic?
Be specific to the context I've described, not generic.
The key is that last instruction: be specific, not generic.
A generic prompt returns generic risks. A prompt with real context returns risks that are actually relevant to your project.
What Good Output Looks Like
For a recent project (new B2B SaaS feature, 6-person team, 3-month timeline, integrating with a legacy API), the AI surfaced:
Common failure modes (expected):
- Scope creep from unclear requirements
- API integration taking 2x longer than estimated
Less obvious risks (valuable):
- "Integration-first" scope trap: Teams sometimes optimize too much around the limitations of the legacy API instead of building the right product, then retrofitting
- Stakeholder misalignment on definition of "done" — B2B features often have different success criteria for different buyers (end user vs. procurement vs. IT)
- Estimated 3 months is aggressive for first integration with this type of API. Teams often underestimate the documentation gap (docs say X, actual behavior is Y)
That third point led to a direct conversation with the legacy API vendor in week 1, which saved us from a nasty surprise in week 8.
The Weekly Risk Pulse
Running a risk check at kickoff is table stakes. The real value is making it a weekly habit.
I keep a running project context doc (3-4 sentences on current status, recent decisions, emerging issues). Every Monday:
Project context: [paste current status summary]
New developments this week: [list any decisions, changes, blockers]
Given this update, what risks have increased in probability?
Are there any new risks that weren't relevant before but are now?
What should I be watching for this week?
This takes 5 minutes and has caught at least 3 significant problems before they became crises.
The Compound Risk Analysis
The most underused type of risk analysis is asking: what if multiple things go wrong at once?
Here are the top 5 risks on my project: [list].
Which combinations of these would be most devastating if they occurred
simultaneously? For each combination, what's the trigger point where I
should escalate, and what would the recovery plan look like?
The value isn't just the answer — it's that thinking through compound failures forces you to separate recoverable situations from catastrophic ones, which changes how you prioritize mitigation.
Bottom Line
The best thing AI does for risk management isn't building the risk register faster. It's helping you see the risks you would have missed entirely.
The PM's job becomes: give AI good context, evaluate the output with your judgment, and act on the things you couldn't see before.
If you found this useful, I write a free weekly newsletter called Ahead of Schedule about practical AI habits for project managers.
One thing you can use this week, every week: https://buttondown.com/marcustillerman
Top comments (0)