It’s a Real Book Now

For the past several months, you’ve been reading Economics for Busy People one chapter at a time. Some of you started at my story about a razor clam. Some of you jumped in somewhere around opportunity costs. A few of you have probably been reading out of order, which — given that the book is about how people make decisions with limited time — feels appropriate.

As of this past week, Economics for Busy People is officially published and available on Amazon as both an ebook and a paperback.

The ebook launched first. Within 24 hours it hit #1 New Release across every sub-category it’s listed in and reached the Top 10 in parent categories. The print edition went live last week and is hovering around the Top 25 in Best Seller and Top 5 in New Releases.

I’m so excited to share this with you all, my early readers, as well as the rest of the world.

This book exists because I believe economics is the most useful and least utilized subject available to you. Not simply the economics of GDP forecasts and Fed press conferences. The economics of how you actually make decisions, why trade-offs are unavoidable, and how millions of strangers cooperate every day without anyone directing them to.

You’ve read the chapters. You’ve seen the ideas in action. If they’ve changed how you see even one decision — at the grocery store, at work, at the ballot box — then the book did its job.

What I’d ask of you.

If this book has been useful to you, two things would help enormously.

First, leave a review on Amazon. Honest. Short is fine. Reviews in the first few weeks matter more than most people realize. They’re how the book reaches people who haven’t found it yet. But, if you do want to leave a review then Amazon tends to only count reviews of verified purchases or downloads (the ebook is free for Kindle Unlimited, $5 otherwise, and $16.99 for the paperback).

Second, send it to someone. You probably know a person — a friend, a coworker, a family member — who cares about making good decisions but thinks economics isn’t for them. This book was written for them.

The print and ebook is available here.

What’s next.

The full Economics for Busy People video series is coming soon — every chapter as a short, watchable episode. The audiobook is right behind it (because I know busiest people like to listen rather than read). And this Substack is about to shift from publishing the book (theres 4 more chapters to close it all out) to putting it to work. Applied questions. Real situations. The economic way of thinking, aimed at things you actually deal with.

Thank you for reading. Seriously.

Let’s get busy.

— Cameron

International trade works the same way as any other voluntary exchange. Both sides benefit, even when one country is “better” at producing everything.

Why Trade Scares People

When a factory closes and jobs move overseas, it’s natural to blame foreign competition.

When imports flood the market, it feels like other countries are “taking advantage” of us.

When politicians promise to “bring jobs back,” it sounds like they’re fighting for workers.

But this view misses something important. Trade isn’t war. It’s cooperation. Just like trade between individuals, international trade makes everyone involved better off.

The Same Logic, Bigger Scale

Everything that is beneficial about exchange between people applies to countries, too.

When you trade with your neighbor, you both benefit because you each give up something you value less to get something you value more. The same thing happens when Americans buy coffee from Colombia or when Germans buy software from Silicon Valley.

Countries don’t trade, people do.

Productiveland and Struggleton

Here’s where it gets interesting. Even if one country is better at producing everything, trade still benefits both countries.

Imagine two countries, Productiveland and Struggleton. Productiveland can make all items more efficiently than Struggleton. You might think, “Why would Productiveland ever trade with Struggleton?”

The answer lies in opportunity cost. Even though Productiveland is better at making all products, it has to choose how to use its limited resources. If Productiveland focuses on mostly computers (where its advantage is biggest) and Struggleton focuses on clothing (where its disadvantage is smallest), both countries can end up with more of both products.

Struggleton may never buy as much from Productiveland as Productiveland buys from Struggleton. But, that’s because Struggleton doesn’t need as many computers as Productiveland needs clothes. At least not yet.

The goal is not to have an equal balance of trade. The goal is to have the cheapest trade possible to allow for the most exchange possible. That way both parties benefit the most.

Why Jobs Arguments Miss the Point

Critics of trade tend to focus on the jobs lost in some industries. These losses are real and painful. But they miss the other side of the equation:

• Consumers benefit from lower prices and better products. A family that saves $2,000 a year on clothing and electronics has $2,000 more to spend on other things. This creates demand and jobs elsewhere.

• Export industries grow. When other countries buy our products, that creates jobs here. That extra demand leads to growth.

• Resources shift to better uses. We free up workers and capital for industries where we have an advantage when we stop making products that others can make more efficiently.

The job losses are visible and concentrated. The job gains are spread out and harder to see. But both are real.

What About “Unfair” Competition?

Sometimes people argue that trade is only fair if wages and working conditions are similar across countries. But this misses why trade happens in the first place.

Countries trade because they’re different. They have different resources, different skills, and different costs. A country with lower wages usually has lower productivity, too. When they specialize in labor-heavy products, it gives them the ability to build skills and capital that raise wages over time.

Blocking this process doesn’t help foreign workers. It traps them in poverty. And it doesn’t help domestic workers either. It forces them to pay higher prices for goods they could get more cheaply through trade.

The Real Costs of Protection

When governments try to “protect” domestic industries with tariffs or quotas, they create several problems:

• Consumers pay more. Tariffs are taxes on imports, and those taxes get passed on as higher prices.

• Efficiency falls. Protected industries have less incentive to innovate and improve.

• Retaliation happens. Other countries respond with their own trade barriers, hurting our exporters.

The result? We get less stuff, at higher prices, produced less efficiently. That “protection” leads to everyone paying more so that one group doesn’t have to adapt.

This pattern reveals something important about how politics shapes economics. Political incentives and promises can often override economic logic.

What This Means for Policy

Good trade policy focuses on reducing barriers, not raising them. This means:

• Lower tariffs that let consumers choose based on value, not artificial price differences.

• Fewer regulations that make it harder for our exporters to compete globally.

• Better systems that make it easy for workers to adapt when industries change, rather than trying to freeze industries in place.

The Bottom Line

International trade doesn’t destroy jobs, it changes them. Some industries shrink while others grow. Some workers need to retrain while others see new opportunities. Reducing barriers for workers to change industries is key. That transition can be difficult, but blocking trade doesn’t stop the need for change. It just makes everyone poorer in the process.

Regulations that try to protect consumers from harm can end up protecting producers from competition.

Rules Can Go Rogue

When people propose new laws or regulations for businesses to follow, the story always sounds the same. “We must protect the public, ensure fairness, and prevent abuse.”

It’s easy to support. Who doesn’t want protection, fairness, or freedom from abuse? Clean air, safe food, and honest businesses are without a doubt good things.

But here’s the harder truth: regulation doesn’t stay where it starts. What begins as an attempt to protect consumers can evolve into protecting producers. It can shield businesses from competition instead of shielding consumers from harm.

Regulation Usually Starts With Genuine Concern

Most regulations begin with genuine concern. A product harms customers. A scandal sparks outrage. A problem feels like it needs a solution, and a rule seems like the obvious answer.

So lawmakers form a new agency. Administrators write new standards. Bureaucrats put new approvals, inspections, and permits in place.

But the moment a rule is created, a new incentive emerges: Who gets to influence how it works now that it exists?

How Producers Take Control

Producers, trade groups, and industry associations, have a lot at stake in how regulation is written and enforced. Unlike individual consumers, they have the resources, time, and coordination to pay attention. They hire lobbyists, and they show up to every meeting.

This constant presence can cause rules to shift:

• A licensing law meant to ensure quality starts requiring expensive programs that only large companies can afford.

• Safety regulations begin mandating equipment that happens to be produced by a small number of approved vendors.

• Processes become so complex that only firms with full-time legal teams can make sense of them.

Regulations that were meant to protect the public start protecting the powerful instead.

When regulation makes it harder for new businesses to enter a market, it’s not protecting consumers. It’s protecting existing businesses.

Examples You May Recognize

Taxi medallions: Local governments created these to manage traffic and ensure safety. They are a barrier to entry and limit who can compete. They lead to less supply and higher prices as a result.

Occupational licensing: Governments can require licenses for certain jobs not because of risk to the public, but because established professionals want to limit competition.

Food safety rules: Sometimes written so narrowly that small farmers or producers can’t comply, even if their practices are safer and more transparent than industrial alternatives.

Consumers don’t always benefit from these rules as much as producers do.

Regulation as a Competitive Strategy

Here’s what’s really going on: established businesses can use regulation as a weapon against their rivals.

A large firm might support stricter environmental rules because it already has the resources to comply. The business may know their smaller competitors don’t have the funds to make the changes fast enough.

An industry association might lobby for mandatory certifications, knowing it can train its members to pass them while leaving outsiders behind.

Even well-meaning laws can be subtly rewritten over time to entrench those already at the top. Economists call this behavior regulatory capture.

Why It’s Hard to Reverse

Once a regulation shifts toward producer protection, it’s hard to reverse.

• The rules are already in place.

• Those benefiting are organized.

• The costs are spread across millions of people who rarely notice.

Consumers rarely lobby to repeal a license requirement. But producers have the money and people to fight hard to keep it. Especially if it locks in their advantage.

This is why regulation tends to expand, even if it doesn’t work that well. The people who benefit most are the ones best positioned to defend it.

What Can Work Better

Regulation doesn’t always have to come from the government. Markets provide ways to regulate businesses as a result of different groups working together pursuing their own goals.

Insurance companies assess risk and adjust pricing. They can create strong incentives for businesses to maintain safe practices to keep premiums low.

Independent quality assurance groups set standards and certifications that consumers trust. Companies compete to earn these certifications because consumers value them.

Industry self-regulation often sets higher standards than the government. Professional groups understand their industries better and are incentivized to maintain credibility.

These market based accountability mechanisms can fail too. None of them are perfect. But, the question is which system fails less catastrophically and corrects faster. The market has an incentive to adapt. When businesses know they’ll pay for harm they cause, they have a powerful incentive to maintain safety and quality. This can disappear when there’s a possibility for the laws to change in their favor.

The Bottom Line

Even when regulation starts with good intentions, it can be used as a weapon against competitors by those with the most to gain. Consumers rarely win from this. But competitors, lobbyists, and insiders often do. To truly protect the public, regulations should rely on rules that hold businesses accountable for harm, and less on complex regulations that just protect incumbents.

Why Bother?

This series has spent a lot of time on what can go wrong inside organizations. Coordination becomes expensive as you grow. The knowledge your leaders need doesn’t reach them. Measurement systems destroy your most valuable work. The rules of the organization make cooperation irrational. The capabilities that made you successful fight against the innovation you need next. I’ve come to call these people problems. These are the costs and failures that arise whenever people try to coordinate work toward a shared goal.

After all of that, a reasonable person might ask: why bother? Working together sounds exhausting. If working together inside a company creates this many problems, why not just work apart? Why not hire contractors for everything through the market, where prices coordinate millions of strangers without anyone needing to be in charge?

It’s not a hypothetical question. It’s a question economists have taken seriously. Ronald Coase won the Nobel Prize in part for answering it. His answer was that firms exist when internal coordination costs less than the transaction costs of using markets. Sometimes it’s cheaper to bring people inside an organization than to buy their work on the open market. That’s true, and it explains why firms emerge in the first place.

But it doesn’t explain what firms actually do that makes them worth continuing. It doesn’t explain:

• Why firms can get better at what they do over time.

• Why they sometimes endure even when market alternatives get cheaper.

• Why organizational knowledge matters so much that companies talk about “institutional knowledge” as one of their most valuable assets.

• Why new employees take months to become effective, and what they’re learning during that time.

• Why the most valuable work inside a firm is often the work that most resists being moved outside it.

Coase answered why firms emerge. The more useful question, especially for anyone actually running one, is what firms do that nothing else can? What makes the costs of coordination worth bearing? What are you building by keeping people together year after year focused on your products and customers?

The answer is about knowledge. But not the kind most people mean when they use that word.

Why Some Problems Resist Standardization

Throughout this series we’ve seen the same pattern from different angles. Organizations build systems that work well for some kinds of work and systematically threaten, or destroy, others. These systems include metrics, processes, incentive structures, and evaluation frameworks. In many cases, the traditional roles of managers. These systems aren’t broken. They’re just designed for a very specific kind of problem and fail when used to address a second kind of problem.

Some problems are complicated. They have many steps and many parts, but the relationships between them are knowable and the outcomes are predictable. These problems can be addressed through analysis, measurement, and optimization. They respond well to the systems most organizations build as they scale.

Other problems are complex. They’re organic, dynamic, and relational. The parts interact in ways that change depending on context. Outcomes come from the interactions rather than being calculated in advance. These problems can’t be addressed through standardization. Not because they’re harder. Because they’re a fundamentally different kind of thing.

I’ve come to call the mismatch “robot thinking.” Not as a criticism. As a description. Robot thinking treats every problem as if it were complicated. Standardize it. Measure it. Optimize it.

For genuinely complicated work, this is excellent. For complex work, it creates the very people problems this series has been diagnosing.

But what exactly makes complex problems resist standardization at a basic level? The answer is about the kind of knowledge each type of problem involves.

Two Kinds of Knowledge

Most discussions of knowledge in business treat it as a thing that exists somewhere and can, in principle, be moved around. You learn something. You write it down. Someone else reads it and learns it too. Knowledge is information and information is transferable. The question becomes how efficiently the transfer happens.

The economist Richard Langlois (Scope, Scale, and the Reuse of Knowledge) pointed out that this picture is partially right, but it misses something important. Some knowledge isn’t a separable artifact at all. It’s generated in the process of producing other things. It is embedded in that production, and because of this, exists nowhere else.

This is the difference between knowledge that can be templated and knowledge that can only be embedded in the doing. You can capture templated knowledge can in a procedure, a standard, a piece of code, a manual, or a model.

Template knowledge is what makes scale possible. Once you’ve figured out how to make a good widget, you can write down the steps, build a jig, train someone to follow the procedure, and reproduce the result. The cost of creating the template gets spread across every unit you produce afterward. This is why standardization works. This is why some kinds of expertise can be packaged into software, sold as consulting frameworks, or contracted out to specialists. Template knowledge is, by its nature, separable from any particular producer. It can be moved.

Embedded knowledge can’t. It develops through repeated experience in a specific context. It accumulates across people who work together over time addressing genuine customer demands. It comes together across functions through sustained collaboration. And it persists in routines, judgments, and relationships that nobody can fully document. You can’t separate it from the people and the work that produced it because it doesn’t really exist apart from them. Even when you try to write it down, what you capture is the surface, the visible procedure. You do not capture the contextual judgment that knew when to follow the procedure and when to deviate from it.

This is what makes complicated problems complicated and complex problems complex.

Complicated problems are problems where template knowledge can do most of the work. Robot thinking works for them because the knowledge they require is templatable.

Complex problems are problems where embedded knowledge is appropriate. Robot thinking fails because the knowledge they require can’t be templated.

The complicated/complex distinction tells you the domains are different. The template/embedded distinction tells you why.

And it tells you what your firm actually does that nothing else can.

What This Looks Like in Practice

