Elephant in the room retrospective

Sooner or later, every team has a topic that everyone knows about and nobody raises. This format gives the team permission to name it, look at what it costs, and understand why it stayed unspoken for so long.

The Elephant in the Room

Name the unspoken problem plainly—what have we been avoiding?

Impacts

Spell out the consequences on people, delivery, and stakeholders

Feelings

Share how this situation makes you feel—helps us build empathy

But why?

Explore why we’ve been avoiding it—what beliefs or dynamics are at play?

Use this template — it's free

What an elephant in the room retrospective is

An elephant in the room is a problem that is obvious to everyone and discussed by no one, at least not in meetings. It comes up in private chats, on the way to lunch and in one-to-ones, then disappears whenever the whole team is together. Ordinary retros rarely catch it, because their columns invite safe, familiar cards.

This retrospective is built around a single question: what have we been avoiding? The board has four columns that take the topic apart in a deliberate order. The Elephant in the Room names it plainly. Impacts spells out what it costs people, delivery and stakeholders. Feelings lets people say how the situation affects them. But why? asks why the team has avoided it, and which beliefs or dynamics kept it quiet.

Why it works when a general retro does not:

• The format grants permission. When the template itself asks for the unspoken problem, raising it is the assignment, not an act of disloyalty.
• Impact before solutions. Teams that finally name a hard topic often jump straight to fixes, and the fixes miss. Writing down the consequences first shows how big the problem really is.
• Feelings get their own space. Kept out of the other columns, emotions stop leaking into the discussion as sarcasm or silence.
• It asks about the silence itself. "But why?" is not only about the root cause of the problem. It is about why nobody said anything. That answer is usually what needs changing, or the next elephant will follow the same path.

When to use it, and when not to

Run it when you see signs of avoidance:

• retros have become polite and empty, while hallway conversations are not;
• the same action item misses its due date sprint after sprint, and nobody asks why;
• a topic gets a long silence or a nervous joke whenever someone touches it;
• a deadline, a decision or a product direction that most of the team does not believe in, but follows anyway.

Do not use it, or not yet, when:

• The elephant is one person's behavior or performance. A group retro is the wrong place to discuss a colleague. That is a conversation for the person and their manager, and for HR if it involves misconduct.
• Two people are in open conflict. Talk to them separately first. A group session can follow, about how the conflict affects the team's work.
• Trust in the team is very low. If people fear consequences for speaking up, start with something lighter. Mad Sad Glad lets frustration out without asking anyone to name a single problem.
• The team has just formed. There is no history to avoid yet; a hopes and fears exercise sets up the trust you will need later.
• It would be the third time this quarter. The format loses its weight if it becomes routine. Use it when there is an elephant, and rotate with formats such as 4Ls otherwise.

Before you run it

This is the one retro format where preparation matters more than the board.

• Talk to the manager first. If the elephant involves their decisions, agree on whether they attend. If they do, ask them to listen through the first rounds and speak last. A single defensive answer can end the session.
• Consider an outside facilitator. A Scrum Master or lead from another team has no stake in the topic, which makes it easier for everyone else to speak.
• Set ground rules out loud. Talk about situations and decisions, not character. What is said in the room stays in the room. Nobody has to write in Feelings. Nobody guesses who wrote a card.
• Be honest about anonymity. ProstoRetro makes cards anonymous by default, each person can choose per card, and voting is anonymous. An anonymous card hides the author's name from the team, but the app still records who wrote it, and nothing hides a writing style or the context. In a team of five, a card about the release process from the only person who runs releases is anonymous in name only. Say this at the start, so nobody feels misled later.

The four columns

The Elephant in the Room: name it plainly

One avoided problem per card, in plain words. Softened phrasing ("communication could be improved") is how elephants stay hidden. The test: would saying this out loud in a normal team meeting feel risky? If not, it is a regular problem, and it belongs in a regular retro.

• The March launch date is not going to happen, and we all know it
• We say we do code review, but most pull requests are approved unread
• Product decisions get reversed after we have started building
• We and the platform team have stopped talking to each other

Several elephants may appear. That is normal: voting decides which one gets the discussion, and the others are now on record.

Impacts: what it costs

Concrete consequences for people, delivery and stakeholders. The test: could you point to it? "Morale is low" is a conclusion; "two weekends worked this month" is an impact. Impacts make the case for dealing with the elephant without anyone having to argue.

• We worked two weekends this month to look on track
• Support keeps promising customers a date we won't hit
• Three bugs that review should have caught reached production this sprint
• New joiners copy the habit because nobody tells them otherwise

Feelings: how it affects you

How the situation makes people feel. A real feeling usually fits after "I am": tired, embarrassed, anxious, relieved. "I feel that the roadmap is wrong" is an opinion; it belongs in another column. This column is where anonymity helps most, and where the facilitator should be most careful: read feelings out, acknowledge them, do not debate them.

