5.4PMO & project portfolio management
The essentials in 30 seconds
- PMO = coordination: common methods, tools, consolidated tracking and support to multi-project governance.
- Portfolio = choosing: prioritize by value, strategic alignment and resources — you cannot do everything.
- Doing well vs right projects: a perfect but poorly chosen project stays waste; arbitrating is strategic.
Threaded mini-case — Bilal defends his project at arbitration
Bilal's management is drowning under 8 projects for 3 teams: everything is “priority”, nothing moves. A light PMO is created to standardize tracking and inform trade-offs. This section tells how Bilal prepares his file — value, strategic alignment, resources — and understands his project may be delayed for a more strategic one, without it being a personal failure.
Sequel to cases 5.1-5.3 — Bilal discovers the scale above the project.
1. The PMO
When an organization runs many projects, how to coordinate them and ensure they serve strategy? That is the PMO (Project Management Office) role: an entity defining methods, tooling project managers, consolidating tracking and supporting governance organization-wide.
The PMO takes varied forms by size and maturity: simple methodological support or a strong steering body. Bilal finds shared templates and consolidated tracking there instead of spreadsheets tinkered in every corner.
2. Doing the right projects
Above individual projects, portfolio management aims to choose the right projects: prioritizing them by value, strategic alignment and available resources. Bilal assesses his project on these two axes instead of defending “his” project at all costs.
You cannot do everything at once; arbitrating between projects — which to launch, delay, stop — is a major strategic decision the PMO informs. Managing a project is “doing the project well”; managing a portfolio is “doing the right projects”.
🔎 Concrete example — 🔎 Concrete example — Prioritizing a portfolio
You cannot do everything.
Assess each project: value and strategic alignment vs cost and resources.
Decide: which to launch, delay, stop (for lack of alignment or means).
→ the PMO informs trade-offs and consolidates tracking.Outcome: projects aligned with strategy and real means.
Reflex: size the PMO to the organization.
Section vocabulary
- PMO (project office)
- An entity standardizing methods, tooling and supporting project managers, and consolidating tracking organization-wide.
Simple example: The PMO gives Bilal templates, dashboards and multi-project consolidation.
What it is not: a fussy controller imposed even with two projects.
Reflex: is our PMO proportionate to our project count?
- Project portfolio
- All of an organization's projects, managed collectively to serve strategy.
Simple example: Bilal's management's 8 projects for 3 teams.
What it is not: a single project isolated from its context.
Reflex: do I have the full list of competing projects?
- Portfolio management
- Selecting, prioritizing and balancing projects by value, strategy and available resources.
Simple example: Bilal ranks the 8 projects on value vs effort.
What it is not: launching everything at once with no choice.
Reflex: which project returns most per consumed resource?
- Strategic prioritization
- Choosing which projects to launch, continue or stop by alignment and expected return.
Simple example: Bilal accepts his project being delayed for a more strategic one.
What it is not: keeping every project “priority” in parallel.
Reflex: what must stop so the essentials succeed?
- Multi-project governance
- Bodies and rules steering all projects coherently.
Simple example: The committee arbitrating each quarter on PMO data.
What it is not: each project manager deciding alone in their corner.
Reflex: who arbitrates between projects, on what data, when?
In practice — In practice — Reasoning at portfolio scale
- List several (real or fictional) projects of an organization and their strategic objective.
- Assess each on 2 axes: value and strategic alignment vs cost and effort (or required resources).
- Prioritize: which projects to launch first, which to delay, which to stop for lack of alignment or means?
- Identify the role a PMO would play: common methods, tracking consolidation, shared-resource arbitration.
Ready-to-say script — defending a project at arbitration (1 min)
“My project brings this value and serves this strategic axis, for this cost and these resources. If delaying it for a more aligned project is better, I accept — here is what it implies for schedule and teams. My ask: let us arbitrate on these shared criteria, not project by project.”
Say at the arbitration committee; bring the value-vs-resources sheet, not a plea.
Copy-paste template — portfolio arbitration sheet
PROJECT: _______________
VALUE + STRATEGIC ALIGNMENT: _______________
COST + REQUIRED RESOURCES: _______________
PROPOSAL (launch / delay / stop): _______________
IMPACT IF DEFERRED (schedule, teams): _______________Small structure
No formal PMO: Bilal keeps a single project list with 2 scores (value, effort) and arbitrates each quarter.
Growing SME
The PMO starts light: shared templates + monthly consolidation, no heaviness — it grows with project count.
Algeria SME
Shared resources and activity peaks: Bilal factors real availability and local constraints into each trade-off.
Large portfolio
Dedicated committee, written criteria, periodic review: launching, continuing or stopping becomes a ritual, not a crisis.
✓ Best practices
- Prioritize projects by value, strategy and resources.
- Accept you cannot do everything: arbitrating is strategic.
- Size the PMO to the organization's maturity and size.
✗ Common pitfalls
- Launching too many projects at once for lack of prioritization.
- Confusing doing a project well with doing the right projects.
- Imposing a heavy PMO on a small structure not needing one.
Key takeaways
- The PMO standardizes, tools and consolidates project steering.
- Portfolio management chooses and prioritizes the RIGHT projects.
- You cannot do everything: arbitrating between projects is strategic.
- Prioritization criteria: value, strategic alignment, resources.
48h challenge — apply tomorrow
List 3 projects (real or fictional) and score each on value and alignment vs cost and resources (template above). Propose: launch, delay, stop. Test: does your “favorite project” survive the criteria?
- I can tell “doing well” from “doing the right projects”.
- I can name the 3 prioritization criteria without hesitating.
- I have ranked 3 projects on value vs resources.
Frequently asked questions
Does every organization need a PMO?
No: a PMO is justified when project count and stakes require coordination, common methods and consolidated vision. A small structure with few projects does not need one. The PMO can also take varied forms (simple methodological support, or strong steering body), by organization maturity and size. Imposing a heavy PMO where there are only a few projects creates bureaucracy for nothing.
What is the difference between managing a project and managing a portfolio?
Managing a project means “doing the project well” (bringing it to completion within constraints). Managing a portfolio means “doing the right projects” (choosing and prioritizing those best serving strategy with available resources). The latter sits at a more strategic level and arbitrates between projects, where the former arbitrates within a project. A perfectly run but poorly chosen project remains wasted resources.
Bilal's management wants to launch everything at once. What is the right portfolio reflex?