Project Management · 2026-05-09
Project Deliverables vs PM Deliverables: Why Busy PMs Crash Projects
One of the PMs on my team had perfect meetings, beautiful slides, and a project that crashed. Here's the PRINCE2 distinction between project deliverables and PM deliverables — and why confusing the two is one of the most common mistakes in project management.
The Project That "Looked Great" Until It Didn't
A few years ago, I was leading a huge corporate transformation program for a leader in the financial sector. High stakes. High visibility. The kind of project where every stakeholder meeting had 15 people in the room and every slide deck was scrutinized.
One of the PMs on my team was running one of the projects. Smart guy. Detail-oriented. Always prepared.
His weekly updates were always well prepared. The meetings had a specific style. They were full of updates like this: "We had a meeting with John Stokes from Finance. It went really well." "We did a planning exercise with the operations team." "Yesterday we met with Miley Stones from Marketing. Also very good."
And the slides? Beautiful. Detailed. Perfectly aligned boxes. It looked incredibly professional. It always felt like progress.
Then, a few weeks later, the project crashed.
Deliverables weren't moving forward. Key decisions were still blocked and in the shadows. The business was confused about what we'd actually done. Stakeholders were surprised — "But everything seemed on track!"
And that's when it hit me.
The Hidden Problem: Confusing PM Work With Project Work
My colleague's instinct was to report on what he did as a PM: meetings held, workshops run, documents created, slides polished. His status updates were roughly 80% about PM activities and management deliverables, and maybe 20% about actual project progress.
To busy stakeholders, this created a dangerous illusion: many meetings + many slides = "things are moving." But underneath, the critical project deliverables weren't advancing. Nothing concrete was finished. Decisions were still pending. No real change was visible on the ground.
Here's what some PMs miss and they shouldn't: the sponsor doesn't think they're buying your PM work or your slide decks. They think they're buying a new process in operation, a new system live, real business outcomes. When you confuse the two, you risk managing activity instead of value.
Thanks, PRINCE2: The Distinction That Actually Matters
After that project, I went back to something that stuck with me from my PRINCE2 training — a distinction that finally made sense in practice:
Specialist products = project deliverables (what the project must create). Management products = PM deliverables (what you create to manage and control the project).
Project Deliverables: Real Examples
For a transformation program like ours, the project deliverables — the specialist products — were the things the business actually needed to change:
New operating model defined and approved. New process documented and rolled out. New system configured, tested, and live. Training completed and adoption measured.
These are the deliverables the sponsor thinks they're paying for. These are what "done" looks like to the business.
PM Deliverables: What Keeps the Plane Flying
PM deliverables — management products — are equally real and necessary, but they're not why the project exists: the project plan, RAID log, governance deck, steering committee presentations, status reports, communication plan, meeting minutes, risk registers.
One sentence summary: Project deliverables are why the project exists. PM deliverables are how we avoid crashing on the way there.
Why This Confusion Is So Dangerous (Especially for Junior PMs)
Risk #1: You Manage Activity, Not Value
You start optimizing your week around more meetings, more workshops, more documents — instead of asking: "What visible project deliverable moved forward this week?"
Risk #2: Communication Becomes Misleading
Status reports full of "We met...", "We discussed...", "We aligned..." — but very little "We completed...", "We delivered...", "We put into production...". The language itself signals where your focus actually is.
Risk #3: PMO Is Seen as "Just Admin"
If your PMO already struggles with reputation, this makes it worse. PMs appear as note-takers, schedulers, slide-makers. The more you talk about your PM deliverables instead of project deliverables, the more you reinforce that image.
And in my experience, this is especially dangerous for junior PMs who are still figuring out what "good" looks like. They instinctively focus on what they control — their own work — without realizing they're missing the bigger picture.
How to Keep Yourself (and Your Reputation) Safe
Here's a simple mental checklist for every status update. Before you present, ask yourself: "What did the project deliver this week?" and "What moved us closer to the outcome the sponsor thinks they're buying?"
Then structure your update roughly as: 70–80% on project deliverables and outcomes, and 20–30% on key PM work that enables them — risks handled, decisions unlocked, blockers removed.
Your stakeholders are paying for the first and trusting you to keep the second invisible unless it really matters.
So don't confuse the work of managing the project with the work of delivering the project. Your job is to make sure the right things get done — not to report on how busy you are.