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
Digital @ Scale

Digital @ Scale

The Playbook You Need to Transform Your Company
Blockbuster had 8,000 stores and $6 billion in revenue, then dismissed a mail-order DVD upstart.
by Anand Swaminathan 2017 288 pages
3.74
87 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Transform the business model, not merely the technology

Technology is the starting point. Digital transformation means using technology to reshape customer value, how work gets done, and how a company earns revenue. Installing new software without changing those things is like building a runway that leads nowhere.

The Tolino e-reader shows the difference. German booksellers joined forces with Deutsche Telekom after Amazon’s Kindle threatened their business. Rather than merely launch a device, they built an e-book offering, app, and marketing campaign, while combining online sales with bookstores. By 2015, Tolino had reached an estimated 40 to 45 percent of Germany’s e-reader market. Its advantage came partly from more than 1,800 physical stores, not from technology alone.

Analysis

What's important in the Tolino story is the strategic use of an existing asset, the bookstore network, to make a new digital product more compelling. Technology becomes transformative when it changes the relationship between customer, company, and channel. This also makes the case more practical than a simple appeal to imitate Silicon Valley. The partnership did not require each bookseller to become a technology firm. Still, collaboration cannot substitute for a clear customer proposition: a coalition that shares costs but offers a clumsy experience would have little lasting advantage.

Use profitable success as a reason to prepare, not to delay

The danger is delayed response. Companies often see a threat but protect current profits rather than risk changing the model. Compaq, once dominant in business computers, held to store-based sales while Dell sold customized computers directly online. Dell’s build-to-order approach cut the costs of inventory and distribution, and Compaq was acquired by Hewlett-Packard in 1997. Kodak had invented a digital camera in 1975, but feared damage to its profitable film business and lost its early lead.

Blockbuster offers the same warning. In 2004 it had 8,000 stores and $6 billion in revenue, yet it dismissed Netflix’s mailed DVDs. When Netflix moved to streaming, Blockbuster’s eventual response was too late. The book argues that leaders must judge how quickly change is moving, not just how well today’s model performs.

Analysis

These cases make a useful distinction between recognizing change and accepting its implications. The threat is not simply a new product. It is a change in the economics of the whole system, such as inventory, access, or distribution. Leaders therefore need to assess what a rival makes easier or cheaper for customers. The caution is that not every new technology deserves a wholesale pivot. Urgency is most useful when grounded in evidence about customer behavior and the company’s vulnerable profit pools, rather than fear for its own sake.

Map transformation across markets, operations, and foundations

Use three questions to organize the work. The book’s Digital@Scale approach asks why change is necessary, what must change, and how to implement it. The Why question establishes urgency, the threat to the business, and the scale of response. What identifies the priorities. How turns those priorities into a transformation that can be managed and expanded.

The What is divided into three levels: New Ecosystems, where industry boundaries and profit pools shift; Business Architecture, where customer experience, products, and internal processes are redesigned; and Foundation, which covers technology, talent, organization, and culture. The How follows a practical sequence: create a plan, establish new ways of working, then spread proven changes across the enterprise. The aim is coordinated renewal, not a collection of disconnected apps.

Analysis

The framework’s strength is that it prevents the conversation from collapsing into an IT shopping list. A company can examine threats outside its sector, weaknesses in its customer journey, and gaps in its own capabilities without confusing those distinct problems. It also gives executives a common language for decisions that otherwise sit in separate departments. The framework is intentionally broad, so it does not decide priorities on its own. Leaders still need to rank initiatives by customer value, feasibility, risk, and the organization’s capacity to absorb change.

Carry your strongest assets into new digital ecosystems

Do not discard the old advantage automatically. Established companies may have a trusted brand, customer relationships, specialized knowledge, or an installed base of equipment. Digital competitors can turn those assets into liabilities if incumbents refuse to adapt, but the same assets can support a stronger digital offer.

