Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
Creative Selection

Creative Selection

Inside Apple's Design Process During the Golden Age of Steve Jobs
How did Apple turn rough software demos into products millions could use?
by Ken Kocienda 2018 264 pages
4.05
5k+ ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Build a convincing slice before committing months to the wrong foundation.

A demo can reveal direction. When Ken Kocienda and Don Melton spent six weeks trying to get Mozilla running on a Mac, they had no working browser and no clear path forward. New teammate Richard Williamson instead took two days to adapt a different open-source browser, Konqueror, enough to load pages, follow links, and go back. A software shim and a couple of shortcuts made the demonstration possible. Its rough edges were visible, but the demo showed the team that the underlying technology could work on a Mac.

Test potential before polishing. Richard did not prove that Konqueror was ready to ship. He made the smallest convincing case that it was worth pursuing. That distinction let the team stop guessing and choose a direction with evidence.

Analysis

What's striking is that the demo changed the team's question from how to make an enormous project work to whether this smaller, promising foundation could be developed further. This resembles a well-designed experiment: reduce uncertainty before investing heavily. In contemporary product work, a prototype can expose both technical risk and user misunderstanding early. The method has a limit, though. A persuasive demonstration can make an unproven system look more complete than it is. Its value depends on being clear about what the demo establishes, and what remains unsolved.

Polish the core interaction, and let the rest remain scaffolding.

Give attention to the load-bearing parts. Kocienda compares software demos to movie backlots. In Singin’ in the Rain, the storefronts could be convincing façades, but the lamppost Gene Kelly climbs had to hold his weight. A demo has the same division: its central interaction must feel real enough to judge, while background elements can be borrowed, simplified, or omitted if they do not distract.

Match effort to purpose. A prototype for a new email preference screen might use an image from an existing app rather than a working settings system. That is useful if the review concerns the main editing experience. The key is to identify what the audience must evaluate, make that part convincing, and avoid spending scarce time perfecting details that cannot affect the decision.

Analysis

This is a practical theory of fidelity: realism is not a virtue everywhere, but a resource to spend where it changes what people can learn. It aligns with experimental design, where a test isolates the variable under investigation instead of recreating the whole world. The danger is that a convincing shell can conceal dependencies that later prove central. A disciplined prototype therefore needs explicit boundaries: which parts are real, which are stand-ins, and what conclusions the demonstration can legitimately support.

Pair bold ideas with a task list that makes progress visible.

Inspiration needs a route forward. After choosing Konqueror, the Safari team had to adapt about 120,000 lines of code spread across roughly 300 files. Their plan was to repair broken connections until the code built, mark uncertain areas with FIXMEs, and then use those markers to guide debugging. The compiler produced a long sequence of small errors, and the first visible result was a black rectangle where a web page should have appeared.

Turn drudgery into steps. The team kept fixing errors and working through FIXMEs until the browser displayed text, links, and images. The early demo had pointed toward possibility; the methodical porting work made that possibility concrete. The lesson is not simply to work harder, but to make the next unit of effort identifiable and finishable.

Analysis

The black rectangle is a memorable reminder that meaningful progress can precede satisfying progress. A plan converts vague effort into observable evidence, which helps teams persist through stretches when the outcome remains hidden. This also clarifies why diligence is not blind endurance: the work was organized around compiler errors and logged uncertainties. Checklists can still become rituals detached from results, so each milestone should answer a useful question about the system, rather than merely record activity.

Measure the promise you made, not just the code you shipped.

Make the priority testable. Steve Jobs wanted Apple’s new Mac browser to be faster than Internet Explorer. Don built the Page Load Test, a program that made Safari load 40 selected websites and calculated the average load time. The pages varied in content and complexity, from text-heavy destinations to graphic-rich ones, so the test could expose different performance problems.

Protect the goal in daily work. Don required the team to run the test before accepting code changes. If a feature made the browser slower, developers had to find a way to recover that lost speed, sometimes by improving stable, well-understood code elsewhere. The test turned a broad ambition into a recurring engineering constraint, and Safari launched with speed as a central, measurable advantage.

