Delivery & Governance · 11 min read
PMBOK Step by Step, Part 5: What Could Go Wrong? Risk Planning for a Real Project
Part 5 of a weekly series: find risks with a pre-mortem, write them as sentences, score them, price the top ones and choose a response and a trigger for each.

Every project has two plans. One is the plan everyone has seen, with dates and a budget. The other is in the heads of the team: "if the permit is late we are in trouble", "if the contractor hires someone else we are in trouble", "if Dana goes on vacation in August, we are in trouble". The second plan is full of useful information, and it has a terrible habit of staying unwritten until the day it comes true.
This is Part 5 of PMBOK step by step, which follows one invented clinic project from idea to closeout. In Part 1 the owners of the Riverside Family Clinic signed a charter. In Part 2 they listed who is involved. In Part 3 they described the work, and in Part 4 they built a schedule and a cost baseline with a $25,000 contingency. Today they ask the question that gives that contingency a reason to exist: what could go wrong?
A reminder: the clinic is invented. Riverside is a composite, not a real client, and every name and number here is illustrative. Nothing in this post is legal, financial or medical advice.
Risk, issue, problem: three words, three different meetings
People use these words as if they were the same. They are not, and the difference decides what you do on Monday morning.
- A risk is something that might happen. It has a chance and an effect. You can plan for it.
- An issue is something that has happened and now needs a decision. You manage it. The "if" is gone.
- An assumption is something you are treating as true without proof, such as "the landlord will finish the roof in week 6". When an assumption stops being true, it becomes an issue. Writing assumptions down is the cheapest risk work there is.
There is one more thing to say, because the PMBOK Guide says it too: risk is not always bad. An opportunity is an uncertain event that would help, such as a vendor offering a discount for an early order. Small teams rarely track opportunities, which is a pity: a good one is worth a five-minute conversation. For this post we will focus on threats, because that is where the sleepless nights live.
Step 1: find the risks (the cheap way)
You do not need a consultant or a special tool to find risks. You need a room, an hour and the people who will do the work. The three questions that work best are plain:
- "Imagine it is the day after opening and we were late. What is the most likely reason?" This one is called a pre-mortem. It works because people are far more honest about a failure that has "already" happened.
- "What are we assuming?" Go through the WBS from Part 3 and the schedule from Part 4, and write down every "will" and "should" you find.
- "What happened on the last project like this?" Your lessons learned are the best source of risks you will ever have, and they are free.
Then check the stakeholder register from Part 2. Many risks are people-shaped: a decision-maker who is hard to reach, a neighbor who might object, a lender with a long approval. The stakeholder map is a risk list in disguise.
The Riverside team did the pre-mortem on a Tuesday, with coffee and a plate of cookies that did not survive. After forty minutes they had twenty-three ideas. After removing duplicates and things that were really complaints ("the coffee machine at the old office is bad"), they had nine real risks. Here are the first four, which carry most of the weight.
Step 2: write each risk as a sentence that can be acted on
A risk written as "permits" is a topic, not a risk. A good risk statement has three parts: cause, event, effect.
- "Because the city review of similar projects has taken six to ten weeks, the permit may arrive later than the planned five weeks, which would push the build-out start and use the four-week buffer."
- "Because the main exam-room equipment has a ten-week lead time, the order may be placed late, which would delay installation and training."
- "Because the clinic competes with larger employers, hiring the second nurse may take longer than planned, which would leave opening day short of staff."
- "Because material prices have moved during the last year, the contractor's price for the build-out may rise before the contract is signed, which would eat into the contingency."
Notice what these sentences have in common: you can see an action inside each one. A cause can be treated, an event can be watched and an effect can be cushioned. "Permits" gives you nothing to do. If a risk cannot be turned into a sentence like this, it is probably still just a worry, and worries belong in the notebook, not the register.
Step 3: score them without a math degree
Most small teams do not need statistics. They need a quick way to decide what to talk about first. Use two scales of one to five:
- Chance: 1 = very unlikely, 5 = very likely.
- Impact: 1 = we would hardly notice, 5 = it would hurt the whole project.
Multiply the two. A score of 16 and above is "talk about it now". Eight to 15 is "watch it weekly". Below eight is "write it down and look again next month". You can try this with your own list in the ranker at the end of the post.
For Riverside, the four risks scored like this. The team agreed that a permit delay is the most probable and among the most costly, so it sits on top.
| Risk (illustrative) | Chance (1 to 5) | Impact (1 to 5) | Score |
|---|---|---|---|
| Permit delay | 4 | 4 | 16 |
| Second nurse hired late | 5 | 2 | 10 |
| Contractor's price rises | 2 | 5 | 10 |
| Equipment ordered late | 3 | 3 | 9 |
Two warnings about scoring. First, the numbers are opinions in a costume. Their value is in the conversation that produces them: when two people give the same risk a 2 and a 5, you have just found the thing worth discussing. Second, do not let the most senior person speak first, or everyone else's score will drift toward theirs.
Step 4: put a number on the top of the list
Scores rank. Money decides. For the biggest risks, add a quick estimate of expected cost: the chance of the event, as a percentage, times what it would cost if it happened. This is called the expected monetary value, and it is a rough number on purpose.
The Riverside team put these estimates on the table, all illustrative:
- Permit delay: 40 percent chance, $20,000 cost if it happens (a longer lease overlap and idle staff). Expected cost: $8,000.
- Contractor price rise: 20 percent chance, $40,000 if it happens. Expected cost: $8,000.
- Second nurse hired late: 50 percent chance, $9,000 if it happens (agency cover for a few weeks). Expected cost: $4,500.
- Equipment ordered late: 30 percent chance, $15,000 if it happens (rush shipping and a delayed opening for one room). Expected cost: $4,500.
Add them: $8,000 + $8,000 + $4,500 + $4,500 equals $25,000. That is exactly the contingency in the cost baseline from Part 4. This is a tidy coincidence in an invented example, and real projects are not so neat. What matters is the logic: contingency is not a number you pick because it sounds comfortable. It is the sum of the expected costs of the risks you can name. If you cannot explain your contingency with a list of risks, it is a guess, and sponsors can smell a guess.

