Jony Ive on care and making

Source: A conversation with Jony Ive, Stripe, 59:05, uploaded 2025-05-08.

What we make records what we value. For Jony Ive, design is therefore less a styling discipline than a visible form of care, including the parts that cannot be measured and the parts nobody is expected to see. The conversation moves from the early Macintosh and Silicon Valley’s lost service ethic, through product and team practice, toward the responsibility a maker retains for unintended harm.

The Macintosh as evidence of values

Ive begins with art school in England and discovering the Macintosh in his final year. The machine did more than demonstrate a useful technology. Every part suggested a group of original thinkers with courage, shared values, and an obsession with people and culture. A product can announce that it was assembled to hit a price and a schedule, or it can embody an attempt to move human capability forward. The Mac gave him the second impression strongly enough that he travelled to California after college to meet the people behind it.

He had been sponsored through college and owed his employer time back in London. That constraint accidentally helped: because he was not asking Californians for a job, his shyness became manageable and meetings carried no hidden agenda. He first visited in 1989, consulted for Apple, and moved there in 1992.

Service before novelty

Ive remembers the 1989–1992 Valley as an “innocent euphoria” of people who could compete while still understanding themselves as servants. The shared purpose was grand but clear: use tools to enable and inspire people. He contrasts that with corporate agendas now organised around money and power, a change he describes as incremental rather than a single betrayal.

Innovation is not difference, speed, or destruction by itself. Breaking an old thing is justified only when it follows from making something better. Progress is not inevitable; it needs an idea, conviction, and the resolve to make that idea real.

A cable tab as contact between strangers

The care argument arrives through an almost absurdly small Sunday-afternoon problem: how to hold and unwrap a cable inside a box. Millions of people would touch the tab. Ive could have described its value as seconds saved across millions of unboxings, but that calculation misses why he was working while he would rather have been with his sons.

The aim was for a stranger opening the box to feel that somebody had considered them. Maker and user would never know one another’s stories or shake hands, yet the object could still transmit love and gratitude. Ive remembers Steve Jobs describing careful making as gratitude to the species.

That is why “function completed” is not enough. A functioning cable package meets an imperative; a considered one records a relationship.

Simplicity, humour, and the maker’s state

The discussion then turns to the humour in products such as the colourful iMacs, the Pixar-like lamp gesture, and even iPod socks. Ive rejects the equation of simplicity with subtraction. Removing clutter can leave a desiccated, soulless object. Simplicity should bring order to chaos and express the thing’s essence, purpose, and role in life.

Joy is often confused with triviality. Ive argues that the emotional state of a team becomes part of its work: anxiety produces anxious products, while hopeful and joyful relations make joyful products possible. Patrick Collison connects this to Daniel Cook’s joke design exercise about turning Super Mario into a princess-saving enterprise application. A purely functional specification forgets that the user is a person who learns and changes, and that software changes them in return.

What metrics omit

Large product groups naturally converge on attributes everyone can compare numerically: schedule, cost, speed, weight, and capacity. Ive gives this a generous interpretation. People use shared numbers because they want to relate, include others, and reach agreement.

The danger comes one step later: because the group spends most of its time discussing measurable attributes, it concludes that only those attributes matter. Ive calls that an insidious lie and a partial truth. Delight, joy, humanity, and trained creative judgment still change whether a product is understood and used.

Calling taste “just an opinion” is no answer. Ive compares it to dismissing a heart surgeon’s judgment before trying the operation oneself. Study does not guarantee good taste, as he jokes, but an informed judgment and an unexamined preference do not carry equal weight.

Collison asks whether speed and quality must trade off. Ive first admits that they sometimes do, then reframes speed as efficiency: the useful question is how to work wonderfully efficiently toward breathtaking quality. The language used to frame the problem constrains the answer before work begins.

Scale, fragile ideas, and team rituals

