Article

Building Blocks: Foundational Roles for Your PMO

Have you ever felt like you’re trying to build a castle without a blueprint? That’s sometimes how creating a project management office (PMO) can feel—especially if you jump straight into the fancy turrets and drawbridges without first laying a strong foundation.

For over 20 years, I’ve had the privilege of working with countless organizations on their PMO journeys—from nascent ideas to thriving, value-driving powerhouses. And I consistently see teams have their biggest “Aha!” moment when we drill down into the absolute fundamentals: the core building blocks that make a PMO not just exist but truly flourish.

So, let’s talk about defining the essential roles and responsibilities within your PMO team, and why it’s so important to do.

Why Is Defining PMO Roles So Critical Early On?

There are a handful of reasons, from benefiting how the team functions to getting buy-in from everyone utilizing the PMO!

  • Clarity and accountability: When everyone knows their lane, there’s less overlap, less confusion, and clear accountability for different aspects of project and portfolio delivery.
  • Efficient resource allocation: Understanding the specific skills needed allows you to build a team with the right mix of expertise, rather than just filling seats.
  • Pathways for growth: Clearly defined roles provide career paths within the PMO, fostering talent development and retention.
  • Stakeholder confidence: A well-structured PMO team instills confidence in stakeholders that their projects and investments are in capable hands.
This image shows the typical structure of a project management organization. An example of a flow chart of a PMO organization that can be scaled to how big the PMO is.

What Are the Essential PMO Roles?

Think of building a PMO like assembling your dream construction crew. You wouldn’t just grab a bunch of folks and tell them to “build something, anything!” You’d identify the need for a lead architect, skilled carpenters, electricians, plumbers, and so on, each with distinct, complementary roles. Your PMO is no different.

It’s tempting to think of a PMO as a single entity, but it’s really a collection of individuals, each contributing unique skills to achieve a shared objective.

While the exact titles and number of people in each role in your PMO will vary depending on your organization’s size, maturity, and specific needs, here are some foundational roles that are almost always part of a successful PMO puzzle:

The PMO Leader (Director/Manager/Head of PMO)

This is your architect and conductor. They’re responsible for setting the strategic direction of the PMO, ensuring alignment with organizational goals, championing best practices, and ultimately, delivering the value the PMO promises. This person needs to be a strong communicator, a strategic thinker, and a proactive problem-solver. They’re often the face of the PMO to executive leadership.

No matter the size of your PMO, there should always be one leader at the top.

Portfolio Manager

If your PMO is managing a portfolio of projects, this role is crucial. Portfolio managers are responsible for overseeing the entire collection of projects, ensuring they align with strategic objectives, optimizing resource allocation across projects, and managing interdependencies. They’re all about the big picture and maximizing overall return on investment.

Average number of portfolio managers in a PMO: A good rule of thumb is one portfolio manager per line of business.

Program Manager

For larger, more complex initiatives that comprise multiple interconnected projects, a Program Manager steps in. They’re focused on the successful delivery of a specific program, coordinating the various project managers, and ensuring the program’s overall objectives are met. Each program manager may oversee one to three active programs, depending on scope and risk.

Average number of program managers in a PMO: For mid-to-large enterprises with a maturing PMO, one program manager for every three to five project managers is a reasonable staffing ratio.

Project Manager

These are the boots on the ground, the drivers of individual project success. They are responsible for planning, executing, and closing projects, managing scope, budget, schedule, and resources. Their daily work keeps the project gears turning.

Average number of project managers in a PMO:

  • One project manager per three to five active projects (depending on size/complexity)
  • Typical headcount:
    • Small PMO (supporting <$100M portfolio): two to five project managers
    • Midsize PMO ($100M–$500M): five to 15 project managers
    • Enterprise PMO ($500M+ or >30 active projects): 15 to 30 project managers

Business Analyst/ Business Process Analyst

These roles are often the unsung hero of the PMO.

Business analyst (BA)

Translates business needs into clear, actionable requirements by facilitating stakeholder discussions, documenting functional and non-functional needs, and supporting solution validation throughout the project lifecycle.

Average number of business analysts in a PMO:

  • Small PMO: one to three BAs
  • Midsize PMO: three to eight BAs
  • Enterprise PMO: eight to 20 BAS

Business process analyst (BPA)

Focuses on analyzing, mapping, and optimizing end-to-end business processes to identify inefficiencies, recommend improvements, and ensure alignment with organizational goals and operational capabilities. They’re often shared across programs rather than assigned to projects.

Average number of business process analysts in a PMO:

  • Small PMO: zero to one BPAs (if any)
  • Midsize PMO: one to three BPAs
  • Enterprise PMO: three to eight BPAs

PM Coordinator

Especially in smaller or growing PMOs, this role is vital for operational efficiency. They might handle scheduling, documentation, communication, and general administrative support, ensuring the PMO runs like a well-oiled machine.

Average number of PMO administrators/coordinators in a PMO:

  • Small PMO: one coordinator
  • Midsize PMO: one to six coordinators
  • Enterprise PMO: six to 12 coordinators

Factors That Go Into Your PMO Size

The number of different roles in a PMO depends on several factors, including the:

  • Size and maturity of the organization
    • Centralized PMO (governing and executing): Tends to require more program managers
    • Supportive or Controlling PMO (advisory/guidance): May rely more on project managers and fewer program managers
  • Complexity and volume of active initiatives
    • Low Complexity: one program manager per five to 10 projects
    • High Complexity: one program manager per two to three large programs or initiatives
  • Program scope and strategic impact
    • Enterprise-level initiatives: Often justify dedicated program managers
    • Departmental initiatives: May not require formal program management
  • Geographic and organizational structure
    • Global or matrixed organizations: Often assign program managers per business unit, region, or capability domain
    • Smaller, co-located organizations: Can centralize program management under fewer roles
  • Industry trends and benchmarks
    • Ex. Technology & financial services: one program manager per $10M–$25M in active program budget
    • Ex. Public sector: Can be more regulated, often one Program Manager per strategic program, regardless of budget
  • PMO scope
    • Governance only vs. delivery support vs. fully embedded execution
  • Industry type
    • Regulated vs. unregulated

You should revisit ratio of roles and support needed quarterly to assess how much full-time and contingent support you need to scale the PMO.

Building a PMO is a journey, not a sprint. And like any great expedition, it starts with a clear map and a well-equipped team. Taking the time to define these foundational roles and responsibilities upfront will pay dividends in the long run, setting your PMO up for sustained success and true value delivery.

More Content