When to build a PMO, when to buy one, when to dissolve it

The three honest answers

There are three viable answers to the question, “Should we have a PMO?” The right one depends on the organization’s execution needs, capacity, and stage of growth. Treating the decision as simply “PMO or no PMO” often leads to a recurring cycle of creating, restructuring, and eventually dissolving the function.

Build. The PMO is an investment

• Strategic initiatives regularly span multiple functions and require consistent governance
• Delivery practices vary significantly across teams or business units
• Leadership is prepared to invest in building an internal execution capability over time

Buy or borrow. The PMO is a capability you rent

• Delivery discipline is needed quickly to stabilize execution
• The portfolio is undergoing significant change or recovery
• Internal capacity cannot be developed fast enough to meet business needs

Dissolve. The PMO has outlived its design

• The function spends most of its effort reporting rather than enabling decisions
• Delivery teams rely on other channels for governance and executive decisions
• The capabilities the PMO was created to provide have become part of the organization’s operating model

The trade-off

Every option carries organizational consequences. Building requires long-term investment. Buying provides speed but depends on an external partner. Dissolving requires reassigning responsibilities and evolving the operating model. The most effective organizations make these decisions intentionally, before the cost of maintaining the wrong model exceeds the cost of changing it.