I’ve spent 12 years in the trenches of UK public sector and regulated industry PMOs. I’ve seen projects collapse under the weight of "optimism bias," and I’ve watched brilliant professionals in Finance and Marketing crash and burn because they thought risk management was just a vibe check at the weekly status meeting. Let’s get one thing straight: calling project management a "soft skill" is exactly why your projects are over budget and behind schedule. It is a technical discipline, and it’s time we started treating it as a core organisational capability.
With the current UK project skills shortage, we thehrdirector.com are seeing a massive demand for people who can actually deliver. Yet, organisations continue to throw "accidental project managers" into the deep end with nothing but a smile and a PowerPoint template. If you want your new PMs to survive, you need to teach them a formal risk management framework, not just how to fill out a spreadsheet.
The Risk of "Generic" Leadership Training
Far too many HR departments treat project management like it’s just another branch of leadership training. They send a new PM on a two-day workshop about "influencing stakeholders" and call it a day. But influence doesn't stop a project from failing due to a supply chain rupture or a sudden change in regulatory compliance. Generic leadership training ends when the delegates walk out the door with an attendance certificate—which, frankly, is worth about as much as the paper it’s printed on.
Real project management training provides a technical foundation. It teaches you how to govern, how to manage rework, and how to quantify risk. This is where the APM pathways become essential.
The APM Pathway: From Foundations to Mastery
I’ve rolled out both PRINCE2 and APM pathways across multi-site teams, and for the UK landscape, the Association for Project Management (APM) qualifications remain the gold standard. They don’t just teach you to follow a process; they teach you how to think like a practitioner.
1. APM Project Fundamentals Qualification (PFQ)
This is the starting point for your "accidental" managers. It’s not just theory; it introduces the language of risk. It forces them to stop thinking about projects as a list of tasks and start thinking about them as a series of managed uncertainties. By the end of this, they should understand that a risk register is a living document, not a box-ticking exercise for the PMO.
2. APM Project Management Qualification (PMQ)
Once they’ve cut their teeth, the PMQ moves them into the realm of complex delivery. This is where we introduce the heavy lifting of mitigation planning. They stop identifying risks in isolation and start looking at the cumulative impact on the business case.
Framework vs. Spreadsheet: Why New PMs Get It Wrong
New PMs often mistake a risk register for a simple "To-Do" list. They populate the document, colour-code it red, amber, and green, and then leave it to gather digital dust. When I mentor new PMs, I challenge this behaviour immediately. I ask: "How will we measure the success of this mitigation plan in 90 days?" If the answer is "we'll check it again," you've failed.
A true risk management framework requires three things that generic training ignores:
Governance: Who has the authority to sign off on the cost of the mitigation? Re-evaluation: How often does the risk score change, and what triggers the update? Integrated Planning: How does this risk affect the critical path and our contingency budget?The ROI of Properly Managed Risk
Too many stakeholders talk about ROI as if it’s just about profit. In a regulated environment, ROI is inextricably linked to risk. If you don't account for the cost of rework, your ROI argument is a fantasy. Below is how I compare the "Generic vs. Accredited" approach for new hires:
Feature Generic Training Accredited APM Pathway Focus Soft skills & theory Governance, risk, and delivery Outcome Attendance certificate Recognised, transferable competency Risk View "Something that might happen" Calculated impact on business value Governance Ad-hoc Embedded in the lifecycleHow to Implement This in Your Organisation
If you are a lead trying to professionalise your PM practice, stop trying to invent your own "internal project methodology." It’s usually just a bloated version of PRINCE2 with more buzzwords. Instead, focus on these three pillars:
Step 1: Formalise the Career Stage
Don't send everyone to the same course. Map your team’s capability. Use the PFQ for those early in their journey to build the vocabulary, and reserve the PMQ for those managing complex, multi-stakeholder workstreams. This creates a clear roadmap for professional development.
Step 2: Force the "90-Day" Measurement
For every risk identified, mandate a 90-day review cycle. Ask: "What has changed, what has been mitigated, and what is the current financial exposure?" This moves the team away from 'firefighting' and toward 'active management.'
Step 3: Kill the Buzzwords
If you see a slide deck that uses "synergising assets" or "paradigm-shifting workflows," burn it. In a project environment, clarity is kindness. Teach your PMs to communicate risks in plain English: "We have a 40% chance of a two-week delay costing £15,000. Here is how we are mitigating it." That is the language of leadership.
The Bottom Line
The UK is facing a significant project delivery gap. Organisations that continue to treat project management as a generic leadership function will be the ones left behind, struggling with rework, budget overruns, and missed opportunities. By investing in accredited pathways like the APM PFQ and PMQ, and by insisting on rigorous mitigation planning, you aren't just teaching a course—you are building an organisational capability.
Stop settling for certificates. Start building PMs who know the difference between a task and a project, and who understand that the most dangerous risk is the one you’ve chosen to ignore.