Let’s say you have a startup and two employees are working together. One has been around for five years and the other is one year in. The newer employee has an idea for a new product. He runs it by the senior employee. It just so happens that the senior employee had that same idea three years ago. She’s sympathetic to it, but she remembers why it didn’t get built in the first place.

Maybe there were product limitations that made it impractical. Maybe a senior executive killed a similar proposal. Maybe they ran a pilot and it was expensive and inconclusive. The thing is, without the institutional knowledge, the new employee is stuck at square one. With it, he either knows quickly this is a dead end, or he becomes aware of specific nuances that need to be thought through before trying again. Either way, the knowledge share saves time, money, and effort by avoiding redundant work.

Now here’s the part that matters for this article. Some of what the senior employee knows can be documented — the fact that the idea was tried, that it failed, what the outcome was. That’s the templatable surface of institutional knowledge, and good documentation practices preserve it. A future employee could find the post-mortem and learn the basic history.

But the most valuable part of what the senior employee knows can’t be documented. It’s the judgment about why it failed in this specific context. Whether a different version might work now that the product has changed. How this idea connects to three other things she’s learned since then. What the new employee’s version would need to address that the original didn’t. That knowledge is embedded in her accumulated experience. It’s what made the hallway conversation more valuable than reading a deck. And it only exists so long as she works for the firm.

If she leaves, the post-mortem stays. The judgment leaves. The firm retains the template. It loses the embedded knowledge that made the template useful.

This is what a firm does that a collection of market relationships can’t quite replicate. The newer employee didn’t hire the senior employee as a consultant. He didn’t contract for her institutional memory. He accessed it because they both work inside the same organization. Because the firm created the conditions where that knowledge could be passed on through a conversation that neither of them planned. The firm does this by keeping people together long enough for knowledge to accumulate and transfer in ways that nobody can fully design or predict.

What matters isn’t whether people are technically employees or contractors. What matters is whether the conditions exist for embedded knowledge to accumulate and transfer. These conditions include:

• Sustained relationships

• Shared context

• Continuity of work and

• A kind of proximity that lets someone access knowledge they didn’t generate through a conversation they didn’t plan.

A firm, in the sense that matters here, is any arrangement that creates those conditions (See Klein What is a Firm, Anyway? for a brief discussion).

The Asset You Don’t Own

Think about what your firm actually controls. It owns its equipment. It owns its real estate, or at least holds the lease. It owns its intellectual property, its codebase, its documented processes, its brand. These assets stay when people leave. They can be inventoried, valued, transferred, and protected. If someone walks out the door tomorrow, the building is still there. The code is still there. The patents are still there.

Now think about the embedded knowledge we just described. The senior employee’s judgment about why that product idea failed and what a new version would need. The engineer’s intuition about which architectural decisions will hold up under scaling. The account manager’s feel for when a client relationship is at risk before any metric shows it. The operations lead who knows which processes can absorb a disruption and which ones will cascade.

Your firm doesn’t own any of that. Not the way it owns a server or a trademark. It accesses it through people. And its access is contingent on something it can’t fully control: that those people continue to show up.

This makes embedded knowledge unlike every other resource a firm manages. Every other asset responds to conventional management logic. Acquire it. Protect it. Optimize its use. Measure its return. Embedded knowledge doesn’t respond to any of these in the way you’d expect.

You can’t get embedded knowledge the way you get equipment. You can’t buy it on the market. You can’t hire someone and have them bring it with them from a previous employer. These employees will bring their own embedded knowledge from a different context, which is valuable but not the same thing.

Embedded knowledge specific to your firm can only be generated inside your firm. It’s gained through sustained experience in your specific context. The only way to “get” it is to create the conditions where it develops over time.

You can’t protect embedded knowledge the way you protect intellectual property. You can’t patent a senior employee’s contextual judgment. You can’t copyright the cross-functional teamwork that lives in the relationships between your teams. Non-compete agreements don’t preserve knowledge. They just prevent the person who carries it from using it somewhere else for a while (maybe). The only way to protect embedded knowledge is to maintain the relationships and conditions that keep it accessible and transferring to others. If it lives in one person and that person leaves, no legal mechanism can recover it.

You can’t optimize the deployment of embedded knowledge the way you optimize a supply chain. You can’t route it efficiently to where it’s needed. You often don’t know where it’s needed until the moment arrives (like the hallway conversation between the senior and junior employee that neither of them planned). The only way to “optimize” embedded knowledge is to create enough proximity and continuity that these unplanned transfers happen naturally and frequently.

And you can’t measure embedded knowledge the way you measure other assets. Its value is often invisible until the moment it prevents a costly mistake, unlocks a cross-functional insight, or enables a judgment call that no template could have produced. You only notice its absence after it’s gone. When the person who carried it has left and the new hire makes the same mistake the organization already paid to learn from three years ago.

This is the paradox at the heart of managing a firm. The asset that makes your organization most valuable is the asset you have the least control over. And the management approaches designed for the assets you do control (standardize, measure, optimize) are precisely the approaches that can destroy the asset you don’t.

Robot thinking works for owned assets. Standardize the process. Measure the output. Optimize the deployment. These assets respond to control because they’re fully within the firm’s possession.

Embedded knowledge doesn’t respond to control. It responds to conditions. It accumulates when people work together long enough in a shared context. It transfers when there’s enough proximity and trust for unplanned conversations to happen. It compounds when the organizational environment treats it as valuable even when it can’t be measured. And it disappears, sometimes overnight, when any of those conditions break down.

Every system your firm builds is a choice about which kind of asset to focus on.

• Metrics that reward only measurable output focus on owned assets and neglect embedded knowledge.

• Incentive structures that punish cross-functional collaboration focus on efficient use of controllable resources and destroy the conditions for knowledge transfer.

• High turnover in the name of cost optimization treats people as interchangeable inputs and resets the embedded knowledge that was the actual competitive advantage.

What Makes It Worth Continuing

The costs of coordination that this series has diagnosed aren’t just friction to be minimized. They’re the price of maintaining the conditions under which embedded knowledge compounds. Some of those costs are genuinely wasteful and should be reduced — that’s what good institutional design does. But some of them are the cost of keeping people together long enough, in close enough proximity, with enough shared context, for the kind of knowledge to develop that no market relationship and no AI tool can replicate.

The question isn’t how to eliminate coordination costs. It’s how to make sure what you’re getting in return — in embedded knowledge, in cross-functional judgment, in accumulated contextual understanding — is worth more than what you’re paying. That’s the trade-off at the center of every firm. And managing that trade-off is what management is actually for.

But managing it well requires seeing a distinction that most organizations miss.

Efficiency vs. Effectiveness

Efficiency means doing work cheaper, faster, with fewer resources. Effectiveness means doing work in a way that produces the right outcome in a specific context. These are not the same thing, and optimizing for one can destroy the other.

Robot thinking optimizes for efficiency. Standardize the process. Reduce the cost per unit. Measure output per hour. For templatable work, efficiency and effectiveness align. The standardized process is the most effective process because the right answer is known and the job is to execute it at the lowest cost. But for embedded work, the two come apart. The cheapest way to do the work is not always the most effective way. Effectiveness depends on contextual judgment that doesn’t show up on a cost-per-hour comparison.

Outsourcing a function, either to a contractor or now even to an AI agent, might be more efficient on paper. Lower hourly rate. No overhead. But if the work has an embedded component, the outsourced version is less effective. It gets done without the contextual judgment that would have made it actually useful. And then you spend more fixing, redoing, or compensating for the gap than you saved on the hourly rate. You maximized efficiency and destroyed effectiveness, and ended up with neither.

This is what every coordination failure in this series has been about.

• Metrics that optimize for measurable efficiency while destroying unmeasurable effectiveness.

• Incentive structures that reward efficient compliance while punishing effective cooperation.

• Reporting structures that surface cost data while stripping out the context that makes the data meaningful.

The cost of working together inside a firm is real. But the return on that cost isn’t efficiency. It’s effectiveness found in the accumulated ability to do the right thing in context, not just the cheap thing on paper.

What This Means for AI

AI is, at it’s core, a templating technology. It lowers the cost of creating templates. It turns previously embedded craft into code, models, and standardized workflows. It excels at complicated problems.

Some economists have predicted that AI will shrink firms by lowering transaction costs. That may well be true for work where template knowledge dominates. Work that was traditionally held inside firms because of the cost of bundling complementary template-based capabilities will, in many cases, move out.

But that only describes part of what firms do. As AI expands what can be templated, the question for any leader becomes: which of the work I’m keeping inside my firm is genuinely embedded, and which am I keeping inside out of habit? The work that AI can template isn’t your competitive advantage. The work it can’t is.

Getting this wrong creates problems in both directions.

Keep templatable work inside when it could be moved out and you waste resources. Your best people spend their time on work a tool could handle, while the complex cross-functional work that only they can do goes unattended.

Push embedded work out, or treat it like template work internally, and you get the failures this series has been diagnosing. You standardize work that depends on contextual judgment and the judgment disappears. You measure it on the wrong metrics and the measurement destroys what made it valuable. You centralize decisions that depend on local knowledge and the knowledge gets stripped out.

AI makes this second mistake harder to see. AI’s success at complicated work creates pressure to template everything. If AI can write the report, surely it can handle the client relationship. If AI can analyze the data, surely it can make the strategic judgment. If AI can standardize the process, surely the process should be standardized.

The question isn’t “will my company survive AI.” It’s “do I know which work in my company is genuinely embedded, and am I building around that distinction or ignoring it?”

What This Means for Managers Like You

This article has been about what firms do that nothing else can. But firms don’t do anything on their own. People do. And the question of what firms do eventually becomes a question about what the people running them should be doing.

If your organization has two kinds of work, it has two kinds of management challenges. And they require fundamentally different things from you.

For the templatable work, your job is relatively clear. Build good systems. Set clear metrics. Standardize processes. Optimize for efficiency. This is important work and the series has never said otherwise. Robot thinking is excellent here.

For the embedded work — the complex, cross-functional, judgment-dependent work that this series has been about — your job is something else entirely. It’s stewarding the asset your firm doesn’t own.

That means making structure decisions based on what kind of knowledge you need to accumulate, not just what looks clean on an org chart.

It means treating hiring in embedded roles as a knowledge investment that compounds over years, not a cost to be minimized per hour.

It means understanding that turnover in these roles doesn’t just create replacement costs. It resets the compounding that was your actual competitive advantage.

It means recognizing that documentation preserves the templatable surface of your institutions knowledge, but not the embedded depth. Pretending otherwise creates a dangerous illusion.

Most fundamentally, it means creating and protecting the conditions under which embedded knowledge accumulates, transfers, and compounds. Designing rules where cooperation is rational. Connecting knowledge between people who have it and people who need it. Protecting valuable work from measurement systems that would destroy it. Recognizing which work is genuinely embedded and making sure your systems treat it accordingly.

This is harmonizer thinking. And it’s not a nice-to-have. It’s the economic justification for your role as a manager.

The manager who only does robot thinking and only standardizes, measures, and optimizes is managing the part of the organization that could increasingly be managed by software or by well-designed processes that don’t need much human judgment. That work matters, but it’s not what makes the firm worth continuing.

The manager who also does harmonizer thinking — who stewards the asset the firm doesn’t own, who creates the conditions for embedded knowledge to compound, who protects complex work from systems designed for complicated work — is doing the work that justifies the costs of coordination. They’re the reason the firm produces something that a collection of independent contractors with AI tools cannot.

Every article in this series has been building toward this point. The coordination failures aren’t bugs in the system. They’re the cost of doing something that only firms can do. Your job isn’t to eliminate those costs. It’s to make sure what your firm produces is worth more than what those costs consume.

The Bottom Line

Working together is costly. This series has shown exactly how and why.

But firms do something that working apart cannot. Working together creates the conditions for knowledge that only exists in the doing. Knowledge accumulated across people working together over time, brought together across functions through repeated collaboration. This is the asset you don’t own but can’t succeed without.

Your products can be copied. Your processes can be studied. Your templatable work can, and increasingly will, be moved to the market and to an AI system. But the embedded knowledge building up in your organization — the pattern recognition, the cross-functional judgment, the contextual understanding built through years of shared experience — is the advantage that persists.

Complicated problems have complicated solutions. Complex problems need something different. Robot thinking handles the first. Your firm exists for the second. And your most important job is making sure it does.

When interest rates are kept lower than they should be, it sends false signals to entrepreneurs and leads to unsustainable booms followed by painful busts.

The Developer’s Dilemma

Back in 2005, a real estate developers in Las Vegas looked at the numbers and saw opportunity everywhere. Interest rates were low. Credit was easy to get. Housing prices had climbed every year for a decade. Dozens of developers borrowed millions to build new subdivisions on the edge of the town.

By 2007, the homes were built. But the buyers never showed up. Not because the homes were bad. Not because Vegas stopped growing. But because the borrowing and credit that made all of it possible was built on signals that weren’t real.

Interest rates weren’t low because Americans were saving more and banks had extra capital to lend. They were low because the Federal Reserve had pushed them there, in addition to ratings policy changes and a decrease in foreign investment.

When rates adjusted, the easy credit disappeared. Buyers couldn’t get loans. Developers couldn’t sell homes. Entire neighborhoods sat empty. The developer didn’t make a reckless bet. He made a reasonable bet based on information that turned out to be false.

Now multiply that story by thousands of developers, in dozens of cities, across several industries and you start to see how an economy can boom and bust all at once.

Why Busts Hit Everything at the Same Time

We’ve been taught to think of recessions as a basic part of the economy. “What goes up must come down.” But that’s worth questioning. In a normal market, some industries grow while others shrink. That’s expected. Consumers’ wants change, technologies evolve, and seasons shift. But a bust that hits the whole economy at once? That’s a sign something deeper went wrong.

What’s the one thing that ties every industry together? Money and credit. If those are distorted, the problem doesn’t stay in one place. It spreads everywhere.

What Interest Rates Are Supposed to Tell Us

Interest rates are more than the cost of a loan. They’re a signal about time.

When people are saving more, there’s generally more money available to lend. Interest rates tend to fall, telling entrepreneurs: “Go ahead and use credit for longer-term projects. Consumer demand will be there when you need it.”

When people are spending more, less money is available. Rates tend to rise, telling entrepreneurs: “Now might not be the time for big, long-term bets.”

In a healthy economy, interest rates coordinate what producers are building today with what consumers will want tomorrow.

Subscribe now

What Happens When That Signal Is Faked?

When central banks push interest rates below where the market would set them, they send a message that isn’t true: “People are saving. Long-term projects are safe bets.”

Entrepreneurs see that signal and respond. They launch big, ambitious projects — new subdivisions, commercial towers, factory expansions — that feel justified by the low cost of borrowing. For a while, everything looks great. Businesses expand. Stock prices climb. Wages and hiring pick up.

But under the surface, the growth is hollow. The projects being built don’t match what consumers actually want or can afford. The savings to support all that investment were never really there. Economists have a word for this: malinvestment. Not too much investment, but investment in the wrong things, guided by the wrong signals.

