Lenny's PodcastLessons from Atlassian | Megan Cook (Head of Product, Jira)
CHAPTERS
- 0:00 – 0:49
Cold open: “Fight Club” as a weekly ritual for healthy conflict
Megan previews a practice she uses with her engineering and design counterparts: a standing weekly slot dedicated to surfacing and resolving tensions early. The goal is to normalize disagreement, prevent avoidance, and strengthen cross-functional trust.
- •A recurring 30-minute weekly meeting for PM/Eng/Design leaders
- •Creates a shared expectation that conflict will be addressed (not avoided)
- •Prevents small issues from compounding into big problems
- •Improves relationships by resolving disagreements early
- 0:49 – 4:02
Who Megan Cook is and what this episode covers (plus sponsor break)
Lenny introduces Megan, her long tenure at Atlassian, and the scale of Jira. He outlines the themes for the conversation: team culture, remote work, buy-in, product expansion, and learning from failure.
- •Megan leads product for Jira, used by a large share of major enterprises
- •Episode topics: innovation, buy-in, remote PM work, psychological safety, failure
- •Context: Atlassian’s breadth of product lines and competitive landscape
- •Sponsor messages before the main conversation begins
- 4:02 – 7:40
Why play matters: psychological safety as the foundation for innovation
Megan explains how she noticed creeping fear and over-polishing in her org, which reduced candor and bold ideas. A leadership offsite reframed “play” as the antidote to fear, motivating deliberate work to restore psychological safety.
- •Signals of low safety: anonymity in feedback, junior folks speaking up less, overly polished work
- •Insight: the opposite of play isn’t work—it’s fear
- •Play helps teams enter flow and stay open to new ideas
- •Psych safety is required for bigger, bolder innovation
- 7:40 – 10:29
Peer feedback groups: making rough drafts normal and feedback a habit
To reduce fear and build trust, Megan’s team formed small recurring peer feedback groups. The structure trains people to both give and receive feedback frequently, lowering the stakes and strengthening relationships across levels.
- •Split a growing PM org into small peer feedback groups meeting biweekly
- •Bring rough drafts (strategies, experiments, new experiences) for early feedback
- •Mixed seniority helps model high-quality, constructive critique
- •Frequent repetition “builds the muscle” and reduces stress around review
- 10:29 – 14:24
In-person “warm-up” and celebrating failure: intentional onsite design for remote teams
Megan describes twice-yearly PM offsites designed to rebuild connection in a remote-first company. They start with fun, then move into strategy and craft workshops, including senior leaders sharing failure stories to normalize learning.
- •Remote teams need time to warm up socially when finally together
- •Onsites combine fun, strategy alignment, and craft skill-building
- •Internal and external experts teach; PMs also teach to reinforce skills
- •Senior leaders share failures to make risk-taking and learning feel safe
- 14:24 – 15:24
The “$10 game” for personal priorities: making time allocation explicit
Megan adapts a classic prioritization exercise to individual workload and expectations. By “spending” $10 across priorities, managers and reports quickly see overload, misalignment, and tasks that aren’t worth the time.
- •List priorities and allocate $10 to represent time/attention distribution
- •Reveals unrealistic plans (e.g., “10 cents” = almost no time)
- •Aligns manager and IC expectations on what matters most
- •Surfaces overload and prompts tradeoffs
- 15:24 – 24:16
Making remote work work: intentional connection, protected deep work, async-first execution
Megan shares Atlassian’s “Team Anywhere” philosophy and practical learnings from remote work. She emphasizes intentional in-person connection a few times a year, synchronized deep work blocks, fewer status meetings, strong documentation, and recorded video updates.
- •Team Anywhere: focus less on where people work, more on effectiveness
- •Bring people together intentionally (connection and productivity lift lasts months)
- •Protect deep work by syncing calendars and limiting meeting sprawl
- •Replace status meetings with async updates (Atlas) and rigorous documentation (Confluence)
- •Use short audio/video recordings (e.g., Loom) to reduce timezone friction and preserve tone
- 24:16 – 32:16
Getting buy-in: treat it as a journey, build advocates early, stay open to better answers
Megan reframes buy-in as iterative coalition-building rather than one perfect pitch. She describes looping in impacted stakeholders early, repeatedly incorporating feedback, and focusing on the problem and hypotheses instead of defending a predetermined solution.
- •Common mistake: aiming for one “perfect proposal” meeting and a quick yes
- •Start early with stakeholders who will be most impacted; iterate with them
- •Executives bring different lenses (CTO vs CMO vs design), so pre-align concerns
- •Be explicit about facts vs hypotheses and how you’ll test them
- •Don’t fall in love with the solution—optimize for customer value and the real goal
- 32:16 – 36:48
Running the decision meeting well: ask for what you need, tell a crisp narrative, know your data
Once the group is convened, Megan recommends setting expectations up front: decision vs feedback vs help on uncertainties. She also stresses a simple narrative arc and being deeply prepared on the supporting data to build credibility under time pressure.
- •Open by clarifying what you want: decision, feedback, or targeted help
- •Use a concise narrative: current situation → what changed → implications/opportunity
- •Bring the right level of detail for busy execs, but be ready to drill down
- •Data fluency increases trust and confidence in the plan
- •Quick recap: partner early, stay open-minded, set up meetings intentionally
- 36:48 – 46:17
Fighting the good fight: driving CSAT and usability improvements without the “shiny feature” appeal
Megan walks through how she helped catalyze investment in customer satisfaction work, which can be harder to fund than new features. The playbook: mine rich feedback, connect usability to revenue outcomes, reduce dependency friction, “show don’t tell,” and start small to build momentum.
- •CSAT = customer satisfaction; usability issues can block access to product value
- •Use survey verbatims and painful customer sessions to pinpoint root causes
- •Tie usability to business outcomes: acquisition, ramp time, and expansion
- •Handle dependencies by making it cheap for partner teams (shepherd model)
- •“Show don’t tell”: demos, before/after, and customer videos create urgency
- •Start small, ship iteratively, and maintain momentum with frequent updates
- 46:17 – 58:00
How Atlassian launches many product lines: signals from usage + a gated innovation process
Megan explains how Jira evolved from a bug tracker into a broader platform supporting many roles, and how that expansion revealed new product opportunities (e.g., Jira Work Management). She then outlines Atlassian’s stage-gated internal innovation system that takes ideas from “wonder” to “scale.”
- •Jira’s user base extends far beyond developers into many functions (marketing, finance, HR, etc.)
- •Customer behavior revealed demand for tailored experiences outside software teams
- •Anyone can pitch new product ideas internally
- •Stage gates: Wonder → Explore → Make → Impact → Scale
- •Resource scaling is gradual (from 1 person to small teams) to validate before investing heavily
- •Customer partnering throughout helps prove product-market fit (examples: Jira Product Discovery, Atlas, Compass)
- 58:00 – 1:04:28
Staying ahead of competitors: customer rituals, innovation culture, agility, and willingness to kill ideas
Megan attributes Jira’s sustained leadership to obsessive customer focus and institutionalized feedback loops, plus a culture that invites experimentation. She also highlights strategic agility (e.g., cloud pivot), seeding future bets, and quickly re-scoping or killing products when needed.
- •Weekly company-wide customer feedback email and frequent research share-outs
- •Multiple feedback channels: in-product, social, and community conversations
- •Innovation rituals like “Ship It” hackathons and broad idea visibility
- •Carving off small teams to explore emerging tech (e.g., AI after ChatGPT)
- •Strategic agility: rapidly reallocating people to big shifts (cloud focus)
- •Kill or reframe bets fast (whiteboard became a Confluence feature instead of a standalone product)
- 1:04:28 – 1:08:29
Failure Corner: missing the bigger platform opportunity (automation) and learning to think 10x
Megan shares a “quiet” failure: shipping a successful automation feature but failing to see it as a broader cross-product service. Atlassian later acquired a company to provide advanced automation—an expensive outcome that taught her to evaluate how ideas could scale across products and years.
- •Original problem: developers forget to update status after switching tools
- •Solution: automation triggered by commits to move issues forward automatically
- •Failure: treated it as a narrow Jira workflow feature instead of a platform service
- •Lesson: ask where the idea could go in 3–5 years and design for broader application early
- •Think about how to 10x impact across user types and products
- 1:08:29 – 1:21:07
Closing practice: “Fight Club” for triad alignment, then lightning round and wrap-up
Megan returns to the Fight Club concept as a concrete practice for remote cross-functional leadership alignment. The lightning round covers books, TV, interview questions, products, life philosophy, surfing advice, and where to find her online.
- •Fight Club: weekly PM/Eng/Design conflict time to resolve hard issues early
- •Book recs: Inspired (Marty Cagan), Scaling People (Claire Hughes Johnson)
- •Hiring: ask about biggest failure to assess introspection and growth mindset
- •Delightful product experience: Traeger smoker (unboxing, playful details, app integration)
- •Life motto: maximize joy; turn annoyances into joy and prioritize relationships
- •Surfing tip: repetition and accountability buddies
- •Where to find Megan: LinkedIn, Atlassian Community, X; she welcomes feedback
