Stacking the Bricks
Concentrate every launch function into one coordinated release moment
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 99%
Stacking the Bricks is Airbnb's method for concentrating product and go-to-market activity around a single release moment. Each brick represents a necessary layer: the product itself, creative work, host or partner communications, brand marketing, performance marketing, public relations, and other customer-facing support. The team maps these layers onto one calendar and prepares important audiences before the public release. This produces more than administrative neatness; simultaneous reinforcement makes the launch easier to understand, more memorable, and more newsworthy. The method depends on upstream cross-functional coordination because every brick has its own production lead time and dependencies. Success is judged by whether customers encounter a coherent event rather than a series of unrelated announcements.
Origin
Extracted from Marketing Against The Grain, where Hiroki Asai named Airbnb's synchronized release method while describing the Co-host Network launch.
Core principles
- 01A launch gains impact when every supporting function lands together
- 02Conceptual alignment must be translated into calendar alignment
- 03Audience preparation is part of the release, not an afterthought
- 04The release moment should connect software, communications, press, and marketing
How to run it
- 1
Define the release moment
Select the date and customer outcome around which every launch activity will align. Describe what must become true for the audience on that day.
Pro tip Frame the moment as a customer event, not merely an internal ship date.
Watch out A date chosen without dependency analysis can force incomplete work into public view.
- 2
Inventory the bricks
List the product, creative, communications, partner enablement, brand, performance, press, and operational components required for the release.
Pro tip Include pre-launch preparation and post-launch support, not only public assets.
Watch out An omitted stakeholder communication can weaken the entire launch.
- 3
Sequence dependencies
Work backward from the release moment to identify approvals, production, briefings, and technical readiness. Assign an accountable owner to every brick.
Pro tip Mark which bricks can proceed in parallel and which block others.
Watch out Do not mistake a shared deadline for a workable sequence.
- 4
Pre-brief key participants
Prepare hosts, partners, support teams, or other affected groups before the public announcement. Give them enough context to reinforce the release coherently.
Pro tip Use pre-briefing to expose unclear messaging or operational gaps.
Watch out Premature disclosure requires appropriate confidentiality controls.
- 5
Land the stack
Release the product and activate communications, marketing, and press around the same moment. Monitor whether every layer is live and telling the same story.
Pro tip Run a launch-room checklist with real-time owners for each brick.
Watch out Do not declare success merely because the software deployed.
In the wild
Airbnb completed the product, host communications, host pre-briefing, broader host outreach, marketing, and press around the same release day.
→ The combined activity created greater impact than isolated product and campaign launches would have produced.
Common mistakes
Shipping isolated bricks
A product may go live before communications or marketing are ready, forcing customers to interpret an incomplete story. Treat every supporting layer as part of the release.
Using multiple source calendars
Separate functional calendars hide dependencies and timing conflicts. Maintain one authoritative launch calendar.
Ignoring participant readiness
Hosts, partners, or support teams can be surprised by the public launch. Pre-brief people whose actions affect the customer experience.
Is it for you?
Best for
It is best for product launches that require coordinated software, stakeholder communication, publicity, and marketing.
Not ideal for
It is not ideal for low-stakes experiments that benefit more from continuous deployment than a concentrated launch moment.
From the transcript
“we call it stacking the bricks from the product to the creative to the marketing to the performance marketing, the brand marketing, all of that…”
“by aligning all these functions and activities together on the same calendar on the same day, you really get a lot of impact.”
From the episode
The $86B Marketing Playbook Behind Airbnb w/ Global CMO Hiroki Asai
Hiroki Asai