An innovation can succeed in a market by attracting users and sustaining a business. When the same system affects education, public services, infrastructure or civic participation, its success has a wider meaning.

Public value asks whether the innovation improves a shared condition while respecting the rights and agency of the people it affects.

Adoption does not prove benefit

People may adopt a system because it is useful, because an institution requires it or because alternatives have disappeared. Usage is important evidence, but it does not explain the quality of the choice.

Evaluation should examine outcomes directly. Did access improve? Did decisions become more accurate or more understandable? Were waiting times reduced without shifting the burden to people with fewer resources?

Accountability must match influence

Systems that shape important opportunities need a visible owner and a process for correction. People should know when a technical system influences a decision and how to challenge information that is wrong.

Procurement does not transfer public responsibility to a vendor. Institutions remain accountable for how a system is selected, configured and used.

Accessibility is part of performance

A service that works well for most people but excludes a predictable group is not fully effective. Accessibility, language support and non-digital alternatives should be included in performance measures from the start.

This can improve the system for everyone. Designs that work across devices, abilities and stressful conditions tend to be clearer and more resilient.

Durability matters

Public systems often need to remain available longer than commercial product cycles. They require stable funding, exportable data, security updates and a plan for provider failure or technology change.

Short-term savings can become long-term costs when an institution loses the ability to operate or change its own service.

Participation improves the test

People who use and deliver a public service hold knowledge that formal requirements may miss. Involving them early can reveal practical risks and help define outcomes that matter outside the project team.

Public value changes the innovation test by asking more of success. Novelty, adoption and efficiency still matter. They sit beside accessibility, accountability, resilience and the durable improvement of a condition people share.