Manufactured Chaos: The Artificial Time Constraint
When things feel too calm, inject an absurd deadline to force intuition and creative leaps
- Difficulty
- Advanced
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 90%
A deliberate leadership move: when an organisation is shipping smoothly and the numbers look fine, that calm is itself a warning sign. Pick an important project, collapse its carefully-sequenced timeline into an absurd constraint (Airbnb's canonical case: design it in 24 hours), and let the resulting chaos strip away dependencies and force the team to lead with intuition rather than process.
Origin
Originated with Brian Chesky, Airbnb's CEO, who told Loktev 'things are just too calm, I don't like it' despite up-and-to-the-right metrics, then compressed a host-onboarding design cycle from weeks into 24 hours. Loktev — self-described lover of order and clean processes — adopted it after seeing what it unlocked.
Core principles
- 01Too calm is a signal, not a reward. Calm organisations stop making leaps.
- 02Chaos is scary and unnatural for most operators — including Loktev — which is why it must be deliberately injected.
- 03An artificial time constraint dials up intuition and forces creative thinking.
- 04The constraint collapses organisational dependencies and process noise as a side effect.
- 05It does not always work — sometimes the honest answer is that the problem needs more time.
How to run it
- 1
Read the calm as a warning
Notice when everything is shipping, metrics are up and to the right, and nothing feels off. Ask whether the organisation is still making leaps in product development or merely executing.
- 2
Pick one important project with a neat timeline
Choose a project that genuinely matters and that currently has a perfectly crafted, rational sequence — four weeks of design, then build, then staged rollout, then learn and iterate.
Pro tip Target the project whose plan is most immaculate; the neatness is what is suppressing intuition.
- 3
Collapse the timeline to an absurd constraint
Discard the plan and impose a radically compressed deadline — Chesky's was 'we're going to design this in 24 hours'. Accept that this sends ripples through everyone who was staffed on the neat flow.
Pro tip Missing the absurd deadline is fine. Airbnb's 24-hour design took a bit longer — but was still designed dramatically faster than planned.
Watch out This is disruptive by design. Expect confusion and pushback from anyone invested in the original process.
- 4
Let the constraint dial up intuition
With no time for the process, the team is forced to go with its gut, throw out crazy ideas, and think more creatively than it would have. Dependencies and coordination noise fall away because there is no room for them.
Pro tip Loktev found these sprints were his most fun and most connective moments with the team — no idea was too crazy.
- 5
Know when to call it off
Sometimes the honest outcome is 'I don't know the answer and I need more time to think about this problem'. Accept that and revert rather than forcing a bad answer to meet the artificial constraint.
Watch out Manufactured chaos is a forcing function for creativity, not a delivery method. Using it as a routine schedule-compression tool will just produce burned-out teams and bad work.
In the wild
Chesky told Loktev things felt off despite good numbers — 'things are just too calm'. He picked host onboarding, which had a carefully-crafted four-week design phase followed by staged build, deploy, and iterate, and said: I don't care about any of that, we're going to design this in 24 hours. Loktev was mind-blown, both by the how and by the ripples it would send through the org.
→ The design got done very quickly (slightly over 24 hours). The artificial constraint dialled up the team's intuition and produced more creative work than the rational timeline would have.
A related move from the same playbook: Chesky routinely responds to a goal by asking what it would take to 10x it. Loktev's read is that the point is not hitting the goal — it is the creative journey of asking what the world would need to look like for that crazy goal to be true, which pushes teams to test extremes.
→ Testing the extremes (everyone in the world does this / nobody does) is where teams realise which path they should actually take.
Common mistakes
Treating chaos as a delivery schedule
The artificial constraint is a creativity forcing function, not a way to actually ship faster. Loktev notes cases where the answer was simply that the problem needed more design time — and the right move was to say so.
Waiting for a crisis to create urgency
The insight is counterintuitive: you inject chaos precisely when nothing is wrong. If you wait until the numbers turn, the chaos is reactive and the creative upside is gone.
Is it for you?
Best for
Founders and senior leaders of organisations that are executing well but have stopped producing product leaps.
Not ideal for
Teams already in crisis, or people who explicitly told you at hiring time that they do not want to work in a constantly-shifting environment.
From the transcript
“sometimes you want to create chaos in an organization to push the organization to think creatively”
“And that chaos forced us with our artificial time constraint to dial up our intuition.”
“Things are just too calm. Sometimes you want to create chaos in an organization to push the organization to think creatively”
From the episode
Airbnb’s Vlad Loktev on embracing chaos, inquiry over advocacy, poking the bear, and “impact, impact, impact” (Partner at Index Ventures, Airbnb GM/VP Product)