Analysis

A shared measure can make a strategic promise operational: engineers can see whether a change advances or undermines it. This is useful beyond software whenever a team needs to preserve a quality across many local decisions. But a benchmark is a proxy, not the whole experience. If page-load time became the only definition of browser quality, accessibility, compatibility, or reliability could be sacrificed. Metrics work best when paired with human review and a clear account of what they leave out.

Make a decision, then remove choices customers should never have to make.

A review should close a question. For the iPad, Kocienda and designer Bas Ording demonstrated two keyboard layouts: one offered more small keys, while the other used fewer, larger keys. Steve Jobs asked Kocienda which one he thought was better. Kocienda chose the larger keys, and Jobs approved that option.

Simplicity has consequences. Choosing one layout also removed the need for a zoom button, an animation, and decisions about when the system should remember a user's preferred keyboard. The demonstration had shown both options, but the shipped design did not need to preserve every experiment. At Apple, review meetings had designated decision-makers, and the work moved forward through clear approvals rather than indefinite discussion.

Analysis

The episode shows decisiveness as a design tool, not merely a leadership style. Selecting one option can eliminate secondary controls and future edge cases, reducing the burden on both users and developers. Yet simplicity should not be confused with minimizing options for its own sake. The choice worked because the team had built and tried both layouts, and the engineer could explain his preference. Authority is most productive when it concentrates informed judgment, not when it replaces evidence or silences dissent.

Treat technical dead ends as invitations to collaborate.

A fresh perspective can expose the real bug. While adapting WebKit so Apple Mail users could edit web-based email, Kocienda struggled for months with insertion-point errors. The blinking cursor sometimes disappeared, jumped, or failed to move consistently. He called these unpredictable failures heisenbugs. The tangled HTML format, where page content and formatting instructions are mixed together, made the problem especially difficult to reason about.

Make the problem visible. Kocienda eventually walked colleagues Darin Adler and Trey Matteson through his diagrams and failed cases. They saw that he was concentrating on the underlying data instead of guaranteeing the visual behavior users needed. They advised organizing the logic around a single representation, called VisiblePosition. Their guidance helped him make progress, and follow-up demonstrations showed them that their advice mattered.

Analysis

The breakthrough came from combining a detailed account of the failures with colleagues able to reinterpret the problem. That is a form of distributed reasoning: expertise becomes more powerful when people can inspect one another's models, not just exchange conclusions. Asking sooner may preserve time, but it also requires enough trust for a capable person to admit uncertainty. Collaboration is not an automatic cure; it works best when the problem is concrete, the advice can be tested, and credit is shared.

Keep familiar cues, but let software absorb the user's imperfect touch.

The first keyboard idea was not the final one. During an urgent iPhone keyboard effort, Kocienda tried large keys that grouped several letters together. The design was easier to tap, but it confused typists: uncommon names were missing from the dictionary, and people lost their place while composing longer words. He returned to single-letter QWERTY keys, a layout users already knew, and let autocorrection interpret taps that landed near the intended letters.

Test how assistance feels. In one prototype, colleague Richard Williamson typed rapidly and made many inaccurate taps, yet the software produced the sentence he intended. That discovery encouraged always-on autocorrection. The keyboard balanced recognizable letter positions with software help, while retaining a way to enter unusual words rather than forcing every attempt into the dictionary.

Analysis

The design succeeds by dividing labor: familiar layout lowers the learning burden, while software absorbs some motor error. This is a strong example of assistive design that supports rather than replaces intention. It also exposes a delicate trust problem. A correction that is helpful most of the time can feel intrusive if the system confidently changes an unusual name or playful spelling. Familiarity is not proof that QWERTY is ideal, but changing a learned convention carries costs that a technically elegant alternative may underestimate.

Turn demos into products through repeated judgment, revision, and small-team ownership.

Creative selection is a working cycle. Kocienda uses this term for repeatedly building a demo, gathering feedback, choosing what to keep or change, and making the next version. The process combined imagination, collaboration, craft, patient execution, timely decisions, taste, and attention to users. On the original iPhone, this meant using technical algorithms alongside human judgments about animation, touch, and what felt intuitive.

