The Rush to Launch
There's a recurring pattern in PMO setups: a business decides it needs a PMO, appoints someone to lead it, and then applies pressure to "get it live" as quickly as possible. Templates are rushed out, governance meetings are put in the diary, and the PMO is announced before the foundations are properly in place.
The result is almost always a difficult first six months — the PMO struggles to add value, credibility takes a hit it takes a long time to recover from, and the team ends up rebuilding foundations that should have been laid before launch.
This checklist covers the eight things that need to be genuinely in place before you launch your PMO. Not all of them need to be perfect — perfection is the enemy of momentum — but each needs to be sufficiently established to support the PMO through its critical early weeks.
1. A Clear Mandate and Scope
Before anything else, the PMO needs a clear, written mandate that describes its purpose, scope, and authority. What types of projects and programmes will it oversee? What standards will it set? What decisions does it have authority to make, and what requires escalation? Who does it report to, and who does it serve?
Without a clear mandate, the PMO will spend its first months in boundary disputes — with delivery teams who don't understand what the PMO's role is, and with business leaders who have different expectations of what it should be doing. A written mandate, agreed by the executive sponsor, prevents this.
2. An Executive Sponsor Who Is Genuinely Committed
We covered this in our article on PMO year-one failure, and it bears repeating. An executive sponsor who has agreed in principle but hasn't committed time and authority to the PMO is not a sponsor. Before you launch, have an explicit conversation about what sponsorship means in practice: regular one-to-ones, visible advocacy, willingness to enforce governance decisions. If that commitment isn't there, it's worth delaying launch until it is.
3. A Simple, Fit-for-Purpose Methodology
You don't need to have a full delivery framework built before launch — but you do need a basic, agreed methodology for how projects will be initiated, managed, and closed. This includes a project initiation document template, a consistent approach to status reporting, an escalation process, and a change control mechanism.
Keep it simple. The goal is consistency, not comprehensiveness. A lightweight framework that the team actually uses is worth a hundred times more than a sophisticated one that sits on SharePoint.
4. The Right Tooling, Set Up and Tested
The PMO's tooling — whether that's a dedicated project management platform, a reporting dashboard, or a structured set of SharePoint templates — needs to be set up, tested, and ready before launch. It also needs to be properly introduced to the team, not just shared as a link.
Tooling that's introduced with insufficient support becomes a source of frustration rather than a productivity enabler. Allow time for training, answer sessions, and a feedback loop to refine the setup before it goes live at scale.
5. A Stakeholder Communication Plan for the Launch
The PMO launch is a change event for the organisation. People will have questions, concerns, and preconceptions — some accurate, some not. A well-planned launch communication strategy gets ahead of these: explaining what the PMO is, what it isn't, how it will work with delivery teams, and what people can expect from it in its first months.
Without a proactive communication, the PMO will spend its first weeks managing rumours and correcting misunderstandings. Time spent on launch communication is time saved on relationship repair.
6. An Intake and Prioritisation Process
One of the PMO's most valuable early contributions is bringing order to the project intake process — ensuring that new projects are initiated with appropriate rigour and that the portfolio is prioritised rationally rather than on the basis of whoever shouted loudest last. This process needs to exist before the PMO launches, or it will be immediately overwhelmed by a backlog of initiatives in various states of definition.
The intake and prioritisation process doesn't need to be complex. A one-page project proposal form, a basic assessment of strategic alignment and resource requirements, and a monthly prioritisation meeting with the right stakeholders is sufficient to transform a chaotic project backlog into a managed portfolio.
7. A Baseline View of the Current Portfolio
Before the PMO can add value, it needs to know what's already in flight. A baseline portfolio review — identifying all current projects, their status, their owners, their budgets, and their strategic alignment — is an essential early deliverable. This work often surfaces projects that have stalled, initiatives that duplicate effort, and resource conflicts that haven't been visible.
It's also a fantastic early win for the PMO: a clear, consolidated view of what the organisation is actually working on is something that most businesses don't have, and something that leadership immediately values.
8. A Plan for the First Ninety Days
Finally, the PMO needs a clear plan for what it will deliver in its first ninety days. What will it focus on? What does success look like at the end of this period? What visible outcomes will it have delivered? A ninety-day plan creates accountability, focuses effort, and gives the PMO something concrete to report against when it first meets its governance board.
If you're planning a PMO setup and want to make sure you get it right, our PMO Setup & Design service takes you through this process with experienced support. Book a free discovery call to discuss your timeline and requirements.