The PodKnowledge|← All Episodes
Based on Lenny's Podcast data
Lenny's Knowledge Sketch

Psychological Safety & the
Art of Productive Conflict

Megan Cook
Head of Product, Jira (Atlassian)
NOV 2024
Core Idea

Fight Club:
Scheduled Conflict

SELFENGINEERINGDESIGN30 MINS WEEKLY
"The opposite of play is not work, it's fear. When you have scheduled conflict, you address issues early before they become big."
  • 30 minutes weekly with self, engineering lead, and design lead
  • Everyone enters knowing there WILL be disagreement
  • Early conflict prevents bigger problems later
  • Scheduled slots create the mindset to solve hard problems
Building Trust

Three Tactics for Psychological Safety

PEER FEEDBACK6-MONTH ONSITE$10 PRIORITY GAME
  • Peer feedback groups every 2 weeks, show rough work, get safe feedback
  • All-hands onsite every 6 months in Sydney with workshops & failure talks
  • $10 priority game to align time spent vs. priorities
Why it worksSmall group settings build trust. People see it's safe to show unfinished work. You practice giving/receiving feedback repeatedly. Over time, it becomes comfortable instead of stressful.
The inflection pointAround 15 PMs, Megan noticed people stopped speaking up. They worried about judgment. Formality crept in. These three tactics directly counteract that decline.
Remote Excellence

Building World-Class Products Anywhere

  • Connection frequency: Intentional in-person time 3-4x per year boosts productivity 30% and sustains for months
  • Meeting discipline: Block casual chat proactively, don't fill every slot just because you can message
  • Asynchronous documentation: Write decisions down. Remote requires explicit knowledge capture, not hallway conversations
  • Same-week onsite intensity: Entire engineering/design teams working side-by-side in one floor, one week at a time
The Atlassian approach

Remote flexibility IS a human benefit, not just a perk. When you stop thinking "where do you sit" and start thinking "how do we work effectively," remote becomes easier.

The timing insight

Connection doesn't need daily. It needs intentional. 3-4 offsite days per year, booked far in advance, sustained months of productivity gains.

The Playbook

Getting Scrappy Initiatives Funded

  • Start small to lower the perceived bet, prove direction before asking for big investment
  • Use rich data: surveys + customer interviews show WHY not just that there's a problem
  • Make it visual: prototypes, customer videos, design comps excite people more than decks
  • Show the revenue impact: how it affects acquisition, retention, expansion, and unit economics
  • Find low-cost partners: "shepherds" from other teams who review but don't bear dev costs
  • Ship momentum: quick wins keep energy high and build case for next phase
The CSAT lessonDon't wait for top-down permission. Find the data, show the impact, make it easy for partners, and move small. That's how Megan improved Jira's usability when it wasn't on anyone's roadmap.
Contrarian

Product Leadership Myths

✗Conflict kills psychological safetyINSTEAD →✓ Scheduled, intentional conflict builds safety because issues get resolved early and people know they're welcome to disagree.
✗Remote = disconnected teamsINSTEAD →✓ Remote with 3-4 intentional onsites per year produces better connection and 30% productivity gains over fully in-office.
✗You need permission for good ideasINSTEAD →✓ Build the case with data, start scrappy, make it easy for partners, and momentum funds the big bet.
✗Customer satisfaction is a polish jobINSTEAD →✓ Fixing usability and quality issues is core product strategy, it unlocks value and drives retention and expansion.
Based on Megan Cook's episode on Lenny's Podcast. All ideas on this page are from the episode.Watch on YouTubeFollow @meganwcook on X
GO DEEPER IN THE EPISODE
03:50 Creating space for play and psychological safety on teams07:36 Peer feedback groups10:30 Sharing stories of failure13:33 The “10 dollar” game for priorities15:24 Advice on making remote work, work24:16 Getting buy-in for your ideas28:33 The importance of staying open-minded34:05 A quick summary of how to get buy-in36:45 Fighting the good fight38:19 Identifying customer pain points43:08 Starting small and showing success46:08 Launching new product lines53:35 Atlassian’s gated process for new product ideas58:29 How Jira stays ahead of competitors01:04:56 Learning from failure01:09:00 Fight club01:10:37 Lightning round
Every sketch here began as a transcript.

Send us yours and we’ll draw it. $1 a transcript.

Sketch mine →
𝕏︎ X / Twitterin LinkedIn📸 Instagram🔗 Copy link
0:00