What this covers

This is a solo episode in which David Senra works through Ken Kocienda's account of building software at Apple under Steve Jobs, including the iPhone and the Safari browser. Senra traces how the work actually moved: from a problem to a design to a demo to a shipped product, with no handbook behind it. Every major iPhone feature began as a demo, and ideas had to be shown rather than described. Jobs attended reviews, asked for specific next steps, and gave final approval. Access to those meetings depended on contributing something useful.

The range goes beyond process. Senra covers simplicity, meaning the stripping away of features because no one will stand over a user's shoulder explaining the product. He covers designing for an imagined customer, such as a busy mother with a sick teenager, and Jobs's single measure for Safari, which was speed compared with Internet Explorer. He also notes Jobs's habit of rehearsing keynotes for weeks, and the idea that every touchpoint, from using a Mac to calling support, adds to or subtracts from a company's reputation. The Seagull Manager, the executive who flies in, decides, and leaves a mess, serves as the foil.

The contested turns come when Senra says Google's data-driven design factored taste out of decisions, leaving doubt where instinct should be, and that product design cannot be derived from data alone. He also borrows from Vince Lombardi, whose Packers perfected one running play, and from Jobs's advice to move on after a success or a failure alike.

Sharpest takeaway

Kocienda's account of Apple's software process shows that Steve Jobs's founder taste and rapid, concrete demos drove great products, and the host argues this is the opposite of data-driven design.

  • Apple iterated through concrete demos reviewed by Steve Jobs, not through abstract meetings or specifications
  • Jobs's personal taste and decisiveness replaced A/B testing and data-driven choices
  • Simplicity and removing nonessential features came from imagining the customer's experience

The claims · ranked46 claims · weighted by value

This asset isn't compiled yet

You're seeing its claims, ranked. Compile it to build the argument threads, weight them, and check each claim against your library — the full view.

0.80

Stripping away nonessential features makes products easier to learn at first use and easier to use over time, because nobody will be standing over a user's shoulder explaining the product.

normativehigh valueestablishednovelty 2/4durability 4/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“He realized that nobody would be standing over the shoulder of a person who is having their first experience with software, carefully describing every nuance of every feature.”

0.76

Apple's success came as much from what it did not do as what it did, because avoiding typical Silicon Valley traps such as talking about projects without examples and separating research from product teams kept the team focused.

normativehigh valueestablishednovelty 2/4durability 4/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“Consequently, our success was as much about what we did not do as what we did.”

0.73

Apple's approach to work was not written in any company handbook or orientation; it flowed from the work itself and came top-down from Jobs's unquestioned authority and uncompromising vision, moving stepwise from problem to design to demo to shipped product rather than relying on Eureka moments.

causalhigh valuecontestednovelty 3/4durability 3/4· David Senra

“We never waited around for brilliant flashes of insight that might solve problems in one swoop, and we had very few actual Eureka! moments.”

0.70

Good product decisions come from imagining a specific customer, such as a busy mother juggling work and a sick teenager, and designing for her rather than for the engineers building the product.

normativehigh valueestablishednovelty 1/4durability 4/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“Steve could put himself in the shoes of customers, people who care nothing for the ins and outs of the software industry.”

0.70

Jobs began rehearsing his keynote slides three weeks to a month before a big product announcement, building the show day by day until he knew it cold, and this practice was a core reason he was a strong presenter.

factualhigh valueestablishednovelty 1/4durability 4/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“Three weeks or a month before the keynote itself, Steve would start rehearsing with portions of his slide deck.”

0.68

Google's data-driven design process factored taste out of decisions, so that when a company lacks a leader who understands design principles it eventually runs out of reasons for design decisions and doubt replaces instinct.

causalhigh valuecontestednovelty 2/4durability 3/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“Without conviction or without taste, doubt creeps in, instincts fail.”

0.61

More data will never be enough for building great products; a company needs conviction and a point of view, because product design is not scientific and cannot be derived from data alone.

normativehigh valuecontestednovelty 2/4durability 3/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“More data will never be enough. You need conviction. You need a point of view.”

0.60

Apple's products were built at the intersection of technology and the liberal arts, so they would be both advanced and intuitive, and the users should not have to come to the product because the product comes to the user.

