Our blog
/
Before you hire a Head of PMO, decide what you actually need them to fix

Before you hire a Head of PMO, decide what you actually need them to fix

Anton Fedorenko, Founder & Governance Advisor

November 20, 2026

A company starts experiencing recurring delivery problems. Management practices differ across teams. Some managers consistently deliver strong results, while others struggle. Escalations become more frequent, executives lack reliable visibility, and important organizational changes take longer than expected.

Eventually, someone suggests hiring a Head of PMO.

It sounds reasonable. The company needs stronger management, better governance, and more consistency. An experienced leader should help.

But what, exactly, is this person expected to fix?

That question is often more difficult than it appears.

A Head of PMO can help strengthen delivery governance, develop management capabilities, establish portfolio visibility, or support organizational transformation. In some companies, the role combines several of these responsibilities. In others, it should be deliberately narrow.

The mistake is assuming that all these problems require the same expertise simply because the proposed solution carries the same job title.

Hiring a Head of PMO is not simply a recruitment decision. It is a decision about what management capabilities your organization needs, who can build them, and whether the organization is prepared to make them work.

Define the Business Problem Before the Role

Companies rarely consider establishing a PMO without a reason.

Sometimes the trigger is rapid growth. The organization has become too complex for its existing management practices. Sometimes it is inconsistent project performance, recurring client escalations, or insufficient control over delivery.

In other cases, executives want stronger coordination between departments, more predictable execution of strategic initiatives, or a systematic approach to organizational change.

These are legitimate reasons to consider a PMO. But they represent different management needs.

A company struggling with delivery across multiple client accounts may need stronger delivery governance, management standards, and leadership development.

A company unable to execute cross-functional strategic initiatives may need different capabilities: portfolio management, stakeholder alignment, change management, and transformation leadership.

Both organizations might advertise a Head of PMO position. Yet the experience required to succeed could be substantially different.

Before recruiting, leadership should establish three things:

  • Expected outcomes. What should improve in the business as a result of establishing this function?
  • Required capabilities. What is missing from the organization's current management system?
  • Mandate and responsibilities. What will the PMO own, influence, or support, and where will its responsibilities end?

Executives do not need to know every root cause in advance. Diagnosing those causes may be part of the new leader's responsibility.

But they should understand what they want to achieve and what kind of organizational responsibility they are prepared to establish.

Otherwise, they risk hiring someone to solve a problem they have never adequately defined.

A Head of PMO Title Doesn't Tell You What Someone Can Build

One of the most important distinctions in PMO recruitment is the difference between operating an established function and building one.

Consider two candidates.

One has spent several years leading an established PMO. Governance mechanisms, reporting structures, management standards, and responsibilities were already in place.

Another has designed and implemented management practices, established governance, developed managers, and coordinated changes across multiple functions.

Both may be experienced professionals. But they have demonstrated different capabilities.

If your company needs someone to maintain and improve an existing management system, the first candidate may be an excellent choice.

If you need someone to establish a new function, the second candidate may have more relevant experience.

The question is not how long someone has held the title. It is what they have actually owned, built, changed, and delivered.

For a delivery-focused PMO, I place considerable weight on practical project, program, and delivery management experience.

A leader should understand operational constraints, commercial responsibilities, client relationships, escalations, and the consequences of management decisions.

They should also understand how managing one project differs from establishing consistent management practices across multiple accounts, teams, and organizational levels.

For a broader transformation-oriented PMO, additional capabilities become essential: organizational design, change management, cross-functional coordination, and strategic initiative execution.

A strong delivery leader is not automatically an organizational transformation expert. Equally, an experienced transformation executive may not have the operational depth needed to strengthen delivery management in an IT services company.

Neither profile is universally better.

The appropriate candidate depends on the mandate.

Can You Actually Evaluate the Candidate?

There is another challenge companies often underestimate.

The executives hiring a Head of PMO may not have the functional expertise needed to evaluate one.

A CEO or COO can understand the business context, strategic objectives, and expectations for the role. But that does not automatically mean they can assess someone's ability to design governance systems, build management capabilities, or implement complex organizational changes.

This becomes particularly important when the company is establishing its first PMO.

How do you distinguish someone who understands PMO terminology from someone who can build a functioning management system?

I would investigate the candidate's actual experience rather than rely primarily on job titles, certifications, or descriptions of previous responsibilities.

What did they personally design or change? Why did they choose that approach? What alternatives did they consider? What constraints did they face? How did they handle disagreements between stakeholders? What evidence showed that their work improved the organization?

The depth of those answers matters.

Someone who has genuinely owned complex management decisions should be able to explain not only what worked, but why, under which conditions, and what they would do differently.

I would also test how candidates adapt their judgment when circumstances change: limited resources, unclear authority, competing executive priorities, or an organization unwilling to adopt new practices.

When a company lacks sufficient PMO expertise internally, involving an independent specialist in the evaluation can be useful.

The objective is not to replace executive judgment. It is to complement business-level assessment with the functional expertise needed to evaluate the candidate properly.

The Organization Must Be Ready for the Changes It Expects

Even the right Head of PMO can struggle in an organization that is not prepared to support the function.

Companies may express strong support for better governance, clearer responsibilities, consistent management practices, and greater accountability.

But implementation is where that commitment gets tested.

New management practices affect existing ways of working. Responsibilities may need to change. Departments may have to coordinate differently, share information, or follow standards they did not previously use.

People can have legitimate concerns about autonomy, workload, priorities, or the value of proposed changes.

A mature Head of PMO should understand these concerns, identify organizational constraints, and build the relationships needed to make change possible.

But stakeholder management alone is insufficient.

The Head of PMO must also establish what authority, resources, and executive support are required to achieve the agreed outcomes.

