What We Can Learn From Facebook About Managing Change

Teresa Torres argues that even improvements to a product will trigger resistance, because users must adjust to any change. She contrasts Facebook's rocky rollout of the News Feed and Beacon with its smoother launch of Timeline. The difference, she suggests, lies in advance announcement, opt-in early adoption, listening to early users, and a firm deadline for full rollout. These steps help product teams separate the normal discomfort of change from genuine product feedback. The lesson matters because teams that ship good changes can still be judged harshly if the transition is mishandled.

01Key takeaways

• Expect resistance to any change, even improvements users asked for, and plan for the adjustment period.
• Announce significant changes well in advance so users can socialize the idea before it affects them.
• Offer opt-in early access to receptive users to gain control, reduce backlash, and gather focused product feedback.
• Use early adopter feedback to refine the product before imposing the change on everyone.
• Set a firm deadline for full rollout so the change does not drag on indefinitely.
• Once the product is validated, learn to discount generic 'change is hard' complaints while still responding to real product issues.

02Key sections

Change is inherently disruptive

Even well-built improvements that users requested will cause friction during adjustment. The real question is how to reduce that disruption and tell adjustment complaints apart from useful product feedback.

The News Feed and Beacon missteps

Facebook's News Feed was a good change that still caused an uproar because it shifted how people interacted and offered little preparation. Beacon repeated a similar mistake, showing the cost of poor change management.

Announcing Timeline early

Facebook publicly previewed Timeline well before it affected users, letting people mentally prepare and start the emotional transition.

Opt-in early adopters and listening

Letting self-selected users opt in gave people a sense of control and produced cleaner product feedback from receptive users, which the team used to improve the product before wider release.

A hard deadline for everyone

Facebook gave itself a fixed date for full rollout, avoiding indefinite limbo, and could then safely set aside general resistance because the product had been vetted.

03From the post

“Does this sound familiar? You spend weeks researching a problem. Your team whiteboards multiple solutions. You user test each one. You build the best one. And despite great feedback from your users along the way, when you finally release, all you get are complaints. Change Is Hard The reality is,”

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.