PMO Templates: What a Small PMO Actually Needs

The starting set for a new or small PMO, in the order it is worth building — and the artefacts that can safely wait.

A PMO's core job is to make a portfolio of projects visible, comparable and governable. Everything a PMO builds should serve one of those three words, and a new PMO that starts by writing a methodology rather than establishing visibility usually loses its audience before it finishes.

What follows is an order of work, not a list of documents. The order matters more than the templates, because each stage earns the credibility needed for the next.

Stage 1: make the portfolio visible

Before any standard can be enforced, somebody has to be able to answer: how many projects are running, who owns them, what state are they in, and what are they collectively costing?

Almost no organisation can answer this on day one, and producing the answer is the fastest way for a new PMO to demonstrate value. What you need is a single register — one row per project — with owner, phase, status, budget and next milestone. Everything else is derived from it.

Resist the urge to make it comprehensive. A register with eight columns that is current beats one with thirty that is six weeks old.

Stage 2: standardise reporting

The second problem is comparability. If every project reports in its own format, consolidation means retyping, and retyping means the consolidated view is always out of date and slightly wrong.

Pick one status format and require it. Weekly or fortnightly, one page, with a fixed RAG definition. Write down what green, amber and red mean, because without shared definitions a portfolio view of RAG statuses is a portfolio view of individual project managers' temperaments. The project status report guide covers what belongs in it.

This is also where you decide the reporting cadence for the layers above: project weekly, portfolio monthly, board quarterly is a common and workable rhythm.

Stage 3: govern risk and dependency across projects

Individual projects manage their own risks. What only a PMO can see is the risk that appears in four projects at once, and the dependency that runs between two of them.

A cross-portfolio risk view and a cross-project dependency register are the two artefacts that justify a PMO's existence to a sceptical delivery organisation, because no project manager can produce them. The dependency tracking guide covers the fields that matter.

Stage 4: resource visibility

Portfolio health usually looks acceptable until you notice that four of the amber projects share the same three specialists. Resource contention is the most common cause of portfolio slippage and the least often measured.

Track named people against projects per period rather than roles against FTE counts. Role-level planning reads well in a business case and helps nobody in June.

Stage 5: selection and prioritisation

Only once the running portfolio is visible does it become credible to influence what enters it. A weighted scoring model, agreed before the candidate projects are known, converts prioritisation from a contest of personalities into a defensible ranking.

Agree the weights first and then leave them alone. Weights adjusted after the scores are known are not weights; they are a preference with arithmetic attached.

What can wait

• A full methodology. Nobody reads it, and enforcing an unread methodology is how PMOs acquire their reputation.
• Stage gate documentation packs beyond a charter and a closure report, until there is evidence that projects are starting or ending badly.
• Benefits tracking, until reporting is trusted. Benefits reporting built on top of unreliable status reporting produces confident numbers that are wrong.
• Tooling. A portfolio tool implemented before the process exists automates the absence of a process. Prove the process in spreadsheets first; if the portfolio outgrows them, the tool selection will be better informed for it.

The measure of a working PMO

Not the number of templates issued. A PMO is working when a sponsor can get an accurate answer about any project in the portfolio within an hour, when two projects competing for the same person are identified before one of them slips, and when project managers use the templates because they are faster than the alternative rather than because they were told to.