Quick orientation

Scott Hurff’s “Designing Products People Love: How Great Designers Create Successful Products” serves as a practical guide for anyone involved in the creation of digital products. The book’s core purpose is to demystify the product design process, emphasizing that successful products are not happy accidents but the result of understanding customer needs, diligent research, and iterative design. It’s relevant for designers, product managers, entrepreneurs, and startup teams aiming to build products that resonate with users and achieve market success.

This summary will walk you through the essential insights and actionable advice from each chapter, presented in a clear and easy-to-understand format. You’ll learn about the historical foundations of product design, modern techniques for discovering customer pain points, and the mechanics and psychology behind crafting engaging user experiences.

Preface

The preface sets the stage by asserting that products are for customers, and ultimately, designing a product means designing something that sells. Hurff shares his own experiences with a failed startup, which fueled his desire to understand how the best products are made, leading him to study successful product designers and historical precedents.

This book is for you

Hurff explains that the book is for anyone wanting to improve at creating digital products, from solo entrepreneurs to members of large organizations.

• Learn from experience: The book synthesizes insights from over 30 product leaders and historical product creation.
• Repeatable processes: It aims to uncover the repeatable processes and strategies used by successful designers.
• Address common challenges: It targets issues like launching products to no customers, last-minute project changes, and customer confusion.
• Key takeaways: Readers will understand how great products are made, learn to discover customer pain, design interfaces across form factors, and utilize psychology for engaging experiences.
• Not a novel invention: The book focuses on how real work is done by those who’ve applied various models and methods.

What’s in the book

The book’s structure is based on a four-step product creation model, designed to guide readers through the messy process of building a product.

• Product creation model: The model consists of: Hunt and synthesize; Build; Test and level up; Launch, monitor, and start over.
• Hunt and synthesize: This phase focuses on understanding customer pain and joy through research, tracing product design origins, and rallying a team around a clear vision.
• Build: This involves writing the interface first, creating user flows, prototyping, and designing the mechanics and psychology of the interface.
• Test and level up: This phase is about refining the product through feedback from various sources, including team critiques and customer input.
• Launch, monitor, and start over: This covers knowing when to ship, preparing for launch, being the “chief of everything,” and monitoring post-launch.
• Practical structure: Each chapter includes a recap, a “Do This Now” section for immediate application, and interviews with experienced product designers.

The preface emphasizes that the book provides frameworks and principles, not a rigid recipe, to help readers design products that truly connect with people.

1. Why products exist

This chapter delves into the definition of product design and its historical roots, arguing that understanding the past is crucial for designing the future. It highlights that successful product design has always been about deeply understanding and serving the customer.

What’s product design?

The chapter opens by exploring the varied definitions of product design from several industry leaders, underscoring its multifaceted nature.

• Broad knowledge: Product designers often possess a wide range of skills, understanding the entire process of bringing a product to life (Josh Brewer).
• Friction removal: It’s about identifying and removing steps that cause friction for users trying to complete a task (Nathan Kontny).
• Comprehensive view: Product design involves crafting an experience and solution to meet a specific need, incorporating user psychology (Ryan Hoover).
• Understanding people: It’s fundamentally about empathy and challenging one’s own assumptions about the world (Keenan Cummings).
• Problem-solving: It focuses on identifying a problem and finding the best way to solve it, much like designing a functional cup (Sahil Lavingia).
• Synthesis of methodologies: Product design is not a single job but a combination of different approaches and skills.

Product design’s heritage

Hurff argues that current challenges in digital product design are not new and can be informed by studying pioneers from the 20th century.

• Lillian and Frank Gilbreth: They revolutionized industries through “motion studies,” observing workers (and later, home kitchen users) to improve efficiency and ergonomics. Lillian’s work led to the modern kitchen layout.
• Henry Dreyfuss: Considered a founding father of human-centered design, Dreyfuss emphasized designing for people’s habits, physical dimensions, and psychological impulses, believing good design improved profits.
• Neil McElroy: As a manager at P&G, he invented the “brand man” (brand manager) concept in 1931, a person responsible for guiding a product to success through field research and data analysis.
• Scott Cook: Founder of Intuit, Cook brought McElroy’s brand manager principles to technology, emphasizing firsthand customer observation through programs like “Follow Me Home” for Quicken.
• History’s lesson: These figures relied on painstaking, firsthand observation and deep understanding of their audience, a practice rooted in ethnography.

Upgrading ethnography for a digital era

The chapter discusses how ethnographic principles – observing people in their natural context – are being adapted for the digital age.

• Hoy and Hillman’s approach: They advocate for “net ethnography,” observing online communities to understand customer needs without bias.
• Dropbox: Drew Houston’s initial success with Dropbox wasn’t just luck; he understood his target online audience, used their language, and addressed their specific file-syncing pain points in his demo video.
• Apple: Despite Steve Jobs’ “no market research” stance, Apple excels by observing how people use technology and imagining life-changing solutions, as seen with Time Machine, the original iPhone, and the iPhone 6/6 Plus catering to demand for larger screens.
• Product Hunt: Ryan Hoover created Product Hunt by observing a need within the tech community for a centralized place to discover and discuss new products, initially starting it as a simple email list for his network.
• Core principle: Successful products start with observing what real people do, not what you think they do.

This chapter establishes that the foundation of great product design lies in a deep, empathetic understanding of the customer, a principle that has remained constant despite technological advancements.

