When adaptation works Paired case study

Microsoft: Make the new thing countable, and the old thing undeniable.

How Microsoft made its cloud direction visible, changed the reporting around it and recognised the cost of the phone strategy it was leaving behind.

This case examines measurement as an instrument of organisational change: making an emerging business visible before it dominates the accounts, exposing progress to scrutiny and acknowledging when an earlier commitment no longer holds.

Case Microsoft
Period 2014-2015
Download as PDF

Why this case

The same lever, pulled the other way.

Read this alongside Silicon Valley Bank. Both cases ask what happens when an organisation changes the way it measures its own position.

In the bank's case, changes to the assumptions behind its tests made an underlying exposure less visible. The position being tested had not improved.

Microsoft's transition offers a contrasting use of measurement: making an emerging cloud business more visible, publishing a target against which progress could be judged and changing its reporting structure to reflect its strategic direction.

Alongside that transition, Microsoft recognised a substantial impairment against its phone acquisition. The financial record acknowledged the deterioration of an earlier bet while the company made its new direction more explicit.

Make the new thing countable. Make the old thing undeniable.

Changing a measure can expose reality or obscure it. The direction of the change is the finding.

The record

What happened.

A change of direction becomes visible through product choices, published measures, financial recognition and, eventually, a different reporting structure. Watch what changes beyond the language of the strategy.

  1. A new chief executive. An inherited commitment.

    Satya Nadella becomes Microsoft's third chief executive. Windows remains central to the business, while the acquisition of Nokia's Devices and Services business, agreed under his predecessor, is still awaiting completion.

  2. A visible product choice

    Office arrives on Apple's tablet.

    Microsoft releases Office for iPad before a comparable touch-first version for Windows tablets. One of its most valuable products is made available on a competing platform.

    The strategic implication is visible: extending the reach of Office can take precedence over protecting Windows exclusivity.

  3. The phone acquisition completes.

    Microsoft completes its acquisition of substantially all of Nokia's Devices and Services business on 25 April. The commitment was inherited, but its completion takes place under the new leadership.

  4. Making the emerging business visible

    Cloud gets a headline number.

    Microsoft reports a commercial cloud annualised revenue run rate of $5.5 billion, alongside quarterly company revenue of $26.5 billion.

    The figures measure different things: the run rate annualises a month's revenue; the quarterly total records revenue already earned. The run rate gives the emerging cloud business a prominent measure of its own.

  5. The organisation is restructured.

    Microsoft announces an organisational change aligned with its strategic direction as a productivity and platform company. Changes to the financial reporting segments follow in the next financial year.

  6. Recognising the earlier bet

    A $7.5 billion impairment enters the record.

    Results published on 21 July for the quarter ended 30 June include a $7.5 billion non-cash impairment relating to the Nokia acquisition and a further $780 million restructuring charge.

    Microsoft reports a quarterly operating loss of $2.1 billion. The impairment formally recognises a substantial reduction in the carrying value of the acquired assets.

  7. FY2015 report

    The new direction carries a public target.

    The annual shareholder letter sets out an ambition to reach a $20 billion commercial cloud annualised revenue run rate in financial year 2018. At the end of financial year 2015, the run rate exceeds $8 billion.

    A directional statement now has a number and a date against which progress can be judged.

  8. Changing the reporting

    The new segments are presented.

    Microsoft presents three reporting segments: Productivity and Business Processes, Intelligent Cloud, and More Personal Computing. The new basis applies from financial year 2016, with comparative figures recast for earlier periods.

    The reporting structure now gives the strategic direction a different financial frame. Intelligent Cloud includes established server businesses as well as cloud services; it is not the same measure as commercial cloud revenue.

The direction became visible in what Microsoft released, measured and recognised. Then the reporting changed to reflect it.

The record, continued

Make it visible before it becomes material.

An emerging business can matter enormously to the future while contributing relatively little to today's results. That creates a problem: the strategic direction can remain difficult to see inside the numbers leadership already follows.

Giving the new direction a headline

Cloud had a number people could follow.

In January 2015, Microsoft reported a commercial cloud annualised revenue run rate of:

$5.5bn A measure of the commercial cloud business's revenue pace, reported alongside the company's quarterly results.

This made progress in the emerging business easier to distinguish from the performance of Microsoft's much larger established activities.

The institutional value was visibility: leaders, employees and investors had a recurring number against which the cloud direction could be discussed and judged.

A useful measure makes the direction visible. A credible one also leaves room for disappointment.

The diagnosis

Two organisations. One lever.

Both cases involve changes to how an organisation measures its position. The distinction is what those changes make easier to see - and what they allow to disappear.

The paired case

Silicon Valley Bank

  • The existing tests exposed a problem.
  • Modelling assumptions were changed.
  • The reported position became more reassuring.