normativehigh valuespeaker onlynovelty 3/4durability 4/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“The reason that Apple is able to create products like the iPad is because we've always tried to be at the intersection of technology and liberal arts.”

0.60

Every customer interaction with a company either adds to or subtracts from its reputation, so one bad experience can undo dozens or a hundred positive ones, which is why Jobs insisted that every touchpoint from using a Mac to calling support to buying a song be excellent.

causalhigh valuespeaker onlynovelty 3/4durability 4/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“A corporation could 'accumulate or withdraw' credits from its reputation”

0.57

At Apple, demos were the primary means of turning ideas into software: every major iPhone feature started as a demo, and demos had to be concrete and specific because an unsophisticated idea is hard to discuss without an artifact to illustrate it.

causalhigh valuespeaker onlynovelty 3/4durability 3/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“Every major feature on the iPhone started as a demo and for a demo to be useful to us, it had to be concrete and specific.”

0.56

Jobs demonstrated that software quality was a real corporate priority by attending demo reviews whenever interesting new work appeared, because his time was valuable and his presence showed what mattered.

normativehigh valuespeaker onlynovelty 2/4durability 4/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“He's showing through his actions what's important. His time is extremely valuable”

0.56

Jobs could trust his own judgment by the time of these decisions because he had two to two-and-a-half decades of practice designing products, which is how he worked himself into a position to decide quickly.

causalhigh valuespeaker onlynovelty 2/4durability 4/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“I know that I -- like especially at that point in his career, he has had two, maybe two-and-a-half decades of practice and experience”

0.56

Lombardi built the Packers' rise by fixating on one running play, the power sweep, practicing it for hours across seasons until opponents who knew it was coming still could not stop it, showing that perfecting one thing creates outsized results.

causalhigh valuespeaker onlynovelty 2/4durability 4/4· David Senra

“Even though opposing teams knew the play was coming, they couldn't stop it.”

0.56

Jobs demonstrated what was important through his actions, especially how he spent his scarce time, and this is one of the best maxims: actions express priorities.

