Comparative Advantage¶
Why It Matters¶
Absolute thinking leads to bad allocation. The best programmer shouldn't debug if their comparative advantage is architecture, even if they're also the best debugger. A country that's worse at everything still has comparative advantage in something. Trade benefits both parties when each specializes in their comparative advantage.
The Key Move¶
Don't ask "who's best at X." Ask "who gives up least to do X." Convert absolute productivity into opportunity cost terms. The person with comparative advantage in task A is the one whose opportunity cost (what they give up by doing A instead of B) is lowest.
Classic Application¶
International trade. A country that's more productive at everything still benefits from trade. If the US is twice as productive at making cars and three times as productive at making computers, it should specialize in computers and import cars. Portugal should make wine even if England could make it more efficiently, because England's comparative advantage is in cloth.
Surprising Application¶
Team composition. A founder who can do everything should still delegate based on comparative advantage. The question isn't what they can do, but what costs them least relative to others. A CEO who's good at coding still shouldn't code if their comparative advantage is fundraising - even if they're better at coding than their engineers.
Failure Modes¶
- Assigning tasks to whoever is "best" in absolute terms - this ignores what they're giving up
- Ignoring transaction costs of coordination and trade - specialization has overhead
- Forgetting that comparative advantage can shift with investment - today's disadvantage can become tomorrow's advantage
- Treating comparative advantage as static - it changes as skills and circumstances change
- Ignoring economies of scale and scope that complicate the simple story
Go Deeper¶
Ricardo's original treatment of comparative advantage in international trade. Deardorff's work on the generalized theory of comparative advantage.