The Dieter Rams of Software: Who Shapes the Apps We Use Every Day

Picture this, it is 1981, and the legendary industrial designer Dieter Rams sits down and he formally writes out his ten principles of good design. Right, the famous ten principles. Exactly. But what is so striking about that moment isn't just the philosophy itself, it's that every Braun radio, every Vitzu shelving unit, every calculator that rolled off his production line was like a physical proof of those principles. You could literally hold his argument in your hand. Yeah, you felt it through the grain of the wood, the tactile precision of the buttons, the absolute deliberate silence of the motor. And because of that, designers today just will not stop arguing over one highly debated question, who is the Dieter Rams of software? That is the great debate in design circles. Right. And welcome to the Deep Dive. Today we have a massive stack of sources. We're looking at Don Norman's foundational texts, Apple and Google's internal guidelines, a five-year McKinsey study, all the way to the EU's Digital Services Act. That's a lot of ground to cover. It is, yeah. Yeah. But our mission is to answer that exact question. Who is the Rams of software? Well, the answer turns out to be nobody, which is actually the most interesting thing about it. Wait, nobody. Out of millions of apps and, you know, decades of tech history, there isn't a single person we can point to who holds that kind of authority. Not a single one. Because, I mean, asking for the Rams of software is basically a category error. How do you mean? Think about the medium itself. Software has no grain. It has no motor. It doesn't have material honesty. I mean, it updates while you sleep, and it runs A-B tests on you without your consent. Right. It's constantly shifting. Exactly. So it's a productively wrong question. Because when you realize why a lone auteur can't exist in software, it forces you to ask a much better question. Whose vocabulary do working designers actually use to make decisions? And we are going to trace exactly how that vocabulary replaced the individual genius today. Before we're done, we're going to look at a modern app called Linear. It's a project management tool that recently reached a $1.25 billion valuation. Which is staggering. It is. And do you know how much they spent on marketing to get there? About $35,000. Total. Wow. Yeah. We're going to explain exactly how they encoded design principles to make that happen. Because whether you're building products yourself or you're just using them, understanding who really shapes these digital experiences and how will completely change what you demand from your software. Absolutely. So if there is no single rams of software whose vocabulary are designers actually using, that brings us to Don Norman. Right. The godfather of UX. Basically, yeah. And what's crucial here is the historical shift he triggered. So imagine buying software in the early 1980s. If it confused you, well, the industry considered that your fault. Like you just didn't read the massive 400-page manual. Exactly. But then in 1988, Norman publishes The Design of Everyday Things. And after that book, if a user was confused, it became the designer's fault. He completely flipped the script. He really did. And he gave us the vocabulary we still use to diagnose the problem. Terms like affordance, which is a word he actually borrowed from a perceptual psychologist named James J. Gibson. Right. Gibson coined it originally. Yeah. And if you're wondering what an affordance is, it's just a property that communicates how something is meant to be used. A physical door handle affords pulling. A digital button affords pressing. And Norman paired that with signifiers. Right. Which are the visual cues that tell you an action is possible. Like underlining a word to show it's a clickable link. Those terms, along with the concept of user feedback, just became the operating language of entire discipline. Norman's real-world impact was immediate. I mean, he became Apple's first user experience architect. He literally coined the term user experience. Yeah. He created frameworks like the seven stages of action, which is a diagnostic tool to figure out exactly where a user gets stuck in a process. It's like Norman is the ultimate grammar teacher. Oh, that's a great way to put it. He didn't write the great American novel of software, but he invented the alphabet and the grammar rules everyone else uses to write their own stories. Dieter Rams required physical proximity to his products. You had to touch the Braun radio. Norman's influence propagated entirely through portable concepts. Right. Totally decoupled from any specific physical object. So if you're listening to this, try this out. Next time an app frustrates you, ask yourself, does this interface give me feedback? Can I form a mental model of how this works? Because you are already thinking in Don Norman's vocabulary. Yeah. Norman gave software design its grammar. But you know, grammar needs rules, and that's where things get pretty complicated. That's the foundation, the vocabulary and frameworks. Now let's look at what happens when influence outlasts its author. Okay. In 1994, a researcher named Jacob Nielsen published his 10 usability heuristics. It's essentially a checklist for evaluating an interface. And they are still canonical 30 years later. Yeah, they're everywhere. He also proved that testing an interface with just five users uncovers the vast majority of problems. Let me stop you there, because the five users thing always sounds like magic to people. Why five? Why not like 50? It's pure mathematical probability. Usability flaws aren't subjective opinions, they are systemic roadblocks. So if a digital door is completely fake, five people trying to open it will all bump their noses. Ah, I see. You get diminishing returns after five users because you just keep observing the exact same fundamental errors over and over. And by standardizing this, Nielsen showed that every dollar invested in usability returns 10 to $100 in value. Wait, but doesn't that cut both ways? I mean, if the heuristics are so general, they're unfalsifiable. Is that really a strength? What do you mean? Well, Nielsen has had some intense controversies recently, specifically his 2023 claims, where he basically said accessibility is doomed to create a substandard user experience. Right, that caused a huge uproar. Yeah. So if his heuristic list says nothing about accessibility, maybe the author's blind spots are e-baked into the framework. A framework reflects the values of its creator, doesn't it? I see what you're saying, but I actually see it differently. Yeah, the whole point is that the heuristics work whether you agree with Nielsen the person or not. That is the proof of their durability. A designer can use his framework to evaluate a site while completely rejecting his recent opinions. Fair point. But consider this. His heuristic list says nothing about accessibility. If he was wrong about accessibility, maybe the heuristics have accessibility blind spots baked in. That's exactly what I thought, too. Until I realized something. Practitioners have been extending and amending Nielsen's heuristics for decades. Oh, to include things like accessibility. Exactly. The framework invites amendment that's different from being fatally flawed. It proves the tool works independently of the author's personal, current opinions. The author just sort of dissolves into the medium. Okay, so the framework survives, but what about actual visuals? Because there are a few rare cases where visual artifacts survive, too. In 1984, Susan Kerr sat down with graph paper and designed the Macintosh icons. Oh yeah, the trash can. The trash can, the command key symbol, the Chicago typeface. Those icons are so influential that her trash can evolved into our universal delete gesture. Her original sketches literally live in MoMA now. True. But Kerr's work is kind of a historical anomaly. You think? Yeah, she could achieve that kind of singular lasting impact because early graphical user interfaces had incredibly low visual complexity. I mean, you had a few dozen pixels to work with. You simply cannot repeat that today. Right, interfaces are way too complex now. A better, modern equivalent of influence detaching from its creator is the digital gesture. Think of Lauren Brichter's 2009 Tweety app. Oh, the inventor of pull to refresh. That's the move every smartphone user makes like 20 times a day. Exactly. Anyway, he introduced a gesture so perfectly aligned with touch screen physics that it just felt inevitable. It perfectly mimicked pulling down a physical window shade, complete with that elastic resistance and that satisfying snap when it reloads. And he didn't even patent it, right? Nope. The gesture's meaning emerged from muscle memory, not from a manual. Nobody decreed it. It just became part of the digital infrastructure. Now, Nielsen, Kerr, and Brichter each proved the same pattern, that influence detaches from its creator. But something bigger replaced them all. The design systems. Yes, the quiet revolution. As software scaled, the individual auteur was completely eaten by the design system. Think about it. Imagine you are a developer building an iOS app today. You don't sit by a fire reading Dieter Rams' philosophy on minimalism. You open Apple's HIG, the Human Interface Guidelines. Right. Or if you're on Android, you open Google's Material Design, which was formalized in 2014. These aren't just like gentle suggestions, they are literal law for how software should look and behave. Yeah, they use what are called design tokens, right? Yes. Design tokens are the smallest reusable values like spacing and color compiled straight into the code. Google established a strict 48-pixel touch target for buttons. I always loved this detail. Why 48 pixels? Because 48 pixels on a standard mobile screen roughly translates to 9 millimeters, which is the exact average width of a human fingertip. Yeah, they literally coded human anatomy into the software's rules. Rams had this idea of being thorough down to the last detail. Well, in software, that thoroughness is automated. It's hard-coded. Des Traynor, the co-founder of Intercom, summed it up perfectly. He said, the closest thing we have to Rams is the iOS HIG plus material design combined with whatever Figma's default components enforce. It's taste as infrastructure. And the business case for this is massive. A five-year longitudinal study by McKinsey looked at 300 publicly listed companies. And what did they find? Their key finding was that companies with strong design commitment had 32 percent higher revenue and twice the industry benchmark growth. That is a huge margin. Now, I have to point out the crucial caveat here. This is correlation, not causation. Right. Important distinction. Well-resourced companies might just have the money to invest in both great design systems and other revenue drivers. But the signal is absolutely there. Good design correlates with massive scale. It does. But I know you have thoughts on this shift, like, is design a system actually better than design is genius? Hmm. Okay. But here's my concern. If taste becomes infrastructure, who's responsible when the infrastructure makes boring, safe choices? That's the trade-off. Systems optimize for consistency, not courage. They prevent bad decisions, sure, but they also prevent great ones. The most iconic products, like the original Mac, the first iPhone, came from strong individual vision, not from committee-driven component libraries. So you think we're losing something? Yeah. To reach users today, designers have to surrender their individual expression to ecosystem rules. We get the platform paradox. Millions of apps that all look exactly the same. I hear that. But the data actually supports systems over individuals for the simple reason of scale. Look at Airbnb. They created their Polaris design system, and it reportedly reduced production time by 35% while increasing user satisfaction. 35% is a massive time save. It is. Systems scale. Individual genius doesn't scale across thousands of engineers. If an auteur leaves a company, their vision often crumbles. When a design system is in place, the company's design language survives personnel changes. Okay. So design systems are the new authority. But is there anyone who's cracked the code on being a design auteur in software today? Is anyone doing it? Actually, yes. And that brings us to Linear. This is the app I teased earlier. The closest contemporary case study we have. It's a project management tool co-founded by Keri Sarinan. Let's revisit that signature stat. They achieved a $1.25 billion Series C valuation with only about $35,000 in total paid marketing. The product IS the argument. Exactly. And if you look at how they achieved that growth without marketing, it's intensely philosophical. Sarinan's approach centers on four commitments. First, speed as a core design value. Second, keyboard-first interaction like, you shouldn't need a mouse. Third, extreme craft and focus. And fourth, opinionated defaults. Opinionated defaults is the secret sauce there. Explain how that turns $35,000 into a billion. Well, by enforcing opinionated defaults, Linear doesn't give you a sandbox to build whatever workflow you want. They tell you, this is how you should work. It's called the Linear way. They force the workflow. By removing customization, they forced users to work faster. That speed created a cult-like word of mouth among developers. Their users literally became their marketing department. That is fascinating. It's Ramseyan, but not just because it's visually minimal. It's Ramseyan because it is normative. It actively reduces what practitioners call behavioral states. Right. In design vocabulary, this is known as principal density or friction as taste. They give you a highly-tuned engine, and they don't let you swap out the parts. And what's really telling is Surinan's background. He's the very first design systems lead at Airbnb. He worked on that Polaris system we just talked about. Oh, wow. The connection is right there. Yep. Influence in software travels like a craft. It moves through proximity to carriers, not through reading manifestos. He learned to systematize taste at Airbnb and then applied it as an individual founder to a new product. So linear is the aspirational case. It's what happens when everything goes right. But the cautionary tales are just as instructive. What happens when a strong design philosophy actively ignores Don Norman's usability grammar? It usually doesn't end well. Let's go to Apple, specifically the launch of iOS 7. Joni Ive takes over software design after Scott Forstall leaves, and Ive decides to strip away all the skeuomorphism. Let's define that real quick for everyone. Skeuomorphism is that design trend where digital interfaces mimic physical objects. So like, the podcast app had fake metallic reels. The notes app had fake yellow paper with leather stitching. Ive wanted pure, flat design, thin fonts, white space. And the usability cost of that was immense. Steve Aquino, an accessibility researcher, documented the tremendous damage this did to visually impaired users. Why? Just because the textures were gone? Because the affordance cues, the drop shadows, the gradients, the thick-buttoned borders that screamed, this is tappable, were completely removed. RAM's version of minimalism removed the extraneous. Ive's iOS 7 minimalism removed the functional. See, I actually think iOS 7 was the right move at the wrong fidelity. Yeah. The direction was correct. The execution was the problem. The skeuomorphic era was completely exhausted. Someone had to make the painful break. But that's exactly why process matters. If Ive had tested those flat designs with real users, instead of trusting his aesthetic instinct, he could have kept the direction without the accessibility damage. That's exactly what I thought too, until I considered the counterfactual. Would Apple have ever made that jump incrementally? Sometimes you need an overcorrection to escape a local maximum. Ive's radical reset created the design space that modern iOS lives in. And they quietly restored those functional cues in later updates anyway. Maybe. But try telling that to the users with visual impairments who suddenly couldn't navigate their phones for a year. Necessary reset doesn't feel so necessary when you're the one who can't use your device. Yeah, that's fair. And we saw this exact same trap play out again just recently with the humane AI pen in 2024. Oh, the AI pen. This is the perfect modern example. It really is. It was based on Mark Weiser's 1995 calm technology philosophy. The idea was to eliminate the screen entirely and inhabit the periphery of your consciousness. Which sounds amazing on paper. Right. Philosophically, it was the most Ramseyan physical concept we've seen in years. Yet it had zero affordances. You tapped it and it gave terrible feedback loops. You had no idea if it was thinking, broken or dead. It just didn't communicate. Exactly. Core 77 called its interaction model repeatedly unsuccessful. And by February 2025, just 14 months after launch, Humane shut down and sold to HP. Beautiful philosophy cannot save a product that ignores Norman's basic rules of feedback. Function before form. Feedback before philosophy. So from Ram's principles to single genius to distributed systems, what does this all add up to? Where is design authority shifting next? The answer is it's moving upwards into the literal law and into artificial intelligence. Let's start with the law. Dieter Rams' seventh principle was good design is honest. Today, honesty is legally enforceable. The EU's Digital Services Act, which became enforceable in 2024, explicitly bans what are called dark patterns. Right. Which is a term coined by researcher Harry Brignull back in 2010. Think of those deceptive interfaces that trick you into subscribing or make it impossible to find the cancel button using like guilt trip language. Oh, I hate those. No thanks. I prefer to pay full price. Exactly. The DSA explicitly states platforms shall not design interfaces in a way that deceives or manipulates. And in the US, the FTC announced a click to cancel rule. Ram's honest design principle is moving from public policy to a strict product requirement. And then there's AI, which is pushing human authority even further upstream. Think about tools like Figma's first draft or Vercel's V0. The human designer is no longer composing individual pixels or drawing boxes. They are writing the constraints. They are curating the outputs that the machine generates. So let's bring it all together. Rams' principles aren't obsolete. They are just decomposed across the entire stack. Innovative now lives in product teams. Useful lives in user research and Nielsen's heuristics. Aesthetic lives in corporate design systems. Understandable lives in Don Norman's vocabulary. And honest is increasingly living in government regulation. Remember that question we started with, who is the Dita Rams of software? It turns out the question IS the answer. How so? By showing us there's no single auteur, it reveals the real architecture of software design. It's a massive stack of decisions from regulators to platforms to design systems to product teams. The authority is very real. It's just not a person anymore. The medium changed the model. Which leaves us with a completely different way to look at the tools we use every day. Exactly. Next time you open an app that feels completely effortless or, you know, one that feels incredibly hostile, try to see the stack behind it. Whose design system is it built on? What platform guidelines constrained it? Does the interface give you feedback? Does it let you form a mental model? Those questions are Norman's legacy. And they're the most powerful tools you have as a user. And here is one final thought to mull over. If AI continues to shift our job from drawing interfaces to merely setting the constraints for machines that generate them on the fly, maybe the next Dita Rams won't be a designer at all. Maybe they will be a philosopher, writing the ethical code for the algorithms that design our world. If this deep dive changed how you think about design, share it with someone who builds products. That wraps this UDAM research deep dive. We'll see you next time.