Innovation That Serves: How Public-Interest Innovation Differs From the Commercial Kind

Not all innovation points the same direction

Innovation is treated as an unqualified good, a word that ends arguments rather than starts them. But innovation always serves some goal, and the goal shapes everything: what gets built, who it is built for, and what happens to it once it works. Commercial innovation is organized to capture value for an owner. Public-interest innovation is organized to create value that stays available to the public. These are different disciplines, not the same discipline applied to nicer causes, and confusing them is how well-meaning public technology ends up behaving like a product that locks people in. This primer is about that difference and why it matters.

The argument is that public-interest innovation has distinct success criteria, openness, interoperability, durability, and freedom from capture, and that building it well means designing for those from the start rather than borrowing the commercial playbook and hoping for public outcomes.

The same tools, different objectives

The methods can look identical from the outside. Both kinds of innovation use modern software practice, iterate quickly, and aim to solve real problems well. The divergence is in the objective function. A commercial product succeeds by capturing and defending value: proprietary advantage, switching costs that keep customers in, features that differentiate against competitors. Those are rational goals for a business, and they produce real benefits.

Public-interest innovation has the opposite relationship to capture. Its job is to create value that remains open, reusable, and beyond the control of any single party, because the public it serves is not a customer base to be retained but a community to be equipped. Where a commercial product treats lock-in as an asset, public-interest innovation treats it as a failure. Where a commercial product guards its internals, public-interest innovation often succeeds precisely by being inspectable and reusable. The tools rhyme; the objectives are nearly inverted.

Why the commercial playbook misfires in public service

The trouble comes when public technology is built on commercial reflexes without adjusting the objective. The pattern is familiar from government and public-service technology. A point solution is procured because it works well on day one, and over time it accumulates dependencies that are difficult and expensive to unwind, until the institution is locked into a single vendor and a proprietary format it cannot easily leave. The innovation succeeded on commercial terms, capturing the customer, and failed on public terms, trapping the public investment.

This is why thoughtful public-sector practice increasingly argues for a different model: seeking solutions that multiple administrations can share, insisting on genuine openness and open standards in procurement, and maintaining a competitive market rather than a captured one. The aim is to harness the energy and discipline of the commercial world, the scale, the incentives, the speed, while preserving the transparency, interoperability, and freedom from lock-in that public service requires. It is not anti-commercial. It is about pointing commercial-grade capability at public-interest objectives, which the default playbook does not do on its own.

What public-interest innovation optimizes for

If commercial innovation optimizes for captured value, public-interest innovation optimizes for a different set of properties, and naming them makes the discipline concrete. Openness, so the public can see, trust, and build on what was made. Interoperability, so the work connects to other systems rather than walling itself off. Reusability, so value created once can serve many rather than being rebuilt repeatedly. And durability, so the innovation survives past its launch and its original team. These are not constraints bolted onto innovation to make it virtuous; they are the actual success criteria when the beneficiary is the public.

The honest complication is that these properties are harder to fund and sustain than commercial capture, because there is no owner whose profit motive pays for the upkeep. Public-interest innovation that achieves openness and interoperability still has to solve for who maintains it, which is the stewardship question the rest of this series takes up. Designing for openness without designing for durability produces a public good that quietly decays. Both have to be built in together.

What this means for public-interest infrastructure

Distinguishing the two kinds of innovation changes how a public-interest organization builds. The measure is not only whether something works but whether it works in a way that stays open, connected, reusable, and durable, which means the design choices that a commercial team would make to capture value are often exactly the choices a public-interest team must avoid. The discipline is to bring commercial-grade skill to non-commercial objectives, deliberately and from the outset.

This is the Foundation's concern applied to the act of building itself. Innovation that serves the public is a distinct craft with its own success criteria, and treating it as commercial innovation with a kinder mission statement is how public technology ends up captured, siloed, or abandoned. Build for openness, interoperability, reuse, and durability from the first design decision, and innovation genuinely serves. Borrow the capture playbook, and it serves whoever ends up owning it.

References

1. Linux Foundation Europe. Building Digital Public Infrastructure Through Open Source: Key Insights from UN Open Source Week 2025. Model of governments seeking shareable open-source solutions, insisting on open standards in procurement, and maintaining a competitive market rather than proprietary dependency. https://linuxfoundation.eu/newsroom/building-digital-public-infrastructure-through-open-source-key-insights-from-un-open-source-week-2025

2. Keystone Procurement. Vendor Lock-In in Public Sector ICT Procurement: Risks, Costs, and Strategies (2026). How point solutions accumulate dependencies and proprietary formats that trap public investment over time. https://keystoneprocurement.eu/vendor-lock-in-in-public-sector-ict-procurement-risks-costs-and-strategies/

3. SpruceID. Interoperability Without Lock-In: Why Standards Matter (2026). Standards-first design lets innovation accelerate rather than stall, fostering healthy vendor ecosystems and protecting public investment. https://blog.spruceid.com/interoperability-without-lock-in-why-standards-matter/

4. Public Digital. Digital public goods. Single-vendor custody risk and the question of whether a project with one dominant maintainer remains genuinely public. https://public.digital/pd-insights/signals/signals-5/digital-public-goods

5. Chatham House. The case for expanding digital public infrastructure (2025). Open APIs, open licensing, and open-source codebases create a flexible foundation others can build on while reducing lock-in. https://www.chathamhouse.org/2025/10/case-expanding-digital-public-infrastructure/08-conclusion-and-recommendations