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
What Would Apple Do?

What Would Apple Do?

How You Can Learn from Apple and Make Money
Turn Apple's product and platform choices into a sharper playbook for your own business.
by Dirk Beckmann 2013 73 pages
3.21
43 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Learn Apple's operating logic, not its products or founder mythology

A company-wide idea. Beckmann argues that Apple's success cannot be explained by Steve Jobs alone. Its advantage comes from combining useful products, integrated technology, clear communication, and a way to earn money from the whole experience. The book is not an insider account. It presents Apple as a case study for businesses adapting to digital markets, as they stood in 2013.

Convenience can create value. When music moved online, Apple worked with record labels to make legal digital purchases simple. Pairing the iPod with iTunes offered customers an easy way to find, buy, and play songs. The commercial insight was larger than either product: remove barriers for users while building a business model that rewards the company and its partners.

Analysis

What's useful here is the shift from hero worship to organizational design. A charismatic founder can set priorities, but repeatable performance depends on how product decisions, engineering, distribution, and customer experience fit together. That is a more transferable lesson than copying a famous launch or keynote. The iTunes example also shows that convenience is not merely a design virtue; it can change what customers consider worth paying for. Still, a smooth experience does not guarantee a fair one. Integrated systems can make participation easier while also giving the operator substantial control over access, rules, and revenue.

Subtract features until the product's main promise becomes unmistakable

Choose the trade-off. Apple treats omission as a product decision, not a failure to innovate. The MacBook Air pursued extreme portability by removing the built-in CD drive. Users could access another computer's drive over a network when they needed one. The product was less complete in one sense, but more distinctive in the way that mattered to its central promise.

Make the choice legible. Beckmann contrasts this with products overloaded by functions, settings, and manuals. The iPhone's separate apps let people use focused tools rather than confront every capability at once. The practical test is whether a feature helps the intended user accomplish the primary task. Leaving something out takes judgment, especially when colleagues and customers all ask for different additions.

Analysis

This is a strong application of choice architecture: every extra option demands attention, and a crowded interface can make the important action harder to find. Yet simplicity is not the same as minimal feature count. Research on choice and decision-making suggests that abundant options can burden people, but the effect depends on the task and the user. A novice may benefit from a guided default, while an expert needs control. The useful discipline is therefore not to remove complexity indiscriminately, but to decide where complexity belongs: ideally in the engineering, rather than in the customer's moment of use.

Watch what customers do before trusting what they say

Behavior reveals friction. Design Thinking is an approach to product development that begins by observing people in real situations, then uses collaborative ideas, repeated trials, and prototypes to find workable solutions. Beckmann warns that focus groups can capture social performance as much as actual behavior. People may describe one preference in a group, then act differently when choosing or using a product alone.

Look at the task, not the spec sheet. An amateur photographer may need better lighting more than a higher megapixel count. A driver may value legroom or clear navigation more than a modest increase in horsepower. Apple, in this account, relies on its specialists to develop the answer rather than asking customers to invent the product. Customer feedback can inform the work without replacing professional responsibility.

Analysis

Observation connects product design to ethnography, the study of people in the settings where their routines unfold. It can expose workarounds and unmet needs that people have trouble articulating, because habits often operate below conscious attention. The distinction between stated preference and observed behavior is valuable, but observation is not automatically objective. Researchers bring assumptions, and a few observed users cannot represent every market segment. Strong practice combines close observation with other evidence, then tests whether an interpretation holds beyond the first compelling anecdote.

Keep generating and testing ideas after the first good one

Ideas need competition. Beckmann describes Apple's 10-3-1 principle: teams begin with many serious concepts, narrow the field to a few, and develop the strongest candidate further. The point is not to produce weak alternatives for show. It is to resist mistaking the first appealing solution for the best one. Designs are challenged, revised, and sometimes abandoned as teams learn what works.

