What Is a PM Office, and When Does a Company Need One?
What is a PM office?
A PM office is the shared operating system for product work in a company. It sets out how ideas reach the backlog, how work is prioritised, which rituals the teams run, and how each metric is defined. It is not a department that approves other people's work. Its job is to make the same decisions look the same across teams, so that people can move between teams and leadership can compare them.
It is sometimes called product operations. The name matters less than what it covers.
What does a PM office contain?
| Part | What it settles |
|---|---|
| Intake | Where requests from sales, support and leadership go, and who decides what happens to them |
| Prioritisation | The criteria used to rank work, and who has the final say |
| Rituals | Planning, review and retrospective routines, who attends and what each produces |
| Templates | The few documents every team uses the same way, such as specs and decision records |
| Metric definitions | One written definition for each number the company reports, with an owner |
| Decision log | A record of what was decided, when, by whom and why |
| Roles | What a product manager is expected to do at each level, and how they are coached |
Keep it small. Each part should exist because a problem demanded it, not because a framework listed it.
What are the signs you need one?
- Every team has its own template, and none agree. Leadership cannot compare plans because each is written differently.
- The same number means different things. Two teams report "active users" and the figures cannot be reconciled.
- Requests arrive by side door. Work enters the backlog because someone senior asked, not because it was chosen.
- Decisions are not recorded. New joiners keep asking why things were built the way they were, and nobody can answer.
- Product managers work alone. There is no shared standard, no coaching, and no agreed view of what good looks like.
If you have one product team and one product manager, you probably do not need a PM office yet. A short written note on how decisions are made is enough. The need grows with the number of teams.
How do you set one up without adding bureaucracy?
- Start with the pain. Ask product managers and engineering leads what wastes their time. Fix the top two or three problems first.
- Write less than you think. One page for intake, one for prioritisation, one for metric definitions. If a document is not used in a real decision within a month, cut it.
- Give every definition an owner. A metric or a rule with no owner drifts. Name one person for each.
- Run the rituals before documenting them. Try a routine for a few cycles, change what does not work, and only then write it down.
- Review it on a schedule. Set a date, each quarter, to remove what is no longer needed.
Who should run it?
Someone with enough seniority that teams follow the rules, and enough closeness to the work to know which rules help. In a company without a product executive, this role often has no owner, which is why the PM office is a common reason to bring in senior help. A fractional product leader can design the operating model, coach your product managers, and hand it over to a permanent owner. Our explanation of what a fractional CPO does on the main ThynkBlox blog covers that role in more detail.
How does a PM office relate to the way we work?
The same logic runs through the ORBIT Method: agree one outcome, choose the smallest bet, wire every release to a metric, and leave a documented system behind. A PM office is that system, written down for more than one team. Our fractional CPO and PM office engagement sets out what is delivered, and our guide to what a product audit covers describes a lighter way to find out which parts you are missing first.
Unsure how much structure your product teams need? Read how the fractional CPO and PM office engagement works, or see the answers about scope and handover in our FAQ.