2. How to create products people want

This chapter focuses on practical methods for uncovering customer needs and avoiding common pitfalls like “ego-first development.” It introduces Sales Safari as a modern ethnographic technique and the Pain Matrix for visualizing research data.

Avoiding “ego-first development”

Hurff, drawing from Amy Hoy and Alex Hillman’s 30×500 bootcamp, critiques the common tendency to build products based on the creator’s desires rather than customer needs.

• The fallacy: “Ego-first development” is thinking an idea is special just because it’s yours, leading to a cycle of building and failing.
• Customer-centricity: The purpose of an enterprise is to create a customer; thus, products should solve customer problems.
• Lean startup critique: The chapter challenges the “Build-Measure-Learn” loop if it relies solely on asking customers what they want, as people often can’t articulate their true needs or predict their behavior.
• Observation over interviews: Observing customers in their “natural habitat” (like lions on a safari vs. in a zoo) yields more reliable insights than direct interviews.

Find product ideas with Sales Safari

Sales Safari, invented by Amy Hoy, is presented as a “net ethnography” technique to discover product ideas by observing potential customers online.

• Online observation: This method leverages online forums, mailing lists, and social media for easy access, speed, reliable records, and unbiased observation.
• Avoiding the “Margaret Mead problem”: By observing without direct interaction, Sales Safari avoids influencing subjects or taking their self-reported information at face value.
• Rooting out pain: The goal is to identify customer pains, as people are more likely to seek solutions for problems they actively experience.
• Close reading at scale: It involves analyzing large amounts of online discussions to identify patterns in jargon, worldviews, recommendations, and problems.
• Pattern recognition: This extensive data collection helps uncover recurring problems and the language customers use to describe them, leading to product ideas.
• Systematic approach: Sales Safari provides a repeatable system for gathering and analyzing customer data to generate product ideas.

Plot the pain

To make sense of the data gathered from Sales Safari, Hurff introduces the Pain Matrix, a tool he invented.

• Pain Matrix axes: The horizontal axis tracks pain intensity (low to high), and the vertical axis tracks pain frequency (low to high).
• Four quadrants:
  • Upper right (frequent, intense pain): Ideal target for products bringing significant relief or joy (e.g., hate, fear, anxiety).
  • Lower right (infrequent, intense pain): Nice-to-have products addressing less common but strong pains (e.g., procrastination, guilt).
  • Upper left (frequent, little pain): Products addressing minor, recurring irritations (e.g., administrative tasks).
  • Lower left (infrequent, little pain): Low-opportunity product ideas.
• Visualization: This tool helps visualize research data, focusing product ideas on the most significant customer pains.

What does a product designer do?

The chapter concludes by revisiting the role of a product designer, emphasizing that it’s a synthesis of many disciplines, all centered on understanding and serving the customer.

• Not just aesthetics: Product design is more than creating beautiful interfaces; it’s about solving problems effectively.
• Merging roles: A product designer often embodies skills of an entrepreneur, product manager, interaction designer, visual designer, motion designer, prototyper, data analyst, user researcher, psychologist, copywriter, project manager, product marketer, and customer support representative.
• Audience first: All design decisions, including visuals, should flow from a deep understanding of the audience and their needs.
• Specialization: While encompassing many skills, product designers often specialize, much like characters in an RPG “leveling up” specific abilities.

This chapter champions a research-driven approach to product ideation, ensuring that what gets built is rooted in genuine customer needs rather than assumptions.

3. What are we building here?

This chapter addresses the crucial phase of defining what product to build, emphasizing the importance of small, focused teams, clear communication, and customer-centric decision-making processes.

Defining what to build

The chapter starts by highlighting that successful product teams are often surprisingly small, referencing examples like Apple’s iMovie/iPhoto teams and early Instagram.

• Two-pizza teams: Jeff Bezos’s concept that a team shouldn’t be larger than what two pizzas can feed (around six people) is introduced.
• Process problems: Larger teams face exponentially more communication links (Hackman’s research), leading to inefficiencies.
• Overconfidence in larger teams: Studies show larger teams tend to underestimate task completion time despite often taking longer (e.g., LEGO building experiment).
• Who’s in the room: The core team should include the product designer/manager, key engineers (frontend/backend), and a representative from marketing/PR.
• Informed participation: Everyone involved must be intimately familiar with the customer research and pain points identified.

Party like it’s 1991

Regis McKenna’s 1991 vision of a new role – an “integrator” synthesizing technological capability with market needs – is likened to the modern product designer.

• Product designer as integrator: You are the customer’s champion, leading the team through research and proposing solutions.
• Team strengths: Leverage the team’s unique capabilities to apply innovative technology and design to the customer’s problem.
• Trust the team: Josh Elman’s insight emphasizes trusting the team’s expertise in what can be built and designed.
• Pain Matrix as a guide: Use the Pain Matrix (from Chapter 2) as a communication device to keep discussions focused on observed customer pains.
• Human motivations: Diogenes Brito’s reminder that designing around basic human desires (Maslow’s hierarchy) leads to more timeless solutions.
• Avoid “MVP” for validation alone: Don’t just throw out a minimum viable product to validate assumptions; build on a foundation of real, observed needs.

Keeping everybody focused

The chapter suggests techniques to maintain focus and foster healthy debate during product definition meetings.