Make concepts tangible. Prototypes help people react to how a product looks and functions, rather than to a description or presentation. Apple prototypes are developed with enough detail to resemble the intended experience, making flaws and complexity easier to spot. The same logic can work with fewer people and resources: create several credible options, test them, and let evidence improve the choice.

Analysis

This method resembles divergent and convergent thinking: first widen the search, then impose criteria to choose. It also counters the sunk-cost trap, in which teams defend an early idea because they have already invested effort in it. A prototype can make disagreement more productive by giving colleagues something concrete to inspect. The limitation is cost. High-fidelity models are useful when the experience depends on details, but rough prototypes may be sufficient for early questions. Teams should match the prototype's expense to the uncertainty they need to resolve.

Make innovation everyone's job, then protect small focused teams

Quality crosses departments. Beckmann argues that innovation cannot be left to research and development while purchasing, production, service, and marketing follow old routines. A supplier chosen only for low price, for example, may not support a distinctive product decision. Apple's attention to detail extends beyond the device to packaging, stores, and customer support.

Give teams room to finish. The book describes focused development groups with short decision paths, a clear goal, and a firm deadline. This start-up-like structure helps large organizations act without requiring the whole company to become a start-up. Digital products also require more than an IT installation: they involve the business model and the customer's experience. A capable team needs input from different disciplines, not just technical implementation.

Analysis

This is a systems view of innovation. A product is experienced through a chain of interactions, so a weak handoff in billing, onboarding, or support can undo excellent engineering. Cross-functional work helps teams anticipate those dependencies before launch. Small groups can also reduce coordination costs, though speed is not automatically wisdom: tight deadlines may suppress dissent or encourage burnout. The best structure pairs a clear mandate with access to expertise, time for recovery, and permission to raise risks. Innovation should be broadly owned, but accountability must still be unmistakable.

Arrive later only when you can remove entrenched frustrations

First is not always best. Beckmann rejects the idea that digital companies must launch before everyone else. A rushed product can disappoint users and damage a company's reputation. A later entrant can study what customers struggle with, invest in a stronger solution, and choose a business model suited to the market.

Improve the experience. The iPhone entered a market already populated by mobile phones, but Apple addressed problems users encountered with existing devices. The iPad also arrived after years of debate about smaller computers, and combined activities such as reading, browsing, email, and app use in a different form. This is not a case for waiting passively. Teams still need to build capabilities, test ideas, and prepare to act when they see a meaningful opening.

Analysis

The principle is closer to strategic timing than to simple patience. A later entrant can benefit from learning what the first wave has taught the market, but only if it can offer a distinct improvement. In technology, early products may establish standards, attract developers, or secure customer habits, advantages that later competitors cannot easily overcome. The decision therefore turns on what is being learned and what can be changed. Waiting without investment is not strategy; studying user frustrations while building a better product can be.

Build the market's missing system, not just another device

Connect the whole chain. A platform links a product to the services, partners, and processes needed to make it useful. iTunes connected music buyers, record labels, software, and the iPod. The App Store connected iPhone owners with outside developers, while Apple handled distribution and payments. Beckmann argues that the value lies not only in the individual item, but in making the whole exchange work simply.

Redesign the business, too. The book tests this idea through imagined products: a kitchen where recipe programs coordinate appliances and grocery orders, and a learning marketplace where educators offer digital courses. These are proposals, not accounts of products Apple actually built. Their shared lesson is to rethink how value is created and delivered, rather than merely transferring an old product onto a website.

Analysis

Platforms can reduce the cost of finding one another for groups that need to interact, while creating new opportunities for complementary products. That helps explain why an app marketplace can become more valuable as more users and developers join. But the platform operator also writes the rules. Decisions about approval, fees, ranking, and access shape which participants can succeed. A business considering this model should ask both sides of the question: what coordination problem does the platform solve, and what dependence does it create for its partners?

Make the benefit visible before asking customers to study specifications

