Two-Week Crisis Operating Cycle
Shorten the horizon, unify the company, and reset priorities every two weeks.
- Difficulty
- Advanced
- Time to result
- ~days to results
- Steps
- 6
- Confidence
- 96%
Airbnb's crisis response replaced quarterly planning with a two-week operating cycle when COVID-19 made long-range forecasts unreliable. Leadership brought top-down survival constraints while product managers, engineers, designers, and customer-experience teams supplied frontline evidence. Every cycle selected the most urgent work for Airbnb as a whole, not for a particular function. Team boundaries were dissolved so people could move to pricing, customer tools, or any other survival priority. Leaders paired the short execution horizon with candid communication: they did not pretend to know what six months would look like, but repeated the durable beliefs that travel would return and Airbnb could serve it. The cycle creates speed through shared priorities, flexible staffing, and frequent re-evaluation rather than through a more detailed forecast.
Origin
During Airbnb's COVID-19 collapse, president Greg Greeley said the company could not plan for a year or quarter and would instead plan and react every two weeks. Saxena's organization used that cadence during the turnaround.
Core principles
- 01Planning horizons must contract when reality changes faster than the plan.
- 02The company's most urgent need outranks every team's local roadmap.
- 03Frontline evidence and top-down direction are both required.
- 04Honest uncertainty builds more trust than invented long-range certainty.
- 05Rapid recovery matters more than preserving the original plan.
How to run it
- 1
Contract the planning horizon
Replace the normal quarterly or annual cadence with a two-week window. Commit only to the period in which current evidence remains useful.
Pro tip Choose a cadence short enough to react but long enough to ship a meaningful unit of work.
Watch out Do not dress a long-term forecast as certainty when conditions invalidate it daily.
- 2
Combine direction with field evidence
Bring leadership's survival constraints together with signals from customer support and frontline product teams. Use both to form a current view of the crisis.
Watch out Purely top-down planning misses customer changes; purely bottom-up planning misses company-level constraints.
- 3
Rank company priorities
Select the few outcomes most urgent for the whole company in the next cycle. Suspend team roadmaps that do not serve them.
Pro tip Ask, 'What is most urgent for the company, not my team?'
Watch out Allowing every team to preserve its old priorities defeats the purpose of the cycle.
- 4
Operate as one team
Move engineers, product managers, and other specialists wherever the current priorities require them. Treat former organizational boundaries as secondary to survival work.
Pro tip Make temporary ownership explicit so speed does not create ambiguity about decisions.
- 5
Communicate uncertainty and belief
Tell employees plainly what leadership does not know. Pair that vulnerability with the first-principles beliefs that justify the work and provide a credible direction.
Pro tip Use customer evidence and concrete stories to make the enduring belief tangible.
Watch out Manufactured certainty will be recognized as marketing and reduce trust.
- 6
Ship and reset
Complete the urgent work, examine the new operating data, and select the next two-week priorities. Lengthen the horizon only when the environment regains stability.
In the wild
As travel collapsed during COVID-19, Airbnb stopped treating CX, Plus, Lux, pricing, and marketplace work as separate team domains. Engineers and PMs moved to whichever work mattered most, including customer-experience tools and marketplace pricing. Leadership reset the priorities roughly every two weeks as country closures and demand changed.
→ Saxena says the roughly 4,000-person company operated with the unity of a four- or forty-person team while it found enough stability to plan again.
Common mistakes
Preserving normal team roadmaps
Local optimization fragments the response. The cycle works only when the company's urgent priorities override subteam ownership.
Inventing a six-month answer
Employees can see through unsupported certainty. State what is unknown and anchor the team in beliefs the evidence still supports.
Using a short cycle without recovery
More planning meetings do not create adaptability. Each cycle must actually redirect resources and ship against current priorities.
Is it for you?
Best for
Leadership teams navigating a severe demand shock, operational crisis, or rapidly changing external environment.
Not ideal for
Stable periods where constant reprioritization would create more churn than useful adaptation.
From the episode
Sanchan Saxena (VP of Product at Coinbase) on the inside story of how Airbnb made it through Covid; what he’s learned from Brian Chesky, Brian Armstrong, and Kevin Systrom; much more