What a project management office (PMO) is, what it does day to day, its three types, and how tools like Tempo Loop link every project to the business goals.
PMO, explained by cats. Kitty had a small tuna shop. Now it's a whole tuna empire. A fleet. A cannery. Eight shops. An online store. One Kitty. So she sets up a PMO. PMO is a team. The project management office.
It tracks every project. And checks it against the business goals. Without PMO, teams fight over people. Deadlines slip. And Nobody notices. But every Monday, the PMO chases updates. Jira here. Azure DevOps there. PowerPoints and spreadsheets everywhere. So Kitty gets Tempo Loop.
Every team's work. One page. Linked to the business goals. This time, someone notices. Kitty's biggest goal? Online ordering. Off track. The digital team? Overbooked. And three projects have no goal. One is eating that team's time. Loop even says what to do.
Link it to a goal. Or pause it. So the PMO pauses that project. The digital team is now free to chase other goals. That's why a good PMO system matters. No more Monday chasing. And Kitty finally has time to eat tuna. Which makes Kitty, happy happy happy.
A project management office (PMO) is the team that tracks every project in an organisation and checks each one against the business goals. Once a company runs more projects than one person can follow, it is how someone keeps sight of who is working on what, and whether that work still serves the plan.
What a PMO is
The Project Management Institute (PMI) defines a PMO in its PMBOK Guide as 'a management structure that standardizes the project-related governance processes and facilitates the sharing of resources, methodologies, tools, and techniques'.
In plainer words, two jobs sit in that sentence. Governance is how decisions about projects get made: who approves a new project, how progress is reported, and who can stop one. Sharing resources means the people, templates and tools that several projects need at once are managed in one place rather than fought over.
A PMO is usually a small team, and it doesn't do the projects' work. Engineers, designers and marketers still build things in their own teams. The PMO sits across all of them.
PMO or project manager?
A project manager runs one project day to day: the plan, the tasks, the risks, the people on it. A PMO looks across every project at once. It asks different questions:
Do these projects together add up to the goals the company set?
Which teams are needed by too many projects at the same time?
Which projects are late, and does anyone know yet?
Is there work going on that no goal asked for?
A project manager can answer those for their own project. Nobody can answer them for the whole company without collecting everything in one place, and that collecting is where most PMOs start.
You'll also see PMO used for a programme management office (supporting a group of related projects) or a portfolio office (covering everything the company invests in). The ideas are the same at different scales.
PMO, explained by cats. Kitty had a small tuna shop. Now it's a whole tuna empire. A fleet. A cannery. Eight shops. An online store. One Kitty. So she sets up a PMO. PMO is a team. The project management office.
It tracks every project. And checks it against the business goals. Without PMO, teams fight over people. Deadlines slip. And Nobody notices. But every Monday, the PMO chases updates. Jira here. Azure DevOps there. PowerPoints and spreadsheets everywhere. So Kitty gets Tempo Loop.
Every team's work. One page. Linked to the business goals. This time, someone notices. Kitty's biggest goal? Online ordering. Off track. The digital team? Overbooked. And three projects have no goal. One is eating that team's time. Loop even says what to do.
Link it to a goal. Or pause it. So the PMO pauses that project. The digital team is now free to chase other goals. That's why a good PMO system matters. No more Monday chasing. And Kitty finally has time to eat tuna. Which makes Kitty, happy happy happy.
With three projects, the founder or a single project manager can keep them in their head. With fifteen, spread across half a dozen teams, some problems show up that no single project can see.
The first is shared people. A small specialist team, say the one that owns the website and the ordering system, is needed by marketing, the shops, finance and the warehouse at the same time. Each project manager asks for them, each request looks reasonable, and the team ends up booked at well over its capacity. Without someone deciding, the loudest request wins.
The second is deadlines that slip without anyone noticing. Each project reports in its own way, and an overloaded team rarely announces that it is overloaded. The problem shows up when a date is missed, which is too late to do anything cheaper than apologising.
The third is work with no goal. Projects that began as someone's good idea keep running long after the plan has moved on. Nobody stopped them because nobody looked at them again, and they keep using the same people the important goals need.
A PMO exists so these three things are seen early and decided on deliberately.
What a PMO does day to day
The work varies by company, but most PMOs do some version of this:
Keep the portfolio list: every project, its owner, its team, its dates and the goal it serves, in one place.
Collect status: a regular, consistent update from every project, so they can be compared.
Check the work against the goals, which many companies write as OKRs: an objective (what you want, such as 'launch online ordering in every shop') with key results that measure it (such as a number of online orders by a date). The PMO checks which projects move which key results.
Spot capacity clashes: compare what each team is booked for with what it can do.
Take decisions to leadership: start this, pause that, move people here. The PMO usually recommends, and leadership (a CTO, say, for technology bets) decides.
Set light standards: templates, a reporting rhythm and review points, so the numbers mean the same thing from team to team.
Three kinds of PMO
PMI's PMBOK Guide describes three types, by how much control the PMO has over projects:
Type
Control
What it does
Supportive
Low
Offers templates, training and lessons from past projects
Controlling
Moderate
Supports, and requires projects to follow its methods and reporting
Directive
High
Manages the projects directly, with project managers reporting to it
A PMO that works at company level and links all projects to the company's strategy is often called an enterprise PMO (EPMO). Most PMOs mix the types: supportive for small projects, stricter for the ones the business depends on.
A worked example: the Monday status chase
Take a seafood retailer that has grown from one shop into eight shops, a cannery, its own boats and an online store. It runs fourteen projects across six teams, and its biggest goal this year is launching online ordering in every shop.
Every Monday, the PMO analyst messages six team leads for an update. The digital team tracks its work in Azure DevOps, the other five use Jira, finance keeps a spreadsheet and leadership wants a slide deck. The analyst copies numbers from all of them into the PMO's own spreadsheet and builds the deck. By the time leadership sees it on Wednesday, it describes last Friday, and every status in it is self-reported.
Suppose the PMO gets all of that into one view, with each project linked to the goal it serves. Three things become obvious that weren't before:
The online ordering goal is off track.
The digital team, which online ordering depends on, is overbooked, because five departments' projects all need it.
Three long-term projects aren't linked to any goal at all, and one of them, a wholesale portal for supermarkets, is using a large share of the digital team's time.
The choice for that portal is simple to state: link it to a goal leadership agrees it serves, or pause it. Here the PMO recommends pausing it, and the digital team's time goes back to online ordering.
Pausing one project doesn't put a goal back on track by itself. It frees people, and the dates still need re-planning with the team. What changed is that the trade-off was made on purpose, on Monday, instead of being discovered when the launch date passed.
Where a tool like Tempo Loop fits
In that example, most of the PMO's week goes on collecting status, and the decision is quick once the picture is clear. Portfolio tools aim at the collecting. This video was sponsored by Tempo, and the tool it shows is Tempo Loop, so that is the one described here.
Loop connects to the tools teams already use, and Tempo names Jira, Azure DevOps and Linear among them. It pulls the work into one live view without moving it out of those tools. In the video's demo, which uses a made-up company, the portfolio lists every project with its team and the system its work comes from:
The demo company's projects in one list, from Jira and Azure DevOps
Each item can be linked to the objective it is meant to serve, and Loop flags work that maps to no objective. A part called Loop Intelligence reads those signals and turns them into recommendations, ranked by their effect on the objectives at risk. Tempo says each one names a specific action, an owner and an execute-by window, and shows its confidence level and the sources behind it. The video uses this one, about the three long-term projects with no goal:
A recommendation names the problem, the evidence and the move
When a change is approved, Tempo says Loop writes it back to the tool where the work lives, so the team sees it there too.
A tool like this takes over the Monday chase. The judgement stays with the PMO: someone still has to agree the goals, keep the links between work and goals accurate, and have the authority to pause a project. If half the work isn't linked to anything, a single view shows that clearly, but fixing it is still people's work. For a company with a handful of projects in one tool, a shared Jira dashboard or a well-kept spreadsheet may be all it needs.
Common mistakes
Becoming a reporting factory: a PMO that only collects status and builds slides adds cost without changing any decision.
Process for its own sake: heavy templates on small projects teach teams to work around the PMO.
No authority: if the PMO can't get a project paused, it can only watch the clash happen.
Green projects, red goals: every project can report on track while the goal they serve is off track.
Starting too strict: a directive PMO in a company that only needed shared visibility tends to meet resistance.
Key takeaways
A PMO tracks every project in an organisation and checks each one against the business goals.
PMI defines it as a structure that standardises project governance and shares people, methods and tools.
It earns its place when projects compete for the same people, deadlines slip unseen or work serves no goal.
Collecting status by hand is slow and dated; tools such as Tempo Loop put the work and the goals in one view.
The decisions are still the PMO's: link a project to a goal, or pause it.