PMO Staffing: Building Your Project Management Office

Last updated: May 12, 2026 | By Tom Kenaley

PMO staffing means building the people side of a project management office: a director, senior PMs, analysts, and coordinators who run portfolio governance, methodology, and resource planning across a company’s strategic projects. Most mid-market PMOs run four to nine people and cost $750K to $1.6M loaded, and the staffing order matters more than the headcount target.

A PMO that hires the analysts before the director almost always stalls. We’ve watched it twice in the past two years and the failure pattern is identical both times. Reporting dashboards stand up, the methodology never does, the executive sponsor loses faith around month seven, and the function gets quietly absorbed back into IT operations. Tooling stays. Authority leaks out.

Tom Kenaley at KORE1. PMO builds are roughly a third of our project-management-related searches across our IT staffing services book, and they have a much higher failure rate than individual PM hires. The first hire is usually wrong. We charge a placement fee when one of these searches closes, so factor that into how you weigh the frame below. What follows is the configuration we’ve seen work, plus the configurations that have wasted six months of payroll before anyone called us.

This guide is built for the executive sponsor who has been told to “stand up a PMO” and is staring at a blank org chart, or for the IT leader who already has three PMs and is realizing the title doesn’t scale. Skip to the staffing order section if you already know which model you’re building. Read the whole thing if you’ve been arguing with finance about whether the function pays for itself.

What a PMO Actually Does (And What It Isn’t)

A PMO is the institutional layer that sits above individual project managers and answers three questions. Which projects are worth running right now. Are the ones already in flight on track, on budget, and using a methodology anyone can recognize. Are the people running them growing into PMs who will be capable of running bigger things next year. Different from a single PM, which owns one initiative. The PMO owns the portfolio.

What it is not. Not a status-report machine. Not a Microsoft Project license farm. Not a soft landing for senior PMs the company doesn’t want to fire but doesn’t have a clear seat for. The “park the senior” PMO is the most common version we see and it dies on contact with anything resembling executive scrutiny, because the function ends up structured around the person rather than the portfolio.

The Project Management Institute’s Pulse of the Profession 2024 tracks roughly 71% of organizations with a formal PMO, and a separate finding worth chewing on: high-performing organizations are nearly three times more likely to have an Enterprise PMO with executive-level authority than low performers. The authority piece matters more than the existence piece. A PMO that reports three layers down is barely a PMO.

The Three PMO Models

Three flavors, in increasing order of how much teeth they carry.

Most enterprise PMOs land as Controlling. SMB and mid-market often start Supportive and graduate. The wrong answer is to hire for Directive authority but configure as Supportive, which is the configuration that consumes the most payroll for the least signal. Pick the model before you write the first job description. The model determines the org chart, the comp band, and the resume profile of the Director you should be looking for.

When You Actually Need a PMO

The size of the company is a poor proxy. We’ve seen a 220-person fintech with a real PMO problem and a 2,400-person regional bank that managed for years without one. What matters is portfolio shape, not headcount.

Portfolio volume is the first useful filter. Once a company is running roughly fifteen to twenty active projects across multiple departments and the executive team has lost the ability to answer “which ones are red?” in real time, the case for a PMO starts making itself. The exact number depends on interdependence. A health system running eighteen unrelated IT projects in parallel actually has eighteen projects. A bank running eighteen with nine of them sharing the same regulatory deadline has one big program and nine satellites, and the PMO was overdue six months ago.

Repeated project failure is the second filter, and the data here is older than most people realize. The Standish Group’s CHAOS Report has been tracking IT project outcomes since 1994. Roughly 31% of projects deliver on time and on budget, 50% are challenged, and 19% are outright cancelled. Those numbers haven’t moved meaningfully in fifteen years. Companies that swing well below the 31% threshold for two consecutive years have a coordination problem that the engineering or product org cannot fix alone. One mid-market client of ours had eight major initiatives over thirty-six months, four of which were cancelled mid-stream, and the cumulative wasted spend was just over $11M before the CFO finally signed off on a PMO. We placed the Director nine weeks later.

