A project management office tends to start with a good intention and a thin plan. Someone senior says the company needs better control of its projects, a few people get moved over, and nobody writes down who owns what. Six months later the office is a reporting desk that nobody trusts.
The fix is not a bigger team. It is deciding which roles you need, in what order, and which ones belong on the payroll versus on a contract.
Start with the job the office has to do
Before you write a single posting, decide which of three jobs the PMO is meant to do:
- Advise: set templates, standards and guidance, and leave delivery to the business units.
- Control: set standards and check that projects follow them, with authority to stop or escalate.
- Deliver: own the projects and the people running them.
An advisory office can run on a lean team of coordinators and a few experienced project managers. A delivery office needs program managers and a deeper bench. Hiring for the wrong model is the most common reason we see PMO roles get posted twice.
The core roles, in the order most employers need them
1. A PMO leader. One person, always. This role sets direction, reports to executives and decides what the office will not do. It needs a communicator more than a methodology expert. If this seat is filled by someone who cannot hold a room with the COO or the plant manager, the rest of the team will struggle for credibility.
2. Project managers. These people plan, run and close individual projects, and they own scope, budget and schedule. They are usually your first volume hire. Look for evidence of finished projects of similar size to yours, not just certifications.
3. A PMO coordinator or administrator. Scheduling, status reports, document control and meeting follow-up. In a small office this role is what keeps the project managers on delivery rather than paperwork. It is often under-hired and then regretted.
4. Business analysts. They turn what the business says it wants into requirements a team can build against. Projects that skip this step tend to deliver on time and still miss the need.
5. Business process analysts. Useful once you have several projects touching the same workflows. They are often shared across projects rather than assigned to one, which makes them a good candidate for contract cover.
6. Program and portfolio managers. Add these when you have multiple linked projects, or several lines of business competing for the same people and budget. A program manager coordinates the project managers inside one large initiative. A portfolio manager looks across everything and asks whether the mix of work still fits the strategy.
Sizing the team
There is no single correct ratio, and anyone quoting one as fact is guessing. These are working starting points we would test against your own numbers:
| Factor | Leans toward fewer roles | Leans toward more roles |
|---|---|---|
| Project complexity | Routine, repeatable work | Many dependencies, regulated work |
| Footprint | One site, one team | Multiple sites, regions or business units |
| PMO mandate | Advise | Deliver |
A practical way to check capacity: count active projects and divide by the number your project managers can realistically carry. Most managers can handle a handful of small projects or one or two large ones. If your people are juggling more than that, quality slips quietly before anyone says so out loud.
What to hire, what to contract
PMO workloads are lumpy. A system rollout, a plant expansion or an ERP change can double the need for analysts and project managers for nine months and then drop away.
A reasonable split:
- Permanent: the PMO leader, a core group of project managers, and the coordinator. These people hold your methods and relationships.
- Contract: business analysts, process analysts and extra project managers tied to a specific initiative with a clear end date.
- Either: program managers, depending on whether the program is a one-off or the shape of your business going forward.
Contract cover also lets you test a role before committing. If a contract business analyst proves their worth, you have a strong case for making the seat permanent.
Review the mix every quarter
A PMO built for last year's portfolio will not fit this year's. Once a quarter, look at active projects, upcoming demand, overtime and missed milestones, then adjust. Decide in advance which roles flex and which are fixed. That keeps you from either carrying idle headcount or burning out the people you have.
Common mistakes
- Promoting the best technical person into the leader seat without asking if they can manage upward.
- Hiring project managers before anyone owns the standards they are meant to follow.
- Treating the coordinator as optional.
- Writing every posting as a senior role because the office feels important.
What to do next
Write down the job your PMO is meant to do in one sentence, list the roles that sentence requires, and mark each one permanent, contract or later. Then check the list against your current project count before posting anything.
A Traverse recruiter can help you define the roles, source project and analyst talent in Canada and the US, and set up contract cover for the peaks.