---
id: "question-cost-of-transformation"
type: "open-question"
source_timestamps: ["§ 1. Create and maintain high-quality data."]
tags: ["roi", "resource-allocation"]
related: ["concept-digital-transformation-1-0"]
resolutionPath: "Case studies detailing the budget, team composition, and executive communication strategies Lenovo used to sustain a 5-year data infrastructure project."
sources: ["tail1"]
sourceVaultSlug: "hbr-seg-tail1"
originDay: 1
articleStem: "hbr-tail-107-lenovo-ai-supply-chain"
sourceUrl: "https://hbr.org/2026/05/how-lenovo-built-an-ai-powered-supply-chain"
sourceTitle: "How Lenovo Built an AI-Powered Supply Chain"
---
# What was the capital and resource cost of Lenovo's Phase 1?

**Open question:** What was the capital and resource cost of Lenovo's Phase 1?

The article notes that Lenovo spent five years fixing its data infrastructure ([[concept-digital-transformation-1-0]]) before building serious AI models. It does *not* detail the financial cost, the size of the engineering teams required, or how executive sponsorship was maintained during a 5-year period with no immediate AI ROI. This gap is precisely where the contrarian bet in [[contrarian-patience-over-speed]] is hardest to execute in practice.

**Resolution path:** Case studies detailing the budget, team composition, and executive communication strategies Lenovo used to sustain a 5-year data infrastructure project.

> **Enrichment note:** Agile/"staged-delivery" schools would answer this by running small, tangible-value pilots *in parallel* with foundation-building to keep sponsorship alive — a tension the source does not resolve.