How Sheryl Sandberg scaled Google and Facebook by breaking plans

Executive overview

Fast-growing organizations outpace every plan made for them. Leaders who cling to commitments — around hiring, processes, or structure — become the bottleneck.

Sheryl Sandberg's career at Google and Facebook shows that the core leadership skill at scale is not making good plans, but knowing when to break them. The leader's job is to build systems that surface problems early, hire for uncertainty, and keep mission constant while everything else changes.

• Build feedback cultures where people feel safe telling the leader they're wrong.
• Hire for who you need now and who you'll need in 18 months — these are rarely the same person.
• Move fast on strategy (OODA loops), but repeat mission relentlessly.

Instructions spread unpredictably in large organizations

• Sheryl banned PowerPoint in her own meetings; it was interpreted company-wide as a ban on client presentations.
• She publicly reversed the decision and used it to reinforce that people must speak up when she's wrong.
• Scale amplifies every leadership signal — precision and psychological safety are both required.

Every plan at Google broke within weeks

• Her team started at 4 people; she promised everyone would interview every new hire. Two weeks later the team was 12 and the promise was unsustainable.
• Birthday celebrations shifted from individual days to weekly to quarterly sheet cakes — small ritual changes matter to early employees.
• Key distinction: anticipate which systems will break and redesign them before they fail, rather than reacting each time.

Creating psychological safety to surface problems

• When Sheryl stopped interviewing all candidates, her team applauded — they had known she was a bottleneck but never said so.
• Leaders must make it explicitly safe to deliver bad news upward.
• Openness to being wrong is not natural in hierarchies; it has to be modeled and rewarded by the leader.

Hiring for roles that have never existed before

• Meg Whitman told Sheryl: "No one has experience for this because no one's done it before." She applied this to every hire at Google.
• Bill Gates's regret: he underestimated how specialized expertise needs to become as an organization grows, assuming smart generalists could learn anything.
• Early startup stage needs generalists who get hands dirty; later stages need specialist managers who delegate.
• Mark Zuckerberg's rule: never hire someone you wouldn't work for in an alternate universe.
• Temp-to-hire was Sheryl's hack for hiring quickly at Google — evaluate in 60 days, convert the best performers to full-time.

Giving people a story of contribution as roles evolve

• The first product manager rarely becomes head of product in a 10,000-person company — leaders must help employees reframe their arc.
• Offer multiple frames for contribution: individual impact, career progression, depth of craft.
• People who can't grow into management are often strongest as individual contributors — distinguish the two early.

How Sheryl and Mark Zuckerberg built their working relationship

• Months of late-night dinners before Sheryl joined Facebook — process agreement, not solution agreement.
• Advice from Sheryl's husband Dave: don't resolve substantive disagreements in advance; agree on how you'll work them out together.
• Weekly structure: first meeting Monday, last meeting Friday, mutual feedback every week without exception.
• Disagreements are a constant — the commitment is to how you resolve them, not to any particular outcome.

Building organizational resilience through feedback culture

• Resilient organizations debrief failures openly; non-resilient ones hide them.
• Margaret Heffernan: constructive conflict is how organizations think — leaders must create safety for disagreement.
• After a vote, everyone gets behind the decision regardless of which side they were on (Ocean Spray example: 49.9% vs 50.1% vote, company unified after).
• Invite discord during debate; ensure alignment on execution.

Cognitive and personality diversity as a strategic asset

• Sheryl values temperamental opposites on the team: David Fisher's calm offsets her urgency; Mark's personality differs across gender, age, and working style.
• Diversity of thought — not just demographic — widens the range of inputs before a decision is made.
• Surround yourself with people who are better than you at specific things; don't be threatened by it.

The mobile OODA loop

• In 2012, Facebook users were migrating to mobile faster than the company's projections. Desktop-trained engineers kept submitting desktop screenshots the day after the "mobile first" all-hands.
• Mark's fix: ban desktop screenshots in meetings entirely. The rule forced the behavioral change.
• Hard strategic choice: freeze new features for two years to fully rewrite for mobile. No half-measures.
• Mark's controlling interest gave the leadership team room to sacrifice near-term revenue for long-term platform survival.

Mission as the one constant

• Everything at scale is subject to change except the mission. LinkedIn: connecting people with opportunity. Airbnb: belong anywhere. Facebook: connect the world.
• Repeat mission at the start of every meeting, even when it feels unnecessary — it orients thousands of people.
• Mission statements on walls are not control mechanisms; they are permission to find your own path to the goal.
• Telling people where to go rather than how to march there is what creates real autonomy.