Lead with the experience. Apple advertising, as Beckmann describes it, centers a single customer benefit rather than a catalogue of technical details. A MacBook Air commercial used an envelope to make thinness immediately apparent. The iPod silhouette ads focused on the pleasure of listening to music, not storage figures. These choices made the product's appeal easy to grasp before a customer needed to compare specifications.

Let design carry meaning. The book traces Apple's visual approach to earlier industrial designers such as Dieter Rams, whose principles included usefulness, clarity, and care for detail. Brand identity also gives customers a way to express affiliation. The 1997 Think Different campaign framed Apple as a choice for people who valued unconventional thinking, helping make the brand's meaning part of the product experience.

Analysis

A visual demonstration can compress information: one clear image may communicate a product attribute faster than a paragraph of claims. Design also works as a signal of the care and identity associated with a product, not merely as decoration. However, a memorable message cannot compensate indefinitely for weak performance. Marketing can attract attention, while continued use depends on whether the promise survives contact with the product. The strongest communication is therefore not a clever slogan pasted onto a device; it is a benefit that the product itself makes easy to notice.

Standardize the platform so customers can personalize the experience

Consistency enables variety. Apple offers a relatively limited range of devices, but software and marketplaces let people adapt those devices to different interests. The App Store supports uses ranging from astronomy to travel. The book argues that a stable set of products can make it easier for developers to build software that works reliably, instead of accommodating a sprawling array of hardware differences.

Put variation in the right layer. Programs such as iMovie, GarageBand, and Pages let people create films, music, and documents without specialist equipment or extensive training. In this model, the manufacturer standardizes the underlying system, while users and developers supply many of the experiences. The result is a different route to individuality than offering a separate physical product for every narrow preference.

Analysis

This is a modularity argument: stable interfaces can let different components develop independently while still working together. Standardization can lower development friction and make the experience more predictable, especially for third-party creators. Yet it shifts power toward the platform owner, whose technical rules determine what can be built and distributed. It can also constrain users who need unusual configurations. The useful design question is not whether to standardize, but which elements need consistency for reliability and which should remain open to adaptation.

Sell digital help at the moment a customer needs it

Think in small useful tools. In the book's account of the post-PC era, apps are focused pieces of software that people can obtain and use with little setup. Beckmann contrasts them with large programs that require installation, training, and ongoing attention. A person decorating a room who needs a level can download a phone app in the moment, rather than buy a tool for occasional use.

Charge for real utility. The example illustrates how immediacy can make a modest price feel worthwhile: the product solves a current problem without delay. Beckmann urges businesses to ask whether a large service can be divided into focused functions available at the right time and place. He also argues that companies should not assume every digital offering must be free and financed indirectly through advertising or personal data.

Analysis

Small, contextual tools fit the economics of software: once built, a digital product can be distributed widely, and a narrow function can serve a specific need. The timing matters because users are more likely to recognize value when the problem is present. But low-friction downloads can also encourage disposable products, weak privacy practices, or subscriptions that are hard to track. A sound business model should make the exchange clear: what the tool does, what it costs, and what data or ongoing access it requires.

Analysis

The book's most durable contribution is its insistence that digital innovation is not a technology department's project. It is a coordinated design problem involving what customers do, what a company can build, how the work is organized, and how value is captured. Its examples repeatedly move from a visible object, such as a phone or music player, to the less visible system around it: software, distribution, partners, and communication. That shift is why the advice travels beyond consumer electronics.

The strongest principles are procedural rather than imitative. Observe real use, make trade-offs explicit, compare multiple concepts, test with prototypes, and align departments around the same product promise. These practices can improve decisions even when a company lacks Apple's resources. The book is also right to challenge the reflex that every digital service must be free, or that customers should be asked to invent the product themselves.

