What to Improve Upon

6 gaps and opportunities for those learning from Ive's approach


01
Build Functional Feedback Loops

The butterfly keyboard lasted four years. The trash can Mac Pro lasted six. Port removal persisted through multiple product generations. When aesthetic conviction conflicted with user feedback, conviction won, often for too long. The design studio's insularity, which protected fragile ideas, also insulated finished products from valid criticism.

Protect ideas when they are fragile, but test them rigorously when they are finished. Create structured moments where functional feedback from real users can challenge aesthetic decisions before they ship, and especially after. Conviction is a strength. Stubbornness is not.

02
Develop Software Fluency

Ive's iOS 7 redesign demonstrated that hardware design intuitions do not automatically translate to screen-based interaction. Physical objects obey physics; software obeys convention and cognition. The flat design hid calls to action, removed visual affordances, and prioritized visual minimalism over usability. Hardware designers and software designers think differently for good reasons.

Treat hardware and software as distinct disciplines with shared values but different grammars. Don't assume mastery in one transfers to the other. If you lead a hardware team into software, bring software-native collaborators who can translate your principles into the medium's own logic.

03
Question the Thinness Doctrine

Thinness became doctrine rather than tool. Originally, thinness served a purpose: making technology feel effortless and unburdened. But it gradually became an end in itself, sacrificing battery life, thermal performance, repairability, and connectivity. The MacBook Air's thinness was philosophical; the later MacBook Pro's thinness was dogmatic.

Regularly revisit which design principles are serving the user and which have become self-referential. Every principle, no matter how successful, has a domain of validity. Thinness serves the user until it doesn't. The question is always "is this better for the person using it?" not "is this more refined?"

04
Find a Creative Counterweight

The strongest work happened during the Jobs partnership. After Jobs' death, Ive lacked a collaborator who could challenge his aesthetic instincts with equal authority. Tim Cook was an operational genius but not a creative interlocutor. The result was a gradual drift toward aesthetic refinement at the expense of functional innovation.

Seek out a creative partner whose strengths complement your blind spots. Ive's philosophy is rich but it benefits from a counterbalancing voice, someone who can say "that's beautiful, but nobody will use it" and be taken seriously. The best creative relationships are dialectical, not harmonious.

05
Incorporate User Research

Apple under Ive famously did not conduct traditional user research. The team designed for an idealized user whose priorities aligned with their own aesthetic values. This worked brilliantly for consumer products but failed for professional users who needed ports, upgradeable components, and keyboards that survived daily use. The studio's taste was exceptional; its empathy for users unlike itself was limited.

Maintain strong design convictions while creating structured channels for user feedback, especially from users whose needs differ from your own. Taste should lead, but empathy should inform. The question is not "what does the user want?" (that leads to mediocrity) but "what does the user's life actually require?"

06
Address the Succession Problem

When Ive left Apple, the design team's identity was so bound to his personal sensibility that the transition was destabilizing. The team had developed shared intuitions over decades, but those intuitions were calibrated to one person's vision. The philosophy was not codified in a way that could survive his departure without either fossilizing or fragmenting.

Build design culture that transcends any individual. Codify principles (not just aesthetics but the reasoning behind them). Develop multiple creative leaders, not just one. A design culture that depends on a single person is fragile, and fragility in organizations, unlike fragility in ideas, is not a feature.