How Mission Economy Actually Works in Practice
I spent about six months trying to apply the framework from Mission Economy A Moonshot Guide To Changing Capitalism to a public-sector infrastructure project, and I still consider that a rough education. The short version is that Mazzucato's central argument is straightforward: governments shouldn't just step in when markets fail. They should be the ones setting ambitious targets — climate stability, green energy transitions, pandemic preparedness — and then designing the institutional architecture to get there. The Apollo program is her reference point because it was a mission, not a subsidy. The problem is that most people who read the book come away thinking this is about spending more money on big government projects. It isn't. It's about a different way of structuring incentives between the public and private sectors. When you actually implement it, the hard part isn't picking the mission. It's getting the contracting, procurement, and evaluation systems to align without defaulting to the lowest-bidder model that's been burning taxpayers since the 1980s.
Getting From Theory to Implementation With Mission Economy A Moonshot Guide To Changing Capitalism
I'll walk through what actually happens when you try to operationalize this, because the book doesn't cover the messy institutional details. First, you define the mission in measurable terms. "Net zero by 2050" works because you can measure it. "Better healthcare" does not. Be ruthless about specificity here or the whole framework collapses into vague spending priorities. Then you build a team that has the authority to cross departmental boundaries. This sounds simple but it is the part where most implementations die. In my experience, the civil service structure is explicitly designed to prevent exactly this kind of cross-cutting work. I found myself fighting a two-month battle just to get procurement, energy, and environment departments to share a reporting line for a clean technology deployment initiative. The workaround was to create a temporary cross-departmental delivery unit with a direct line to the cabinet or governor's office, funded through a pooled budget that couldn't be redirected back to individual departments. It worked, but only because someone with enough political weight backed it. After that comes the procurement piece. Traditional procurement awards contracts based on price. Mission-based procurement awards contracts based on whether the mission gets accomplished. That means you structure deals where the government takes some of the upside risk. If a company develops a breakthrough in battery storage and the mission target is hit, they get a premium. If they miss, they don't get the full payment. This sounds fair until you realize that most mid-tier contractors won't touch it. They can absorb cost overruns. They can't absorb the possibility of going unpaid after investing real capital. You end up working mostly with larger firms or specialized startups that have the balance sheet flexibility, which limits your competitive pool significantly.
What the Book Leaves Out About Risk Allocation
Here's something Mazzucato doesn't stress enough: the state taking risk doesn't mean the state takes all the risk. The whole point is that government de-risks the early stages of innovation — the phase where private capital refuses to go because the technology isn't proven yet — and then exits gracefully once the market can handle it. But exiting is harder than it sounds. I watched a clean energy deployment program get permanently stuck in government hands because no private firm had the capacity to scale the technology fast enough to justify a handoff. The mission became a permanent state enterprise instead of a launched rocket. That's not what the framework envisions and it's not sustainable. The counter-intuitive part that nobody talks about is that mission-oriented policy actually requires more market discipline, not less. You're directing markets toward a goal, which means you need price signals, competitive tension, and performance metrics all operating correctly. If you replace those with bureaucratic allocation, you haven't created a mission economy. You've created a Soviet-style planning apparatus, which is exactly the thing Mazzucato is arguing against. The difference is subtle in theory and devastating in practice.
The Monitoring Problem Nobody Wants to Admit
You can't manage what you don't measure, and measuring mission success is genuinely difficult. The Apollo program had a clear metric: put a man on the moon and bring him back. Climate change mitigation, the kind of mission Mazzucato advocates for, has compound indicators that shift depending on which models you trust and which baseline year you pick. I've sat in meetings where a program was declared a success because it hit its emissions target while simultaneously causing a spike in energy poverty that the metrics didn't capture. The workaround I used was to build a dashboard with leading indicators, not lagging ones. Emissions data comes out a year late. Grid investment commitments, patent filings in the relevant technology space, and private capital deployment figures come out quarterly. When I pushed for those as the primary tracking metrics, we could course-correct in real time instead of discovering failure after the fact. It's not perfect. Patent data is noisy. Private capital commitments include money that may never materialize. But it's better than waiting for the annual emissions report to tell you whether you're on track.
When This Approach Fails Completely
I need to be honest about where this framework breaks down. It doesn't work in weak institutional environments where corruption is endemic. The mission economy model assumes a state that can credibly commit to long-term contracts, enforce performance clauses, and resist capture by the firms it's supposed to be directing. In countries where procurement is systematically rigged or where political cycles are so short that no one plans beyond two years, you're not going to pull off mission-oriented policy. You'll just create new opportunities for rent-seeking dressed up in green rhetoric. It also doesn't work well for problems that are diffuse rather than concentrated. Climate change is mission-able because the causes and effects, while global, map onto specific sectors — energy, transportation, agriculture. A problem like inequality doesn't map as cleanly. There's no single technology to deploy or infrastructure to build. You could argue that educational reform or healthcare access fits the model, but the causal chains are too long and too tangled for the mission framework to generate clear deliverables. You'll get bureaucratic activity without measurable progress.
A Practical Starting Point If You Want to Try This
If you're actually considering implementing anything inspired by Mazzucato's work, start small. Pick a mission that's geographically contained, technically defined, and has a clear deadline. A city-level net-zero building retrofit program is a much better test case than a national industrial strategy. You'll learn more from a contained failure than from a half-executed grand vision. The institutional learning that matters — how to structure cross-departmental teams, how to design performance-based contracts, how to build real-time monitoring — compounds faster when the stakes are manageable. I've seen too many organizations skip straight to the grand mission and then spend years arguing about scope and governance instead of delivering anything. The Apollo program succeeded because it had a clear target, unlimited funding backing, and a dedicated organizational structure that answered to someone with final authority. Most modern policy initiatives have none of those three things. You don't need all of them, but you need at least two or the framework will consume resources without producing results. That's the practical takeaway that the book hints at but doesn't drive home hard enough.
