MBUS 853 — Session 2: Digital Leadership

Block 1 — Session Theme: From Strategy to Leadership

Why This Session Follows DBS

Session 1 established what digital strategy is and showed a case where it worked. Session 2 asks a harder question: what leadership behaviors turn a good digital vision into a successful transformation — or let a good vision collapse in execution? GE is the deliberate counterweight to DBS: a company whose CEO (Jeffrey Immelt) diagnosed the same shift DBS's Piyush Gupta diagnosed — that data and software would become more valuable than the hardware that produced it — and moved early and aggressively on it. The case's title is blunt about the outcome: "What Went Wrong?"

A correct diagnosis of the future is not the same thing as a successfully led transformation.

GE and DBS both saw the same industry shift coming. Only one of them is still telling that story as a success in 2019.

Two Companies, One Shared Insight

Both DBS and GE bet on the same underlying logic: that whoever controls the data and software layer sitting on top of an asset (a bank account, a jet engine) captures more value than whoever just manufactures or operates the asset. DBS called this "AI to the core." Immelt called it becoming a "top ten software company" and building Predix to occupy the position Microsoft's Windows occupied over the IBM PC ecosystem — the platform other companies' hardware and software had no choice but to interoperate with. The strategic insight was sound enough that the market has largely proven it right since 2019 (AWS, Azure, and Siemens MindSphere are all built on exactly this logic). The session's diagnostic question isn't "was GE wrong to try" — it's "why did the same insight produce DBS's record profits and GE's spin-off."

Reading the Case as a Leadership Post-Mortem, Not a Strategy Failure