• Whiteboarding: Use whiteboards for idea collection because it’s hard to remember all spoken ideas, allows for visual expression, and helps detach ideas from individuals, letting the best ones surface.
• The Cauldron (Apple technique): This method, used at Apple, allowed ideas to be discussed without worrying about ownership, letting good ideas rise and bad ones sink.
• Timed techniques (Medium example): Jason Stirman described Medium’s process of timed brainstorming (e.g., 2 minutes to write ideas, 5 minutes to present) to generate a high volume of ideas quickly.

The “working backwards” approach

Amazon’s “Working Backwards” technique is presented as a powerful method for clarifying product vision.

• Future press release: The product owner writes a future press release, fake customer quotes, FAQs, and a customer experience story before building.
• Involve all stakeholders: This process includes input from product, engineering, marketing, sales, and support, forcing a holistic view.
• Documents involved: The core documents are the press release, FAQ, customer experience definition (with mockups), and user manual.
• Clarity of thought: The goal is to flesh out the concept and achieve clarity before committing to building.
• Low-cost iteration: Iterating on a press release is cheaper than iterating on a built product. If the benefits aren’t compelling in the release, they likely won’t be in the product.
• Press release structure: Includes heading, subheading, summary, problem, solution, spokesperson quote, how to get started, customer quote, and call to action.

Create a product guide

Leaving the definition meeting with a tangible document is crucial for maintaining focus and accountability.

• Key elements (Cap Watkins’s approach): The product guide should outline: What you’re doing, why you’re doing it (problems solved), and what success looks like (quantitatively and qualitatively).
• Prevent design creep: If a feature doesn’t solve the problem or meet goals, it doesn’t go into the current version.
• DRI (Directly Responsible Individual): Apple’s rule of assigning a DRI to every task ensures accountability. Include DRIs in the product guide.
• Deadlines: Assign deadlines to every task to maintain momentum.
• Accountability and cadence: Intercom’s weekly goals or AngelList’s daily/weekly execution focus are examples of maintaining pace. Tinder’s frequent product update meetings also serve this purpose.

This chapter provides a roadmap for transforming customer research into a focused product definition, ready for the design and development process.

4. User interfaces begin with words

This chapter champions the idea that effective user interface (UI) design starts not with visuals, but with carefully crafted words and well-thought-out user flows. It emphasizes clarity, context, and consistency in interface copy.

Really? Start with words?

Drawing on the wisdom of Jef Raskin (creator of the Macintosh project at Apple), the chapter argues that the interface is the product from the customer’s perspective, and its foundation is language.

• Raskin’s principle: Start UI implementation by listing exactly what the user will do and how the system will respond – essentially, write the interaction.
• Foundation in research: This stage builds on knowing your audience, their tasks, and your team’s capabilities.
• Time-saving: Writing the interface first is quick, allowing easy iteration on flows and concepts without the overhead of visual design tools.
• Focus on productivity: It keeps the focus on customer goals, not on fonts or UI conventions.
• Words as building blocks: Interfaces are task-driven sets of words and symbols. Good copywriting vastly improves product design.
• UI as conversation: Jason Zimdars (Basecamp) suggests treating UI design as a conversation, asking “How would I tell a friend what they can do here?”
• Three key steps: 1. Map interaction sequences (flows). 2. List required components for each screen. 3. Write the actual copy (no Lorem Ipsum).

Creating user flows

User flows map the sequences of interactions a customer will use to complete tasks. They are essential because tasks rarely happen on a single screen.

• Storytelling analogy: J.K. Rowling’s meticulous plot spreadsheets for Harry Potter are an example of planning complex narratives, similar to mapping user flows. This low-overhead planning allows for easy changes.
• Smooth and logical: Great products have smooth, logical user flows. Mapping helps identify interaction types needed (e.g., single screen vs. pop-up, forms, confirmations).
• Exposing details: Flows reveal starting points, customer assumptions, decision points, data needs (input and output), and error/success paths.
• Team collaboration: Sharing flows keeps the team aware and allows for adjustments.
• Focus on the essence: Start by mapping the most essential flows (epicenter design), then orient secondary functionality around them.
• Troutman’s TextEdit method: Jon Troutman (Canary) maps flows in a text editor to focus solely on content and purpose, avoiding visual distractions. This linear approach helps prioritize content.
• Friedson’s flowchart method: Katelyn Friedson (Care.com) used flowcharts to communicate general flows with designers and engineers, allowing developers to start thinking about backend requirements early.
• Brito’s mind-mapping: Diogenes Brito (LinkedIn) uses notebooks for mind-mapping requirements, related problems, and information architecture.

Writing your screens

Once flows are mapped, the specifics of each screen’s content must be written. This is where much of the meaningful UI work happens.

• Context matters: Successful screens are aware of preceding and succeeding screens.
• Embrace “shit drafts”: Don’t fear imperfection in the first attempt (Hemingway’s adage). List everything that could be on the screen.
• Stream-of-consciousness listing: Include user info, common connections, media, core/secondary actions – anything relevant to the screen’s purpose.
• Reality check: After listing, assess data loading, client constraints (desktop, mobile), and essential elements for the ideal state.
• Dorsey’s Twitter sketch: Jack Dorsey’s early sketch of Twitter identified core components that remain today, showing the power of focusing on the product’s use case.
• Eliminate bad ideas early: Writing and drawing out the interface before pixel-perfect design weeds out bad ideas with minimal investment.

