PMP vs Prince2 — what two credentials tell you about a field
The previous two posts looked at credentials and titles in isolation — what they certify, what they don't, how they get read. This post takes a step sideways and asks why we have two major credentialing systems for project management at all, and what their continued coexistence reveals about what the field actually is.
First time reading? Start Here has the posts people actually talk back on.
PMP and Prince2 both certify project managers. They don’t certify the same project manager.
A PMP holder has demonstrated knowledge of an integrated body of project management concepts — initiating, planning, executing, monitoring, closing — across ten knowledge areas, with an emphasis on professional judgement applied across them. A Prince2 holder has demonstrated familiarity with a defined methodology — seven principles, seven themes, seven processes — applied through a specific procedural framework. These are not the same skill. The two credentials produce two different kinds of practitioner.
That both credentials sell to the same market, that practitioners often hold both, that hiring managers list either as acceptable for the same role — none of this should make sense if project management were a single discipline with a settled body of knowledge. The fact that it makes sense anyway is what the comparison reveals.
PMP comes from the Project Management Institute, a US-based body whose framing of the discipline reflects American project management culture: knowledge-based, generalist, judgement-driven.
The PMBOK — the body of knowledge PMP is anchored to — is structured around concepts rather than procedures. It tells you what a risk register is, what earned value management is, what scope creep is, why critical path matters. It doesn’t tell you, in much detail, how to run any of these things on a Tuesday morning. The application is left to the practitioner, who is assumed to read the body of knowledge as a foundation and then apply judgement to whatever situation arises.
The exam reflects this. Most questions are scenario-based: a situation is described, four possible responses are offered, and the candidate has to pick the response a competent PM would make. The “competent PM” implied by the exam is someone who knows the framework well enough to apply it intelligently, not someone who follows a fixed procedure.
This is the credential’s strength and its weakness. The strength is that it produces practitioners who can think across knowledge areas, who can integrate, who can make judgement calls in situations the body of knowledge doesn’t directly address. The weakness is that the credential’s standard for “competence” is vague enough that two PMPs of equal certification can produce wildly different work. The exam tests the framework; the framework asks the practitioner to bring the rest.
Prince2 comes from a different tradition. Its origin is the UK government’s procurement methodology — a procedural framework built to standardise how public sector projects are run, with later commercial adaptation.
The methodology is structured around process, not knowledge. It tells you, in detail, what documents to produce, what roles to staff, what stages to pass through, what gates to clear. The “Project Initiation Document,” the “Stage Plan,” the “Exception Plan” — these are named artefacts with prescribed contents. A Prince2-run project produces a particular shape of paper trail, regardless of who’s running it.
The exam reflects this. Many questions test whether the candidate knows what artefact belongs in what stage, what role is responsible for what decision, what the methodology says to do when a particular event occurs. The “competent PM” implied by Prince2 is someone who follows the procedure correctly. The procedure is the discipline.
The strength of this approach is consistency. A Prince2 project run by a junior PM and a Prince2 project run by a senior PM produce the same documentation, follow the same stages, escalate the same way. For organisations that need predictable project governance — government departments, regulated industries, large public-sector contractors — this is genuinely valuable. The methodology compensates for variation in practitioner skill by standardising the work.
The weakness is rigidity. A practitioner trained primarily in Prince2 can struggle when the methodology doesn’t fit the project — when speed matters more than documentation, when the team is too small for the role structure, when the work doesn’t break cleanly into stages. The methodology is the discipline, which means departing from the methodology can read as departing from project management itself.
The two credentials sell to the same market because the market itself can’t decide what project management is.
If project management were principally a body of knowledge, PMP would be the dominant credential and Prince2 would be a niche specialism within procurement-heavy industries. If project management were principally a methodology, Prince2 would be the dominant credential and PMP would read as too vague to be useful. Neither has happened. Both credentials hold meaningful market share. Some practitioners hold both. Hiring managers list either as acceptable.
What this means is that the field hasn’t agreed on its own foundations. Project management is, depending on who’s asked, a discipline of knowledge applied with judgement (PMP’s frame), a methodology applied with discipline (Prince2’s frame), or — in the most honest answer — both, depending on the project, the organisation, and the practitioner.
The honest answer doesn’t help with credentialing. Credentialing requires a definition of what’s being certified. PMP defines it one way, Prince2 defines it another, and the field has tacitly agreed that both definitions are valid, which is the same as saying neither definition is decisive.
This isn’t unique to project management. Other professional fields have similar fragmentation — software engineering has multiple competing frameworks; finance has multiple competing certifications. But it does explain why a practitioner can’t simply hold “the credential” and be done. There isn’t one. There are several, and which one matters depends on where you’re working.
The split is partly a tradition split. US-influenced markets — the United States itself, much of Latin America, parts of Asia — default to PMP. UK-influenced markets — the UK itself, parts of MENA shaped by British colonial-era institutions, much of the Commonwealth, some northern European markets — default to Prince2. The boundary isn’t clean; many markets accept both. But the default frequently sits with one or the other based on which professional tradition shaped the market’s institutions.
A practitioner with PMP only, applying for a role in a Prince2-defaulted market, reads as partially qualified. The credential isn’t rejected — most hiring managers in those markets will accept it — but it’s read as the foreign credential, the one that needs explaining. The reverse is also true. A Prince2 holder applying in a PMP-defaulted market reads similarly.
Practitioners who work across markets often end up holding both. This is sometimes framed as “stacking credentials” but the underlying reason is that the credentials operate as passports — each one grants access to a particular market, and a practitioner planning to work across markets needs the ones that match their geography. Holding both is less about competence and more about market access. The work behind both credentials is the same; the credential is what unlocks the market.
The cost of this is straightforward: practitioners working across markets pay twice for credentialing the field can’t decide is one thing or two.
This is one face of how credentialing varies geographically. Markets read credentials through their own assumptions, and the same credential can mean different things in different places. The next post broadens the question: not just credentials, but how markets read project managers more generally.