The third filter is harder to name and the one most companies miss. The strategy-execution gap. A board approves a three-year strategic plan in January, and by July nobody can tell you whether the projects funded against the plan are actually moving the company toward it or just consuming capacity in roughly the same direction. The gap is what a Directive PMO is built to close, and it usually gets justified at the SVP-or-above level rather than at IT. If your CEO is asking the question and your COO can’t answer it confidently, the conversation is already overdue.

Any one filter alone is not enough. Two of them, especially portfolio volume plus either of the others, and the math starts working.

How to Staff a PMO in the Right Order

Hire the Director first. Everything else follows from their early decisions, and if you hire the supporting cast before the leader you’ll spend the first ninety days reworking what those people are doing.

The full role stack, in the order most successful builds we’ve supported actually filled them.

Bands compiled from the PMI Project Management Salary Survey, Thirteenth Edition, Glassdoor (April 2026), and ZipRecruiter (April 2026). Coastal metros add 12% to 22% on top. Run your role profile through our salary benchmark assistant before finalizing the band.

Director first. Then an anchor PM. Then the analyst.

Director comes first because every other hire is shaped by their choice of model, methodology, and reporting cadence. A Director who came up under Agile transformation programs will hire a different analyst than one whose last job was running a Sarbanes-Oxley remediation portfolio. Both are valid hires. Neither is interchangeable. Bringing in the analyst first and then hiring the Director means the analyst spends a quarter rebuilding what they already built.

Anchor PM second. You need someone with credibility delivering live project work in the seat before the rest of the org agrees the PMO is doing anything beyond consuming meeting time. This person carries one or two of the most visible projects on the portfolio. Their job is to make the PMO useful in week six, not in month nine. We have placed senior PMs into this role on contract while the Director’s permanent search ran, and the bridge worked surprisingly well, because the contract PM doesn’t have the political baggage that a permanent hire would acquire by week four.

Analyst third. The reporting and governance work cannot start in earnest until the Director picks the methodology and tooling. Hire the analyst once the Director has at least mapped out the portfolio inventory and selected the primary platform, which is typically Smartsheet, Jira Align, Microsoft Project for the web, or Planview. Otherwise the analyst is building dashboards against a methodology that will get changed under their feet in month two.

The rest depends on volume and model. Coordinators are optional for small Controlling PMOs and essential for Directive ones, especially in regulated environments where document control is a real function. Additional senior PMs scale linearly with portfolio size. Rough rule: one senior PM per six to eight active projects, depending on complexity.

Three PMO Staffing Mistakes We Keep Seeing

Mistake one. Promoting the senior PM internally instead of hiring a Director from outside. The logic sounds clean. Sarah has been here eight years, she’s PMP-certified, she knows the political map, she’ll have a running start. The thing the logic misses is that the new Director’s job is partly to push back on the political map. To say no to projects the CFO’s brother-in-law sponsored. To kill a methodology that the current VP of IT personally rolled out three years ago. An internal promotion candidate has, in our experience, about an even chance of doing that work without flinching, because the relationships that helped them get promoted are the same relationships they need to disturb. External Director hires score higher on that specific dimension. Not always. But more often than not.

Mistake two. Treating the PMO as an IT function when the portfolio is half operational. We see this in companies that grew up on technology projects and then started adding M&A integration work, finance transformation, supply chain redesign, and HR system rollouts. The PMO Director gets hired from a pure-IT background, the methodology is Agile, the tooling is Jira, and the operational projects do not fit the muscle. Sponsors on the non-IT side stop attending portfolio reviews and quietly route their work around the PMO inside six months. Fix: hire a Director with hybrid IT-plus-operational experience and structure the PMO under a COO or strategy officer rather than the CIO if the portfolio is genuinely mixed.

Mistake three. Hiring analysts before the methodology is real. The board approved budget for “six PMO hires” in Q1, the recruiter starts sourcing analysts in Q2 because they fill faster than directors, and by Q3 there are four analysts producing reports nobody asked for because the methodology they’re reporting against doesn’t exist yet. Tools without process. Forms without policy. The Director joins in month four and spends month five undoing month two. Cheaper to leave the analyst seats open for ninety extra days than to fill them and rework everything.

