Renewal Is an Operating Discipline, Not a Second Transformation
The deck's stated objective: examine concepts and discuss challenges with digital operations, application portfolio, and responsible management. Where the article asks how incumbents respond to disruption and the case shows The Post doing it, the deck supplies the less glamorous mechanics of keeping a transformation alive: running it (DevOps), paying down what it accumulates (technical debt), pruning what it built (APM), and governing what it can harm (responsible digital management). It also closes the whole course, so it doubles as the course review.
Digital Transformation creates new capabilities. Digital Renewal keeps those capabilities operational, useful, secure, efficient and adaptable over time.
The deck's definition of the session. Note that it is narrower and more operational than the "sustained reinvention" framing in Block 1.
The Four Dimensions of Digital Renewal
Efficient
How Software Ships
Continuously improve how digital applications are built, released, monitored and restored. This is where DevOps and CI/CD live.
Useful
What Software Stays
Invest in the right applications while consolidating, modernizing and replacing those that no longer justify their cost. This is where APM lives.
Responsible
What Could Go Wrong
Review digital assets (data, applications, infrastructure) regularly for vulnerabilities, dependencies and emerging risks.
Adaptable
What It Can Become
Maintain a resilient and sustainable technology foundation that can evolve with changing needs and constraints.
Responsible Digital Management (Blackman, HBR)
Organizations must anticipate the ethical consequences of emerging technologies before deploying them, not after harm, scandal or regulation. Leaders should explicitly name their organization's "ethical nightmares": discrimination, privacy violations, fraud. Emerging technologies amplify risk even without malicious intent:
- AI learns from historical data and can reproduce discrimination at scale.
- Quantum computing may make already-opaque "black-box" decisions even harder to understand or challenge.
- Blockchain makes information and rules hard to alter, so poor early governance can lead to irreversible privacy breaches, fraud or losses.
Ethics is a leadership responsibility. Engineers can explain how a system works, but fairness, accountability and harm are business judgments. Manage ethical risk before deployment through Content (which nightmares, their causes, who is affected, what follows) and Structure (governance, controls, workflows, oversight, monitoring).
Good intentions are not enough; modern technologies can produce enormous harm through ordinary business processes, flawed data and weak governance. Responsible digital management is a must.
The deck's key message on responsible digital management (adapted from R. Blackman, HBR)
Digital Operations and DevOps
Digital (IT) Operations are the processes and services the technology department runs in production: hardware, OS and application upgrades, network and systems administration, authentication, device management, remote access, backup/restore and help desk. The deck lists the usual pathologies: too many costly, overlapping applications on mixed or legacy platforms; staff stuck reacting to short-term problems with repetitive tasks; bureaucratic change policies; and limited ability to run both classical and modern methodologies.
DevOps is a set of practices, tools and policies built on agile principles that brings development, testing and operations into the same cycle. It requires much tighter coordination between Software Development, QA and IT Operations, organized around a Continuous Integration / Continuous Deployment (CI/CD) loop.
DevOps Principles 1–3
Iterative · Continuous · Collaborative
Suits high-uncertainty work that doesn't need a comprehensive plan; aims for continuous delivery into testing and deployment and is never "done"; all stakeholders share objectives, mission and metrics.
Source: C. Haight, Gartner (per deck)
DevOps Principles 4–5
Systemic · Automated
Applies agile principles to operations and removes as many delivery constraints as possible; automates the links between development, testing, integration and deployment wherever practical, for fast, safe, cost-effective delivery.
Source: C. Haight, Gartner (per deck)
The deck's pizza analogy for CI/CD: without it, chefs (developers) make pizzas all shift and nobody checks them until 6 PM, when everything goes out at once (manual deployment). Some are raw or have pineapple nobody ordered (bugs), and the delivery team (operations) takes the blame. With CI/CD, every finished pizza (code change) goes onto a conveyor belt (pipeline), automated QC checks crust, toppings and cooking (automated testing), failures go straight back, and passes go straight to delivery (continuous delivery).
In-class question: ShopVirtual. A fictional e-commerce company builds features with Agile, but handoffs to a separate IT Operations team cause slow releases (months), frequent production issues and many rollbacks (reverting to a previous version after a bad update). What should management do? The deck's own answer is DevOps. Make it concrete: (1) merge dev, QA and ops into shared teams with shared release and stability metrics, so ops isn't blamed for code it didn't write; (2) build a CI/CD pipeline with automated testing so defects are caught per change rather than per release; (3) ship smaller, more frequent releases so each rollback is cheaper and rarer. The point to make: Agile in development alone just moves the bottleneck to the handoff.
Technical Debt
Technical debt is the cost to an organization of supporting sub-optimal or legacy technology: aging hardware, operating systems and applications. It is inevitable through age and change (incremental development, M&A, new regulation, platform shifts). The deck's sources: poor application design and UX; integrating multiple technologies across application versions; insufficient or overly complex architecture (multiple platforms or versions); development practices that changed without being standardized; and applications built in haste that are hard to upgrade.
What to do about it: measure it (maintenance, defect and integration-cost metrics); partner with risk and security to tie it to quantifiable business risk; take a business point of view so business and technology stakeholders choose mitigations together; manage it explicitly with plans, budgets, an IT-Finance specialist and Total Cost of Ownership (TCO); and, most importantly, take an Application Portfolio Management approach.
Application Portfolio Management (McKeen & Smith)
APM is an ongoing process of categorizing, assessing and rationalizing the hardware, OS and application inventory to decide what to maintain, invest in, replace or retire. Its goal is the best use of the capital and operating funds allocated to building and maintaining applications.
50%+
of applications in most established organizations are legacy
70 / 30
typical technology budget split: existing systems vs. new systems
3
APM barriers: flat budgets, owners who won't give anything up, IT's limited political clout
Application Portfolio Analysis: technical condition (vertical) × business value (horizontal), with bubble size representing cost.
Reassess · High Condition, Low Value
Technically sound but not earning its keep. Ask whether it still has a business purpose.
Renew · High Condition, High Value
Keep investing. These are the assets the business actually runs on.
Retire · Low Condition, Low Value
Sunset it. Costs money and creates risk for little return.
Replace · Low Condition, High Value
The business needs what it does, but the technology can't carry it. Rebuild or swap.
APM barriers, ranked by the deck: (1) constrained budgets while IT keeps absorbing new applications with flat headcount; (2) arguably the biggest: few business managers want to give up an application once installed, because "the agony of change is clearly not worth the rewards"; (3) IT management often lacks the political clout to make the business rationalize and sunset applications.
In-class question: When resources are limited, how should an organization balance funding new digital applications against maintaining the legacy systems people already depend on? A deck-grounded answer: don't treat it as a new-vs-old budget fight. Run the portfolio analysis first. Retiring the low/low quadrant and consolidating overlaps frees part of the 70% "existing" budget, then Replace (high value, poor condition) competes with new builds on business value and TCO, not on who shouts loudest. The hard part is barrier #2, which is political, so the business, not IT, has to own the sunset decisions.
The Deck's Read on The Post: Responses and Risks
The deck maps The Post onto Birkinshaw's four responses, with a risk for each, and places it in all four quadrants:
| Response | What The Post did | Risk |
| Double Down (build on strengths) | Amplified journalism, hired more journalists and data scientists, reinforced fact-based journalism while moving to a digital-first newsroom | Market may shift faster; younger audiences devalue traditional formats |
| Fight Back (attack disruptive forces) | Next Gen Task Force, a social-first strategy, new digital content to compete with digital players | Hard to execute and easy to mistime |
| Retrench (defend territory) | Didn't explicitly retrench, but avoided aggressive acquisitions or risky moves into unfamiliar sectors; improved processes and infrastructure | Can signal defensiveness and managed decline |
| Move Away (enter new business) | Arc XP: built for internal use, then sold to external clients as a high-growth revenue stream | Loss of focus on the core; diversification needs new capabilities |
Correction to this page's earlier framing: this prep originally called Arc XP "fight back." The professor files it under Move Away and files Next Gen and social-first content under Fight Back. Use the professor's mapping in class and in the memo's language. The interesting argument it opens: Move Away is usually Birkinshaw's defensive quadrant (Thomson, Fujifilm), but The Post is running it from strength, alongside Double Down, not instead of it.
The deck also lays out a Business Model Canvas for The Post with three customer segments: subscribers (older, US and DC-metro for print; growing global digital), advertisers (end-to-end partnerships, data analytics) and Arc XP customers (other newspapers, SaaS platform). Revenue: subscriptions (print; digital all-access, premium, academic), advertising (print and digital) and Arc XP. Channels include search, app stores, social platforms and Apple/Amazon/Google voice assistants. The "older" subscriber label is the Next Gen problem written into the canvas itself.
The Course Review Slides
Articles mapped on two axes. The deck plots all seven articles on strategic ↔ executional (what the advice focuses on) × incremental ↔ radical (how much change it calls for). On the slide, Competing in the Age of AI is the most strategic and radical. How Incumbents Survive and Thrive (straddling the centre line) and AI Won't Give You a New Sustainable Advantage are strategic and incremental. Digital Doesn't Have to Be Disruptive and Discovery-Driven Digital Transformation are executional and incremental. Stop Tinkering with AI is executional and radical, and Building the AI-Powered Organization sits at the centre, leaning radical. Prof. Mufti's point: the articles give differing, sometimes conflicting advice because transformation is context-dependent. "Don't just follow some general approach. Build your own approach through your own research and decision making."
Digital transformation is business transformation, not just a technology deployment. It requires organizations to rethink their strategy, structure, processes and culture.
Prof. Mufti's stated lesson across all seven cases (slide 28)
Framework for Digital Transformation, now with eight elements. The closing framework adds Digital Partnership (leverages external expertise) to the seven session topics: Strategy (integrates technology with business), Leadership (creates champions of change), Landscape (enables efficiency and innovation), Organization (supports collaboration and governance), Architecture (establishes a blueprint for scalability), Implementation (structured yet flexible deployment), and Renewal (ensures sustainability for ongoing change).
Session takeaways, per the deck: treat Digital Operations as mission-critical, with DevOps breaking down silos between users, management, development, QA (including automated testing), operations and security. Technical debt is a problem, and APM reduces portfolio cost and complexity and improves technology investment decisions.