Less visible

A more comfortable result did not, by itself, mean that the underlying exposure had been reduced.

This case

Microsoft

  • The strategic direction was changing.
  • Cloud progress received a prominent measure.
  • A public target made the remaining gap visible.

More visible

The measure gave people something specific to follow, question and compare with the company's stated ambition.

The strategy changes. The old numbers keep winning.

A new direction can be announced without changing the information that governs everyday decisions. The board pack stays familiar. The established business remains easier to explain, easier to compare and easier to defend.

When the emerging business has no clear measure of its own, progress can remain a matter of narrative. Its sponsors describe promise; its critics point to its small contribution to today's results.

Microsoft's reporting choices made the new direction more legible. They did not guarantee success, but they created a clearer basis for judging whether the transition was progressing.

A new strategy needs more than a place in the presentation. It needs a place in how the business is judged.

The diagnosis, continued

The write-off was the other half.

Giving the new direction a measure is only part of the work. The organisation must also recognise what has happened to the commitments it is moving away from.

An organisation can add a dashboard for a new initiative while continuing to defend the assumptions behind the old one. Both strategies remain alive in its reporting, its resource commitments and its explanations of performance.

Microsoft's phone impairment made a substantial loss of value explicit in the financial record. The acquisition had completed in April 2014. Results for the quarter ended June 2015 recognised a $7.5 billion impairment relating to the acquired assets.

The impairment itself was non-cash. It reduced the carrying value of assets and reported earnings; it did not represent a new $7.5 billion cash payment in that quarter.

Recognition changes what can still be defended.

The institutional significance is an interpretation: formally recognising the deterioration made it harder to maintain that the original bet retained its earlier value. The accounts now reflected a changed assessment.

That does not establish why every decision was made. It does show that the financial record was revised rather than left carrying the earlier valuation.

The pattern worth examining

Make room for the new assessment.

A change of direction becomes more credible when the institution updates its account of the earlier bet. Otherwise, people are asked to pursue a new future while continuing to justify the assumptions it replaces.

The practical discipline is to review old commitments as seriously as new opportunities, and let the evidence change the valuation, the resources or the decision.

What the record does not establish

An impairment is not an optional gesture.

Accounting rules require impairment when the relevant conditions are met. We should not assume management could legitimately have delayed recognition or spread the loss across several years.

Nor does the filing prove that the charge was taken primarily to send a cultural signal. The narrower finding is sufficient: the deterioration was recognised, publicly and at substantial scale.

Make the new direction visible. Let the record of the old one change too.

Against the model

What was present.

This is predominantly a Wave Two case, with two Wave One attributes doing important enabling work.

The Shortboard model describes twelve attributes across three cumulative waves. Here, four attributes provide a useful interpretation of the observable decisions. The remaining eight are not established by this episode. That is a limit of the evidence, not a verdict on whether those capabilities existed elsewhere in Microsoft.

Wave One

Lean dependability

  • Scrappy Resourcefulness Evidenced in this episode
  • Healthy Conflict Not established here
  • Ruthless Consolidation Evidenced in this episode
  • Distributed Ownership Not established here
Wave Two

New growth

  • Continuous Reinvention Not assessed here
  • Structural Fluidity Evidenced in this episode
  • Strategic Optionality Not assessed here
  • Platform Thinking Evidenced in this episode
Wave Three

Perpetual relevance

  • Pioneer Sanctuaries Outside this episode's scope
  • The Awe-Driven Mindset Outside this episode's scope
  • The Pioneer's Leap Outside this episode's scope
  • Supply-Driven Optionality Outside this episode's scope

Highlighted attributes describe behaviours visible in this case. They are not a company-wide capability score or proof that those behaviours were sustained over time.

What each one looked like in practice.

Behaviours rather than qualities. The connection to the model is our interpretation; the underlying decisions are visible in the record.

Wave One

Scrappy Resourcefulness

Using an explicitly constructed run-rate measure to make the emerging commercial cloud business legible alongside a much larger established company.

The instrument gave people a way to follow progress before the new direction dominated the accounts. Its usefulness depended on disclosing how it worked and reading it alongside conventional financial results.

Wave One

Ruthless Consolidation

Recognising the deterioration of the phone acquisition through a substantial impairment, alongside a restructuring of the business.

The impairment was an accounting requirement, not proof of discretionary courage. Its institutional significance was that the financial record no longer carried the earlier valuation unchanged.

Wave Two

Structural Fluidity

Changing the organisational structure and then the reporting segments to reflect the strategic direction, with earlier financial periods recast for comparison.

This went beyond redrawing an organisation chart: the information used to assess performance and allocate resources changed too. It does not, by itself, establish distributed decision-making.

Wave Two

Platform Thinking

