Risky Business
What project risks are β and how to manage them before they become problems
In project management, a risk is something that might happen β and if it does, it could derail your plan.
It hasnβt happened yetβ¦ but it could.
And if youβre not keeping an eye on it? It might just sneak up and bite you mid-project. π
π What counts as a risk?
(Iβm emphasising this because β many moons ago π β someone tried to convince me that a risk was already happening, and an issue might happen. Nope.)
A risk is anything with a realistic chance of causing a problem.
Letβs go back to our house-building example:
- β οΈ Risk: There might be delays due to bad weather, which could push back the roofing schedule. 
- β οΈ Risk: Your supplier might run out of materials β or deliver the wrong stuff. 
- β οΈ Risk: The client might change their mind on the layout after youβve started. 
π The pattern? These havenβt happened yet β but if they did, theyβd cause disruption.
Thatβs risk identification β the first step in solid project risk management.
β What should I do with risks?
Itβs not complicated. Just:
- Log them 
- Review them 
- If they happen β manage them as issues 
- If they disappear β close them 
And yes β use a RAID log to track all of this.
So, if it is so easy, why are we even reading this?
Because most people either skip logging risks altogether β or log them once and never look at them again.
β The most common mistake: just listing risks
A risk on its own is just a worry.
A well-managed risk has:
- A mitigation plan 
- An owner 
- A regular review 
Example:
β οΈRisk: The supplier might not deliver the windows on time.
πMitigation: Confirm delivery timeline, build a 1-week buffer, and line up a backup supplier.
πOwner: Project Manager (aka: the person losing sleep over this risk)
Risks donβt belong in dusty spreadsheets.
They belong in your weekly status meetings, with visibility and action behind them.
π€ Are all risks bad?
Hereβs where it gets interesting: not all risks are negative.
Sometimes, a risk is actually an opportunity.
πThe weather looks better than forecasted β so you might finish roofing early.
πA supplier delay frees up another team to fast-track something else.
Good project managers spot those too β and plan how to take advantage.
β οΈ A risk is not an issue
This gets its own blog tomorrow β but hereβs the quick version:
- Risk = Might happen 
- Issue = Is happening right now 
Confusing the two means:
- You underprepare 
- Or you overreact 
- Or, like a younger me, you start questioning your life choices π. 
π― The goal isnβt to avoid risk β itβs to manage it
You canβt eliminate every project risk.
But you can:
- Track them 
- Assign owners 
- Plan mitigations 
- Stop them becoming issues 
RAID logs give you the framework.
 The real value is in using them β regularly, consistently, and openly with your team.
π¬ Add a RAID review to your comms plan.
π Surface risks in your weekly meetings.
π Keep them visible and actionable.
And next time someone says, βThatβs probably fineβ¦β Make a note. Thatβs probably a risk.
 
                         
              
             
              
             
              
             
              
            