Incorrect password.
MBUS 853 — Session 7 (Final Session)

Digital Renewal

Queen's Smith AMBA 2027 · October 5, 2026 · Prof. Salman A. Mufti
How Incumbents Survive and Thrive Washington Post Case DevOps & Technical Debt Application Portfolio Management Responsible Digital Management Memo #5 Due — Thu 11:59pm ↓ Deck
Block 1 — Session Theme: Renewal Isn't a Finish Line

From Surviving Disruption to Sustaining Reinvention

Sessions 1–6 each examined a company mid-transformation — strategy, leadership, landscape, organization, architecture, implementation. Session 7 closes the course with a different question: after a transformation succeeds, how does an incumbent keep renewing itself, rather than treating the transformation as a project with an end date? The Washington Post is the course's clearest success story — CEO Fred Ryan's own answer to "are we out of the woods yet?" is blunt: "The woods are endless; we will never be out because the woods are growing."

Only 17 of today's Fortune 500 didn't exist in 1995. The other 483 have been around, in some shape or form, since that year.
Birkinshaw's headline finding — most incumbents survive disruption. The real question this session asks is how, and at what cost of continuous effort.

A Direct Callback to the Article's Own Example

Birkinshaw's article states outright: "The newspaper industry is still in flux — with paper and online versions alongside each other — 25 years in." That's not a generic aside; it's a direct reference to the exact industry the case studies. The Post is effectively the article's own example, given a full case-length treatment — useful to note explicitly in discussion.

Block 2 — Frameworks from Prof. Mufti's Slide Deck

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:

ResponseWhat The Post didRisk
Double Down (build on strengths)Amplified journalism, hired more journalists and data scientists, reinforced fact-based journalism while moving to a digital-first newsroomMarket 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 playersHard 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 infrastructureCan 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 streamLoss 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.
Block 3 — In-Class Mini-Case: BBI and the People-Analytics System

Trust the Algorithm or Your Instincts?

The situation. Aliyah Jones, VP of sales and marketing at Becker-Birnbaum International (BBI), must pick a new marketing director. Molly Ashworth is her trusted protégé from cleaning products; she built a promising subscription service and knows Aliyah's business intimately. Ed Yu is a high performer from the beauty division who grew FreshFace sales 60% in three years. HR's new AI people-analytics system rates Ed a 96% match and Molly 73%.

What happens. Ed interviews early with well-researched answers. Molly asks for a formal interview to neutralize her relationship advantage, and performs well. HR leader Christine Jenkins and data scientist Brad Bibson show network analyses: Ed has broader relationships across BBI, while Molly's are concentrated in cleaning products. But the algorithm is brand-new and has informed only three promotion decisions, too few to validate. Aliyah worries the reviews and resumes feeding it already carry bias. Christine says the tool is meant to broaden judgment, not replace it, and then reveals that Ed is a flight risk and Molly is not.

CHRISTINE: "You wouldn't launch a new product or a new campaign without data. HR decisions should be approached the same way." — BRAD: analytics can help managers rely "more on the data and less on gut instinct," but "our algorithm is brand-new." — ALIYAH: "I'd trust the algorithm more if I understood it better."
Source: J.T. Polzer, Harvard Business Review (edited and adapted, per deck)
The question posed in class: What do you think Aliyah should do?

The deck's own answer key, "Applying the Strategic Mindset": it reuses Session 1's Business Problem → Business Solution ← Technology sequence and crosses out the shortcut from technology problem to technology solution.

1

Begin with the business problem, not the algorithm. BBI's problem is selecting the person most likely to succeed in the role, not "which candidate scores higher."

2

Define the business solution before choosing the technology. Leadership decides what the role requires (deep category knowledge like Molly's, or cross-divisional reach like Ed's), and only then decides which data is relevant. A 96% "match" means nothing until someone says what it is matched against.

3

Treat ethics as a business requirement. Fairness, employee privacy and explainability belong in the solution design, not bolted on afterward. Aliyah's bias worry is exactly Blackman's point: AI trained on historical reviews can reproduce past bias at scale.

4

Design the business process to govern the technology. Structured interviews, transparent selection criteria, independent reviewers and clear accountability. These controls should decide how the algorithm is designed and used, not the reverse.

5