Traits of good interface copy

The words used in an interface set the product’s tone and are foundational. Jon Troutman emphasizes writing actual content, not placeholders.

• Who’s the audience?: Tailor language to the user’s familiarity with the product and their context. Use customer jargon where appropriate, but avoid internal terms.
• In what tone is it written?: Copy should be helpful, forgiving, and aware of whether it’s delivering good or bad news. The tone should match the audience (e.g., stockbrokers vs. teenage girls).
• What’s the context?: Content should be relevant to the user’s current location (landing page, signup, settings, etc.) and help them decide the next action. Be clear and concise, like a newspaper editor.
• Are you being consistent?: Use consistent labels and commands throughout the product (e.g., “Log In” vs. “Sign In”). Buttons should reflect the action they perform (e.g., “Send Message” not just “Submit”). Be mindful of regional differences (zip code vs. postal code, date formats).

This chapter stresses that by focusing on words and flows first, designers lay a strong, user-centric foundation for the visual and interactive aspects of the product.

5. Tangible trumps theoretical

This chapter champions the power of prototyping as an essential tool for communication, iteration, and decision-making in product design. It argues that making ideas tangible early on saves time, improves quality, and fosters collaboration.

Prototypes: worth 1,000 mockups

The chapter opens with George Lucas’s use of “videomatics” (spliced-together film clips and crude animation) to pre-visualize complex Star Wars dogfight sequences. This early form of prototyping allowed him to refine scenes before costly filming.

• Lucas’s method: He created rough cuts to define shots, timing, and overall feel, essentially prototyping scenes. This evolved into digital pre-visualization.
• Parallels to product design: Lucas’s one-page scripts are like user flows/screen-writing, and his rough storyboards/video sequences are akin to product prototypes.
• Externalization: Prototyping gets ideas out of your head and into a form that can be experienced by the team, clients, and potential customers.
• Working quickly: The goal is to get something working as quickly as possible, where “working” depends on fidelity, timeframe, audience, and tool comfort.
• Not pixel perfection: Early prototypes don’t need to be perfect; they need to be functional enough to test assumptions and feel like a real product (Kyle Bragger).

Bigger than a buzzword

Prototyping is more than a trend; it’s a fundamental communication method with practical benefits.

• IDEO’s adage: “If a picture is worth a thousand words, then a prototype is worth a thousand meetings.”
• Democratization of tools: Tools like InVision (simple, no-code), Keynote/PowerPoint (for animations), and more advanced options like Facebook’s Origami, Pixate, Google Form, and Framer.js are making prototyping accessible. Apple also has internal tools like “Mica.”
• Benefits: Prototyping brings teams closer, speeds up decisions, and makes end users happier.
• Skepticism overcome: Hurff shares his initial skepticism, then highlights insights from prototyping veterans Steve Meszaros (Wildcard) and Pauly Ting.

Goals of prototyping

Prototypes serve multiple purposes, primarily to test, prove, or conceptualize ideas within constraints.

• Focus and conciseness: Prototyping helps cut out fluff and feature creep by focusing on specific use cases or workflows.
• Articulating ideas: They allow designers to articulate complex interaction and animation ideas clearly (Steve Meszaros).
• Not for entire products: Prototypes are for bite-sized interaction pieces or specific workflows, not the entire product at once.
• Audience-specific fidelity: The level of polish depends on who will see it (team members vs. stakeholders vs. users) and the time constraints.
• Time well spent (or not): Paul Stamatiou (Twitter) notes that prototyping is valuable for big questions but can be a time-waster if overdone for minor details.
• Storytelling tool: Prototypes tell a story, helping to sell one flow over another and emotionally connect users to the experience, even if it’s “faked.”
• Early Twitter example: An early, unstyled Twitter prototype (text box, submit button, list of updates) allowed the team to test core functionality without visual polish.
• Cross-organizational buy-in: Prototypes become a common language understood by everyone, fostering collaboration.
• Typical timeframe: The prototyping loop (create, test, iterate, ready for implementation) can take about a week, sometimes two, or even a single day for small teams.
• Equalizer: Prototyping encourages multidisciplinary understanding and collaboration (Pauly Ting).

Readying for consumption

Once vetted, prototypes must be prepared for engineers to implement.

• Connective tissue: Prototypes bridge design and engineering by communicating interaction logic, timing, speed, and other specifics.
• Increasing fidelity: Each iteration increases the product’s fidelity, getting it closer to realization.
• Handoff: Share code from tools like Framer.js, Xcode storyboards, or Origami compositions. Provide specific values for transitions and animations.
• Micro-builds: This process allows for quick testing of features on actual devices.
• Benefits: Unifies teams, builds excitement, improves decision-making, and ultimately makes designers more productive and creative.
• Iterative feedback: Prototypes allow for real-time design changes during discussions, saving significant time (Pauly Ting).

This chapter makes a strong case for integrating prototyping deeply into the design process, transforming abstract ideas into testable, communicable, and refinable experiences.

6. The mechanics of interface design

This chapter dives into the practical aspects of crafting user interfaces, moving from prototypes to more polished designs. It covers the importance of pixel perfection at the right stage, the five states of any interface (the UI Stack), ergonomic considerations for touchscreens, and principles for cross-platform design.

