R
Retromik

Elephant in the Room Retrospective

Name the hard thing first — the one everyone sees but no one says.

Use this template free

Free · No credit card · Guests join by link

The board

01

THE ELEPHANT

What's the hard thing we keep avoiding?

02

EARLY CRACKS

What small issues could grow if ignored?

03

WINS

What went genuinely well?

Every team has an elephant in the room — the problem everyone can see but no one wants to name. It survives not because people don't know about it, but because raising it feels risky. The Elephant in the Room retrospective is built to make naming it the point, not the exception.

Inspired by the idea of doing the hardest thing first, this format gives the uncomfortable truth its own column and discusses it before anything else — while the team still has the energy and focus to act on it. A Wins column keeps the session balanced, so it surfaces hard truths without turning into a pile-on.

When to use an Elephant in the Room Retrospective

  • A recurring problem keeps getting worked around instead of raised
  • Retros feel polite but nothing uncomfortable ever actually gets said
  • The team trusts each other enough to go deeper than surface-level feedback
  • After a rough sprint where the real cause is obvious but unspoken

How to run an Elephant in the Room Retrospective

  1. 1

    Name the elephant anonymously

    Everyone writes cards at the same time, concealed and unattributed. Anonymity is exactly what makes it safe to name the hard thing no one says out loud.

  2. 2

    Vote on what actually matters

    Place a limited set of voting tokens on the cards that most need a conversation. The team's votes usually push the real elephant straight to the top.

  3. 3

    Discuss the elephant first

    Start with the highest-voted hard card while focus and energy are highest — don't save the uncomfortable topic for the last five minutes, when it's too late to act on it.

  4. 4

    Reveal and group themes

    Authors are revealed and related cards group into named themes, so one big elephant doesn't fragment into ten disconnected complaints.

  5. 5

    Commit to a first step

    Turn the elephant into one small, owned action — the first bite. A hard problem you can actually start on beats an ambitious plan nobody begins.

Anonymous writing, voting, grouping and action items work the same as in any Retromik retro.

Read the full facilitation guide

Example cards

What good cards look like for a software team. Specific, about the work, never about a person.

THE ELEPHANT

  • We keep committing to more than we can finish.
  • Two senior engineers disagree on the architecture and decisions are stuck.

EARLY CRACKS

  • Code reviews are getting shorter and less careful.
  • People have stopped speaking up in planning.

WINS

  • We shipped the export feature customers asked for.
  • Onboarding the two new joiners went smoothly.

A 50-minute agenda

  1. 0–5 minSet expectations: anonymous, no blame, one first step
  2. 5–15 minWrite cards silently
  3. 15–20 minVote
  4. 20–40 minDiscuss the top elephant first, then early cracks
  5. 40–50 minAgree a first step, then close by reading the wins

Common mistakes

  • An elephant that names a person. Describe the situation, not who's in it.
  • A good discussion that ends without a first step.
  • Skipping the wins. Hard conversations need the reminder.
  • The facilitator defending the status quo. Let the elephant be named before anyone explains it away.

Frequently asked questions

What is an Elephant in the Room retrospective?

It is a retrospective format with three columns: the hard, avoided topic (the elephant), small issues that could grow if ignored (early cracks), and what genuinely went well (wins). The team discusses the elephant first, while focus is at its highest.

Why discuss the hardest thing first?

Teams tend to spend their energy on easy wins and leave the uncomfortable topic for the last few minutes, when there's no time left to act. Naming and discussing the elephant first — the hardest task first — is what turns it into a real action item instead of a parking-lot note.

Does this format stay psychologically safe?

Yes. Cards are written anonymously and aren't attributed to individuals, so people can name a hard truth without it being tied to them. The Wins column keeps the session balanced so it surfaces problems without becoming a pile-on.

Is this template free to use?

Yes. Retromik is a free retrospective tool — sign up, pick the Elephant in the Room template, and share the board link. Participants join as guests without an account.

What if nobody writes an elephant card?

Give it one more round of writing and say why it matters: anonymous cards are the safest place to raise it. If the column is still empty, look at the Early Cracks; sometimes the elephant shows up there first, in smaller pieces.

Related templates

Mad, Sad, Glad Retrospective

Mad · Sad · Glad

An emotional check-in that surfaces how the team actually feels — before it becomes attrition.

View

Sailboat Retrospective

Wind · Anchors · Rocks

A visual metaphor the whole team gets instantly: what propels us, what drags us, what could sink us.

View

Start, Stop, Continue Retrospective

Start · Stop · Continue

The most actionable retro format — every column maps directly to a behaviour change.

View

Run an Elephant in the Room Retrospective with your team

Create the board in under a minute, share the link, and your team joins anonymously — no accounts needed for participants.

Start free