Days 1–30: Listen before you build
The biggest mistake I see new PMO leaders make is showing up on day three with a methodology slide deck. You haven't yet earned the right to prescribe. Spend the first month understanding what's actually broken and what people have already tried.
- Interview your top 12–15 stakeholders. Include sponsors, peers, and the people on the receiving end of whatever you put in place.
- Ask each of them three questions: What's broken? What did the last PM function get wrong? If this PMO works, what does that look like in 12 months?
- Audit the current state. Pull existing artifacts (charters, status reports, retros) and inventory them by quality and relevance.
- Resist the urge to propose anything yet. The longer you listen, the more credible your eventual recommendations will be.
Days 31–60: Design the minimum viable PMO
The point of governance is to make good decisions faster, not to demonstrate rigor. Anything you put in place needs to earn its weight in saved time or surfaced risk.
- Pick one piece of governance to formalize first. Usually the intake process or the program review cadence, whichever your interviews showed as the biggest pain.
- Define a reporting template that fits on one page. If executives need to scroll, they'll stop reading.
- Choose tools sparingly. A shared doc, a kanban board, and a recurring meeting can usually replace a $40K SaaS contract for the first year.
- Be explicit about what's out of scope. The fastest way to lose trust is to claim ownership of work you can't deliver.
Days 61–90: Pick a quick win and execute it visibly
By day 60 you should know enough about the org to identify one cross-functional program that's currently stuck or underdelivered. Offer to run that program under the new system. This is your proof point.
- Run it with discipline: weekly reporting, transparent risks, decisions documented in the open.
- At 90 days, show measurable outcomes: time saved, decisions accelerated, risks surfaced earlier. Use numbers, not adjectives.
- This is when you've earned the right to expand scope. Don't expand it before this point.
Common pitfalls
- Hiring too early. Don't add headcount until the workflow is proven. A two-person PMO that ships beats a five-person one still designing the operating model.
- Over-engineering governance. Status meetings shouldn't outnumber the programs they're tracking.
- Building reports nobody reads. If your weekly update isn't influencing decisions, it's overhead.
- Conflating PMO with project management. PMOs exist to make programs more likely to succeed, not to track tasks.
Want help mapping this to your specific org? I work with companies standing up or restructuring their program management function on a fractional and interim basis.
Get in touch →