A PMO that treats OKRs and KPIs as the same kind of thing ends up with neither working. The usual result is a portfolio dashboard where quarterly bets and permanent health metrics sit in one table, updated on the same cadence, colored with the same red-amber-green, and read with the same glazed expression.
OKRs and KPIs answer different questions, and initiative tracking answers a third. A PMO's job is to keep each in its lane and connected to the others. Here is how each earns its place.
KPIs are the vital signs
KPIs are the metrics you watch continuously because they tell you whether the business is healthy. On-time delivery rate, gross margin, customer churn, resource utilization. They have no end date. You are not trying to complete churn; you are holding it inside a range and want to know quickly when it moves out.
For a PMO, KPIs are the standing dashboard; they frame whether the portfolio is doing its job at all. A KPI on its own, though, gives you the temperature without telling you what to do about it. That is the gap OKRs fill, and the distinction is worth getting exact. This breakdown of OKR vs KPI covers it in depth.
OKRs are the change you are making this period
An OKR is a time-boxed bet on a specific change. "Keep churn healthy" is a KPI. "Cut mid-market churn from 4 percent to 2.5 percent by the end of Q3" is an OKR, with an explicit target and a deadline it either hits or misses. Where a KPI runs indefinitely, an OKR closes.
The relationship is straightforward once you see it. OKRs are the deliberate moves you make to push a KPI in a direction it will not go on its own. If a KPI is already drifting the right way without special effort, it needs monitoring, not an objective wrapped around it. You write an OKR when you have decided to force a change and are willing to point real work at it.
Initiative tracking is the work underneath both
Initiatives are the projects and programs that actually deliver the change: the platform migration, the new onboarding flow. This is usually where a PMO already has the most muscle.
The mistake is letting the initiative layer float free of the goals above it. A program can be on budget and green on every milestone while moving no OKR and improving no KPI. A PMO that only tracks initiative health is measuring motion and calling it progress. Holding the line of sight from a project up to the OKR it serves and the KPI it moves is the real discipline, and it is what strategic initiative management means done properly.
Where PMOs get it wrong
The most common failure is turning OKRs into a status-reporting chore. The PMO, being the function that owns reporting, absorbs OKRs into its existing rhythm. Every OKR gets a weekly percentage and a RAG status, and the quarterly review becomes a read-out of those percentages. Within two cycles the OKRs have stopped being bets and become another table the PMO maintains, the exact drift that makes teams resent them.
A second failure is promoting every KPI to an OKR, so the portfolio carries forty "objectives" that are really just metrics somebody is watching. The opposite also happens: a PMO tracks initiatives diligently but never ties them to an outcome, so the portfolio looks busy while nobody can say what changed. A PMO earns its seat by protecting the connection between work and outcome, not by collecting the most status.
How they fit in a portfolio
Picture the portfolio in layers. KPIs are the health panel you always keep open. OKRs are the short list of changes the portfolio is trying to produce this period, each aimed at a KPI. Initiatives are the funded work under each OKR. The PMO's job is to keep that stack connected and act when it comes apart: when an initiative is burning budget while its OKR sits still, or when an OKR is reported green while the work beneath it has stalled.
Read top to bottom, the stack shows intent. Read bottom to top, it shows whether intent is being delivered. A PMO that can move in both directions is doing strategy execution. One that only collects percentages is doing administration.
That is easier to describe than to maintain, because the link between an initiative and the OKR above it usually lives in someone's head or a manually updated slide. Vindaris keeps that stack connected structurally, so a PMO sees when the work and the goal have drifted apart instead of discovering it at quarter-end.
FAQ
Should a PMO own the company's OKRs? A PMO should own the connection between OKRs, the initiatives beneath them, and the KPIs above them, but not the objectives themselves. The accountable owner of each objective is the leader making the bet. When the PMO becomes the owner, OKRs slide back into being a reporting artifact the office maintains rather than decisions leaders answer for.
Can an initiative exist without an OKR? Yes, and many should. Plenty of run-the-business work keeps a KPI healthy without representing a deliberate change, so it needs no objective attached. The test is whether the work is meant to move something to a new level or hold something at its current one. Only the first kind needs an OKR.