Key Takeaways
Treat UX as disciplined empathy, not a matter of artistic taste
Serve the person using it. Grant argues that user experience is not decoration: a product must help people accomplish tasks, even when visual polish matters. The essential skills are empathy, to understand users' goals and frustrations, and objectivity, to notice flaws in a product that its makers may have grown used to. These skills can be developed; UX is not a mysterious talent reserved for specialists.
The book's examples show how organizational preferences can crowd out user needs: a familiar feature gets renamed with brand language, pale text becomes difficult to read, or a hard-to-dismiss pop-up chases marketing numbers. In each case, the interface reflects internal priorities rather than what the person came to do.
The principle aligns UX with service design: success is judged not by the maker's intention but by what happens at the point of use. Empathy helps identify friction, while objectivity makes it possible to question a beloved design decision. Neither is a substitute for evidence, though. Designers can sincerely imagine users and still mistake their own habits for universal ones. The strongest reading of Grant's advice is not to distrust aesthetics, but to treat appearance as one part of a working experience, subject to the same scrutiny as speed, comprehension, and task completion.
Make controls recognizable before asking users to learn your interface
Familiar cues reduce guesswork. Buttons should look and behave like buttons, links should be visibly distinguishable, and controls should be large enough to tap accurately. Fitts' Law describes how target size and distance affect the time needed to reach a target, which makes tiny, tightly packed controls a practical usability problem, not merely an aesthetic one. Use established controls, including device-native input features, rather than making people learn an unfamiliar alternative without a clear benefit.
Typography also guides attention. The book recommends no more than two typefaces, a small number of meaningful text sizes, and a readable default such as 16-pixel body text with generous line spacing. System fonts can load quickly and feel native to the device. Labels alongside icons help make unfamiliar symbols understandable.
Recognizable controls draw on learned conventions and visual affordances, the cues that suggest what an object does and how to operate it. This lowers the amount of interpretation required before action. Yet convention is not an absolute: a familiar pattern can still fail when adapted to a new context, or for users with different abilities. The useful test is not whether a control looks traditional, but whether users can identify its purpose, operate it reliably, and tell when it has responded. A new interaction earns its complexity only when the improvement is clear in use.
Cut form friction by asking less and accepting human variation
Every field costs effort. A form can turn a promising product into a chore. Grant recommends collecting only information needed for the task, explaining why sensitive or optional details are requested, and avoiding duplicate entry. A basic account may need only an email or phone number and a password. Payment forms should likewise request only what is necessary, display card digits clearly, and use a secure connection.
Make errors easy to fix. Preserve everything the user has entered, identify the field that needs attention, and give feedback before submission when possible. But do not reject reasonable variations just because they complicate the data model: names may contain accents or apostrophes, and phone numbers or postal codes vary across places. Use the device's suitable input, such as a numeric keypad for number entry, and allow password managers to paste passwords.
Form design makes a hidden exchange visible: users give time and personal data in return for a service. Minimizing fields can therefore improve both completion and trust, especially when the request is proportionate to the task. Flexibility also shifts complexity to the system, where software can often normalize different inputs after they are entered. That shift is not cost-free: some information must be checked for safety or legal reasons. The design challenge is to distinguish necessary verification from rigid formatting rules that protect internal convenience more than the user.
Keep users oriented, and give them a way back from mistakes
Recoverability creates control. People make accidental choices, so important actions should be reversible where possible. Grant points to Gmail's undo-send feature, which holds a message briefly before sending, and recommends an undo option after actions such as removing an item. Users gain a chance to recover without having to prevent every mistake in advance.
Orientation matters just as much. Finite content, such as an inbox or a list of products, benefits from pagination because it gives the list a visible extent and preserves a sense of location. Infinite scroll is better suited to feed-style browsing. Whichever pattern is used, return people to the same place after they open an item and come back. Refreshing a feed should not unexpectedly send someone to the beginning or replace the item they were reading.
Undo and preserved position are examples of designing for human fallibility rather than treating every error as user failure. This is closely related to resilience in safety-critical systems: recovery paths reduce the consequences of small slips. There is a useful balance to strike. Undo is valuable when an action has meaningful consequences, but adding confirmation dialogs to every minor step can create friction and encourage reflexive clicking. A good interface makes recovery available at the moment it matters, while keeping ordinary actions direct.
Design access into every interaction, not as a special accommodation
Use more than one signal. Color alone should not communicate success, failure, or status, because some people cannot distinguish particular colors. Pair it with text, an icon, shape, or another cue. Keep text readable against its background; the book points to the WCAG 2.0 minimum contrast ratio of 4.5:1 for ordinary text. Links should be identifiable without relying only on color, and form fields need persistent labels rather than placeholder text that disappears during entry.
Access also depends on interaction. Let users zoom, provide a logical keyboard tab order, include a way to skip repeated navigation, and make touch targets large enough to hit without precision. Descriptive link text helps screen-reader users understand destinations. These choices often help everyone, including people using a small screen, a poor connection, or a device in difficult conditions.
Accessibility is not a separate layer placed on top of a finished interface. It exposes whether the interface communicates through a single narrow channel, such as color, tiny targets, or visual placement alone. Redundant cues make meaning more robust across devices and situations. The book's practical guidance is valuable, though numeric standards should be checked against the current version of the relevant accessibility guidelines and the specific text size and context. Compliance is a floor, not proof that a particular interface works for a diverse group of people.
Use defaults and conventions to shorten the path to the user's goal
Make the common case easy. Most people never change a product's settings, so defaults shape the experience for the majority. Choose them using evidence about what users commonly need, how difficult it is to change the setting, and whether alternatives are discoverable. A search for children's pajamas, for example, might sensibly prioritize children's clothing and available items rather than requiring users to set those filters themselves.
Search should surface the most relevant results first, let users adjust sorting and filters, and group large result sets into useful categories. Familiar conventions matter too. In online shopping, the expected path is products, a basket, then checkout, with a guest option where possible. Following established patterns reduces the amount users must learn before they can complete a task.
Defaults are decisions made on behalf of people who may never inspect the settings menu. That makes them powerful, but also potentially paternalistic: a convenient default can quietly steer choices or hide alternatives. The best defaults reduce repeated work while remaining visible and changeable. Familiar conventions offer a similar trade-off. They let users transfer knowledge between products, but should not excuse copying a pattern that fails the actual task. Evidence about real behavior is what separates helpful anticipation from organizational guesswork.
Show the user's place, progress, and next step throughout each journey
Give tasks clear signposts. A user should be able to tell where a process begins, what stage it has reached, and when it is finished. Progress indicators, breadcrumbs, confirmation messages, and visible saved states can answer practical questions such as whether an order was placed or a document was stored. Breadcrumbs also show how a current view fits into a larger hierarchy and give users a route back to a broader section.
A blank slate, an empty view shown before someone has created content, can explain a useful first action instead of presenting a dead end. Onboarding tips should be easy to dismiss, especially for returning users. Optional steps should be skippable. For work that takes time, show a progress bar when duration can be estimated and a spinner when it cannot; never imply progress that is not happening.
These cues help users build a mental model: an understanding of where they are, what the system has done, and what they can do next. Clear status is especially important when a product behaves differently from everyday physical tools, as digital processes can otherwise be invisible. The challenge is to provide enough information without turning every task into a guided tour. A persistent indicator is useful when it reduces uncertainty; it becomes noise when it repeats what the interface already makes obvious.
Give frequent actions prominence and rare actions room to hide
Match visibility to use. Grant proposes sorting interactions into three practical levels: actions that must be obvious, actions that should be easy to find, and actions that only need to remain possible. A camera's shutter is central and belongs in plain view. Switching lenses is less central but should still be easy to reach. Adjusting advanced focus settings can be available deeper in the interface without crowding the main screen.
This hierarchy helps resolve a common design tension: users need access to powerful features, but placing every option in front of them makes a product harder to scan. Group long menus into meaningful sections, put advanced settings in their own area, and make core destinations visible rather than hiding everything in a hamburger menu. Test where people look and what they fail to find, then adjust the hierarchy.
This is a practical form of progressive disclosure: show the complexity needed for the current task while keeping less common capabilities available. It recognizes that discoverability and simplicity can conflict, rather than pretending one interface can maximize both everywhere. Frequency alone is not enough to rank a feature. A rarely used emergency control may deserve immediate visibility because the cost of not finding it is high. Task importance, urgency, and consequences should shape prominence alongside usage data.
Never trade user trust for engagement metrics or brand theater
Serve the user's interest. Grant objects to interfaces that prioritize a company's image or short-term metrics over the task at hand. A branded splash screen delays access; an aggressive rating prompt interrupts it; obscure labels make familiar actions harder. He is especially critical of dark patterns, interface choices that steer or trick people into actions they might not otherwise take. Examples include preselected add-ons, disguised advertisements, and obstructive unsubscribe flows.
He also warns that engagement can become a justification for addictive design, such as notifications that encourage people to check repeatedly. The alternative is to give users control, including the ability to tune notification types, and to make commercial flows clear. Users should understand what they are buying, what a setting does, and how to reverse a choice when possible.
The ethical argument is strongest when it treats trust as a product requirement, not a decorative value. A design that increases clicks by obscuring choice may deliver a short-term metric while weakening informed consent and long-term confidence. Engagement is not inherently harmful: notifications can be genuinely useful, and business goals need not oppose user goals. The distinction lies in whether people can understand, control, and decline the interaction. Ethical review becomes more concrete when teams examine defaults, exit paths, and who benefits from each friction point.
Test with five real users before polishing assumptions into product
Observe behavior early. Grant argues that principles are starting points, not substitutes for testing. Put even a rough prototype in front of people who resemble the intended users and ask them to complete real tasks. Watch where they hesitate, what they misunderstand, and whether they can recover. Testing early can reveal problems before they become expensive to change; colleagues and stakeholders are poor substitutes for actual users.
The book cites usability research suggesting that a test with five users can uncover about 85 percent of usability problems in a given round. This is a claim about finding common qualitative problems, not a guarantee that five people represent an entire population or can estimate how often a problem occurs. A small study can expose issues quickly; broader research may still be needed for diverse or high-stakes products.
The value of a small usability test is diagnostic, not statistical. A handful of observed sessions can reveal recurring breakdowns that a design team has stopped noticing, but the reported percentage depends on assumptions about users, tasks, and the distribution of problems. Testing should therefore be treated as an iterative search for failure modes, not a certificate of usability. The most useful question is not whether a design passed, but what people tried to do, where their expectations diverged from the interface, and what change would make the next attempt clearer.
Analysis
Grant's collection is best understood as a field manual for reducing the small frictions that make software feel hostile. Its examples range from typography and touch targets to password recovery, shopping, and ethical manipulation. The through-line is that usability is produced by many decisions that appear minor in isolation: whether a button looks actionable, whether an error preserves entered data, whether a list remembers its place, and whether a company asks for information it does not need. Together, these decisions either respect or consume a user's attention.
The book is strongest where it turns broad values into observable interface choices. Empathy becomes a clear label, a visible exit, a recoverable action, or a sensible default. Its insistence on familiar conventions also reflects a sound learning principle: people arrive with expectations formed elsewhere, and products can benefit from that accumulated knowledge. Its ethical critique usefully widens the designer's responsibility beyond task completion to the motives built into interactions.
The main limitation is the form's confidence. One hundred and one compact rules can sound universal, though many are context-sensitive heuristics. Infinite scrolling, hidden navigation, custom controls, and even the right default depend on the task, audience, device, and consequences of error. A convention can be familiar and still be inaccessible or inappropriate. The book's own emphasis on testing offers the best corrective: treat each rule as a hypothesis, then observe people using the product.
Some recommendations also reflect the technical environment of 2018, and standards or platform behavior can change. The enduring contribution is less any single pixel value than a method of judgment: identify what users are trying to do, remove unnecessary effort, preserve control, and verify the result with real users. In that sense, the book is not a catalog of visual rules so much as an argument for humility in product design.
Review Summary
101 UX Principles receives mostly positive reviews, with an average rating of 4.12/5. Readers appreciate its practical advice, clear writing style, and comprehensive coverage of UX topics. Many find it useful for both beginners and experienced professionals. The book is praised for its straightforward approach and real-world examples. Some reviewers note that while the content may seem obvious, it serves as a valuable reminder of important principles. A few critics mention that certain principles are debatable or that the book could benefit from more recent examples.
People Also Read
Glossary
Fitts' Law
Target size and reachA model of human movement stating that the time required to reach a target depends partly on the target's size and its distance from the starting point. In interface design, it supports making important buttons large enough and placing related controls within practical reach, while leaving enough separation to prevent accidental taps.
Blank slate
Guidance for empty viewsAn empty state in a product where content would normally appear, shown because a user has not yet created or added anything. Rather than leaving the view uninformative, a blank slate can explain the feature and suggest a relevant first action, such as adding a task or creating a project.
Infinite scroll
Content loads while scrollingA browsing pattern that automatically adds more items as a person approaches the end of the visible list. It suits continuously browsed feeds, but can make finite collections difficult to navigate because users lose a clear sense of extent, position, and endpoint. When used, the product should preserve the user's place.
WCAG 2.0
Web accessibility guidelinesThe Web Content Accessibility Guidelines version 2.0, published by the World Wide Web Consortium. The guidelines describe ways to make web content more perceivable, operable, understandable, and robust. Grant highlights a minimum contrast ratio of 4.5:1 for ordinary text as one practical accessibility measure.
Jakob's Law of Internet User Experience
Reuse familiar interaction patternsA principle associated with Jakob Nielsen stating that people spend much of their time using products other than yours, so they bring expectations from those experiences. Interfaces can reduce learning effort by following familiar conventions, unless there is a clear user benefit to doing something differently.
Hook Model
Habit-forming product cycleA framework described by Nir Eyal and cited in the book for how products can encourage repeated use through recurring behavioral cycles. Grant references it while warning that product teams can use engagement techniques to foster compulsive checking. The concept helps distinguish useful return visits from designs that exploit attention.
dark patterns
Interfaces that manipulate choicesInterface patterns that mislead, pressure, or obstruct users to advance an organization's interests over the user's own. Examples in the book include hidden charges added to a basket, advertisements disguised as ordinary controls, and unsubscribe processes designed to make leaving difficult.
CRUD
Core record operationsAn acronym for create, read, update, and delete, the standard operations used to manage records in software. Grant notes that products built around these operations can save users substantial effort by letting them create a new record from an existing one, preserving details that do not need to be entered again.
Obvious, Easy, or Possible
Interaction priority levelsGrant's way of classifying interface actions by how prominently they should be presented. Core actions should be obvious, secondary actions should be easy to locate, and infrequent advanced actions need only remain possible to find. The distinction helps teams balance discoverability against screen clutter.
Why you only need to test with 5 users
Small usability studyA usability research article cited by Grant to support testing with small groups. It reports that five users can uncover a large share of usability problems in a test round. The finding is useful for qualitative discovery, not as proof that five participants statistically represent a full user population.
FAQ
What's "101 UX Principles" about?
- Comprehensive UX Guide: "101 UX Principles" by Will Grant is a definitive guide that provides a broad set of guidelines for designing digital products with a focus on user experience.
- Core Principles: The book outlines 101 core principles that aim to make digital products more usable and effective, saving time and enhancing user satisfaction.
- Practical Advice: It offers practical advice for both novice and seasoned UX professionals, covering various aspects of UX design such as typography, controls, and user journeys.
- User-Centric Approach: The book emphasizes the importance of putting the user first and designing products that are intuitive and easy to use.
Why should I read "101 UX Principles"?
- Improve UX Skills: Whether you're a beginner or an experienced designer, the book provides valuable insights and shortcuts to improve your UX design skills.
- Real-World Examples: It includes real-world examples and scenarios that illustrate common UX challenges and solutions.
- Comprehensive Coverage: The book covers a wide range of topics, from typography and controls to user journeys and consistency, making it a comprehensive resource.
- User-Centric Focus: It encourages a user-centric approach, helping you design products that meet user needs and enhance their experience.
What are the key takeaways of "101 UX Principles"?
- Empathy and Objectivity: Empathy and objectivity are crucial traits for UX professionals to understand user needs and improve product design.
- Simplicity and Clarity: Strive for simplicity and clarity in design to make products more intuitive and user-friendly.
- Consistency is Key: Consistent use of icons, terminology, and controls across a product enhances usability and user satisfaction.
- Test with Real Users: Regular testing with real users is essential to identify usability issues and improve the overall user experience.
What are the best quotes from "101 UX Principles" and what do they mean?
- "User experience is not art. It's the opposite of art." This quote emphasizes that UX design should prioritize functionality and user needs over aesthetics.
- "A designer knows he has achieved perfection not when there is nothing left to add, but when there is nothing left to take away." This highlights the importance of simplicity and removing unnecessary elements in design.
- "Fight for the user, not the company." This encourages designers to prioritize user needs and experiences over corporate interests or branding guidelines.
- "Test with real users and listen to them, and you'll build something they love." This underscores the importance of user testing in creating successful products.
How does "101 UX Principles" define a UX professional?
- Anyone Can Be a UX Professional: The book suggests that anyone involved in designing software products can be a UX professional, regardless of their official role.
- Key Traits: Empathy and objectivity are identified as the primary skills needed to excel in UX design.
- Learning and Practice: While formal study and experience are valuable, the book emphasizes that UX skills can be learned and honed through practice.
- User-Centric Focus: A UX professional should always prioritize the user's needs and strive to create intuitive and effective designs.
What typography advice does "101 UX Principles" offer?
- Limit Typefaces: Use no more than two typefaces to avoid visual noise and enhance readability.
- System Fonts: Utilize system-native fonts to improve page load times and ensure better rendering across devices.
- Information Hierarchy: Use type size to depict information hierarchy, making important information more prominent.
- Sensible Defaults: Set a sensible default size for body copy, typically 16px with a 1.5 line height, to ensure readability.
What does "101 UX Principles" say about button design?
- Make Buttons Obvious: Buttons should look like buttons, with visual affordances such as texture and shadows to indicate interactivity.
- Clickable Area: Ensure the entire button is clickable, not just the text, to improve usability.
- Sensible Size and Grouping: Buttons should be a sensible size and grouped by function to facilitate easy navigation.
- Avoid Arbitrary Controls: Do not invent new, arbitrary controls; use established patterns that users are familiar with.
How does "101 UX Principles" address form design?
- Minimal Information: Only ask for the information you truly need to reduce user effort and increase form completion rates.
- Immediate Validation: Validate data entry as soon as possible to provide instant feedback and reduce errors.
- Forgiving Design: Be forgiving with data entry, allowing flexibility in how users input information.
- Clear Error Indication: If a form fails validation, clearly show which fields need attention to guide the user in correcting errors.
What does "101 UX Principles" recommend for navigation design?
- Avoid Hamburger Menus: Hamburger menus can slow down discovery and increase task difficulty; consider alternative navigation patterns.
- Breadcrumb Navigation: Use breadcrumb navigation to help users understand their location within a product and easily navigate back.
- Logical Tab Order: Ensure navigation elements have a logical tab order to improve accessibility and usability.
- Consistent Icons: Use consistent icons across the product to enhance recognition and reduce user confusion.
How does "101 UX Principles" suggest handling user feedback?
- Test with Real Users: Regularly test with a diverse group of real users to gather valuable insights and improve the product.
- Listen and Iterate: Use feedback to iterate quickly and make necessary adjustments to enhance the user experience.
- Small Test Groups: Even small test groups can provide significant insights, uncovering the majority of usability issues.
- User-Centric Approach: Always prioritize user feedback and needs over internal assumptions or preferences.
What are some advanced UX concepts covered in "101 UX Principles"?
- Obvious, Easy, Possible: Classify interactions as obvious, easy, or possible to determine their prominence and accessibility in the UI.
- Infinite Scroll vs. Pagination: Use infinite scroll for feed-style content and pagination for content with a clear beginning, middle, and end.
- Sensible Defaults: Choose default settings that reduce user effort and align with common user behaviors and preferences.
- Established Metaphors: Build upon established metaphors and patterns to create intuitive and familiar user experiences.
How does "101 UX Principles" address ethical considerations in UX design?
- Avoid Dark Patterns: Refrain from using deceptive or manipulative design patterns that prioritize company goals over user needs.
- Ethical Implications: Consider the moral and ethical implications of the software you help create, ensuring it benefits users.
- User-Centric Focus: Always fight for the user, prioritizing their needs and experiences over corporate interests.
- Transparent Design: Design interfaces and experiences that are transparent and respectful of user autonomy and choice.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.