Latest / The Productivity Podcast with Fexingo: Output, Efficiency, and Long-Term Economic Growth / How Standardized Screw Threads Changed The World
Transcript
- Lucas: If you walk into any hardware store today and grab a bag of screws, you are holding one of the most significant intellectual property rights in human history that was never patented. It’s a paradox, but it’s true. In 1841, Joseph Whitworth proposed a standard for screw threads that would eventually become the foundation of global manufacturing. Luna: Right, because if every manufacturer used their own pitch and angle, the entire industrial revolution would have stalled out before it really began. You couldn't have a machine made in Manchester working with a part made in Manchester three streets over if they spoke different mechanical languages. Lucas: Exactly. And that is the core lesson here about productivity and economic growth. We often think of productivity as doing more with less labor, or faster software, or better algorithms. But sometimes, productivity is simply the reduction of friction in exchange. Whitworth’s standard reduced the friction of assembly so drastically that it allowed for mass production. He set the major diameter, the pitch, and the angle—fifty-five degrees—so that a nut from one factory could always fit a bolt from another. Luna: It’s interesting because that feels like something we take for granted now, but back then, it was actually quite chaotic. I remember reading that before standardization, engineers had to measure every single screw with calipers and file custom nuts to make them fit. That’s not just inefficient; it’s a massive barrier to entry for new manufacturers. Lucas: Precisely. And that barrier to entry is what economists call a transaction cost. When you have to spend time and money verifying compatibility before you can even start building, your capital is tied up in verification rather than creation. Whitworth realized that by giving away his standard, he wasn’t losing money; he was creating a market. He understood that the value wasn’t in the screw itself, but in the ecosystem of screws. Luna: So it’s almost like a network effect, but for physical objects. The more people who adopt the standard, the more valuable the standard becomes to everyone else. Lucas: That’s a great way to put it. But there’s a nuance here that often gets missed. A network effect usually implies that the technology improves or becomes smarter as more people join. With Whitworth, the technology didn’t change. What changed was the predictability. Predictability is the currency of long-term investment. If I know my parts will fit, I can invest in larger machines, larger warehouses, and larger workforces because I know the output will be usable. Luna: And without that predictability, you’re stuck in a local optimization loop where every solution is bespoke. You can’t scale bespoke solutions, no matter how efficient they are individually. Lucas: Right. So let’s look at the data point that really sticks with me. By the late nineteenth century, the Whitworth Standard had been adopted across much of Europe and the United States. This wasn’t just a British thing. It became the lingua franca of industry. And during that same period, we saw an explosion in the complexity of machinery. Steam engines, textile mills, railway systems—all of these relied on thousands of interchangeable fasteners. Without that standard, the complexity curve would have flattened. Luna: It makes me think about our current digital landscape. We have standards everywhere, but they’re often proprietary. Like charging ports or cloud APIs. Is there a risk that we’re regressing into a pre-Whitworth era of fragmentation? Lucas: That is a fantastic question, and it’s one that keeps a lot of economists up at night. We do see fragmentation in tech, particularly in enterprise software. Companies build walled gardens because they want to lock in customers. But the irony is that those walled gardens often reduce overall productivity because integration costs go through the roof. When two systems don’t talk to each other natively, you need middleware, you need manual data entry, you need reconciliation teams. Luna: Which is basically the modern equivalent of filing custom nuts. You’re spending all your resources making things fit instead of actually using them. Lucas: Spot on. And here is where it gets tricky for policymakers and business leaders today. Who sets the standard? In Whitworth’s time, it was a respected engineer who published his findings and invited critique. It was a bottom-up process driven by technical merit. Today, standards are often set by corporate behemoths or government bodies. Both can work, but both carry risks. Corporate standards might prioritize profit over interoperability. Government standards might move too slowly to keep pace with innovation. Luna: So the challenge isn’t just having a standard, but having a standard that evolves. The Whitworth standard worked for fifty years, but eventually, it ran into limits with higher precision needs, leading to the metric system and the Unified Thread Standard. Adaptability is key. Lucas: Yes, and that adaptability requires trust. Trust that the standard won’t change arbitrarily. Trust that the entity managing the standard is acting in the interest of the ecosystem, not just their own balance sheet. This is why open-source software models are so fascinating to economists. They mimic the Whitworth dynamic: a community agrees on a spec, and everyone benefits from the interoperability. Linux is essentially a giant, digital Whitworth standard for computing. Luna: I love that comparison. It’s funny to think of a kernel codebase as the successor to a British engineer’s screw gauge. But it holds up. The principle is the same: shared infrastructure enables specialized innovation. Lucas: Exactly. Let’s bring it back to the present day, October twenty-sixth, twenty-six. We are seeing a new wave of standards emerging in artificial intelligence and energy grids. The AI world is currently fragmented, with different models speaking different formats. It’s a bit like the pre-standardization era. But once a dominant format emerges—whether it’s for model weights or data pipelines—the productivity gains will be enormous. We’ll stop spending time converting data and start spending time analyzing it. Luna: And the energy grid is similar. With renewable energy coming from so many disparate sources, we need a standard interface to manage the flow. Otherwise, we’re trying to plug solar panels into coal plants and hoping the bolts match. Lucas: A perfect analogy. So, the takeaway for our listeners, whether you’re running a startup or a multinational corporation, is to ask yourself: where are we creating unnecessary friction? Are we building proprietary interfaces when open ones would serve us better? Are we measuring compatibility before we measure performance? Because in the end, speed doesn’t matter if you’re going the wrong way, and direction doesn’t matter if you’re broken down on the side of the road. Luna: Or if you’re trying to tighten a bolt with the wrong wrench. Which, honestly, happens to me at least once a month. Lucas: We’ve all been there. But thinking about that moment of frustration as a historical echo of the nineteenth century adds a whole new layer of appreciation for the simple screw. It’s a reminder that the biggest innovations are often the quietest ones. They don’t get headlines. They just make everything else work. Luna: Well said. And it’s a good reminder that efficiency isn’t just about moving faster; it’s about making sure we’re all speaking the same language. Lucas: Before we go, I want to mention something important about how this show operates. If walking through the economy with us has made something click, or if you appreciate the deep dives into topics like industrial history and standardization, your support directly keeps this content ad-free and independent. We rely on listeners who value long-form economic analysis to help sustain the work. Luna: Yeah, and if you want to contribute, you can find us at buy me a coffee dot com slash fexingo — that's F. E. X. I. N. G. O. Lucas: It’s a small gesture, but it makes a big difference in allowing us to cover these niche, high-signal topics without compromising on quality. Thank you for considering it. Luna: Absolutely. Now, back to the topic. Lucas: Let’s circle back to one last thought on Whitworth. He was also a keen observer of social dynamics. He believed that fair wages and good working conditions were essential for a productive workforce. He wasn’t just optimizing machines; he was optimizing society. There’s a parallel there for modern business leaders. You can have the best standards and protocols in the world, but if your team is burned out or misaligned, the system will fail. Luna: That’s a crucial point. Technical standards are only half the equation. Human alignment is the other half. You need both interoperable systems and interoperable people. Lucas: Exactly. So, as you leave today, check your own workflows. Look for the friction points. Are you dealing with bespoke problems that could be solved with standard ones? Are you talking past your colleagues because you’re using different definitions? Sometimes, the most productive thing you can do is stop building custom solutions and start agreeing on a common language. Luna: Agreed. And if that means throwing away your weirdly shaped wrenches and buying a standard set, well, that’s a win in my book. Lucas: There you have it. From the workshops of Victorian Britain to the boardrooms of today, the lesson remains the same: clarity creates value. Thanks for listening.