Keep the people close to the work. Small groups let designers, programmers, and decision-makers review concrete progress together. They tested ideas by living with the software, not only by discussing it. For example, the team found that a suggestion bar above the iPhone keyboard added another place to look, so removing it modestly improved typing speed. The result emerged through accumulated choices, not one master plan.

Analysis

The framework's strength is its connection between creative judgment and executable work: taste does not remain a slogan when each review leads to a specific revision. It also resists two common extremes, treating design as decoration or treating data as the sole authority. The account is rooted in a company with unusually direct executive involvement and small teams, conditions many organizations cannot reproduce wholesale. The transferable principle is a cadence of visible work, candid critique, and accountable decisions, adapted to the constraints of each setting.

Analysis

Creative Selection is both a product-development memoir and an argument about how ideas become reliable experiences. Its central unit is not the brainstorm or the finished product, but the demo: a shared object that makes an abstract proposal concrete enough to test, criticize, and change. This matters because people often disagree productively only after they can point to the same thing. The book's best examples show prototypes doing double duty as technical experiments and social instruments. Richard Williamson's browser demo redirected a stalled project; the iPhone keyboard demos allowed the team to discover that a clever design could still confuse its users.

The method can be understood as a disciplined search through a changing design space. Teams generate a candidate, expose it to knowledgeable critics, preserve its useful features, and modify the next version. Measurement supports this search when the target is objective, as with browser speed. Human judgment matters when quality depends on perception, context, and fit. The argument is persuasive because it does not claim that every decision can be quantified, nor that taste excuses technical weakness. It shows the two modes correcting each other.

The account also makes organizational power part of the method. Steve Jobs's frequent reviews and clear decisions created focus, but the same authority could be intimidating, and the process depended on managers who filtered pressure and selected who could contribute. A reader should therefore separate the productive mechanisms from the mythology of a singular leader. Small teams, fast prototypes, explicit decision rights, and visible accountability can be built without copying one executive's temperament.

There is a further limitation: a successful product story can make a process appear more coherent in retrospect than it felt during development. Kocienda's examples help counter this by showing abandoned keyboards, failed approaches, and long stretches of invisible labor. Even so, creative selection does not guarantee a socially beneficial outcome or a market success. It improves the quality of learning and execution. The purpose that guides the selection still deserves independent scrutiny.

Summary in 30 Seconds
A working demo makes an abstract idea concrete enough for a team to test, critique, and improve. Build only the parts reviewers need to judge, then break the work into visible tasks: adapting a browser involved about 120,000 lines across 300 files. Turn priorities into measurable tests, such as checking load times across 40 websites. Small teams, direct feedback, and clear decision rights help ideas improve through successive versions, while user judgment complements technical measures.
Contains spoilers

Last updated:

Report Issue

Review Summary

4.05 out of 5
Average of 5k+ ratings from Goodreads and Amazon.

Creative Selection receives mostly positive reviews, praised for its insider's view of Apple's product development process. Readers appreciate the detailed anecdotes about creating Safari, the iPhone keyboard, and other projects. Some criticize the book for oversimplifying technical concepts and lacking a broader perspective. The author's writing style is generally well-received, though some find it repetitive. Many readers value the insights into Apple's demo-driven, iterative approach and the emphasis on user experience. Overall, it's recommended for those interested in Apple's software development practices during the Steve Jobs era.

Your rating:
4.48
355 ratings
Want to read the full book?

Glossary

Creative selection

Demo-driven product iteration

Kocienda's term for developing a product through repeated cycles of making a concrete demonstration, reviewing it, selecting changes, and producing another version. Each round allows a team to test its assumptions and accumulate improvements. The process combines technical work with design judgment, rather than separating engineering from the experience users encounter.

Page Load Test (PLT)

Browser speed benchmark

An automated Safari test that loaded a selected set of 40 websites and calculated an average page-loading time. The team ran it as code changed, using the result to detect performance regressions. It converted the goal of building a fast browser into a repeatable measure that informed daily engineering decisions.

