Topic 1.2 — The Strategic Triangle: Legitimacy, Value, and Capacity

Why this matters in public value

Most public and social-sector leaders can name, this year, a decision that satisfied two legs of a triangle and quietly failed on the third. A popular manifesto commitment turns out to need engineering capability the organization does not have. A technically elegant reform never wins political sign-off to launch. A well-funded, well-staffed program delivers exactly what was promised, and nobody outside the building particularly wanted it. Each failure looks different from the inside, but they share a shape.

That shape is what Mark H. Moore, the Harvard Kennedy School scholar who coined the term, called the strategic triangle: legitimacy and support, the public value proposition, and operational capacity. Topic 1.1 — Introduction to Public Value introduced the triangle at a high level (see Topic 1.1 — Introduction to Public Value); this topic is its home — the full working model of each leg, and, more importantly, how leaders navigate the tension between them when, as is normal, the three do not point the same way at once.

The stakes are not academic. An organization that ignores its authorizing environment loses its mandate exactly when it is most needed. One that treats its value proposition as self-evident spends authority and capacity on something citizens turn out not to want. One that says yes to every authorized, valuable idea without checking its own capacity breaks its credibility on the gap between promise and delivery. Getting the triangle right, continuously, is not preparation for the real work of public management — it is the real work.

Core concepts

The strategic triangle is Moore's framework for testing whether a proposed course of action by a public or social-sector organization is a sound strategy: legitimate and supported, valuable, and deliverable, all at once. Moore set out the idea in Creating Public Value: Strategic Management in Government (1995), partly against the backdrop of New Public Management's tendency to judge public bodies mainly on efficiency and output, and partly as a public-sector analogue to corporate strategy, which tests a plan against only what the market wants and what the organization can do. Public and social-sector strategy needs a third dimension because these organizations draw on collective authority that has to be earned and re-earned, not purchased through a single transaction (see public value for how the concept has been taken up and contested since). Moore's own scorecard for tracking the three legs in practice, itself adapted from the private-sector balanced scorecard tradition, is covered in full elsewhere, not here (see Topic 2.1 — The Public Value Scorecard and Outcomes Frameworks).

Legitimacy and support, often called the authorizing environment, is the set of people and institutions whose consent — formal or informal — an organization needs in order to act, and whose withdrawal of consent can stop it acting. Formal authorizers include legislatures, elected councils, boards of trustees, courts, regulators, and funders with contractual power; many of these relationships are also principal–agent relationships, since an authorizer delegates authority to managers whose interests and information are never perfectly aligned with its own. Informal authorizers overlap with the organization's wider stakeholders — media, professional bodies, coalition partners, employees whose cooperation cannot be commanded, and citizens whose compliance a program depends on — and legitimacy is one channel through which accountability runs, though the two are distinct: an organization can be accountable on paper and still lack real support. Political legitimacy is the underlying concept: the right of an authority to be obeyed or supported, resting on law, democratic consent, tradition, or demonstrated competence, and never permanent once granted. An authorizing environment is rarely a single body; it is a shifting coalition, and reading it accurately matters more than satisfying whoever is loudest.

The public value proposition is the case that a given use of collective authority and resources is worth what it costs — not to one customer or interest group, but to citizens acting collectively through their political community. This differs from a market value proposition, the private-sector idea that a product is worth more to a buyer than its price: a market proposition is validated by a purchase, but a public one has no equivalent single transaction and must be inferred from votes, willingness to pay through taxation, expressed preferences, and observed behavior — none as clean a signal as a sale. Public value is also frequently plural rather than a single scalar quantity — liberty, equity, efficiency and security do not collapse onto one scale, a point this topic treats only as far as the triangle requires (see Topic 1.4 — Public Goods, Merit Goods, and Value Pluralism).

