FedEx Was Broken Until They Changed One Thing: The Munger Lesson Every Builder Needs to Understand
Years ago, FedEx had a serious problem with their overnight package sorting operation.
Packages weren't arriving on time. The service was falling apart. They hired more people. Improved processes. Gave extra training. Nothing worked.
The real problem? They were paying workers by the hour.
If you finished early, you kept getting paid until the shift ended. If you took longer, same deal. The incentive was completely misaligned with what the company needed.
When they changed the model — paying per completed shift and letting people go home once all packages were sorted — the problem disappeared almost overnight.
They didn't hire new employees. They didn't buy new technology. They just changed the incentives.
Charlie Munger puts it simply:
> *"Show me the incentives and I'll show you the outcome."*
---
Why This Is the Most Powerful Sentence I've Ever Read
Look, I come from the coding world. I'm a developer. My natural instinct when something isn't working is to look for the technical bug, the broken process, the wrong tool.
But Munger taught me that most problems that look technical, operational, or people-related are actually problems of misdesigned incentives.
And the worst part is they're invisible. Nobody at FedEx woke up thinking *"I'm going to do my job badly today."* They were just rationally responding to the incentives in front of them.
That's what's wild about this concept: irrational behavior is almost always completely rational once you understand the person's incentives.
---
How Incentives Destroy Products Without Anyone Noticing
In 2026, I see this constantly in the SaaS and digital tools world.
A classic example: the poorly designed freemium model.
Many products offer a free version to acquire users. Sounds good in theory. But if the product team's incentive is measured by *number of registered users* and not *paying users*, the team optimizes for capturing people, not converting them.
Result: complicated onboardings that don't explain real value. Features you don't need before seeing the ones that would make you pay. A product that seems designed to keep users on the free version forever.
Nobody made that decision consciously. They just followed the incentives they had.
The Question You Should Ask About Your Product
What behavior are your metrics actually incentivizing?
Not the one you think they're incentivizing. The real one.
If you measure *time in app*, you're incentivizing addiction, not value. If you measure *features used*, you're incentivizing complexity, not clarity. If you measure *support tickets closed*, you're incentivizing closure speed, not real problem resolution.
This isn't theory. It's something to review this week.
---
The Problem With Your Own Incentives as a Builder
Let me be direct because this happened to me.
For months I was building features nobody had asked for. I felt productive. I was in pure builder mode, shipping things, watching the repository grow.
The problem? My real incentive was *feeling busy and useful*, not *solving the user's problem*.
The feeling of building is immediate and satisfying. Feedback on whether what you built actually matters arrives late and is uncomfortable to seek.
Munger would say: "Of course you did that. Your personal incentives were pointing in that direction."
How I Changed It
Two concrete things I did:
1. Changed my weekly metric. I stopped measuring *what I built* and started measuring *how many conversations I had with real users*. If in a week I hadn't spoken with anyone using my product, the week had been bad regardless of how much code I'd written.
2. Set a validation-before-building rule. Before starting any new feature, I need to identify at least two users who've asked for something similar. Not a variant of what I want to build. Something they described in their own words.
Seems obvious. It wasn't to me.
---
Munger and Institutional Incentives: The Darkest Part
There's a deeper level to this concept that Munger explored extensively: institutional incentives.
Large institutions — banks, consultancies, big tech companies — have their own incentive systems that often work against the client's interest.
A consultant who charges by the hour has a structural incentive for projects to last longer. A doctor who charges per visit has an incentive for you to come back. An advertising agency that charges based on managed budget has an incentive to increase that budget.
This doesn't mean all these people are corrupt or bad. Munger was very clear on that: don't assume malice where the incentive explains everything.
But it does mean that when you work with someone, the first question should be: *how does this person make money and how does that affect what they recommend to me?*
---
How to Use This Mental Model This Week
Three concrete exercises:
Exercise 1: Audit your current metrics. Take the 3 main metrics you use to measure your project's success. For each one, ask yourself: *what behavior does this metric incentivize if I optimize it to the max?* If the answer makes you uncomfortable, the metric is wrong.
Exercise 2: Analyze a recent decision you didn't understand. Think of someone (a client, a partner, a competitor) whose behavior seemed irrational or counterproductive. Now ask yourself: *what is their real incentive in that situation?* Almost always the behavior makes more sense than it seemed.
Exercise 3: Design an incentive, not a rule. If you want to change a behavior in your life or business, before creating a new rule or process, ask yourself if you can change the underlying incentive. Rules get broken. Incentives work on their own.
---
The Idea I'm Taking With Me
What impresses me most about Munger is that this framework works at every level: your personal behavior, your product, your business metrics, the institutions you work with.
You don't need advanced psychology or complex models. Just learn to ask this question before judging or designing any system:
*What's the real incentive here?*
FedEx didn't fix their people. They fixed the system.
Sometimes you don't need to change your discipline, your willpower, or your processes either.
You just need to change the incentives.
---
*Do you have a personal example where incentives were misaligned and you couldn't see it until it was obvious? I'd love to read it.*
