Design Like Apple: Seven Principles for Creating Insanely Great Products, Services, and Experiences

The Central Argument

John Edson’s book is not, despite what the title might suggest, a hagiography of Steve Jobs or a retreat into the familiar mythology of the black turtleneck. The central argument is more operationally serious than that: design, understood as a discipline of intention rather than decoration, is the primary competitive differentiator of our era, and Apple’s success can be reverse-engineered into transferable principles that any organization can deliberately practice. Edson, who led the design firm LUNAR and worked closely within the Apple ecosystem, is writing from the inside of practice rather than the outside of admiration. That distinction matters enormously for how the argument lands.

The framework he builds around seven principles — things like “simplify,” “differentiate,” and “begin with empathy” — sounds like it could collapse into motivational seminar material. It doesn’t, quite, because Edson keeps pulling the argument back to specificity: what does it actually mean to simplify when your engineering team has seventeen legitimate feature requests and your sales team has twelve more? What does empathy require when you’re designing for a user who doesn’t yet know they want the thing you’re making?

Why This Argument Is Necessary Now

The context that makes Edson’s intervention necessary is the post-industrial reality of abundance. When products were scarce and distribution was the bottleneck, design was a finishing coat — the chrome on the car, the font on the package. Now that manufacturing has been commoditized and distribution is nearly frictionless, the differentiator has shifted upstream, all the way into the question of what to make and why. Organizations that still treat design as the department you call after the engineers are done are operating with a fundamentally obsolete model of value creation.

Edson’s book is also responding to a specific misreading of Apple: the cult-of-personality interpretation that reduces everything to the taste and willfulness of Jobs. That reading is both flattering to Jobs and useless to everyone else, because it implies the lesson is “hire a genius and get out of the way.” Edson argues instead that Apple’s genius is structural — it lives in process, in the elevation of design as a first-class organizational concern, in the discipline of saying no more often than yes. These are learnable, reproducible things.

The Key Insights in Depth

The principle I find most intellectually generative is the insistence on beginning with empathy rather than with capability. There is a persistent engineering temptation — and I recognize it in myself — to start from what is technically possible and then search for a use case. Apple’s counter-move, and Edson’s prescription, is to start from a lived human situation, to study it with something approaching anthropological seriousness, and only then to ask what technology might serve it. The product becomes the answer to a question that the user is actually asking, even if they couldn’t have articulated it before the product existed.

This connects to a subtler point about the nature of simplicity. Simplicity in Edson’s account is not minimalism for its own sake. It is the deliberate removal of everything that does not serve the core use case, which requires first having diagnosed what that core use case actually is. The iPod’s click wheel is not simple because Apple’s engineers were lazy; it is simple because Apple had decided with great precision what the device needed to do and had refused to let it do anything else. Simplicity is downstream of clarity of purpose, and clarity of purpose requires the empathy work first.

The principle of differentiation is where the argument engages most directly with business strategy, and here Edson is careful not to conflate differentiation with novelty. Differentiation means being meaningfully distinct in the dimensions that matter to the user, not being different for its own sake. This is a harder discipline than it sounds, because novelty is easy to generate and meaningful distinction is hard to earn. It requires knowing what users actually value, which brings everything back, again, to empathy.

Connections to Adjacent Fields

The architecture of Edson’s argument has strong resonances with Clayton Christensen’s jobs-to-be-done framework — the idea that customers “hire” products to accomplish specific tasks in their lives, and that understanding the job precedes everything else. It also rhymes with the lean startup tradition’s emphasis on building only what you have validated. But Edson’s contribution is to frame this not as a methodology of risk reduction but as a philosophy of craft. He is interested in design as a mode of caring about the person who will eventually hold the thing you’ve made.

There are also connections to organizational psychology here. Edson’s argument implies that design-led organizations must protect designers from the institutional pressures that inevitably push toward complexity, toward feature accumulation, toward the risk-averse average. That requires a certain kind of leadership culture, one that is willing to absorb the short-term cost of saying no.

Closing Reflection

What makes this book worth sitting with is not any single principle but the insistence that design is an ethical stance as much as an aesthetic one. To design well is to take seriously the experience of another person — to refuse to foist complexity onto them because complexity was easier to produce. That refusal requires courage, organizational will, and genuine curiosity about human life. Apple happened to be extraordinarily good at all three simultaneously. The lesson Edson is really teaching is that this combination can be cultivated, that it is a choice, and that the choice has consequences far beyond the product itself.