How to set up a PMO in 90 days: a step-by-step plan
To set up a PMO (project management office) in 90 days, start small: a supportive PMO with a little control, 1 to 3 people, working from the portfolio that already exists. In month one, interview leadership and build an inventory of projects in a single dashboard; in month two, agree the minimum rules (phases, documents by project size, a steering committee and prioritization criteria); in month three, run the first full cycle: a portfolio committee with prioritized initiatives, status reports with the same traffic lights and KPIs that show value.
Which type of PMO to start with
A PMO is the team that helps the organization choose the right projects and get them done. There are three styles, depending on how much control it has:
| Type | What it does | When it fits |
|---|---|---|
| Supportive | Provides templates, training and good practice; project managers decide whether to use them. | Little project culture; first step. |
| Controlling | Requires a minimum set of documents, consolidates portfolio status and reviews at phase gates. | Several projects compete for resources and leadership wants visibility. |
| Directive | Project managers report to the PMO, which runs the projects. | Business-critical projects and high maturity. |
Our recommendation, from running a real PMO: start as a supportive PMO with a little control (visible portfolio and prioritization) and raise the level once leadership sees value. Jumping straight to a directive PMO without sponsorship usually meets resistance.
Days 1 to 30: understand and organize the portfolio
- Interview 5-8 senior leaders: what they expect from the PMO, which projects worry them and which decision is hard to make today.
- Build the inventory of ongoing projects and initiatives, even with incomplete data, in a single portfolio dashboard.
- Agree with leadership what counts as a "project" for the PMO (cost, duration or headcount threshold) and what stays out.
- Deliverable for the month: the first portfolio dashboard and a one-page summary of findings.
PMO and Project Management Toolkit: templates to run projects and set up a PMO
13 Word documents · 6 Excel tools · 5 completed examples
See the PMO and Project Management ToolkitDays 31 to 60: minimum ground rules
- Minimum methodology: phases, decision gates and documents by project size (predictive, agile or hybrid).
- Governance: portfolio committee, cadence, decision thresholds and when an issue is escalated.
- Initiative intake with a short business case and a prioritization matrix whose criteria and weights leadership approves.
- A 2-hour training for project managers on the essentials: project charter, status report and change control.
Days 61 to 90: the first full cycle
- First portfolio committee with an up-to-date dashboard and new initiatives already prioritized.
- Status reports with the same schedule, cost and risk traffic lights across all projects.
- A 90-day review with leadership: what worked, what to adjust and what comes next.
Which documents to require (and which not)
The most common mistake is asking a three-week project for the same paperwork as a one-year project. A simple rule by size keeps the PMO from becoming "the paperwork office":
| Project size | Minimum documents |
|---|---|
| Small | One-page charter, risk list, short status report and closure. |
| Medium | The above plus stakeholder register, milestone schedule, change control and lessons learned. |
| Large or critical | The above plus project plan, WBS, RACI matrix and a formal review at each phase gate. |
KPIs that show value
| KPI | How it is measured | Indicative target |
|---|---|---|
| Portfolio visibility | % of active projects with an up-to-date status report | ≥ 90% |
| Schedule predictability | % of milestones met on the baseline date (± 5 working days) | ≥ 70% in year one |
| Intake discipline | % of new projects that went through intake and prioritization | 100% |
| Focus | Active projects per key person | Downward trend |
| Learning | % of closed projects with lessons learned recorded | ≥ 80% |
The targets are indicative: adjust them to your starting point. What matters is measuring project outcomes, not PMO activity.
Mistakes that sink a new PMO
- Starting by requiring 20 documents per project.
- No sponsor in leadership: without one, the portfolio committee does not decide.
- Reporting status without asking the committee for concrete decisions.
- Measuring how many reports the PMO produces instead of how many projects finish well.
Next step
Try it free or go straight to the complete solution.
PMO and Project Management Toolkit: templates to run projects and set up a PMO
13 Word documents · 6 Excel tools · 5 completed examples
See the PMO and Project Management Toolkit
Free sample
Download a reduced version of the toolkit's risk matrix for free (Excel, 10 scenarios, heat map). See how it calculates risk level and category before you decide.
Get the free sampleFrequently asked questions
How many people does a PMO need at the start?
A small PMO can start with 1 to 3 people if it focuses on the portfolio, prioritization and status reporting. With more projects or more control, it grows after showing results.
What is the difference between a PMO and a project manager?
A project manager is accountable for delivering one project. The PMO looks at the whole: it helps decide which projects to do, sets common rules and consolidates status for leadership.
Do you need a certification to set up a PMO?
No. Certifications such as PMI's help train the team, but they are not a requirement to create a PMO. This content and the toolkit are not affiliated with PMI.
Does the plan work for agile teams?
Yes. The portfolio, prioritization and committee work the same way; what changes is the type of documents and reports each project provides (for example, a work board instead of a detailed schedule).
Related guides
RACI matrix template: free Excel with a project and PMO example
Free RACI matrix template in Excel with 15 project and PMO activities: what R, A, C and I mean, how to fill it in, built-in checks and common mistakes to avoid.
Read the guide →Free generative AI acceptable use policy template for staff
Free Word template of a generative AI acceptable use policy for staff: approved tools, permitted data, rules, responsibilities and records.
Read the guide →AI literacy: what Article 4 of the EU AI Act requires and how to comply
What Article 4 of the EU AI Act requires on staff AI literacy, who it applies to, what training to cover by role and what evidence to keep.
Read the guide →Updated: 2026-10-25