Whatever you think of the company, the products are worth studying, because the choices behind them are unusually legible. Very little about them is technically unavailable to competitors. What is hard to copy is the willingness to decide something and then hold the decision across a decade and a dozen product lines.
Subtraction as a design method
The consistent pattern is removal. A port goes, a button goes, a setting that four percent of people used goes. Each removal is unpopular on the day and defensible in aggregate, because every element that survives has to justify the space it occupies against everything else competing for it.
This is genuinely difficult, and not because the design work is hard. It is difficult because inside a large organisation, adding is safe and removing requires someone to absorb the complaints.
The details you are not supposed to notice
Much of the perceived quality lives in places that never appear on a specification sheet — the weight of a hinge, the resistance of a dial, how a box opens, what an animation does when you interrupt it halfway. None of it can be marketed, which is precisely why it functions as a signal. Effort spent where nobody will see it suggests effort elsewhere.
What is actually transferable
The lessons worth taking are not about aesthetics. They are organisational, and they scale down to teams of any size:
- Decide who it is not for. A product that refuses an audience can be excellent for the one it keeps.
- Make the default excellent. Most people never open settings, and a preference is often an unmade decision.
- Own the boundaries. Where hardware, software and service meet is where most products feel worst.
- Be consistent long enough to be learned. A pattern that changes every release never becomes intuition.
The costs are real too
An honest account has to include the trade-offs. Tight integration is also lock-in. Removing an option genuinely strands the people who needed it. Repairability and long-term ownership are recurring, legitimate criticisms. Studying the method does not require accepting the whole package, and the most useful reading treats it as a set of trade-offs someone made deliberately rather than a formula that worked.
Anyone can list what a product does. The harder document is the list of what it will never do, written down and honoured.