Strategy Execution in Government: Four Gaps That Do Not Exist in the Private Sector

Table of Contents

Key Takeaways

• No profit signal means arbitration must be explicit: commercial platforms assume a single ranking metric exists. Public agencies need the trade-off between competing mission priorities made visible in the system rather than resolved informally.
• Agencies are judged on outcomes they only partly control: the gap between agency outputs and societal outcomes is wider than in any commercial sector, and a platform that cannot hold both loses either accountability or fairness.
• Political cycles are an external clock: leadership and priorities can change on a date nobody in the agency chose, which makes institutional memory a functional requirement rather than a nice-to-have.
• Budget is appropriated, not allocated: funds are voted for defined purposes, so the reallocation flexibility commercial portfolio tools assume simply is not available.
• Statutory reporting is a platform requirement: Profit.co maps GPRA-M structures directly, Agency Priority Goals become top-level OKR Objectives and Strategic Objectives become the scorecard measures annual OKRs contribute to.
• The government scorecard has five perspectives, not four: Profit.co’s Balanced Scorecard module supports the Kaplan and Norton public-sector configuration with Mission at the apex as its default.

1. Why Government Needs a Different Evaluation

Public sector strategy leaders evaluating execution software are usually shown a commercial demo with the word “revenue” swapped for “mission.” That substitution hides the actual problem, which is not vocabulary but structure.

Profit.co puts the underlying issue plainly: the OKR methodology was originally developed in the private sector for organizations with clear profit objectives, flexible resource allocation, and rapid feedback loops. Government has none of the three, and the adaptations required are documented in its guide to the six adaptations needed to implement OKRs in government.

What this article covers, and what it does not

This is an evaluation piece for someone selecting or configuring a platform, not a methodology guide. Profit.co maintains a substantial body of public sector methodology material, a four-phase implementation roadmap for public sector leaders, guidance on champions, cadence, and execution discipline in government, and a Mission Profit framework covering the ten dimensions of public value an agency creates. This article assumes that material and asks a narrower question: what must the software actually do?

The answer organizes around four gaps. Each exists because of a structural feature of public administration that has no commercial equivalent, and each generates a requirement that a private-sector-designed platform will not meet by default.

2. Gap 1, The Arbitration Gap

The gap: no single metric exists to rank competing priorities against one another.

A commercial organization facing a choice between two initiatives has a tie-breaker. Expected return arbitrates, imperfectly but decisively. An agency choosing between reducing processing times and improving inspection coverage has no equivalent, both serve the mission, both matter, and the units do not convert.

Left unresolved, the arbitration happens anyway: informally, by whoever has the most political weight, the loudest stakeholder, or the nearest deadline. It is made in every case; it is simply made invisibly.

What the platform has to supply

• Multi-dimensional value made explicit rather than collapsed. Profit.co’s Mission Profit framework defines the multidimensional public value an agency creates relative to the resources it invests, replacing financial profit with measurable societal, institutional, and generational outcomes. The point for a software evaluation is that the platform must hold several incommensurable value dimensions side by side without averaging them into a score.
• A cost-per-outcome view. Profit.co’s program performance module tracks cost-per-outcome alongside mission OKR achievement. This does not eliminate the arbitration problem, but it gives the trade-off a shared denominator where one is available.
• Weighting that is visible and revisable. Where key results are weighted, progress becomes a weighted contribution rather than a simple average. In an agency that means the relative priority of two competing objectives becomes an explicit, auditable decision rather than an implicit one.
• A hard constraint on objective count. Profit.co’s public sector guidance recommends three to five objectives per department, each with two to five key results, and names too many objectives as one of the three most common causes of failure. Where arbitration is hard, the discipline of a fixed budget does much of the work.

3. Gap 2, The Outcome-Output Gap

The gap: agencies are held accountable for societal outcomes while controlling only their own outputs.

A public health agency is judged on population health. It controls vaccination programmes, inspection regimes, and public communication. Between its outputs and the outcome sit individual behaviour, economic conditions, demographics, and the actions of other agencies. The causal chain is long, lagged, and shared.

Every sector has some version of this. In government it is wider than anywhere else, and it produces two opposite failures. Measure only outputs and the agency reports activity while outcomes stagnate. Measure only outcomes and staff are held to account for forces outside their control, which destroys the credibility of the measurement system.

What the platform has to supply

