▲Takeaway21:30
Your winning playbook is an unvalidated assumption
Atlassian's bottom-up playbook (devs adopt the tool, then it spreads to the business) was assumed to transfer to team chat. It didn't. Tanguy's lesson: success comes from an 'X,' but X is rarely validated, and teams wrongly assume the same X will keep working. Go back and explain why you actually won, then test whether that reason applies to the next bet.
- Atlassian won by seeding tools with developers/IT who then evangelized to the business
- Slack won the same bottom-up motion but with business users who cared about feel and emojis
- Atlassian underestimated how different a new user segment really is
- Whatever made you successful is an assumption; find ways to validate it before building on it
“the founders keep telling us like what took us here won't take us there”
“it's very easy for teams when they see”
#assumptions#product-market-fit#segments
▲Takeaway43:00
Acquisitions are mostly about people, not technology
From integrating Statuspage, Tanguy learned that buying a company to 'go faster' rarely goes as smoothly as expected. Startups hit culture shock as founders lose day-to-day control, teams get split into functional silos, and new processes feel parasitical. The hardest part is the people, not the tech, and mismatched tech stacks create a 'Franken stack' customers don't want.
- Acquired founders suddenly stop owning decisions they used to make daily
- Big-company planning horizons (multi-year) clash with a startup's 3-month roadmap
- One-team startups get fragmented into product/eng/marketing/design silos
- Treat an acquisition like hiring a team, not just buying a business or product
“Integrations are mostly about people they're not about technology as much”
“we call that the Franken stack otherwise which is you you get one text tack here one text tack there”
#acquisitions#integration#org-design
▲Takeaway50:00
Great work gets parked without a strong 'why now'
Tanguy pitched an IT-operations bet to every level of Atlassian and got encouragement but no decision for months, then gave up, only for the company to enter that market a year later. His lesson: a big company has endless good opportunities sitting on a shelf, so a business case needs a strong, articulated trigger for why it must happen now versus in a year or two.
- Everyone was excited but no one said yes or no for months, leaving him in limbo
- He misread the appetite and sense of urgency around the opportunity
- Atlassian's abundance of opportunities means good ideas can simply be parked
- The rationale for urgency must be built into the business case itself
“we need a very strong trigger for why now now to go after it”
“was that I misread the appetite and sense of urgency around that topic”
#why-now#prioritization#business-case
▲Takeaway1:26:30
Ten customers you know by name beat any research report
Tanguy argues that as products grow, teams start 'hiding behind research' and lose closeness to customers. Instead he puts the whole team, engineers included, in direct contact with about ten named customers over months. Like caring about climate change through one affected person, empathy with specific users drives the team to act, turning engineers into product engineers.
- Formal research and surveys can become a way of hiding from real customers
- The whole team meets the same ~10 customers on Zoom and Slack over months
- Empathy with individuals, not aggregate data, is what makes people want to change the product
- Any engineer can become a product engineer given the right user context
“what is it it's 10 customers you know by name you know their context you know their problems”
“if I know someone that's impacted by climate change it's going to make me relate a lot more strongly to the concept of climate change”
#customer-research#empathy#product-teams
▲Takeaway1:30:30
Build a high-speed train no one wants to get in front of
To protect an early 'ugly baby' product, Tanguy treats internal communication as everything. He posted weekly, bite-sized updates and demos, once even saving features to have something to show during a vacation week, to project constant momentum. Paired with honest data and personal customer stories, this sense of velocity discourages others from trying to stop or slow the bet.
- Internal comms is the main job when protecting an early, unproven product
- Weekly tweet-sized updates and demos on Atlassian's Atlas tool drew hundreds of subscribers
- Three-minute customer snippets beat 30-minute research reports for internal buy-in
- A visible high-speed train discourages people from getting in its way
“be very clear about what we're testing where we're in testing it doing that with data doing that with personal customer stories”
“keeps moving it keeps moving you don't want to get in front of it”
#internal-comms#momentum#stakeholders