Law 10Part 1: Foundations

Simplify Relentlessly

Every element added must justify its existence.

Complexity dilutes impact. Minimalism isn't just aesthetics—it's strategy. Simplification forces clarity, speed, and memorability.

Example

Google's search homepage, stripped to a single input box, demonstrates that simplicity can power global adoption. Every unnecessary element removed strengthens the core function.

Actionable Takeaways
  • 01Audit every element; if it doesn't add value, remove it.
  • 02Prioritize primary actions and messages.
  • 03Embrace minimalism as both visual and functional discipline.
Decision Framework

When to Apply

  • Before you've invested too much in a direction
  • When you're uncertain about something
  • After completing any meaningful milestone
  • When you've been working in isolation
  • When you notice you're avoiding sharing

When NOT to Apply

  • When feedback would be premature (very early ideation)
  • From people who don't understand your context
  • When you need to trust your vision against popular opinion
  • When feedback-seeking becomes a form of procrastination
Skill Assessment

Assessment Criteria — Where Are You?

You accept feedback when given. You don't immediately become defensive.

Self-assess honestly — growth requires knowing where you are

Deep Mode — Applied Perspectives
Deep Mode — The Designer Perspective

Simplicity in design is not the absence of complexity—it is complexity resolved. The simple design that truly works has considered and rejected alternatives, tested edge cases, and refined solutions until only the essential remains. This process is more demanding than adding elements.

Real-World Examples
  • 01The iPhone's original interface: Radical simplification that redefined mobile computing.
  • 02Craigslist: Function stripped to absolute essentials—no design for design's sake.
  • 03Muji products: Simplicity as philosophy, not just aesthetic.
How to Implement
  • 01Start with everything, then remove until it breaks. Add back only what's necessary.
  • 02Apply the 'one feature per screen' rule for digital interfaces.
  • 03Use progressive disclosure: show complexity only when users need it.
  • 04Question every element: 'Would the design fail without this?'
  • 05Test with minimal designs first—add complexity only where data demands.
Tools & Resources
01

Hick's Law Calculator

Measure decision complexity

02

Feature Audit Template

Evaluate each element's value

03

User Testing for Comprehension

Verify simplicity works

04

Content Priority Matrix

Rank elements by importance

Further Reading
  • "The Laws of Simplicity" by John Maeda — Ten laws for balancing simplicity and complexity
  • "Insanely Simple" by Ken Segall — Apple's simplicity obsession
  • "Subtract" by Leidy Klotz — The science of doing less

Reflection Prompts

"What am I afraid to show someone right now?"

The thing you're avoiding sharing is often the thing that most needs feedback.

"Who would give me the feedback I need (not want) to hear?"

Seek critics who share your goals, not just supporters who share your biases.

"What feedback have I received that I'm ignoring?"

We often collect feedback without acting on it. What patterns are you dismissing?

Practice Exercises

Share something at 50% completion instead of 90%. Notice what feedback you get that you wouldn't have gotten later.

Difficulty:

Power Combinations

Feedback Loop

Iteration + Feedback creates continuous improvement.

Vulnerable Iteration

Feedback + Authenticity allows you to receive feedback without defensiveness.

Synergies — Laws That Amplify This One

Prerequisites — Understand These First

Sign in to track applications

Personalized Analysis

Sign in to get AI-powered insights on applying this law to your life.

Sign In to Continue