Hard-won lessons building 0 to 1 inside Atlassian | Tanguy Crusson (Head of Jira Product Discovery) — Lenny's Podcast: Product | Career | Growth Summary

Hard-won lessons building 0 to 1 inside Atlassian | Tanguy Crusson (Head of Jira Product Discovery) — Lenny's Podcast: Product | Career | Growth Summary | Galaxy of Podcasts

The Conversation Breakdown

Check whether distribution reaches the right users

⏱ Untimed topic

Crusson says a large installed customer base does not automatically mean a new product serves the same people or needs. His HipChat account includes an assumption about expanding from technical to business teams. Test the audience fit rather than treating existing distribution as proof of demand.

Test an assumption before building around it

⏱ Untimed topic

In his Jira Product Discovery account, the team tested interest with a newsletter message and a website before building the product. The point was to learn whether interested users could be reached. Interest is a useful early signal, not proof that a finished product will succeed.

Do not let competitors replace customer research

⏱ Untimed topic

Crusson describes reacting to competitor features as a way the team lost focus on serving some users well. He notes that a shipped feature is only the visible result of another team's research and thinking. Copying that surface does not reproduce the understanding behind it.

Bring customer needs back into the discussion

⏱ Untimed topic

He recommends separating the creative and research process from constant competitor reaction. When an announcement draws attention, the team can return to the problems its own users describe. This is a focus discipline, not a claim that competitors should never be observed.

Solve the problem before building a reusable platform

⏱ Untimed topic

Crusson reflects that trying to rebuild a product and create reusable platform pieces at the same time added complexity. His alternative is to test and iterate with customers, then make successful parts reusable later. The account illustrates a scope trade-off rather than a universal rule against platform work.

Judge a new bet differently from an established product

⏱ Untimed topic

He explains that early-stage work can have small user numbers while the team is still learning what should be built. Applying the same success measures as a mature product can conceal that stage difference. State what the current work is trying to learn before judging it by scale alone.

Communicate learning without inflating progress

⏱ Untimed topic

Crusson describes weekly communication grounded in what the team was testing, data and customer stories. He says to be honest about where the work stands rather than make it appear more successful. A progress report can show motion while preserving the uncertainty that still matters.

Hard-won lessons building 0 to 1 inside Atlassian | Tanguy Crusson (Head of Jira Product Discovery)

Executive Summary (TL;DR)

Key Takeaways

Check whether distribution reaches the right users

Test an assumption before building around it

Do not let competitors replace customer research

Bring customer needs back into the discussion

Solve the problem before building a reusable platform

Judge a new bet differently from an established product

Communicate learning without inflating progress

The Conversation Breakdown

Check whether distribution reaches the right users

Test an assumption before building around it

Do not let competitors replace customer research

Bring customer needs back into the discussion

Solve the problem before building a reusable platform

Judge a new bet differently from an established product

Communicate learning without inflating progress

Core Frameworks & Ideas

Audience-assumption check

Problem before platform

Learning-centered update

Actionable Next Steps

Notable Quotes

The One Thing to Remember