When Reality Shows Up

Eventually, the gap between what was built and what people actually want becomes impossible to ignore. Projects stall when demand doesn’t materialize. Borrowers struggle to repay debts taken on during the boom. Resources locked into unsustainable ventures have to be freed and redirected to where they’re actually needed.

That’s the bust. It’s painful. But it’s also the economy correcting itself clearing out the mismatches so resources can find their way to better uses.

The Farmer and the False Forecast

Here’s another way to see it. Imagine a farmer hears a weather forecast predicting record-breaking rainfall this year. Excited, he plants a water-hungry crop across every acre he owns.

For a few weeks, the fields look promising. But the rain never comes. The crops fail. The investment made perfect sense based on the forecast. The problem was the forecast was wrong.

That’s what artificially low interest rates and easy credit do. They tell entrepreneurs the economic equivalent of “it’s going to rain.” Entrepreneurs “plant” accordingly. When the rain doesn’t come, when the savings and ability to pay aren’t actually there, the crops fail.

What This Means

The business cycle isn’t some natural rhythm of the market process. It’s what happens when the signals that coordinate millions of decisions get overridden.

When interest rates reflect real saving and spending, entrepreneurs can plan with less uncertainty. When they don’t, even smart, careful people end up building the wrong things at the wrong time.

The bust isn’t a disease that needs more intervention to be sured. It’s the painful process of getting the diagnosis right and starting to heal.

The Bottom Line

The cause of economy-wide boom and bust cycle is bad information. When interest rates are manipulated, they stop reflecting existing conditions. Entrepreneurs then respond to signals that aren’t real, and the economy pays for it later. The best way to avoid the cycle isn’t better management of the boom. It’s letting interest rates tell the truth in the first place.

Central banks try to stabilize the economy, but by overriding market signals, they can cause the very instability they try to stop.

Two Grocery Trips

In 2020, you could fill a grocery cart for about $150. By 2026, that same cart cost closer to $200. Nothing about the food changed. The eggs are the same eggs. The bread is the same bread. But somewhere between those two trips, something happened to your money.

Most people have blamed the grocery store. Some have blamed supply chains. Some have blamed greedy corporations. But here’s the question worth asking: what if the problem wasn’t with the prices at all? What if the problem was with the money?

What Sits at the Center of It All

Money is the quiet infrastructure of every exchange. It connects buyers to sellers, borrowers to lenders, and savers to investors. But in most modern economies, one institution sits at the center of this system: a central bank.

Central banks, like the Federal Reserve in the United States, are tasked with managing the monetary system. Their responsibilities tend to include:

• Having a monopoly on issuing the currency everyone must accept.

• Regulating banks.

• Adjusting the cost of borrowing money for financial institutions.

• Being the lender of last resort for distressed financial institutions.

In theory, they attempt to bring stability to the monetary system.

But think about what that means. One institution decides how much money exists. One institution sets the price of borrowing. One institution signals to every business, family, and investor in the country whether now is the time to spend or save, expand or hold back.

That’s an enormous amount of power concentrated in one place. And if those decisions are wrong, the consequences don’t stay in Washington. They show up in your grocery cart.

How Inflation Works

Most people think of inflation as rising prices. That is one part of inflation. Inflation starts with an increase in the supply of money and credit. Rising prices are the result.

Not all rising prices are inflation. Prices can rise because of a drought that destroys crops or a spike in demand for a popular product. Those are real changes in supply and demand of specific goods. Inflation is different. Inflation is what happens when more money is created without a corresponding increase in goods and services. Inflation isn’t about specific or relative prices. It’s about the general price level across many goods.

Inflation most often enters the economy through three channels:

• Central banks injecting new money

• Governments borrowing and spending money they don’t have

• Banks expanding credit

More dollars chase the same goods, so prices rise. But they don’t all rise at once, and they don’t all rise evenly.

Why It Doesn’t Hit Everyone the Same Way

Imagine pouring dye into a pool. It doesn’t spread evenly. The color is strongest near the source and fades as it moves outward.

That’s how new money works. The first people to receive it (banks, large investors, government contractors) spend it before prices have adjusted. They get full purchasing power. By the time that money reaches wage earners, retirees, and savers, prices have already risen. Their dollars buy less.

This isn’t just an inconvenience. It’s a hidden redistribution. If a government raised taxes to take 25% of everyone’s cash, people would notice. But if inflation quietly cuts your money’s purchasing power by 25%, most people just blame the grocery store.

The Traffic Light Problem

Here’s a way to see the bigger picture. Imagine a traffic light system where the lights change based on what traffic engineers think traffic should be, rather than responding to actual traffic flow. Sometimes it works fine. Other times you get green lights when no one’s there and red lights when traffic is backed up for miles.

Now imagine this system controls every intersection in the country, and you can’t install better traffic sensors.

That’s what central banking does to money when they expand the money supply through credit expansions, issuing new money, or influencing interest rates. It can override the real signals that come from millions of people saving, spending, and borrowing based on their own lives with centralized guesses about what the economy needs. When those guesses are right, things feel smooth. When they’re wrong, the whole system feels the impact.

Interest rates or credit issuances that don’t reflect real savings mislead businesses into projects that can’t be sustained. Expanded money supplies erode the value of what people have already earned. And bailouts for failing institutions teach the biggest players that they can take oversized risks because someone else will cover the losses.

The Bottom Line

Money works best when it tells the truth. When interest rates reflect real savings, businesses make better plans. When money holds its value, families can plan for the future. When the rules are stable, people can cooperate with confidence. Central banks promise stability, but by overriding the signals that coordinate millions of decisions, they risk delivering the opposite. Sound money matters not just for economic efficiency, but for fairness.

Competition isn’t about how many producers there are. It’s about whether new ones are free to challenge them.

Monopoly and the Role of Competition

When people hear the word monopoly, they tend to picture a villainous company with total control. They envision someone choosing to set high prices, lowering their quality, and getting rich at everyone else’s expense. But that image oversimplifies how markets work.

Here’s an important idea: what matters most isn’t whether there’s more than one producer. What matters most is whether others are free to compete.

How to Define Monopoly?

Each of us is the only source of our own labor and ideas. Does that mean we are monopolists? No. Not in any way that matters. Just because we’re the only provider of one specific type of good doesn’t make us a threat to competition. So the idea of monopoly isn’t about being the only producer. Instead, historically, it was defined by a much larger issue: protection.

Protection means barriers to entry. Sometimes people see things like high start up costs, geography, or control of specific resources as barriers. These barriers make competition harder, and in some cases they can keep competitors out for a long time. But they don’t make competition permanently impossible the way legal protection does. Technology, innovation, and changing demand can eventually overcome even the highest natural barriers. Legal barriers can’t be overcome by a better product.

Competition is most threatened when a producer is legally protected from new competitors.

When a government-granted advantage is given to a producer it can prevent others from entering the market. That’s when consumers lose.

Why Government-Created Monopolies Hurt

When the government steps in and shields a business from competition, the trade-offs tend to work against consumers:

• Innovation can slow. With no challengers, there’s no pressure to improve.

• Prices rise and quality drops. Consumers have nowhere else to go.

• Resources get misallocated. Instead of chasing consumer wants, producers chase compliance, favors, or subsidies.

When you don’t have to win customers, you stop trying.

Competition Is a Process, Not a Scorecard

The market isn’t about how many firms exist right now. It’s about whether entrepreneurs are free to enter when they see an opportunity.

Competition is process of discovery. It’s what happens when someone sees a better way to serve customers and decides to act. That pressure keeps even a lone producer honest to an extent, so long as others are free to challenge them.

Legal barriers can kill this process. When rules block new entrants—through licenses, zoning laws, or exclusive contracts—the process of competition breaks down, even if only one more firm was ever trying to enter.

Are Monopoly Laws Always Helpful?

Many people assume antitrust laws are the natural answer to monopoly power. And sometimes they’ve addressed real abuses. Sometimes they have broken up arrangements that blocked competitors and harmed consumers.

But antitrust laws come with their own trade-offs, and those are worth understanding.

Regulatory costs don’t fall evenly. Large firms can afford teams of lawyers to navigate antitrust compliance. Smaller competitors and new entrants often can’t. The rules meant to keep markets open can quietly raise the cost of entering them.

The line between dominance and excellence isn’t always clear. A company might hold a large market share not because it blocked competitors, but because it built something consumers prefer. Penalizing that outcome can discourage the very innovation competition is supposed to reward.

Legal battles consume resources. When companies spend years and millions defending their position in court, that’s time and money not spent improving products or serving customers. The process itself can become a competitive weapon used strategically by rivals who can’t win in the market.

None of this means antitrust law is useless. It means we should evaluate it the same way we evaluate any intervention: by asking whether it’s actually increasing competition or just increasing complexity. More rules don’t automatically mean more challengers. Sometimes they mean fewer.

A Story of Two Bakeries

Imagine a small town with one bakery. It’s not a monopoly in any harmful sense. If it raises prices or lowers quality, someone else is free to start a competing bakery.

Now imagine the town council passes a law saying no one else can open a bakery. That’s basically giving the bakery permission to underperform. The bakery raises prices. Consumers have no other choice. Service declines. And customers are stuck.

The lesson? It’s not about how many bakers exist. It’s about whether someone new could bake a better loaf.

The Bottom Line

Competition isn’t a number, it’s a check on inefficient behavior. A lone firm in an open market still faces some form of discipline, because someone can always build a better mousetrap. Laws that prevent challengers from entering the market are the biggest threats to competition. If you want better service, lower prices, and more innovation, the best policy is simple: don’t block the next competitor.

Public officials respond to incentives just like the rest of us. We must always remember that self-interest doesn’t disappear simply because someone wants to be a public servant.

Why Good Intentions Aren’t Enough

Many times we expect governments to act like wise caretakers. We want them to be objective, farsighted, and selfless. We often assume or hope that once someone is elected to office or appointed to a public agency, they stop being self-interested and start working solely for the public good.

But that’s not how people work. And it just so happens that politicians, regulators, and bureaucrats are people. They respond to incentives just like consumers and business owners do. This idea changes how we understand everything from budgets to bailouts.

People, Not Angels

People in government are not self-sacrificing angels. They’re humans. Because of this, we need to apply the same logic to government that we apply to everyone else and keep in mind:

• Politicians want to stay in office. They’re rewarded for making promises and spending money in ways that secure votes, not necessarily in ways that create long-term prosperity.

• Bureaucrats want more resources. Agencies are rewarded for expanding their budgets, increasing staff, and regulating more things, not for becoming more efficient.

• Voters are rational, but don’t have all the information they may need. Most citizens don’t have time to research every policy or candidate. That’s not laziness. It’s a reasonable response to the low likelihood of their vote changing the outcome and the fact that there may be other more time-sensitive demands on their plate.

In this system, each parties’ behavior makes sense, but the outcomes often don’t.

Incentives in the Wrong Places

When private businesses serve customers poorly, they lose money. But in government, there’s no equivalent feedback loop. The incentives don’t reward serving the public. They reward expanding power, budgets, and influence.

A few examples:

• Politicians propose popular programs, even if they’re unaffordable, because the costs can be delayed while the (perceived) benefits are immediate.

• Bureaucrats rarely shrink their own departments. Why would they? Larger agencies mean more prestige, more funding, and more job security.

• Lobbyists seek favors for their industries because the benefits are concentrated on their clients, while the costs are spread across millions of taxpayers who may never notice.

This isn’t corruption, it’s understandable behavior based how the system is designed.

Why “Government Failure” Happens

Well-intentioned policies can fail. Not because of bad people, but because of bad incentives, knowledge, or both.

When policies are made through the political process:

• Short-term optics beat long-term planning.

• Symbolic victories beat real solutions.

• Winners are chosen based on promises, not value creation.

For instance, a politician might support giving taxpayer money to a specific industry not because it’s good policy, but because that industry is located in a district they need to win or that maybe (likely) funds their campaign.

The result? Policies that look good on paper or at press conferences, but backfire in practice.

The Trouble With Benevolent Planning

Markets are messy, but they align incentives. Customers reward businesses that serve them well. Investors fund companies that manage uncertainty and deliver value.

Government, by contrast, operates without prices, profit, or loss. Without those signals, planners must guess what people want. They can, and do, guess wrong.

That’s not a moral failing. It’s both an information problem and a motivation problem.

No one becomes all-knowing or perfectly self-sacrificing just by winning an election or getting hired at a regulatory agency.

A Realistic View of Reform

Economics doesn’t argue that government can’t do anything right. It simply insists we need to build systems that account for how humans are, not how we wish they were.

That means:

• Aligning incentives. For example, giving schools more autonomy while tying funding to performance, not how well they fill out forms.

• Decentralizing decisions. Local governments are more accountable because they’re closer to the people they affect.

• Adding transparency. Citizens need tools to see how money is spent and who benefits.

Good governance doesn’t reliably come from simply finding better people. It comes from better rules.

We sometimes create rules based on the hope that we will get the brightest and best to be in charge. Ideally, we want the best and the brightest to do the most good possible once they are in office. But, at the same time, we shouldn’t want a system where the best people can do the most good if that system also can allow the worst people to do the most bad.

We need rules where the worst people do the least harm because the people who end up in charge aren’t always good.

The Bottom Line

Government actors are not above self-interest. Recognizing this isn’t cynical, it’s honest. Economics helps us stop building for angels to be in charge and start designing systems that work for real people, with real incentives.

Cross-functional alignment isn’t a new idea. Matrix organizations, cross-functional teams, dotted-line reporting, alignment meetings, shared OKRs. Organization and management experts have been working on these problems for decades. Every management book tells you to break down silos. Every leadership seminar teaches you to align teams around shared goals.

And yet problems tend to persist. Not because leaders are bad at alignment. Because bad alignment is a symptom for many types coordination failures. Bad alignment is a symptom, it is not a sufficient diagnosis.

The Same Problem, Three Different Causes

A mid-market SaaS company noticed that their enterprise product launches kept failing. Product, sales, and customer success were supposed to work together on every launch. They had cross-functional meetings. They had shared timelines. They had executive sponsorship. Leadership kept saying “we need better alignment.” They tried everything the leadership playbook recommends.

Nothing worked. Launches kept missing the mark. Leadership concluded they had a culture problem.

They didn’t. They had three different problems that looked identical from the outside but required completely different solutions.

Problem one was a design problem. Product was measured on time to get new features out. Sales was measured on deals closed. Customer success was measured on ticket resolution time. Each team was individually incentivized to optimize for their own metrics. When a launch required product to slow down feature work, sales to delay pipeline activity, and customer success to invest in pre-launch preparation, each team faced a reasonable reason not to cooperate. The shared timeline existed on paper. The incentives each team was evaluated on pointed in three different directions.