The push and pull of prototypes versus pixel perfection

The chapter opens with an analogy of sculptor François Pompon, who would sculpt animals with full detail and then gradually eliminate the unnecessary to reveal the subject’s essential form. Similarly, product designers gather information, iterate, and refine.

• Increasing fidelity: The design process moves from rough ideas (copy, flows, prototypes) towards a shippable product.
• Avoiding premature perfection: Many designers jump into pixel-perfect mockups too soon, before the direction is clear.
• The “hero” version: Eventually, pixel-perfect mockups are needed as the ultimate communicator, integrable into prototypes and serving as a guide for engineers.
• Apple’s “10 to 3 to 1” approach: Designers create 10 different high-fidelity mocks, narrow to 3, then combine the best ideas into 1 final version, balancing creativity with production.
• Challenges of pixel perfection: Time consumption, multiple screen sizes, platforms, orientations, ergonomics, and interface states make it complex.

The UI Stack: five states of interface design

To avoid “awkward UI” (lifeless interfaces, missing indicators, jarring transitions), designers must consider the multiple personalities or “states” of every screen.

• Awkward UI example: Apple TV’s “Purchased movies” screen lacking a loading indicator, causing momentary fear.
• Computers are lazy: They don’t naturally provide human-friendly feedback.
• The UI Stack: Every screen can have up to five states: Ideal, Empty (including first-time use, user-cleared data, no results), Error, Partial, and Loading. These states transition smoothly.
• Evolution of Basecamp’s “Three State Solution”: The UI Stack expands on this earlier concept to account for modern interface complexities.

What’s the UI Stack?

A detailed look at each of the five states:

• Ideal state: The first state to design, representing the product at its maximum value, full of useful content. It sets the tone for other states (e.g., Skype Qik’s group list, Tinder’s potential matches, Starbucks app’s card balances).
• Empty state: Crucial for first impressions, encouraging action and demonstrating value.
  • First-time use/onboarding: Guides new users, like a “hero’s journey.” Examples: Hipchat’s direct instructions, Facebook Paper’s gesture tutorial, Basecamp’s placeholder content, Airbnb’s Wish List prompt. Avoid overwhelming coach marks.
  • User-cleared data: Rewards users for engagement (e.g., “Inbox Zero” in Mailbox).
  • No results: Offers helpful suggestions instead of a dead end (e.g., Amazon’s smart search corrections, Pinterest’s categorized “no results”).
• Error state: Handles things going wrong (missing data, connection issues). Should be comforting, preserve user input (Raskin’s “first law of interface design”), and avoid destructive reloads.
  • Good error messages: Constructive, clear, positive, specific, timely, grammatically correct, and offer resolution paths (e.g., Basecamp’s friendly signup error). Avoid vague codes like Microsoft’s “Blue Screen of Death.”
• Partial state: The screen is no longer empty but sparsely populated. Aims to prevent discouragement and guide users toward the ideal state.
  • Micro-interactions and acceleration: Use game design principles like “acceleration flow” to motivate completion (e.g., LinkedIn’s Profile Completeness bar, Dropbox’s storage reward steps, Apple Watch’s activity circles).
• Loading state: Manages expectations when fetching data. Perception of loading is key.
  • Skeleton screens (Luke Wroblewski): Display the page structure and gradually fill content, focusing on progress rather than waiting (used by Polar, Pinterest, Facebook).
  • Optimistic actions (Instagram): Assume success for actions like “liking” or commenting, performing server requests in the background to make the app feel faster.

A hypothetical example

An illustration of the UI Stack using a messaging app:

• Transitions: The app moves from an empty state (no messages, prompt to send) to a partial state (one message sent).
• Loading indicators: A typing indicator shows an incoming message (loading state). Sending a message involves UI changes (Send button enabling), a sending spinner (loading), and a delivery confirmation.
• Error handling: A failed send shows an error (red marker), with an option to retry, which then transitions back through loading to success.

Ergonomics: thumb zones and tap targets

With touchscreens now ubiquitous (even for babies!), designing for how people physically interact with devices is critical.

• Hoober’s research: Most people use phones one-handed (49%), often with the right thumb (67%). Grip changes subconsciously based on interface demands.
• Screen size trends: Smaller screens are declining; larger screens (4.7″+) are common. This necessitates designing for thumbs.
• The Thumb Zone: A heat map showing ease of reach for thumbs, typically anchored in the lower-right. “Safe” (green), “Natural” (yellow/orange), and “Ow” (red) zones.
• Impact of screen size: Larger screens increase “Ow” space; our thumbs don’t scale. The grip itself changes on very large phones (e.g., 5.5″).
• Choking up: Shifting grip mid-phone changes the Thumb Zone, sometimes making larger screens more accessible in certain areas.
• Thumb-friendly interfaces: Examples like Airbnb and Tinder place primary controls at the bottom, within easy thumb reach, and utilize comfortable swipe gestures.

Cross-platform design

With more mobile-connected devices than people, and diverse individual device usage patterns, consistent yet platform-aware design is key. Benedikt Lehnert (Wunderlist) offers insights.

