Making Simplicity a Superpower: How Ruthless Reduction Builds Better Products
When Apple’s team sat around debating two on-screen keyboard versions for the iPad, they were tempted to include both—lots of options seemed safer, more flexible, maybe even 'innovative.' But after a tough demo with Steve Jobs, the group realized what was truly at stake: simplicity wasn’t just aesthetics, it was about respecting real people's brainpower in everyday life. By focusing on one clear solution, they not only eliminated a bunch of confusing decisions for users but also sidestepped hard technical questions about remembering preferences or toggling modes. In the end, users got a keyboard they could trust instantly—even under stress. The group learned the value of relentless reduction, of being willing to cut their own clever features, and that almost always, the path to elegance is paved by what you say 'no' to, not what you add.
Look at your work—project, process, or design—and write down every feature, step, or option. Step through each, one by one, and ask yourself if it would truly be missed. Cut out the ones that don't serve the main purpose, even if it feels a little scary or if you’re oddly attached to them. Let a newcomer or friend try the stripped-down version, and observe if it's actually easier to use and learn. Keep what matters most and let clarity do the heavy lifting. Take five minutes tonight to try this and see the difference for yourself.
What You'll Achieve
Build the courage and clarity to simplify your solutions, increase user satisfaction, and reduce errors and confusion both for yourself and others.
Strip Away Features Until Only the Essentials Remain
List every feature, option, or component in your project.
Write down every function, button, screen, or step your work currently includes. Be brutally comprehensive—don't leave anything out.
Question each item’s true necessity for users.
For every entry, ask: If I removed this, would most users be confused, or would the product get easier? Challenge yourself to imagine doing without it.
Remove or hide anything non-essential.
Delete, hide, or postpone features that don’t serve the core purpose. If it’s just 'nice to have', let it go for now—even if you worked hard on it.
Test the streamlined version with a fresh user.
Let someone unfamiliar with the project try the reduced version. Notice if they get lost or if things feel more intuitive and less overwhelming.
Reflection Questions
- What features or steps could be removed without harming your project's core value?
- Why do you find it hard to delete or reduce your own ideas even when they're not helping?
- How do others respond to a simpler solution versus a more complex one in your experience?
- What would your product or plan look like if it had only half its current features?
Personalization Tips
- A student simplifies a class presentation by cutting 2 of 5 main points, focusing only on the strongest ideas.
- A team leader removes rarely-used steps from a group workflow, making new employee onboarding twice as fast.
- A parent reorganizes a messy family calendar by hiding less important recurring reminders so everyone stops missing key events.
Creative Selection: Inside Apple's Design Process During the Golden Age of Steve Jobs
Ready to Take Action?
Get the Mentorist app and turn insights like these into daily habits.