Better leadership wouldn’t fix this. Better meetings wouldn’t fix this. The system was designed so that cooperation was a sacrifice. The fix was redesigning the economics. It was creating shared launch metrics that all three teams were evaluated on jointly. This made cooperation the rational choice rather than the self-sacrificing one.

Problem two was a connection problem. Customer success had detailed knowledge from support conversations about which features customers actually used and which they ignored. This knowledge would have been invaluable for product prioritization and sales positioning. But it lived in support tickets and team conversations. It never reached product planning or sales in a usable form. Product built features based on their roadmap. Sales pitched based on their assumptions. Customer success watched customers struggle with launches that didn’t reflect how they actually used the product.

Better leadership wouldn’t fix this either. The knowledge existed. It just didn’t flow. The fix was transfering that knowledge. Ensuring that customer success insights reached product planning before the roadmap was set and reached sales enablement before the pitch was built. Not through another reporting template that would strip out context. Through someone who understood all three functions well enough to translate between them.

Problem three was a protection problem. The company had a small team exploring a new approach to customer onboarding. The work was promising but early. It didn’t fit the standard launch process. It couldn’t show revenue impact yet. Every quarter, the team had to justify their existence. They had to compete in reviews against existing departments showing clear metrics. After two quarters of “no measurable results,” leadership cut the cord. They reassigned their resources to proven optimization work.

Better leadership wouldn’t fix this. The measurement system was doing exactly what it was designed to do. It allocated resources toward measurable returns. The fix was protecting the new innovative work. They needed different evaluation criteria for experimental initiatives. They needed someone to translate what the team had learned into language leadership could evaluate. They needed time and space for the work to mature before being judged by metrics designed for a different type of activity.

From the outside, all three problems looked like “silos” and “lack of alignment.” The standard leadership response—more meetings, more communication, more vision speeches—addressed none of the actual causes. Each problem had a different economic factor underneath it and required a different fix.

Why Economic Thinking Changes the Diagnosis

This is the counterintuitive conclusion that runs through this entire series. Economics makes you a better leader because it gives you specific, diagnosable explanations for problems that leadership intuition often treats as generic.

Consider what each economic insight actually provides.

Transaction cost economics (Coase, Williamson) explains that cooperation has real costs. Things like information costs, negotiation costs, enforcement costs. These costs often increase as organizations grow. When a leader sees departments failing to collaborate, the intuitive response is “we need to communicate better.” The economist instead asks: what are the actual friction costs preventing this collaboration? Can we redesign the system to reduce them? The leadership response leads to more meetings. The second leads to structural changes like shared budgets, joint metrics, different authority structures. Solutions that make collaboration rational rather than relying on goodwill.

The knowledge problem (Hayek) explains that the information needed for good decisions is spread throughout the organization. Often it’s found in forms that resist centralization. When a leader sees bad decisions being made, the intuitive response is “we need better data” or “we need more reporting.” The economist instead might ask: is the relevant knowledge even able to be quantified? Is the reporting process itself destroying the context that makes it valuable? The leadership response leads to more dashboards. The second leads to ensuring decisions get made where the knowledge lives or investing in people who can translate between local knowledge and central decision-making without flattening it.

Measurement economics (Goodhart, Muller, McCloskey) explains that measurement systems create systematic bias toward the quantifiable over the valuable. When a leader sees innovation dying, the intuitive response is “we need to prioritize innovation” or “we need an innovation budget.” The economist might ask: is the measurement system making innovation invisible and punishing the people who pursue it? The leadership response leads to a speech. The second leads to fundamentally different evaluation frameworks for different types of work. It leads to portfolio evaluation for exploration, different time horizons for different functions, or space for work that can’t justify itself on a quarterly dashboard.

In each case, the economic thinking doesn’t replace leadership judgment. It sharpens it. It takes a vague sense that “something isn’t working” and gives you a specific mechanism to investigate and a specific intervention to try.

The Diagnosis Determines the Intervention

This is what separates the design, connect, protect framework from generic leadership advice. Each diagnosis leads to a different action.

If you diagnose a design problem and try to solve it with better knowledge flow, nothing changes. The incentives are still misaligned. People now have better information about an opportunity they’re still punished for pursuing.

If you diagnose a connection problem and try to solve it with new metrics, nothing changes. The knowledge still doesn’t reach the right people. You’ve redesigned the incentives around outcomes that teams don’t have the information to achieve.

If you diagnose a protection problem and try to solve it with better knowledge transfer, nothing changes. The measurement system still kills the work. Everyone now understands the opportunity and still watches it die on the dashboard.

The interventions aren’t interchangeable because the underlying economics forces are different. Misaligned incentives, knowledge that doesn’t flow, and measurement bias are three distinct problems that share the same symptom: coordination failure. Treating them all as “alignment issues” is like treating every fever with the same medicine.

Sometimes a fever means you have the flu. Other times a fever means you have heat stroke. You don’t treat them the same way.

Why the Wrong Fix Makes Things Worse

This isn’t just about wasted effort. Applying the wrong intervention to a coordination problem can actively make things worse.

I learned this firsthand at Lyft. Our vehicle service centers offered maintenance and repair for drivers’ vehicles. Most maintenance and repair operations run on a traditional model: one technician per car, start to finish. Leadership wanted to improve throughput and hit profitability targets, so they tried to redesign this. They decided to shift to an assembly line model. In this case multiple technicians worked on vehicles simultaneously, each handling their specialty.

The workflow change made operational sense. But it broke the compensation system. Under the old model (that every competing repair garage used), individual technicians were evaluated on their own output. They were compensated for cars completed, quality of work, and speed. Performance bonuses were straightforward. Under the assembly line model, no single technician owned a vehicle’s outcome. Individual performance metrics stopped making sense. So compensation shifted to team-based bonuses.

Now leadership had a new problem. Some technicians felt they were carrying others. High performers who had thrived under individual incentives felt punished by team-based compensation. Their contribution (and compensation) was averaged with less productive teammates. The workflow improvement that was supposed to increase throughput actually decreased morale. It created retention risk among the best technicians. It made recruitment efforts difficult. All this together threatened both the quality and profitability the design intended to improve.

Fixing the workflow without simultaneously redesigning the incentive structure didn’t move us closer to the goal. It moved us sideways into a different set of problems. The two systems were interconnected in ways that meant optimizing one in isolation created new distortions in the other.

Sometimes Second Best is Totally Fine

This is a pattern economists have studied extensively. In a complex system with many less than ideal situations, removing one doesn’t automatically move you closer to the best outcome. Sometimes it moves you further away. This can happen because the remaining issues interact with the change in ways you didn’t anticipate.

If your main problem is misaligned incentives and you invest in better knowledge flow without fixing the incentives, you may make things worse. People now have better information about an opportunity they’re still punished for pursuing. The frustration increases. The coordination doesn’t.

If your main problem is measurement bias and you redesign incentives without addressing the measurement system, people are now incentivized to pursue work that the evaluation system will still destroy. They’ll try, fail to show results on the dashboard, and learn not to try again.

This is why diagnosis has to come before intervention. This is why the Design, Connect, Protect distinction matters practically, not just conceptually. The three failure modes interact. Getting one right while the other two remain broken can produce outcomes worse than leaving them all broken. You can end up creating new problems between the fixed and unfixed parts of the system.

It’s also why harmonizer thinking requires economic reasoning rather than leadership instinct. Instinct says “fix what you can see.” Economic reasoning says “understand the system well enough to know which limit is actually the problem. Then know what happens downstream when you change it.”

That difference in approach is often the difference between a leader who makes things better and a leader who makes things different but no less broken.

What This Means for How Leaders Develop

Most leadership development focuses on communication, vision, empathy, and decision-making under pressure. These matter. But they’re general capabilities applied to every situation the same way.

Economic thinking acks as an important diagnostic. A leader who understands transaction costs sees coordination failures differently than one who doesn’t. They ask different questions. They investigate different mechanisms. They design different solutions. Not because they’re smarter, but because they have a framework that distinguishes between problems that look identical on the surface.

This is what we mean by harmonizer thinking. It’s not a specific role to hire for. It’s a way of seeing organizational problems that most leaders haven’t been trained to see. Business education teaches optimization and motivation. They often don’t teach the economics of coordination, knowledge, and measurement. These are central to understanding and explaining why organizations can break down as they grow.

The leads us to a counterintuitive implication. The subject most likely to help you become a better organizational leader isn’t always leadership studies.

It’s often times economics.

Not the economics of GDP and interest rates. The economics of how people coordinate. Why that coordination breaks down. And what specific mechanisms cause specific failures.

Every growing company faces transaction cost problems, knowledge distribution problems, and measurement bias problems. Having names for these, and the ability to tell them apart, gives you an advantage that no amount of general leadership advice provides.

The Bottom Line

Cross-functional coordination isn’t new. Every organization has been trying to break down silos and align teams for decades. What’s been missing isn’t “alignment.” It’s better diagnosis of the causes of the breakdown.

The Design, Connect, Protect framework provides that diagnosis.

Design problems need structural solutions. New rules, new metrics, new incentive systems.

Connection problems need knowledge transfer. Ensuring the right information reaches the right decisions in forms that preserve context.

Protection problems need advocacy. Different evaluation frameworks for different types of work, with space for the unmeasurable.

These aren’t leadership platitudes.

They’re diagnostic categories grounded in specific economic realities. They’re built on transaction costs, knowledge distribution, and measurement bias. Each leads to a different intervention because each addresses a different cause of the same symptom.

Economics gives leaders something that leadership advice alone cannot. It gives leaders the ability to see why coordination is failing, not just that it’s failing. That alone can be the difference between a leader who keeps calling meetings and one who actually fixes the system.

Not every cost or benefit stays between the buyer and seller. When our actions spill over onto others, understanding why it happens matters more than assuming someone needs to step in.

The Neighbor’s Bonfire

Your neighbor loves weekend bonfires. He invites friends over, lights up the fire pit, and has a great time. He bought the wood. He’s on his own property. The transaction between him and the firewood seller was completely voluntary. Everyone involved agreed to the deal.

But the smoke drifts into your yard. Your kids can’t play outside. Your laundry on the line smells like a campfire. You didn’t agree to any of this.

That smoke is what economists call an externality. Externalities are costs (or benefits) that land on someone who wasn’t part of the original exchange. Your neighbor isn’t doing anything wrong in his own mind. He made a voluntary purchase and is using his property. But the full cost of his bonfire isn’t falling on him. Part of it is falling on you.

This is one of the most common reasons people say markets “fail.” And it’s worth understanding carefully, because how you think about this problem shapes how you think about solving it.

What Externalities Are

Externalities come in two forms.

Negative externalities are costs that fall on someone outside the transaction. A factory that pollutes a river imposes costs on the people downstream. A loud bar imposes costs on the residents next door. The producer benefits, the customer benefits, but a third party pays a price they never agreed to.

Positive externalities are benefits that spill over to people who didn’t pay for them. A neighbor who maintains a beautiful garden might raise your property value. A beekeeper’s bees pollinate nearby farms. The teenager who decides to wear deodorant for the first time (everyone can relate here). The buyer and seller both benefit…and so do others who had nothing to do with the exchange.

In both cases, the price of the purchase or exchange doesn’t capture the full benefits and costs across all direct and indirect parties.

The Usual Response, and Its Trade-Offs

When people encounter externalities, the instinct is to call for a rule. Tax the polluter to make up for the damage. Subsidize the beekeeper so they can do more good. Pass a law about bonfires. Detention to every smelly teen!

Sometimes that works. But it always comes with its own costs. Regulations can be captured by the people they’re supposed to restrain. Taxes require someone to measure the damage accurately, which is harder than it sounds. Subsidies can encourage more of some thing than the amount people actually want. And every intervention introduces new incentives that produce their own unintended consequences.

The question isn’t whether externalities are real. They are. The question is whether the solution creates fewer problems than the problem itself.

What Ownership Makes Possible

There’s another way economists think about this. Many externalities exist not because markets failed, but because property rights are unclear or incomplete.

If the polluted river is owned by someone, the factory can’t pollute it without consequence. In that case the owner will demand compensation to offset cleaning costs or take the factory to court. If your neighbor’s smoke crosses onto your property, that’s a dispute that clear property rules can help resolve. When ownership is defined and enforceable, people can negotiate directly. The person causing the cost and the person bearing it can find a solution that works for both of them. Often times they can do this without anyone else getting involved.

This isn’t always straightforward in every case. Some problems are widely spread out. You can’t easily negotiate with a million car drivers about air quality. But the principle still matters: the clearer the ownership, the fewer the spillovers go unaccounted. Many of the externalities we blame on “market failure” start with failures to define who owns what.

When Markets Solve It Themselves

Markets also develop their own solutions to spillover problems when they’re allowed to.

Insurance companies price risk in ways that incentivize safer behavior and decrease external costs they have to cover. Neighborhood associations create shared rules for shared spaces. Industry groups develop standards that go beyond what any regulation requires, because their credibility depends on it.

These aren’t perfect. But they have something government solutions often lack: built-in feedback. When they stop working, people stop paying for them. That self-correction is valuable.

The Bottom Line

Not every cost stays between buyer and seller. That’s real, and it matters. But recognizing the problem and knowing how to solve it are two different things. The best responses tend to start with clear property rights, rely on the people closest to the problem, and stay humble about unintended consequences. Externalities are a reason to think carefully, not a reason to assume that every spillover requires a new rule.

Voluntary exchange creates value because both sides choose to participate. When decisions are made on our behalf, even with good intentions, we lose the information and feedback that help resources go where they’re needed most.

The Search for a Better Park

Let’s say a few years ago, a neighborhood needed a new park. Everyone agreed the old one was in bad shape. But how to fix it became a different question entirely.

The city council proposed a $4 million renovation funded by a tax increase. The plan included a splash pad. A performance stage. A new redesigned walking trail. The mock-ups looked great.

But some residents wanted something simpler. They just wanted the old playground fixed and to have some better lighting. Others would have preferred the $4 million to go toward road repairs. A few small business owners pointed out that the tax increase would eat into the cash flow they’d been putting toward hiring.

The park got built. It looked beautiful. The splash pad was popular in the summer. But the performance stage sat mostly empty. Meanwhile, the roads didn’t get fixed. Some of the business owners delayed their hires. And more than a few residents felt they’d paid for someone else’s priorities.

Was the park a waste? Not exactly. Some people genuinely valued it. But the process revealed something important: when one group makes spending decisions for everyone, some people end up paying for things they wouldn’t have chosen, and the things they would have chosen don’t get done.

That trade-off is real. And it’s worth understanding clearly.

Why Voluntary Exchange Works So Well

Throughout this series, we’ve built up a picture of how markets coordinate millions of people without anyone being in charge. A key ingredient to all that is voluntary choice.

Every time you buy something, you’re saying: “I’d rather have this than keep my money.” Every time a business sells something, it’s saying: “I’d rather have the revenue than the product.” Both sides expect to benefit. If they didn’t, the exchange wouldn’t happen.