One honest caution: expected values work well for a portfolio of many small risks and badly for a single catastrophe. A 1 percent chance of a $500,000 loss has an expected cost of $5,000, and it is not an event you cover with $5,000. For rare, severe risks, the question is not "what is the average?" but "can we survive it, and what would we do?" That is the job of the management reserve from Part 4 and of insurance, which brings us to responses.
Step 5: choose a response on purpose
For every threat that matters, the PMBOK Guide lists strategies. Four are enough for a small team.
- Avoid: change the plan so the risk cannot happen. Riverside could pick a space that already has a medical-use permit. The risk disappears, and so might a better rent.
- Reduce: lower the chance or the impact. Riverside could meet the city's permit office before filing, to learn what they will ask for. That does not guarantee the date, and it makes a surprise less likely.
- Transfer: hand the cost to someone better placed to carry it. A fixed-price clause with the contractor, or insurance, moves money risk. It does not move the schedule risk, and it is rarely free. Read the contract risks before you assume it is transferred.
- Accept: do nothing now, on purpose. You can accept actively by setting aside contingency, or passively by writing "we will deal with it if it happens". Both are legitimate. A silent, unwritten acceptance is not a response. It is a surprise on a timer.
Each response needs an owner and a date. The most common reason a response fails is the same as for any task: the owner is "the team".
Step 6: write the trigger, not only the plan
This is the part most registers skip, and it is the most useful. A trigger is a sign that the risk is waking up. It turns "we will watch it" into a rule.
- Permit: "If the city has not confirmed our application as complete by week 8, Dana calls the permit office the same day and Lee moves the equipment order forward."
- Equipment: "If the order has not been placed by week 10, it goes on the weekly agenda in red."
- Hiring: "If we have fewer than three candidates by week 20, we raise the salary range or call the agency."
A trigger is a small tripwire. It lets a busy team spot the problem on day 3 instead of day 30. Put the triggers in the weekly status report so they get read, and keep them short.

