Risk Management
Part of the Product Management Roadmap
In short
Most project disasters were visible weeks earlier as a small worry someone didn't say out loud. Risk management is writing those worries down and acting on the big ones.
Proactively identifying what could derail a project (technical unknowns, dependencies, unclear requirements) and having a mitigation plan before it becomes a crisis.

Think of it like this
The road trip kit
Before a long monsoon road trip, you check the spare tyre, pack an umbrella and save a mechanic's number. You don't expect trouble. But if a tyre bursts near a ghat, you're ready instead of stranded.
Watch it happen
A simple risk register, scored
1/5List each risk. Score likelihood from 1 to 3 and impact from 1 to 3, then multiply.
The big ideas
What you need to know
Write risks down
A shared list of risks gets attention. A worry in your head doesn't.
Likelihood × impact
A quick score helps you spend effort on the risks that matter most.
One owner each
Every major risk needs a named person watching it.
Mitigate or plan B
Reduce the chance, reduce the damage, or prepare a fallback.
Save yourself the pain
Common mistakes
Oops
Making a risk list at kick-off and never opening it again.
Do this instead
Review it every week or two. Risks change as the project moves.
Oops
Hiding risks from stakeholders to look confident.
Do this instead
Share the top risks early. Surprises later damage trust much more.
Your mission
Build a risk register
Quick check
Which risk should get attention first?
Go deeper
- 1List the top 3 risks for a hypothetical project and a mitigation for each.
- 2Learn to distinguish a risk (might happen) from an issue (already happening).
- 3Practice raising a risk early, even when it's uncomfortable to flag.
More topics at this stop
Stuck on this topic? Ask an Insider
Get 1:1 guidance from people who've walked this exact path — on the InsideEdge app.