• What do your customers need and expect?: The core task and feel of the product should be consistent (e.g., Wunderlist helps “get stuff done”). Values like speed, clarity, simplicity, and humanity shape decisions.
• What’s specific to the platform?: Respect platform paradigms (e.g., Android’s bottom controls vs. iOS’s home button). However, know when to break guidelines to ensure core product consistency or offer a better solution (e.g., Loren Brichter’s pull-to-refresh in Tweetie).
• What are the use cases for each device?: The product version should adapt to the device’s context (e.g., Wunderlist on Apple Watch is stripped-down and contextual, not a full-fledged app).

This chapter provides a robust framework for translating user flows and prototypes into well-considered, usable, and ergonomically sound interfaces across various platforms.

7. The psychology of an experience

This chapter explores the subtle psychological factors that influence how users perceive and interact with products. It covers aspects like speed, behavioral triggers, aesthetics, personality, and motion, arguing that these elements, when applied thoughtfully, can create habit-forming and emotionally engaging experiences.

Products and psychology

The chapter opens with a story from the TV show Halt and Catch Fire, referencing the “Doherty threshold” – the idea that system response times under 400 milliseconds can make a computer addictive.

• Doherty threshold: IBM research in 1982 showed that rapid response times (under 400ms) significantly increase productivity and user engagement.
• Context matters: Optimal speed varies; 400ms is too slow for touch drawing interfaces, where 1ms latency feels like pen on paper (Microsoft Research).
• Speed impacts behavior: Google found that slower search results (30 vs. 10 results per page) led to 20% fewer searches. Shopzilla saw revenue and pageview increases with faster page loads.
• Beyond functionality: Transitions, animations, personality, positive reinforcement, feedback loops, and even sound contribute to a product’s psychological impact. These are modifiers to the underlying value.
• Sweat the details: Jonathan Badeen (Tinder) emphasizes that software should not only be efficient but also delightful, with interactions feeling natural.

Loops

Product loops are designed to guide customers through specific flows, often to encourage engagement, activation, or retention.

• Real-life loop example: A banquet hall’s furniture storage guide (a visual template) made cleanup fast and easy.
• Fogg Behavioral Model (B=mat): For a behavior to occur, three factors must converge: Motivation, Ability, and a proper Trigger.
  • Motivation: Can be sensation (pleasure/pain), anticipation (hope/fear), or belonging (social acceptance/rejection).
  • Ability (Simplicity): Making a behavior easier to perform increases ability. Avoid forcing users to learn complex new things.
  • Trigger: A simple cue that prompts the desired behavior at the right moment.
• Planting the right seed: BJ Fogg’s metaphor emphasizes choosing a tiny, well-sequenced behavior that will grow naturally without excessive coaxing.
• LinkedIn Groups trigger: A subtle animation in the sidebar after joining a group, which changes on hover, is an example of a gentle trigger.

Additive actions

Introducing new features requires notifying customers at the correct time and demonstrating value to encourage use.

• Apple Music’s “love” icon: Initially, this feature lacked a clear trigger or explanation of its value. A better approach would be to prompt after observing user behavior (e.g., playing a song multiple times).
• Snapchat’s “Add to Your Story”: This dialog appears during the snap-sending flow, clearly explaining the feature’s benefit and making it easy to adopt.
• Twitter Video & Apple Emoji: Twitter used an unobtrusive tooltip for its video feature. Apple used a more direct (but educational) full-keyboard takeover to introduce new emoji skin tones.

Giving value, then asking for feedback

Products that deliver ongoing value can effectively solicit feedback at opportune moments.

• Instacart’s feedback loop: Uses text messages for order updates (keeping users engaged) and then requests a rating via text 5-10 minutes after delivery, allowing time for unpacking. The friction is low (reply with a number).
• Uber’s rating system: Prompts for a driver rating when the app is next opened after a ride. Hurff critiques the timing, as it might be long after the ride.
• DoorDash’s superior loop: Provides step-by-step push notifications, building anticipation. Asks for a rating shortly after delivery, then often offers a time-sensitive coupon, encouraging repeat orders.

Variable rewards

Variable-ratio schedules, where reinforcement is unpredictable, are highly effective at conditioning behavior.

• Slot machine analogy: The unpredictable nature of winning keeps users playing.
• Tinder’s “It’s a Match!”: The swipe gesture is easy, but the unpredictable “match” screen provides a dopamine rush, encouraging continued swiping. This was intentionally designed to be light-hearted and playful.
• Unexpected channels: Warby Parker’s personalized thank-you video and Product Hunt’s handwritten notes are examples of creating emotional connections through surprising, positive interactions.

Aesthetics and personality

Visual appeal and a product’s “character” significantly impact trust, usability, and emotional connection.

• Trust and appeal: Attractive interfaces are perceived as more usable and credible (hotel room analogy).
• Emotional impact: Pleasant aesthetics stimulate pleasure centers, influencing the user experience.
• Cockney Cash Machine: An ATM in East London offering a Cockney language option endears itself to locals while fulfilling its function.
• Building relationships: Aesthetics and personality help build a lasting relationship with users, not just a one-time transaction (Jeffrey Kalmikoff).
• Matching mood to product:
  • Airbnb: Warm, trustworthy design using clear typography, ample whitespace, and high-quality imagery.
  • Tinder: Playful, game-like design with bright colors and physical-feeling card manipulation to reduce the intimidation of meeting people.
  • USAA Bank: Exudes security and military values (service, honor) through hard corners, a blue/red/white palette, and no-nonsense navigation.
  • Uber: Embodies luxury and efficiency with a minimalist black interface that focuses on the core function of summoning a car.
  • Eat24: Uses humor and directness in copywriting throughout the app and marketing (e.g., witty coupon emails, funny empty cart dialogs).

