By playing, you agree to uListen's Terms and Privacy Policy and YouTube's Terms of Service.
Lenny's PodcastHard-won lessons building 0 to 1 inside Atlassian | Tanguy Crusson (Head of Jira Product Discovery)
Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.
At a glance
WHAT IT’S REALLY ABOUT
Inside Atlassian’s skunkworks: hard truths of zero‑to‑one innovation
- This episode explores how to successfully build zero‑to‑one products inside a large, established company, through Atlassian’s hits and misses: HipChat/Stride, Statuspage, and Jira Product Discovery.
- Tanguy Crusson shares how overconfidence, rewrites, acquisitions, and platform constraints derailed earlier bets, and how Atlassian’s internal incubator, Point A, changed their approach.
- He details concrete tactics: creating artificial scarcity, isolating small pirate teams, using lighthouse customers, redefining success metrics, and running a staged incubator process (wonder → explore → make → impact).
- A recurring theme is balancing rule‑breaking with organizational trust, while protecting fragile early ideas from the core business and from premature scale expectations.
IDEAS WORTH REMEMBERING
5 ideasAssume most new bets will fail—and say that out loud.
By explicitly framing new products as likely failures, you reduce over‑investment, keep other teams from piling on premature dependencies, and buy the freedom to hack, move fast, and experiment without dragging the whole org into your bet.
Create artificial scarcity and autonomy to mimic a startup.
Big companies are not starving, so you must simulate scarcity: very small teams, limited scope, minimal platform dependencies, and physical/organizational distance (e.g., a ‘pirate’ team in another region) to avoid being consumed by legacy processes.
Don’t blindly reuse the playbook that made you successful.
HipChat assumed Atlassian’s bottom‑up dev adoption model would translate to broader communications; Slack instead targeted business users. Always re‑validate your distribution and adoption assumptions before porting them to a new segment or market.
Avoid competitive myopia; build for your users, not your rival’s roadmap.
Chasing a competitor’s feature set means copying the visible ‘tip of the iceberg’ without the underlying research and strategy. Periodically scan competitors, but anchor product decisions in your own user interviews, problems, and segments.
Use phased incubator stages with explicit gates and different success metrics.
Point A’s stages (wonder → explore → make → impact) separate problem validation, solution validation, build, and scaling. Each gate is decided by a six‑pager review with founders, with expectations set around learning and qualitative signals—not MAUs.
WORDS WORTH SAVING
5 quotesStartups have the benefit of starving. And so you need to create scarcity.
— Tanguy Crusson
What took us here won’t take us there.
— Tanguy Crusson (referencing Atlassian founders’ mantra)
Don’t eat your own bullshit.
— Tanguy Crusson
We needed the rest of the company to go away so we could get the autonomy to test the things that we needed.
— Tanguy Crusson
No one wants to fuck with a high‑speed train.
— Tanguy Crusson
High quality AI-generated summary created from speaker-labeled transcript.
