Plenty of mid-sized companies reach a point where projects run late, nobody agrees on status, and the same mistakes repeat. A project management office (PMO) is the usual answer. The structure matters less than the hiring. A PMO with the wrong people becomes a reporting desk that everyone resents.
This post covers how to staff one in stages, what each stage needs, and where contract talent fits.
Decide what problem the PMO is solving
Before you post a single job, write down the problem in one sentence. Typical answers:
- Projects finish over budget and nobody can say why.
- Two departments compete for the same people and systems.
- Leadership gets different status numbers from different teams.
- Growth has outpaced the informal way things used to get done.
The problem decides the first hire. A budget problem calls for someone with a finance sense. A resourcing conflict calls for someone who can plan capacity. A reporting problem calls for a coordinator who is good with data and patient with people.
Stage 1: one senior person, not a team
The first hire sets the tone, so go senior. You want someone who has built or repaired a delivery function before, can talk to a plant manager and a CFO in the same afternoon, and is comfortable with rough tools. Early on the work is mostly:
- Agreeing on a simple project lifecycle with defined stages and approvals.
- Setting up one intake process so requests stop arriving by hallway conversation.
- Choosing basic templates and a single place to track status.
- Naming who owns what, in writing.
A common mistake is hiring three junior coordinators first and hoping structure emerges. It rarely does. Coordinators need someone who knows what good looks like.
If you are not sure the office will become permanent, fill this role on contract. A 6 to 12 month engagement lets you test the model, and the person can set it up and hand it over, or convert if it works.
Stage 2: add the people who make it repeatable
Once the basics are in use, the work shifts to consistency. This is where you add:
- Project or program managers who run the larger initiatives under the common method.
- A project analyst or coordinator who keeps schedules, budgets and risk logs current.
- A resource or capacity planner, if people are being pulled between projects.
- A business or systems analyst, if your projects are mostly technology or process change.
At this point, check that the PMO is trusted. If operations leaders see it as overhead, no template will fix that. Hire people who have worked on the receiving end of projects, in a plant, a finance team or a sales organization, not only people with certifications.
Stage 3: use data, and be careful with AI
When reporting is reliable, the office can start forecasting: which projects are drifting, where capacity runs out, which investments paid back. That calls for someone comfortable with data, often a analyst with BI skills rather than another project manager.
AI tools can help with status summaries, risk flagging and schedule forecasting. They help only when the use case is specific and the underlying data is clean. Pointing a tool at inconsistent project records produces confident nonsense and costs you the trust of the teams you are trying to win over. Fix the data discipline first, then add the tool, then decide whether you need a specialist to own it.
Where the hiring usually goes wrong
- Hiring for certification alone. A credential shows someone studied the method. It does not show they can get a reluctant department head to hand over accurate numbers.
- Skipping the sponsor. If no executive owns the PMO, it will lose every budget conversation. Name the sponsor before the first interview.
- Over-building early. A heavy governance model on day one gets ignored. Start light and add structure where problems show up.
- No plan for the people who stay. Good project professionals are in demand in both Canada and the US. If the PMO offers no growth path and no clear mandate, expect to lose them within two years.
Questions to ask in interviews
- Tell me about a project you took over that was already off track. What did you do in the first 30 days?
- How did you get a team to adopt a process they did not want?
- What did you stop doing because it added reporting without adding value?
- How do you handle a senior leader who ignores the process?
Listen for specifics, trade-offs and honest accounts of what failed.
What to do next
Write the one-sentence problem, name the executive sponsor, and decide whether your first hire should be permanent or contract. Then define the three or four outcomes that person will be judged on in the first year.
If you want help finding a senior PMO lead, project managers or analysts, a Traverse recruiter can help with that, on contract or permanent.