Direct Hire, Contract, or Fractional: Picking the Engagement Model

Direct hire is standard for the Director, the PMO Manager, and any anchor PM you expect to keep beyond the build phase. These are the seats that need long-cycle authority and institutional knowledge. Direct hire staffing is the right model for everything in the top half of the table above.

Contract is good for the stand-up phase, especially when the build is faster than the permanent search can fill. We have stood up six- to twelve-month contract staffing bridges in three configurations that worked: an interim Director while the permanent search runs, a senior PM seat covered by contract until the Director picks their long-term anchor, and a contract analyst running portfolio inventory and current-state mapping for the first ninety days while the methodology stabilizes. The contract analyst pattern is the one most clients underestimate. The work front-loads heavily and then tapers, which is exactly what contract is for.

Fractional or interim PMO Director is the right fit for SMB companies under roughly 300 employees that need the function but cannot justify the full $180K-plus salary line. The typical engagement is two to three days a week for nine to fifteen months, the fractional Director sets up the framework, hires the analyst, and exits at the handoff point. We do not place fractional PMO Directors directly. We refer when it comes up, because the candidate pool is small and specialized.

Contract-to-hire is the blended option and it works well for the Senior PM role specifically. You bring the candidate in on a six-month contract, the Director assesses fit against the model they’re building, and the role converts to direct if it lands. The structure pushes the Director to make a decision rather than letting a contract drag, which is the failure mode of pure contract arrangements in PMO settings.

The First 90 Days of a New PMO

A clean stand-up has a rough shape. The Director’s first month is mostly listening, inventorying, and drafting a charter. Months two and three are when the function gets traction. Numbers below are typical, not prescriptive.

1. Days 1 to 30: Portfolio inventory and charter. Director joins, builds a current-state map of every active project, drafts the PMO charter (scope, authority, reporting line, intake process), and presents to the executive sponsor. No methodology rollout yet. No tooling decisions yet. The work is observation and documentation. Anchor PM may already be seated on contract; if not, sourcing kicks off in week two.
2. Days 31 to 60: Methodology selection and first pilots. Director picks the primary methodology (Agile, hybrid, stage-gate, or model-specific like SAFe) and pilots it against three projects already in flight. Tooling decision lands here, usually one of Smartsheet, Jira Align, Microsoft Project for the web, or Planview depending on the existing ecosystem. Analyst onboards once tooling is selected. Intake process starts gating new project requests.
3. Days 61 to 90: Reporting cadence and governance live. Portfolio dashboard is live and reviewed monthly with the executive sponsor. Standardized templates and intake forms are in use. The Director presents a six-month expansion plan to the sponsor and finance, covering additional headcount, tooling spend, and projected portfolio coverage. By day ninety the function should be producing signal the C-suite is using. If it isn’t, the model or the methodology is wrong and the Director should be raising the flag, not papering over it.

Companies that try to compress this into thirty days usually end up with a PMO that looks active but isn’t, because the inventory and charter work cannot be skipped without producing reports against the wrong portfolio.

What a PMO Actually Costs Loaded

$750,000 to $1.6M annually for a four-to-nine-person mid-market PMO once you include benefits at roughly 30% and tooling. Direct compensation is about 65% of the total. Benefits add another 22% to 28%. Tooling lands somewhere between $50K and $180K per year depending on the platform stack and how many licenses you need.

A representative mid-market stack: PMO Director at $165K base, one PMO Manager at $130K, two Senior PMs at $130K each, one Analyst at $85K, one Coordinator at $65K. Comp total $705K. Loaded with benefits at 27%: $895K. Add Smartsheet at $30K annually plus Microsoft Project Online at $18K plus modest training and conference budget at $25K, and the all-in is right around $968K. Enterprise PMOs running ten or more people clear $1.6M without straining.

The return calculation is harder to nail down because most companies don’t measure rigorously enough. PMI’s Pulse of the Profession research consistently puts high-performing organizations at roughly 89% of projects meeting original goals against 34% for underperformers. The gap is what makes the case work for any mid-market portfolio over $20M in annual project spend. Below that threshold the case is harder and the fractional or contract model usually beats a full build.