Per the course's case-prep protocol, place yourself inside the case's own timeline and use only what the case gives you. The case deliberately declines to resolve its own question — it lists five candidate explanations (flawed vision, flawed execution, bad luck, giving up too soon, or simply needing more time) without picking one. That ambiguity is the discussion: your job is to weigh leadership decisions — sequencing, talent placement, culture management, capital allocation — against a backdrop of genuinely unlucky timing (the 2008 financial crisis's GE Capital legacy, an SEC accounting investigation, a mistimed $10.6B Alstom acquisition) and decide how much of "what went wrong" is attributable to leadership choices versus circumstance.

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

How the Deck Sets Up the Leadership Question

The session's discussion aim, stated directly on the deck's second content slide: examine the challenges with business and technology leadership in digital strategy and execution. Before the article and case, the deck builds four tools for diagnosing where a leadership breakdown is actually happening — a technology-manager/leader typology, a strategic-value grid, a meta-study of why transformations fail, and a ladder of CIO credibility. All four recur directly in the Lenox mini-case and the GE case diagnostic below.

Enabler / Technologist / Strategist / Innovator

Technologist

Transactional × Technology Function

Focused on day-to-day operations, maintenance, and troubleshooting.

Innovator

Transformational × Technology Function

Focused on emerging technologies, experimentation, and taking risks.

Enabler

Transactional × Organization

Focused on optimizing existing operations and aligning technology with business needs.

Strategist

Transformational × Organization

Focused on business strategy and technology's role in achieving strategic objectives.

Direct line to GE: Bill Ruh and GE Digital's San Ramon team were staffed and structured as Innovators — transformational, technology-function-first — without the Strategist half of the quadrant (business-side executives co-owning the platform's role in GE's actual strategy) ever fully engaging. Source: C. Brown et al., Information Systems Management.

The Strategic Grid (McFarlan & Nolan) — Where Does Technology Sit?

	Low Strategic Value	High Strategic Value
High Operational Dependence	Factory — reliability & efficiency focus, existing tech is critical to run the business	Strategic — technology integrated into business strategy, focus on competitive advantage
Low Operational Dependence	Support — cost management focus, technology plays a minimal role	Turnaround — innovation focus, new technology expected to have strategic impact

The deck's worked example (TechOps Inc., a mid-sized manufacturer) assigns different leadership postures per quadrant: Support gets minimal investment and delegation to technology managers; Factory gets moderate executive involvement focused on uptime/security; Turnaround gets selective pilot investment with higher business-led engagement; Strategic gets full executive sponsorship and a business champion. The lesson generalizes past manufacturing: misjudging which quadrant a system sits in — treating a Strategic system with Support-level engagement, or vice versa — is itself a leadership failure mode, independent of whether the technology performs correctly.

Why Digital Transformations Fail — Two Root Causes

Cause 1

Lack of engagement from business management. Source: Sutcliff et al., "The Two Big Reasons That Digital Transformations Fail," HBR.

Cause 2

Lack of business understanding from IT management. Same source.

The deck's meta-study diagram (Vial, Journal of Strategic Information Systems) traces the full causal chain: disruptions (customer expectations, competitive landscape, data availability) trigger a strategic response, which relies on digital technologies, which require structural changes (structure, culture, leadership, employee roles/skills) and are enabled by/affect changes in value creation — all while organizational barriers (inertia, resistance) push back the whole way through. BCG's finding, quoted directly on the deck: 70–95% of digital transformations fail to meet their original objectives, averaging 87.5%. Only 30% meet or exceed target value with sustainable change.

CIO Role and the Three Levels of Technology Leadership

The deck defines the CIO's mandate as three-part: (1) help formulate business-digital strategy, (2) deploy and maintain technology, (3) address business needs and demonstrate leadership. J.D. McKeen's "Levels of Technology Leadership" table (Smith School of Business) then separates CIOs by how far up that mandate they've actually reached:

	Level 1 — Service Provider	Level 2 — Trusted Advisor	Level 3 — Strategic Partner
Objective	Establish competence	Build credibility	Develop partnerships
Audience	Technology staff, operational managers	Business managers	Executive committee, board
Pitfall	Promise more than technology can deliver	Trying to direct business strategy using technology	Automating existing processes, not re-designing
Success Criterion	No news is good news	Technology is consulted about decisions	Technology is at the decision-making table

Where the four leadership types plot on these three levels (per the deck's bar chart): Strategist reaches full Level III (Partnership); Innovator reaches deep into Level II/III; Enabler reaches mid Level II; Technologist stays within Level I. A CIO's actual influence ceiling is a function of which type they're operating as, not tenure or title.

Chief Digital Officer — A Related but Distinct Role

Per G. Westerman (HBR), the CDO exists because "in many companies, digital is a cacophony of disconnected, inconsistent, and sometimes incompatible activities" — the CDO's job is to turn that cacophony into a symphony: a unifying digital vision, coordinated activity, and rethought products/processes. The deck poses a pointed hiring dilemma worth having a position on: choosing between William (internal, proven track record, weak on digital), Sarah (external digital-native talent, e.g. from Amazon), or Sophia (ex-consultant, advised on digital but never built it). The deck's own framing suggests the "right" answer depends on whether the organization's gap is credibility (favors William), capability (favors Sarah), or translation between the two (favors Sophia) — rarely is one candidate strictly dominant.

Digital Transformation and Organizational Change — Two Halves

The deck's simplest but sharpest slide splits change into a personal register (Psychology, Physiology, Anatomy) and an organizational register (Culture, Systems, Structure) — the same "hard infrastructure changes without the soft change-management work" gap that recurs across GE Digital (structure changed via San Ramon, culture never followed) and Lenox (Lifexpress the system shipped; agent culture/incentive change didn't).

Block 3 — Article: Digital Doesn't Have to Be Disruptive (Furr & Shipilov, HBR 2019)

Five Myths About Digital Transformation

Built from interviews with 60+ companies, the article's core argument is a direct challenge to the Immelt-era GE playbook: most successful digital transformations are adaptations of a stable value proposition, not reinventions of it. "For most companies, even those truly threatened by disruption, digital transformation is not usually about a root-and-branch reimagining of the value proposition or the business model."

Myth 1

Digital requires radical disruption of the value proposition

Reality: it usually means using digital tools to better serve the known customer need. Maersk used blockchain to fix supply-chain transparency — it didn't become Google. Aeroflot used dashboards and sensor data to become a better airline, not a different kind of company.

Case parallel: GE aimed squarely at becoming a platform company (Predix as "the next Windows") rather than a better industrial company — the most radical reading of digital transformation on offer.

Myth 2

Digital will replace physical

Reality: it's a "both/and." Galeries Lafayette, Bonobos, and Warby Parker all use physical stores to build the emotional/trust relationship digital can't, while using digital/AI to understand customers.

Case parallel: GE's traditional "selling boxes + maintenance contracts" relationship was itself a trust asset — outcomes-based deals asked customers to abandon it overnight rather than building on it.

Myth 3

Digital involves buying start-ups

Reality: it involves protecting start-ups. Avnet's "guardian angel" role and Galeries Lafayette's accelerator model both deliberately avoid absorbing acquired companies into parent-company bureaucracy.

Case parallel: GE Digital was staffed almost entirely (5,500 hires, 2012–2016) from outside GE and based in San Ramon, near Silicon Valley — the inverse problem: an internal unit with no relationship capital inside its own parent.

Myth 4

Digital is about technology

Reality: it's about the customer. Mastercard Labs' Orange/Red/Green Box process and ING's agile "squads" reorganize people around customer journeys, not systems.

Case parallel: GE's own customer poll found 63% of customers weren't using the data their machines already generated, and 63% weren't performing condition-based maintenance at all — the market wasn't asking for what GE was building yet.

Myth 5

Digital requires overhauling legacy systems

Reality: it's more often about incremental bridging. TUI took three years, built a middleware interface, and replaced back-end modules one at a time rather than all at once. "Attempts to replace multiple complex, mission-critical systems all at once nearly always end in disaster."

Case parallel: this is close to a direct description of Predix's actual rollout problems — a company-wide platform launched against wildly heterogeneous legacy business-unit infrastructure, with a disruptive mid-course switch from internal data centres to AWS/Azure.

"Managers who believe that digital disruption requires wholesale reinvention of the core business end up running in a thousand directions."

— Furr & Shipilov — a near-verbatim description of GE Digital's simultaneous bets across go-to-market model, sales force retraining, cloud infrastructure, and customer education

The uncomfortable overlap: every one of the five "myths" in this article maps onto a specific choice GE made in the opposite direction. That's not a coincidence worth glossing over in discussion — it's the single sharpest analytical thread connecting the article to the case.

Block 4 — Case: Digital Transformation at GE: What Went Wrong?

From "Best-Managed Company" to a $10 Stock

General Electric — founded by Thomas Edison in 1890, matured into one of the world's largest conglomerates with 150,000+ patents (the light bulb, the X-ray machine, the jet engine, the MRI machine) — entered 2019 with its stock near $10, down from over $30 two years earlier, its dividend cut twice (once to just one cent), a fresh credit downgrade, and an active SEC accounting investigation. Culp, installed as CEO on October 1, 2018, inherited a company in crisis.

Three Eras, Three Different Companies

1981–2001 — Jack Welch: Scale and Discipline

Revenue grew 400% ($25B → $130B) via 600 acquisitions including NBC Universal. Required every business unit to be #1 or #2 in its industry. Drove Six Sigma and a "rank and yank" performance culture — later blamed for eroding collaboration and creating a short-term "beat the quarter" earnings culture that persisted into 2019's accounting troubles.

2001–2017 — Jeffrey Immelt: The Digital Pivot

18-year GE veteran executes five strategies: refocus the portfolio toward high-tech/manufacturing, invest heavily in R&D and the "industrial internet," expand emerging-market presence, decentralize the org structure, and — the case's central thread — shift competitive advantage from commoditizing hardware to "smart, connected products." Immelt's stated ambition: transform GE into a "top ten software company."

2011–2015 — Building GE Digital

Immelt hires ex-Cisco executive Bill Ruh (2011) to build an Industrial Internet strategy. GE Digital formally established as a separate business unit in 2015, based in San Ramon, California — deliberately away from existing GE organizations. ~5,500 people hired 2012–2016, almost entirely from tech companies, not GE's own IT organizations.

2017 — Leadership Transition and "Time Out"

Immelt retires; John Flannery becomes CEO. Predix rollout hits a "time out" in May/June 2017 after accumulating technical problems — some from legacy integration complexity, some from platform bugs, compounded by a disruptive mid-course shift from internally built data centres to AWS and Microsoft Azure hosting.

2017–2018 — Compounding Crises

SEC investigates GE's accounting (a sudden $6.2B after-tax charge, a $15B reserve for an undisclosed decade-old GE Capital Insurance liability). GE Power revenue falls 22% as the Alstom acquisition ($10.6B, closed late 2015) proves mistimed against a contracting gas-turbine market — the decision was two years earlier, the damage lands here. Board replaces Flannery with Culp — a rare outside hire for GE's top job, though the case itself doesn't dwell on that — after just 14 months, the fourth CEO transition point relevant to the case in under two years, alongside a CFO, a vice-chair, and half the board departing.

Feb–Jul 2019 — Retreat from the Vision

GE announces it will streamline and refocus on core competencies — "which no longer included GE Digital." Reports emerge GE intends to sell GE Digital; it's ultimately spun off as an independent company expected to survive on its own ~$1.2B revenue rather than further GE funding. Bill Ruh departs; layoffs hit San Ramon.

The Three Go-to-Market Options GE Debated

Option 1 — Bundle

Sell hardware + maintenance as always, but bundle in software/analytics to differentiate and defend margins. Least radical — resists commoditization without asking customers or salespeople to change behaviour.

Option 2 — License + Consult

Sell Predix licenses and specialized consulting as a separate business line, add-on to hardware sales. A distinct new revenue stream, but still a conventional sales motion.

Option 3 — Outcomes-Based Deals (chosen path)

Revenue/profit-sharing tied to measured customer outcomes. GE absorbs implementation risk. Requires deep client trust, new contract-design skills, and reliable shared metrics — the most radical option, and the one GE pursued hardest.

What the Article Would Predict

Furr & Shipilov's evidence base says incumbents succeed by adapting the known value proposition (Option 1-style) while bridging legacy systems incrementally — closer to what actually worked at Maersk, Aeroflot, and TUI than to GE's Option 3 bet.

Block 5 — Where Implementation Broke Down

Four Distinct Failure Points

1. The Predix Rollout

Bill Ruh: "Every one of our products had a different underpinning platform, architecture, technology and set of vendors." Business units with the greatest reliance on legacy infrastructure resisted hardest. Because GE Digital's San Ramon staff were hired almost entirely from outside GE, they lacked the internal relationship capital to win over long-time GE managers — the exact opposite of Furr & Shipilov's "guardian angel" model, where new digital talent is protected and translated into the parent organization by an internal champion.

2. Sales Force Retraining

GE's veteran salespeople excelled at selling "boxes" and maintenance contracts. Outcomes-based selling required them to become, in the case's words, "part business consultant, part contract designer, part software customizer, and part ongoing relationship manager" — while also needing sign-off from more senior client executives than a routine equipment sale ever required. Chief Commercial Officer Kate Johnson: "The customer expects you to talk about outcomes and values — not the best widgets." Explaining why GE widgets were the best was exactly what GE's sales force had spent decades learning to do well.

3. Limited Customer Enthusiasm

63%

of polled customers said machines were connected to networks — but weren't yet using the data

13%

claimed they used data for competitive advantage

63%

were performing no condition-based maintenance at all

CMO Beth Comstock's own framing was blunt: "We're trying to sell them something they don't know they need." Even where GE's education efforts worked, Ruh noted customers realized they'd need "to rethink what they're doing entirely" — a prospect many couldn't quickly act on, regardless of GE's own readiness.

4. Contributing, Non-Digital Difficulties

Not all of GE's 2019 troubles were digital in origin, and the case is explicit that they compounded rather than caused each other: an SEC accounting investigation into "black box" multi-business-unit accounting and quarterly earnings "window-dressing"; a 22% revenue decline in GE Power layered on a mistimed $10.6B Alstom acquisition just as the gas-turbine market contracted; and a legacy of GE Capital's pre-2008 "shadow bank" model, which required a $139B emergency federal bailout and left a $1.5B DOJ settlement over subprime mortgage originator WMC Mortgage. Untangling how much of "what went wrong" is digital-strategy failure versus balance-sheet and governance failure is the case's real analytical challenge.

Block 6 — In-Class Mini-Case: Lenox and Lifexpress

Diana Sullivan's Next Move

Lenox Insurance's CEO James Bennett hired CIO Diana Sullivan a year ago to fix a technology function that had never been Lenox's strength, in a distribution model built entirely on independent agents free to sell competitors' products at will. Diana's flagship project, Lifexpress, cut agent tasks from days down to hours or minutes. A year in, CFO Clay Fontana and James are benchmarking Lenox unfavorably against National Life (a later-starting system rollout that has already trained more agents, reportedly more user-friendly, with younger and more tech-savvy agents) and Manchester Mutual (all insurance products plus some securities on one platform, enabling effective cross-selling). Diana's defense: only 40% of Lenox's product line is on Lifexpress because the disability team hasn't delivered data for input/testing, mutual funds were deliberately excluded pending bug fixes, and — in her words — "our problem is we lack a clear strategy. We jump on every bandwagon... Lifexpress can't fix that." James has ordered a management-committee presentation. Diana knows Lifexpress hit every technical target — on time, on budget, to spec — and is unsettled that this hasn't translated into visible competitive parity.

Diagnosing the Gap Diana Is Actually Facing

Run the deck's "Why Digital Transformations Fail" lens over the dialogue and both causes are present, but on opposite sides of the table. Lack of engagement from business management shows up as the disability team not delivering data on schedule and the CEO/CFO not having resolved which products belong on Lifexpress and in what order — a business-strategy gap, not a coding gap. Lack of business understanding from IT is the risk on Diana's side: has she been pushing the product-strategy question up to James and Clay proactively, or absorbing it quietly as "not an IT issue" while the technology gets blamed anyway? On the Technology Managers/Leaders quadrant, Diana has spent the year operating as an Enabler — optimizing existing operations, meeting agreed specs — when James's demand for a committee presentation is effectively asking her to show up as a Strategist.

Option 1 — Defend the Delivery Record

Restate that Lifexpress was delivered on time, on budget, and to agreed specifications. Accurate and worth stating once, but alone in front of a management committee it reads as defensiveness rather than a path forward.

Option 2 — Race to Match National Life

Rush the remaining 60% of the product line and mutual funds onto Lifexpress immediately to close the visible gap. Optimizes for the appearance of speed but repeats exactly the pattern Clay is already worried about — shipping scope without governance risks a second bug cycle before the first is closed out.

Option 3 — Reframe as a Joint Roadmap (recommended)

Bring data that separates what Lifexpress (the system) delivered from what business governance (product sequencing, disability-team timelines, agent training investment, cross-brand product strategy) has not yet resolved — then propose a named, sequenced roadmap with business-side owners accountable for their own inputs and deadlines.

What the Deck's Frameworks Predict

Diana has met the Level 1–2 CIO bar ("no news is good news," technology consulted about decisions). James's committee demand is the actual opening to move toward Level 3 Strategic Partner — but only if she brings the business-strategy gap into the room herself, rather than delivering a system-status report and waiting to be asked.

Likely class answer: Diana should walk into the management committee meeting with two separate columns, not one defense. Column one: what Lifexpress delivered against its original scope (on time, on budget, to spec, task time cut from days to hours/minutes) — stated once, briefly, as context. Column two: the specific, named business decisions still outstanding that no amount of system speed can substitute for — disability-team data delivery date, a decision on mutual funds and remaining product coverage, and an actual cross-brand product strategy so Lenox stops "jumping on every bandwagon." She should ask James and Clay to assign owners and dates to column two in the same meeting, converting "Lifexpress can't fix that" from a complaint into a governance proposal with her name attached to driving it.

What Diana Should Bring to the Committee

A sequenced product roadmap, jointly owned with each product line (disability, mutual funds, securities), with business-side dates for data/testing inputs — turns "that's not an IT issue" into a concrete cross-functional plan.
An agent-adoption comparison against National Life that separates system speed from training investment and agent demographics — National Life's advantage the case attributes to younger, more tech-savvy agents and an earlier training push, not necessarily a faster system.
A named decision-owner for cross-brand product strategy — since "we lack a clear strategy" is a business-strategy failure Diana identified herself, she should say so plainly in the room rather than let Lifexpress keep absorbing blame for a decision that was never hers to make.

Risk to avoid: raising these points without paired asks reads as blame-shifting onto the CEO and CFO who are already frustrated with her. Every critique above needs a concrete, ownable next step attached to it in the same breath — that distinction is what separates a Strategist-level CIO contribution from a defensive one.

Block 7 — Case Diagnostic: Issues, Decision, Position

Applying the Case Prep Protocol

Step 1 — Who and What

Vantage point: the case is written retrospectively as of late 2019, with Culp newly installed as CEO. There's no single decision maker choosing a path forward here the way there is in a memo case — this is a leadership post-mortem. Core tension: GE diagnosed the same industrial-data shift as DBS and Ant Financial, moved earlier than most industrial peers, and still ended up spinning off the unit it built to capture it.

Step 2 — Five Issues Grounded in Case Facts

Platform ambition outran organizational readiness. Immelt wanted Predix to occupy the position Microsoft's Windows held over the IBM PC ecosystem — but GE's sales force, business-unit IT, and customer base were nowhere near ready for a platform-standard play.
GE Digital was built as an outsider unit. ~5,500 hires, almost entirely from tech companies, based in San Ramon — structurally isolated from the "relationship capital" needed to win internal adoption, per Ruh's own account of uneven business-unit buy-in.
The riskiest go-to-market option was pursued hardest. Outcomes-based deals required a level of client trust and metric-sharing sophistication far beyond GE's traditional box-and-maintenance-contract relationship — and GE's own customer poll showed most customers weren't even using connected data yet, let alone ready to share profit metrics.
Leadership discontinuity fractured the vision's continuity. Immelt (16 years) → Flannery (14 months) → Culp, plus a departing CFO, vice-chairs, and half the board, all inside about two years — with each transition changing GE Digital's strategic priority.
Non-digital crises crowded out the digital narrative. The SEC accounting investigation, the mistimed Alstom acquisition, and legacy GE Capital liabilities consumed leadership bandwidth and capital at precisely the moment GE Digital needed sustained investment and executive attention to work through its rollout problems.

Step 3 — A Position

Underlying problem, one sentence: GE tried to execute the most radical version of digital transformation available (Furr & Shipilov's "Myth 1," pursued in full) using an organization built as an outsider enclave rather than one that protected and translated new capability into the core business (the inverse of "Myth 3") — so when non-digital crises hit and leadership changed twice in two years, there was no internally rooted coalition left to defend the unfinished platform bet.

Counterargument to prepare for: One could argue leadership execution wasn't really the failure — capital allocation discipline was. GE was simultaneously funding a decade-plus platform build, a $10.6B Alstom acquisition, and absorbing GE Capital's legacy liabilities, all while its core Power business was mis-forecasting a declining market. Even flawless digital execution might not have survived that balance-sheet stress. The sharpest response: capital stress explains why GE had no room for error, but it doesn't explain the specific execution choices (outsider-unit staffing, jumping straight to outcomes-based contracts) that made GE Digital fragile even before the crises hit.

Second counterargument — the case's own preferred out: the case explicitly floats "GE gave up too soon; such major change takes far longer than expected." TUI's own bridging fix took three years for a single back-end migration — a company-wide industrial platform plausibly needs a decade. The reply: that's true in the abstract, but GE's board didn't have a decade of runway to test it. The SEC investigation and the Alstom write-downs are what closed the window — which makes the timing itself a leadership and capital-allocation failure, not a rebuttal to one. "Needing more time" and "leadership failed" aren't competing explanations here; the second caused the absence of the first.

30-second answer if cold-called first: "GE and DBS diagnosed the same shift — that data would outvalue hardware — but GE built Predix as an outsider enclave (San Ramon, 5,500 external hires) and went straight to its riskiest go-to-market option, outcomes-based deals, while customers weren't even using the data they already had. That would have been fragile in good times. It became fatal because the SEC investigation and the Alstom write-down cost GE the years it needed to fix the platform rollout — so by the time three CEOs and half the board had turned over, there was no one left inside GE with the standing to defend an unfinished bet."

Block 8 — Discussion Questions & Sharp Answers

Likely Professor Questions

Framing to expect: (1) What did GE get right and wrong in its digital transformation? (2) Was this a failure of vision, execution, timing, or leadership? (3) What would you have done differently as Immelt, Flannery, or Culp?

Q1: GE aimed to become a platform company like Microsoft. Was that ambition itself the mistake?

Not necessarily — the underlying economic logic (whoever owns the data/analytics layer captures disproportionate value from the hardware layer) has since been validated by AWS, Azure, and Siemens MindSphere all succeeding at a similar play. The mistake wasn't the ambition, it was sequencing: Microsoft won its platform position by embedding inside an already-massive existing ecosystem (the IBM PC), not by building a walled-off unit and asking an entire industry to adopt a brand-new standard cold. GE tried to originate the standard rather than embed into one.

At Redamo Labs, the enterprise IAM platform succeeded because it plugged into clients' existing identity infrastructure incrementally rather than asking them to rip out and replace their whole stack — the GE Digital team asked the opposite of its customers.

Q2: Furr & Shipilov say smart companies "protect" acquired digital talent rather than absorbing it. GE Digital wasn't acquired, it was built from scratch — does the lesson still apply?

Yes, and arguably more sharply. The article's "guardian angel" concept exists to solve a translation problem between a new-culture unit and an old-culture parent — a problem GE Digital had in an even purer form, since its ~5,500 hires came almost entirely from outside GE with zero prior relationship capital in the organization they were trying to transform. GE built the isolation the article warns against, without any of the acquisition logic (speed-to-capability, proven product-market fit) that might justify accepting that risk.

Prodigy Education's growth and analytics team worked because it sat inside existing cross-functional teams across three time zones rather than as a separate "innovation lab" — visibility and trust were built in, not bolted on afterward.

Q3: Three CEOs and a spun-off unit later — did GE give up too soon, or too late?

The case explicitly leaves this open, and it's worth taking a real position rather than hedging. Too late is the stronger case: the company had already sunk roughly $4 billion into GE Digital and absorbed years of organizational disruption by the time it retreated — most of the sunk cost was spent before the retreat, not avoided by it. If the platform bet was going to be abandoned, doing so in 2016–2017 (before the SEC investigation and Alstom write-downs compounded the crisis) would have preserved more capital and leadership credibility than doing so in 2019, once GE was managing multiple simultaneous fires.

This is the strongest question to lead with in class — it forces the room past "GE messed up" into a falsifiable claim about timing that can be argued with case evidence (the $4B figure, the 2017 "time out," the 2018 CEO change) rather than hindsight.

Block 9 — Participation Hooks & Taju's Edge

How to Contribute Distinctively

Session 2 still carries no memo, so the payoff is entirely in discussion quality and setting the team's tone before memos begin in Session 3.

Open Strong

Don't open with "GE's strategy failed." Open with the parallel to Session 1: DBS and GE diagnosed the identical shift in value from hardware to data/software — only one of them is still telling that story as a success. That framing sets up a leadership-execution discussion instead of a strategy-critique discussion.

Push the Consensus

Class will likely say "GE moved too fast" or "GE's leadership changed too often." Push further: GE built its digital unit as a structural outsider (San Ramon, external hires) rather than embedding it — that single organizational design choice explains both the slow internal adoption and the fragility once leadership changed.

Bridge to the Article

Every one of Furr & Shipilov's five myths maps directly onto a GE choice made in the opposite direction — naming that mapping explicitly is a strong, source-grounded contribution few in the room will have structured this cleanly.

Bridge to the Mini-Case

Both Lenox and GE feature a technology delivery that hit its own metrics while a business-side governance gap (product strategy at Lenox, cross-brand platform ambition at GE) got blamed on the system instead — a clean thread to draw explicitly if the mini-case comes up before or after the GE discussion.

Taju's Edge — Redamo Labs

Directing IAM strategy for 50,000+ users required incremental integration into clients' existing identity stacks — a live counter-example to GE Digital's "adopt our new platform standard" approach.

Taju's Edge — Prodigy Education

Cross-functional growth teams embedded across three time zones (not a separate innovation unit) drove Prodigy's 200% engagement lift — direct contrast to GE Digital's San Ramon isolation.

Taju's Edge — Stutern

Scaling Stutern from zero to 100,000+ users meant staying close to the existing customer relationship at every step rather than betting the business on an unproven new value proposition — the discipline GE's outcomes-based bet lacked.

Block 10 — Reflections Journal Prep (Concept Options + Example Prompts)

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

Per the syllabus (Appendix B) and the course's ban on generative AI in submitted work, this block only narrows down which slide concept to reflect on and offers prompts to help you surface your own real example. The actual 150–200 word concept description and 150–200 word example need to be written by you, in your own words — concept strictly from the class slides, example strictly from your own professional/personal experience, never from the article or case.

Candidate Concepts — Straight From the Session 2 Slides

Technology Managers & Leaders

The Enabler / Technologist / Strategist / Innovator quadrant (transactional vs. transformational × technology function vs. organization). Fits if your example is about a leader — or you — moving from delivering technology to shaping strategy.

The Strategic Grid

Factory / Support / Turnaround / Strategic — McFarlan & Nolan's operational-dependence × strategic-value matrix. Fits if your example involves misjudging how much executive attention a system actually deserved.

Levels of Technology Leadership

Service Provider → Trusted Advisor → Strategic Partner (J.D. McKeen). Fits if your example is about a technology leader — or you — earning a seat at a more strategic table over time.

Why Digital Transformations Fail

Lack of engagement from business management / lack of business understanding from IT management (Sutcliff et al.). Fits if your example involves a transformation stalling specifically because of a business-IT disconnect.

Organizational Change: Culture/Systems/Structure vs. Psychology/Physiology/Anatomy

The deck's split between organizational-level and individual-level change. Fits if your example is about a system or structure changing faster than the people inside it did — or vice versa.

Chief Digital Officer Role

G. Westerman's "turning digital cacophony into a symphony" framing, plus the William/Sarah/Sophia hiring dilemma. Fits if your example involves choosing between insider credibility and outsider digital capability.

Questions to Surface Your Own Example

Use these to find the right real memory — don't write the example straight from the prompt itself:

Where have you, or a leader you worked under, delivered a technically sound project on time and on budget, only to watch its business impact lag because of a gap the technology side didn't control?
Where has a transformation you were part of survived — or failed to survive — a change in its sponsoring leadership?
Where have you seen "the system changed" outrun "the people/culture changed," or the reverse?
Redamo Labs, Prodigy Education, AfroShorts, Haven, and Owo are all worth checking against whichever concept you pick above — but the fit has to be genuine, not forced to match.

Block 11 — Key Takeaways

What to Walk Away Knowing

A correct strategic diagnosis is necessary but not sufficient. GE saw the hardware-to-data value shift as clearly as DBS did — the gap was entirely in organizational execution.

Isolating digital talent from the core business trades speed for adoption risk. GE Digital's outsider staffing model (San Ramon, external hires) meant technical capability was never the constraint — internal trust and relationship capital was.

The most radical version of a strategy is rarely the one that survives contact with execution. Furr & Shipilov's evidence favors incremental adaptation of a known value proposition; GE chose the most disruptive option (outcomes-based deals) available to it.

Leadership continuity is itself a transformation capability. Three CEOs, a departing CFO, and half a board in under two years didn't cause GE's digital difficulties, but it removed any chance of a sustained internal champion working through them.

A technology team can hit every delivery metric and still take the blame for a business-strategy gap. Lifexpress shipped on time, on budget, to spec — Lenox's real gap (unclear product strategy, slow disability-team data, agent training investment) sat one level up, on the business side. Diana's task is to make that visible, not to keep absorbing it quietly.

Looking Ahead — Session 3: Digital Landscape

→ Session 3 (Landscape)

Session 2 asks "what leadership behaviors make or break execution?" Session 3 (AI Won't Give You a New Sustainable Advantage; DeepSeek case) asks "what happens to a hard-won capability advantage when a competitor can replicate it almost overnight?" — a direct continuation of the GE Digital fragility theme, applied to AI moats specifically.

↔ Recurring Thread: Platform Ambition

GE's Predix-as-platform bet recurs conceptually through Sessions 4–5 (Organization, Architecture) as the underlying question of how much centralization/standardization a digital transformation should attempt versus how much modularity it should preserve.

Memos Begin Session 3

This is the last no-memo session. Team Case Study Memos are due Thursday before Session 3 at 11:59pm — confirm team roles and memo-writing logistics before this session ends.