True simplicity is, well, you just keep on going and going until you get to the point where you go... Yeah, we... — Jonathan Ive

True simplicity is, well, you just keep on going and going until you get to the point where you go... Yeah, well, of course.

Author: Jonathan Ive

Insight: There's something almost contradictory about Ive's view of simplicity—it sounds like it requires endless effort to achieve something that should feel effortless. But that's actually the whole point. Real simplicity isn't about stripping things down arbitrarily or making them bare. It's about working through layer after layer of complexity until what remains feels so obvious, so right, that people forget anyone had to think about it at all. Most of us experience this in reverse. We see a beautifully designed object or interface and assume it was simple to create. We don't see the hundred decisions that had to be unmade, the features that seemed essential until someone realized they weren't. We don't see the argument about that one button that stayed because removing it broke something invisible. The "of course" moment only arrives after you've wrestled with everything else. This matters because it explains why genuine simplicity costs something—usually time, or taste, or the willingness to cut things you're attached to. It's why complex solutions often feel easier than simple ones. We want the payoff without the process. But anything worth using—whether it's a product, a system, or even an idea—usually got that way because someone refused to stop questioning until they hit that moment where it all suddenly made sense.

The exhausting work of obvious

True simplicity is, well, you just keep on going and going until you get to the point where you go... Yeah, well, of course.

There's something almost contradictory about Ive's view of simplicity—it sounds like it requires endless effort to achieve something that should feel effortless. But that's actually the whole point. Real simplicity isn't about stripping things down arbitrarily or making them bare. It's about working through layer after layer of complexity until what remains feels so obvious, so right, that people forget anyone had to think about it at all.

Most of us experience this in reverse. We see a beautifully designed object or interface and assume it was simple to create. We don't see the hundred decisions that had to be unmade, the features that seemed essential until someone realized they weren't. We don't see the argument about that one button that stayed because removing it broke something invisible. The "of course" moment only arrives after you've wrestled with everything else.

This matters because it explains why genuine simplicity costs something—usually time, or taste, or the willingness to cut things you're attached to. It's why complex solutions often feel easier than simple ones. We want the payoff without the process. But anything worth using—whether it's a product, a system, or even an idea—usually got that way because someone refused to stop questioning until they hit that moment where it all suddenly made sense.

AI generated

Comments

Sign in to leave a comment or reply to one.

Sign in

Jonathan Ive

Jonathan Ive is a British industrial designer best known for his work at Apple Inc., where he served as Chief Design Officer. He played a pivotal role in the design of iconic products such as the iPhone, iPad, and MacBook, significantly influencing contemporary product design and aesthetics. Ive's contributions have earned him numerous accolades, including being named a Knight Commander of the Order of the British Empire in 2012 for his services to design and enterprise.

Graph

Related