This process generates enormous amounts of information. Prices tell producers what people want. Profits tell them they’re getting it right. Losses tell them to adjust. The whole system runs on feedback that no one has to design or manage.

What Changes When Choices Are Made For Us

Government currently plays a role in the economy that some people may take for granted. Courts enforce contracts. Laws protect property. Public infrastructure can connect communities. Whether the government is the only ways to provide these institutions is a deeper question, but for now, they’re the foundation that makes voluntary exchange possible.

But government also makes spending decisions that go beyond this foundation. And when it does, the economics change.

Tax-funded programs replace individual choice with collective decision-making. That’s not automatically bad, but it does mean we lose a critical feedback loop. When this happens there are no prices telling officials whether the park was worth more than the road repair. There’s no profit-and-loss signal telling them the performance stage was a poor use of funds. The information that would normally guide resources toward their best use simply isn’t there.

This matters because:

• Without market signals, officials have to guess what people value, and different people value very different things.

• Without profit and loss, programs that aren’t working don’t automatically get corrected. A private business that builds something nobody wants goes under. A government program that is unsuccessful can get a bigger budget next year.

Without individual choice, the people paying for a decision and the people making it aren’t always the same people. This changes the incentives.

The Unseen Side of Every Public Decision

This doesn’t mean government programs never help anyone. They often do. But every dollar spent publicly is a dollar that was taken from someone who would have spent it differently. The community center gets built, but the business doesn’t hire. The subsidy supports one industry, but consumers pay higher prices. The may tariff protect one set of jobs, but likely raises costs.

These aren’t arguments against government. They’re arguments for taking trade-offs as seriously as we’ve taken them throughout this entire series.

The question that matters is asking whether a specific action creates more value than what it displaces. And without the feedback that voluntary exchange provides, that question is genuinely hard, if not impossible, to answer.

The Bottom Line

Voluntary exchange works because both sides choose to participate, and the signals it generates help resources flow toward their best use. When decisions are made collectively, we lose that feedback. This means even well-intentioned programs can direct resources away from where people would have sent them. Understanding the difference between chosen exchange and directed spending helps us tell whether any given intervention is helping or quietly making things harder.

Throughout this series, we’ve explored why coordination is expensive, how knowledge resists centralization, why measurement can kill innovation, and how structure enables or prevents complex work. But there’s an underlying tension beneath each of these seperate ideas that none of them fully resolves.

The systems that make operators and refiners effective (standardized processes, clear metrics, hierarchy) are the same systems that kill creator work. And the freedom that creators need threatens the reliability that operators and refiners depend on. This isn’t a tension you can end or assume away. It’s one you have to learn to use rather than be constrained by.

Two Companies, One Shift

When cloud computing emerged as an alternative to on-site data centers, two enterprise software companies with similar market positions faced the same choice.

Company A (optimization wins). Their on-site business was highly profitable. $500M in annual revenue, 40% margins, customers on predictable multi-year contracts. Moving to cloud would cannibalize this revenue stream. The entire organization was optimized for on-premise success.

When product development proposed a cloud initiative, every function had rational objections. Sales: cloud deals are smaller and compensation will drop. Operations: we don’t have cloud capabilities and building them will distract from our profitable core. Customer success: our existing customers are happy with on-premise and don’t want to migrate. Finance: cloud will hurt current profitability because we’ll recognize revenue slower.

Everyone was right from their individual perspective. The cloud initiative got delayed, scaled back, and eventually killed. Company A continued optimizing their on-premise business. They focused on better processes, enhanced features, more efficient operations.

They optimized themselves right into irrelevance. As the market shifted to cloud over five years, revenue declined 60%. They were eventually acquired at a fraction of their peak valuation.

Company B (managed creative destruction). Same initial position. Same profitable on-premise business that cloud would cannibalize. But the executive team recognized the core dilemma: if we don’t destroy our own business, someone else will.

They created a separate cloud division with fundamentally different economics. Different success metrics—customer acquisition and platform stability, not profitability. A five-year runway to reach profitability while the on-premise business funded the transition. A separate budget that didn’t compete with on-premise optimization. And a dedication to bridging the two divisions. They needed a way to ensure the cloud team learned from on-site customer relationships without on-site blocking cloud’s progress.

The result: Company B managed the transition while maintaining the core business. Cloud revenue eventually exceeded on-site. They maintained market leadership while competitors optimized themselves into decline.

The difference. Both companies understood cloud was important. Both had the talent. Both had customer relationships to leverage. The difference was managing the economic conflict between optimization and innovation. Company A let optimization win because that’s where the immediate rewards were for every individual team. Company B restructured the economics so both were viable at the same time.

Why Innovation Creates Value by Destroying It

Joseph Schumpeter, a highly influential economist from the early 20th Century, had a fundamental insight called creative destruction1. It wasn’t just that innovation and optimization conflict. It was that innovation creates value precisely by destroying existing value.

A new technology makes existing skills irrelevant. A new business model undermines existing competitive advantages. A new product makes existing products less valuable. The value creation happens through the displacement itself. Digital cameras didn’t add to film photography. They destroyed it. Cloud computing didn’t supplement on-site infrastructure. It displaced it.

Inside organizations, this creates an inherent conflict. Your operators and refiners have optimized their current processes, relationships, skills, systems. These represent real economic value built through years of accumulated learning. Your creators identify opportunities that likely will make those valuable creations less valuable or even obsolete.

The same organization must both protect value it’s created and destroy value it’s created. These aren’t just different activities. They’re opposing forces where one’s gain feels like the other’s loss. It only feels this way, though, if we approach our work with an expectation that it should never change.

Most organizations resolve this by choosing preservation over destruction. They protect existing value. They default to what is certain and measurable at the expense of creating new value, which is uncertain and difficult to measure. This is rational for every individual and team inside the system. The problem is it’s often catastrophic for the organization as a whole.

Why Capabilities Become Constraints

Economists Richard Nelson and Sidney Winter showed that organizational skills can become barriers to change.2 Organizations function through routines. They create established patterns for how teams qualify leads. They create consistent approached to designing products. They have a predictable way to handle exceptions, divide resources, and coordinate across teams.

These routines are genuine economic assets. They encode valuable learning from experience. They enable coordination without constant negotiation. They create the consistency that customers depend on. They allow the specialization that operators and refiners need to do their jobs well.

But the same routines that enable efficient execution create barriers to innovation. The better you get at your current approach, the harder it becomes to adopt a different one. Company A was exceptional at on-site software because they’d refined those routines over a decade. That same expertise made them terrible at cloud. It wasn’t because their people were incapable. They needed different routines than they’d developed. Economists call this a “competency trap.” Capabilities become constraints.

People whose expertise is embedded in specific routines resist innovations that would require different routines. This isn’t stubbornness. It’s rational economic self-interest. If your value comes from mastering certain routines, innovations that make those routines obsolete can be threatening.

When a creator identifies an opportunity, they’re implicitly saying: the routines you’ve spent years developing need to change or become obsolete. Even if the creator is right, they’re threatening value that operators and refiners have created. So creator insights get rejected. They aren’t turned down for being wrong. They’re turned down because they threaten existing organizational capital.

The Organizational Immune System

The resistance to innovation that most organizations experience isn’t about closed-mindedness. It emerges from individually rational economic behavior that produces collectively destructive outcomes.

The operator’s logic: “My job is to maintain stability. Innovation creates disruption that threatens the metrics I’m evaluated on. My bonus depends on uptime, and changes can reduce it.”

The refiner’s logic: “Resources spent on innovation are resources not spent on the optimization I’m measured on. My promotion depends on efficiency results.”

The middle manager’s logic: “Innovation might destroy my division’s revenue. My career depends on my quarterly performance.”

The executive’s logic: “R&D investments reduce near-term earnings and stock price. I may not be here when they pay off.”

Every one of these ideas is individually rational. Taken together, they create an organization that rejects beneficial innovation. Think of it like a biological immune system. An immune system doesn’t evaluate whether a foreign body is helpful or harmful. It identifies anything unfamiliar and attacks it. That’s exactly what’s happening here. Innovation is unfamiliar work that disrupts established routines. It threatens existing metrics and redirects resources away from proven activities. The organization’s incentive structure identifies it as a threat and mobilizes against it. The same self-preserving logic that makes immune systems effective in the first place ends up stopping beneficial, new work.

This is why alignment speeches don’t work. Telling people “we need to innovate” doesn’t change their economic incentives. They understand that innovation matters. It’s intuitive. But it’s still irrational for them as individuals given how they’re actually measured and rewarded. The CEO’s speech changes nothing about the economic logic they face every day.

Company A’s leaders were all individually rational. Sales protecting their commission structure. Operations protecting their expertise. Finance protecting current profitability. They were all protecting their trees, while the forest slowly died.

Why Portfolio Thinking Matters

The economic problem isn’t that organizations evaluate innovation projects badly. It’s that they evaluate them using individual project logic when portfolio logic applies.

Individual project evaluation works for optimization. Each initiative either generates positive returns or doesn’t. You can measure results within quarters. Kill what doesn’t work. Expand what does.

Innovation requires portfolio evaluation. Most individual experiments fail. But the portfolio succeeds if you maintain enough experiments to capture the rare dramatic successes while learning from everything else. If a creator team runs ten experiments and eight fail, one produces modest results, and one opens a $50M market that’s an extraordinarily successful year. But individual measurement reports an 80% failure rate.

You can kill innovation by using individual project logic on work that only makes sense as a portfolio. Each “failed” experiment becomes evidence to cut the program. But the “failures” were generating learning that made the successes possible.

This connects to the measurement problem from “Why Metrics Kill Innovation.” It’s easy to measure individual project failure. It’s hard to measure portfolio learning and option value. Organizations tend to underweight innovation because the costs are immediate and visible while the benefits are distant and hard to quantify.

Financial economists understand that some investments create “option value.” This can be thought of as the ability but not obligation to go after future opportunities. Innovation investments work the same way. Company B’s cloud experiments had three types of value.

1. Direct revenue from cloud products

2. Learning that improved their business overall

3. The option to pursue new opportunities as markets evolved.

Traditional ROI analysis captures only the first. Portfolio and option value thinking captures all three. This is why creator work is essential even when it doesn’t generate immediate measurable returns. Creator work creates flexibility that the organization can turn to when conditions change. Organizations that underinvest in creator work are destroying option value. They sacrifice future adaptability and resilience for current optimization.

The Exploration-Exploitation Tradeoff

Organizational theorist James March formalized this tension.3

• Exploitation (what we’ve been calling optimization) refines existing capabilities within known parameters. Returns are quick, certain, and measurable.

• Exploration (what we’ve been calling innovation) searches for new capabilities in unknown domains. Returns are slow, uncertain, and distant.

The bias toward exploitation is structural, not cultural. Managers get evaluated on time horizons shorter than exploration payoffs. Annual performance reviews punish exploration “failures” before successes can emerge. Boards get nervous about exploration spending without visible returns. Investors pressure for near-term results.

But organizations need to optimize over their existence, which, hopefully, is decades or longer. The people making resource use decisions have 3-5 year time horizons. Exploration investments that would pay off in year seven often may not benefit the manager who made them. Rational managers favor exploitation. The result is underinvestment in exploration even when more investment would be optimal for the long-term.

March had a key insight. The right balance depends on how quickly your environment changes. Stable environments need less exploration. Unstable environments need much more. Most organizations get this backwards. They explore aggressively when young and small, then reduce exploration as they mature and have more the resources to fund it. Companies gain capacity for investment exactly when their systems evolve to prevent it.

How Harmonizer Thinking Changes the Economics

The solution isn’t to convince people to act against their economic interests. It’s to restructure the economics so that supporting innovation becomes individually rational.

This is the same principle we’ve seen before in this series applied to the innovation-optimization tension.

• In “The Cost of Working Together,” harmonizer thinking meant building new rules and structures that made coordination the rational choice.

• In “What Headquarters Can’t See,” it meant brokering knowledge between people who had it and people who needed it.

• In “Why Metrics Can Kill Innovation,” it meant protecting valuable work from measurement systems that would destroy it.

• In “Why Structure Determines Strategy,” it meant bridging separated functions so organizations got specialization without fragmentation.

Here, it means doing all of these together to manage creative destruction.

In Company B someone thinking this way might have:

• Created shared success metrics. The cloud team’s progress contributed to everyone’s evaluation. This made cloud support individually rewarding rather than individually threatening.

• Maintained separate budgets. so cloud “failure” on profitability metrics didn’t hurt on-premise teams.

• Made sure the cloud team learned from on-site customer relationships.

• Made sure the on-site team didn’t block experimentation.

• Translated between different evaluation frameworks so leadership could assess both divisions on appropriate terms.

When the individual economic logic aligns with organizational needs, the immune system becomes an adaptive rather than a barrier. People still act in their economic self-interest. But their self-interest now includes supporting innovation rather than blocking it. You don’t change human nature. You change the economics that guides rational human behavior.

The Bottom Line

Schumpeter’s creative destruction explains why the success patterns from Growth Isn’t One Sided are so difficult to sustain. Innovation creates value by destroying existing value. Inside organizations, this means the same company must both protect what it’s built and destroy what it’s built. These are opposing forces.

Organizations understandably default to optimization. Those returns are near-term and measurable. Individuals are evaluated on shorter time horizons. But the company needs longer term thinking. Routines make companies good at what they already do. But, they make them bad at doing things differently. Incentive structures almost always reward exploitation over exploration.

Understanding this as an economics problem enables systematic solutions. Portfolio evaluation that judges innovation on collective learning rather than individual project success. Structural protection that prevents optimization from crowding out innovation. Different measurement approaches for different types of work. And harmonization that aligns individual incentives with organizational needs rather than trying to convince people to act against their interests.

The competitive advantage goes to organizations that can manage creative destruction internally rather than waiting for external pressure to force their hand. They optimize what works today while discovering what will work tomorrow. They exploit and explore simultaneously.

Doing this requires every principle this series has covered. You have to match coordination efforts to the type of work being done. You have to make sure knowledge reaches the right decisions. You have to measure what matters without destroying what you can’t measure. You have to design structures that enable different types of work to coexist. And you have to manage the tension between preserving value and creating it. Not by choosing one over the other, but by building systems where both can happen at the same time.

None of this is easy. But it’s a lot harder if you don’t recognize the problem in the first place. Most organizations experiencing creative destruction don’t know that’s what’s happening. They think they have a motivation problem, or a culture problem, or a leadership problem. They have an economics problem. And economics problems have economics solutions.

A successful and growing economy depends more on good rules than wise overseers. Clear, consistent institutions allow people to cooperate, plan, and adapt — even when no one is in charge.

The Game Works Well When the Rules Are Clear

Most of the time, when we think of what makes an economy work, we picture active players: entrepreneurs, workers, investors, consumers. But behind every decision they make is something easy to miss: the rules of the game.