Axel Springer invested in digital businesses and sold profitable print titles that no longer fit its direction. By 2015, digital activities produced about 70 percent of its earnings before interest, taxes, depreciation, and amortization. Caterpillar used sensors on its machinery to sell software services that help customers monitor fleets and prevent downtime. John Deere applied its agricultural expertise to data-based advice about seed, soil, and weather. In each case, technology extended an existing customer promise into a changing market.

Analysis

This is a more precise way to think about disruption than simply asking whether a company should imitate a start-up. The key question is which parts of its advantage remain valuable when delivery methods change. A brand without a useful digital experience can weaken; a large installed base without data capability can become an obligation. Asset-based strategy also encourages selective cannibalization: leaders may need to reduce the value of a legacy activity to protect the deeper customer relationship. The difficult work is deciding which strengths transfer and which are merely familiar.

Design one customer journey across every channel

Customers experience one company. Omnichannel means allowing people to move between physical stores, websites, mobile apps, and service channels without having to restart or accept a worse experience. It is relevant beyond retail, including banking, insurance, and industrial sales.

Walgreens connected its stores with digital services and drew 14 million visits a week across its digital channels. Nearly half of digital visitors said their next step was a store visit, and customers using both digital and physical channels spent 3.5 times as much as store-only customers. Tolino also used bookstores to sell e-readers and support e-book customers. To make these journeys work, companies need shared customer information, joined-up incentives, and teams that can identify where people encounter friction.

Analysis

Omnichannel is not the same as adding more places to buy. Its real test is whether information and service travel with the customer. That requires organizations to coordinate inventory, pricing, support, and accountability across channels, which can expose internal conflicts that a new app cannot fix. The spending figures suggest that channels can reinforce one another, but they do not prove that every channel investment pays off. Companies should examine which combinations customers actually use, and whether convenience or service quality improves enough to justify the added complexity.

Launch useful products early, then let evidence improve them

Replace certainty with short learning cycles. A minimum viable product, or MVP, is an early version with enough essential functions to test whether it solves a real customer problem. Teams gather feedback, adjust the product, and repeat, rather than waiting for a supposedly perfect launch.

Lufthansa introduced digital check-in in stages, moving from airport kiosks to home printing and then mobile boarding passes. Each step tested what passengers would accept while reducing friction and cost. Digital pricing applies a similar learning loop to commercial decisions. Online retailers can adjust prices using competitor prices, sales, and customer responses. The book reports that dynamic pricing can raise returns on sales by 3 to 8 percent, while warning that individualized prices can anger customers when the differences seem unfair.

Analysis

The method treats product development as a process of reducing uncertainty, not merely completing a design. That logic suits digital services especially well because usage data can reveal where people struggle or disengage. But speed is not automatically a virtue: an MVP must be safe, comprehensible, and genuinely useful, particularly in health, finance, or transportation. Dynamic pricing illustrates the same boundary. An algorithm may optimize revenue while damaging trust. Evidence should therefore include customer perceptions and long-term relationships, not only conversion or margin.

Keep core systems reliable while making customer-facing IT fast

Separate different operating needs. Two-speed IT pairs stable systems for essential activities, such as billing and records, with a faster environment for customer-facing services and experiments. Middleware connects the two. This avoids the risk and cost of replacing every system at once while allowing teams to test new digital offerings quickly.

The foundation also includes data quality, analytics, software skills, and cyber security. Analytics can describe past behavior, predict what may happen, or recommend a response. But useful results depend on reliable data and people who can translate business problems into analytical questions. Security belongs in the design of products and processes, not as a final barrier. The book’s cyber resilience approach starts by identifying the company’s most valuable data and tailoring safeguards to the risk.

Analysis

The two-speed idea recognizes that organizations have to protect continuity while changing how they serve customers. It is a transition design, not a permanent excuse to let legacy and agile systems drift apart. The connection between analytics and security is especially important: more data can improve decisions, but it also increases the potential cost of misuse or loss. A company should ask not only whether it can collect or analyze information, but whether it has a legitimate purpose, sound governance, and a clear response when systems fail.

Replace departmental handoffs with accountable, cross-functional teams

Structure work around outcomes. Digital organizations bring people from technology, design, marketing, operations, and other relevant functions into teams responsible for a product or customer process. A product owner represents customer priorities and helps set the work, while teams operate in short cycles and learn from results.

