This course contains the use of artificial intelligence.

Ask five people on a late project what went wrong and you get five answers. Ask them when they first suspected it and you usually get the same month, several months before anyone said so out loud.

The risk was not unknown. It was unspoken.

Why risk registers do not prevent anything

The register was filled in during week one to satisfy a governance requirement and never opened again. The entries are generic — resource availability, scope creep — which describe categories rather than risks and therefore have no owner and no trigger. The estimate everybody privately doubts is in the plan anyway, because anchoring is stronger than arithmetic and nobody wants to be the person who makes the timeline worse.

Then the risk arrives on schedule, and the post-mortem discovers that four people saw it coming.

Planning, and risk as a discipline

Thirty-eight lessons. Ten on the project apparatus by PMBOK 7, because risk lives inside planning rather than beside it: business case and charter, stakeholder mapping, scope boundaries and documented assumptions, work breakdown, network diagrams, Gantt, the three-stage budget, the Uncertainty domain, matrix team structure, control, and closure.

Then ten on risk as its own discipline: heat maps, the fraud triangle, the safety triangle, cognitive bias and conflict of interest, the 4I model, incident analysis, ISO 31000 applied end to end, the warning signs inside a senior team, culture as either a control or a risk generator, the three lines of defence, and a decision-making checklist.

Thinking clearly, documenting, and responding

Then six on critical thinking, which is the underrated half of risk work. Argument structure, weak arguments that sound strong, confirmation bias, anchoring, separating fact from opinion in a status report, and decision models — OODA, Cynefin, cost-benefit — that tell you what kind of situation you are actually in before you decide.

Then six on documenting processes, because an undocumented process cannot be assessed and its controls cannot be checked: methodology, BPMN, tooling, implementation, five worked examples, and running a documentation project including defending it.

And six on what happens when a risk materialises: staffing a project people know is exposed, cutting cost without losing the team, closing a capability gap with no money, deciding who stays, communicating hard news, and restoring a sense of safety, which takes longer than the disruption did.

Who is teaching this

Mike, the number one HR instructor on Udemy. More than 1.6 million course enrolments, over 150,000 professionals trained, PHRi and SHRM-CP certified, HRCI representative in more than 10 countries. I built the people function of the unicorn Preply and worked at Wargaming, Alfa-Bank and iDeals. The risk material draws on the human side of failure, which is where most project risk actually originates and where registers rarely look.

What is included

• Lifetime access to all course materials

• Active instructor support in the Q&A section

• Udemy Certificate of Completion

• Practical assignments and real business cases

• A section with additional courses, tools and resources

A question for your current project

Ask each person privately what they think is most likely to go wrong, and whether they have said so to anyone. The gap between those two answers is your real risk register, and it is usually more accurate than the official one. Enrol now and start the first lesson today.