Feb 4, 2024 · 1h 21m · lennys-podcast
Lessons from Atlassian | Megan Cook (Head of Product, Jira)
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 interview, Atlassian's Head of Product for Jira, Megan Cook, shares actionable frameworks for scaling multi-product portfolios, fostering psychological safety, and proactively navigating team conflict. She outlines tactical methods for managing remote product teams, securing executive buy-in, and turning career missteps into expansive, long-term product vision.
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 25.6% of the talking time here. How this is scored →
Lenny as informed peer 4.3 Guest teaching 5.8 Guest disagreement 1.3 Lenny pushing back 1.7
speaking balance: gold is Lenny, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 6:05 Reframing work versus fear
Megan challenges the conventional wisdom that work and play are natural opposites, arguing forcefully that the true antithesis of play is fear and anxiety.
Hardest push from Lenny ▶ 58:00 Confronting the 'Jira Sucks' reputationLenny directly confronts the guest with common industry criticism that Jira is clunky and resented by users, demanding an explanation beyond generic customer-listening platitudes.
Biggest teaching moment ▶ 51:15 Stage-gate product incubation frameworkMegan walks Lenny through Atlassian's precise 5-stage innovation framework (Wonder, Explore, Make, Impact, Scale) for sheltering new bets from enterprise overhead.
Lenny holds their own ▶ 38:48 Lenny cites data on CSAT superiority over NPSLenny demonstrates deep metric domain expertise, referencing external research and previous interview findings to validate why CSAT outperforms standard NPS surveys.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Lenny as informed peer | Guest teaching | Guest disagreement | Lenny pushing back | Why |
|---|---|---|---|---|---|---|
| Fostering Psychological Safety, Play, and Early Peer Feedback | 4 | 5 | 1 | 1 | Lenny prompts Megan on building psychological safety and play into product teams. Megan details Ben Crowe's philosophy that the opposite of play is fear, leading to peer feedback groups, while Lenny connects the idea to an informal personal board of directors. | |
| Team Gatherings, Craft Workshops, and the Ten-Dollar Priority Game | 3 | 5 | 1 | 1 | Megan outlines Atlassian's biannual craft workshops and the ten-dollar priority game for personal time management. Lenny clarifies logistics and highlights the secondary benefits of PMs teaching their peers. | |
| Mastering Remote Work: Team Anywhere, Intentional Connection, and Async Tools | 4 | 6 | 1 | 2 | Megan shares lessons from Atlassian's Team Anywhere remote policy, including intentional in-person bursts and async updates. Lenny challenges on how remote productivity improvements were specifically measured and shares his own calendar-blocking techniques. | |
| Tactical Strategies for Securing Stakeholder and Executive Buy-In | 5 | 6 | 2 | 3 | Megan advises treating buy-in as a collaborative discovery journey rather than a single high-stakes pitch. Lenny pushes back on the common delusion that PMs believe they are open-minded when they are actually rigid, prompting Megan to explain hypothesis-driven framing. | |
| Sponsor Break: Streamlining Compliance and Security Audits with Vanta | 5 | 6 | 1 | 1 | Following the sponsor break, Megan explains how she drove an unglamorous usability initiative using CSAT and platform shepherds. Lenny demonstrates subject expertise by comparing CSAT's predictive power against flawed NPS metrics based on recent research. | |
| Scaling Multiple Product Lines: Atlassian's Stage-Gate Innovation Framework | 5 | 7 | 1 | 1 | Megan details Atlassian's stage-gate innovation model (Wonder, Explore, Make, Impact, Scale) used to incubate Jira Product Discovery without enterprise bloat. Lenny meticulously synthesizes the criteria for each stage gate. | |
| Maintaining Market Leadership, Culture of Paranoia, and Open Innovation | 5 | 6 | 2 | 3 | Lenny challenges Megan by pointing out the constant market narrative that Jira is disliked and under siege by nimble startups, pressing her on what actually maintains their dominance. Megan attributes their defense to baked-in paranoia and continuous hackathon incubation. | |
| Failure Corner: Learning to Expand Scope and Think Ten Times Bigger | 4 | 6 | 1 | 1 | Megan shares her career failure of building an automation feature narrowly for Jira developer workflows instead of architecting a cross-product engine, which Atlassian later had to acquire. Lenny distills the principle of stress-testing ideas at 10x scale during early scoping. | |
| Embracing Direct Disagreement with the 'Fight Club' Meeting Cadence | 4 | 5 | 2 | 2 | Megan introduces the triad Fight Club cadence for proactive conflict resolution, then moves into the lightning round covering books, Foundation (where Lenny asserts the superiority of the books over the TV adaptation), hiring tests, and surfing. |
Statements from this episode (12)
Cook: Jira product managers use biweekly peer groups to review rough drafts
“So we divided the team into these smaller groups, the peer feedback groups. And the idea is that they meet every two weeks or so. Somebody brings something that's in a pretty rough draft that they want to get reviewed, and then everyone's expected to get feedb…”
Cook: Team hesitation and silence emerge when work streams hit 15 people
“So I think that was probably around, even, even around 15, we started to see a little bit of that.”
Atlassian research shows intentional in-person meetups boost remote productivity by 30%
“We found that connection and productivity, they both get boosted by about 30% when you bring people together, but then intentionally, and it lasts for months.”
Cook: Product managers require three to four uninterrupted hours for creative flow
“You know, as PMs, we need time for creative work. We need that deep work time, and that doesn't happen when you've got all of these meetings with 30 minutes in between each of them. You need sort of, you know, three to four hours to get that going, to get into…”
Cook: Atlassian acquired Loom because asynchronous video became internally essential
“That's a big part of why we bought Lib.”
Cook: Jira operates as a platform underlying four distinct Atlassian products
“Jira is also a platform as well as just, you know, Jira software, the product. There's actually four different products on top of it.”
Cook: Aligning three or four separate team roadmaps is basically impossible
“I don't know if you've ever tried to align, you know, three or four different roadmaps so that the timing is just right to get some improvement through, but it's basically impossible.”
Cook: Half or fewer of all Jira Software users are developers
“Then actually it's more like 50% or maybe just shy of 50% are developers. And the rest is this huge mix of support and operations and sales and marketing, finance, design, HR, Legal, just this massive mix of everybody, all the roles you could think of in a com…”
Cook: Atlassian evaluates new product bets using a five-stage gate framework
“So we changed that to create really small groups with stage gates that we call wonder, explore, make, impact, and then getting to scale. And that meant to assess those bets at every stage.”
Cook: Atlassian pivoted a standalone whiteboard product into a Confluence feature
“So we had a whiteboard product that we thought would Be its own product, sort of like a Jira product discovery. And when we came to one of those gates with the team, we realized actually, you know, this is more like a really useful document type. And so now yo…”
Jira leadership holds weekly 'Fight Club' meetings for direct product conflict
“What we put into place is something we called fight club... It's 30 minutes every week, and it's just for myself, my engineering, and my design leader, and we get together, and we know that we're going in there to have a conflict.”