Animation and motion

Motion makes interfaces more humanizing, understandable, and memorable by reflecting real-world physics and guiding attention.

• The “in-between states”: Designers are responsible for the transitions between screens, not just the static screens themselves (Paul Stamatiou, Josh Brewer).
• Motion tells a story: Animations explain how elements appear/disappear or how users navigate between screens, stirring emotion (Jonathan Badeen). Tinder’s card-to-profile animation visually connects the two views.
• Making space: Pasquale D’Silva’s example of a list making room for a new item, mimicking real-life stacking, feels more natural.
• Disney’s 12 principles of animation: These principles, like “slow in and slow out” and “staging,” aim to create believable, expressive motion.
  • Slow in, slow out (easing): Simulates real-world acceleration/deceleration, making movements softer and more natural. Skype Qik’s menu and Keezy’s menu (with “follow through and overlap”) are examples.
  • Staging: Directs the audience’s attention to the most important elements. For UI, this means concise animations and focusing motion on what matters. Google Material Design’s “hierarchical timing” is an example.
• Challenges: Creating original, supportive animations is still difficult with current tools. Adhering to animation principles helps.

This chapter highlights that a deep understanding of human psychology, applied through thoughtful design of interactions, aesthetics, and motion, can elevate a functional product into an engaging and beloved experience.

8. Interpreting feedback and “leveling up” your product

This chapter focuses on the iterative process of refining a product through feedback. It acknowledges the emotional challenges of creative work and provides strategies for gathering, interpreting, and acting on critiques from teams and customers to progressively improve the product.

It’s a creative journey, after all

Building a product is messy and often involves moments of doubt, likened to Sid Meier’s “Valley of Despair.”

• XCOM example: Jake Solomon, lead designer of XCOM: Enemy Unknown, faced years of failed prototypes. He and Sid Meier eventually stripped the game down to a physical board game prototype to solve core gameplay problems, leading to a successful release.
• Star Wars’ Chewbacca: The iconic character’s design evolved through a complex, iterative process, not a single moment of inspiration.
• Refinement process: Creative endeavors, including product building, involve a continuous stream of refinement before each release.

Leveling up

The product improvement process is compared to a character “leveling up” in a role-playing game, following an “acceleration flow” curve: great strides early on, then gradual growth, and a final acceleration as cumulative feedback drives significant improvements.

• Feedback can be tough: Product designers invest themselves in their work, so negative feedback can be hard to take. It’s important not to take it personally.
• Sources of feedback: The chapter outlines three main sources: your team, current customers/clients, and potential customers/clients.

Team critiques

Gathering feedback from the internal team can take several forms.

• Start with who defined the product: Informal, one-on-one feedback from the core team (product, engineering, marketing) on early prototypes is invaluable for spotting problems and gaining buy-in.
• Pixar’s Braintrust: A group of smart, passionate people who meet regularly to provide candid, constructive feedback on films in development.
• Break down silos with open design reviews: Benedikt Lehnert (Wunderlist) created biweekly “Open Design Reviews” where designers present work to the entire company, explain rationale, and ask specific questions. This creates checkpoints, ensures communication, and exposes designs to broader scrutiny.
• Open up to a private, internal beta: Distribute beta builds internally for real-world usage. Monitor download rates, usage analytics, and crash reports.
• Encourage bug filings: Observing what team members report as “bugs” versus “designed behavior” can highlight confusing flows or actions.
• Communicate updates often: Keep the team informed about what’s new, changed, or reconfigured to maintain attention and the feedback loop.
• Address the toughest first: Prioritize fixing core product issues over minor cosmetic ones to allow time for essential course corrections.
• Trust in the research: When feedback creates confusion, refer back to the original customer research and the core problems the product aims to solve.

Customer feedback

Getting feedback from actual or potential users is crucial but requires careful handling.

• Identify the right customers:
  • Existing customers: Segment customers based on their product usage relevant to the feature being tested (e.g., for a media sharing feature, talk to active sharers). Hiten Shah (KISSmetrics) emphasized testing analytics tools with customers’ own data.
  • Potential customers: Recruiting from existing research communities is better than approaching random people (avoiding biased or ill-informed opinions). Ryan Hoover used his existing network for early Product Hunt feedback. Dropbox also launched with a private build for a select community.
• Pitch clarity: If potential users misunderstand your product’s description, it’s a warning sign (Josh Elman).
• How to analyze customer feedback: Apply “close reading” (as in Sales Safari) to uncover patterns and true meaning, rather than taking isolated comments at face value. Don’t let a few negative points derail a research-backed direction.
• Interpreting feedback example: If a dating app gets feedback that profiles seem fake, the underlying issues might be users not knowing how to initiate contact or finding profile completion too hard.

Don’t squander your gains

The research and feedback gathered are valuable assets.

• Proprietary data: Treat customer input as raw, proprietary data. Take time to parse, understand, and integrate it into the product.
• Avoid building the wrong thing: Interpreting feedback correctly is less painful than launching a product that misses the mark.
• Fall in love with the problem: Jon Crawford (Storenvy) emphasizes spending more time understanding the problem than creating the solution.
• Pre-launch benefits: Early customer input can yield testimonials, success statistics, and evangelists before a full launch.

