ABSTRACT
The U.S. federal government spends approximately $100 billion on IT annually — and fails to deliver the intended value from roughly 80% of those investments. Project overruns, underperforming systems, perpetual legacy debt, and a chronic failure to connect technology expenditure to mission outcomes represent one of the most costly and persistent management failures in public administration. Yet the same government that wastes billions on failed IT projects also executes some of the world’s most complex and consequential technology deployments — air traffic control, nuclear weapons management, Social Security payment processing, and pandemic response data infrastructure. The difference between success and failure in government IT is not primarily technical. It is managerial: the quality of mission definition, accountability structure, delivery methodology, and measurement discipline that determines whether a technology investment delivers digital transformation profit or becomes another line item in the IT project graveyard.
This article provides the complete framework for measuring and managing digital transformation ROI in government: six root causes of IT project failure with prevention strategies; a twelve-benefit taxonomy for quantifying technology value in mission terms; technology OKR examples for five agency types; a three-horizon technology portfolio management model; eight agile delivery health metrics aligned to the DORA research; an IT governance health checklist; and a practical guide to connecting technology investment data to Profit.co mission profit dashboards. The goal is not merely to avoid failure — it is to build the measurement and management discipline that makes government technology investments reliably generate the mission value that justifies their cost.
- $100B Federal Annual IT Spend FY2023 — the largest IT budget in the world
- 80% IT Projects Underperform cost overrun, schedule slip, or scope reduction (McKinsey/GAO)
- 6 Root Causes of Failure and proven prevention strategies for each
- 12 Mission-Value Benefit Types taxonomy for quantifying digital transformation ROI
1. The $80 Billion Problem: Why Government IT Fails
The scale of the government IT performance crisis — and the specific managerial failures that produce it.
In 2023, the U.S. federal government spent approximately $100 billion on information technology. By most reasonable estimates, roughly $80 billion of that investment either failed to deliver its intended value, ran significantly over budget, took substantially longer than planned, or produced systems that are underused, poorly adopted, or already obsolete by the time they launched. The IRS’s Customer Account Data Engine 2 (CADE2) — a modernization program that began in 2009 and consumed over $6 billion — still runs on a COBOL codebase. The VA’s Veterans Benefits Management System, launched in 2012 at a cost exceeding $1 billion, still processes a significant portion of claims manually. The healthcare.gov launch in 2013 spent $840 million to produce a system that crashed on its first day.
These failures are not primarily caused by the complexity of the technology. They are caused by predictable, well-documented managerial failures: poorly defined requirements that change throughout delivery; waterfall development methodologies that deliver everything or nothing; vendor relationships structured as cost-plus contracts with no incentive for performance; oversight processes that measure inputs and activities instead of outcomes; and a fundamental disconnect between the people who write the checks for technology and the people who understand what mission outcomes the technology is supposed to deliver.
The good news is that these failures are preventable. The DevOps Research and Assessment (DORA) research, the work of the U.S. Digital Service and 18F, the UK Government Digital Service’s delivery model, and a growing body of successful federal IT modernization projects all demonstrate that government technology investments can and do deliver transformative value — when they are designed, managed, and measured with the discipline that mission accountability requires.
2. Six Root Causes of Government IT Failure — and How to Prevent Each
The specific mechanisms through which government technology investments destroy value — and the proven prevention strategies that the best government IT programs apply.
McKinsey’s research on large government IT programs found that projects over $15M running for more than two years have a 66% probability of significant cost overrun, schedule delay, or scope reduction. But these aggregate statistics obscure the specific failure modes that determine outcomes. The six root causes below represent the most consistently documented drivers of government IT project failure — and each has specific, evidence-based prevention strategies that distinguish successful programs from unsuccessful ones.
| Root Cause | How It Destroys IT Project Value | Prevention Strategy |
|---|---|---|
| Requirements Volatility Without Change Control | Government IT projects accumulate scope changes throughout delivery — driven by policy changes, leadership transitions, new regulatory requirements, and stakeholder demands. Without rigorous change control, the project that was scoped for $40M becomes a $180M effort without anyone having approved the expansion. | Freeze requirements at project initiation; separate policy changes from technology changes; use iterative delivery to reduce the gap between requirements and implementation; establish a formal change control board with cost and schedule impact analysis for every change request |
| Waterfall Delivery in an Agile World | Most government IT projects still use waterfall delivery methodologies — requirements first, then design, then build, then test, then deploy — producing systems that were designed for problems that no longer exist when they finally launch. A 3-year waterfall project will launch a system designed for 2022 requirements in 2025. | Mandate agile or hybrid-agile delivery for all projects over $5M; require working software demonstrations every 90 days as a condition of continued funding; kill projects that cannot demonstrate working software within 6 months |
| Vendor Lock-In and Single-Source Dependencies | Government agencies frequently become so dependent on a single vendor for a core system that they lose the ability to negotiate, modernize, or switch providers. The vendor effectively becomes a captive annuity — able to charge premium prices for maintenance, modifications, and support because switching costs are prohibitive. | Modular contracting strategy (no single vendor for the full stack); open standards requirements (APIs, data formats, authentication); source code escrow; competitive re-procurement every 5–7 years; cloud-first policy to reduce infrastructure lock-in |
| Lack of Product Ownership | Government IT projects are typically managed by contracting officers and project managers — not by product owners who are accountable for the actual mission value the technology delivers. When no one is accountable for whether the system improves mission outcomes, the project defaults to delivering technical specifications rather than mission value. | Designate an empowered government Product Owner for every major IT investment — a career civil servant with decision-making authority over product direction, not just contract administration; require the Product Owner to set OKRs for mission value delivery, not just technical deliverables |
| IT Investment Measurement Theater | The federal IT investment review process (OMB Exhibit 300, TechStat sessions, OMB MAX portfolio) generates enormous documentation of inputs and activities — project schedules, cost tracking, earned value management — but rarely measures whether the technology is improving the mission outcomes it was procured to improve. | Require mission outcome OKRs (not just project milestone OKRs) for every IT investment over $5M; connect IT investment review to mission profit dashboard data; measure technology ROI in mission terms, not just cost-per-transaction |
| Security as Afterthought | Security requirements are frequently added late in the delivery lifecycle — after architecture decisions are locked in — producing systems that require expensive remediation to achieve ATO (Authority to Operate), often delaying launches by 12–24 months and adding 20–40% to project cost. | Security by design from day one: security architect on project team from requirements stage; cloud-native security patterns reduce custom security code; DevSecOps pipeline with automated security testing; FedRAMP-authorized cloud services reduce ATO timeline from 18 months to 3–6 months |
Figure 1: Six Root Causes of Government IT Project Failure — mechanisms, and prevention strategies
3. The Mission-Value Benefit Taxonomy
A twelve-category framework for quantifying the full mission value of technology investments — moving beyond cost savings to capture efficiency, outcome, and strategic benefits.
The most consequential measurement failure in government IT investment is the habit of measuring ROI exclusively in cost savings — labor hours avoided, infrastructure costs eliminated, and paper forms replaced by digital ones. Cost savings are real and important, but they represent only a fraction of the value that well-executed technology investments generate. The most important benefits — program participation rate improvements, processing time reductions that reduce citizen burden, fraud prevention, and trust improvements — are mission outcome benefits that cost-saving frameworks systematically ignore.
The twelve-category benefit taxonomy below provides a comprehensive framework for quantifying the full value of technology investments across three categories: efficiency benefits (what government saves), mission outcome benefits (what mission results improve), and strategic and intangible benefits (what future capacity and trust the investment creates). Each benefit type includes a calculation methodology and an illustrative example to make the quantification concrete.
| Benefit Type | Calculation Methodology | Illustrative Example |
|---|---|---|
| EFFICIENCY BENEFITS | ||
| Labor Hours Avoided | Staff time freed by automation, self-service, or process simplification. Calculated as: (hours per transaction × transaction volume × staff cost rate) − new system operating cost. FTE hours × hourly fully-loaded cost; transaction volume × time per transaction; can be validated by pre/post time study | IRS e-file: 45 minutes/return manual processing → 3 minutes automated = 42 min × $28/hr × 150M returns = $2.9B annual labor value |
| Facility & Infrastructure Cost Avoidance | Physical space, equipment, and infrastructure costs avoided by digital service delivery. Most directly relevant for in-person to digital channel shift. Square footage × cost per square foot; equipment lifecycle cost; maintenance cost avoided | DMV appointment system: 30% reduction in walk-ins → 4 office locations consolidated → $2.1M annual lease/facilities savings |
| Error and Rework Cost Reduction | Cost of processing errors, appeals, corrections, and re-adjudications reduced by improved data quality, validation, and decision support tools. Error rate × average cost per error (including staff time, delay cost, appeal processing) × annual volume | Benefits processing: 19% → 8% error rate × $340 average rework cost × 180,000 applications = $6.7M annual savings |
| Procurement and Contract Consolidation | Cost savings from consolidating redundant systems, renegotiating vendor contracts, and eliminating licenses for unused technology assets. Annual license fees + maintenance costs for retired systems; contract renegotiation savings; in-sourcing savings | Legacy system consolidation: 14 redundant HR systems → 1 modern platform = $4.2M annual license savings + $1.1M maintenance |
| MISSION OUTCOME BENEFITS | ||
| Program Participation Rate Improvement | Increase in eligible citizens actually receiving benefits, permits, services, or assistance — driven by reduced application burden, better eligibility screening tools, or improved awareness. The highest-mission-value benefit category for most social service agencies. Take-up rate increase × eligible population × average annual benefit value per recipient | SNAP digital eligibility screener: 38% → 52% take-up in target counties × 45,000 eligible non-participants × $2,400 average annual benefit = $15.4M additional social value annually |
| Processing Time Reduction: Mission Impact | Reduction in time citizens wait for decisions, benefits, or approvals — measured in the cost of the waiting period to the citizen and to program outcomes (delayed treatment, foregone economic activity). Average processing time reduction × daily cost to citizen × annual application volume; for benefits: delayed benefit × wait period × volume | VA claims: 122 → 75 day average × $42/day veteran financial stress cost proxy × 1.2M claims = $2.4B annual mission value (conservative) |
| Fraud Detection and Improper Payment Reduction | Revenue protected and improper payments avoided through improved data matching, anomaly detection, and identity verification. Directly quantifiable in dollars. Improper payment rate × program expenditure × detection improvement factor; fraud recovered × recovery rate | Medicaid data analytics: 1.2% improper payment rate × $800B program × 15% detection improvement = $1.4B annual improper payment reduction |
| Regulatory Compliance and Safety Outcomes | Improvements in safety, environmental, or regulatory compliance driven by better monitoring systems, digital inspection tools, or automated compliance tracking. Incident rate reduction × average incident cost (direct + indirect); penalty avoidance; insurance cost reduction | Food safety digital inspection: 18% reduction in critical violations × $85,000 average cost per outbreak × 2,400 annual inspections = $3.7M annual safety value |
| STRATEGIC & INTANGIBLE BENEFITS | ||
| Citizen Trust and Confidence | Improvement in measured citizen trust in government, satisfaction scores, and democratic participation — driven by better service experiences. Difficult to monetize directly but strongly correlated with program compliance and long-term cost outcomes. ACSI/satisfaction score improvement; trust index; program compliance rate change; complaint volume reduction | IRS online account modernization: ACSI score +7 points; voluntary compliance rate +0.3% × $4.2T revenue base = $12.6B potential revenue impact (indirect) |
| Workforce Attraction and Retention | Improvement in the agency’s ability to attract and retain talent — particularly technology talent — driven by modern digital tools and reduced administrative drudgery. HR cost savings plus mission capability improvement. Attrition rate × replacement cost (typically 50–150% of annual salary); time-to-fill improvement; offer acceptance rate | Modernized HR/payroll system: 12% → 7% annual attrition × $85,000 average replacement cost × 2,400 FTE = $10.2M annual retention value |
| Data Asset Value Creation | Value of structured, accessible data created as a byproduct of digital service delivery — enabling better policy analysis, fraud detection, program evaluation, and interagency coordination. Analytics use cases enabled × decision quality improvement value; research value; audit quality improvement | Longitudinal case management system: research data enables 6 new program evaluations annually → $2.4M evaluation cost avoidance + improved policy ROI on $240M program |
| Resilience and Continuity Value | Reduction in operational disruption risk — the value of systems that maintain service delivery during natural disasters, cyberattacks, pandemic response, and other continuity events. Probability of disruption × cost per disruption day × resilience improvement factor; cyber incident cost avoidance | Cloud migration: on-premise outage probability reduced from 3% to 0.4% annually × $2.8M daily service disruption cost = $728K expected annual value |
Figure 2: Twelve-Category Mission-Value Benefit Taxonomy — benefit types, calculation methodologies, and illustrative examples
3.1 Building the Business Case: The Total Value Calculation
A rigorous technology investment business case combines benefits from all three categories, discounted appropriately for realization probability and timeline, against the full cost of the investment including implementation, transition, training, and steady-state operations. The calculation takes the form: Total Benefit Value = Σ(Efficiency Benefits) + Σ(Mission Outcome Benefits) + Σ(Strategic Benefits × Probability × Discount Factor).
The most common analytical error in government technology business cases is using an unrealistically high probability for benefit realization. A $40M legacy system modernization program has perhaps a 60% probability of achieving its full efficiency benefits on schedule, a 45% probability of achieving its mission outcome targets, and a 30% probability of realizing its strategic benefits within 5 years. Applying honest probability estimates — based on the historical track record of comparable programs — produces a conservative business case that is more credible to oversight bodies and more useful for investment prioritization than an optimistic case that assumes everything goes right.
4. Technology OKRs: Five Agency Examples
Complete OKR templates for five government technology investment contexts — demonstrating how to balance mission outcome, technical delivery, and financial accountability KRs.
Technology OKRs must balance three types of Key Results in every investment: mission outcome KRs (the ‘so what’ — how does this investment improve what government achieves for citizens?), technical delivery KRs (the ‘how’ — what technical milestones confirm the investment is on track?), and financial accountability KRs (the ‘worth it’ — are we realizing the cost savings and ROI targets that justified the investment?). Investments with only technical KRs measure activity, not value. Investments with only mission KRs lack the operational tracking needed to manage delivery risk. All three types are required for a complete accountability picture.
| Agency / Context | Investment Description | Sample OKRs (Mission + Technical + Financial) |
|---|---|---|
| Federal Benefits Agency | Legacy System Modernization ($48M, 3-year program) |
|
| State DMV | Digital Service Modernization ($12M, 18-month project) |
|
| City IT Shared Services | Cloud Migration & Infrastructure Modernization ($6.8M) |
|
| Federal Law Enforcement / Regulatory | Data Analytics & AI Platform ($22M, 2-year program) |
|
| State/Local Health IT | Health Information Exchange (HIE) Expansion ($9.4M) |
|
Figure 3: Technology OKR Examples — five agency types with balanced mission, technical, and financial Key Results
5. The Three-Horizon Technology Portfolio
The portfolio management framework that ensures government technology investment is balanced across operational continuity, active modernization, and future capability — with OKR measurement for each horizon.
Individual technology project management and technology portfolio management are different disciplines requiring different accountability structures. At the portfolio level, the strategic question is not ‘Is this project on schedule?’ but ‘Is our overall technology investment allocation producing the right balance of operational continuity, mission transformation, and future capability development?’ The McKinsey Three Horizons framework, adapted for government technology portfolio management, provides the structure for this conversation.
Most government technology portfolios are dramatically over-weighted toward Horizon 1 (Run: keeping existing systems operational) and under-invested in Horizon 2 (Transform: modernizing for mission). The chronic accumulation of technical debt in government systems is both a cause and a consequence of this imbalance: old systems require ever-increasing maintenance investment, consuming budget that could fund the modernization programs that would eliminate the debt.
| Horizon | Label | Typical Budget % | What Belongs Here | How to Measure Value |
|---|---|---|---|---|
| Horizon 1 | RUN: Keep the Lights On | ~70% of typical government IT budget | Legacy system maintenance, security patching, helpdesk support, routine infrastructure operations, license renewals, minor enhancements to existing systems. |
The baseline cost of keeping government functional. Value is measured by absence of failure: uptime, security incidents avoided, service continuity. Too much Horizon 1 = organizational stagnation.
|
| Horizon 2 | TRANSFORM: Modernize for Mission | 25% target allocation | Legacy system migrations, digital service redesigns, process automation, cloud migrations, data platform modernization — the investments that transform existing capabilities. |
The core of digital transformation ROI. Value is measured in mission outcomes improved, costs reduced, and citizen experiences transformed. Under-investment here = perpetual legacy debt accumulation.
|
| Horizon 3 | INNOVATE: Build Future Capability | 5% target allocation | AI/ML pilots, emerging technology experiments, novel service delivery models, cross-agency data sharing pilots — investments in capabilities that don’t yet exist at scale. |
The agency’s innovation pipeline. Value is measured in lessons learned, viable concepts for Horizon 2 investment, and competitive positioning for future technology cycles. Too little = falling behind; too much without Horizon 2 = perpetual piloting.
|
Figure 4: Three-Horizon Technology Portfolio Framework — what belongs in each horizon, target allocation, and OKR measurement approach
5.1 The Technical Debt OKR
Technical debt — the accumulated cost of outdated, inefficient, or insecure technology that the agency operates — is one of the most under-measured dimensions of government IT performance. An agency that has not quantified its technical debt cannot make rational investment decisions about where to prioritize modernization, cannot honestly assess its cybersecurity risk posture, and cannot answer the basic stewardship question: are we leaving our infrastructure in better or worse condition than we found it?
Profit.co’s government IT module supports technical debt tracking as an explicit OKR dimension: debt is inventoried, quantified in annual maintenance cost terms, and reduced through specific modernization investments tracked as Key Results. The target is a declining technical debt ratio — the proportion of IT budget consumed by Horizon 1 maintenance on legacy systems — measured quarterly and reported to the CIO and CFO as a strategic portfolio health indicator.
6. Agile Delivery Health: The Eight DORA Metrics
The research-validated software delivery performance metrics that distinguish high-performing government technology programs — and how to track them in Profit.co.
The DevOps Research and Assessment (DORA) annual State of DevOps report, based on over a decade of research across thousands of technology teams, has identified the specific metrics that most reliably predict software delivery performance and organizational outcomes. These metrics — deployment frequency, lead time for changes, change failure rate, and mean time to restore, alongside four additional delivery health measures — provide a research-grounded framework for assessing whether a government IT program is being delivered with the discipline and capability that mission outcomes require.
Government oversight bodies and program managers can use these metrics not as performance ratings of individual teams but as organizational diagnostics: what is the current delivery capability of this program, and is it improving or deteriorating over the delivery lifecycle? A program that shows declining deployment frequency and increasing lead time three months into delivery is accumulating delivery risk that will manifest as cost overrun and schedule delay if not addressed — and these signals are visible months before the cost and schedule problems become irrecoverable.
| Agile Health Metric | What It Measures and Why It Matters | Performance Benchmarks (DORA) | Measurement Cadence |
|---|---|---|---|
| Deployment Frequency | How often the team deploys working software to production or a production-like environment. The single most important predictor of software delivery performance in the DORA research. | Elite: multiple times/day; High: daily to weekly; Medium: weekly to monthly; Low: monthly to quarterly | Weekly during active delivery; target: at least biweekly deployments after initial stabilization |
| Lead Time for Changes | Time from code commit to production deployment. Measures the efficiency of the delivery pipeline and the team’s ability to respond quickly to user needs and security vulnerabilities. | Elite: <1 hour; High: <1 day; Medium: 1 day–1 week; Low: 1–6 months | Track from first day of delivery; long lead times early signal pipeline investment needed |
| Change Failure Rate | % of deployments that cause a production incident requiring hotfix, rollback, or emergency patch. High rates indicate test coverage gaps or insufficient code review. | Elite: 0–15%; High: 16–30%; Medium: 31–45%; Low: 46–60%+ | Any rate above 30% requires root cause analysis; track alongside deployment frequency to avoid perverse incentives |
| Mean Time to Restore (MTTR) | Average time to restore normal service after a production incident. Measures team readiness to respond, quality of monitoring and alerting, and rollback capability. | Elite: <1 hour; High: <1 day; Medium: <1 week; Low: 1–6 months | Requires incident tracking system; improves naturally as deployment frequency increases and test coverage grows |
| Sprint Velocity (Story Points) | Measure of team output per sprint. Most useful as a relative trend indicator within a team — not for cross-team comparison or as a proxy for productivity. | Stable velocity: team is predictable; increasing velocity: team is improving; volatile velocity: planning or execution issue | Track 3-sprint rolling average; use for capacity planning, not performance evaluation of individuals |
| Backlog Health | Quality and prioritization of the product backlog: % of backlog items that are estimated, prioritized, and ready to be worked in the next 2 sprints. Predicts team predictability and reduces planning meeting waste. | Healthy: 2+ sprints of ready, estimated stories; Unhealthy: sprint planning frequently delayed by unclear requirements or missing estimates | Review monthly with Product Owner; backlog refinement is the Product Owner’s most important ongoing responsibility |
| Working Software Demonstration Rate | % of sprints that produce a working software demonstration to stakeholders. The government-specific accountability mechanism that replaces traditional milestone reporting with real evidence of progress. | Target: 100% — every sprint produces a demonstrable increment; any sprint that does not is a signal of systemic delivery risk | Required by OMB for Agile contracts; most important accountability mechanism for oversight bodies; replaces slide-ware with working software |
| User Story Acceptance Rate | % of user stories accepted by the Product Owner without rework at sprint review. Low acceptance rates signal misalignment between developer understanding and product owner expectations — often indicating that requirements were insufficiently clear. | Target: ≥ 90% acceptance; rates below 75% indicate systematic requirements clarity problem | Track sprint-by-sprint; declining trend is an early warning of delivery risk before cost or schedule overrun becomes visible |
Figure 5: Eight Agile Delivery Health Metrics — definitions, DORA performance benchmarks, and measurement cadence
7. IT Governance Health Check
A ten-practice governance checklist for CIOs and program managers — the management infrastructure that makes technology investment accountability structurally possible.
Technology investment performance is as much a governance problem as a technical one. Agencies with strong governance structures — clear investment review processes, mission-linked performance measurement, agile delivery mandates, and professional product ownership — consistently deliver better technology outcomes than agencies with weak governance, regardless of the technical complexity of their systems. The governance health check below identifies the ten practices that most reliably distinguish high-performing government technology organizations from low-performing ones.
| Governance Practice | Status | What ‘Done Well’ Looks Like |
|---|---|---|
| Technology Business Management (TBM) Framework | Adopted | Agency has classified IT spending by TBM taxonomy (Run/Grow/Transform; Business Capability; IT Tower) enabling apples-to-apples comparison with peer agencies and OMB benchmarks |
| Capital Planning and Investment Control (CPIC) | Required (Federal) | All IT investments >$5M documented in OMB Exhibit 300/53; investment review board meets quarterly; OMB IT Dashboard rating maintained above ‘Needs Attention’ |
| Agile Delivery Mandate | Target | All new development projects >$5M required to use Agile or hybrid-Agile delivery with biweekly sprint demonstrations; waterfall delivery requires CIO waiver |
| Mission OKR Linkage for IT Investments | Target | Every IT investment >$2M has at least 2 mission outcome OKRs (not just technical/schedule OKRs) approved by both the CIO and the mission program owner |
| Security Authorization (ATO) Pipeline | Required (Federal) | Continuous ATO (cATO) process in place; no systems operating without valid ATO; FedRAMP-authorized services used by default; ATO timeline target <90 days for new SaaS |
| Vendor Contract Structure | Target | Modular contracting for all major systems (no single vendor for full stack); performance-based contracts with mission outcome metrics; source code escrow required; competitive re-procurement scheduled |
| Tech Debt Inventory | Target | Formal technology debt register maintained; debt quantified in dollar terms (annual maintenance cost + risk); debt reduction targets set as OKRs; tech debt ratio tracked quarterly |
| Data Governance Policy | Required | Data governance framework published; data stewards designated for all major data assets; open data policy; privacy impact assessments for all new data collections |
| IT Portfolio Review Cadence | Required | Monthly IT portfolio review by CIO/CISO; quarterly investment review board; annual strategic IT plan aligned to agency mission OKRs; TechStat sessions for at-risk investments |
| Workforce Capability Assessment | Target | Annual IT workforce skills assessment; upskilling OKRs for cloud, cybersecurity, data, and agile capabilities; succession plan for CIO-level and key technical roles |
Figure 6: IT Governance Health Check — ten practices, required status, and what ‘done well’ looks like
8. Connecting Technology Investments to the Mission Profit Dashboard
How to configure Profit.co so that technology program OKRs feed directly into the agency’s mission profit dashboard — making digital transformation visible as a mission performance driver.
- Step 1: Create the technology investment OKR hierarchy: In Profit.co, create an OKR Objective for each major technology investment (>$2M). Link each technology Objective to the mission OKRs it is designed to support — making the mission linkage explicit and traceable. Technology OKRs that cannot be linked to a mission OKR are candidates for cancellation.
- Step 2: Configure the three KR types for each investment: For each technology Objective, set mission outcome KRs (improvement in the mission metric the technology is designed to move), technical delivery KRs (working software milestones, DORA metric targets), and financial accountability KRs (cost savings realized, ROI milestone). Require all three types for investments over $5M.
- Step 3: Set up automated data feeds for technical metrics: Configure CI/CD pipeline integration to automatically update deployment frequency and lead time KRs from the development toolchain. Configure cloud cost management tools to update financial KRs automatically. Manual check-ins cover mission outcome metrics where automated feeds are not available.
- Step 4: Build the technology portfolio dashboard: Create a Profit.co dashboard view that shows all technology investments organized by horizon (Run/Transform/Innovate), with their current KR achievement scores, risk ratings from the AI Progress Agent, and planned vs. actual cost. This is the CIO’s primary portfolio management view.
- Step 5: Connect technology KRs to mission metrics: Where a technology investment is designed to improve a specific mission outcome metric (processing time, error rate, citizen satisfaction), configure Profit.co to display the technology KR and the mission outcome metric on the same dashboard panel — making the causal linkage visible and tracking whether the technology investment is actually moving the mission needle.
- Step 6: Report to oversight bodies from the platform: Use Profit.co’s executive report generation to produce the quarterly IT investment performance report for OMB, oversight boards, and congressional staff. The report should show working software milestones met, mission outcome progress, financial performance vs. business case, and agile delivery health metrics — all generated from the platform with AI-drafted narrative.
9. Conclusion: Technology as Mission Infrastructure
Government technology is not an end in itself. It is infrastructure for mission delivery — the same way highways are infrastructure for commerce, and public health systems are infrastructure for population health. The standard for evaluating technology infrastructure is not whether the infrastructure exists, but whether it enables the mission outcomes that justify its cost.
The agencies that lead on digital transformation profit are those that hold their technology investments to this standard from the first day of the project: What mission outcome will improve when this technology is deployed? How much will it improve? By when? Who is accountable for the improvement — not the deployment? These questions, embedded in the OKR framework as mission outcome Key Results, transform technology investment from a procurement exercise into a mission performance strategy.
The $80 billion that the federal government wastes on underperforming IT projects every year is not primarily a technology failure. It is a measurement and accountability failure — the consequence of an investment culture that rewards completion of technical milestones and penalizes the honest acknowledgment of mission gaps that those milestones were supposed to close. Building the measurement discipline to hold technology investments accountable for mission value — using the benefit taxonomy, the OKR framework, the agile delivery health metrics, and the governance practices in this article — is how government begins to close that gap. The technology already exists to do it. The management discipline is what remains to be built.