Topic 1.1 — Introduction to Public Value

Why this matters in public value

Ask a hospital finance director, a city parks commissioner, or the executive director of a small charity how they know their work is worth doing, and you rarely get a confident answer built on one clean metric. A private firm can point to profit: if customers keep paying more than a good costs to produce, the firm is creating value, and if they stop, the firm fails. Public and social-sector organizations have no equivalent single signal, because much of what they produce — clean streets, due process, a place a family can rely on when things go wrong — is a public good never sold at a price that reveals what it is worth to the people who receive it.

This gap creates a real, current tension for public managers and social-sector leaders. Governments and non-governmental organizations (NGOs) are asked, in the same budget cycle, to behave like efficient businesses — cut cost per unit, chase key performance indicators — and to behave like the pure instrument of a democratic or fiduciary mandate: do only what the manifesto promised, or only what the founding grant specified. Neither test on its own settles whether a specific programme deserves its budget this year. A rigid efficiency test undervalues services that exist precisely because no market would provide them at an affordable price; a rigid mandate test undervalues the judgement that public managers exercise translating a broad mandate into a changing world.

Public value theory exists to close this gap. It gives public and social-sector leaders a vocabulary for justifying their work that is neither pure market economics nor pure electoral or fiduciary mandate, but a third, distinct standard: is this something that citizens, as a collective, would authorize spending shared resources to produce? This topic introduces that standard and the framework built to apply it, at a level detailed enough to use immediately. It leaves the deeper mechanics of the framework to (see Topic 1.2 — The Strategic Triangle: Legitimacy, Value, and Capacity).

Core concepts

Public value is what a public or social-sector organization contributes to society, judged by what citizens, collectively, would regard as worth the shared resources spent producing it. Harvard professor Mark H. Moore coined the term as the public-sector counterpart to shareholder value: where a company's board asks whether an investment will return more than it costs shareholders, a public manager should ask whether an initiative will return more than it costs citizens, broadly conceived to include money, authority, trust, and freedom foregone. Public value is not the same as popularity — a majority can want something that turns out not to be worth having — and it is not the same as market price.

Moore's device for making public value operational is the strategic triangle: a public manager's plan is sound only when it satisfies three tests at once. The first leg is legitimacy and support — whether the people and institutions who must say yes (elected overseers, funders, courts, the public) actually authorize the effort, a question that rests on the wider concept of political legitimacy and is distinct from formal accountability lines, which are the dedicated subject of (see Topic 3.4 — Accountability, Transparency, and Legitimacy). The second leg is the value proposition — whether what the effort produces is genuinely worth the resources it consumes. The third leg is operational capacity — whether the organization, on its own or through partners, can actually deliver what it proposes. This topic introduces the triangle only at this level; its interactions and trade-offs are the dedicated subject of (see Topic 1.2 — The Strategic Triangle: Legitimacy, Value, and Capacity).

Public value theory sits deliberately between two older stories about why public bodies exist. The market-failure story treats government as a patch for the gaps markets leave, including goods that markets under-provide (see Topic 1.3 — Market Failure and Government Failure). The mandate story treats government as the executor of whatever the electorate or a funder most recently instructed. Both are true as far as they go, but neither explains the ordinary, daily judgement calls that public administration practitioners make within a necessarily general mandate — which is also why the field moved beyond New Public Management, which judged public bodies mainly by private-sector efficiency measures (see Topic 3.1 — Public Administration Systems and Models).

A related idea, developed by public-administration scholar Barry Bozeman, is publicness: 'public' and 'private' are not watertight boxes but a matter of degree, since even private organizations are constrained by public authority and government bodies rely on market mechanisms. A national ministry, a regional water utility, and a nonprofit organization delivering the same service sit at different points on one spectrum, and each still needs a theory of the value it creates, not only a theory of its legal form. Value pluralism — public value as several distinct, sometimes conflicting goods such as liberty, equity, efficiency, and security, not one scalar quantity — is introduced properly in (see Topic 1.4 — Public Goods, Merit Goods, and Value Pluralism).

Finally, public value theory reframes who counts as a producer of value. Citizens and the wider civil society that sits between the state, the market, and the family are not only voters or customers; they often co-produce the outcome alongside the organization, from parents co-producing a child's education to residents co-producing neighbourhood safety. This dimension is the dedicated subject of (see Topic 1.5 — Stakeholders, Citizens, and Co-Production); here, it matters mainly as a reminder that operational capacity often lives partly outside the organization's own walls.

Best practices