Convergence

Final bug-fixing phase

The late stage of product development when the intended features and design are largely settled and teams focus on fixing defects and polishing details before release. Kocienda describes tracking this work through bug reports and trends. Convergence does not mean software becomes faultless; it means the team decides the product is ready to ship.

Directly responsible individual (DRI)

Person accountable for delivery

The person responsible for doing what is necessary to deliver a defined piece of hardware, software, or other work. At Apple, taking on a project as its DRI meant accepting ownership rather than merely contributing suggestions. The role made responsibility legible, while leaving room to seek help and collaborate.

heisenbugs

Intermittent software defects

Unpredictable bugs whose behavior does not reliably recur when a programmer repeats the same steps. Kocienda uses the term for insertion-point failures in his WebKit editing work, including cursors that vanished or jumped unexpectedly. Their inconsistency made them difficult to diagnose and pushed him to seek a more organized model of the behavior.

Pattern skew algorithm

Touch-pattern matching method

Kocienda's autocorrection technique for comparing a person's touchscreen taps with idealized patterns for dictionary words. It measured how far the taps would need to shift to match each candidate pattern, then used that fit alongside word frequency to rank suggestions. The method helped the keyboard interpret imperfect taps without requiring a separate gesture for each letter.

Usage frequency value

Word popularity ranking

A value assigned to dictionary entries to represent how common each word is in ordinary writing. The iPhone keyboard used these values to rank possible autocorrections, preferring a common word over a rare alternative when the tap pattern was ambiguous. Incorrect values or missing entries could produce bizarre corrections, even when the underlying algorithm functioned as intended.

heuristics

Judgment-based interaction rules

Rules that guide software behavior when there is no single objectively correct answer. In Kocienda's account, choosing how a gesture should feel, how an animation should behave, or when autocorrection should intervene required evaluation through prototypes and user experience. He contrasts these judgments with algorithms, whose results can be assessed against a defined quantitative or logical outcome.

FAQ

What's Creative Selection about?

  • Author's Experience: Creative Selection is a memoir by Ken Kocienda, detailing his 15 years at Apple during the transformative period under Steve Jobs. It focuses on the software development process and the culture that led to the creation of iconic products like the iPhone and iPad.
  • Software Development Insights: Kocienda shares his experiences as a software engineer, highlighting the unique methods and collaborative spirit that defined Apple's approach to product creation.
  • Seven Essential Elements: The book outlines seven key elements that contributed to Apple's software success: Inspiration, Collaboration, Craft, Diligence, Decisiveness, Taste, and Empathy.

Why should I read Creative Selection?

  • Behind-the-Scenes Perspective: Readers gain an insider's view of Apple's design and development processes, particularly how software engineers contributed to the company's innovative products.
  • Lessons on Collaboration: The book emphasizes the importance of teamwork and collaboration in achieving great results, making it relevant for anyone interested in effective group dynamics.
  • Inspiration for Creatives: For aspiring designers and engineers, Kocienda's journey serves as motivation to pursue excellence and creativity in their work.

What are the key takeaways of Creative Selection?

  • Importance of Demos: Demos are crucial in the software development process, serving as a means to showcase potential and drive decisions.
  • Focus on User Experience: The book highlights the need for empathy in design, urging developers to consider the user's perspective when creating software.
  • Iterative Development Process: Kocienda discusses the iterative nature of software development, where continuous feedback and refinement lead to better outcomes.

What are the best quotes from Creative Selection and what do they mean?

  • "We only need one of these, right?": This quote from Steve Jobs during a demo illustrates his decisiveness and focus on simplicity in product design.
  • "None of my inventions came by accident.": Reflects Thomas Edison’s philosophy that hard work and persistence are key to innovation.
  • "People matter more than programming.": Underscores the significance of collaboration and communication in successful software development.

What is the Creative Selection method?

  • Definition: "Creative selection" is the process of combining inspiration, collaboration, and craftsmanship to develop innovative software.
  • Seven Essential Elements: Built on seven elements: Inspiration, Collaboration, Craft, Diligence, Decisiveness, Taste, and Empathy.
  • Practical Application: These elements were applied in real projects at Apple, contributing to the success of products like the iPhone.

