How Steve Jobs built great products through demos and taste

Executive overview

Most product teams debate ideas in meetings without anything concrete to react to. At Apple, every decision flowed through working demos reviewed by Steve Jobs himself — no specs, no A/B tests, just a prototype and a verdict.

Ken Kocienda's 15 years at Apple reveal the operating system beneath the products: a relentless demo cycle driven by Steve's clarity, taste, and personal involvement.

Great products come from taste and conviction, not data — and from a founder who is present, not detached.

The demo as the engine of product development

• Every major iPhone feature started as a demo; demos were the only accepted currency for ideas
• Demos had to be concrete and specific — telling was not allowed, only showing
• Steve would review demos regularly and always state exactly what he wanted next, in four sentences or fewer
• The sooner a team started making creative decisions via demos, the more time remained to refine them
• Almost all demos fail — the psychological hurdle is committing time to an idea you're not sure is right
• Steve's involvement kept momentum going; his presence signalled what mattered

Steve's decisiveness and clarity

• Steve was unpredictable in mood but utterly predictable in his passion for great products
• When reviewing the iPad keyboard demo, Steve heard two options, asked one question, and chose in seconds: "Okay, we'll go with the bigger keys"
• He spoke four sentences in that meeting yet taught Kocienda more than hours of discussion could
• His unblinking focus was a signal: he would not let anything slide
• He treated the demo creator as the expert and asked directly: "Which one do you think we should use?"

One priority, not ten

• For Safari, Steve gave the team a single rule: the browser must be fast — faster than Internet Explorer
• Speed was the definition of greatness for that product; everything else was secondary
• Lombardi's power sweep analogy opens the book: winning is built on perfecting one well-chosen thing, not covering everything
• Focus is about saying no; Apple's success was as much about what they did not do

Putting yourself in the customer's shoes

• Steve imagined a specific customer — a busy mom, running late, distracted — to pressure-test every design decision
• Nobody will be standing over the user's shoulder explaining features; software must be intuitive from the first touch
• When reviewing ads, Steve refused to hear the thinking behind them: "Are you going to be there when I see it on a billboard?"
• Stripping non-essential features makes products easier to learn and easier to use over time

Taste vs. data: the Apple–Google contrast

• Google tested 41 shades of blue to pick a link colour; Apple picked one shade and moved on
• When a company lacks a design authority, doubt creeps in and data becomes a crutch for every decision
• Steve trusted his own taste — formed over decades of practice — and moved fast; Johnny Ive's colour approvals that would take other companies months took Steve half an hour
• Data can confirm; it cannot originate a point of view

Design is how it works

• Steve's definition: "Design is not what it looks like and feels like. Design is how it works."
• Shallow visual beauty does not serve people; form should follow function
• Objects should explain themselves — no manual, no shoulder-tap required
• Every customer interaction either deposits or withdraws from a company's reputation; one bad experience can undo dozens of good ones

What Apple deliberately avoided

• No discussions without a concrete demo to ground them
• No paper mock-ups shuffled for weeks without progress
• No senior leaders making decisions without personal engagement (the "seagull manager" anti-pattern)
• No research departments disconnected from shipping teams — Steve disbanded Apple's Advanced Technology Group in 1997
• No A/B testing for product design choices on the iPhone

Technology at the intersection of liberal arts

• Steve inherited this idea from Edwin Land (Polaroid) and made it a core operating principle at Apple
• The goal: products so intuitive they come to the user, not the other way around
• Apple ran an internal university course on this intersection; Steve repeated it publicly from his 20s until his final keynote
• Studying great work from the past calibrates taste — it provides the means of comparison and contrast

Practice and preparation

• Steve began rehearsing keynotes three to four weeks out, building the show day by day
• He went over material until he knew it cold — practice was the secret behind his reputation as a presenter
• After a success or a failure, his instinct was the same: figure out what's next, don't dwell

The end of an era

• Kocienda's last demo with Steve never happened; his manager's words — "at this point" — told him Steve wasn't coming back
• Six weeks later Steve resigned; six weeks after that he was gone
• His legacy: single-minded focus on great products and a vision that motivated everyone around him