Use technology to inform, not replace, accountable leadership. Aliyah stays responsible for the decision. The best answer combines validated data with informed human judgment, and three data points don't make a validated model.

A position to take: don't pick a candidate yet. Pick the criteria. Write down what the role needs, have an independent reviewer score both candidates against those criteria in structured interviews, and treat the 96/73 split as one unvalidated input. If the role is about scaling Molly-style subscription innovation inside one category, Molly's depth wins. If it's about cross-divisional marketing, Ed's network is real evidence (it comes from network data, not the black-box score). Either way, price in Ed's flight risk, which is a business fact and not an algorithm output. The trap to name: Aliyah's confidence in Molly and the algorithm's confidence in Ed are both unexplained, so neither is a tiebreaker on its own.
Bridge to the whole course: the BBI answer key is Session 1's strategic mindset reapplied to an AI decision about people, and Course Conclusion question 2 asks it directly: "To what degree should I deploy digital technologies to replace human work and judgment?" It also mirrors Session 6's Vanir Bancorp, where frontline staff worried an AI credit model would "discriminate against the very customers we strive to serve." Two sessions in a row, the professor has picked a mini-case where AI is technically ready and the blocking issue is governance and trust.
Block 4 — Article: How Incumbents Survive and Thrive (Birkinshaw, HBR 2022)

Digital Disruption Has Been Oversold

Birkinshaw's research on the Fortune 500 and Global 500 from 1995–2020 challenges three widely believed myths: that every sector is under threat, that disruption happens quickly and is accelerating, and that established firms are struggling to adapt. Of 1995's Fortune 500, only 35 went bankrupt; 198 remained on the list in 2020; the rest merged, were acquired, or simply grew too slowly to stay ranked — a very different story from wholesale replacement by "17 new digital-native firms."

Four Ways to Respond to Disruption

Offense · Existing Markets

Double Down

Play to existing strengths rather than chasing the disruption directly. Disney built on its movie franchise strength (Pixar, Marvel, Lucasfilm) before launching streaming, using its content library as leverage against Netflix rather than competing head-on immediately.

Offense · New Markets

Fight Back

Take on the disrupter at its own game — a new unit, acquisition, or joint venture. High risk, mixed track record: Microsoft has struggled against Google in search; GM's Maven car-sharing service, meant to rival Uber, went nowhere.

Defense · Existing Markets

Retrench

A defensive move from weakness — consolidation, lobbying for regulatory protection, managed decline. Hard to sell to stakeholders; "a CEO who says we aren't capable of responding... isn't likely to be in the job very long."

Defense · New Markets

Move Away

Migrate existing competencies into new markets. Thomson Corporation sold its newspaper business and moved into information services (later merging with Reuters); Fujifilm redeployed chemical expertise into health care and materials.

"Judgment beats paranoia... a fixation on disruption gets you into trouble, because when you're so focused on the risks of coming late to a new technology, you ignore the perhaps greater risk of moving too quickly."
— Birkinshaw, citing Eli Lilly's $300M biotech write-off, GM's abandoned EV1, and Time Warner–AOL's $54B write-off as cautions against overcorrecting
Where The Post fits (per the deck, slide 26): Prof. Mufti places The Post in all four quadrants at once: Double Down (bigger, digital-first newsroom), Fight Back (Next Gen Task Force, social-first content), a mild Retrench (no risky acquisitions or moves into unfamiliar sectors; process and infrastructure improvements) and Move Away (Arc XP as a new SaaS business). Birkinshaw allows hedging early but warns that "eventually you need to get off the fence." That makes the sharp question: is running four responses at once a deliberate portfolio, or a company that hasn't chosen yet?
Block 5 — Case: Digital Transformation at The Washington Post: Innovating for the Next Generation

From Six Years of Decline to "The World's Most Innovative Companies"

Founded in 1877, The Washington Post built its reputation on Katharine Graham-era investigative journalism (Watergate, the Pentagon Papers) before industry disruption and the 2008 financial crisis drove six straight years of declining revenue. In 2013, Jeff Bezos bought The Post for $250 million through his personal holding company, ending 42 years of public trading and four generations of Graham family ownership. He brought in Fred Ryan — Politico cofounder, former Reagan chief of staff — as CEO and publisher in 2014.

The Renewal Playbook

