Key Takeaways
Treat digital transformation as a business redesign, not an IT upgrade
Technology is only the start. Saldanha defines digital transformation as moving an organization into an era where digital technology shapes its products, operations, and business model. Automating an existing process can make it cheaper, but it does not necessarily change how the organization creates value. The difference is between adding technology to the old game and redesigning the game itself.
The book argues that roughly 70 percent of digital transformations fail, often because organizations lack discipline in choosing and executing the right changes. The pressure is not abstract: the author cites an average S&P 500 company lifespan of about 20 years, down from 60 years in the 1950s. The central question is no longer whether to change, but how to change reliably.
The distinction between digitizing work and changing the value proposition is crucial. A faster legacy process can still leave a company vulnerable if customers have shifted to a different way of solving the problem. This also explains why technology spending alone is a poor measure of progress. The failure-rate figure deserves caution, since studies may define transformation and success differently. Still, the underlying warning holds: a technology project can finish on time while the business remains strategically unchanged.
A successful launch is only halfway to surviving disruption
Transformation has two tests. The John Stephenson Company was innovative in carriages, streetcars, and related products, yet it did not shift into the automobile business. Studebaker made the transition from wagons to cars, but struggled to scale profitably and keep investing in its factories. One company failed to take off; the other took off but could not stay competitive.
Saldanha uses these contrasting histories to argue that a single successful change is not enough. His maturity map runs from basic process automation, through scattered experiments and enterprise-wide alignment, toward an integrated digital business and, finally, continuous reinvention. The destination is not a finished transformation project. It is an organization that can keep adjusting its business as technology and customer expectations change.
The carriage and Studebaker stories separate invention from adaptation, a distinction that appears across economic history. Existing companies often possess excellent engineers and products but remain attached to the economics that made the old model successful. The book's emphasis on continuous reinvention is strong, though perpetual change should not become change for its own sake. Durable organizations need a stable purpose and the capacity to revise their methods, not constant reorganizations that exhaust people.
Keep strategy and obstacle removal in the executive suite
Leaders cannot delegate ownership. Digital transformation requires executives to connect business goals to technology choices, make time for the work, and remove barriers when execution stalls. They can rely on technical experts, but delegating the strategy itself leaves the organization without accountable leadership. That responsibility requires enough digital literacy to ask informed questions about what technology can and cannot do.
Singapore illustrates visible ownership: its government began computerizing public services in the 1980s, and its later Smart Nation work was led from the prime minister's office. At P&G, executives helped sustain a single SAP-based enterprise system across more than 100 countries. During the integration of Gillette, senior sponsors made frequent decisions on hundreds of complex issues. In both cases, hands-on leadership helped translate ambition into action.
This argument usefully distinguishes executive sponsorship from executive ownership. Sponsorship can mean approving a budget; ownership means accepting responsibility for difficult choices and organizational tradeoffs. That matters because digital change crosses boundaries that technical departments cannot control alone. Yet digital literacy need not mean that every executive becomes a programmer. The more practical standard is the ability to understand major opportunities, question assumptions, and judge whether proposed technology serves a clearly stated business outcome.
Break transformation into fast tests, not one spectacular launch
Small releases expose problems early. HealthCare.gov's 2013 launch failed under real user demand after a large, complex build involving federal agencies, insurers, states, and contractors. The book argues that teams could have tested the complete user experience in smaller steps rather than discovering critical problems at launch. Denver's automated airport baggage system offers a second warning: an ambitious, tightly coupled design contributed to a 16-month delay and $560 million in cost overruns.
Saldanha recommends pairing iterative delivery with a portfolio of projects. A minimum viable product, or MVP, is an early, testable version that lets users reveal whether an idea works before the full investment is made. At P&G's Next Generation Services, teams used short cycles, tested projects, and stopped weak ones. A protected early-stage process and explicit time targets helped keep experiments moving.
Iteration is a form of risk management, not merely a software preference. Frequent tests generate information while the cost of changing direction is still low. The approach is especially valuable when users, technical systems, or partners are difficult to predict. However, speed cannot replace careful testing where failure threatens safety, privacy, or essential services. The useful principle is to shorten learning cycles while preserving the review and safeguards appropriate to the potential harm.
Give change leaders purpose, protection, commitment, and an early win
Authority must be tangible. Saldanha calls the support needed for disruptive work disruption empowerment. It includes a compelling purpose, visible protection from organizational pushback, leaders' personal commitment, and an initial set of projects that can build momentum. A purpose gives people a reason to join; protection gives them room to test ideas without being punished for every failed attempt.
The stalled US effort to adopt the metric system had laws and a designated board, but lacked durable political backing and broad commitment. By contrast, Jeff Bezos invested in the Washington Post, set an ambitious digital direction, and gave change leaders significant freedom. At P&G, leaders recruited credible operators into the transformation team and selected early opportunities likely to show progress. Empowerment meant more than an inspirational announcement: it changed who could act and what risks they could take.
The contrast shows how formal authority can exist without practical power. Change leaders need both permission to experiment and a credible route for resolving conflicts with the core business. A visible early win can make an abstract strategy believable, particularly for employees who have seen previous initiatives fade. There is a limit, though: charismatic purpose and executive protection cannot compensate for poor project selection. Empowerment works best when paired with clear boundaries, evidence, and responsibility for consequences.
Bet on digital where it multiplies a real strategic advantage
Start with the business problem. Digital leverage points are the areas where technology can most strongly improve an organization's strategy. Saldanha recommends identifying strategic strengths, customer needs, or operational pain points, then examining relevant technologies and shaping ideas through creative methods such as design thinking.
Technology is only one part of the opportunity. Reimagined processes can remove unnecessary steps, while ecosystems can bring in resources the company does not own. Netflix repeatedly changed its model, from mailed DVDs to streaming and then original content, by pairing technology with customer convenience and organizational agility. McDonald's, by contrast, spent heavily on a global back-office technology program that did not build on a distinctive digital strength and was abandoned. The point is not to adopt the newest tool, but to choose where it changes the economics or experience of the business.
This is a useful defense against technology-first planning. The same tool can be strategically transformative in one organization and an expensive distraction in another. Combining technology with process redesign and outside capabilities also broadens the search beyond automation. A useful test is whether the proposed change removes a meaningful customer or operational constraint, rather than merely making an existing workflow more fashionable. Design methods help generate possibilities, but business evidence must still decide which idea deserves investment.
Match the change structure to urgency, resistance, and capability
There is no universal route. Saldanha describes three broad ways to organize change: build it within the existing structure, create a separate edge organization with room to move, or acquire or partner for outside capabilities. The right choice depends on available time, internal skills, and how resistant the organization is to change.
The global Y2K effort succeeded through decentralized work because the deadline and threat were clear. P&G's Gillette systems integration created urgency differently: leaders set a measurable goal, gave the integration priority, and established clear decision authority. Transformation teams must also account for the corporate immune system, the controls and habits that protect stable operations but may resist new work. Middle managers are especially important because they are accountable for keeping current operations running. Their incentives and responsibilities need to support the change, not quietly undermine it.
The organizational-design lens improves on the assumption that resistance is simply a personality problem. A separate team can move quickly, but it risks isolation; an internal effort has legitimacy, but may be slowed by established routines. Acquisitions can add capabilities quickly, yet integration itself is demanding. The idea of a protective immune system helps explain why organizations resist change, while also reminding leaders that some safeguards exist for good reasons. Change design should distinguish needless friction from necessary control.
Fund enough experiments to make transformation more than theater
A few ideas rarely suffice. Strategy sufficiency means having enough well-chosen initiatives, at an appropriate mix of risk, to deliver the transformation sought. Saldanha warns against innovation theater: visits to technology hubs, idea contests, or innovation labs that generate excitement but lack the funding, staffing, or authority to implement anything.
Google's approach reserved most effort for its core business, some for related opportunities, and a smaller portion for more radical bets. P&G's transformation team focused on high-impact experiments while the main organization continued routine improvement. Intrapreneurship, or entrepreneurial work inside an established company, can supply ideas from employees who understand real operational problems. The key is to generate more ideas than the organization can pursue, test them, and stop weak ones before they consume the budget meant for stronger opportunities.
The portfolio approach treats innovation as a system of choices rather than a contest to find one brilliant idea. That is sensible because early forecasts are unreliable, and a range of bets can produce more learning than a single grand plan. Still, a portfolio needs more than a target number of projects. Teams need criteria for stopping, scaling, and transferring successful work into ordinary operations. Without those transitions, an organization can become very good at experimentation while remaining unchanged.
Rebuild digital capability and keep learning as technology shifts
The old engine may not fit. Saldanha argues that a traditional IT function, built mainly to deliver reliable systems efficiently, may not be equipped to lead rapid business-model change. He proposes a broader digital resources function that helps teams build flexible platforms, develop new skills, coordinate digital work across the enterprise, and manage external partners.
That redesign must include the workforce, not just the technology department. AT&T, for example, launched a large retraining effort as many existing roles faced change. Leaders also need a practical way to stay current: learn from start-ups and venture capitalists, invite partners to explain emerging capabilities, and enlist technically skilled employees as digital ambassadors. The book's advice is to experiment with technology when it is usable, rather than waiting for a perfect future version that may arrive after competitors have learned from the imperfect one.
The proposed change recognizes that digital capability is distributed across the enterprise. Central IT can provide standards and expertise, while business teams need enough skill to identify and apply opportunities. Retraining can preserve institutional knowledge, but it cannot be the sole answer when roles or business models disappear; workforce transitions require credible career paths and honest planning. Continuous learning is most effective when attached to live problems, since abstract technology briefings rarely teach leaders how a tool behaves in their own context.
Make customer focus and adaptability part of daily culture
Culture must support repeated change. Saldanha describes an agile culture through customer-focused innovation, an environment that adapts, and a shared purpose. Zappos built its online shoe business around unusually attentive service, helping compensate for customers' inability to try shoes in a store. Adobe replaced annual performance reviews with more frequent conversations and gave employees a simple kit and modest funds to test ideas. These practices made experimentation part of ordinary work.
The New York Times' early digital struggles showed the opposite problem: print-centered schedules, systems, and newsroom habits did not fit real-time publishing. SpaceX, despite repeated launch failures, drew employees around an ambitious mission. These examples suggest that culture is built through concrete routines, incentives, and choices, not slogans. The organization must be able to hear customers, adjust work, and treat intelligent failure as information rather than automatic disgrace.
The strongest cultural examples link values to operating mechanisms. Customer focus matters when it changes product decisions, service standards, and what employees are rewarded for doing. Adaptability also depends on psychological safety, the sense that people can raise problems or test ideas without humiliation. Yet tolerance for failure should be calibrated: a failed prototype can teach, while repeated avoidable harm is not a learning strategy. The practical challenge is to make experimentation safe enough to encourage candor and disciplined enough to protect customers.
Track disruption signals before a healthy business turns brittle
Success can hide exposure. The digital disruption index is a way to assess risk across four areas: industry change, customer expectations, business-model shifts, and the organization's digital performance and capabilities. Saldanha proposes reviewing these signals as part of regular strategic planning rather than relying only on a leader's intuition.
Customer satisfaction alone may miss danger. A service can be acceptable while a digital alternative removes effort or improves convenience. Leaders should watch how channels, partners, and value creation are changing, as well as where technology investment goes and whether it produces customer value. The book points to fear of cannibalizing existing products, organizational inertia, and mistaken assumptions about timing as reasons warning signs are ignored. Kodak's early work on digital photography illustrates how a company can recognize a technology yet underestimate how quickly it will matter.
A recurring risk review can counter the tendency to treat today's strong results as evidence that tomorrow is secure. Combining customer, industry, and internal signals is stronger than relying on a single score, because disruption often begins at the edges of an established market. The proposed index should be treated as a prompt for investigation, not an oracle: composite ratings can conceal disagreements and uncertainty. Its greatest value is institutionalizing the question of what would make the current model less relevant.
Analysis
The book's most useful claim is that digital transformation is an organizational reliability problem as much as a technology problem. Its aviation analogy makes that point memorable: complex work becomes safer when recurring failure modes are identified, responsibility is clear, and checklists make essential steps hard to overlook. The analogy is strongest when applied to execution discipline, not when it implies that organizational change can be engineered with the predictability of a takeoff.
Saldanha's progression from automation to continuous reinvention also corrects a common measurement error. A company may complete a platform migration or launch a digital product and report transformation, even if its incentives, decision rights, and customer proposition remain unchanged. The examples of carriage makers, Studebaker, and P&G's shared-services work make the distinction between one-time change and sustained adaptation tangible. The framework is especially helpful as a diagnostic vocabulary, though its stages should not be mistaken for a universal sequence. Organizations differ in regulation, market position, labor structure, and the cost of experimentation.
The practical strength is its insistence on connecting strategy to operating mechanisms: iterative testing, project portfolios, executive intervention, skills development, and attention to middle managers. These mechanisms address the gap between declaring change and making it possible in daily work. The risk is that portfolio language can make people appear interchangeable, as though failed projects are cheap while their human consequences are not. Responsible experimentation requires explicit protections for employees, customers, data, and essential services.
The deepest implication is that leadership must manage two obligations at once: exploit the current business reliably and create options beyond it. Neither side can be neglected. Too much protection of today's operations produces strategic inertia; too much experimentation fragments attention and weakens execution. The disciplined organization is not the one that changes constantly, but the one that detects when its assumptions are failing, learns at manageable cost, and has authority to act on what it learns.
Review Summary
Why Digital Transformations Fail receives mixed reviews, with an average rating of 3.84/5. Readers appreciate the author's experience and practical advice on digital transformation, including a 5-stage model and disciplined approach. Many find the book's examples and checklists helpful. However, some criticize the writing as repetitive and lacking depth. The book is praised for its insights on change management, technology trends, and organizational culture. Readers recommend it for executives and digital leaders, though some find it basic for those already familiar with the topic.
People Also Read
Glossary
Digital Transformation 5.0
Transformation maturity mapSaldanha's model for describing organizational progress from basic digitization toward ongoing digital reinvention. It distinguishes foundational automation, isolated experiments, partially coordinated change, integrated digital operations, and a state in which adaptation is built into the organization. The model is intended both to identify an organization's current position and to clarify that a completed technology rollout is not the final goal.
Living DNA
Continuous digital reinventionThe book's label for an organization in which digital capability and adaptation are embedded in normal operations. Rather than completing one enterprise-wide transformation and then standing still, the organization continually detects change, experiments, and adjusts its products, processes, and business model. The term describes the intended mature state of the book's transformation model.
disruption empowerment
Support for change leadersA package of organizational support that gives transformation leaders a compelling purpose, protection to take bounded risks, visible commitment from senior leaders, and early initiatives that can create momentum. It is meant to give change teams practical authority and legitimacy, not merely an inspirational message or a budget.
digital leverage points
High-impact digital opportunitiesThe strategic areas where digital capabilities can produce the greatest change for a particular organization. They may involve new business models, new technology-enabled products, or transformed operations. Identifying them begins with business strengths, customer needs, or operational problems, then connects those priorities to relevant technology, process redesign, and external resources.
Minimum viable product
Early testable versionAn initial, limited version of a product or service that can be placed in front of users to test important assumptions. Its purpose is to produce evidence and learning before a team commits to a complete build. In the book's approach, small testable releases help reveal problems early and make it easier to revise or stop an initiative.
edge organization
Protected innovation structureA team or unit set apart from ordinary organizational routines so it can develop and test new ideas with greater freedom and speed. It remains connected to the larger organization because successful work must eventually affect core operations. The approach is useful when urgency is high and existing structures or habits would otherwise block experimentation.
strategy sufficiency
Enough bets to transformThe discipline of ensuring that an organization's transformation has both an adequate number of initiatives and an appropriate mix of risk and potential impact. A few celebrated ideas may not be enough to alter the business. Sufficient strategy requires generating opportunities, testing them, stopping weak projects, and scaling the efforts that deliver meaningful results.
digital disruption index
Composite disruption-risk measureA proposed measure for reviewing exposure to digital disruption across four areas: industry trends, customer information, business-model changes, and digital business performance and organizational capability. The index is intended to be revisited during strategic planning so leaders can compare signals and act before strong current results conceal a growing threat.
digital resources function
Enterprise digital capability groupSaldanha's proposed successor to a narrowly defined IT function. It would support technology platforms while also building digital skills, enabling transformation across business units, governing shared capabilities, and coordinating external partners. The concept reflects a shift from managing technology as an internal service to helping the enterprise use digital resources to change how it operates.
intrapreneurship
Entrepreneurship inside organizationsThe practice of applying entrepreneurial behavior within an established company. Employees develop and test ideas that may create new products, services, or business models, using the organization's resources and reach. In the book, intrapreneurship is a way to generate a continuing flow of transformation opportunities, provided the organization also funds, tests, and scales promising ideas.
innovation velocity
Pace of inventionThe speed at which an organization moves ideas through assessment, design, testing, development, and rollout. Saldanha treats speed as a management goal because digital opportunities can lose value while organizations deliberate. Shorter cycles can build momentum and reduce the cost of learning, provided that speed does not bypass necessary safety, security, or legal review.
FAQ
What is Why Digital Transformations Fail by Tony Saldanha about?
- Comprehensive guide to transformation: The book explores why up to 70% of digital transformations fail and provides a disciplined, practical roadmap to improve success rates.
- Focus on discipline over creativity: Tony Saldanha argues that discipline, not just innovation, is the key to successful digital transformation.
- Five-stage maturity model: The book introduces a five-stage digital transformation model, guiding organizations from initial automation to perpetual innovation.
- Real-world examples and frameworks: Drawing on Saldanha’s experience at Procter & Gamble, the book uses case studies and proven frameworks to illustrate its points.
Why should I read Why Digital Transformations Fail by Tony Saldanha?
- Addresses a critical business challenge: With digital transformation failure rates at 70%, the book helps leaders understand and overcome the root causes of failure.
- Actionable, experience-based advice: Saldanha offers step-by-step guidance, checklists, and disciplines grounded in real-world experience, not just theory.
- Applicable across industries: The insights are relevant for leaders in private, public, and nonprofit sectors facing digital disruption.
- Learn from practical case studies: The book includes examples from P&G, Singapore, and other organizations to illustrate successful transformation.
What are the key takeaways from Why Digital Transformations Fail by Tony Saldanha?
- Discipline is the key: Success in digital transformation comes from applying disciplined approaches, not just creative ideas.
- Five-stage journey: Organizations must progress through five maturity stages, from automation to “Living DNA,” to achieve lasting transformation.
- Checklists and portfolio management: Using checklists and managing a balanced portfolio of projects reduces risk and increases success rates.
- Leadership and culture matter: Committed ownership and an agile, adaptive culture are essential for transformation to take hold.
What is the Five-Stage Digital Transformation Model in Why Digital Transformations Fail by Tony Saldanha?
- Stage 1: Foundation: Automate internal processes and ensure leadership commitment and digital literacy at the top.
- Stage 2: Siloed: Individual business units experiment with digital innovations, but efforts are not yet coordinated enterprise-wide.
- Stage 3: Partly Synchronized: The organization develops a digital strategy and begins aligning efforts, but full transformation and culture change are lacking.
- Stage 4: Fully Synchronized: A company-wide digital platform or model is established, but the organization remains vulnerable to disruption.
- Stage 5: Living DNA: Digital transformation becomes embedded in the organization’s DNA, enabling perpetual innovation and market leadership.
How does Tony Saldanha define “Committed Ownership” in digital transformation?
- Leadership engagement is essential: Top leaders must personally own the digital strategy and cannot delegate accountability.
- Digital literacy at the top: Leaders, including the board, need enough digital understanding to make informed decisions and drive transformation.
- Active barrier removal: Leaders must translate business goals into digital strategies and actively remove obstacles to progress.
- Case study example: Singapore’s digital success, driven by Prime Minister Lee Hsien Loong’s personal commitment, illustrates the power of committed ownership.
What is “Iterative Execution” in Why Digital Transformations Fail by Tony Saldanha?
- Avoid big-bang failures: Large, one-time digital projects often fail; breaking work into smaller, iterative chunks increases success.
- Frequent feedback loops: Iterative execution allows for rapid learning, adjustment, and momentum.
- Portfolio approach: Balancing high-risk and low-risk projects in a portfolio reduces overall risk and ensures transformation sufficiency.
- Speed and innovation velocity: Fast iterations generate enthusiasm and help organizations keep pace with rapidly changing digital ideas.
What does “Disruption Empowerment” mean in Tony Saldanha’s digital transformation framework?
- Four empowerment elements: Massive Transformative Purpose (MTP), leadership “skin in the game,” air cover for risk-taking, and a pipeline of quick-win projects.
- MTP inspires action: A compelling, ambitious purpose motivates teams to pursue difficult transformations.
- Support for change agents: Leaders must provide protection and freedom for experimentation and fast failure.
- Visible leadership commitment: Leaders should visibly commit time and resources to empower transformation.
What are “Digital Leverage Points” in Why Digital Transformations Fail by Tony Saldanha?
- Strategic focus areas: These are the best places within an organization to apply digital technology for maximum impact.
- Three-step approach: Identify strategic strengths or pain points, understand digital possibilities, and use creative methods like design thinking to generate big ideas.
- Case study—Netflix: Netflix’s success is attributed to leveraging its culture, technology platform, and early detection of disruption as key leverage points.
- Transformational impact: Focusing on leverage points ensures digital efforts drive real business transformation.
How does Why Digital Transformations Fail by Tony Saldanha address “Effective Change Management”?
- Change model selection: Leaders must choose the right change model—organic, edge organizations, or inorganic (acquisitions/partnerships)—based on urgency and culture.
- Managing resistance: The “frozen middle” (middle management) often resists change; reward systems and engagement strategies are needed to overcome this.
- Learning from success stories: Examples like the Y2K fix and P&G’s Gillette integration show how urgency and motivation drive effective change.
- Sustained engagement: Ongoing communication and involvement at all levels are critical for successful transformation.
What is “Strategy Sufficiency” in Tony Saldanha’s digital transformation method?
- Sufficient project volume: Organizations need enough disruptive projects, especially 10X ideas, to fuel sustainable transformation.
- Portfolio management: Use models like Google’s 70-20-10 to balance core, adjacent, and disruptive innovation efforts.
- Failure tolerance: Accept that at least 50% of initiatives may fail, focusing on learning and forward progress.
- Avoiding “innovation theater”: Real transformation requires rigorous execution and portfolio balance, not just superficial innovation activities.
How does Why Digital Transformations Fail by Tony Saldanha recommend organizations stay current with digital technologies?
- Track disruptions, invest wisely: Monitor emerging technologies but invest in applied innovation that delivers quick returns.
- Five disciplined activities: Executive learning, partnerships with VCs and startups, leveraging partner companies, opening data via APIs, and enlisting digital ambassadors.
- Focus on Exponential Five: Prioritize AI, smart process automation, blockchain, robotics/drones, and special-function tech like IoT and 3D printing.
- Quick, disposable solutions: Opt for solutions that pay out rapidly and can be replaced as technology evolves.
What role does culture play in digital transformation according to Tony Saldanha’s book?
- Agile culture is critical: An agile, adaptive culture is the ultimate enabler of perpetual digital transformation.
- Three pillars of agile culture: Customer-focused innovation, adaptive environments, and a shared common purpose drive ongoing evolution.
- Start culture early: Building an agile culture should begin before full synchronization to avoid resistance and ensure transformation sticks.
- Fail-forward environment: Encouraging safe experimentation and learning from failure embeds transformation into the organization’s DNA.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.