This chapter underscores that product development is a journey of continuous refinement fueled by diverse feedback, leading to a stronger, more customer-aligned offering.

9. Shipping is an art—and a science

This final chapter discusses the art and science of launching a product, emphasizing that “shipping” is not just about speed but about readiness, quality, and taking full ownership of the product’s journey into the world and beyond.

The invention versus the manufactured article

The chapter opens with Thomas Edison’s struggle to bring electric light from his Menlo Park lab demonstration to a commercial reality on Pearl Street, New York. This highlights the significant leap from a working invention to a marketable product.

• Edison’s challenges: He had to design an entire electrical system, find a site, line up customers, and even determine pricing through market research, all while facing public skepticism.
• Digital product parallels: While stakes might differ, moving from prototypes and iterations to a product supporting real customers is a huge undertaking.
• “Ready” is key: If you’ve built a product to improve users’ lives, ensure it’s truly ready for the wild.

It’s ready when it’s ready

The chapter critiques the tech industry’s obsession with shipping quickly for its own sake, arguing that quality and customer problem-solving should dictate readiness.

• “Ship, not shit”: Cat Noone’s phrase emphasizes the responsibility to ship quality products that solve problems, not just anything to meet a deadline.
• Shipping for shipping’s sake: Often a sign of not knowing what customers need or who they are.
• Facebook’s shift: Mark Zuckerberg changed the “move fast and break things” philosophy to “making sure we’re getting it right first.”
• Apple’s deadlines: Apple sets rigorous internal deadlines but is willing to move them if a product isn’t “magical and delightful” enough.
• Minimum Lovable Product (MLP): Coined by Cat Noone, this is the lowest form of a product that is capable of being loved, accepted, and solving a problem, with the understanding it’s not flawless. It balances problem-solving with an emotional connection.
• Natural forcing functions: A focus on audience problems, self-imposed deadlines, and a quality threshold naturally push a product towards readiness.

Being “chief of everything”

Shipping means taking full ownership of every aspect of the product. You are the COE (Chief of Everything).

• Tracking tools: Use whatever tools work (Trello, Post-it notes, Wunderlist, JIRA, Google Docs) to keep the team clear on tasks, expectations, and responsibilities. Cat Noone uses shared Wunderlist; Katelyn Friedson used JIRA/Google Docs.
• Ready-to-defend deck: Ruby Anaya advises always having an updated 10-page deck for your product to own and defend ideas.
• Launch preparations: This includes predicting press questions, honing sales pitches, creating assets, finalizing landing page copy/pricing, and tweaking launch videos – all falling under your guidance.
• Hard work: Graham Jenkin emphasizes that achieving product quality requires putting in the time and energy.
• Monitoring customer support: Timoni West and Kyle Bragger identify customer support as a crucial post-launch monitoring channel. It’s a direct conduit to customer minds, identifying what’s not working or confusing.
• Resist immediate panic: Katelyn Friedson advises riding out the initial 24-48 hour passionate feedback period before making rapid changes, as negative reactions are often louder and initial.

It’s not over yet

Shipping is just one step. The journey of observation, research, and evolution continues.

• Pixels evolve: Digital products are never truly “done.”
• Continuous observation: Keep focusing on your audience and their problems, and you’ll always know what to do next.
• Future-focused: You’re building the future, which can be scary to some, but armed with customer knowledge, you can navigate it confidently.

The chapter concludes by reinforcing that successful product design is an ongoing commitment to understanding and serving the customer, even after the product has “escaped” into the world.

Big-picture wrap-up

“Designing Products People Love” by Scott Hurff provides a comprehensive and actionable framework for creating successful digital products. The book consistently emphasizes that the heart of great product design lies in deeply understanding and empathizing with the customer, from initial idea conception through launch and beyond. By blending historical wisdom with modern techniques and insights from industry leaders, Hurff demystifies the product creation process, offering readers a clear path to building products that not only solve problems but also resonate emotionally with their users.

• Core takeaway: Truly understanding your customer’s pains and joys through dedicated research (like Sales Safari) is the non-negotiable foundation for designing products people will actually want and use.
• Next action: Choose one product you use daily and try to reverse-engineer its core user flow for a primary task. Then, attempt to write out the interface copy for each step, considering the audience, tone, context, and consistency. This will highlight the importance of words in UI design.
• Iterative process: Embrace prototyping not as a final step, but as an ongoing communication and refinement tool to make your ideas tangible and testable early and often.
• Holistic design: Consider all five states of the UI Stack (ideal, empty, error, partial, loading) for every screen to create a more human and forgiving experience.
• Psychology matters: Leverage principles of speed, behavioral triggers, aesthetics, personality, and motion to make your product more engaging and habit-forming.
• Feedback is a gift: Actively solicit and thoughtfully interpret feedback from your team and customers to continuously “level up” your product, but always ground decisions in your core research.
• Ownership: As a product designer, you are the “Chief of Everything” for your product, responsible for its quality and its journey from concept to customer.
• Reflective question: How can you integrate more direct, unbiased observation of your target users into your current product development process, even before writing a single line of code or designing a pixel?

This book empowers product creators to move beyond guesswork and “ego-first development,” equipping them with the mindset and methods to design products that genuinely connect with people and succeed in the market.