01
Digital-Product Mindset
02
Rebuild the Newsroom
03
Redesign Core Processes
04
Tech + Journalism Excellence
05
Build Arc XP
06
License It Externally
07
Next Gen Task Force

CIO Shailesh Prakash (ex-Motorola, Sun, Netscape, Microsoft, Sears) found "product development had slowed to almost a standstill" on arrival in 2011 — his fix moved the org from "babysitting systems" to "building and inventing digital products," empowering engineers to work directly, co-located, with newsroom partners rather than routing every request through a spreadsheet-driven approval process. One pivotal meeting: a 60-person, one-hour review of a red/yellow/green stakeholder-request tracker ended with the realization that what the newsroom actually needed required minimal engineering effort — "a revelation in terms of how much the bureaucracy of constant debate had stifled both stakeholders and product developers."

Rebuilding, Not Just Retooling

The newsroom had been cut by a third in the decade before Bezos's purchase (580 employees in 2013); by 2021 it was on track to reach 1,010 — the largest in Post history — with new roles emphasizing data scientists, graphic/data designers, and software engineers who could turn complex stories into interactive visualizations (2020 election-night voting models were a widely cited example). The Post also built out 26 foreign bureaus (its largest-ever foreign corps), added AR storytelling, audio content, and three video studios.

Monetization Through Constant Experimentation

The Post ran roughly a dozen live experiments at any given time — moving from a 20-story paywall to 10 to 5, then to dynamic paywalls that offered a subscription only after detecting genuine reading commitment (e.g., repeated views of a specific columnist). Results: 111.6 million unique website visitors in January 2021 (3 million more than the New York Times that month) and the second-highest number of paying digital subscribers in the world, at 3 million.

Block 6 — Arc XP: A Business Within a Business

From Internal Tool to Global SaaS Platform

Arc XP began as an internal technology platform built to solve The Post's own publishing challenges — Fast Company later described it as "The newspaper created a platform to tackle its own challenges. Then, with Amazon-like spirit, it realized there was a business in helping other publishers do the same." Prakash framed the strategic logic as a deliberate blue-ocean move: "To build technology for The Post and then 'Arc-ify' it for other publishers" — adjacent, not head-to-head, competition.

Arc XP by the Numbers (2021)

1,500+
client sites across 25+ countries, including LA Times, Chicago Tribune, El País, Infobae
1.5B+
unique visitors per month across the Arc XP platform
$100M
projected annual revenue, with Arc Commerce expected to triple it within three years

The Unresolved Internal Debate

Despite Arc XP's scale, the case is explicit that its future inside The Post was genuinely contested: "The pace of hiring created an internal debate about whether this collection of talented engineers was being used properly in the service of either a perceived competitor or an adjacent industry... when the newsroom had plenty of needs of its own." Open questions the case leaves unresolved: Is Arc XP operating in enough of an adjacency? Is Arc XP on path, or off path? Prakash's own framing — "We need to figure out the ultimate steady state for Arc... today, I'm glad somebody like Fred is at the helm, because he trusts and he believes in it" — signals confidence without resolution.

Why this matters for the diagnostic: Arc XP is simultaneously The Post's clearest "move away" bet (the deck's classification: a new, high-growth business serving media and non-media clients, with the risk of losing focus on the core) and its most exposed strategic ambiguity — a $100M "business within a business" with no confirmed long-term ownership logic relative to the core journalism mission.
Block 7 — Memo Protocol: Team Case Study Memo #5 (Final Memo)

Format Reminder Before the Team Writes

Due Thursday 11:59pm before Session 7, based only on the Washington Post case, two pages, 11-point font, written wholly by the team — the last of five graded memos.

