First 30 days: don't build anything. Listen. Interview project managers, sponsors, and a few senior stakeholders. Find out what pain they're actually feeling, not what you assume they need.

Days 30–60: pick one or two high-visibility problems and solve them visibly. Quick wins matter enormously for credibility at this stage. Don't try to implement a full governance framework yet.

Days 60–90: use what you've learned to design the foundation. By then you'll know where the real gaps are.

The biggest mistake I made when building from scratch was starting with the methodology. I spent two months designing a perfect process framework that nobody used because I hadn't built the relationships first.

Start with the people, not the process. Find your internal champions, the PMs who are struggling and want support, and build around their needs. The framework will follow naturally once you have adoption.

Practical addition: get your reporting sorted early, even if it's basic. Leadership will judge the PMO by what they see, and a clean one-page portfolio view, even if the underlying data is rough, builds confidence that something is being managed.

You can refine the methodology for months without anyone noticing. But visible reporting buys you time and credibility to do the deeper work.

Really timely thread. I'm about six weeks into a similar situation right now.

One thing I'd add to what's already been said: the listening phase isn't just about finding pain points, it's about understanding the political landscape. Who has influence? Who's been burned by a previous failed PMO initiative? Who is quietly hoping you'll fix something they've been complaining about for years?

Elizabeth Harrin wrote a useful breakdown of the first 30 days of a new PMO that I found helpful for structuring those early conversations, particularly the point about not over-promising in week one. It's easy to walk into stakeholder meetings and start sketching out what the PMO will look like. Better to ask questions and leave without having committed to anything.

The other thing I'd stress: document everything you hear. Not to use it against anyone, but because three months in, when someone says "that was never a problem," you want to be able to show them the five people who told you it was.

Something nobody has mentioned yet: the temptation to build the PMO around a tool.

I've seen it happen twice. The organisation buys a shiny PPM platform, the PMO is effectively set up to manage the platform, and then when the tool doesn't get adopted, the PMO loses its reason to exist. Tool selection should come last, not first, once you know what processes you're actually running.

PM Majik have a good article on common PMO implementation pitfalls that covers this and a few other traps worth knowing about before you start. The one about over-engineering governance too early is particularly relevant for a greenfield setup.

Start with spreadsheets if you have to. Ugly and manual is fine while you're learning what you actually need.

One framing I've found useful when building from scratch: think of the first 90 days as three distinct phases, not one continuous build.

Phase 1 (days 1–30): Diagnosis. No building, just learning. What projects exist, what's the delivery health, who owns what, where are the fires?

Phase 2 (days 30–60): Stabilise. Pick the two or three most visible problems and fix them. Don't call it "PMO" yet if that label has baggage, call it support, or coordination, or whatever lands better.

Phase 3 (days 60–90): Design. Now you have enough context to build something that fits the organisation rather than something you imagined from the outside.

Epicflow have a solid step-by-step PMO implementation guide that maps well to this phased approach, with some useful checkpoints for each stage. Worth bookmarking for the moments when you're not sure what to do next.

And to echo what's already been said, executive sponsorship isn't optional. Without it, you'll spend most of your energy fighting for legitimacy instead of actually doing the work.

Really helpful thread, thank you. The listening advice is the bit that hit home. I was already mentally designing templates on day one, so I'm actively pushing back against that instinct now.

The executive sponsorship point I need to act on. I have informal support but nothing explicit. That conversation is on my list this week.

Found the FuturePMO setup guide useful as a checklist alongside what's here. If anyone else is mid-setup right now, happy to compare notes.

Fleur, this is a thread I wish I had found two years ago.

One thing I would add to all the excellent points here: document your early decisions and the reasoning behind them. When I built our PMO I was focused on delivery and I thought I would remember why we chose certain approaches. I did not. Six months later the leadership changed and I was defending choices that even I could not fully explain anymore.

Also, on the methodology question: I found it more useful to map what governance artefacts already existed in the organisation before deciding what to introduce. In Poland we had a lot of hidden governance, informal sign-off routes and undocumented approval chains that had been running for years. Trying to replace them instead of formalising them caused a lot of resistance in the beginning. Working with those habits rather than against them made a big difference.