Decide Teaching note · Case 11

The Network That Lived on Desktops

This note reveals the outcome. Participants should decide the case first, on their own devices, before the discussion.

Who it was
Facebook's shift to mobile, 2012
The question
Do you reorganise the whole company around the phone, rebuilding your apps and putting ads into the mobile news feed itself, while your existing business is still on the desktop?
What they chose
Make the phone the primary product. Rebuild the apps natively for each platform, move engineers into product teams that all build for mobile, and put ads directly into the mobile news feed.
Judgement
Paid off Strong process
Session length
60 minutes, for 4 to 40 participants

Learning objectives

  1. Recognise the innovator's dilemma when users move to a new screen before revenue does.
  2. See why reorganising the company, not only the product, was necessary.
  3. Weigh short-term pressure from public investors against long-term position.

Session plan

  1. 0–5 min Read the situation, what is known and unknown, and the voices in the room. No discussion yet.
  2. 5–13 min Each participant chooses an option on the case page, states a confidence and writes a one-line pre-mortem: if this choice fails, the most likely reason is…
  3. 13–28 min Debate by option. Ask each group to describe the company's organisation chart a year later under its option.
  4. 28–33 min Reveal the outcome.
  5. 33–50 min Discuss the public admission that the earlier approach had been a mistake, the reorganisation into product groups, and the costs of putting ads into a personal feed.
  6. 50–60 min Transfer: participants identify where their own users are moving faster than their organisation.

The case page records each participant’s choice, confidence and pre-mortem in their own browser, and scores the confidence once the outcome is revealed. Nothing is sent anywhere, so it can be used in any classroom.

Questions before the reveal

  1. Your prospectus says you earn almost nothing from mobile. Why not wait until you know how to?
  2. What does it cost to rewrite the apps natively, and what does it cost not to?
  3. Is there a way to put ads in a mobile feed that users will accept?

Questions after the reveal

  1. The share price roughly halved before the numbers turned. What made it possible to bear that?
  2. Why did the attempt to own a layer of the phone, a year later, fail?
  3. Which costs of this decision do the revenue figures not show?

The key facts on one page

  • The network had 845 million monthly users and more than 425 million mobile users in December 2011.
  • Its prospectus warned that it did not generate meaningful revenue from mobile.
  • Shares priced at $38 in May 2012 fell to about $17.55 by September.
  • Mobile was about 23 percent of advertising revenue at the end of 2012 and about 53 percent a year later.

Where discussions go wrong

  • Seeing the outcome as inevitable. Many established companies failed the same transition.
  • Leaving out the costs to users of a more intrusive, more attention-hungry product.

The forces at work

  • The innovator's trap: The desktop business was profitable, growing and well understood. Mobile users were growing faster but earned almost nothing. Every rational short-term signal pointed to protecting the desktop, which is exactly how established companies miss shifts.
  • The cost of a previous bet: The company had spent about two years building its mobile apps in web technology. Abandoning that work meant admitting a costly mistake in public, just as investors were judging the company for the first time.
  • Two sides of the network: Users and advertisers had to move together. Ads that annoyed users could shrink the audience advertisers were paying to reach; an audience with no ads could not pay for the service.
  • The pressure of a share price: As a newly public company, every quarter's revenue would be scrutinised. The temptation was to optimise for the number analysts watched rather than for where users were going.
  • The view from outside: Earlier platform shifts, from mainframes to personal computers and from desktop software to the web, had punished leaders who stayed loyal to the old screen. The base rate was not on the side of caution.

The lesson to carry out of the room When your users move to a new screen, follow them before your revenue does, and rebuild the product for that screen rather than shrinking the old one to fit.

Pairs well with: The idea Why Good Management Fails and the essay on social media.

Where this comes from

Sources

  1. Facebook, Inc., Form S-1 registration statement, 1 February 2012. 845 million monthly active users and more than 425 million mobile monthly active users in December 2011; risk factor on not generating meaningful mobile revenue and not displaying ads in mobile products.
  2. “Facebook Amends IPO S-1 To Admit Advertising Biz Hurt By Increasing Shift To Mobile,” TechCrunch, 9 May 2012.
  3. “Facebook HTML5 vs native apps,” The Register, 14 September 2012. Zuckerberg at TechCrunch Disrupt on the HTML5 bet.
  4. “11 takeaways from Zuckerberg's first interview since Facebook's IPO,” NPR member stations, 11 September 2012.
  5. “Facebook shakes up engineering teams in mobile move,” Inquirer Technology, September 2012.
  6. Tom Simonite, “How Facebook Slew the Mobile Monster,” MIT Technology Review, 6 March 2013.
  7. “Facebook introduces mobile app install ads,” Social Samosa, October 2012.
  8. “Facebook Stock Nears IPO Float Price,” Silicon UK, 2013.
  9. “Facebook Q4 2013 Earnings. Mobile Drives 53% Of Revenue,” Marketing Land, January 2014.
  10. “HTC First sales reportedly so bad that AT&T is discontinuing it,” TechRadar, May 2013.
  11. Meta Platforms, “Meta Reports Fourth Quarter and Full Year 2025 Results,” 28 January 2026.

Teaching note by Shrikant Kumar. Free to use in classrooms and workshops with attribution.

How to cite

Shrikant Kumar. “Teaching note: The Network That Lived on Desktops.” Decide case teaching note, Telos. https://shrikantk.com/decide/the-network-that-lived-on-desktops/teaching/

↑ ↓ to move↵ to open⌘K to toggle