Rules shape actions. In soccer, you can’t use your hands. In chess, each piece moves a certain way. The same is true in the economy. The rules, whether written or unwritten, determine what kinds of decisions are possible, encouraged, or punished.

Economists call these rules “institutions.”

Institutions aren’t necessarily buildings or organizations. They’re the invisible skeleton that holds the system together. Think of things like:

• Property rights

• Contract enforcement

• Banking laws

• Trust in the currency

• Cultural norms of fairness or reputation

When institutions work well, the economy just feels like it works. People trade, invest, and build for the future. When institutions break down, even smart people with the best intentions struggle to get anything done.

Why Institutions Matter

Imagine two cities. In one, there are clear rules, honest courts, and stable money. In the other, property can be seized without warning, contracts are never written down, and money loses value overnight.

In which society would you rather:

Start a business?

Save for retirement?

Lend money to a friend?

In the first society, you can plan. In the second, you just try to survive.

That’s the power of institutions. They reduce uncertainty. They help strangers cooperate rather than conflict with each other. They allow value to be stored over time. And they give people the confidence to try new things. That’s what makes them foundational to long-run prosperity.

Good Rules Matter Most

People often think the solution to economic problems is to elect the “right leader.” Someone who will fix everything with wisdom and fairness.

But no matter how smart a ruler is, they face the same problem we all do: limited knowledge and self-interest. No matter how great they are, they aren’t an all-knowing angel. Even well-meaning leaders can’t replace the information embedded in millions of scattered decisions.

That’s why good rules are better than relying on only good rulers.

Rules don’t have to be perfect, but they certainly can be better or worse. Ideally the rules need to be clear, consistent, and applied the same way no matter who, when, or where an issue may come up. When they are applied consistently and in a predictable way, people can take chances, make deals, and adjust as circumstances change.

Institutions in Everyday Life

You experience institutions every day without even noticing:

When you swipe your card at a store and it goes through? That’s a system of financial and legal trust.

When you sign a lease or work contract and expect it to be honored? That’s contract enforcement.

When you buy from a stranger on the internet and expect the product to arrive? That’s a mix of reputation systems, third-party guarantees, and social norms.

None of this works because someone planned it all. It works because people built, maintained, and followed institutions. These institutions almost always evolve over time, rather than being invented overnight.

The Cost of Weak Institutions

What happens when institutions are weak, inconsistent, or corrupt?

• Bribes might replace rules. Decisions go to the connected, not the capable.

• Investment likely dries up. No one builds for the long term if tomorrow is uncertain.

• Talent can run away. Entrepreneurs and skilled workers go where their efforts are protected.

• Wealth stagnates. Not because people don’t want to try, but because the system doesn’t reward good decisions.

Weak institutions are a tax on human progress. They punish those who want to play by the rules by changing the rules halfway through.

Institutions Are Built, Not Given

Strong institutions don’t appear by magic. They’re shaped by history, culture, technology, and incentives. Some evolve informally—like trust. Others require formal systems—like courts.

The key insight? We must be humble about how much we can engineer institutions from scratch. Like language or markets, they often emerge through trial, error, and iteration.

But once in place, they’re incredibly powerful. They allow free people to cooperate without being controlled by having a predictable means of addressing conflict.

The Bottom Line

A healthy economy depends on good rules that sometimes simply work quietly in the background. These rules shape the incentives and expectations that guide human action, trade, and trust. Markets don’t need to be managed, but they do need to be made possible. And that starts with the right rules.

Without prices that reflect reality, no one, not even the smartest, most informed planner, can know how best to use scarce resources.

How Do We Decide What to Make and How Much of It?

Imagine trying to bake and sell bread without knowing what flour costs. Or deciding to build a bridge without knowing whether steel or concrete is cheaper. These situations sound far-fetched, but they are more common in history than people realize, and they lie at the core of what some economists call the calculation problem.

Economic calculation is how producers make decisions. It’s how they answer basic but essential questions:

• What should we produce?

• How should we produce it?

• How much should we produce?

To answer these, producers rely on prices. Prices reflect information about scarcity, alternatives, and consumer wants. Prices condense millions of choices into a simple signal that anyone can use.

The Information Hidden in Every Price

Every price tells a story you could never learn any other way. The price of copper reflects:

• How much copper exists in known mines

• How difficult it is to extract and refine

• What industries need copper right now

• What substitutes are available

• What people expect copper prices to be tomorrow

No single person knows all this. But the price captures it all. When copper gets more expensive, construction companies may start using more plastic pipes. Electronics manufacturers may look for alternatives.

Why Markets Do This Better Than Government Planners

In markets, prices emerge from voluntary exchange. Buyers and sellers interact, each using their own knowledge, wants, and limits. The result? Prices that reflect reality, even if no one understands all the pieces.

In economies where governments own inputs like raw materials, machinery, or labor, there are no real prices. Without private ownership and competition, there’s no true exchange. Planners are left with no alternative other than to guess at values, set quotas, and hope for the best. This is where things go wrong.

Without market prices, which rely on property rights and voluntary exchange:

• Resources don’t flow where they’re most needed.

• Producers can’t tell whether they’re creating value or wasting effort.

• Innovation stalls, because no one gets a clear signal about what’s working.

A Tale of Two Bakeries

Let’s say you own a bakery. In a market:

You buy flour based on demand. If it surges, you bake more. If it drops, you bake less. While producing, you track the price inputs like flour, butter, electricity, and wages. If flour prices spike, you might switch to recipes that use less flour, or you might try to charge more, if customers are willing and able to pay.

Now imagine you run a bakery under a system without prices:

The government gives the same amount of flour to everyone, both bakers and non-bakers. You don’t know what flour costs, or how scarce it is, or if someone else needs it more. If you produce too much, it goes to waste. If too little, customers’ needs aren’t met. When flour becomes scarce, you have no way to know until you run out or it stops coming.

That’s the calculation problem. It’s not a math error, it’s a knowledge error. Without prices, there’s no way to know what choices make sense.

The Soviet Steel Mill Problem

Here’s a real-world example of what happens without prices. In the Soviet Union, the government set production targets for steel mills to meet. They said something like “produce 1,000 tons of steel goods.” Sounds reasonable, maybe? But without market prices to guide them, the mills had no way to know what kind of steel goods consumers needed.

So, they made what seemed easiest. They made thousands of thick, heavy sheets and enormous nails. These met their weight quotas but the products weren’t useful for much (what are you going to do with a 20 lb nail?). Meanwhile, other producers needed thin steel for machinery and small nails for roofing. The mills produced millions of tons of steel goods nobody needed and the producers were compensated for making things no one needed.

Why? Because tons of steel isn’t the same as the right tons of steel. Without prices to signal what consumers valued, there was no way for the mills to know the difference, or really to care.

When Prices Lie, Decisions Fail

Even in markets, problems arise when prices get don’t reflect reality. Suppose the government pays some of the cost of corn production. This allows producers to get away with cheaper prices. Suddenly:

• Food companies use more corn syrup instead of sugar

• Farmers plant corn instead of vegetables

• Ethanol producers use corn for fuel instead of food

These decisions make sense based on the fake, low corn price. But they’re actually wasteful. We end up using corn for things that aren’t worth its real cost.

Why It Matters

Prices must come from voluntary exchanges not by decree. The more people that own and exchange goods means more information is reflected within prices. Without ownership and exchange, prices don’t exist. If prices don’t exist, no one can figure out if what they are producing is helpful or wasteful.

The Bottom Line

Without prices, planning is guessing. With prices, it’s calculation. And calculation is what keeps the economy moving forward.

Throughout this series we’ve explored why coordination becomes expensive (”The Cost of Working Together”), how knowledge distribution affects decisions (”What Headquarters Can’t See”), why measurement systems create systematic biases (”Why Metrics Can Kill Innovation”), and why a fundamental job of organizational leadership is designing rules that make cooperation rational rather than hoping for motivated compliance (”Bad Rules Beat Good People”). But all of these insights need organizational structure to actually work.

You can understand the idea that operators, refiners, and creators need different systems. But, if your structure forces them into uniform processes, that understanding doesn’t help.

You can recognize that some decisions need decentralization. But, if your structure centralizes authority, recognition doesn’t matter.

You can design thoughtful measurement systems and well-aligned incentives. But, if your structure makes coordination impossible, none of it matters.

Structure is where institutional design becomes real. It’s how the rules of the game actually get implemented. Get it wrong and success becomes near impossible no matter how good your strategy, people, or resources.

Two Companies, Same Strategy, Different Structures

Two SaaS companies pursued identical strategies: maintain a profitable core product while building a next-generation platform. Both understood they needed different systems for each. Both had smart leadership. Different structures produced radically different results.

Company A used a single product team with all work integrated within it. The same engineering team worked on both core product and the new platform. They used the same prioritization process for maintenance of the current system and innovation for the new product. They had a unified roadmap. They split resources. They had common success metrics.

The logic: “We’re one company with one strategy. Integration enables sharing best practices and maximizes resource efficiency.”

What actually happened: In Q1, the new platform got 40% of engineering resources as planned. By Q2, critical bugs in the core product pulled resources away “just temporarily.” A major customer threatened to cancel their contract unless they got specific core product features. Project management prioritized measurable core product work. New platform resources dropped to almost nothing and became an afterthought.

This pattern repeated for months. Important new platform work was repeatedly deprioritized for urgent core product needs. Engineering productivity dropped. The platform shipped eighteen months late. By then, a competitor had captured the market. Company A was eventually acquired at a disappointing valuation.

Company B split the work into separated divisions. The Core Product Team got 70% of resources and focused on optimization of the current system that was generating revenue and clients. They had dedicated engineering. They planned in quarters. They focused on profitability and customer satisfaction. The New Platform Team got 30% of resources and focused on innovation. They had their own dedicated engineering. Planned in annual sprints. And their metrics focused on technical milestones and customer validation.

Company B assigned someone to bridge the two divisions. Their role was to think across the boundary rather than within each side. They made sure core product insights informed platform design. They prevented the platform from rebuilding what already existed. They managed resource allocation. And they translated between different evaluation frameworks. This was harmonizer thinking in practice. They didn’t create a new department. They simply made a deliberate commitment to having someone focus on the connection between the two rather than the success of either one alone.

What actually happened: When the core product hit critical bugs, the core product team solved them without pulling resources. When a major customer requested features, the core team delivered without affecting the platform. The team member thinking like a harmonizer made sure customer insights informed new platform strategy without creating resource conflicts.

After eighteen months: the core product achieved profitability improvements. Meanwhile, the new platform began customer pilots on schedule. Engineering was productive because teams had focused work. The company launched its platform on time, created competitive differentiation, and was eventually acquired at a premium valuation.

The difference wasn’t strategy. Or talent. Or total resources. It was structure. Company A’s integrated structure created conflicts that favored optimization over innovation. Every resource decision became zero-sum. Urgent measurable work always won. Company B’s separated structure enabled both at the same time. Different evaluation systems meant they weren’t competing. Physical separation prevented resource conflicts.

The Fundamental Trade-off: Specialization vs. Coordination

Every org structure solves the same economic problem that Adam Smith identified centuries ago. Specialization creates value but requires coordination. Coordination can become more expensive as specialization increases.

From earlier in this series, we know operators need reliability and clear processes. Refiners need systematic improvement and analytical tools. Creators need exploration and failure tolerance. When these functions get brought together, conflicts can emerge in terms of priorities, resources, and evaluations.

Operators demand stability that can prevent creator experimentation. Creator uncertainty can threaten refiner’s goals to precise system improvement. Urgent needs from operators can consume creator resources. Measurable refiner and operator work dominates unmeasurable creator work. Separation lets each function optimize for its own requirements without interference.

The thing is, business problems don’t care about your org chart. Separation can create its own costs when problems span across different teams. Separate teams often end up solving similar problems independently. Knowledge developed in one team doesn’t reach others. Different teams make contradictory decisions. Opportunities that require cross-functional work die because nobody owns the coordination.

The org design question is always the same: do the benefits of specialization exceed the costs of coordination? This is Coase’s question from “The Cost of Working Together” applied to structure. Separate when specialization benefits exceed coordination costs. Integrate when coordination benefits exceed specialization costs.

When to Separate

Separate functions when their requirements are fundamentally incompatible. The strongest case for separation shows up when:

• Time horizons conflict (optimization evaluated quarterly, innovation over years)

• Risk profiles conflict (optimization minimizes failure, innovation requires it)

• Resource needs conflict (optimization is predictable, innovation is lumpy and uncertain)

• Success metrics conflict (optimization measured on efficiency, innovation on learning)

When these conflicts exist inside a single company, optimization usually gets prioritized above all else. Not because managers don’t value innovation. Because the rules of the combined system (shared metrics, unified resource allocation, common evaluation frameworks) make optimization individually rational and innovation individually costly.

This is the measurement bias from “Why Metrics Can Kill Innovation” and the design failure from “Bad Rules Beat Good People” put together. The system isn’t broken. It’s working exactly as designed. It’s just designed for one type of work.

Effective separation means dedicated teams, dedicated budgets, different evaluation frameworks, and different processes. But separation without coordination is just fragmentation. This is where harmonizer thinking applies. Thinking in this way bridges separated functions so the organization gets specialization benefits without paying the full cost of lost coordination.

When to Integrate

Integration makes sense when coordination benefits exceed specialization costs. This happens when:

• Functions need constant communication. Like customer success and sales, where handoffs occur daily and success depends on a shared customer understanding.

• When specialization costs are low. Like different product lines in similar markets that share capabilities and can be evaluated on similar metrics.

• When consistency matters more than adaptation. Like brand and marketing, where fragmentation confuses customers and duplication wastes resources.

Even when you integrate, you still need to acknowledge different needs inside the shared structure. Create sub-teams with specialized focus. Use time separation—innovation sprints alternating with reliability sprints. Design evaluation systems that support both optimization and exploration. Protect time and budget for innovation even within an integrated structure. Integration works when you can manage conflicts without a systematic bias toward one type of work.

When Hierarchy Can Help and When It Fails

Hierarchy is the default structure in large businesses for a reason. It reduces real transaction costs. Authority replaces negotiation. A boss decides instead of parties bargaining. It creates clear accountability. It enables standardized processes. These benefits explain why every growing company reaches for hierarchy first.

But hierarchy fails predictably when knowledge is distributed. From “What Headquarters Can’t See,” we know that hierarchy centralizes decisions while valuable knowledge is often local. Information gets filtered climbing the chain. Context gets lost in reporting. Decisions are made without the knowledge needed to make them well. The larger the organization, the more severe this failure becomes.

Hierarchy can work when decisions depend overwhelmingly on systematic knowledge. These are times when consistency matters more than local adaptation. They also apply when speed of decision matters more than quality of local information. Hierarchy fails when decisions depend on local, tacit, time-sensitive knowledge. These are times when local adaptation creates more value than consistency, and when innovation requires the kind of risk-taking that hierarchical control tends to prevent.

Beyond Hierarchy