• Both layers, explicitly linked and separately readable. Profit.co separates these in its data model: Initiative key results cover Percentage Tracked, Milestone Tracked, and Task Tracked types, while KPI key results are Increase, Decrease, and Control types. An agency objective needs both, the output the team controls and the outcome it contributes to, visible against each other rather than merged.
• Contribution rather than attribution. The platform should let an agency state that an output contributes to an outcome without claiming to cause it. Alignment linkage does this structurally; a single blended progress figure does not.
• Lag acknowledged in the plan shape. Outcome measures move slowly and often non-linearly. Five progression models are available, Linear, Front-loaded, Back-loaded, S-curve, and Stepped, and a public health outcome modelled as linear will read as failure for most of its life.
• Existing statutory measures preserved. Profit.co’s guidance is that existing performance metrics typically become key results or KPIs supporting OKRs rather than being replaced. For an agency with mandated indicators, that is the difference between a system it can adopt and one that would require abandoning its reporting obligations.

4. Gap 3, The Continuity Gap

The gap: leadership and priorities can change on an electoral clock nobody in the agency controls.

A commercial strategy cycle ends when leadership decides it ends. A public sector strategy can be redirected by an election, a ministerial reshuffle, or an administration change, on a date fixed years in advance and entirely independent of where the strategy had got to.

The resulting failure is institutional amnesia. A new leadership team inherits objectives whose rationale is undocumented, evidence that is scattered, and programmes whose original business case nobody can locate. The default response is to start again, which discards years of accumulated evidence and resets the clock on every long-horizon outcome.

What the platform has to supply

• A decision record that survives personnel change. Profit.co’s Governance module tracks eight independently configurable categories, Actions, Assumptions, Decisions, Issues, Risks, Strategic Alignment, Project Changes, and Tollgates, each with an immutable activity log capturing the acting user and timestamp. The Decisions category records what was chosen, what alternatives were considered, and the rationale, which is exactly what an incoming leadership team needs and almost never has.
• Assumptions recorded as objects, not prose. The Assumptions category covers factors believed true for planning that still require validation. When an administration changes, the question is rarely “what were they doing” but “what did they believe when they decided this,” and unvalidated assumptions are the highest-value part of the inherited record.
• Multi-year structure that outlives a cycle. Profit.co’s strategy roadmaps cascade vision areas into themes, sub-themes, and initiatives on a single timeline, which suits a five-year statutory strategic plan better than a quarterly goal list does.
• Evidence continuity across the transition. Historical performance data, with the context that produced it, is the asset a new administration should inherit. A system where the record resets with the leadership is a system that guarantees the amnesia.

5. Gap 4, The Appropriation Gap

The gap: funds are voted for defined purposes, not allocated freely against strategic priority.

Commercial portfolio management assumes reallocation is available: an underperforming initiative can be defunded and the money moved. In an appropriated environment that flexibility is heavily constrained. Funds are voted to purposes, transfers between them may require authority the agency does not hold, and unspent balances can lapse.

This breaks a core assumption of commercial portfolio tooling. A platform that recommends reallocation as the standard response to underperformance is offering an action the agency frequently cannot take.

What the platform has to supply

• Budget structure that mirrors appropriation, not just portfolio. The system should show funds against the purposes they were voted for, so the question “can we move this?” is answerable rather than assumed.
• Budget execution measurement, not only outcome measurement. Profit.co’s Financial Stewardship Profit framework covers a sixteen-metric financial management library spanning budget execution, audit quality, cost efficiency, and long-term fiscal health, and its treatment of financial stewardship beyond budget compliance sets out the frameworks in full.
• Cost-per-outcome as a first-class measure. Where reallocation is constrained, the lever available is efficiency within a purpose rather than movement between purposes. That makes cost-per-outcome the operative metric rather than a reporting nicety.
• Evidence that feeds the next budget formulation. Profit.co describes the integration between OKR performance data and budget planning as creating an evidence pipeline for budget formulation, which matters because in an appropriated environment the real reallocation opportunity is the next budget cycle, not the current one.

6. The Four Gaps and What Each Requires

An evaluation grid. The final column is answerable in a demo, and each question exposes an assumption a commercially designed platform is likely to have baked in.