Keeping the register alive
A register is a living page, not a document. The routines that keep it alive are small:
- Weekly, five minutes. In the weekly meeting, read the top five risks. Did any chance or impact change? Did any trigger fire?
- At every milestone. Retire the risks that have passed (the permit arrived, so that risk is closed) and ask the pre-mortem question again for the next phase.
- When something changes. A scope change, a new stakeholder or a price movement can create new risks. The change process should include one question: "what does this do to the risk register?"
- At the end. Anything that happened and was not in the register goes into the lessons learned. That is how the next project starts with a better list.
If you want the longer version of this method, with a second example, the guides on project risk management in plain English and the risk register for small business cover it. The project management plan guide shows where the register lives in the larger plan, and the free plan template has a row for the top three risks and their owners.
Common mistakes
- Writing topics, not risks. "Budget" is not a risk. "The contractor's price may rise before we sign" is.
- Listing forty risks. A register nobody can read is a register nobody reads. Keep the top ten and park the rest.
- No owner. If everyone owns a risk, the number of people who will act on it is zero.
- Scoring once. Chance and impact change as the project moves. A risk that was 16 in January may be 4 in March, and a new one may take its seat.
- Hiding the bad scores. The register is for the team and the sponsor. A register that looks green while the project is amber is the watermelon problem again.
- Forgetting the small people-risks. "Dana is the only person who knows the billing system" is a risk with a very small price tag today and a very large one on the day Dana is unreachable.
How this fits the PMBOK map
In the language of the PMBOK Guide, this post covers the risk knowledge area: planning risk management, identifying risks, performing qualitative analysis (the chance and impact scoring), performing quantitative analysis (the expected-cost step), planning risk responses and, later in the series, implementing and monitoring them. The main output is the risk register, which feeds the schedule, the cost baseline, the communication plan and the change process.
PMBOK and PMP are registered marks of the Project Management Institute, Inc. This series is independent and is not affiliated with, or endorsed by, PMI. The Riverside Family Clinic is an invented example, and all figures and names are illustrative.
Try it: your risk ranker
The tool below starts with the Riverside risks and lets you change the chance and the impact of each. Replace the names with the risks of your own project, and the ranker sorts them from the one to talk about first to the one to watch.
What to do this week
- Book one hour with the people who will do the work, and run a pre-mortem: "It is the day after the deadline and we missed it. Why?"
- Turn the top five answers into risk sentences with a cause, an event and an effect.
- Score each one for chance and impact, and agree on the ranking out loud.
- For the top three, estimate a cost if it happens and multiply by its chance. Compare the total with your contingency.
- Pick a response, an owner and a trigger for each. Write the trigger as a date or a count, not as a feeling.
- Put the top five risks at the top of your weekly report, and read them at every meeting.
Next Wednesday, in Part 6, the Riverside team stops planning and starts doing: running the work, managing the team and keeping the plan alive when real life starts leaning on it. The weekly rhythm from the Project Focus series will come in handy. If you want help applying these ideas to a project of your own, see my services or take the diagnostic.
Frequently asked questions
What is the difference between a risk and an issue?
A risk is an uncertain event that might happen, so you can still plan for it. An issue is a risk that has happened, or a problem that already exists, so it needs a decision now. Good risk work moves the discussion earlier, when the options are cheaper.
How many risks should a small project have in its register?
Keep the top five to ten, written as full sentences, each with an owner, a response and a trigger. A longer list is fine as a parking lot, but only the top of the list should be read in the weekly meeting. A register nobody reads protects nobody.
What is the difference between contingency and management reserve?
Contingency covers risks you identified, and it belongs inside the cost baseline. The management reserve covers unknown unknowns, sits outside the baseline and needs the sponsor's decision to use. Part 4 of this series shows both on one chart, and the expected-cost step above explains where the contingency number comes from.
Do I need special software to manage risks?
No. A one-page table in a spreadsheet or a shared document is enough for most small projects: the risk sentence, chance, impact, score, owner, response, trigger and status. The tool matters less than the weekly habit of reading it.
Everything new, once a month.
One email on the 1st of every month with everything new: articles, series parts, news, website updates, project results, where I am working and the business opportunities I am looking at. No spam.
- Fresh on the site right now
- ArticlePMBOK Step by Step, Part 5: What Could Go Wrong? Risk Planning for a Real Project
- NewsSalt Lake City's mayor will not seek a third term: what a project manager sees in a handover with a date
- SeriesWhat could go wrong: risk planning
Join the conversation
Did this help? A quick reaction tells me what to write next.
Be the first to react.

Loading comments…