101 Things I Learned® in Product Design School

We are taught that great design is about addition—adding a brilliant feature, a new material, or a revolutionary technology. We celebrate the complex, the multi-functional, the object that promises to do everything. Yet, the most iconic and beloved designs often achieve their power through subtraction. The elegance of a paperclip, the intuitive nature of a well-placed door handle, or the clarity of a simple road sign all speak to a different truth: the most difficult, and most valuable, act in design is strategically removing everything that is unnecessary. This process is a rigorous intellectual exercise. It’s about understanding that every element added to a design increases its cognitive load, demanding more from the user. The true genius lies in achieving the intended function with the absolute minimum of components, making the final product feel not designed at all, but simply… inevitable.

This disciplined pursuit of simplicity is precisely what Sung Jang, Martin Thaler, and Matthew Frederick sought to distill. As educators and practitioners in the world of design, they noticed a recurring gap between the complex theories taught in school and the elegant, often deceptively simple, principles that governed successful products in the real world. They saw students and young professionals drowning in a sea of abstract concepts, struggling to grasp the foundational truths that separate good design from great design. "101 Things I Learned® in Product Design School" was born from their collective effort to bridge this gap, to codify the essential, non-obvious lessons that often take a lifetime of practice to uncover. They created a collection of direct, illustrated insights—a series of focused revelations designed to re-wire how we see and create the world around us.

Module 1: The Foundation — Redefining the Problem

We often think design starts with a great idea. The authors argue it starts with a great problem. But not the one you're handed. The real work is finding the real problem. This module is all about the foundational mindset shift required before a single sketch is made.

The first step is to reframe the apparent problem to uncover the real problem. What looks like the issue is often just a symptom. For example, a client might ask you to design a better pooper-scooper. They believe the problem is that existing tools are ineffective. But after some research, you might discover the real issue. People aren't picking up after their dogs because they forget to bring bags on their walks. The apparent problem was the scooper. The real problem is bag availability. The solution might be a leash with a built-in bag dispenser. This shift from symptom to root cause is the first major leap toward an effective solution.

Once you start digging, you’ll find that a need is best understood through action. This leads to the next insight: a need is a verb. People don't fundamentally need a chair; they need to rest. They don't need a vase; they need to display flowers. This simple change in language is powerful. It frees you from the constraints of existing product categories. Focusing on the verb—the action or experience—opens up a much wider field for innovation. Instead of just making a better chair, you might design a standing desk that reduces fatigue, or a floor cushion that encourages active sitting. You're solving for the need, not just iterating on the object.

Building on that idea, it becomes clear that great design isn’t about inventing something from a vacuum. In fact, originality begins with competency. The book draws a parallel to learning a musical instrument or a sport. You don't start by composing a symphony. You start by playing scales. You copy the masters. You practice relentlessly. In design, this means studying, sketching, and even replicating successful products. This is about building a deep, intuitive understanding of form, function, and materials. True creativity—the ability to create something genuinely new and better—emerges from this foundation of mastery, not from a desperate search for a "unique" idea.

Finally, this foundational stage requires a crucial balance. The authors introduce Raymond Loewy's MAYA principle. It stands for Most Advanced Yet Acceptable. The core insight is to balance novelty with familiarity to encourage acceptance. If a product is too radical, users will reject it. It feels alien and untrustworthy. If it's too familiar, it's boring and offers no reason to switch. The sweet spot is a design that feels fresh but also reassuringly recognizable. The Nest thermostat is a perfect example. Its round shape was a direct nod to the classic Honeywell thermostat, a familiar archetype in homes for decades. This familiarity made its advanced learning technology feel accessible and safe, not intimidating. This balance is key to bridging the gap between a great idea and a successful product.

Module 2: The Process — From Idea to Insight

Once you've framed the right problem, how do you actually start solving it? This module dismantles the myth of the lone genius and reveals a messier, more collaborative, and far more effective process. It’s about moving, writing, and feeling your way to a solution.

Let's start with a common roadblock: the blank page. It's intimidating. The authors suggest that to overcome this, you have to make your ideas mobile for creative connections. Your brain is a powerful connection engine, but it works best when it can see all the pieces at once. Get your ideas out of your head and onto a wall. Use sketches, notes, images, and research findings. Pin them up. When ideas are physical and visible, you can literally move them around. You can cluster them, re-sequence them, and draw lines between them. This physical act of manipulation triggers new associations. It allows you and your team to see patterns and scenarios that would remain hidden in a linear document or a slide deck.

But here's the thing. While visual brainstorming is critical, another tool is often overlooked. The authors insist that you must use writing as a design thinking tool. Writing is a tool for forming thoughts. Force yourself to write a short design statement every week. Explain who the user is. Describe the problem you're solving. Articulate your proposed approach. This act of translating vague ideas into concrete sentences forces clarity. It exposes gaps in your logic. It helps you refine your understanding. When you get stuck later in the process, you can look back at these written statements. The evolution of your own thinking will often point the way forward.

This process of exploration requires a specific kind of mindset, one that moves from simple observation to profound understanding. The book makes a crucial distinction: you must distinguish observation, awareness, and insight.

• An observation is a simple, objective fact. "I see a user struggling to open a jar."
• An awareness is an observation that sticks with you. You sense it might be important. "I keep noticing people struggle with that jar."
• An insight is the breakthrough. It's a deep understanding that reframes everything. "Their grip strength isn't the problem. The universal, one-size-fits-all lid design fails to account for human variability."
  An insight organizes all the complexity into a simple, powerful truth. It’s the "aha" moment that transforms a project.

So what does this process feel like? It’s an iterative dance between two modes of thinking. The author suggests you must integrate "why" work and "how" work iteratively.

• "Why" work is conceptual and strategic. Why are we building this? Who is it for? What value does it create? This is the fuzzy, front-end exploration.
• "How" work is technical and executional. How will we build it? What materials will we use? How does the mechanism work?
  Inexperienced designers try to do all the "why" work first, then hand it off to the "how" team. This is a recipe for failure. The reality is that these two modes must constantly inform each other. While exploring the "why," you might have a technical idea. You should briefly switch to the "how" to test its feasibility, then return to the "why." This constant back-and-forth ensures the final product is both conceptually sound and technically viable.