Write the public value proposition down, in one sentence, before drafting a business case. If a team cannot state what value a programme creates and for whom, the business case will paper over that gap with output targets instead of resolving it.
Name your authorizing environment explicitly, not just your budget line. List every body and constituency whose consent, tacit or explicit, keeps a programme alive: a legislature, a board, a regulator, a funder, the people who use the service.
Ask three separate questions, never one collapsed question. 'Is it authorized?', 'is it worth doing?', and 'can we deliver it?' are distinct tests that can each fail independently, and treating them as one hides exactly the failures the strategic triangle is designed to surface.
Treat legitimacy as earned continuously, not granted once. An election, an appointment, or a founding grant confers authority at a point in time; it does not certify every subsequent decision indefinitely.
Distinguish output volume from public value. Counting more clinic visits, permits issued, or meals served describes activity, not value; the relevant question is whether that activity produced an outcome citizens would judge worth the cost (see Topic 2.1 — The Public Value Scorecard and Outcomes Frameworks).
Use shared vocabulary across government and the social sector deliberately. A city agency and a nonprofit delivering adjacent services often describe the same underlying value in incompatible language; adopting a common three-legged vocabulary makes joint funding bids and partnerships easier to negotiate honestly.
Resist collapsing the case for a programme into a single number. A cost-per-unit figure or a satisfaction score is useful evidence but addresses at most one leg of the triangle; present all three side by side.
Revisit the value proposition whenever the authorizing environment shifts materially. A change of political leadership, a funder's new strategy, or a shift in public attitudes can turn a previously well-authorized programme into a contested one overnight.
Document who benefits and who pays, as two separate lists. Public value claims are strongest when a leader can say plainly who gains and who bears the cost, because the two groups are rarely identical in public and social-sector work.
Treat operational capacity claims as testable, not aspirational. 'We can deliver this' is a falsifiable claim about staffing, systems, and partner reliability, and it should be tested against delivery history on comparable work before it goes into a plan.

Questions to discuss with your team

What would our organization stop doing if every programme had to pass all three tests of the strategic triangle? Most organizations carry at least one activity that persists on inertia rather than active authorization, proven value, or confirmed capacity. It usually survives because no single leg of the triangle is ever tested against it directly, so its weakness never becomes anyone's explicit problem to solve. Naming it out loud is uncomfortable, which is exactly why it is worth doing as a team exercise rather than leaving it to one person's judgement. Use this question to surface candidates, not to make a final call in the same meeting — the point is to notice where the three tests have quietly stopped being asked.

Who, specifically, makes up our authorizing environment right now, and has that list changed in the past two years? Many teams can name their formal reporting line but struggle to name everyone whose ongoing consent actually matters: a funder's new leadership, a community group that has grown more vocal, a regulator with new powers. A list built from memory in the meeting itself, rather than copied from an old document, usually reveals gaps faster than either. Write the list from scratch rather than pulling last year's version, because authorizing environments drift quietly and the drift is easy to miss from inside the organization. Compare the new list with whatever list, if any, was used the last time a major decision was made.

Where are we currently substituting a market metric for public value, and where are we substituting a mandate for it? Teams often default to whichever justification is easiest to produce: a unit cost if the finance function is strong, a reference to the founding mandate if it is not. Neither substitution is wrong to mention, but each is incomplete on its own, and relying on either exclusively lets the other two legs of the triangle go unexamined. Use this question to find the places where one leg of the triangle is doing all the work that should be shared across three. Pick one current programme and try answering the value-proposition question without reaching for either shortcut.

If someone challenged us to justify our budget without saying either 'the market wants this' or 'we were elected or funded to do this', what would we say? This question forces the value-proposition leg into the open, independent of legitimacy and independent of price. A good answer names a concrete outcome for a specific group of people; a weak answer restates the organization's existence as its own justification. Practising the answer in the team's own words, rather than borrowing a mission statement, tends to expose gaps fast. Ask each person in the room to answer separately before comparing notes, since a shared script often hides disagreement that a written mission statement would not reveal.

Which of our current activities have strong legitimacy but weak delivery capacity, or the reverse? A programme with political backing and funding but no realistic delivery plan behind it, or a highly capable delivery team working on something nobody outside the organization has actually authorized, are both common and both risky in different ways. Neither failure is visible from a single leg of the triangle alone, which is why it needs to be asked as a deliberate cross-check rather than left to come up on its own. Map a handful of current activities against this question honestly, using recent delivery evidence rather than confidence alone. Where the two legs pull apart sharply, treat that as the priority for the next planning cycle, not a footnote.