When hierarchy fails, organizations need different coordination mechanisms. Oliver Williamson, who extended Coase’s work, argued that the choice between governance mechanisms should match the economic properties of the activity being governed. Routine, well-specified work fits hierarchical control. But the most valuable cross-functional work is often too complex for hierarchy and too uncertain for market mechanisms. It needs something else.

That something else is what Elinor Ostrom’s work pointed toward in “Bad Rules Beat Good People.” Cross-functional opportunities inside organizations look a lot like the shared-resource problems she studied. No single department owns them. Success requires multi-party cooperation. Neither hierarchy nor internal markets can coordinate them on their own. The five rules we drew from her research are exactly what harmonizer thinking works to bring inside organizations. As a reminder these rules were

1. Make cooperation individually profitable

2. Let affected parties design their own processes

3. Match rules to context

4. Use graduated consequences

5. Back the system with legitimate authority

The shared budgets, joint metrics, and reputation systems we discussed in “The Cost of Working Together” are those principles made operational. In practice, this means most conflicts get resolved at the working level. They use pre-agreed frameworks rather than escalating everything up the chain. People thinking like harmonizers, who look across boundaries rather than up through them, make this possible by creating agreements before disputes become crises. But it only works if leadership supports these efforts rather than overriding them. When executives arbitrarily override cross-functional decisions, people quickly learn that the real authority is elsewhere. The coordination system collapses.

Structural Requirements for Each Function

Given everything this series has covered, here’s how structure can enable the three types of work.

Operators need decentralized authority with process standards. Operator work depends on local, time-sensitive knowledge. Centralizing operational decisions kills effectiveness because the knowledge doesn’t survive the reporting chain. By the time central decision-makers review operational issues, circumstances have already changed. Give operators authority at the point of customer interaction. Let them use local knowledge without escalation. Provide them with process standards that enable coordination, knowledge sharing across operators, and centralized resources for common needs. The operator principle: autonomy within boundaries.

Refiners need centralized analysis with distributed implementation. Refiner work benefits from systematic analysis across contexts. Data patterns that only appear in aggregate or optimization opportunities that need to compare performance across locations. Centralize analytical capabilities, data access, and knowledge management. But distribute implementation authority so local teams can adapt improvements to their context. Pure centralization loses local knowledge and creates resistance. Pure decentralization loses systematic analysis and creates duplication. The refiner principle: centralized learning, distributed execution.

Creators need protected separation with strategic alignment. Creator work needs protection from optimization pressure. Dedicated teams that don’t compete for operational resources. Different budget processes. Different evaluation criteria. But creators can’t be isolated completely or they lose connection to customer reality and organizational capabilities. Strategic alignment and coordination with the rest of the organization, maintained through harmonizer thinking, keeps creator work grounded without subjecting it to the measurement and resource dynamics that would kill it. The creator principle: separation with connection.

Aligning Incentives With Structure

Structure enables different types of work. But incentives determine what actually happens. If structure separates innovation and optimization but incentives reward only measurable short-term results, structure fails. As we discussed in “Bad Rules Beat Good People,” compensation is one lever among many. Decision rights, information flows, authority structures, and evaluation frameworks all shape behavior independently of pay. Structure has to align all of these, not just the compensation plan.

The most visible misalignment is incentive time horizons. Most incentive systems reward measurable outcomes on short time horizons. This works for operator and refiner work. It destroys creator work. If everyone is compensated the same way, everyone optimizes the same way. That means optimizing for what’s measurable now rather than what’s valuable later.

The solution is matching incentive time horizons to the economics of the work.

• Operators create value through reliability and quality on short cycles. Quarterly bonuses tied to operational performance make sense here. They reward what operators actually produce.

• Refiners create value through systematic improvement on medium cycles. Annual bonuses tied to learning and capability building match how their value materializes.

• Creators create value through exploration and option creation on long cycles. Long-term equity that vests over multiple years aligns their incentives with the time horizon of their actual contribution.

On top of role-specific incentives, shared participation in overall company success, equity or profit sharing, keeps specialization from becoming selfishness. Everyone benefits when the whole organization succeeds. This creates natural pressure toward collaboration even when functions are structurally separated.

The same logic applies to cross-functional initiatives. When a project needs creator exploration, refiner optimization, and operator delivery, give it a dedicated budget and shared success metrics. All participating functions get rewarded based on the project’s outcome. When collaboration is profitable for everyone involved, it stands a better chance at happening naturally. When only one function benefits, it requires forcing. This predictabily creates resistance and produces poor results.

Looking Ahead: Creative Destruction Inside the Firm

Understanding organizational design as an economic problem explains how to build structures that enable operators, refiners, and creators to work together. But there’s a tension we’ve been circling throughout this series that structure alone can’t resolve.

The systems that make operators and refiners effective (standardized processes, clear metrics, hierarchical coordination) are the same systems that kill creator work.

The freedom that creators need (uncertainty tolerance, failure acceptance, long time horizons) threatens the reliability that operators and refiners depend on.

Structure can separate these functions, but the underlying tension between optimization and innovation remains.

Next, we’ll explore Schumpeter’s creative destruction as an internal organizational challenge. How do you build organizations that can destroy their own successful approaches when the market demands it? How do you keep the structures that enabled past success from preventing future adaptation? And what role does harmonizer thinking play in managing the most fundamental organizational tension: the need to follow through on what works and explore what might work next at the same time?

The Bottom Line

Organizational structure is about economic trade-offs between specialization and coordination. Every structural choice represents a decision about which costs to accept.

Separation creates specialization but requires coordination. Integration enables coordination but limits specialization. Hierarchy enables quick decisions but limits local knowledge use. Decentralization uses local knowledge but creates consistency challenges. You can’t eliminate these trade-offs. You can only choose which ones to accept deliberately.

The practical implications follow from the economics of the situation and the roles involved. Separate innovation from optimization when their requirements systematically conflict. In a combined structure, measurable urgent work tends to almost always beat unmeasurable important work. Bring functions together when coordination benefits exceed specialization costs. This is helpful when constant communication, shared knowledge, and consistency matter more than specialized focus. Match structure to the work. Hierarchy for decisions requiring systematic knowledge. Peer coordination for cross-functional challenges. Decentralized authority for work that depends on local knowledge.

Structure alone doesn’t determine success. But the wrong structure makes success near impossible, and more dependent on luck than we might like. The right structure can better enable operators, refiners, and creators to all succeed at the same time which is what long-term success actually requires.

Property rights make exchange, investment, and cooperation possible. Without them, markets can’t function and progress stalls.

The Garden You Won’t Plant

Imagine you rent a small house with a bare backyard. You’d love to plant a garden, but your lease is month-to-month and your landlord has been talking about selling the property.

So you don’t plant anything. Why invest weeks of work and money if someone else might benefit from it, or worse, tear it all out next month?

That hesitation isn’t laziness. It’s rational. You’re responding to the fact that you don’t have a secure claim on the outcome of your effort. Without confidence that what you build will remain yours, you won’t build.

Now scale that feeling up to an entire economy, and you start to see why property rights matter so much.

What Property Rights Actually Are

Property rights are the rules that define who can use something, benefit from it, and transfer it to someone else. They apply to physical things like land, tools, inventory, and to intangible things like ideas, contracts, and creative work. Property rights are essential for things that are rivalrous (one person’s use of a thing reduces another person’s use) and excludable (owners are able to prevent other’s from using it).

But property rights aren’t just about legal ownership. They’re a bundle of expectations:

• Can I use this resource the way I see fit?

• Will I benefit from improving it?

• Can I sell it, trade it, or give it away?

• Will someone protect my claim if it’s challenged?

When these expectations are clear and reliable, people invest, plan, and cooperate. When they aren’t, people protect what they have rather than building something new.

Why Everything Else Depends on This

Throughout this series, we’ve talked about prices, trade, saving, investment, and entrepreneurship. Every one of these depends on property rights functioning in the background.

You can only sell something if it’s yours to sell. A buyer can only pay for something if the money they’re offering belongs to them.

Trade requires transferability. If you can’t transfer what’s yours to someone who values it more, trade doesn’t happen. Without trade, we lose the gains from specialization, comparative advantage, and cooperation that make prosperity possible.

Investment requires security. It is rare for anyone to put money into a business, a piece of land, or someone’s education if the returns can be taken or the rules can change without warning. The carpenter who saves to buy power tools in order to produce more only does so because he expects to keep the benefit of that investment.

Entrepreneurship requires the freedom to try. Starting a business means rearranging resources in a new way. That requires the freedom to obtain and use property based on your own judgment about what might work.

Remove any of these and the entire system we’ve been describing slows down or stops.

The Tragedy of No Ownership

When nobody owns a resource, nobody takes care of it.

Consider a public park with no maintenance budget and no one assigned to look after it. Trash builds up. Equipment breaks. People stop visiting. This can happened because no one had the incentive or the authority to maintain it.

The same logic applies to fisheries where no one owns the fish, forests where no one owns the trees, and aquifers where no one owns the water. When everyone can take but no one is responsible, resources can get used up faster than they can recover.

This isn’t because people are greedy. It’s because the incentives point in the wrong direction. Ownership aligns the person using the resource with the long-term consequences of how they use it. Without that alignment, short-term thinking wins every time.

Ownership Doesn’t Require a Government Deed

Property rights often start informally. Families establish norms about shared spaces. Communities develop customs about water use or grazing land. Online platforms create reputation systems that function like property protections for digital sellers.

Formal legal systems can strengthen and extend these arrangements. But the instinct to define “what’s mine” and “what’s yours” shows up wherever people cooperate and has throughout history. It’s not a government invention. It’s a foundation of human coordination and governments can either support or undermine that foundation.

The Bottom Line

Property rights make the rest of economics work. They give people the confidence to invest, the ability to trade, the incentive to maintain what they have, and the freedom to try something new. When property is secure, people think long-term. When it isn’t, they think about survival.

No one person has all the knowledge in the world. The best systems are those that help us use what we do know to make better decisions, even if we don’t know everything.

Who Knows What We Should Do?

Every day, people make decisions based on things only they know. How long the commute is that day, whether their kid is getting sick, how much their neighbor might pay for a used bike. These tiny pieces of knowledge may not seem like much, but they’re everywhere. And they matter.

The central challenge in economics isn’t just scarcity, it’s figuring out how to make the best use of all this spread out knowledge. The real question isn’t, “What should we do?” It’s, “Who knows enough to decide what should be done?”

What Is The Knowledge Problem?

No single person or authority can know enough to make good decisions for everyone else. This is a very simplified version of what’s known as the knowledge problem.

Knowledge is spread out. It lives in the minds of millions of individuals, each with access to their own slice of information. This knowledge is often based on time, place, habits, and situations no outsider could ever fully grasp. Because of this, we all know some things, but no one knows all of it.

Different Kinds of Knowledge

To see why this matters, it helps to distinguish between different types of knowledge:

• General Knowledge: Broad principles like how engines work or that too much pesticide can kill plants.

• Local Knowledge: Information specific to a particular time and place. Something like knowing that customers in your neighborhood prefer different groceries when it’s hot out.

• Tacit Knowledge: Skills and insights you have but can’t easily explain. Like knowing when bread dough feels “right,” or sensing when a customer is about to buy.

All three types matter. But local and tacit knowledge tend to be the most valuable, and the hardest for others to access.

The Wal-Mart Example

During Hurricane Katrina, Wal-Mart’s disaster response for getting supplies to the region outperformed government agencies. While FEMA waited for damage reports and approval processes, local Wal-Mart managers got to work. Among other actions, these managers verified which roads were passable by going and inspecting them. This allowed them to route deliveries correctly. This information didn’t exist in any government database. It took on the ground, second-to-second data.

Wal-Mart had supplies arriving before FEMA had even finished its assessment. They achieved this because they had systems that trusted and enabled people with local knowledge to make local decisions.

Why Local Knowledge Beats Central Plans

This is why local decision-makers can repeatedly outperform distant authorities. They see changes as they happen. They understand local trade-offs. And they know details that never make it into official reports.

For example:

• A store manager likely understands the buying habits of local customers better than the company’s CEO. If a retail chain mandates the same winter inventory across the U.S., stores in hot and cold climates might end up with the same amount and types of coats. The result? Unsold goods in one state and empty shelves in another.

• A farmer knows the specific conditions of their land (soil quality, weather, and pest risks) better than a policymaker miles away.

• A teacher knows which students learn better through visuals versus through discussion. This knowledge doesn’t show up in standardized test data.

Making decisions from too far away means making decisions without being able to see what truly matters.

When General Knowledge Isn’t Enough

While general knowledge is important, it has limits. General principles are certainly helpful, but they must be applied with care at the local level.

For example, McDonald’s has general guidelines for their service. But how they put those guidelines in place differs across the globe. In some markets they may not serve beef, or they may offer table service. No matter what, the general principle of fast, consistent food service stays the same. But knowing the right way to apply the knowledge changes.

How Markets Solve the Knowledge Problem

Markets don’t solve this problem by giving one person more knowledge. They solve it by not needing to.

Prices, profits, and losses carry information. They do all this without anyone having to centrally process, verify, and approve every data point and fact or opinion.

When a restaurant owner sees that fish prices have jumped, she doesn’t need to understand if global fishing regulations are to blame. She just knows fish is expensive today. Maybe that means tonight’s special should be chicken instead.

The beauty of markets is that they bring together all this spread-out knowledge without requiring anyone to collect it.

The Bottom Line

No one knows everything, but everyone knows something. Good systems don’t concentrate decision-making at the top. They build feedback loops that let each person act on what they know best. When people are free to use their knowledge, outcomes across the economy improve.

One Takeaway

Statistics like GDP are helpful summaries, but they offer limited explanations of how the economy is doing. Without a crystal ball to predict the future, it’s better to focus on principles than managing statistics.

The Number Everyone Talks About

Maybe last night’s news told you that GDP is expected to grow this next quarter. Good news…right?

Maybe. GDP adds up everything we spend. This includes whether we’re building a new business or replacing a flooded basement. Both count the same in GDP stats. More spending sometimes is progress and other times only looks like progress. Not all spending makes us better off.

That doesn’t mean GDP is useless. It means it’s a summary, not a story. And summaries need someone who knows how to read them.

The same is true for every economic stat you hear on the news. Once you know what questions to ask, you’ll be able to understand them better than most people do.

What the Numbers Can Miss

Take unemployment. The headline might say 4%. That sounds healthy. But behind that number are six different ways the government measures unemployment. The most narrow measures only long-term job seekers. The most broad includes part-time workers who want full-time jobs and people who’ve stopped looking entirely. Depending on which measure you use, the story can change.

A falling unemployment rate could mean new jobs are being created. Or it could mean people gave up looking. The number alone doesn’t tell you which.

Or inflation. The news says 3%. But your rent went up 10% and your grocery bill climbed 5%. Meanwhile, the price of your TV dropped. The official number averages all of that together. Your lived experience of inflation and the reported number can feel like they’re describing two different economies.

