Public entities often have the most elaborate strategy machinery of any organization: national visions, multi-year programs, central performance units, hundreds of KPIs. They also face a distinctive failure: reporting compliance against a KPI catalogue while the outcomes the strategy promised move slowly or not at all.
In this guide
Key Takeaways
- →Long horizons, central performance units, mandated KPI sets and shared outcomes all change how deployment works.
- →Outputs are what an entity produces; outcomes are what changes as a result.
- →A few outcome objectives per entity, with the full KPI set kept as supporting measures.
- →Negotiate targets with the central unit, and record the entity’s commitments and needs.
- →Cross-agency dependencies decide shared outcomes, so agree them explicitly.
- →Public accountability creates pressure to report green and reluctance to retire programs.
What’s different in the public sector
Six features of public organizations change how deployment has to work. None of them is a reason it cannot.
| Feature | Effect on deployment |
|---|---|
| National or sector visions spanning many years | Long horizons; annual plans must trace to them |
| Central performance or strategy units | A strong downward channel; risk of one-way cascades |
| Large mandated KPI sets | Effort goes into reporting many measures rather than moving a few outcomes |
| Many agencies sharing outcomes | Dependencies across agencies decide results |
| Annual budget cycles | Funding fixed before delivery plans are agreed |
| Public accountability | Pressure to report green; slow to retire programs |
The second row is the one to watch: a strong central unit makes a one-way cascade easy, and the failure modes are the same as anywhere, set out in Cascading Goals vs Negotiating Them: Why Top-Down Cascades Fail.
From KPI catalogue to outcomes
A common pattern is an entity reporting dozens or hundreds of KPIs to a central unit every quarter. Each is defined, tracked and colored. The reporting is a significant workload, and the conversation it produces is about which KPIs are red, not whether the entity’s strategic outcomes are improving.
The public-sector distinction between outputs and outcomes is the key. Outputs are what the entity produces: permits processed, programs launched, people trained. Outcomes are what changes as a result: waiting times, employment, service satisfaction. Deployment should make each output answer to an outcome, the same distinction as Alignment Isn’t Effect: Why Well-Aligned Plans Still Miss.
A public entity can hit every output target and leave its outcomes unchanged. The reporting should make that impossible to miss.
Five practices that help
- A few outcome objectives per entity, with the full KPI set kept as supporting measures.
- Targets negotiated with the central unit, with the entity’s commitments and needs on the record.
- Outputs linked to the outcomes they should move, with an expected time lag.
- Cross-agency dependencies agreed explicitly, so shared outcomes have shared commitments.
- Programs reviewed on outcome evidence, so ones that aren’t working can be changed rather than defended.
The fourth of those is the one public bodies find hardest, and the mechanics are in Deploying Across: Managing Cross-Functional Dependencies.
A worked example: one outcome, two agencies
Here is a hypothetical outcome objective, split across two agencies that never agreed a dependency:
One outcome objective, split across two agencies that never agreed a dependency.
| Item | Content |
|---|---|
| Outcome objective | Reduce average business license approval time from 21 to 7 days |
| Agency A output | New online application portal launched |
| Agency B dependency | Inspection scheduling, owned by another agency |
| Month six | Portal 100% live; approval time 19 days |
| Diagnosis | Applications are faster; inspections still scheduled manually by agency B |
| Action | Cross-agency agreement: inspection slots bookable in the portal by Q3; agency B commits capacity |
Under a KPI catalogue, agency A would report its portal output as green, and agency B’s inspection backlog would sit in a different report. Deploying across made the dependency, and the fix, visible.
What a KPI catalogue costs to report
An entity reporting two hundred KPIs quarterly to a central unit usually has a performance team doing little else. The visible cost is their time; the real one is that the quarterly conversation is about which measures are red rather than whether the outcome the strategy promised is moving.
Among published alternatives, OnStrategy lists $200 per month for unlimited users, which suits entities adding many light users across agencies. i-nexus publishes a free Starter tier for up to five users and $28 per user per month at its Standard tier. For a public body, hosting, data residency and procurement terms usually matter as much as the licence line.
Profit.co publishes two plans, Essentials and Enterprise, quoting against modules and scale rather than a public seat rate, which fits entities that vary widely in size and maturity. Outcome objectives with supporting KPIs, catchball and the exception queue sit in Essentials with OKRs and Goals, Balanced Scorecard, Hoshin Kanri and Strategy Roadmap, so the catalogue can stay as supporting measures without becoming the report.
Software considerations
Public entities usually add requirements around data residency, hosting, accessibility and procurement. Check these early in any evaluation. On the deployment side, the same tests apply as anywhere: negotiated targets, evidence beside progress, and agreed dependencies; see How to Evaluate Strategy Deployment Software.
Profit.co supports these practices with catchball sessions for negotiated targets, correlations between outputs and outcomes with expected lags, an exception queue for programs not moving their outcomes, and OKRs, scorecards and hoshin plans on one model. See the strategy deployment software page.
Two of those address the public-sector failure directly:
- Correlations with expected lags make an output answer to an outcome, so a 100% portal with a 19-day approval time shows as a gap rather than as green.
- The exception queue brings that gap to the quarterly review without anyone having to raise it, which matters most where raising it is politically costly.
Free Product Demo
Connect your outputs to your outcomes
A 30-minute walkthrough, tailored to your team.
Book a free demo
What happens in the call
How your teams set goals, track progress and review results.
Strategy, performance, projects and engagement on one platform, with AI.
A practical path to align teams, execute faster and drive results.
Questions this article answers
With a few outcome objectives per entity, targets negotiated with the central strategy unit, outputs linked to the outcomes they should move, agreed cross-agency dependencies and program reviews based on outcome evidence.
Outputs are what an entity produces, such as permits processed. Outcomes are what changes as a result, such as approval times or service satisfaction.
Large mandated KPI sets shift effort to reporting many measures, while the few outcomes the strategy promised receive less attention.
Agree the dependency explicitly, with each agency committing its part and a date, and show it on both agencies’ objectives so both reviews see it.
No. Keep the full set as supporting measures and put a few outcome objectives above it, so the quarterly conversation is about outcomes rather than about which of two hundred measures is red.
