Jun 16, 2024 · 1h 54m · lennys-podcast
Hard-won lessons building 0 to 1 inside Atlassian | Tanguy Crusson (Head of Jira Product Discovery)
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this in-depth interview, Lenny Rachitsky and Tanguy Crusson, Head of Jira Product Discovery, unpack the practical frameworks, structural traps, and operational tactics for building successful zero-to-one products inside large tech corporations.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Lenny holds 20.5% of the talking time here. How this is scored →
Lenny as informed peer 4.2 Guest teaching 5.7 Guest disagreement 1.8 Lenny pushing back 0.8
speaking balance: gold is Lenny, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 13:38 Tanguy refutes the 'Slack killer' framing
When Lenny frames HipChat as Atlassian's attempt to build a Slack killer, Tanguy forcefully cuts in and corrects him, emphasizing that HipChat dominated the market long before Slack existed.
Hardest push from Lenny ▶ 47:22 Lenny challenges Tanguy on rewrite contradictionsLenny directly confronts Tanguy with the apparent contradiction between his strict 'never rewrite' rule from HipChat and his recommendation to rebuild acquired startup tech stacks on the core platform.
Biggest teaching moment ▶ 24:23 Tanguy breaks down why Slack actually defeated HipChatTanguy thoroughly reframes Lenny's assumption about enterprise sales dynamics by proving both tools used bottom-up adoption, but Slack captured non-technical business employees while HipChat was trapped in developer silos.
Lenny holds their own ▶ 37:31 Lenny demonstrates his domain expertise in status pagesLenny establishes deep subject-matter credibility by recounting his early career creating the Transparent Uptime monitoring blog and interacting with early status page founders a decade prior.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Lenny as informed peer | Guest teaching | Guest disagreement | Lenny pushing back | Why |
|---|---|---|---|---|---|---|
| Tanguy Crusson's Track Record: 10 Years of Bootstrapping at Atlassian | 4 | 4 | 1 | 0 | Lenny opens the episode and frames the discussion around the rarity of honest retrospectives on internal 0 to 1 building. Tanguy gives a transparent overview of his 50/50 track record at Atlassian across 10 years. | |
| The Paradox of Scale: Distribution Power vs. Success Criteria | 5 | 6 | 2 | 2 | Lenny wonders why internal products fail despite massive advantages like 300,000 customers and deep resources. Tanguy explains how these exact scale advantages create mismatched success bars (like $100M thresholds) and dangerous premature scaling. | |
| The HipChat Story: From Market Leader to Full Rewrite and Sale | 4 | 6 | 4 | 2 | When Lenny describes HipChat as an attempt to become the 'Slack killer', Tanguy immediately corrects him, noting HipChat existed long before Slack. He then details how attempting a full rewrite under competitive pressure doomed Stride. | |
| Navigating Failure: The Seven Stages of Grief After HipChat | 3 | 5 | 1 | 0 | Tanguy reflects on the emotional toll of shutting down HipChat and seeing the stock price jump $10 the next day. Lenny listens empathetically as Tanguy describes guiding his team through the stages of grief. | |
| HipChat Lessons: 'Don't Eat Your Own Bullshit' and User Differences | 5 | 7 | 3 | 2 | Tanguy details the core lesson of not eating your own dog food unquestioningly. When Lenny suggests Atlassian failed by selling to enterprise IT buyers, Tanguy corrects him by noting both tools had bottom-up adoption, but Slack won business users while HipChat only captured tech users. | |
| Validating Demand Early: Pre-Code Testing Strategies | 4 | 5 | 1 | 0 | Tanguy illustrates how to validate demand before writing code, giving the example of running a simple waitlist landing page inside a Jira newsletter that gathered 3,000 signups in two weeks. | |
| The Platformization Trap vs. Moving Fast like a Starving Startup | 4 | 6 | 2 | 1 | Tanguy outlines the trap of trying to solve a new product problem while simultaneously building platform components and microservices, arguing startups thrive precisely because they are forced to starve and hack solutions first. | |
| Exploring IT Operations and the Statuspage Acquisition | 6 | 4 | 1 | 0 | Tanguy explains how exploring IT operations led to the Statuspage acquisition. Lenny jumps in to share his personal history founding the Transparent Uptime blog a decade earlier, connecting deeply with the problem space. | |
| Post-Acquisition Friction: Culture Shock, Silos, and Corporate Rituals | 4 | 6 | 2 | 1 | Tanguy breaks down the operational shock that acquired startups face when subsumed by corporate craft silos, OKRs, and allocation rules. Lenny highlights the paradox between leadership telling founders to keep doing what they do while functional heads impose heavy process. | |
| Acquisition Strategy: Avoiding the Frankenstack via Acqui-Hires | 5 | 6 | 3 | 4 | Tanguy advocates treating small acquisitions as acqui-hires to rebuild on the core platform rather than maintaining a 'Frankenstack'. Lenny pushes back on how to reconcile this with the earlier warning against rewrites, prompting Tanguy to distinguish mid-flight rewrites from early-stage platform rebuilds. | |
| Building Urgency: Finding the 'Why Now?' in Business Cases | 6 | 5 | 1 | 1 | Tanguy shares his frustration when his IT ops business case stalled in corporate limbo because he failed to articulate the 'Why Now?'. Lenny connects this to Mahika's advice from Figma on keeping the flame alive and identifying perishable opportunities. | |
| Sponsor Message: Coda | 5 | 2 | 0 | 0 | Lenny summarizes the first half's key strategic lessons before transitioning into a detailed discussion on Jira Product Discovery. | |
| The Genesis of Point A and Jira Product Discovery | 4 | 6 | 1 | 0 | Tanguy explains how Atlassian launched Point A to rebuild its internal innovation muscle, giving teams psychological safety by borrowing staff who could return to previous roles if bets failed. | |
| Framing Failure and Enforcing Scarcity for Internal Autonomy | 4 | 7 | 3 | 2 | Tanguy explains his counterintuitive strategy of aggressively telling everyone in the company that their project has a 70% chance of failing within six months, using that framing as a shield to keep well-meaning corporate teams and heavy architectural reviews away. | |
| The Point A Framework: Wonder, Explore, Make, Impact | 4 | 6 | 1 | 1 | Tanguy details the four gates of Point A: Wonder, Explore, Make, and Impact. He explains how 6-pager reviews with Atlassian's founders acted as strict stage gates for funding and head count. | |
| Breaking Rules Without Breaking Trust: The Dual PM-Eng Leader | 4 | 7 | 3 | 1 | Tanguy details spending all his accumulated social capital to break engineering rules, including refusing an engineering manager and leading both PM and Eng himself to hire senior contractors and bypass corporate mandates. | |
| The European Advantage: Escaping Corporate Process via Geography | 4 | 6 | 2 | 1 | Tanguy explains how running the team out of France created a geographic shield against Sydney HQ's rituals, as corporate teams refused to wake up early or stay up late to block them. | |
| The Safety Funnel: Protecting Brand Equity and User Experience | 4 | 7 | 2 | 1 | Tanguy explains adopting Reforge's 'Safety Funnel' and establishing the Lighthouse Users program (scaling strictly from 10 to 100 to 1,000 customers) to avoid exposing unpolished software to Atlassian's broader customer base. | |
| Connecting Teams Directly to Users: Transforming Engineers into Product Engineers | 4 | 6 | 2 | 0 | Tanguy critiques teams that 'hide behind research' and CSAT surveys. He describes putting engineers directly in front of the 10 Lighthouse customers on Zoom and Slack to transform them into true product engineers. | |
| Protecting the Ugly Baby: High-Velocity Internal Comms | 4 | 6 | 2 | 0 | Lenny asks how to protect early, vulnerable ideas (the 'ugly baby' phase). Tanguy explains how weekly bite-sized video snippets of real users and constant progress demos created unstoppable internal momentum. | |
| From Alpha to GA: Progress Tracking and Founder Polish Standards | 4 | 5 | 1 | 0 | Tanguy recounts co-founder Mike Cannon-Brookes stopping their GA launch because the UI was too ugly for Atlassian standards, requiring a 3-month polish sprint to meet brand expectations. | |
| Individual Agency vs Organizational Reality: Choosing the Right Environment | 4 | 6 | 2 | 1 | Lenny asks whether individual ICs can truly drive change in rigid corporate cultures. Tanguy candidly warns listeners not to become cynical fighting insurmountable bureaucracy and to leave toxic environments if necessary. | |
| Lightning Round: Cutting Through Interview Scripts | 3 | 6 | 1 | 0 | In the lightning round, Tanguy recommends unique books and reveals his favorite interview question: asking candidates what their previous manager will say when called directly. | |
| World-Class Freediving: Diving 300 Feet on a Single Breath | 3 | 6 | 1 | 0 | Tanguy describes diving 300 feet (92 meters) on a single breath as a top-ranked freediver. Lenny looks up comparisons on Perplexity to conceptualize the depth as the length of a full football field. |
Statements from this episode (37)
Crusson: Atlassian aimed to win enterprise communications before Slack and Teams
“I worked on HipChat and Stride. HipChat was one known, Stride less so we were trying to win the enterprise communications market before Slack and Microsoft Teams came about.”
Crusson: Jira Product Discovery spent 2-3 years in incubator before GA
“And more recently, I started GR Product Discovery, which was part of our internal incubator for two to three years. And came out of the incubator and generally available a year ago.”
Crusson: At Atlassian, a $100M business is merely a good start
“A one hundred million dollar business is a good start, basically. In most companies out there, like a hundred million dollar business is a home run. For us, it's not like that. It's, we're trying to build businesses that, that grow really big and keep growing …”
Crusson: Internal corporate startups should deliberately keep initial MAU low
“What if you're building an quote unquote internal startup, your monthly active user number should look very low for quite some time up until you know that your product is ready to serve the vast majority of the customers that you want to put it in front of so …”
Crusson: Software teams should never do a full product rewrite
“There's lots of literature around there on should you do rewrites, should you not do rewrites? You ask me now, I tell you never.”
Crusson: Slack was pretty much destroyed by Microsoft Teams
“At that point, Microsoft launched Teams, and I don't know if you remember this moment where Slack put an ad in the, I think it was the New York Times, copying the Apple versus Microsoft thing from ages before, going, you know, welcome to the game, welcome to t…”
Atlassian's stock jumped from $60 to $70 after shutting down HipChat
“Yeah, it was actually, it was noticed by the market in that as soon as we did that, our stock price went up, which was, and I think it was 60 dollars back then, and it went up to 70.”
Crusson: Atlassian bet HipChat could expand from tech teams into business
“Atlassian was successful with a playbook, and the playbook was, we've got people in, like developers or tech or IT, they choose Atlassian apps, they love them, they start to recommend them to people in the business, and we start to see adoption, like bottom-up…”
Crusson: Atlassian targeted tech teams while Slack targeted business teams bottom-up
“Atlassian was going after the users in tech teams. Slack was going after the users in business teams. And in both cases, what happened was a bottom up adoption.”
Crusson: Companies must validate why they succeeded before reusing playbooks
“The other one is what took you here is not going to take you there. And so go back and try to explain why you are successful today. And then if you try, if you think you can use the same thing on the next thing, find ways to validate it, find ways to test it. …”
Crusson: Competitor feature launches reflect research from a year earlier
“Your competitor, like if you think of what they do as an iceberg, like the top side, what comes out of the water is what they've shipped in terms of features, but it's based on all this stuff that they've built in terms of research. An understanding of their c…”
Crusson: Disconnect creative and research processes from competitor tracking
“Now I, whenever I work at, I tend to try and ignore competition other than watching key, like every three months or so seeing what came out, if there's anything we should be worried about, afraid of stuff like that. But Really just try to disconnect all the cr…”
Crusson: 70% of HipChat's code remains in Atlassian's platform today
“So, I would say that in terms of code, purely in terms of code, 70% of what we wrote for HipChat is, is, is probably still in the Atlassian platform today.”
Crusson: Large companies can sustain opportunities longer than individuals can
“That's more like a story of big companies can play the long run, and for you individually, inside that process, it might look like a loss, and you might feel like you're going around, going nowhere, Yet the company stays on the opportunity for long enough to m…”
Crusson: M&A integrations are mostly about people, not technology or vision
“Integrations are mostly about people. They're not about technology as much or product vision or, like, all of that stuff is the easy stuff. The hard part is the people.”
Crusson: Acquired startups face a major operational slowdown before re-accelerating
“Don't expect your business to join and keep running at exactly the same pace, because there's going to be a big slowdown before it accelerates again.”
Crusson: Accelerating Market Entry by One Year Pays for Startup Acqui-Hires
“If we can like enter a market one year earlier, it's probably going to pay the acquisition back on its own.”
Crusson: Rebuilding a High-Traction Product Differs from Tuck-In Rebuilds
“In one case, what you try to do is, so when you rebuild, you've got a successful business. You've got hundreds of thousands of customers, for example, and you're trying to rebuild the same thing or a different thing, but for the same customers that have got ex…”
Crusson: Business cases must articulate an urgent 'why now' trigger
“We need a very strong trigger for why now to go after it. And I did not do a good enough job at articulating this. Why now? Why, why do we have to do this now versus in a year's time, in two years time? And the next team that came in afterwards did a much bett…”
Crusson: Atlassian's Point A incubator selected only three products from 100 pitches
“There were a hundred pitches, and out of it came out three products that basically went through all the different stages of it.”
Crusson: Jira Product Discovery hit 8,000 customers within one year
“So anyway, so we launched a year ago, fast forward to today, we've got 8000 customers, amazing CSAT, great traction, it's one of the fastest growing products in Atlassian history, which is great.”
Crusson: Accepting help from internal teams inevitably slows down new products
“The help always comes with condition, and the condition is usually things slow down.”
Crusson: Corporate intrapreneurs must manufacture artificial scarcity to emulate startup urgency
“The thing that we're trying to do when starting new products is to basically emulate a startup in an environment that is not hungry. Like, it's not starving, and so you need to create scarcity.”
Crusson: Point A stage gates require a 6-pager reviewed with Atlassian's founders
“So we basically write a six pager. That looks at all the different aspects of all the questions that we're going to answer. And then we are in a meeting with the point A stakeholders and the founders of Atlassian. And everyone reads that page for about 15 minu…”
Crusson: Internal 0-to-1 teams must break scale rules without breaking trust
“If you're starting something like this, your teams will need to break a lot of rules. That are established, but they need to be able to do that without breaking the trust of everyone in the organization. The rules were created to support the business at the st…”
Crusson: Served as both PM and engineering lead for Jira Product Discovery
“So I decided not to have an engineering leader in the team and to do it myself. So I was the product leader and the engineering leader.”
Time zone distance shielded early Jira Product Discovery from corporate meddling
“And so there was a lot of the early Success that we had in being able to move super fast that came from being so far that people just did not engage to stop us. And that's why we were initially the group with the fastest speed.”
Crusson: First 10 product users must be proven proxies for target market
“Where we spend most of the time for the Lighthouse, the first 10 Lighthouse users, is to explain why they are the Lighthouse users. Everything that explains why we believe they are a proxy for every customer that we serve afterwards.”
Crusson: Phased user tiers protected Jira Product Discovery from premature MAU targets
“That helped us because we could then claim the space to do the right thing, and we were not asked to hit, for example, a monthly active users number, or number of customers number, or percentage of users who use this number, because it's very qualitative still…”
Crusson: Growing product teams often hide behind formal research and surveys
“As the products grow, you tend to leverage a lot more user research, formal user research, or CSAT surveys, and the way I call it, it's hiding behind research. And not being close enough to the ground with customers.”
Crusson: Any engineer knowing ten customers by name becomes a product engineer
“In my opinion, everyone can be a product engineer. They just need to be exposed to the right user context, and the right user context, what is it? It's 10 customers. You know by name. You know their context. You know their problems.”
Crusson: Teams prefer 3-minute customer video snippets over 30-minute research reports
“No one is going to read a research report that takes 30 minutes to read. Everyone is happy to watch a three-minute snippet with four customers talking about something.”
Crusson: Relentless weekly momentum protects early corporate projects from executive interference
“Those kinds of things are what give people a sense of velocity and speed. And no one wants to fuck with a high speed train. You don't get in front of it. That doesn't help, and you're going to look bad by doing that.”
Crusson: Early 0-to-1 evaluation focuses on team rigor, not business outcomes
“And I think initially they judged not the outcome. They judged the team a lot more than the outcome. So there's all this talk of a founder market fit. And I think really that's what you need to be teasing out, which is, is it the right team going after the rig…”
Cannon-Brookes delayed Jira Product Discovery's launch over ugly design standards
“And one of the founders, Mike, went, no, you're not. That thing is ugly. I do not want to look at it. It needs to, you know, level up with the rest of the Atlassian design standards. Our customers have expectations from us on that front, like your stuff is fun…”
Crusson: Remaining the only sane person in a room will make you insane
“You cannot be the only sane person in a room. At some point, you will go insane. The environment will permeate on you. You are not this entity that is absolutely permeable to everything that happens around you. Like everything around you will affect you and wi…”
Crusson: Asking candidates what their boss will say breaks scripted interview answers
“When people describe an experience, you ask them the name of the person that they worked with back then, and you ask them, so when I call this person after our call, what do you think they're going to say about that? And apparently this does something, and I'v…”