The Laws of Simplicity

In one sentence

Simplicity is the intentional removal of noise to allow the essential purpose of a thing to shine through.

Why read this (and who it's for)

Most people mistake "simple" for "easy." They think that making something simple means doing less work, but in reality, simplicity requires more effort: it requires the courage to say no to good ideas so that the great ones can survive.

This book is for product designers, engineers, writers, and leaders who find themselves overwhelmed by "feature creep," bloated communication, or cluttered systems. After reading this, you will stop viewing simplicity as an aesthetic "look" (like minimalism) and start seeing it as a functional strategy to reduce cognitive load and increase clarity of purpose.

The big idea

Maeda argues that complexity is the default state of human creation. When we build things—software, furniture, businesses, or even sentences—we naturally add features, decorations, and layers because they seem like "value adds." However, every addition increases the cognitive load on the user. Eventually, the system becomes so complex that the original purpose of the thing is buried under its own weight.

The core thesis is that Simplicity is a process of subtraction. It is not about what you add to make something look clean; it is about what you remove until only the essential remains. To achieve true simplicity, you must identify the "Job to be Done"—the singular reason the object exists—and ruthlessly eliminate anything that distracts from that job.

Simplicity is hard because it requires making difficult trade-offs. It requires rejecting features that are "cool" but unnecessary. It requires a deep understanding of how humans perceive information and where their attention naturally falls. If you cannot explain what something is in one sentence, you don't yet understand its simplicity.

Key ideas

Simplicity vs. Easy

What it is — A common misconception is that "simple" means "easy to do." In reality, simple designs are often the hardest to engineer because they require a perfect understanding of the user's needs and the removal of all distractions. Why it matters — If you aim for "easy," you will produce bloated products that are cluttered with unnecessary features. If you aim for "simple," you will produce elegant solutions that require deep thought but offer effortless use. In the book — Maeda highlights how a simple interface (like a single button) might be harder to design than a complex one because it requires the designer to ensure that one button does exactly what the user needs without any secondary distractions.

The Cost of Complexity (Cognitive Load)

What it is — Every piece of information, every button, and every word requires mental energy to process. This is "cognitive load." When a system exceeds a human's ability to process it quickly, the system fails. Why it matters — Users have a limited "budget" for attention. If you waste their budget on non-essential features, they won't have enough left to accomplish their actual goals. In the book — Maeda discusses how over-designed interfaces lead to "choice paralysis," where the sheer volume of options prevents the user from making any decision at all.

Simplicity as a Discipline

What it is — Simplicity is not an aesthetic style (like "minimalism"); it is a rigorous discipline of subtraction. It is a way of thinking about how we organize information and actions. Why it matters — If you treat simplicity as a style, you will just end up with a "clean" version of a complex mess. If you treat it as a discipline, you will fundamentally rethink the architecture of your product or project. In the book — Maeda argues that we must be disciplined enough to remove things even when they seem useful, because their presence dilutes the primary message or function.

The "Job to be Done" Principle

What it is — Before you can simplify anything, you must define exactly what the thing is supposed to do. You cannot subtract until you know what is essential. Why it matters — Without a clear definition of purpose, subtraction becomes arbitrary. You might accidentally remove something vital or keep something useless because you haven't defined the "Job." In the book — Maeda emphasizes that simplicity starts with clarity of intent. If you can't state the primary goal of your project in one sentence, you aren't ready to simplify it yet.

Precision in Communication

What it is — Simplicity applies to language and communication as much as it does to visual design. It means using the fewest words possible to convey the highest amount of meaning. Why it matters — In a world of information overload, clarity is a superpower. Precise language reduces the chance of misunderstanding and allows for faster decision-making. In the book — Maeda explores how removing "filler" words and focusing on active verbs can make communication more impactful and easier to digest.

Frameworks & tools

The Subtraction Framework

Use this when you are overwhelmed by a project's scope or a product's feature list.

1. Identify the Core Job: Write down the one thing the user/reader wants to achieve. (e.g., "The user wants to book a flight.")
2. Audit the Current State: List every single feature, word, or element currently present in the experience.
3. The "Why" Test: For every item on that list, ask: "Does this directly help the user complete the Core Job?"
4. Ruthless Removal: If an item is "nice to have" but doesn't directly serve the Core Job, remove it.
5. Iterate: Repeat until the experience feels lean and focused.

The Cognitive Load Audit

Use this during the design phase of a UI or a complex process.

1. Identify Entry Points: Where does the user start?
2. Trace the Path: Map out every step the user must take to reach their goal.
3. Count the "Decisions": At each step, how many choices does the user have to make?
4. Minimize Decisions: Any step with more than 3-5 choices is a high-friction zone. Break those choices into sub-steps or remove the unnecessary ones.

Memorable examples & stories

The "Paradox of Choice" in UI

Maeda discusses how providing too many options can actually hinder a user's ability to choose anything at all. By offering 20 types of buttons, you make it harder for the user to find the right button. The lesson: Constraints are often more helpful than freedom; by limiting choices, you empower the user to act.

The "Invisible" Design

Maeda points toward designs that disappear into the background—where the tool becomes an extension of the user's intent. When a design is truly simple, you don't notice the design; you only notice the task being completed. The lesson: Great design isn't about being noticed; it's about making the experience seamless.

The "Feature Creep" Trap

He describes how products often grow organically (and poorly) as teams try to please everyone at once, leading to a "Swiss Army Knife" product that is mediocre at everything and master of nothing. The lesson: Saying "no" to a good feature is the only way to keep a product great.

Key quotes

"Simplicity is not about what you add; it's about what you take away." (Paraphrased) Why it matters: It shifts the mental model from additive creation to subtractive curation.

"Complexity is often a mask for a lack of understanding." (Paraphrased) Why it matters: If you can't make something simple, it usually means you don't yet understand how it works or why it exists.

"The goal of simplicity is to reduce the cognitive load on the user." (Paraphrased) Why it matters: It centers the design philosophy on the human experience rather than the designer's ego.

How to apply it

This week

• The One-Sentence Audit: Take a project you are currently working on. Try to write down its primary purpose in exactly one sentence. If you can't, stop working and redefine the goal until you can.
• The "Delete" Exercise: Look at your most-used app or a piece of software you use daily. Identify one feature you never use but that is always there. Note how it affects your mental space.
• Email/Message Pruning: Before sending your next internal update, delete the first two sentences and any "filler" adjectives. See if the message still lands clearly.

Ongoing

• The "One-In, One-Out" Rule: For every new feature, button, or piece of information you add to a project, you must identify one thing that can be removed or simplified to compensate for the added complexity.
• The Purpose Test: Before adding any new element to a design or process, ask: "Does this directly help the user complete the Core Job?" If the answer isn't a definitive "Yes," it stays off the list.

Common pitfalls

• Confusing Simple with "Empty": People often think simplicity means white space and lack of content. That’s just aesthetics. True simplicity is about functional clarity. A page can be full of information but still be simple if that information is perfectly organized to serve a single goal.
• The Fear of Saying No: The biggest hurdle to simplicity is the fear of disappointing stakeholders who want "more." You must advocate for the user's cognitive load as a primary metric of success.
• Over-simplifying to the point of uselessness: If you remove so much that the product no longer works, you haven't simplified it; you've broken it. Simplicity is about finding the minimum viable complexity required to achieve the goal.

Connects to

• "The Design of Everydaythings" by Don Norman: Extends Maeda’s ideas by focusing on "affordances"—how objects tell us how to use them—which is a key component of making things simple.
• "Zen and the Art of Motorcycle Maintenance" (Robert Pirsig): While not a design book, its exploration of "Quality" as a deep, internal standard relates to Maeda's view of simplicity as a discipline rather than a style.
• "Atomic Habits" by James Clear: Connects to the idea of "Simplicity as a Process." Just as habits are built through small, repeated actions, simplicity is achieved through the consistent practice of subtraction.

If you remember only three things

• Simplicity is a process of subtraction, not addition.
• The primary goal of simplicity is to reduce cognitive load for the user.
• You cannot simplify anything until you have clearly defined the Core Job it is supposed to perform.

Internalize it

• Reflection questions

  1. What is the "Core Job" of the project I am currently working on? Can I state it in 10 words or less?
  2. Where am I adding complexity because I'm afraid of saying "no" to a stakeholder?
  3. If I had to remove 50% of the features/words from my current project, what would be the absolute minimum required for it to still function?

• Flashcards Q: Is simplicity the same as "easy"? A: No. Simple designs are often harder to create because they require a deeper understanding of the user's needs and more intentional subtraction.

Q: What is "Cognitive Load"? A: The amount of mental energy required to process information; simple design aims to minimize this so users can focus on their goals.

Q: What is the first step before you can simplify any product? A: You must define the "Core Job"—the single primary purpose the product exists to serve.

Q: How does Maeda define simplicity as a discipline? A: It is the intentional removal of noise and distractions to allow the essential purpose of an object or experience to shine through.

Q: What is the "Subtractions Framework"? A: A process of identifying the Core Job, auditing current elements, testing each against that job, and ruthlessly removing anything that doesn't serve it directly.