How do we know the value we believe we create is the value our stakeholders actually recognize? Organizations can be sincerely convinced of their own value proposition while the people meant to benefit, or the people meant to authorize it, see something different. That gap rarely announces itself; it shows up later as falling support, renewed grants that come with new conditions, or quiet disengagement from the people a programme was meant to serve. Discuss what evidence — direct feedback, independent evaluation, complaints data, renewed funding — would tell you if your internal story and your stakeholders' story had quietly diverged. Agree, as a team, on which one piece of evidence you would trust enough to change course on.

In practice: a public value example

Consider a mid-sized city government weighing whether to fund a new youth employment programme from a shrinking discretionary budget. The parks and recreation department has proposed the programme for three years running; each time it was judged a good idea in principle and left unfunded, because nobody answered, together, whether it was authorized, worth doing, and deliverable.

This year, the department's director works through the three legs of the strategic triangle before writing the funding request. On legitimacy, she maps the authorizing environment properly: the city council has raised youth unemployment in three of the last four public sessions, a coalition of local employers has offered to co-fund placements, and a community organization has asked for exactly this programme for two years — a documented case, not an assumed one.

On the value proposition, she resists reducing the case to 'it will create 200 summer jobs', setting out instead what those jobs are meant to change: movement on youth unemployment in the two most affected districts and a credible pathway into the employers' own entry-level hiring. She is explicit that some of this value is hard to monetize and will only be visible after several years, rather than inflating a single number to make the case look tidier than it is.

On operational capacity, she is deliberately sceptical of her department's ability to deliver alone. It has run smaller placement schemes competently but never managed employer relationships at this scale, while the community organization has that relationship experience but no placement infrastructure; rather than overpromise, she proposes a delivery partnership and names the capacity gap directly in the request.

The council approves a two-year pilot, smaller than originally proposed, with the partnership and clear reporting points built in from the start — a decision made possible not by a stronger pitch, but by a case that named all three legs honestly, including where they were weak. This scenario is illustrative only; it does not describe any actual city, department, or programme.

Four sector lenses

Local government

Local authorities sit closest to the citizens who both authorize and receive a service, which makes the legitimacy leg unusually visible and fragile: a single poorly handled public meeting can shift an authorizing environment overnight in a way a national ministry rarely experiences as sharply. Local leaders also carry the smallest operational margin for error, since capacity gaps show up immediately as visible service failures rather than abstract policy underperformance.

National government

National governments usually have the deepest formal mandate and widest resource base, which makes it tempting to treat legitimacy as settled by the last election and to focus almost entirely on value and capacity. That temptation is a trap: a national mandate is broad precisely because it was not written with any specific programme in mind, so a defensible case for a specific initiative still needs the full three-legged test, at a scale where capacity failures can affect millions of people at once.

Nonprofit and NGO leaders often have the most explicit value proposition of any of the four lenses, expressed in a mission statement, but frequently the least stable authorizing environment, since funders, boards, and beneficiary communities can each withdraw support independently and on different timelines (see Topic 3.8 — Social Sector and Nonprofit Management). The absence of either a market price or an electoral mandate makes the strategic triangle especially useful here: it gives a nonprofit board language for oversight that is not borrowed uncomfortably from corporate or government practice.

Multilateral and international

Multilateral and international bodies operate with an authorizing environment split across member states with different, sometimes conflicting interests, which makes legitimacy a matter of ongoing diplomacy rather than a single domestic mandate. Operational capacity is frequently delivered indirectly, through national governments or local NGOs rather than the body's own staff, so the capacity leg has to be assessed across the whole delivery chain, not just the secretariat that designed the programme.

Common failure modes

Value colonization by cost accounting. When an organization cannot easily measure its value proposition, it is tempting to let whatever is easiest to count — cost per unit, throughput, response time — stand in for value itself. This causes the organization to optimize for the measured proxy at the expense of the outcome it was meant to represent, and it costs the organization its ability to notice when efficient delivery is producing the wrong thing well.

Legitimacy capture. An authorizing environment can quietly narrow to whichever constituency is loudest or best organized, while the broader public interest the organization is meant to serve goes unheard. This causes programmes to drift toward the captured constituency's preferences, and it costs the organization its wider legitimacy the moment that group's interests diverge from everyone else's.

Capacity theatre. Organizations sometimes claim delivery capability they do not have, relying on optimism or a partner's unconfirmed promise rather than delivery history. This causes commitments to be made that cannot be met, costing the organization credibility that is far more expensive to rebuild than the original programme would have cost to fund properly.

Mandate confusion. Treating a single election result, grant letter, or founding statute as a permanent, self-renewing justification for every subsequent decision conflates a moment of legitimacy with an ongoing one. This causes organizations to keep running programmes long after the circumstances that authorized them have changed, and it costs them the ability to notice when support has quietly lapsed.