Its vulnerabilities come from the same source as its appeal. Apple is an unusually visible winner, so its practices can look more causal and universally transferable than the evidence here establishes. A premium, integrated system may suit customers who value simplicity, but it can exclude people who need flexibility, interoperability, or lower prices. A closed platform can make a purchase effortless while concentrating control over developers and users. Similarly, the book's proposals for connected kitchens, travel, education, and news are thought experiments, not validated forecasts. Their value is in the questions they pose about fragmented services and obsolete value chains, not proof that one company should own every layer.

Read the Apple method as a set of hypotheses to test, not a recipe to copy. Its best question is not what Apple would manufacture, but where customers face needless effort, what a company can simplify without sacrificing choice, and whether the resulting business remains valuable to everyone who must participate.

Summary in 30 Seconds
Strong products solve a clear customer problem, so remove features that distract from the main benefit. Observe how people behave, develop several credible concepts, and use prototypes to expose flaws before committing. Innovation depends on focused, cross-functional teams and coordination across service, marketing, and operations. A platform can connect products, software, partners, and payments into one useful experience. Digital tools can earn revenue when they solve an immediate need.
Contains spoilers

Last updated:

Report Issue

Review Summary

3.21 out of 5
Average of 43 ratings from Goodreads and Amazon.

What Would Apple Do? receives mixed reviews, with an average rating of 3.24 out of 5. Some readers appreciate the book's exploration of Apple's business model and design thinking, particularly enjoying the author's imaginative scenarios of Apple creating products in other industries. The book is praised for its easy flow and interesting discussion of design thinking. However, critics find it lacking in new insights and potentially boring. One reviewer highlights the author's argument about digital natives' lack of understanding regarding internet data usage.

Your rating:
3.94
61 ratings
Want to read the full book?

Glossary

Design Thinking

User-centered product development

A collaborative approach to creating products and services by studying people in real contexts, generating and revising ideas, and using prototypes to test possibilities. In Beckmann's account, it brings different disciplines together and treats development as an iterative search for solutions that are useful to customers and feasible to produce.

10-3-1 principle

Narrow many concepts to one

A product-development practice described in the book in which teams begin with ten strong concepts, select three for further work, and refine those until one leading solution remains. The numbers are an illustration of disciplined comparison, not a requirement that every organization must field ten teams.

Agile

Flexible iterative development

A development approach that uses flexible planning and repeated adjustment rather than assuming that every requirement can be fixed in advance. In the book, Agile is associated especially with software work, where teams respond to changing needs and refine an initial concept as they learn more about the problem.

platform

System connecting market participants

A system that brings together a product, its users, and other participants who contribute complementary services or content. In the book's examples, iTunes links listeners with music sellers, while the App Store connects developers with iPhone users. A platform organizes the exchange and can reshape how value is delivered and paid for.

post-PC era

Computing centered on mobile devices

The period Beckmann associates with touch-screen devices such as the iPhone and iPad changing how people use computers. Software becomes easier to access as focused apps, rather than programs that require the habits and setup associated with traditional desktop computers.

skeuomorphism

Digital design mimicking physical objects

A design approach in which digital interfaces borrow the appearance or behavior of familiar physical objects. The book uses it to describe features in early mobile software that resembled real-world materials and objects, such as leather-bound books or cases. Such visual cues can make unfamiliar interfaces easier to recognize, though they can also limit a design to old metaphors.

About the Author

Dirk Beckmann is the author of What Would Apple Do?, a book that examines Apple's business practices and design philosophy. Beckmann's work demonstrates extensive research into Apple's strategies and mindset. He applies design thinking principles to explore how Apple might approach product development in various industries beyond their current offerings. Beckmann's writing style is described as having a good flow, making for light reading. He engages readers by inviting them to imagine Apple's approach to designing products like kitchens, TVs, and transportation. The author also discusses the concept of 'digital natives' and their relationship with technology, particularly social media platforms like Facebook.

Download PDF

To save this What Would Apple Do? summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.30 MB     Pages: 16

Download EPUB

To read this What Would Apple Do? 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.35 MB     Pages: 19
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 25,
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...