These numbers aren’t wrong. They’re often just incomplete. And that’s an important difference. The problem isn’t the stats themselves. It’s treating them like the full picture when they’re really a sketch.

The Right Questions Change Explanations

You don’t need a degree in economics or data analysis to understand these data points. You simply need to start with questions that most people don’t think of when they hear a headline number.

When you hear GDP grew: Ask whether that growth came from productive investment or from spending that replaced something lost.

When you hear unemployment fell: Ask what’s happening underneath. Are people finding work they want? Or are they settling, or giving up?

When you hear inflation is under control: Ask in what way? If you’re a retiree on a fixed income and food and medical costs are climbing, a low headline number doesn’t describe your reality.

The numbers are summaries. The human decisions and actions behind them are the full picture.

Why This Matters Beyond Your Living Room

These aren’t just questions for you to ask while watching the news. They’re the same questions policymakers should be asking. The trouble is they most often aren’t.

When a government designs a program to “reduce unemployment,” it’s targeting a number. But if that number can fall for reasons that have nothing to do with people finding good work, then hitting the target doesn’t mean they solved the problem. When a central bank promises to “control inflation,” it’s managing an average. But if that average hides the fact that housing and food costs are surging while electronics get cheaper, the policy might look successful on paper while families feel squeezed.

This is one reason we can’t simply make the economy do what we want. The tools we use to measure success are helpful, but are blunter than we think. When we build policies around moving a number, we risk improving the scoreboard without improving the game.

GDP growth is great, but not if it comes at a loss to lives, liberty, and livelihood.

Why Predictions Fail But Principles Don’t

It’s tempting to think that better numbers would lead to better predictions. If we just measured more precisely, we could see what’s coming. But the economy is made up of millions of people making plans, changing their minds, and responding to each other in real time. That’s not a system that lends itself to perfect forecasting.

Economic statistics can help us spot broad trends over time, compare approaches in similar situations, and identify problems that need attention. These are genuinely useful things. But they can’t tell us what caused what without deeper analysis. They also can’t predict what comes next.

That’s why principles matter more than predictions. Understanding how prices work, why people cooperate, and what drives growth helps you adapt to whatever comes next. A headline number can’t do that. How you think about that number can.

The Bottom Line

Economic statistics are tools, not answers. They can sketch the outline of what’s happening, but they can’t paint the full picture. The best economic thinking doesn’t try to predict what the numbers will say next. It gives you the principles to understand what the numbers mean and what they miss.

Every article in this series has circled the same observation. Organizations fail at coordination not simply because people are selfish or lazy ,but because the systems they operate within can unintentionally make cooperation irrational. Misaligned incentives punish collaboration (”The Cost of Working Together”). Reporting structures strip out the knowledge that matters (”What Headquarters Can’t See“). Measurement systems destroy the most valuable but least measurable work (”Why Metrics Kill Innovation“).

The common thread is that in each case, the people weren’t the problem. The rules were.

Economist James Buchanan won the Nobel Prize in part for applying this insight to political institutions. His core question wasn’t “how do we get better politicians?” It was “how do we design rules so that self-interested political actors produce outcomes that serve the public interest?” He argued that focusing on the character of the people inside a system is a losing strategy. Focusing on the rules of the system itself is where lasting improvement comes from.

The same logic applies inside every organization. And almost nobody applies it there.

The Motivation Trap

Most management approaches treat coordination failure as a motivation problem. Teams aren’t collaborating? Inspire them. Departments are siloed? Build culture. Innovation is dying? Bring in a speaker to talk about the importance of risk-taking.

All this assumes that if people cared enough, they’d cooperate. The default solution is to make them care more. Hire only those who bleed ping, or black, or whatever color is in your brand toolkit. This can work for a bit, but it’s unsustainable.

This approach has a fundamental flaw. It requires everyone to be the best version of themselves at all times. On the days they love the company, they go above and beyond. They bridge gaps between departments. They flag problems that aren’t their responsibility. They pursue opportunities that don’t fit their metrics. On the days they’re tired, frustrated, or simply focused on their own deliverables, the coordination fails.

As Steven Kerr explains in his famous article “On the Folly Of Rewarding A and Hoping for B”, this turns the organization into “a fortunate bystander” rather than an active force shaping behavior. Some people will be generous with their time and attention regardless of incentives. Some will bridge cross-functional gaps out of personal commitment. But the organization isn’t causing these behaviors. It’s just getting lucky when they happen.

Kerr’s insight cuts to the core: “By altering the reward system the organization escapes the necessity of selecting only desirable people or of trying to alter undesirable ones... where such reinforcement exists, no one needs goodness (Kerr pg. 782).”

That last phrase is vital. A well-designed system doesn’t need everyone to be selfless. It needs the rules to make cooperation individually beneficial. The goal is for people to do the right thing for the organization on their best days and their worst days, because the right thing for the organization is also the right thing for them.

Design Problems, Not Motivation Problems

Buchanan’s contribution was reframing political dysfunction from a people problem to a rules problem. Bad outcomes don’t always come from bad people (to be clear, bad people are a problem too). They instead can come from rules that make bad outcomes individually rational.

Inside organizations, the same reframing transforms how you approach every persistent coordination failure.

The motivation framing: “Our teams aren’t collaborating on cross-functional problems. We need to build a culture of collaboration. Let’s do an offsite. Let’s bring in a facilitator. Let’s have the leadership team set the example and model the behavior we want to see.”

The design framing: “Our teams aren’t collaborating on cross-functional problems because each team is measured on independent metrics that make collaboration a sacrifice. Product loses momentum. Sales loses pipeline time. Customer success loses ticket resolution speed. The system punishes collaboration. Let’s redesign the incentives so that success is profitable for every team involved.”

The first approach asks people to act against their incentives. It works briefly. Offsites generate enthusiasm, facilitators create temporary alignment. But when you get back in front of your computer it fades as people return to the daily reality of how they’re actually measured and rewarded.

The second approach changes the daily reality. It doesn’t require sustained enthusiasm or cultural transformation. It requires getting the rules right, then letting self-interest do the work that motivation can’t sustain.

This is what Buchanan meant by focusing on the rules of the game rather than the players. You don’t need better people. You need better rules.

What Good Rules Look Like

Buchanan’s work gives us an important principle: focus on the rules of the game rather than the character of the players. But principles need evidence. How do you actually design rules that produce voluntary cooperation? For that, we turn to Elinor Ostrom.

Ostrom won the Nobel Prize for studying a problem economists had largely given up on. She researched how communities manage shared resources without either markets or top-down control. Conventional theory predicted that fisheries, forests, and irrigation systems held in common would be overused and destroyed. This is famously known as the “tragedy of the commons.” Ostrom went and looked at actual communities around the world and found something different. Many of them had developed rules that produced voluntary cooperation for generations without external enforcement.

What made these systems work wasn’t better people. It was better rules. Ostrom identified specific design principles that successful self-governing communities shared. These principles can translate directly to the cross-functional coordination challenges inside organizations. Combined with Buchanan’s insights, her research points to five rules for designing systems where cooperation becomes the default choice.

Rules must make cooperation profitable for individuals, not just the organization. It’s not enough for collaboration to be “good for the company.” Each worker needs to see personal benefit. Shared success metrics where all participating functions receive bonuses based on collective outcomes. Joint budget authority where teams must agree on allocation, creating natural negotiation that reveals real priorities. Career advancement paths that reward cross-functional contribution, not just siloed performance.

People who live under the rules should design them. Ostrom’s research showed that systems imposed from the top fail far more often than those designed by the affected parties. When teams co-design their collaboration processes, they build in features that work for their context. When leadership imposes frameworks, they create compliance without commitment. The difference is a focus on information rather than buy-in. The people doing the work know which rules would actually help and which would just add complexity.

Rules must match the type of work. One-size-fits-all solutions create unnecessary friction. Operator coordination needs formal standards and clear processes. Creator coordination needs lightweight check-ins and experimental flexibility. Refiner coordination needs structured improvement cycles with room for iteration. Applying operator rules to creator work kills innovation. Applying creator rules to operator work creates chaos. Good system design is specific to context.

Rules must have graduated consequences. Ostrom also found that successful rules start with mild consequences for non-cooperation. Things like peer feedback and reputation effects are helpful steps before escalating to formal consequences. This keeps enforcement costs low and maintains relationships. Most conflicts can get corrected informally when the rules are well-designed. Heavy-handed enforcement from the start signals distrust and creates resistance.

Rules must be supported by legitimate authority. When leadership respects cross-functional decisions made through these processes, those processes work. When they override them arbitrarily, people learn that the real authority is elsewhere. The coordination system collapses. The rules only function if the organization genuinely commits to them.

Why This Isn’t Just “Better Incentive Design”

You might read this and think: this is just about aligning incentives. HR and compensation teams already work on this.

It’s deeper than that. Compensation is one lever. Buchanan’s insight is about the entire system. Things like decision rights, information flows, authority, evaluation frameworks, resource allocation processes, career paths all shape behavior independently of compensation.

Consider the persistent cross-functional problems in your organization. The ones that survive every reorg and every new initiative. These problems persist not because your compensation structure is wrong (though it might be). They persist because the full system of rules makes those problems nobody’s rational priority to solve. Rules like: Who has authority? Who has information? Who gets evaluated on what? Who allocates resources? Who resolves disputes?

This is the gap that your organization may be currently filling with hope. Hoping that someone will take ownership of cross-functional problems that don’t appear in anyone’s metrics. Hoping that teams will collaborate despite incentives that point in different directions. Hoping that people will flag problems that aren’t their responsibility because they care about the company.

Some will. On some days. But you’re banking on people being the ideal version of themselves to address gaps and misalignments as they come up. That’s not sustainable. You need systems where people do their job well on the days they love the company and on the days they feel differently. The success of your company depends on building rules where people aren’t assumed to be the ideal version of a worker. You need systems where cooperation happens because it’s rational, not because it’s virtuous.

The Connection Across This Series

This idea to design rules for voluntary cooperation rather than hoping for motivated compliance is the economic logic underneath every concept in this series.

Transaction costs might be high because the rules make cooperation expensive. Redesign the rules (shared budgets, joint metrics, cross-functional authority) and cooperation becomes cheaper.

Knowledge doesn’t flow because the rules don’t make sharing rational. If the customer success manager’s insight about a struggling account doesn’t connect to any incentive or evaluation they face, why would they invest time translating it for product development? Redesign the rules so that knowledge sharing is rewarded, and information flows.

Measurement kills innovation because the rules evaluate all work the same way. Redesign the rules (portfolio evaluation for creators, reliability metrics for operators, improvement metrics for refiners) and different types of work can coexist.

In every case, the intervention isn’t motivation. It’s design. Thinking like a harmonizer to design new rules and structures that make cooperation rational is Buchanan’s economic insights applied inside the firm. You can’t rely on inspiration to make people cooperate. You need to build systems where cooperation is the obvious choice.

The Bottom Line

Your organization’s cross-functional problems aren’t motivation problems. They’re economic problems. The people inside your organization are responding rationally to the rules, incentives, and structures they operate within. When those rules make cooperation a sacrifice, people won’t cooperate no matter how many offsites you run or team speeches you give.

Buchanan’s insight from political economy applies directly here. Focus on the rules of the game as much if not more than you focus on hiring. Design systems where self-interested behavior produces collective benefit. Make cooperation profitable for individuals, not just desirable for the organization. Build rules that work when people are at their best and when they’re not.

Where such systems exist, no one needs to rely on goodness alone. They just need rational self-interest, which is the one thing you can always count on.

One Takeaway

The economy runs on signals, not switches. The more we try to control outcomes from the top down, the more we distort the very signals that help people make good decisions from the ground up.

Messing With Signals Messes With the System

If you could push a button to raise your income, lower unemployment, or make your money worth more, wouldn’t that be nice?

That’s the promise a lot of economic policy tries to sell. Twist a few knobs, set some rates, pass the right bill and poof the economy will do what we want.

But the truth is, the economy isn’t a machine with levers and dials. It’s a system of people. And every person is acting, choosing, reacting, and adapting based on the signals around them.

Change those signals, and you change the choices.

This means the tools some choose to use to “manage the economy” (interest rates, inflation targets, stimulus packages) aren’t neutral. They shape behavior. And when used poorly, they mislead the very people the economy depends on.

Coordination Without a Conductor

Markets work not because anyone is in charge, but because everyone is adjusting to everyone else.

That’s the real beauty of systems without central control. You don’t need a master plan. You need clear signals. Prices tell us where things are scarce. Interest rates tell us whether people are saving or spending. Profits and losses tell us whether we’re creating value or wasting resources.

These aren’t just numbers. They’re information.

They help us answer essential questions: Should I invest now or wait? Should I hire more people or cut back? Should I move to this city, change careers, buy a home?

What Happens When The Signals Are Wrong?

In the early 2000s, families across the U.S. looked at the numbers and made what seemed like a smart decision. Interest rates were low. Housing values seemed to never stop climbing. Their monthly payment on a new home would barely be more than rent. Every signal said: buy now.

So they did. And so did millions of others.

But those signals were misleading. Interest rates weren’t low because Americans were saving more. They were low because the Federal Reserve had pushed them there. Housing prices weren’t climbing because of real demand. They were climbing because cheap credit flooded the market with buyers who couldn’t actually afford what they were purchasing.

When rates adjusted and the credit dried up, homes lost significant amounts of their value. Monthly payments jumped. Owners got stuck owing more than the house was worth.

These families didn’t make bad decisions. They made reasonable decisions based on bad information. That’s exactly what distorted signals do. They turn good judgment into bad outcomes across millions of people at once.

Why Some Try Anyway

So why do we keep trying to manage the system from the top?

Because it’s tempting. Big problems seem to call for big solutions. And aggregates like GDP, inflation, and unemployment give the illusion of control. They turn a messy, dynamic system into a scoreboard. And if you think you can move the score by adjusting a few settings, why not try?

But the scoreboard isn’t the game. When you focus too much on moving the numbers, you forget about the players. You forget about the incentives, the trade-offs, the limits, the local knowledge. You forget the stuff that actually makes the economy work.

Good Rules Beat Good Intentions

This doesn’t mean we throw up our hands and do nothing. But it means we focus on what can work.

We don’t need a better pilot. We need a better autopilot. That means:

• Clear, stable rules people can rely on.

• Honest money that holds its value over time.

• Prices that reflect reality, not someone’s best guess.

• Freedom to adjust, innovate, fail, and try again.

When we focus on those things, the system works surprisingly well and better than any other alternative. Not because we control it. But instead because we’ve stopped trying to.

The Bottom Line

The economy is made up of people, not equations. Every attempt to manage it from the top down risks distorting the signals people rely on to make good decisions. It’s true that you can’t manage something if you can’t measure it. But it’s also true that just because you can measure something does not automatically mean it needs to be managed.