• Tired. Every planning session feels like theater
• Embarrassed when customers ask me about the date
• Anxious that writing this makes me look like I'm not a team player
• Relieved that this is finally on the board

But why? What kept it unspoken

The beliefs, incentives and dynamics that made silence the safer choice. Keep the focus on the avoidance, not only on the problem's technical cause. "The estimate was wrong" explains the late launch; "nobody wants to be the one who delays it" explains why the elephant got this big.

• Last time someone questioned a date, they were told to be more positive
• We assume leadership already knows and has decided
• Raising it means admitting we agreed to the plan
• It's easier to fix it quietly ourselves than to have the argument

Use this template — it's free

A 60-minute elephant in the room agenda

For a team of four to nine. If the discussion is still going somewhere useful when time runs out, book a follow-up.

1. Check-in, 5 minutes. Something calm rather than playful, such as a question from the work icebreakers, or a round where each person says in a word how they arrive.
2. Purpose and ground rules, 5 minutes. Say why you chose this format, read the ground rules and explain what anonymous cards do and do not hide.
3. Silent writing, 12 minutes. Start with the elephant column, then add impacts, feelings and reasons. Cards stay hidden from others until the writing ends, so nobody waits to see whether it is safe to write first.
4. Grouping, 6 minutes. Group the elephants that describe the same problem, then the cards in the other columns. Read cards out without commenting on them.
5. Voting, 4 minutes. Everyone votes on which elephant to discuss. Votes are anonymous, so the result reflects the team, not its most senior member.
6. Discussion, 20 minutes. Take the top elephant across the board in order: impacts, then feelings, then why. Ask "what would have to be true for us to talk about this openly?" before anyone proposes a fix.
7. Next steps, 5 minutes. One or two actions, each with an owner and a due date. Some are practical ("Present the revised launch date to the product director by Friday"); some are about the silence itself ("Dates get a confidence check in every planning").
8. Close, 3 minutes. A quick check-out: what each person takes away, or an anonymous poll on whether the session was worth it.

Running it with a remote team

• Restrict who can join. For most retros, an open link is convenient. For this one, limit the room to team members, so a forwarded link does not bring in someone the team did not expect.
• Make cameras optional. Some people say difficult things more easily without being watched. Agree that nobody needs to explain a switched-off camera.
• Write cards with the summary in mind. Participants who signed in get the retro summary by email, cards included. Describe situations and decisions, never people by name.
• Watch the mood over time. The anonymous pulse survey keeps a history on the team page. The next few results show whether naming the elephant changed anything.

Variations

A pre-named elephant

If one-to-ones have already made the topic clear, the facilitator can name it at the start and the team writes only impacts, feelings and reasons. This is faster and avoids several elephants competing for attention. Ask the team first whether you have named it right.

The elephant hunt

Open an infinite room a week before and ask only for elephant cards. People add them in their own time, and the cards stay hidden until the meeting. When the team meets, decide whether there is enough for a full session or whether a lighter retro fits better.

Add a first step

A fifth column, First step, asks for the smallest move that would make the elephant discussable in normal meetings. It keeps the session from ending on feelings alone. Build it as a custom template; ProstoRetro allows up to five columns.

Common mistakes

• No preparation with the manager. A surprised, defensive leader can turn the session into evidence that speaking up is a bad idea.
• Guessing authors. "Who wrote this?" ends honesty for months. Stop it the first time it happens.
• Debating feelings. "You shouldn't feel that way" is never a useful reply. Acknowledge the feeling and move to impacts and reasons.
• Making it about one person. If the cards start describing a colleague, steer back to situations and decisions, and take the rest offline.
• Ending with no step at all, or with ten. One or two small, owned actions show the session mattered. Ten show that none of them will happen.

FAQ

What is an elephant in the room retrospective?

A retrospective format for the problem everyone knows about and nobody raises. The team names the problem, writes down its impacts and their feelings about it, and explores why it stayed unspoken, then agrees on a first step.

Are the cards really anonymous?

In ProstoRetro, anonymous cards do not show the author's name to the team, and they are the default. The app itself still knows who wrote each card, and in a small team the content can give a person away, so tell people both before they write.

Should the manager attend?

It depends on the elephant. If it is about the manager's own decisions, some teams hold the session without them and share the outcome afterwards. If the manager attends, they should listen first and speak last.

How long does an elephant in the room retrospective take?

Plan for 60 minutes, as in the agenda above, and leave room for a follow-up session. Rushing a hard conversation to finish on time does more harm than stopping at a natural point.

Can I run an elephant in the room retrospective online for free?

Yes. ProstoRetro includes the Elephant in the Room template at no cost, and you can limit the room to your own team members for a session like this. Read how to run a great retro, or see all retrospective templates.