LLenny's Podcast
← All frameworks
LeadershipMegan Cook (head of product, Jira)

Peer Feedback Groups

Small standing peer pods that review each other's rough-draft work to build feedback muscle and trust.

Difficulty
Easy
Time to result
~months to results
Steps
4
Confidence
93%

Divide a large team into small, mixed-seniority feedback groups that meet on a regular cadence. Members bring genuinely rough drafts, and everyone is expected to give feedback aimed at lifting the work up. The small size lowers the stakes so people share early and often, building both craft and relationships.

Origin

Developed by Megan Cook to rebuild psychological safety on her growing Jira PM team.

Core principles

  • 01Feedback is a muscle — reps in low-stakes settings build comfort for high-stakes ones
  • 02Small groups feel safe; big rooms feel like exposure
  • 03Mixing leadership levels models what helpful feedback looks like
  • 04Reviewing early drafts prevents wasted work on polished-but-wrong direction

How to run it

  1. 1

    Split the team into small pods

    Break a large team into small groups so members actually get to know each other and don't have to reach out cold across the whole org.

    Pro tip Mix leadership levels in each pod so senior members model the kind of feedback that's helpful.

  2. 2

    Meet on a regular cadence

    Have each pod meet roughly every two weeks so the practice becomes routine rather than a rare, stressful event.

    Pro tip Regularity is the point — doing it again and again is what makes it feel comfortable.

  3. 3

    Bring rough drafts, not polished work

    Someone brings an early-stage artifact — a strategy, a new experience, an experiment idea — and everyone is expected to give feedback.

    Pro tip Anything to do with the craft qualifies; leaders bringing their own rough strategies signals it's safe.

    Watch out Waiting until work is painfully polished to seek feedback risks wasting large amounts of work when direction has to change.

  4. 4

    Keep the culture lifting

    Orient every session around making the person's work stronger, so getting feedback is experienced as positive and relationships are forged.

In the wild

Cook's own strategy review

Cook took her own strategies into a peer feedback group and got excellent, surprising feedback from the team.

Members forge new relationships and learn that early feedback is positive rather than threatening.

Common mistakes

Only seeking feedback at big formal milestones

Going through a review once a quarter keeps it stressful and rare; frequent small reps are what build the muscle.

Is it for you?

Best for

Product or craft teams that have grown too large for everyone to know everyone and want mentorship-like feedback without formal mentors

Not ideal for

Very small teams where everyone already reviews everyone's work informally

From the transcript

we divided the team into these smaller groups with

07:30

peer feedback groups. And the idea is that they meet uh every 2 weeks or so. Somebody brings something that's in a pretty rough draft…

08:00

it's a small team, so it's less stressful

09:30

I've taken my own strategies in there and gotten excellent feedback, surprising feedback from the team

09:00

From the episode

Lessons from Atlassian: Launching new products, getting buy-in, and staying ahead of the competition

Megan Cook (head of product, Jira)