MIT Digital Transformation Framework : a techno-structural framework

"Technology changes quickly, but organisations change much more slowly." George Westerman of MIT Sloan calls it his law of digital transformation, and it is the best way into the MIT digital transformation framework, because it contains both its strength and its limit.

MIT's research does not ignore people. Westerman's own summary is that digital transformation is a leadership challenge, not a technology one. What the MIT digital transformation framework offers, though, is mainly a description of what successful large companies have built. It says much less about how a mid-sized company gets its people from here to there.

What is the MIT digital transformation framework?

There is no single document with that name. The phrase usually covers three bodies of MIT work.

The nine elements of digital transformation (2014)

George Westerman, Didier Bonnet and Andrew McAfee grouped what companies change into three areas, each with three elements: customer experience (customer understanding, top-line growth, customer touch points), operational processes (process digitisation, worker enablement, performance management) and business models (digitally modified businesses, new digital businesses, digital globalisation).

Digital mastery (2014)

In Leading Digital, the same team defines "digital masters" as companies strong on two axes at once: digital capabilities and leadership capabilities. Leadership here means vision, engagement, governance and the relationship between business and IT.

The five building blocks (2019)

MIT's Center for Information Systems Research (CISR), with Jeanne Ross, Cynthia Beath and Martin Mocker, identified five building blocks in Designed for Digital: shared customer insights, an operational backbone, a digital platform, an accountability framework and an external developer platform.

A techno-structural framework, by MIT's own description

The "techno-structural" label is not an outside accusation. CISR's research briefing states that three of the five building blocks are technology platforms (the operational backbone, the digital platform and the external developer platform), and the other two are organisational capabilities: shared customer insights and an accountability framework that coordinates autonomous teams.

MIT is also candid about what the blocks do not provide. Jeanne Ross has said the building blocks come without assembly instructions, and that what works best depends on the company. She points to GE as an example of starting in the wrong place: building a platform without a strong operational backbone or strong customer insights. Her advice is to start with the backbone and customer insights, accept that progress will feel slow, and let them drive the platform.

Where the framework stops for a mid-sized European company

The first limit is the sample. Designed for Digital presents itself as practical advice for redesigning "big, old" companies, with examples such as Amazon, LEGO, Philips and USAA. A company of 300 or 3,000 people usually has neither the platform teams nor the change budgets those examples assume.

The second limit is the gap between a target state and a path. The nine elements and the five building blocks describe what to build. The sequence, the pace and the order in which teams take on new work are left to the company, as Ross herself acknowledges.

The third limit concerns people. They appear in the framework as worker enablement, as leadership capability and as autonomous teams inside an accountability framework. These are roles to design. What the framework does not address is the organisation's ability to see how it thinks and decides, which assumptions it never questions and what it failed to learn last time. That capacity is what I call organisational metacognition.

The fourth limit is institutional and comes from my field experience rather than from published research: in much of continental Europe, employee representatives have a say on new technologies before decisions are taken. A roadmap built around the building blocks has to make room for that dialogue from the start.

How to use MIT's framework with a human-centric layer

The five building blocks are a sound target architecture, and Ross's advice on sequencing is worth following. The useful addition is to size each step to what teams can absorb, and to shape the direction with the people who will carry it rather than announcing it to them.

That is the logic of the RESONANCE™ framework: an audit of how the organisation thinks and decides, then scoping, then boundaries agreed with those concerned, before technology choices are locked in. The same reading applies to Gartner's framework, Deloitte's five digital imperatives and Accenture's approach. The full comparison is in 8 digital transformation frameworks ranked.

Three questions before adopting the MIT framework

Is your operational backbone solid? If not, MIT's own research says to start there, not with a platform.

Who decides the order of the work? The framework leaves it to you; make sure the people who will absorb each step have a say in it.

What will you measure besides the building blocks? A platform in production shows that something was built. It does not show that people work differently.

Assess your transformation readiness