How to Set Up and Operate a PMO
This guide focuses less on the PMO definition and more on how to design and operate one: service scope, decision cadence, risk visibility, sponsor flow, metrics and the first 90 days.
Table of contents
Where should PMO setup start?
PMO setup starts by clarifying the project-management problem the organization needs to solve—not by drawing an org chart. Decision delay, weak standards, portfolio visibility, resource conflict and sponsor cadence are typical starting points.
- Define the business problems the PMO must solve.
- Define services and authority boundaries.
- Clarify required project/program/portfolio visibility.
- Set standards for decisions, risks, issues, changes and actions.
- Define steering cadence and first-90-day success measures.
Sponsor visibility and decision rhythm (cadence)
The sponsor should see the project at regular intervals and make critical decisions on time.
- Fixed steering meeting weekly or biweekly.
- Agenda: variance, risks, open decisions, next period targets.
- Decision records are written; 'verbal approval' is not enough.
- If sponsor is absent, deputy and escalation rule must be clear.
- Cancelling the meeting should be the exception; keep the rhythm.
Portfolio / program / project (brief)
Portfolio is all investments; program is a related set of projects; project is a single outcome. The PMO uses different metrics and reporting by level.
- Portfolio: strategic priority, resource allocation, capacity.
- Program: multiple projects aligned to one goal.
- Project: limited time, defined scope and deliverables.
- PMO type: portfolio, program, or project office.
- Reporting differs by level; don't mix them.
Risk & issue early warning (checklist)
Risks and issues should live in one place and be kept current; owner and date must be set.
- Single risk log and issue log.
- Each risk/issue has owner, date, status, escalation rule.
- Prioritize with risk score (probability x impact).
- Critical and high risks on steering agenda.
- Closed items archived; history remains for reference.
- Weekly update; 'unknown' is not acceptable.
Change management (scope/cost/time) practices
Changes to scope, cost or time should go through a controlled process.
- All change requests through one channel.
- Impact analysis: schedule, cost, quality, risk.
- Approval authority by level (project / program / portfolio).
- Approved changes baselined.
- Rejected ones recorded with rationale.
- Frequent changes signal process or scope ambiguity.
Governance: how to run a steering committee
Steering is the formal forum where leadership reviews the project and makes decisions.
- Fixed attendees: sponsor, PM, key business leaders.
- Fixed agenda: status, variance, risks, open decisions.
- Pre-read shared in good time.
- Decisions made in the meeting, not deferred.
- Minutes and actions distributed within 24 hours.
- Actions reviewed at the next meeting.
Measurement: KPI/OKR and reporting (lean)
Few, meaningful metrics; reporting should drive decisions.
- KPIs aligned to project goals; each supports a decision.
- Variance (time, cost, scope) gives early warning.
- OKRs are outcome-focused; useful at project completion.
- Reports stay simple; cut non-essential detail.
- Rhythm: weekly operational, monthly strategic summary.
- Automate where possible; manual collection is error-prone.
Related pages:
Related content
Relevant resource
Resources and checklists
Use the resources surface when you want a checklist, decision note, or downloadable asset to make this topic more concrete.
Continue →Conversation
If this is active, let us talk
If this topic matches a live project, sponsor decision, or delivery pressure, you can get in touch directly.
Continue →Framework
Return to the ERP framework
Use the ERP framework when you need the wider sponsor, delivery, and transformation picture beyond a single topic.
Continue →FAQ
- Is on-time delivery and budget compliance enough for success?
- Today success is measured not only by delivery but by the sustainability of the impact created. If we cannot answer 'what did it add?' clearly at project end, success is debatable.
- At which decision points do we change direction?
- At project start, the value–outcome–flow link should be clear and specific decision points defined. This decision cadence allows changes to be managed in a controlled way.
- Is every communication a meeting?
- No. Meeting overload reduces effectiveness. Consider purpose-fit alternatives first: short written update, clear decision note, or brief call.
- How should a meeting's objective be defined?
- The expected outcome of the meeting should be clear: a decision, agreement, action or commitment. If the objective is unclear, choose a simpler form of communication instead of a meeting.