Operational capacity is what the organization can actually produce with the people, money, technology, legal authority, partnerships, and time it currently has or can credibly obtain. Capacity is not the same as ambition, and it is not fixed — it can be built deliberately (see capacity building, the established development-sector term this topic narrows to a single organization's delivery ability). Capacity has a legal dimension as well as a resource one: an organization may have the money and staff to do something and still lack the statutory authority, a constraint as real as an empty budget line.

How the three legs interact. The triangle is not a checklist to be ticked in sequence; it is a set of live constraints that each shift as the other two shift. Four patterns recur across sectors and jurisdictions:

Popular but infeasible — strong support and a clear value case, but the plan exceeds what the organization can deliver; the initiative stalls, is descoped, or fails visibly.
Deliverable but unauthorized — real capacity and a genuine value case, but consent has not been secured from those who must grant it, so the initiative is blocked or reversed once a missing authorizer objects.
Authorized and feasible but not actually valuable — permission and means both exist, and the organization proceeds, only to find citizens do not experience the result as worth what it cost, eroding legitimacy for the next initiative.
All three, but for different people — the hardest case: value is real for one group, the authorizers represent another, and capacity was built around a third, so no single account of "this works" is true for everyone with a stake.

Because authorizers change, capacity depreciates or is renewed, and a value proposition can be validated or invalidated by evidence, the triangle is never solved once. It is managed continuously — this topic is where the pieces meet; later topics each supply tools for one leg or one interaction.

Best practices

Map your authorizing environment explicitly, and keep the map current. List every formal and informal authorizer by name, what each can grant or withdraw, and when you last checked whether their position had changed — a stale map is worse than none, because it creates false confidence.
Write the value proposition down in one page before the business case, not after. State plainly who benefits, what they gain, and why it is worth the collective cost, before spending effort on implementation detail that a weak value case cannot justify.
Test operational capacity honestly before making a public commitment. Separate "we have approved budget" from "we have the staff, systems, and lead time to deliver", and treat a gap between the two as a decision point, not a risk to be managed away by optimism.
Treat the triangle as a design constraint from the start, not a scorecard applied afterwards. Bring legitimacy, value, and capacity questions into the room at the point a strategy is chosen, not the point it is being defended.
Use small, reversible moves to test and expand your authorizing environment before a large ask. A pilot, consultation, or limited-scope trial can reveal whether support exists at a fraction of the cost of discovering its absence after full commitment.
Ask three separate questions of every major decision: can we, may we, and is it worth it. Keep the answers distinct even when one person answers all three, because conflating them is how weak proposals survive scrutiny.
Renew legitimacy continuously, not only at elections or funding rounds. Treat the authorizing environment as needing regular, low-stakes contact, so a large ask is not the first time an authorizer has heard from you in a year.
Build capacity ahead of the mandate you expect to need, not only in response to the one you have. Capacity built reactively arrives late and expensively; capacity built in anticipation is cheaper and lets the organization say yes when the moment arrives.
Name the trade-off publicly when the three legs genuinely conflict. Stakeholders forgive a stated trade-off far more readily than one they discover was hidden behind an appearance of consensus.
Involve operational leaders in authorizing conversations, and governance leaders in capacity conversations. The most common triangle failures happen when the people negotiating legitimacy do not know what capacity allows, or delivery leaders are absent when promises are made.

Questions to discuss with your team

Who is actually in our authorizing environment right now, and has it shifted in a way our strategy has not caught up with? Authorizing environments change with elections, board turnover, new regulators, and shifts in public attention, often faster than internal strategy documents are updated. Use this question to list every formal and informal authorizer by name rather than by role, and check when each relationship was last actively managed. A stale list is a common cause of surprise opposition to initiatives the organization believed were already supported. Discuss which relationships have gone quiet, and whether that silence means comfort or disengagement.

Where in our current portfolio is the value proposition assumed rather than tested? Many organizations can state clearly what a program does but struggle to state, with evidence, who is genuinely better off and by how much. Use this question to separate programs with a tested value case — survey data, usage evidence, independent evaluation — from those running on institutional belief alone. Discuss what it would take to test the untested ones, and what you would do if the test came back negative; this is not an accusation that untested work is worthless, only a prompt to know which claims are load-bearing.

What would we do differently if we treated operational capacity as a hard constraint rather than an adjustable detail? Many strategy processes set ambition first and treat capacity as something to be found later through hiring or heroics. Use this question to identify which current commitments were made before anyone checked whether the organization could deliver them at the promised scale or date. Discuss whether the answer is to build capacity deliberately, renegotiate the commitment, or reduce scope, and who has the authority to decide.

Which current commitment is popular and well-supported but not, on an honest look, feasible as promised? This is the "popular but infeasible" pattern from this topic's core concepts, and most organizations are carrying at least one example without having named it as such. Use this question to surface it explicitly rather than letting it surface as a missed deadline later. Discuss whether the fix is more resource, a renegotiated conversation about scope or timeline, or an honest conversation about withdrawal.

Which current commitment is feasible and fully authorized but has not actually proven its value? This is the mirror failure: something the organization is fully entitled and equipped to do, that nonetheless has not demonstrated it is worth what it costs. Use this question to identify candidates and discuss what evidence would settle it either way. Consider, too, whether "proving value" means proving it to the people who use the service, the people who pay for it, or both, since those audiences are not always the same.

When the three legs conflict, who in this organization actually has the authority to decide, and do we agree on what they would say? Conflict between legitimacy, value, and capacity is normal, not a sign of failure, but an organization without a clear decision path either freezes or lets the conflict resolve by default, usually in favor of whichever leg has the loudest advocate. Use this question to name the decision-maker or forum explicitly, and discuss a recent example where the path was unclear and what would have made it clearer.

In practice: a public value example

The transit authority of a mid-sized coastal city — fictional, illustrative of a pattern rather than a report on any real body — had spent three years planning a dedicated bus rapid transit corridor along its busiest commuting route. The engineering case was strong: journey times would fall by close to a third, connecting two of the city's largest employment districts to neighborhoods with historically poor transport access. A national infrastructure grant already covered most of the capital cost, on condition that construction began within eighteen months.

Capacity looked sound: the authority had delivered smaller bus-priority schemes before, its engineering team had room in its schedule, and the timeline was tight but workable. The value proposition looked equally strong on paper — shorter commutes, lower emissions, and better access for residents without cars, disproportionately lower-income households. The project team treated the case as settled and moved straight to detailed design.

The authorizing environment told a different story. The corridor ran past shops whose owners depended on street parking the dedicated lane would remove, and were well organized and well known to councillors. Some residents argued the scheme served through-commuters more than locals, and that its benefits were overstated relative to construction disruption. The council had approved the underlying transport strategy two years earlier only in general terms, never this specific corridor design, and several councillors said so publicly once the plans became widely known — the "deliverable but unauthorized" pattern: the general strategy had been authorized, this particular design had not.

Rather than treating the skeptics as an obstacle to outlast, the project team returned to the council with a phased design: a shorter first segment avoiding the most contested stretch, published before-and-after evidence from earlier schemes to make the value case concrete rather than assumed, and a compensation package for the affected shops negotiated before construction, not after. The full corridor took two years longer than planned, but it survived: the council reauthorized it, opposition was withdrawn, and ridership data from the first segment became the evidence base for the rest. The value proposition had not changed; what changed was the authority's recognition that legitimacy for the general strategy was not legitimacy for this specific design, and that the two had to be secured separately.

Four sector lenses

Local government

A local authority's authorizing environment is unusually visible and local: councillors facing re-election on short cycles, residents who can attend a public meeting in person, and local media covering a single decision in more detail than a national outlet ever would. Legitimacy is easier to sense directly but harder to satisfy, since a small, vocal, concentrated group can outweigh a diffuse citywide majority in practice even when it would lose a formal vote. Capacity is often the tightest leg locally, since local bodies frequently lack the specialist skills or scale that national government or large contractors draw on, which is why partnership and shared-service arrangements recur so often.

National government

Nationally, the authorizing environment is layered: a legislature, an executive, opposition parties, international treaty obligations, and increasingly a public that expects consultation on major policy between elections, not only at the ballot box. This layering gives national bodies more potential legitimacy but also more points at which a single actor can withhold it. Capacity is often abstracted through long delivery chains — agencies, contractors, devolved bodies — so a leg that looks strong on paper, a large budget or clear legal authority, can conceal real gaps several layers down that only surface once delivery begins.

A nonprofit organization's authorizing environment includes its board, funders and donors, any regulator governing its charitable status, and the people it serves, who may have little formal power yet whose trust is a form of legitimacy it cannot operate without. The value proposition is complicated by the people who pay — donors and grant-makers — often not being the people who receive the service, a structural difference from both a market and a tax-funded transaction. Capacity is frequently volunteer-dependent and tied to grant cycles that do not match the multi-year timelines many social problems require, making "build capacity ahead of the mandate" harder to follow than for a body with a stable tax base.

Multilateral and international

Multilateral bodies answer to member states rather than a single electorate, making the authorizing environment a negotiation among sovereign interests rather than one line of democratic accountability; legitimacy is often contested on the grounds of representation itself — whose consent should count, and how much. Capacity is rarely owned directly; it is mediated through national governments and implementing partners, so real delivery capacity depends on relationships the body does not fully control. The value proposition must satisfy heterogeneous interests at once — donor states, recipient states, and affected populations often want different things from the same program, the plural-value problem at its sharpest (see Topic 1.4 — Public Goods, Merit Goods, and Value Pluralism).

Common failure modes

Triangle capture. One leg dominates every decision at the expense of the other two — most often legitimacy, when an organization focuses so hard on winning political or donor support that it commits to things its capacity cannot sustain. The cost surfaces later, as a launch that cannot be delivered on time, at quality, or at all, damaging the very legitimacy the capture was meant to protect.

Capacity theater. An organization presents itself as ready to deliver, to a funder, an authorizer, or the public, before honestly assessing whether its people, systems, and legal authority match the claim. The gap is not disclosed, so it costs trust sharply and all at once when it becomes visible, typically mid-delivery under public scrutiny.

Stealth mandate. A team delivers something operationally excellent and genuinely valuable by its own judgment, but never sought broad authorization for the specific form the work took, relying instead on the mission's general legitimacy. This is the pattern behind the worked example above; it costs a painful, avoidable renegotiation once a missing authorizer notices, and sometimes the initiative outright.

Value assumed, not tested. An organization treats its value proposition as self-evident because it feels obviously worthwhile from the inside, and skips testing it against citizens' actual preferences. This is the most quietly expensive failure mode, producing no crisis — only a slow accumulation of programs running on institutional belief.

Authorizing environment drift. The coalition that originally granted legitimacy changes — a new administration, a board turnover, a shift in public attention — without the organization re-securing consent from the new configuration. Legitimacy erodes silently until a crisis or an election exposes how little support actually remains.

Maturity model

Sub-dimension	Initiate	Develop	Standardize	Manage	Orchestrate
Authorizing environment is mapped and monitored	Known informally to leaders, not written down	A map exists for major initiatives but goes stale between reviews	A living, organization-wide map with a defined update cadence	Authorizer sentiment tracked; changes trigger a defined response	Coalition actively cultivated and renewed across boundaries, ahead of shifts
Value proposition is defined and tested	Asserted in mission language, rarely per initiative	Some initiatives have a written case, of variable rigor	Every major initiative requires a written, testable proposition before approval	Propositions tested against evidence and revised when contradicted	Testing is continuous, shared with citizens directly, and feeds strategy in real time
Operational capacity is honestly assessed	Assumed adequate unless a crisis proves otherwise	Checked for flagship initiatives only, usually after commitment	A mandatory, standardized gate before public commitment	Gaps trigger resourcing decisions or renegotiated scope automatically	Built ahead of anticipated mandates, coordinated with partners
Conflicts among the three legs are surfaced and resolved	Not named; resolved informally by whoever is most persistent	Noticed but resolution inconsistent across teams	A defined decision path and decision-maker exist	Resolved conflicts and their rationale recorded and reviewed	Recurring patterns treated as strategic signals that reshape structure

Checklist

List every formal and informal authorizer by name, with what each can grant or withdraw.
Date-stamp the authorizer map and set a recurring review.
Write the value proposition as a single page, naming who benefits and by how much.
Identify what evidence would confirm or falsify the value proposition, and gather it.
Separate "approved budget" from "confirmed capacity to deliver" for every major commitment.
Check whether legal authority, not just money and staff, covers the proposed action.
Ask can-we, may-we, and is-it-worth-it as three distinct questions before committing.
Name, in writing, any initiative that is popular but not truly feasible.
Name, in writing, any initiative that is feasible and authorized but unproven in value.
Identify who has authority to resolve a conflict between the three legs, and confirm they know it.
Plan one low-cost, reversible test before a large, hard-to-reverse commitment.
Revisit the triangle at each major milestone, not only at initiation.

Key sources

Mark H. Moore, Creating Public Value: Strategic Management in Government (1995) and Recognizing Public Value (2013) — the originating texts for the strategic triangle.
John Benington and Mark H. Moore (eds.), Public Value: Theory and Practice (2011) — extensions of the triangle across jurisdictions and sectors.
Gerry Stoker and Stephen Osborne's work on public value management and New Public Governance as successors to New Public Management.
Barry Bozeman's work on the "publicness" of organizations; John Alford's critical engagement with the strategic triangle.
Bryson, Crosby and Bloomberg's synthesis of public value governance as a successor paradigm.
World Bank and UK National Audit Office material on institutional capacity and value-for-money assessment.

References

Public value — Wikipedia — https://en.wikipedia.org/wiki/Public_value
Mark H. Moore — Wikipedia — https://en.wikipedia.org/wiki/Mark_H._Moore
Legitimacy (political) — Wikipedia — https://en.wikipedia.org/wiki/Legitimacy_(political)
New Public Management — Wikipedia — https://en.wikipedia.org/wiki/New_Public_Management
Balanced scorecard — Wikipedia — https://en.wikipedia.org/wiki/Balanced_scorecard
Value proposition — Wikipedia — https://en.wikipedia.org/wiki/Value_proposition
Principal–agent problem — Wikipedia — https://en.wikipedia.org/wiki/Principal%E2%80%93agent_problem
Accountability — Wikipedia — https://en.wikipedia.org/wiki/Accountability
Stakeholder (corporate) — Wikipedia — https://en.wikipedia.org/wiki/Stakeholder_(corporate)
Nonprofit organization — Wikipedia — https://en.wikipedia.org/wiki/Nonprofit_organization
Capacity building — Wikipedia — https://en.wikipedia.org/wiki/Capacity_building
Mark H. Moore, faculty profile — Harvard Kennedy School — https://www.hks.harvard.edu/faculty/mark-moore
John Bryson, Barbara Crosby and Laura Bloomberg, "Public Value Governance: Moving Beyond Traditional Public Administration and the New Public Management" — Public Administration Review / Wiley — https://doi.org/10.1111/puar.12238
Gerry Stoker, "Public Value Management: A New Narrative for Networked Governance?" — American Review of Public Administration / SAGE — https://doi.org/10.1177/0275074005282583
Stephen P. Osborne, "The New Public Governance?" — Public Management Review / Taylor & Francis — https://doi.org/10.1080/14719030600853022
Governance topic page — World Bank — https://www.worldbank.org/en/topic/governance
National Audit Office — UK National Audit Office — https://www.nao.org.uk/