MBUS 853 — Session 7: Digital Renewal

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 — 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: the case shows a company doing something the four-quadrant model doesn't fully capture on its own — simultaneously doubling down on its core asset (trusted, investigative journalism) and fighting back by building genuine, competitive-grade technology capability (Arc XP) in-house, rather than choosing one quadrant. Birkinshaw's own framework allows for hedging early, but flags that "eventually you need to get off the fence" — worth testing whether The Post has actually chosen a lane or is still successfully hedging across two.

Block 3 — 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

Digital-Product Mindset

Rebuild the Newsroom

Redesign Core Processes

Tech + Journalism Excellence

Build Arc XP

License It Externally

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 4 — 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 evidence of successful "fight back" (competing directly against dedicated media-tech vendors) 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 5 — 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 6 — 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

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.
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.
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.
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.
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 7 — 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?

A genuine hybrid of double down and fight back, sustained longer and more deliberately than the article's own examples. The Post doubled down on its core asset — trusted, investigative, fact-based journalism, expanding the newsroom to its largest-ever size — while simultaneously fighting back by building competitive-grade engineering capability from scratch (Arc XP) rather than buying or partnering for it. Most of the article's examples pick one lane; The Post's five-plus years of parallel investment in both is closer to what Birkinshaw calls "hedging your bets" under high ambiguity — except The Post never fully resolved off the fence, and arguably didn't need to, because both bets paid off.

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 8 — 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.

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 9 — Reflections Journal Prep (Fill In After Class)

Concept Must Come From Live Slides — Last Chance for a Sixth or Seventh Entry

As with Sessions 2–6, the journal's concept half needs to be captured live from Prof. Mufti's Session 7 slide deck. Since only 5 of 7 sessions' entries are required, this is either the final entry needed or a spare in case an earlier session's entry needs replacing before the October 15, 2026 deadline.

Concept — Fill In From Session 7 Slides

[3–7 word identification — write after class]

150–200 words, from class slides only. Renewal-focused candidates to listen for: organizational ambidexterity, continuous reinvention, digital renewal cycles, or incumbent-response frameworks — write down whichever the professor actually presents.

Candidate Example — Ready to Pair With Whatever Concept Fits

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 10 — 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.

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.