normativehigh valuespeaker onlynovelty 2/4durability 4/4· Unidentified Speaker (Host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“He's showing through his actions what's important. His time is extremely valuable”

0.56

Clarity of purpose kept Apple on track, and concentrating on what to do may help block out what not to do, the same way Vince Lombardi focused the Packers and Jobs pushed for a fast first Safari.

causalhigh valuespeaker onlynovelty 2/4durability 4/4· Unidentified Speaker (Host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“perhaps concentrating keenly on what to do helped us block out what not to do.”

0.56

Great products make people happy almost all the time and rarely do the opposite, and excellent user experience is as much about preventing negative experiences, such as confusing overlapping features, as about creating positive ones.

normativehigh valuespeaker onlynovelty 2/4durability 4/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“Designing an excellent user experience was as much about preventing negative experiences as facilitating positive ones.”

0.53

Jobs argued that after doing something great you should move on to the next thing without dwelling on it, and Kocienda found this approach worked equally well after a failure as after a success.

normativehigh valuespeaker onlynovelty 2/4durability 4/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“I think if you do something, and it turns out pretty good, then you should go do something else wonderful and not dwell on it for too long. Just figure out what's next.”

0.53

Jobs pushed for simplicity by asking succinct questions to make software simpler, because customers, even busy people who care nothing for software, should not be overloaded with features.

normativehigh valuespeaker onlynovelty 2/4durability 4/4· David Senra

“He never wanted Apple software to overload people, especially when they might already be stretched by the bustle of their everyday lives.”

0.52

Steve Jobs made the important product decisions by reviewing demos personally, asking for specific next steps, and giving final approval before shipping, so he could make a product turn out the way he wanted.

factualhigh valuespeaker onlynovelty 2/4durability 3/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“Steve was at the center of all circles. He made all the important product decisions. He used these demo reviews as his chief means of deciding how Apple software should look and feel and function.”

0.52

Detached top executives who fly in occasionally, make key decisions, and leave a mess for the team to clean up, the so-called Seagull Manager, are a widespread affliction that undermines product work, whereas Jobs stayed deeply engaged.

normativehigh valuespeaker onlynovelty 2/4durability 3/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“A detached high-level manager making all the key decisions is such a widespread affliction.”

0.52

Jobs insisted that work should speak for itself, telling an Apple ad creative to stop explaining the concept and just show the ads, because he would experience them the way customers would.

factualhigh valuespeaker onlynovelty 2/4durability 3/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“Then shut up. I don't want to hear it. I'm going to experience it like the customer is going to experience.”

0.52

Jobs gave the Safari team one measure of success, speed, requiring the browser to be much faster than Microsoft Internet Explorer because speed was the long-term key to better browsing and a fast first impression would win customers.

normativehigh valuespeaker onlynovelty 2/4durability 3/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“The focus would be on one thing, speed. Steve wanted our browser to be fast, to be really fast, much faster than Microsoft Internet Explorer”

0.52

The iPhone team required that ideas be demonstrated rather than described, so no one could get away with telling; feedback was given on each other's demos, creating a virtuous collaborative cycle.

normativehigh valuespeaker onlynovelty 2/4durability 3/4· Unidentified Speaker (Host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“We couldn't get away with telling. We were required to show.”

0.52

Access to Steve Jobs's demo meetings was conditional on making substantive contributions to the discussion; if he judged that you had no valuable insight, you would not be invited back.

normativehigh valuespeaker onlynovelty 2/4durability 3/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“You have to make substantive contributions to discussion with him as a way -- that's the way to earn future invitations.”

0.51

Design is not what a product looks like; it is how it works, and beauty that is only visual does not serve people, so form should follow function and objects should explain themselves.

definitionhigh valuespeaker onlynovelty 2/4durability 4/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“Most people make the mistake of thinking design is what a product looks like.”

0.51

Taste can be developed by studying great work from the past, comparing and contrasting it with your own judgments, and building a catalog of refined responses that later surface in present-day work.

normativehigh valuespeaker onlynovelty 2/4durability 4/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“When I study the past, I make a point of deciding what I like, and sometimes this built-up catalog of refined like responses about past works, find a suitable outlet”

0.51

Google tested 41 shades of blue to see which performed better, and Kocienda argues that more data is not automatically better, since testing 100 or 1,000 shades would only deepen the reliance on data over judgment.

factualhigh valuespeaker onlynovelty 3/4durability 2/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“if they were willing to go that far at Google, why not test for 100 or 1,000. If some data is good, more must be better, right?”

0.50

The sooner a team starts making creative decisions, the more time it has to refine, backtrack, or push forward, so early concrete decisions are a compounding advantage.

causalhigh valuespeaker onlynovelty 2/4durability 3/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“The sooner we started making creative decisions, the more time there was to refine and improve those decisions”

0.50

Even an unsophisticated idea is hard to discuss constructively without an artifact to illustrate it, so teams should show rather than tell, and the Purple (iPhone) team accepted nothing that was not concrete and specific.

normativehigh valuespeaker onlynovelty 2/4durability 3/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“We couldn't get away with telling. We were required to show.”

0.50

Jobs's demo verdicts were easy to understand: he would either approve a demo or request something different next time, and while his moods were hard to predict, his passion for products was utterly predictable.

factualhigh valuespeaker onlynovelty 2/4durability 3/4· Unidentified Speaker (Host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“He would either approve a demo or he would request to see something different next time.”

0.50

Apple never ran A/B tests on iPhone software and picked colors using good taste, which let Jobs approve new iMac colors in half an hour when other companies would have taken months.

factualhigh valuespeaker onlynovelty 2/4durability 3/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“Steve did it in a half-hour.”

0.49

Steve Jobs disbanded Apple's Advanced Technology Group after reasserting control in 1997, and separating software research from the designers and engineers shipping products blocks the steady accumulation of demos.

factualestablishednovelty 2/4durability 3/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“Steve Jobs famously disbanded such an organization at Apple, which is called the Advanced Technology Group, surely after he reasserted control over the company in 1997.”

0.49

Steve Jobs asked Ken Kocienda to choose between two iPad keyboard designs, and when Ken explained he had been using the bigger-key layout and thought people could learn to touch type on it, Jobs decided in four sentences, 'We'll go with the bigger keys.'

factualhigh valuespeaker onlynovelty 2/4durability 2/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“'Okay. We'll go with the bigger keys.' That was it. The Oracle of Apple had spoken, the demo was over.”

0.41

Warren Buffett's line that intensity is the price of excellence captures the demanding standard Steve Jobs held, which the host argues is central to Apple's pursuit of insanely great work.

normativeestablishednovelty 0/4durability 4/4· David Senra

“Intensity is a price of excellence.”

0.38

Ken Kocienda realized from his manager Henry's phrase 'at this point' that Jobs was not coming back to review the multitasking gestures, and about six weeks later Jobs resigned as CEO and within another six weeks was gone.

factualestablishednovelty 1/4durability 2/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“then it hit me, Henry knew. Steve wasn't coming back.”

0.34

Jobs took Edwin Land's idea about the intersection of technology and liberal arts, built Apple around it, repeated it throughout the company, and taught everyone why it mattered, which shows how an idea can be institutionalized.

causalspeaker onlynovelty 2/4durability 3/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“Steve took one of Edwin Land's ideas and built his company around it and then repeated it and made sure he taught everybody else in the company, why this is important.”

0.34

Creative Selection by Ken Kocienda describes his 15 years at Apple, including his software work and observations on Steve Jobs, and argues that Apple's design process was an intense school of stepwise, demo-driven product creation.

definitionestablishednovelty 0/4durability 4/4· David Senra

“Every day at Apple was like going to school, a design-focused, hi-tech product creation university.”

0.34

Jobs's unblinking gaze could intimidate people, and the host has heard dozens of stories about this intensity across roughly ten books on Jobs.

factualestablishednovelty 1/4durability 2/4· Unidentified Speaker (Host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“he wouldn't blink, I've heard like dozens of stories about this in the 10 or so books I read on him.”

0.33

In any complex effort, communicating a well-articulated vision is the starting point for figuring out how to achieve it, and this vision-to-action sequence is what closes the gap between accidental and intentional results.

normativespeaker onlynovelty 1/4durability 4/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“in any complex effort, communicating a well-articulated vision for what you're trying to do is the starting point for figuring out how to do it.”

0.30

Making demos is hard because it requires committing time to an idea you are not sure is right, and most demos fail outright, which makes the psychological hurdle grow with experience of failure.

factualspeaker onlynovelty 1/4durability 3/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“Making demos is hard. It involves overcoming apprehensions, about committing time and effort to an idea that you are not sure is right.”

0.21

Of all the people the host has covered, Steve Jobs is the clearest thinker, and his clarity of thought is the trait the host admires most and finds hardest to understand.

normativespeaker onlynovelty 1/4durability 2/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“If I had to say the single trait I admire the most about him and the one that I don't even understand how it's capable that he was able to do it, is his clarity of thought.”

0.17

Anybody building a product should read Creative Selection, because it explains how Apple's demo-driven, taste-led process produced great products and is a no-brainer recommendation.

normativespeaker onlynovelty 0/4durability 2/4· Unidentified Speaker (Podcast host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“Anybody building a product should read this book. It should be in your library.”

0.17

Becoming Steve Jobs is the best single biography of Steve Jobs if a reader can only read one.

normativespeaker onlynovelty 0/4durability 2/4· David Senra

“if you only had to read one, that'd be Becoming Steve Jobs”

0.17

The host has read Creative Selection three or four times and returns to it because each reading surfaces new material on Jobs's process.

factualspeaker onlynovelty 0/4durability 2/4· David Senra

“That is an excerpt from a book that I've read three or four times now”

0.13

The host uses Readwise to store over 20,000 highlights from books and recommends it, with a free 60-day trial.

normativespeaker onlynovelty 0/4durability 1/4· Unidentified Speaker (Host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“I have over 20,000 highlights from the books I read”

0.13

Not numbering the Founders bonus episodes was a mistake because it makes past episodes hard to reference, and the podcast is treated as one 400-hour conversation.

factualspeaker onlynovelty 0/4durability 1/4· Unidentified Speaker (Host) — #281 Working with Steve Jobs [colossus_senra-281-working-with-steve-jobs]

“not numbering the bonus episodes was a giant mistake”