Releasing Office on Apple's iPad demonstrated that reaching users on another platform could take precedence over Windows exclusivity.

The visible choice broadened where Microsoft's software could create value. The product no longer had to serve only the company's own operating system to earn its place.

Study the capabilities the record supports. Do not award the others by association.

The aftermath

What they got wrong.

Recognising a failed commitment does not erase its cost. And a successful strategic transition does not establish that every part of the organisation is healthy.

The error inside the transition

The acquisition still completed.

The Nokia deal was agreed under the previous chief executive, but it completed in April 2014 under the new leadership. The substantial impairment recognised the following year is evidence of how far the value of that commitment deteriorated.

It does not, by itself, establish what cancellation options were available at completion or what those options would have cost. The narrower lesson remains: recovering from an unsuccessful commitment is different from avoiding it.

The later finding that qualifies the success story

A federal review found serious weaknesses in the security foundation.

In its 2024 review of the summer 2023 Microsoft Exchange Online intrusion, the US Cyber Safety Review Board identified failures in security controls, risk management and public accountability.

Operating discipline

The Board attributed the intrusion's success to multiple avoidable errors and identified weaknesses in the protection and management of critical authentication infrastructure.

Risk management

It found that security investment and risk management had received insufficient priority, and judged Microsoft's security culture inadequate.

Correcting the record

The Board criticised Microsoft's delay in correcting inaccurate public explanations of the incident, despite repeated questioning during the review.

Read the Cyber Safety Review Board report (PDF) →

A successful transition is evidence of a capability. It is not a character reference for the whole institution.

The conclusion

Your strategy needs to reach the board pack.

If the direction has changed, what has changed in how the organisation judges progress?

A new strategy can receive its own presentation while the regular reporting pack continues to tell the old story. The established measures remain prominent, comparable and connected to accountability. The new direction remains a promise.

Microsoft's transition illustrates a practical response: make the emerging business visible, explain the measure, attach a target and adapt the reporting structure. Alongside that, recognise when an earlier commitment has lost value.

None of those acts guarantees a successful strategy. Together, they make it harder for the organisation to avoid judging whether its stated direction is becoming real.

Three questions for your own team.

  1. If our strategy is working, which measure should show progress first - and does it appear in the regular board pack?

  2. What are we still reporting because we always have, and which assumptions or commitments does that keep protecting?

  3. Which earlier bet needs to be reassessed, reduced or stopped - and what evidence would make us act?

Make progress visible early. Make revision possible before commitment becomes defence.

The Shortboard lesson

Make the future visible. Let the past be reassessed.

Microsoft's transition illustrates how organisational judgement depends on the information through which a business sees itself. An emerging direction needs to become visible enough to be judged. Existing commitments need to remain open to revision when their assumptions no longer hold.

Give the emerging business an instrument.

The cloud run rate made a developing business easier to follow before it dominated Microsoft's accounts. The transferable discipline is to make progress legible early, disclose how the measure works and keep its limitations visible.

Change the reporting with the direction.

Structural Fluidity includes changing how performance is understood and resources are allocated. Microsoft's new segments and recast comparisons gave the strategic direction a different financial frame, beyond the announcement of an organisational restructure.

Keep earlier commitments open to evidence.

The phone impairment formally recognised a substantial deterioration in value. For leaders, the wider lesson is to revisit existing bets with the same discipline applied to new proposals. A past commitment should not make its assumptions immune to examination.

Examine the foundation separately.

Wave Two progress cannot establish Wave One reliability. The later security review demonstrates why operating discipline, risk management and accountability need direct scrutiny, even when the commercial story appears compelling.

The evidence

How we know this. And what we don't.

The financial record is unusually useful here: published figures, disclosed methods and reporting changes can be examined without relying solely on retrospective accounts of a successful transformation.

What makes this strong.

  • The cloud run-rate figures, impairment charges and financial results were published while the transition was happening.
  • The calculation behind the run rate was disclosed, allowing readers to distinguish an annualised measure from revenue already earned.
  • The reporting-segment changes and recast comparisons are documented in company disclosures and regulatory filings.
  • The later security findings come from an external federal review rather than a retrospective company success story.

What to hold lightly.

  • Filings establish reported actions and results. They do not reveal every internal debate, available alternative or decision-maker's motive.
  • A run rate is a constructed measure. Its prominence does not make it a complete account of the business's economics or risks.
  • The connection between these decisions and the Shortboard attributes is an interpretation, not a capability assessment conducted inside Microsoft.
  • The later security review cannot establish that the same weaknesses existed throughout the preceding decade, or that the cloud transition caused them.

Sources and further reading.

The useful question is not whether Microsoft succeeded. It is which behaviours another institution could examine, test and apply.

Read the paired SVB case Explore all case studies