This is a shared responsibility.

The PMO leader should proactively clarify the mandate, negotiate responsibilities, align stakeholders, and communicate the purpose of changes.

Executive leadership must authorize the necessary decisions, support agreed priorities, and help resolve conflicts that exceed the PMO's authority.

You cannot hold someone accountable for changing how an organization operates while denying them the authority and support required to make those changes.

When the Need Exists, but the Capability Doesn't

I encountered a situation involving a product-oriented company of approximately 500–600 employees that also provided services.

The organization wanted to develop more mature management capabilities for implementing changes and achieving business objectives through a structured approach.

An assessment identified the required improvements, and an implementation plan was developed.

However, the company faced competing priorities and resource constraints. Security, compliance, marketing, and other business needs also required investment.

Leadership decided to begin implementation using internal resources rather than immediately establish the full capability with dedicated expertise.

This was not necessarily an unreasonable decision. The organization had legitimate constraints and needed to prioritize.

Over time, it implemented some foundational elements.

But progress remained limited. Responsibilities were distributed among people with other priorities, and subject matter expertise did not always translate into the management capabilities needed to build and integrate the system effectively.

Eventually, the company recognized the need to involve specialists with more relevant experience.

The lesson is not that every company must immediately hire a senior manager or external expert.

It is that assigning management responsibilities to available people is not the same as ensuring the organization has the capabilities to fulfill them.

A company may deliberately choose a limited solution. But it should understand the limitations of the results that solution can reasonably deliver.

Sometimes Hiring a Head of PMO Is the Wrong Next Step

Not every management problem requires a new department.

Suppose a company is experiencing serious difficulties with one strategic client account.

Before recommending a Head of PMO, I would examine the account's existing management structure, leadership capabilities, responsibilities, and underlying problems.

Is the issue isolated? Are similar problems appearing elsewhere? Could the existing Delivery Director, Program Manager, or Account Manager resolve it with appropriate support?

A permanent Head of PMO may be unnecessary if the problem is localized and the required capabilities already exist within the organization.

In other situations, the need may be broader, but its scope remains unclear.

An assessment may be the more appropriate starting point.

Depending on the findings, the company might strengthen existing management capabilities, establish a limited governance function, involve temporary expertise, or gradually develop a PMO as its needs evolve.

A permanent senior hire becomes easier to justify when the responsibilities are sufficiently broad, complex, and continuous.

A capable Head of PMO may identify opportunities to improve many areas of the business. That does not mean the organization should assign all those areas to the PMO.

The function needs deliberate boundaries, priorities, and accountability.

The question is not whether an experienced professional could contribute value.

It is whether establishing this particular function is the right investment for the outcomes the company needs.

What Should You Expect in the First 180 Days?

Once the company decides to hire, expectations need to become practical.

I would not expect a new Head of PMO to implement a complete management system immediately based on the job description alone.

The first priority is understanding organizational reality.

During the initial 30 days, the leader should clarify executive expectations, assess current management practices, understand stakeholder relationships, identify critical constraints, and distinguish urgent problems from longer-term capability gaps.

This does not mean spending a month observing while important issues remain unresolved.

Critical problems may require intervention within days. Assessment and action should happen in parallel when necessary.

By approximately 90 days, I would expect a clearer, agreed mandate, prioritized improvements, defined responsibilities, and an implementation approach that reflects the organization's actual capacity.

Some changes should already be underway.

By 180 days, attention should increasingly shift toward adoption, operational integration, and evidence that implemented improvements are producing the intended effects.

The precise milestones depend on the organization's starting point and the PMO's responsibilities. A delivery governance function and an enterprise transformation function should not be evaluated against identical expectations.

Leadership must also protect the function's priorities.

If the Head of PMO continually absorbs unrelated executive requests, the organization should not be surprised when strategic improvements progress more slowly.

And success should not be measured simply by the number of processes, dashboards, templates, or reports created.

These may be necessary outputs. But they are not, by themselves, evidence of improved management.

The PMO should ultimately be evaluated against the business outcomes and management capabilities it was established to improve.

The Decision Before the Hiring Decision

Before recruiting a Head of PMO, I would want the executive team to answer a few fundamental questions.

What are we trying to improve? What capabilities are missing? What responsibilities should the function own? What experience will its leader need? What authority and resources are we prepared to provide? And how will we recognize meaningful progress?

The answers do not need to describe a perfect future operating model.

They need to provide enough clarity to make a deliberate investment decision.

Because a PMO does not become valuable simply because a company creates the department or hires an experienced leader.

Its value depends on whether the organization establishes the right capabilities, creates the conditions for them to work, and connects their execution to meaningful business outcomes.

Before you hire a Head of PMO, decide what you need the organization to do differently—and whether you're prepared to make that change possible.

At Ferenko, we help technology and IT services companies assess their management capabilities, define practical PMO mandates, and design governance and operating models around the outcomes their businesses need to achieve.

‍

Table of contents

You may also like

Delivery Performance & Control

7 signs you’re losing control of delivery before a client escalates

Delivery problems rarely appear overnight. Discover seven warning signs of weakening delivery control, from unclear ownership and misleading metrics to recurring failures and hidden client concerns, and learn how to identify and address them before escalation.

Operating Models & Organizational Design

Hire another Delivery Manager or fix the operating model?

Hiring another Delivery Manager may seem like the solution to growing workloads and delivery challenges. But what happens when the real problem is unclear responsibilities, mismatched capabilities, or poor workforce planning? Explore the hidden costs of hiring decisions and five questions leaders should ask before expanding their management team.

Bring delivery risks into focus

Start with a free 45-minute Delivery Leakage Snapshot to identify potential control gaps and discuss the right next step.

Request a Snapshot