The third question is the most revealing in practice, because it is rarely asked and almost never has a good answer. Most platforms treat decision history as an internal convenience rather than an institutional asset, which is a defensible position in a company and a serious weakness in an agency facing an administration change. Sector-general evaluation criteria that still apply are set out in how to choose the right strategy execution platform.

7. Statutory Reporting as a Platform Requirement

In the private sector, reporting format is an internal choice. In government, a significant portion of it is legislated, which turns reporting structure from a preference into a requirement the platform either meets or forces the agency to work around.

The structural mapping that matters

For US federal agencies, the Government Performance and Results Act Modernization Act requires a five-year strategic plan and an annual performance report, with Annual Performance Plans containing Agency Priority Goals, Strategic Goals, and Strategic Objectives. Profit.co maps these onto its own structures directly: Agency Priority Goals become top-level OKR Objectives, and Strategic Objectives become the Balanced Scorecard measures that Annual OKRs contribute to. The full mapping is set out in its treatment of running the Balanced Scorecard and OKRs simultaneously.

Evidence-based policymaking

Profit.co also connects this to the Foundations for Evidence-Based Policymaking Act of 2018, which requires federal agencies to systematically build and use evidence about programme effectiveness. Its position is that an agency tracking cost-per-outcome as key results, and reviewing programme performance data at the budget formulation stage, is operationalizing what the Evidence Act intends rather than merely documenting compliance with it.

A scoping note

Statutory requirements vary by jurisdiction, level of government, and agency type. The mapping above is specific to the US federal context; state, municipal, and non-US agencies operate under different regimes. This article is not legal advice, and the reporting obligations a platform must support should be defined by the agency’s own compliance function rather than inferred from a vendor’s materials.

8. The Five-Perspective Government Scorecard

One structural detail deserves its own section because it is the clearest single indicator of whether a platform was designed with the public sector in mind.

The standard Balanced Scorecard places the Financial perspective at the top. Kaplan and Norton addressed this in their 2001 work on Strategy Maps for Public Sector and Non-Profit Organizations, proposing a five-perspective government model with Mission at the apex, Citizen/Stakeholder and Financial perspectives below it, Internal Process in the middle, and Learning and Growth at the foundation. Profit.co’s Balanced Scorecard module supports this five-perspective government configuration as the default, with each perspective’s strategic objectives serving as source material for the OKR hierarchy.

Why the ordering is not cosmetic

Placing Financial below Mission changes what a scorecard says when the two conflict. In a commercial configuration, financial performance is the apex measure and everything else is instrumental to it. In the government configuration, financial stewardship is a constraint and an enabler rather than the objective, which is an accurate description of how an agency is actually judged, and a reversal a platform cannot express if its scorecard structure is fixed.

The complementary argument for why agencies need both frameworks rather than choosing between them is that the scorecard answers whether all the right things are being tracked while OKRs answer whether the most important things are moving now. Profit.co develops this in how the Balanced Scorecard helps government agencies better serve the public.

9. Public Sector Measures Across the Gaps

Measures drawn from Profit.co’s public sector material, placed against the gap each addresses. These are illustrative of measure types rather than recommended targets, agencies should set their own from a baseline.

Two design notes. First, budget execution rate is a control measure rather than an increase one, spending too little against an appropriation is a finding, and spending too much is not available, so the target is a band. Second, the final row is a process measure rather than a mission measure, and it exists because continuity is a real risk that nothing else on the list would detect. Outcome examples are drawn from Profit.co’s discussion of the impact of OKRs on public sector workforce performance.

10. Three Agency Deployments

Three composite scenarios, each showing a different gap left open and what would have closed it.

Deployment A, The agency measured only on outputs

Deployment B, The transition that erased the record

Deployment C, The portfolio tool that recommended the impossible

The common thread: in each case the platform functioned correctly against assumptions that do not hold in public administration. That is why evaluation should test the assumptions rather than the features.

11. Procurement Questions to Ask a Vendor

1. “Can the scorecard put Mission above Financial?”

Tests whether the perspective structure is configurable or hardcoded to a commercial model. A fixed four-perspective scorecard with Financial at the apex cannot express how an agency is judged.

2. “Show me an objective where the team owns the output and contributes to the outcome.”

Tests whether the platform can express contribution without forcing attribution. If both have to sit in one blended progress figure, the system will produce either unfair accountability or empty activity reporting.

3. “A new leadership team arrives tomorrow. What do they inherit?”