Things Hiring Managers Ask Before Calling Us

How many people do you actually need in a PMO?

Four to nine for most mid-market companies. The floor is two: a Director and a senior PM with portfolio visibility. Below that and you have a project manager with a fancier title, not a PMO.

Enterprise PMOs scale beyond nine, sometimes well beyond, but the structure usually splits into regional or domain-specific sub-PMOs at that point rather than scaling one monolithic team. If a company has more than fifteen PMO seats centralized under a single Director, the org structure is the next problem to fix.

PMO Director or VP of PMO, does the title actually matter?

$30K to $50K of base, mostly. Beyond that, the title signals reporting line. VP-titled PMO leads usually report into the COO, CEO, or CIO directly. Director-titled leads typically report into a CIO or a VP.

Get the reporting line right first. The title follows. We have seen companies offer a Director title with a VP reporting line and lose finalists at the offer stage because the comp band didn’t match the authority signaled in the org chart.

Do we need PMP certification on every PMO hire?

For the Director and senior PMs, yes. It’s a market filter, not a skill filter, and the candidate pool you want is mostly inside it. For analysts and coordinators, no.

Requiring PMP across the board screens out otherwise strong analytical candidates and adds three to four weeks to the search. Most analysts who do well in PMO work come from operations analyst, business analyst, or finance-adjacent backgrounds and they pick up the PM vocabulary inside a quarter. If the role is heavy on Agile rather than waterfall, swap PMP for PMI-ACP or CSM at the senior PM level.

Realistically, how fast can we fill a PMO Director role?

Six to ten weeks on a clean search. Faster if the comp band is honest and the reporting line is at VP or above.

We’ve seen Director searches go to fourteen weeks when the title says “Director” and the offer reads like a senior PM with one direct report. The candidates who can run a PMO at the level the C-suite expects have multiple offers in flight, and they read the band, the reporting line, and the equity component before they read the job description. The fastest PMO Director placement we ran in 2025 was twenty-three days, retained search, mid-market healthcare client with a fully decided model and a CFO who took the meeting personally in week one. The slowest was eighty-eight days, same comp band, undecided model, CEO who delegated the final round to HR. The variable is rarely the candidate pool.

Should the PMO own the project managers or just coach them?

Depends on the model. Directive PMOs own the PMs. Controlling PMOs set the rules but the PMs report to business units. Supportive PMOs do neither.

The wrong answer is to hire for Directive authority but configure the org chart as Supportive, which produces a function that consumes the most payroll for the least signal. Make the model decision before the first hire, write the authority level into the charter, and revisit it at the twelve-month mark.

Can we run a PMO with one person?

Not for long. A solo PMO works as a six-month bridge if a senior person already inside the company takes it on, but the moment they get pulled into ad-hoc firefighting the function stalls.

Plan to add an analyst within the first year or it quietly collapses back into project management. Solo PMO Directors in our placements have a high attrition rate after eighteen months, because the job becomes either firefighting or report-generation and neither was what they signed up for.

How does a PMO build differ from hiring individual project managers?

A PMO is a permanent function with portfolio authority. An individual PM owns one initiative. The hiring profile, comp band, and onboarding timeline are different at every level.

If you’re hiring a single project manager rather than building the function, our hire a project manager guide walks through the standalone search. The compensation context lives in the IT project manager salary guide. The PMO build is a layer on top of those, and the failure modes are different.

Building a PMO Worth Keeping

Stripped down: pick the model, hire the Director, give them a real authority charter, let them choose the methodology, and don’t backfill the analyst seats until that methodology is decided. The longer answer is that every company has political and budgetary realities that warp this plan, and the Director’s job in month one is partly to surface those realities to the executive sponsor rather than absorb them silently.

If you’re standing up a PMO from zero or rebuilding one that has lost executive faith, we can usually map the role stack, comp bands, and methodology fit against your portfolio in a thirty-minute call. Talk to a recruiter when you’re ready to scope the first search. The Director hire sets the trajectory for the rest of the function. Get that one right and the build pays for itself inside a year. Get it wrong and you start the conversation over.