ING reorganized much of its headquarters into roughly 300 squads of nine people, grouped into larger units with shared purposes. Software releases shifted from five or six times a year to weekly, and employee engagement scores rose. The shift depends on more than a new chart: managers must move from directing every task toward setting direction, coaching teams, and giving them authority. A chief digital officer can help connect departments, recruit expertise, and keep the transformation visible to senior leaders.

Analysis

Cross-functional teams shorten the distance between identifying a customer problem and changing the service that causes it. They also make accountability more concrete: the team cannot simply pass a defect to another department and declare its part complete. Yet autonomy needs boundaries. Teams require shared priorities, clear decision rights, and coordination when their products depend on common systems or data. The CDO is valuable when empowered to resolve these dependencies, not when assigned a digital title without budget, authority, or executive backing.

Release funding by milestones, and scale only proven solutions

Treat projects as investments, not entitlements. The book borrows a venture-capital practice: fund an early test, set measurable milestones, and release more resources when evidence supports the next step. If a project misses its targets, change its direction or stop it. This is difficult for companies accustomed to annual budgets and reluctant to cancel initiatives.

A digital transformation still needs an enterprise-wide plan, but that plan must adapt as customer feedback and experiments reveal new information. A utility company used short development cycles to build apps for field engineers. One team-management app helped engineers complete about 50 percent more repairs. In the first year of its broader transformation, the utility also improved its customer satisfaction ranking by three places and increased revenue by 20 percent. The lesson is to scale demonstrated value, not activity.

Analysis

Milestone funding combines discipline with flexibility. It protects resources from being locked into projects whose original assumptions have failed, while giving promising teams room to grow. The approach works only if milestones measure meaningful outcomes rather than easy-to-count outputs, and if leaders tolerate honest evidence that an idea should end. The utility example links operational results with customer outcomes, a useful reminder that transformation should be judged across more than one metric. No single pilot proves enterprise-wide success, so scaling requires adaptation to local conditions.

Build alliances where no company can own the whole customer system

Compete through networks as well as products. Digital ecosystems connect organizations that once operated in separate industries. A company may coordinate the network, join someone else’s platform, or build a specialized service that fits within a larger system. Each role requires compatible technology, clear agreements, and a reason for partners to participate.

Audi, BMW, and Daimler, despite competing in premium cars, jointly acquired the mapping service Here because precise maps mattered to all their autonomous-driving ambitions. In health care, the book describes open platforms as a way to connect patients, researchers, providers, and app developers, while stressing the need to protect sensitive data and measure actual outcomes. Partnerships can add skills and speed, but companies must negotiate data access, intellectual property, customer ownership, and how value is divided.

Analysis

The ecosystem view captures a structural shift: value may depend on coordination among firms rather than ownership of every component. Competitors can cooperate on shared infrastructure while still differentiating in products and customer service. That makes partnership a strategic capability, not a procurement task. It also creates governance questions that cannot be solved by enthusiasm for collaboration. Participants need rules for privacy, interoperability, dispute resolution, and reward sharing. Without those, the most central partner may capture the benefits while others provide the data or labor.

Analysis

Digital@Scale is best understood as a management program for changing a company’s operating logic, not as a technology forecast. Its durable contribution is the alignment of three levels: external markets, the internal value-creation system, and the capabilities that support both. The Tolino example makes that alignment tangible. Retailers did not defeat Amazon by copying its online store; they combined a shared digital product with a physical network and a technology partner.

The implementation argument is equally central. Small experiments reduce uncertainty, cross-functional teams shorten feedback loops, milestone funding prevents sunk costs from dictating strategy, and an enterprise rollout turns local learning into organizational change. These mechanisms reinforce one another. A pilot without authority cannot alter the core business; autonomy without shared priorities produces scattered projects; speed without reliable data or security can amplify failure.

The book’s strongest challenge is political rather than technical. Leaders must accept cannibalization, redistribute authority, and allow teams to question routines that once made the company successful. Its optimism about data and automation is less complete: better measurement does not settle questions of privacy, fairness, or who bears the costs of displaced work. Those issues belong inside transformation decisions, not in a separate ethics discussion.

