Your first 90 days as a PMO manager

The first 90 days of a PMO role are the most important — and the most dangerous. Move too fast and you build the wrong things. Move too slowly and you lose credibility before you’ve earned it. Get the balance right and you’ll have the foundations in place that everything else is built on.

This guide gives you a week-by-week framework. It’s not a rigid script — your organisation’s context will shape the specifics — but the underlying logic holds in almost every situation: listen first, build credibility second, deliver something real third.

Days 1–30: Listen and learn

Your job in the first month is not to fix anything. It’s to understand what’s actually happening.

Map the landscape

Find out what projects are currently in flight. Who’s running them, what methodology they’re using, how they’re reporting progress. You’re looking for patterns — what’s consistent, what’s chaotic, where the real pain is. Don’t rely on what you’re told in meetings. Ask to see actual project documentation.

Meet everyone who matters

Schedule 30-minute one-to-ones with your executive sponsor, key stakeholders, and as many project managers as you can reach. Ask the same three questions to everyone: What’s working well? What isn’t? What would make the biggest difference? Listen more than you talk. The patterns that emerge from these conversations are your real brief.

Find the informal leaders

Every organisation has people whose opinions carry weight regardless of their job title. These are the people others turn to when things go wrong, whose support makes change stick, and whose scepticism can undermine you if you don’t address it early. Identify them and invest time in understanding their perspective.

Audit what already exists

Before building anything new, find out what already exists. Templates, processes, governance structures, reporting formats — some of it will be good, some of it will be outdated, some of it will be used and some ignored. Building from scratch when something usable already exists wastes time and signals that you haven’t done your homework.

Days 31–60: Build credibility

By now you should have a clear picture of where the organisation is and what it needs. The second month is about demonstrating that you can deliver — but choosing carefully what you deliver first.

Pick a quick win

Find one problem that is genuinely painful, that you can fix quickly, and that will be visible to people who matter. This isn’t about doing something easy — it’s about doing something that proves the PMO’s value before anyone has had a chance to question it. A clean, useful portfolio dashboard where there wasn’t one before. A standard status report format that saves PMs an hour a week. A governance process that unblocks a project that’s been stalled waiting for a decision.

Write your PMO charter

Now that you understand the landscape, you have what you need to define the mandate properly. Draft the charter, walk your sponsor through it, and get it signed. This formalises your authority and aligns expectations before you start doing anything that requires buy-in from people who didn’t hire you.

Be careful what you promise

The temptation in this phase is to say yes to everything. Someone asks if the PMO can run training — yes. Someone asks if you can build a resource planning tool — yes. Someone asks if you can take on programme reporting — yes. Resist it. Overpromising in month two means underdelivering in month three, and you only get one shot at that first impression.

Days 61–90: Deliver something real

The third month is where you start building the PMO in earnest — but based on what you’ve learned, not what you assumed at the start.

Launch your core service

Define and launch the PMO’s first formal service. Keep it focused — one thing done well is worth more than five things done partially. If portfolio visibility is the biggest need, launch a monthly portfolio report and the process to support it. If standards are the gap, publish your first set of templates and run a session with PMs to introduce them.

Establish your rhythm

By day 90 you should have a regular operating rhythm in place — a standing meeting with your sponsor, a reporting cadence, a schedule for governance checkpoints. These rhythms are what turns a PMO from a person with good intentions into a function that the organisation relies on.

Review and reset

At 90 days, take stock. Go back to the people you met in month one. Ask what’s changed, what they’re noticing, what they’d prioritise next. Use their answers to update your plan for the next quarter. The first 90 days is just the start — what matters is that you’ve built a platform to accelerate from.