The continuity question. Look for decisions and assumptions as first-class objects with automatic, immutable activity logs, not for a document library.

4. “How do you handle funds that cannot be reallocated?”

Tests whether portfolio logic assumes fungibility. The right answer involves budget execution against voted purpose and evidence for the next formulation cycle.

5. “How does this support our statutory reporting?”

Ask for the specific mapping rather than a general claim. For US federal agencies that means Agency Priority Goals, Strategic Goals, and Strategic Objectives mapping onto the platform’s own structures.

6. “What is the audit trail, and can it be edited?”

Public sector records face audit and, in many jurisdictions, freedom of information access. A log that can be altered after the fact is not an audit trail.

7. “What are your security credentials and hosting arrangements?”

Profit.co publishes SOC 2 Type II, ISO 27001, GDPR compliance, and a 99.9% uptime SLA on its strategic planning software page. Public sector procurement frequently adds jurisdiction-specific requirements beyond these, data residency, national accreditation schemes, or cloud authorization programmes, and those should be confirmed against your own framework rather than assumed from a general certification list.

12. Seven Mistakes in Public Sector Deployments

1. Measuring only what the agency controls

Safe, fair, and strategically empty. Output-only measurement reports activity indefinitely while the mission outcome stays flat.

2. Measuring only outcomes

The opposite failure. Holding staff accountable for population-level results they influence but do not control destroys the credibility of the whole system.

3. Replacing existing statutory measures

Profit.co’s guidance is that existing performance metrics typically become key results or KPIs supporting OKRs rather than being replaced. An implementation that discards mandated indicators creates a parallel reporting burden rather than reducing one.

4. Too many objectives

Named by Profit.co as one of the three most common causes of government OKR failure, alongside lack of leadership engagement and cascading too quickly. Its recommendation is three to five objectives per department with two to five key results each. Where arbitration is structurally hard, the cap does much of the prioritization work.

5. Treating budget execution as an increase measure

Underspending an appropriation is a finding, not a saving. Budget execution belongs in a control measure with a defined band.

6. Letting the decision record live in documents

Slide decks and minutes do not survive a transition in usable form. Decisions and assumptions need to be objects in the system, captured automatically as work proceeds.

7. Cascading too quickly

The second of Profit.co’s three named failure causes, and particularly damaging in large agencies where a premature cascade produces hundreds of objectives nobody can maintain. The phased approach is set out in Profit.co’s practical roadmap for public sector leaders.

13. A Rollout Sequence for an Agency

Phase 1, Settle the measurement model before configuring

• For each agency-level objective, name both the output the agency controls and the outcome it contributes to. If only one exists, the model is incomplete regardless of how good the objective sounds.
• Map existing statutory measures into the structure as key results or KPIs rather than planning to replace them.
• Agree how competing mission priorities will be arbitrated, and make the mechanism explicit, weighting, cost-per-outcome, or an escalation route.

Phase 2, Configure for continuity from day one

• Set decisions and assumptions up as tracked governance objects before the first cycle, not after the first transition.
• Structure the multi-year plan so it outlives the political cycle, with the annual and quarterly layers beneath it.
• Confirm that the audit trail is automatic and immutable, and that it survives personnel and ownership changes.

Phase 3, Pilot on one department with a full vertical slice

• Choose a department with both a clear output set and a genuine outcome exposure, so Gap 2 is tested rather than deferred.
• Hold to three to five objectives with two to five key results each, and connect measures that already exist in source systems so check-ins interpret data rather than enter it. Connector coverage is listed in the integrations catalogue.
• Run one full cycle including a review that produces recorded decisions, then test the continuity question directly: could someone new read this and understand why?

Phase 4, Extend by department, and connect to budget formulation

• Add departments rather than users, so each extension carries a complete output-to-outcome chain.
• Feed programme performance data into the next budget formulation cycle, which in an appropriated environment is where the real reallocation opportunity sits.
• Review the arbitration mechanism annually, it is the part most likely to have quietly reverted to informal practice. Role-level framing sits on Profit.co’s hub for strategy and transformation leaders, with the delivery view on its page for PMO leaders.

Profit.co reports most customers complete setup and run their first cycle within two to four weeks, with enterprise rollouts involving custom integrations typically taking four to eight weeks. For a public agency, expect longer, procurement, security accreditation, and the measurement-model work in Phase 1 are the pacing constraints, and none of them is a software task.