Because the book appeared in 2017, its technology timelines and market forecasts should be read as period-specific scenarios rather than current predictions. The more lasting test it offers is practical: can the company identify a customer problem, change the whole process around it, learn quickly, and extend what works without weakening trust or resilience?

Summary in 30 Seconds
Digital transformation means changing how a company creates value and earns revenue, not installing software. Profitable incumbents fail by protecting current profits while rivals reshape the market. Plan across new ecosystems, redesigned customer journeys, and foundations of technology, talent, and culture. Launch early versions, learn from feedback, and fund projects by milestones, scaling only what proves value. Run stable core systems beside fast customer-facing ones, and organize cross-functional teams around outcomes. Partner where no firm owns the whole system.
Contains spoilers

Last updated:

Report Issue

Review Summary

3.74 out of 5
Average of 87 ratings from Goodreads and Amazon.

Digital @ Scale receives mixed reviews, with an average rating of 3.75/5. Readers appreciate its comprehensive approach to digital transformation, practical strategies, and real-world case studies. The book is praised for its clarity and actionable insights. However, some find it lacks depth for experienced readers and may be overwhelming for beginners. Critics note repetition and a focus on large organizations. Overall, it's considered a valuable resource for executives and managers navigating digital transformation, though opinions vary on its effectiveness for different reader levels.

Your rating:
4.28
51 ratings
Want to read the full book?

Glossary

Digital@Scale

Enterprise-wide digital renewal

The book’s approach to transforming a company across its business model, processes, technology, organization, and culture. It links strategic change in emerging markets to redesigned business architecture and stronger foundations, then calls for implementation that moves beyond isolated pilots to the wider enterprise.

Two-speed IT

Stable and agile systems

An IT architecture that operates a dependable environment for essential back-office functions alongside a faster environment for customer-facing products and experiments. Middleware connects the systems. The arrangement allows a company to protect critical records and operations while developing digital services at a quicker pace.

Digital Quotient (DQ)

Digital readiness diagnostic

A diagnostic approach described in the book for assessing a company’s digital readiness. It prompts leaders to examine strategy, customers, talent, investment, pace, and measurable targets, helping them identify strengths, weaknesses, and the scope of change required.

minimum viable product (MVP)

Basic testable product

An early product version that includes enough core functionality to test whether it addresses a customer need. Teams release it, observe how customers respond, and use that evidence to decide what to improve, add, or abandon. It is intended to reduce the cost and delay of building from untested assumptions.

Digital operating system

Repeatable learning and delivery

The management practices that let a company develop and improve digital offerings through rapid testing, measurement, and adjustment. It includes cross-functional teams, clear ownership, customer feedback, performance measures, and decisions about whether to continue or stop work based on results.

Digital build-operate-transfer (DBOT)

Temporary expertise transfer

A method for accelerating digital capability by bringing in external specialists to establish and operate an initial digital team or business unit. After the team and processes are functioning, the specialists are gradually replaced by company employees, reducing the risk of permanent dependence on an outside provider.

DevOps

Joined development and operations

A way of organizing software work in which development and operational teams share processes, tools, and incentives instead of working as separate stages. The aim is to release improvements more quickly and reliably, with operational feedback informing development and developers accountable for how their systems function in use.

About the Author

Anand Swaminathan is a co-author of Digital @ Scale and a consultant at McKinsey & Company. As a digital transformation expert, he brings extensive experience in helping organizations navigate the complexities of the digital age. Swaminathan's work focuses on providing practical strategies and insights for businesses undergoing digital transformation. His collaboration with Jürgen Meffert on this book showcases their combined expertise in digitization, business strategy, and organizational change. Swaminathan's background in consulting allows him to offer valuable perspectives on the challenges and opportunities presented by digital technologies across various industries.

Download PDF

To save this Digital @ Scale summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.33 MB     Pages: 16

Download EPUB

To read this Digital @ Scale 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.39 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 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...