Value by fiat. Leaders occasionally declare a programme valuable by force of conviction or seniority, without testing legitimacy or capacity at all. This costs the organization the discipline the strategic triangle exists to provide: discovering, before commitment rather than after failure, that a leg of the case was never actually checked.

Maturity model

Sub-dimension	Initiate	Develop	Standardize	Manage	Orchestrate
Public value proposition	No shared language for 'value'; each team justifies work its own way	A few teams can state a value proposition in one sentence, informally	A common template for stating value propositions is used organization-wide	Value propositions are reviewed and refreshed on a fixed cycle, tied to resourcing	Value propositions are co-developed with delivery partners and citizens, not written in isolation
Authorizing environment awareness	Leaders can name their budget approver but little else	Some leaders informally track key stakeholders	Every major programme has a documented authorizing-environment map	Shifts in the authorizing environment trigger a formal re-assessment	The organization actively cultivates and renews its authorizing environment across boundaries, not just monitors it
Operational capacity assessment	Capacity is assumed rather than checked	Capacity is checked informally, based on individual managers' judgement	A standard capacity assessment is required before a programme is approved	Capacity gaps are tracked and resourced through a formal remediation process	Capacity is planned jointly across delivery partners, including partners the organization does not control
Use of the three-legged test	The three tests are unknown or unused	Individual leaders apply the triangle informally to their own decisions	The triangle is a required part of business case templates	Triangle assessments are audited and feed into performance reporting	The triangle is used as shared language across government, funders, and delivery partners in joint decisions

Checklist

State your organization's public value proposition in one sentence.
List every member of your authorizing environment by name or role, not just your formal reporting line.
Separate 'is it authorized', 'is it worth doing', and 'can we deliver it' into three distinct answers for your top programmes.
Identify at least one place where a market metric or a mandate claim is standing in for a full public value case.
Check operational capacity claims against actual delivery history, not aspiration.
Document who benefits from each major programme and who pays for it, as two separate lists.
Confirm your team shares a common vocabulary for 'public value' across departments or delivery partners.
Identify one activity that persists on inertia rather than active authorization, proven value, or confirmed capacity.

Key sources

Mark H. Moore, Creating Public Value: Strategic Management in Government (Harvard University Press, 1995) — the foundational statement of the strategic triangle.
Mark H. Moore, Recognizing Public Value (Harvard University Press, 2013) — the measurement companion (see Topic 2.1 — The Public Value Scorecard and Outcomes Frameworks).
John Benington and Mark H. Moore (eds.), Public Value: Theory and Practice (Palgrave Macmillan, 2011) — extends the framework beyond Moore's original US setting.
Barry Bozeman, Public Values and Public Interest: Counterbalancing Economic Individualism (Georgetown University Press, 2007) — the 'publicness' argument referenced in this topic.
Gerry Stoker on public value management and Stephen Osborne on New Public Governance, both referenced in (see Topic 3.1 — Public Administration Systems and Models).

References

Public value — Wikipedia — https://en.wikipedia.org/wiki/Public_value
Mark H. Moore — Wikipedia — https://en.wikipedia.org/wiki/Mark_H._Moore
Barry Bozeman — Wikipedia — https://en.wikipedia.org/wiki/Barry_Bozeman
Public administration — Wikipedia — https://en.wikipedia.org/wiki/Public_administration
New Public Management — Wikipedia — https://en.wikipedia.org/wiki/New_Public_Management
Public good (economics) — Wikipedia — https://en.wikipedia.org/wiki/Public_good_(economics)
Nonprofit organization — Wikipedia — https://en.wikipedia.org/wiki/Nonprofit_organization
Civil society — Wikipedia — https://en.wikipedia.org/wiki/Civil_society
Legitimacy (political) — Wikipedia — https://en.wikipedia.org/wiki/Legitimacy_(political)
Accountability — Wikipedia — https://en.wikipedia.org/wiki/Accountability
Public Value in Public Service Transformation — OECD Observatory of Public Sector Innovation — https://oecd-opsi.org/wp-content/uploads/2022/03/public-value-public-service.pdf
Creating Public Value: The Core Idea of Strategic Management in Government — Mark H. Moore, Harvard Kennedy School — https://www.hks.harvard.edu/publications/creating-public-value-core-idea-strategic-management-government
Public Values and Public Interest: Counterbalancing Economic Individualism — Barry Bozeman, Georgetown University Press — https://press.georgetown.edu/Book/Public-Values-and-Public-Interest