Latest / The Productivity Podcast with Fexingo: Output, Efficiency, and Long-Term Economic Growth / The Productivity Paradox of Standardized Units
Transcript
- Lucas: Let’s start with a number that feels like a joke until you do the math. In nineteen seventy five, when France fully committed to the metric system across its industrial base, the transition cost was roughly three percent of its annual GDP. That sounds small, right? Three percent. But when you break that down per worker, it was about two hundred dollars in lost productivity per person just to retrain, retool, and recalibrate. And that was before the real hit: the years of confusion between old and new parts. Luna: Two hundred dollars per worker sounds manageable in isolation, but in aggregate, that’s billions in dead weight. Did the French economy actually recover that loss, or did it linger? Lucas: It lingered for a decade. The official narrative is always that standardization equals speed. You pick one unit, everyone speaks the same language, transactions become frictionless. But the reality in the late seventies was a chaotic hybrid era where French engineers were ordering British bolts in millimeters and getting American threads in inches, leading to massive assembly line stoppages. We tend to view standardization as a pure good, but sometimes the cost of enforcing it outweighs the benefit of using it. Luna: So the friction isn't just in the initial switch; it's in the ongoing mismatch of legacy systems trying to talk to new ones. Lucas: Exactly. And here is the thing that really trips people up. We look at today’s tech stack and think, 'Oh, APIs are the standard. If we just get everyone on REST endpoints, everything will flow.' But I want to talk about a different kind of standard: the standardization of work processes themselves. Specifically, how rigid adherence to standardized operating procedures can actually reduce long-term economic output by killing local adaptability. Luna: You’re saying that if every factory floor follows the exact same playbook, they lose the ability to fix problems on the spot? Lucas: Right. Let’s look at the Japanese automotive industry in the eighties versus the American auto industry. Toyota didn’t just standardize the car; they standardized the problem-solving method. But crucially, they allowed for 'jidoka' — stopping the line when something was wrong. The Americans had standardized the line to keep moving at all costs, which meant defects piled up. The lesson wasn't that standardization was bad; it was that the standard had to include the mechanism for deviation. Luna: That’s interesting because most companies today are trying to eliminate deviation entirely, viewing it as waste rather than data. Lucas: Precisely. And that brings us to the core of today’s angle: The Productivity Trap of Perfect Alignment. We are seeing a massive wave of consolidation in software tools, supply chains, and even educational curricula toward single, dominant standards. On paper, this should maximize efficiency. In practice, it creates brittle systems that collapse under minor shocks. Think about the recent semiconductor shortages. They weren't caused by a lack of standardization; chips are highly standardized. They were caused by a lack of redundancy in a hyper-efficient, just-in-time model. Luna: So efficiency without resilience is just a faster way to fail when the environment changes. Lucas: I would argue it’s worse than failure. It’s invisible decay. Because the system looks smooth, you don’t notice that you’re losing market share to more agile competitors who are willing to be slightly messy. Let’s look at a concrete example from the logistics sector. In the nineties, FedEx pioneered the hub and spoke model. It was a brilliant standardization of package routing. But as volume exploded, that standard became a bottleneck. They had to invest billions not to improve the standard, but to break it apart into regional micro-hubs. Luna: Which means the optimal standard changes as the scale increases. What works for ten packages doesn't work for ten million. Lucas: Correct. And yet, we see corporations trying to apply the same 'best practice' templates across vastly different operational scales. A template that works for a fifty-person marketing team is disastrous for a fifty-thousand-person sales force. The productivity loss comes from the mismatch, not the template itself. We need to talk about 'contextual standardization' — knowing when to stick to the script and when to improvise. Luna: How do organizations measure that balance? Is there a metric for 'good enough messiness'? Lucas: Not officially. But if you look at ROIC, Return on Invested Capital, you’ll find that companies with high process variance in their customer-facing roles often outperform those with rigid scripts. Why? Because they spend less time fixing process errors and more time solving customer problems. The variance is the productivity gain. It’s an arbitrage of attention. Luna: So the goal isn't zero variance, but managed variance. Where does the data suggest the tipping point is? Lucas: There’s a study from MIT Sloan back in two thousand eighteen that tracked call centers. They found that agents who deviated from the script by more than fifteen percent had higher customer satisfaction scores but slightly longer handle times. However, when you factored in retention rates and upsell success, the net revenue per hour was twelve percent higher for the deviators. The 'waste' of extra time was offset by the value of the interaction. Luna: Twelve percent is huge. So the standard script is costing them money by being too rigid. Lucas: It is. And this applies far beyond call centers. Look at software development. The rise of Agile was essentially a rejection of Waterfall, which was the ultimate standardization of the development lifecycle. Agile introduced controlled chaos. It wasn't less structured; it was structure that adapted to feedback loops. The productivity jump came from allowing teams to change direction without violating protocol. Luna: But doesn't that create coordination overhead? If everyone is improvising, how do you ensure the pieces fit together? Lucas: That’s the key question. The answer lies in interface standardization, not process standardization. You standardize the handoffs, but not the work itself. Like electrical outlets. The outlet shape is fixed, so any device can plug in. But what happens inside the device is up to the manufacturer. Most companies try to standardize both, which is why integration projects take so long and cost so much. Luna: So we should focus on making the boundaries clear, not the interiors uniform. Lucas: Exactly. Clear boundaries, flexible interiors. This is particularly relevant in the current economic climate of October twenty twenty-six. With interest rates stabilizing but growth slowing, companies are cutting costs by tightening control. They’re trying to squeeze more efficiency out of existing structures by removing autonomy. My argument is that this is the wrong lever to pull. You’ll get short-term compliance, but long-term stagnation. Luna: Because you’re trading potential innovation for guaranteed mediocrity. Lucas: Guaranteed mediocrity is a very real risk. Let’s look at retail. Walmart’s supply chain is legendary for its standardization. Every item has a barcode, every truck has a RFID tag, every store has the same layout. It’s incredibly efficient. But when consumer preferences shifted toward experiential shopping, Walmart struggled to adapt because their entire infrastructure was optimized for throughput, not experience. They had to rebuild from scratch, whereas smaller, less standardized retailers pivoted faster. Luna: So the standardization that made them successful became a liability when the market changed. Lucas: It did. And the cost of reversal is astronomical. This is why we need to think of standardization as a temporary state, not a permanent goal. You standardize to scale, then you de-standardize to innovate. Most companies forget the second step. They stay locked in the first phase, accumulating technical debt in their organizational design. Luna: Technical debt in culture. I like that. How do leaders know when it’s time to de-standardize? Lucas: When the marginal cost of enforcement exceeds the marginal benefit of consistency. If you’re spending more energy policing deviations than gaining value from them, you’ve crossed the line. And in many knowledge-work industries, that line was crossed ten years ago. We’re still running twenty-first-century problems on twentieth-century rules. Luna: So the prescription is periodic audits of our own rules? To see which ones are dragging us down? Lucas: Yes. And then having the courage to break them. It’s counter-intuitive, but true. The most productive organizations are those that can toggle between standardization and experimentation based on the task. Routine tasks get standardized. Novel tasks get freed up. Mixing them up is where the productivity leak happens. Luna: It sounds like we need a portfolio approach to workflows, similar to how investors manage assets. Lucas: A portfolio approach is exactly right. Some assets are stable bonds, some are growth stocks. You don’t treat them the same way. You rebalance regularly. If you hold all bonds, you miss growth. If you hold only stocks, you risk ruin. Balance is dynamic, not static. Luna: Dynamic balance. That’s a much better mental model than aiming for perfect efficiency. Lucas: Perfect efficiency is a myth. It’s a destination that doesn’t exist because the environment is always moving. The goal is adaptive capacity. The ability to shift gears quickly. And that requires leaving room for imperfection in the daily operations. Luna: Before we wrap up, I have to ask about the listener support that keeps this network going. If walking through the economy with us has made something click, consider supporting independent journalism that dives deep into these structural issues. Lucas: We rely on listeners who value nuance over noise. Your support helps us keep this show ad-free and focused on the details that matter. You can find us at buy me a coffee dot com slash fexingo — that's F. E. X. I. N. G. O. Every contribution goes directly into keeping the lights on and the research thorough. Luna: It’s a small way to ensure we can keep digging into these hidden costs for you. Lucas: Back to the topic. If you’re managing a team, try one experiment this week. Pick a routine process, document it, standardize it completely. Then, pick a novel problem, and forbid your team from using any existing templates. See what happens. Measure the difference in speed and quality. Luna: It might reveal that your current standards are holding you back more than helping you. Lucas: Or it might confirm they’re necessary. Either way, you’ll have data, not just intuition. And in economics, data always wins. Luna: So the next time you feel the urge to enforce a rule, ask yourself: is this creating flow, or just preventing drift? Lucas: If it’s just preventing drift, you might be building a dam instead of a channel. Thanks for listening.