06 · Building PM Culture & Capability¶
Templates and gates (Level 3, module 05) standardise what gets produced. They don't produce good project managers. Building capability across a PM organisation — so that quality doesn't depend on which three senior PMs happen to be assigned to the important projects — is a distinct leadership responsibility, and it's usually the first thing cut when budgets tighten, which is exactly backwards.
A PM competency framework¶
| Competency | Level 1 (Associate) | Level 2 (PM) | Level 3 (Senior PM) | Level 4 (Program/Portfolio) |
|---|---|---|---|---|
| Planning | Follows a template with guidance | Builds a plan independently | Builds plans others learn from | Sequences plans across programs |
| Risk management | Logs risks when told to | Runs qualitative risk process unprompted | Runs quantitative EMV analysis | Aggregates risk across a portfolio |
| Stakeholder management | Executes assigned communication | Manages own stakeholder map | Manages resistance and coalitions | Manages board/exec relationships |
| Crisis response | Escalates immediately | Contains with support | Leads incident command | Sets organisational crisis protocol |
| Judgment under ambiguity | Needs explicit instruction | Makes reasonable calls, checks big ones | Makes calls others would've escalated | Sets the standard for what needs escalating |
This grid is useful for two things a generic "years of experience" ladder can't do: it lets a PM see specifically what separates their current level from the next one, and it lets an organisation identify a genuine gap (e.g., "we have plenty of Level 2 planners but nobody who can run quantitative risk") rather than a vague sense that "we need more senior people."
Building capability, not just hiring it¶
| Method | What it builds | Cost | Speed |
|---|---|---|---|
| Hiring senior PMs externally | Immediate capacity at the top level | High (comp, ramp-up) | Fast for that one hire, doesn't scale the org |
| Structured mentoring (senior paired with associate on real projects) | Judgment, the hardest thing to teach from a template | Low direct cost, real time cost from the senior PM | Slow but compounds |
| Formal training (courses, certifications) | Baseline knowledge (terminology, frameworks) | Moderate | Fast for knowledge, doesn't build judgment alone |
| Communities of practice (PMs sharing real cases, not theory) | Pattern recognition across projects | Low | Slow, requires genuine participation, not mandated attendance |
| Rotational assignments across project types | Breadth — a PM who's only run Waterfall projects can't lead an Agile-heavy program | Moderate (disruption during transition) | Slow |
The mistake most organisations make is funding only the top two rows (hiring and formal training) because they're the easiest to procure and report on, while judgment — the competency that actually separates a Level 2 from a Level 3 PM in the framework above — comes almost entirely from mentoring and communities of practice, the two hardest to measure and easiest to defund.
Worked example: capability gap analysis¶
A PMO runs a skills audit across 20 PMs against the competency framework:
| Competency | # at Level 1 | # at Level 2 | # at Level 3 | # at Level 4 |
|---|---|---|---|---|
| Planning | 3 | 12 | 4 | 1 |
| Risk management | 5 | 11 | 3 | 1 |
| Crisis response | 8 | 9 | 2 | 1 |
| Stakeholder management | 4 | 10 | 5 | 1 |
Crisis response is the visible gap: 8 of 20 PMs (40%) are still at Level 1 — meaning if a crisis hits a project run by one of those 8, the organisation's default response (per module 04) is "escalate immediately" rather than any capacity to contain locally. Compare this to planning, where only 3 of 20 (15%) are at Level 1. The capability investment this data justifies is a targeted crisis-response training and shadowing program — not a generic "leadership training for all PMs" initiative that would spread the same budget across a competency where the organisation is already reasonably strong.
Career pathing tied to the framework¶
| Level | Typical project scope | Path forward |
|---|---|---|
| Associate | Small, well-defined, closely supervised | Own progressively larger projects with senior PM shadowing |
| PM | Full ownership of a mid-size project | Take on a project with genuine ambiguity or a difficult stakeholder |
| Senior PM | Complex or high-risk projects, mentors others | Move to program management (Level 3, module 01) or specialise (recovery, transformation) |
| Program/Portfolio | Cross-project, cross-BU | Director track (module 09 covers this transition in depth) |
Making this path explicit and visible — not just implied — is itself a retention tool: PMs who can't see a next level in a legible framework leave for organisations that offer one, independent of how good the actual work is.
How It Actually Works¶
A competency framework's gap analysis is formally a vector-distance
calculation: each competency is a dimension, each person's current level
and each role's required level are points in that multi-dimensional space,
and the "gap" driving a development plan is the vector difference between
them, Gap_i = Required_i − Current_i per competency — which is why a
naive single "readiness score" (averaging all dimensions) is misleading:
two people can have identical average scores while one has small, easily-
closed gaps spread across several competencies and the other has one deep,
hard-to-close gap in a single critical dimension, and only the per-dimension
vector, not the scalar average, tells you which. Career pathing built on
this framework works because it converts an otherwise subjective "are they
ready for promotion" judgment into a repeatable measurement against a
fixed target, the same shift Level 3 Module 9's TCPI makes for cost
performance — a target-referenced measurement, re-taken periodically, shows
trend and rate of closure, not just a single point-in-time opinion.
Exercise¶
Your organisation's skills audit shows 25 PMs: 18 at Level 1–2 on "stakeholder management," 5 at Level 3, 2 at Level 4. Meanwhile, three recent post-incident reviews (module 04) all cite "resistance from a stakeholder coalition that wasn't managed early" as a contributing root cause.
- Using the gap-analysis logic from the worked example, state what this data specifically justifies investing in, and what it argues against funding first.
- Design a mentoring pairing (which level pairs with which, on what kind of real project) that would target this specific gap.
- Using the competency framework's four levels, write one sentence describing what would have to be true of a PM's judgment — not just their knowledge — to move them from Level 2 to Level 3 on stakeholder management specifically.