To Fred Ryan, CEO and Publisher — the case's closing questions (about the Next Gen task force's roadmap) are his to answer, making him the clean single decision maker.
Issues Exactly 5, each grounded in a specific case fact — Gen Z's social/aggregator news consumption habits, Arc XP's unresolved strategic identity, reliance on Bezos's ownership model, the "endless woods" transformation-fatigue risk, and structural print-to-digital ad revenue shifts are all strong, distinct candidates.
Problem/Decision 40–60 words on the underlying cause — consider whether the root issue is audience/distribution, monetization, or organizational focus, since these point toward different recommendations for the Next Gen roadmap.
Alternatives Exactly 3, mutually exclusive, feasible, not simultaneous, not status quo.
Criteria Exactly 3 standards for judging the alternatives.
Evaluation/Recommendation 120–140 words, pros/cons per alternative per criterion, no table, ending in a justified pick.
Actions Exactly 3 steps not already taken in the case.
Case-only constraint: this case closes with the Next Gen task force's questions explicitly unanswered — resist the pull to resolve them using real-world knowledge of what The Post did after 2021. The case's own five open questions (subscription funnel, younger audiences' trust in fact-based reporting, willingness to pay, consumption format/timing, and how to leverage Arc XP) are the strongest source material for the memo's Issues section.
Academic integrity — GenAI is banned in submitted work for this course. The diagnostic analysis below is discussion prep, not memo text — the team's actual submission must be written independently.
Block 8 — Case Diagnostic: Issues, Decision, Position (Discussion Prep)

Applying the Case Prep Protocol

Step 1 — Who and What

Decision maker: Fred Ryan, CEO and Publisher. Core challenge: The Post has, by any measure, already successfully renewed itself — record subscribers, record ad revenue, a thriving $100M SaaS business — but the Next Gen task force's own founding premise is that success with today's audience doesn't guarantee relevance with tomorrow's, since younger and more diverse audiences consume news through fundamentally different channels than the ones that drove the current success.

Step 2 — Candidate Issues Grounded in Case Facts

  1. Gen Z bypasses direct distribution entirely. The share of Americans using social media to access news had nearly doubled to 48%, with Gen Z far more likely than earlier generations to use social media and news aggregators instead of visiting washingtonpost.com directly — undermining the subscription funnel the current model depends on.
  2. Arc XP's strategic identity remains genuinely unresolved. The case's own open questions ("is Arc XP on path, or off path?") show that even Prakash, its architect, hasn't settled whether it's a core adjacency or a distraction from journalism's needs.
  3. Deep dependence on a singular ownership model. Bezos's biweekly engagement, patient capital, and hands-off editorial stance have been pivotal to recruiting engineering talent who'd otherwise join Facebook, Google, or Microsoft — a structural advantage that is not obviously replicable or permanent.
  4. Transformation fatigue risk. Ryan's own "the woods are endless" framing is honest, but it also signals no stable end-state is coming — a risk the ANZ case (Session 6) showed can strain an organization if not actively managed.
  5. Ad revenue's structural shift isn't fully resolved. Print advertising declined sharply industry-wide without an equally offsetting rise in digital advertising for many publishers — The Post's RED team and Zeus ad-tech stack are a genuine answer, but the case doesn't show whether this fully closes the gap long-term.

Step 3 — A Position

Underlying problem, one sentence: The Post's renewal playbook (digital-product mindset, in-house engineering excellence, constant experimentation) was built to win and monetize readers who visit washingtonpost.com and its owned apps directly — but the Next Gen task force's own data shows the audience The Post most needs to secure its next decade increasingly never arrives at that direct destination at all, meaning the playbook that produced the current success may not be the one that secures the next generation.
Counterargument to weigh: One could argue The Post doesn't need a fundamentally new playbook — Birkinshaw's "double down" logic suggests leaning harder into what already works (trusted, fact-based journalism, Arc XP's distribution reach through partner sites) rather than chasing younger audiences on platforms The Post doesn't control. The strongest response has to weigh whether meeting Gen Z where they already are (aggregators, social) is a distribution-channel adjustment consistent with doubling down, or whether it requires a genuinely different, unproven business model — closer to Birkinshaw's riskier "move away" quadrant.
Second counterargument — the more urgent open question may not be about audience at all: the case leaves two things genuinely unresolved, not one: the Next Gen task force's audience questions, and Prakash's own "is Arc XP on path, or off path?" With 150 more engineering hires planned and Arc XP already a "business within a business," one could argue Ryan's more consequential near-term decision is settling Arc XP's steady state — because that choice determines how much engineering capacity, capital, and executive attention is even available to act on whatever the Next Gen task force recommends. Chasing younger audiences with an organizationally unresolved Arc XP risks repeating GE Digital's mistake from Session 2: building offense before the organization backing it has a settled identity.

Step 4 — 30-Second Cold-Call Answer

The Post's transformation is the course's clearest success — 111.6 million monthly visitors, 3 million paying subscribers, and a $100 million SaaS business in Arc XP — but Fred Ryan's own framing is the point: "the woods are endless." The same playbook that won this decade (digital-product mindset, in-house engineering, constant A/B experimentation on paywalls and formats) was built around readers who visit washingtonpost.com directly. The Next Gen task force exists because Gen Z increasingly doesn't — 48% of Americans now use social media to access news, and Gen Z leans on aggregators and social platforms The Post doesn't control. So the real decision isn't whether The Post can adapt again — it's proven it can, repeatedly — it's whether winning a Gen Z audience means extending the same test-and-learn discipline to distribution itself, or whether it requires resolving Arc XP's own unsettled identity first, since that engineering capacity is what would build whatever the Next Gen roadmap recommends.
Block 9 — Discussion Questions & Sharp Answers

Likely Professor Questions

Framing to expect: (1) What made The Post's digital transformation succeed where others failed? (2) Which of Birkinshaw's four strategies best describes The Post's approach? (3) How should Ryan answer the Next Gen task force's open questions?
Q1: Which of Birkinshaw's four adaptation strategies best describes The Post's transformation?
All four, which is the professor's own answer on slide 26, so open with that rather than picking one. Double Down: trusted, fact-based journalism, with the newsroom grown to its largest-ever size. Fight Back: the Next Gen Task Force and social-first content aimed at digital competitors. Retrench: mild, with no risky acquisitions and steady process and infrastructure improvement. Move Away: Arc XP, a new SaaS business. Most of Birkinshaw's examples pick one lane. The distinctive point is that The Post runs Move Away from strength rather than in retreat, the opposite of Thomson or Fujifilm, and funds it from capability the core business needed anyway. The deck names the risk of each: Double Down if young readers devalue the format, Fight Back because it's easy to mistime, Move Away because it can pull focus from the core.
Redamo Labs pursued a similar hybrid — doubling down on trust and compliance credibility (the core asset enterprise clients pay for) while simultaneously building genuinely competitive in-house verification technology, rather than choosing between brand trust and technical capability.
Q2: Was building Arc XP as an external SaaS business a distraction from The Post's core journalism mission, or a legitimate extension of it?
A legitimate extension, on the case's own evidence, though the internal debate is fair to take seriously rather than dismiss. The engineering capability Arc XP monetizes externally is the same capability that powers The Post's own digital product excellence — the platform wasn't built as a side project, it was "Arc-ified" from tools already required internally. Revenue from 1,500+ external clients also means The Post isn't solely dependent on its own subscription and ad revenue for the capital needed to keep investing in engineering talent — a genuine diversification of risk, not just of revenue.
Owo's underlying data infrastructure, if it were ever licensed to other retail-investor platforms in adjacent markets, would face the identical question Arc XP faces — whether the core product's technology is a sellable adjacency or a resource-diverting distraction. The Post's evidence suggests the answer depends on whether the internal need funded the build in the first place.
Q3: How should Ryan and the Next Gen task force answer the case's core open question — can The Post win younger, more diverse audiences who increasingly don't visit washingtonpost.com directly?
By extending the same test-and-learn discipline that built the current subscription model to distribution itself, not just content or pricing. The Post already has direct evidence this works — it was Snapchat's first editorial partner, first to announce breaking news on Alexa, an early Facebook Journalism Project partner, and the first national publisher to test Subscribe with Google. The Next Gen answer is very likely a continuation of that meet-audiences-where-they-are experimentation, applied more aggressively to the platforms (TikTok, aggregators, algorithmic feeds) where Gen Z actually spends attention — with Arc XP's own technology potentially providing the infrastructure to do this faster than competitors.
This is the strongest question to close the course on — it's a direct, evidence-backed extrapolation of a pattern The Post has already proven works (distribute where the audience is, monetize with patience) rather than a leap into an unproven new strategy.
Block 10 — Participation Hooks & Taju's Edge

How to Contribute Distinctively — Final Session

This is the last graded discussion of the course — a strong, distinctive contribution here closes out Team Class Contribution (20%) on a high note.

Open Strong

Don't open with "The Post successfully digitized." Open with the paradox: The Post is Birkinshaw's own cited example of an industry "still in flux, 25 years in" — even its clearest success story admits the disruption threat never fully resolves, just changes shape.

Push the Consensus

Class will likely credit Bezos's capital and patience as the key success factor. Push further: capital explains why The Post could afford to experiment, but the digital-product mindset shift (empowering engineers, killing the spreadsheet-approval bureaucracy) explains why the experiments actually worked — capital without that cultural shift would have just funded more failed pilots.

Bridge the Whole Course

Use this session to explicitly connect back to Session 1: DBS and The Post both prove Sunil Gupta's "digital leadership wheel" claim — you can't create a separate digital unit, you have to embed digital in the organization's DNA. Closing the loop back to Session 1's frameworks is a strong signal of synthesis across the full course.

Use the Deck's Own Map

The deck files Arc XP under Move Away. Push it: Move Away is normally a retreat (Thomson sold its newspapers). The Post is the rare incumbent moving away from strength while doubling down on the core, and Arc XP was funded by engineering the newsroom needed anyway. That's why the "loss of focus" risk is smaller than it looks.

Connect Case to Deck

The Post's turnaround is a DevOps story. Prakash ended the 60-person red/yellow/green approval meeting and co-located engineers with the newsroom, which maps to the deck's collaborative and continuous principles. A dozen live paywall experiments is CI/CD applied to the business model.

Answer the Legacy-vs-New Question

If the prof asks how to fund new apps against legacy, answer with APM before opinion: retire the low-value/low-condition quadrant first to free part of the 70% "run" budget, then make Replace candidates compete with new builds on value and TCO. Name barrier #2 (owners won't give up apps) as the real constraint.

Taju's Edge — Redamo Labs

99.9% uptime and 95% CSAT reflect the same "engineering excellence in service of trust" logic that let The Post's technology platform become credible enough for 1,500+ external publishers to depend on.

Taju's Edge — Prodigy Education

Running continuous A/B testing across a 150M-user platform is a smaller-scale version of The Post's "half a dozen experiments running at any given time" — proof that constant, disciplined experimentation compounds into durable competitive advantage.

Taju's Edge — Stutern (Exited)

Stutern's exit is itself a data point in Birkinshaw's favor — most ventures (like most incumbents) don't get disrupted into oblivion; they get acquired, merged, or evolve, which is a very different, less dramatic story than the "disrupt or die" narrative the article debunks.

Block 11 — Reflections Journal Prep

The Deck Is Available — Pick a Concept and Write the Entry Yourself

The concept half must come from the Session 7 slides only, with no article, case or external sources. The deck is in hand, so the candidates below are real slide concepts. Pick one, confirm the professor emphasized it in class, and write the 150–200 words yourself. The slide that reminds you to write the entry also restates the rule: one key concept from the session slides and one specific example from professional experience or personal observation. The journal (any 5 of 7 sessions, one Word file, cover page, each entry on its own page) is due October 15, 2026 at 11:59 PM.

Candidate Concepts — Straight From the Session 7 Slides

Any one of these is a defensible 3–7 word concept identification

  • Digital Renewal versus Digital Transformation: transformation creates capabilities, while renewal keeps them operational, useful, secure, efficient and adaptable. Beyond the definition: renewal is a permanent operating cost, not a phase after the project.
  • Technical debt: the cost of supporting sub-optimal or legacy technology, inevitable through age and change. Beyond the definition: it's a business risk and a finance problem, so it needs measurement, a budget and business ownership.
  • Application Portfolio Management (Reassess/Renew/Retire/Replace): technical condition × business value, sized by cost. Beyond the definition: the hardest barrier is political (owners won't give apps up), not technical.
  • DevOps and the CI/CD cycle: development, QA and operations in one continuous, automated cycle, built on five principles (iterative, continuous, collaborative, systemic, automated). Beyond the definition: Agile in development alone just moves the bottleneck to the handoff.
  • Responsible digital management ("ethical nightmares"): name the harms to prevent, then build content and structure to govern them before deployment. Beyond the definition: fairness is a leadership judgment, not an engineering one.
  • Begin with the business problem, not the algorithm: the BBI strategic-mindset slide (business problem → business solution → technology, with ethics as a business requirement and technology informing, not replacing, accountable leaders).

Write your own 150–200 words: describe the concept, then add the insight that goes beyond the definition. That second part is what separates an A+ entry from a summary.

Candidate Example — Pairs Best With Digital Renewal or Technical Debt

Redamo Labs — Treating a Finished Project as an Unfinished One

After the IAM verification overhaul shipped and hit its 75% time-reduction target, the instinct across the team was to treat it as complete and move attention fully elsewhere. Revisiting it three months later, purely to check for drift, surfaced a subtle issue: a subset of international users were quietly experiencing longer verification times again as their document types changed, a slow regression nobody had been watching for once the project was declared "done." Fixing it required treating the original success not as a finish line but as a new baseline to keep defending. The lesson generalizes past this one project: the instinct to declare victory and stop watching is exactly the instinct that lets a working system quietly decay, and the fix is building in the expectation, from the start, that nothing digital ever actually reaches a permanent finished state.

Block 12 — Course Arc: How Sessions 1–7 Connect

The Throughline Across Seven Sessions

Each session asked a different question about the same underlying challenge — how organizations use digital capability to create and sustain competitive advantage. Read together, they form a single argument.

Session 1 (Strategy) — DBS Bank: digital strategy is business strategy informed by technology, not a parallel track. DBS proved a correct diagnosis, well executed, compounds into durable advantage.
Session 2 (Leadership) — GE: a correct diagnosis is not sufficient. GE saw the same shift DBS did and still failed, because leadership continuity, culture, and organizational buy-in weren't built alongside the vision.
Session 3 (Landscape) — DeepSeek: even flawless execution doesn't guarantee a sustained advantage — visible, easily-copied capability erodes fast; durable advantage lives in harder-to-replicate underlying assets.
Session 4 (Organization) — Pernod Ricard: the same technology, the same team, the same company can produce wildly different adoption outcomes depending on whether a tool asks people to execute differently or think differently.
Session 5 (Architecture) — Harley-Davidson: foundational "digital defense" work has to be uniform before "digital offense" bets pay off — and stakeholder trust can break faster than architecture can be fixed.
Session 6 (Implementation) — ANZ Bank: how a transformation is sequenced is itself a strategic choice — big-bang, company-wide rollouts skip the discovery a smaller, sequenced approach would have surfaced early.
Session 7 (Renewal) — The Washington Post: even a successful transformation isn't a finish line — the capability that won yesterday's audience has to keep evolving for tomorrow's, indefinitely.
Business Problem/Opportunity → Business Solution, informed by (not dictated by) Technology Problem/Opportunity.
The Session 1 principle the entire course has tested against seven very different companies — DBS, GE, DeepSeek, Pernod Ricard, Harley-Davidson, ANZ, and The Washington Post all succeed or struggle in direct proportion to how well they honored this sequencing.
Digital transformation is business transformation, not just a technology deployment.
Prof. Mufti's own one-line lesson across all seven cases (deck slide 28), and the same claim the Session 1 principle above makes

The Professor's Three Closing Questions

Conclusion 1

Differentiation

How can I leverage digital capabilities to help further enhance the differentiation of my company?

Conclusion 2

Human Judgment

To what degree should I deploy digital technologies to replace human work and judgment? (This is the BBI mini-case.)

Conclusion 3

Whose Philosophy

Whose philosophy do I want within the digital transformation, mine or the vendor and consultant's? (This echoes "build your own approach" on the articles slide.)

Framework

Eight Elements, Not Seven

The closing framework adds Digital Partnership (leverages external expertise) alongside the seven session topics, with Renewal "ensuring sustainability for ongoing change."

What's Left in the Course

Journal Due

Individual Reflections Journal (5 of 7 entries, 40%) is due October 15, 2026 at 11:59pm — confirm all five session concepts have been captured from live slides before then.

Memos Complete

All five Team Case Study Memos (40%) conclude with this session's Washington Post submission — no further memos are due.

Team Contribution

Team Class Contribution (20%) is graded on quality and diversity of participation across all seven sessions — this final session is the last opportunity to add a distinctive, evidence-grounded voice to that record.

MBUS 853 · Session 7 Prep (Final Session) · Queen's Smith AMBA 2027 · Prof. Salman A. Mufti · All 5 Team Memos Complete (40%) · Reflections Journal Due Oct 15, 2026 (40%)