How did Ken Kocienda contribute to the iPhone's development?

  • iPhone Keyboard Development: Kocienda was responsible for creating the software for the iPhone's keyboard, including the autocorrect feature.
  • Demos to Steve Jobs: He describes the pressure of presenting his work to Steve Jobs, who had high expectations for product functionality and user experience.
  • Iterative Refinement: His work involved continuous testing and refinement based on feedback from demos, leading to a functional and user-friendly keyboard.

What challenges did Ken Kocienda face while at Apple?

  • High Expectations: Kocienda faced immense pressure to deliver high-quality software under tight deadlines, often feeling the weight of Steve Jobs' demanding standards.
  • Secrecy and Competition: Working on secret projects like the iPhone and iPad meant navigating a culture of secrecy while competing with other teams for resources.
  • Technical Hurdles: He encountered numerous technical challenges, particularly with the iPhone keyboard and web page editing features.

How did Kocienda's approach to software development differ from traditional methods?

  • Emphasis on Demos: Unlike traditional methods, Kocienda's approach focused on the importance of demos as a means of communication and decision-making.
  • Iterative and Collaborative: His method was iterative, allowing for continuous feedback and improvement rather than a linear development process.
  • User-Centric Design: Prioritized user experience and empathy, ensuring that software was intuitive and met the needs of users.

What role did Steve Jobs play in the development process at Apple?

  • Visionary Leadership: Steve Jobs provided a clear vision for Apple's products, setting high standards for quality and user experience.
  • Decisive Feedback: Known for his decisive feedback during demo sessions, often making quick decisions that shaped the direction of projects.
  • Cultural Influence: Jobs' leadership style fostered a culture of excellence and innovation at Apple, pushing teams to strive for greatness.

What is the "keyboard derby" mentioned in Creative Selection?

  • Focused Problem-Solving: The "keyboard derby" was a critical phase in the development of the iPhone's keyboard, involving rapid prototyping sessions to solve touchscreen typing challenges.
  • Collaboration and Competition: Team members presented their keyboard prototypes in a competitive format, fostering innovation and leading to the selection of the most effective design.
  • Outcome of the Derby: Kocienda's "Blob keyboard" prototype won, leading to the development of the iPhone's autocorrect feature.

What does Kocienda mean by "working at the intersection"?

  • Combining Disciplines: Refers to the blending of technology and liberal arts in product design, leading to more meaningful and user-friendly products.
  • Holistic Approach: Emphasizes considering both technical functionality and user experience, guiding the development of the iPhone.
  • Cultural Significance: Reflects Apple's mission to create products that resonate with users on multiple levels, valuing creativity and innovation.

How did Kocienda's experiences at Apple shape his views on product development?

  • Emphasis on Collaboration: Learned the value of collaboration and teamwork in achieving innovative results, highlighting the importance of diverse perspectives.
  • Iterative Design Philosophy: Adopted an iterative design philosophy, understanding that continuous improvement is key to creating successful products.
  • User-Centric Focus: Reinforced the need for empathy in design, ensuring that products are tailored to meet user needs.

About the Author

Ken Kocienda is a software engineer and designer who worked at Apple for 15 years. He played a significant role in developing the Safari web browser and the original iPhone keyboard. Kocienda's background as a self-taught programmer and his experience working on groundbreaking projects at Apple during its renaissance under Steve Jobs provide him with unique insights into the company's creative process. His work focused on the intersection of technology and liberal arts, a key principle of Apple's design philosophy. Kocienda's firsthand experience with Apple's demo-driven development approach and collaboration with high-profile executives like Steve Jobs and Scott Forstall informs his perspective on product creation and innovation.

Download PDF

To save this Creative Selection summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.36 MB     Pages: 18

Download EPUB

To read this Creative Selection summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 1.34 MB     Pages: 23
Want to read the full book?
Follow
Listen
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 24,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
1M+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...