As an organisation grows, no single person can inspect every decision. Ive treats this as a sequence of seasons rather than a problem solved once. Methods must change, but principles, values, and motivations must not drift unnoticed. His alarm sounds when he asks why he made a decision and discovers the motivation has changed.

Ideas begin as precarious thoughts and tentative conversations. A small team needs enough trust and affection to listen before expressing opinions. Ive draws a hard line here: opinions are not ideas, and eagerness to be heard can kill something valuable before a quiet person has managed to explain it. What frightens him is not the bad idea he rejected but the good one he may never have heard.

“Make things for each other” is his practical team strategy. Designers took turns making Friday breakfast, ranging from ambitious cooking to cornflakes and milk. The quality mattered less than the direction of attention: the maker becomes concerned for colleagues, becomes vulnerable to their judgment, and gives them a reason for gratitude.

The team also took turns hosting a workday at home. Hosts became self-conscious about their furniture; guests behaved differently than they did in a conference room. More importantly, sketching on someone’s floor or coffee table made domestic life present in the design process. A living room makes the eventual user harder to abstract away.

Beauty, humanity, and unseen work

Ive rejects a clean split between function and aesthetics. If an object does not work, its appearance cannot prevent it from being ugly. Taste remains partly subjective, but not all judgments deserve the same weight.

Collison introduces Christopher Alexander’s proposal that, between two alternatives, choose the one that feels more humane. Ive connects humanity to a capacity people already demonstrate in the negative: they can sense carelessness in an object or interface, so it is reasonable that they can also sense care.

This explains his insistence on finishing product interiors. Like the cabinetmaker who finishes the back of a drawer, the team designs what most buyers will never see. Work done only for the visible surface would feel performative. What people do when nobody sees is evidence of what they actually value.

Modernism, materials, and LoveFrom

The conversation briefly tests Ive’s relationship to modernism. Early movements can be energetic and dissonant before they become beautiful. Bauhaus designers had newly learned how to bend metal tubes without kinking them, so they made bent-tube furniture with the delight of people exploring a fresh capability. The material experiment came before mature beauty.

Collison describes Ive’s post-Apple work as an “ornament era.” Ive attributes the broader range less to a conversion than to LoveFrom’s remit. Its team of roughly 50–60 industrial designers, graphic designers, interface designers, architects, typographers, musicians, and sound designers works on problems as different as a coronation identity and iMac instructions. The appropriate language follows the problem.

Responsibility for consequences

Innovation inevitably has unintended consequences, including consequences of products Ive helped make that he describes as far from pleasant. Lack of intent does not remove responsibility. If a maker participates in a harmful outcome, they have to own it.

The Industrial Revolution supplies the comparison. British sewage systems quietly removed waste from streets, and their machinery was housed in cathedral-like pumping stations. Industrial change was immense, but society had time to build physical infrastructure and social frameworks around it. Digital systems move quickly enough that public discussion often arrives after adoption.

This is why Ive is cautiously encouraged that AI safety appears in ordinary AI conversations. His deeper fear about social media was that years passed without serious discussion of its harms. An unspoken problem is harder to address than an acknowledged one.

His current fascination with industrial history also widens the definition of design. Quaker companies such as Cadbury and Fry did not stop at factories; they built housing and towns for workers moving from land to cities. Hershey followed a related model in Pennsylvania. Innovation here became architectural, civic, cultural, political, and spiritual at once.

The final question asks why an infrastructure company such as Stripe should care about design. Ive refuses the separation between a commercial role and an ethical self. We spend much of life working. If that work shows no concern for other people, they suffer and the worker enters a corrosive existence. Care is therefore obligation and privilege, not polish reserved for consumer products.

Further reading / references

• Christopher Alexander’s preference for the more humane of two alternatives.
• Sigmund Freud’s formulation of love and work as the central contents of life.
• Related: Bauhaus truth to material, The Design of Everyday Things, the revolt against technology.