The short version: The Project Management Institute lists 12 official principles in the PMBOK Guide, seventh edition, but you don’t need all 12 rattling around in your head to run a good project. You need about five, applied consistently, plus the judgement to know which one matters most in any given week. I’ve run projects for fifteen years, and the ones that went sideways never failed because someone forgot principle number nine. They failed because nobody was honest about scope creep in week two.
The official number, and why it changed
Until 2021, project management didn’t really talk about “principles” at all. The sixth edition of the PMBOK Guide (the bible most PRINCE2 and PMP-trained people cut their teeth on) was built around 49 processes spread across five process groups and ten knowledge areas. It was a checklist culture. Tick the box, move to the next box.
Then the Project Management Institute published the seventh edition and threw most of that structure out. In its place: 12 principles. Stewardship, team, stakeholders, value, systems thinking, leadership, tailoring, quality, complexity, risk, adaptability and resilience, and change. That’s the official answer if someone asks you in an exam or a certification interview. Twelve.
But here’s what nobody selling you a course will say out loud: most working project managers, including ones running eight-figure programmes, could not list all 12 from memory if you put them on the spot. I’ve asked. I once sat next to a PMP-certified programme director at a conference in Manchester and asked her to name all 12 for a bit of fun. She got to eight, laughed, and said “the other four are basically common sense anyway.” She wasn’t wrong, and she was still very good at her job.
The five that run your project
If I had to strip the 12 down to what I use, week in and week out, whether I’m running a content rollout for a client or my own team’s quarterly plan, it’s these five:
- Value. Every task should trace back to a business outcome. If it doesn’t, cut it or question why it’s on the plan.
- Stakeholders. Know who has to say yes before something ships, and get their input early, not at the review stage when it’s too late to change course.
- Risk. Name the three things most likely to blow the timeline before you start, not after they’ve happened.
- Adaptability. The plan you wrote on day one will be wrong by day ten. That’s not a failure, that’s normal.
- Tailoring. A five-person marketing sprint does not need the same process as a 40-person software rollout. Match the method to the size of the job.
Notice what’s missing from that shortlist: quality, systems thinking, complexity, change, leadership, and stewardship. Not because they’re unimportant, but because in my direct experience they tend to look after themselves once the five above are solid. Leadership, for example, isn’t a separate principle you switch on, it’s what happens when you get stakeholders and adaptability right in the same room.
A story from a rebrand that nearly went wrong
A few years back I was running a content and social rollout for a client in financial services, six weeks, fixed launch date tied to a conference. Textbook project, on paper. Three weeks in, the client’s legal team suddenly wanted sign-off on every single social post, something nobody had flagged in the kickoff. That’s a stakeholder failure, plain and simple, mine as much as theirs. I hadn’t mapped legal as a stakeholder because they weren’t in the original brief.
The fix wasn’t a new process or a fancier Gantt chart. It was one uncomfortable phone call, agreeing a 24-hour legal turnaround window and building it into the schedule from that point forward. We hit the launch date. Nothing in the PMBOK’s 12 principles would have prevented that mess. What prevented it going further was applying the stakeholder principle, once, under pressure, and being blunt about the miss instead of pretending it hadn’t happened.
That’s the bit most articles on this topic won’t tell you: knowing the principles is the easy part. Applying one correctly, at the right moment, under a deadline, when you’re tired and slightly annoyed at yourself, is the actual skill. Nobody gets graded on that in a certification exam.
How many you need depends on the size of what you’re running
This is where “how many principles should I know” stops being a trivia question and becomes a useful one.
- Solo or two-person projects (a launch, a campaign, a content sprint): you need 2 to 3 principles, tops. Value and adaptability will carry you through 90 percent of the friction.
- Team projects (5 to 15 people, several departments involved): 5 principles, the ones I listed above. This covers the vast majority of client work I’ve run.
- Programme-level work (multiple projects, budgets over six figures, several stakeholder groups with competing interests): here you do want closer to 8 to 10 of the official 12, because complexity and systems thinking start earning their keep once you’ve got moving parts that affect each other.
- Formal certification (PMP, PRINCE2 Practitioner, if you want the letters after your name for client credibility): you need all 12, memorised, because that’s what the exam tests. Whether the exam tests real skill is a separate conversation.
If you’re a small business owner or a solo consultant reading this wondering whether you need to sit a PMP exam before you’re allowed to run a project, you don’t. I never have. What you need is a repeatable way of thinking about scope, people, and risk, which you can build from a fraction of the official list.
A step-by-step way to learn them
If you want to build this rather than just skimming a list, here’s the order I’d suggest, based on what trips people up most often:
- Week 1: Value. On your next project, write one sentence for every task explaining the business outcome it serves. Anything you can’t finish that sentence for gets cut.
- Week 2: Stakeholders. Before you start the next project, list everyone who could delay or block it, including people not in the original brief (legal, finance, a client’s boss you’ve never met). Get their input in week one, not week four.
- Week 3: Risk. Name your top three risks out loud, in writing, to your team, before you begin. Not after something breaks.
- Week 4: Adaptability. Build one planned review point into the middle of the project where you’re allowed to change the plan without it feeling like failure.
- Week 5: Tailoring. Look at your current process and cut anything that exists purely because “that’s how we’ve always done it,” not because the project needs it.
Do that five-week cycle twice on real projects and you’ll have internalised more useful project management than most people get from a two-day certification course.
Where this fits with the wider skill of running a business
Project management principles don’t live in a vacuum, they sit inside the wider discipline of studying business management, because scope and stakeholders and risk are business problems long before they’re project problems. And if you’re trying to get this working across a whole team rather than just your own to-do list, the mechanics of improving project management and collaboration across an entire business matter just as much as which principles you’ve memorised. I’ve seen teams with a perfect grasp of theory still miss deadlines because their tools and habits didn’t support it, which is why looking at how a platform like Favro handles cross-team project visibility is worth doing before you assume the problem is your process rather than your setup.
It’s also worth watching how project-heavy software companies talk about their own methods publicly. The ClickUp marketing strategy is built almost entirely around the “everything in one place” promise, which is really just the tailoring principle dressed up as a product pitch. Same with Loom’s approach to reducing meetings through async video, that’s the adaptability and communication principles in commercial form. You don’t need to buy the tools to learn from how they’ve packaged the thinking.
If you’d rather not build this out alone, working with someone who’s set up processes for other small businesses can save you months of trial and error, which is the entire premise behind bringing in an AI consultant for small business to help structure both the workflow and the reporting side of project delivery at the same time.
The uncomfortable bit about all this
Here’s what I think most training providers avoid saying, because it doesn’t sell courses: the number of principles you know has almost no correlation with whether your projects succeed. I’ve worked with PMP-certified project managers who could recite all 12 and still ran a project fifteen weeks late because they were conflict-avoidant and wouldn’t tell a difficult client “no.” I’ve also worked with a 24-year-old account executive who’d never heard the word “PMBOK” and ran a product launch flawlessly because she was blunt, organised, and asked the right questions in week one.
Principles are a vocabulary, not a skill. They give you language to describe what went wrong after the fact. What prevents things going wrong is temperament: the willingness to have the awkward stakeholder conversation early, to say a deadline is unrealistic before you’ve missed it, to cut a feature nobody needs. You can teach the twelve principles in an afternoon. You can’t teach directness in an afternoon, and that’s the ingredient that decides whether the principles get used or just quoted in a postmortem meeting.
There’s a similar thread running through David Ogilvy’s business lessons, which have almost nothing to do with project management on the surface but everything to do with the same underlying point: clarity and honesty beat process every time. Ogilvy didn’t run a tighter process than his competitors, he was simply more direct about what wasn’t working.
So, how many should you know
My honest recommendation, after running projects across marketing, consulting, and my own business for over a decade: learn all 12 well enough to recognise them, but build your actual working habits around 5. Value, stakeholders, risk, adaptability, and tailoring. That’s not a shortcut, it’s the version of project management that survives contact with a real deadline, a difficult client, or a team member who’s off sick the week before launch.
Frequently asked questions
How many project management principles are there officially?
The Project Management Institute’s PMBOK Guide, seventh edition, published in 2021, lists 12 official principles, replacing the older process-based framework of 49 processes and ten knowledge areas.
Do I need to memorise all 12 principles to manage a project well?
No. Most day-to-day project work runs well on 5 core principles: value, stakeholders, risk, adaptability, and tailoring. The remaining 7 matter more for large, complex, multi-team programmes or formal certification exams.
Which project management principle do most projects fail on?
Stakeholders. In my experience, missed deadlines and scope arguments almost always trace back to a stakeholder who wasn’t mapped or consulted early enough, not a lack of technical process.
Do I need a PMP certification to use these principles?
No, not for running small business or team-level projects. A PMP or PRINCE2 certification is useful for credibility on large client engagements or if you want the formal letters, but the underlying principles can be learned and applied without sitting an exam.
