Explorer

Curious and ready to dig in.

Keen to figure out why our releases keep slipping at the last minute.
I've got a few theories about the handover problem and want to test them with everyone.
Ready to go. Last sprint was messy and I'd like to understand it.
Shopper

Here to find one useful idea to take away.

If I leave with one fix for our standups, I'm happy.
Looking for a practical tip on handling interrupt work.
Hoping to pick up one thing I can try next sprint.
Vacationer

Glad to be away from the day job for a while.

Honestly just glad to stop looking at tickets for an hour.
It's been a long week. A break from the backlog is welcome.
Nice to sit down without a deadline hanging over me.
Prisoner

Here because I was told to be.

I have a release going out today and this feels like a distraction.
We never act on retro actions, so I'm not sure why we keep doing these.
Attendance is mandatory, so here I am.

What is an ESVP retrospective?

The ESVP retrospective (Explorer, Shopper, Vacationer, Prisoner) is a short check-in that shows how invested people are before the main discussion begins. It comes from Norm Kerth's book Project Retrospectives: A Handbook for Team Reviews (2001), where it was used to gauge whether a group actually wanted to be in the room. Explorers are curious and ready to dig in. Shoppers want to leave with one useful idea. Vacationers are happy to get a break from the day job. Prisoners are there because someone told them to be. Each person anonymously adds one idea to the column that fits them, and the facilitator then reads the spread out to the team. Anonymity is what makes the format work. A public show of hands produces a room full of Explorers, because nobody wants to admit they would rather be elsewhere. In TeamRetro, ideas are hidden from authorship, so people can answer honestly. Present the four labels neutrally. None of them is the right answer, and a Vacationer or Prisoner is giving you useful information. The value of ESVP comes from acting on the reading. If the board shows mostly Explorers and Shoppers, run the retro as planned. If it shows three Prisoners and a Vacationer, the planned retro is the wrong meeting: shorten it, change the agenda, or ask the room what is going on. Use ESVP when you suspect low buy-in, such as after a new retro cadence, an incident or a change of manager. Running it every sprint tends to make people vote Explorer on autopilot. For quick check-ins, a three-label version without Shopper works well.

ESVP retrospective format

Explorer

Curious and ready to dig in.

Explorers want to discover new insights and are happy to look at anything the retro brings up. When you read the spread, treat a high Explorer count as a green light for a deeper agenda. Be a little cautious if every single idea lands here, especially in a team that has been struggling. That can mean people are answering on autopilot or don't fully trust the anonymity, so it may be worth asking a gentle follow-up question.

Shopper

Here to find one useful idea to take away.

Shoppers are engaged but selective. They will look over everything and leave satisfied if they take home one practical improvement. A board with lots of Shoppers suggests keeping the session focused and ending with clear, small actions. Make sure the retro closes with something concrete so these people feel the time was worth it.

Vacationer

Glad to be away from the day job for a while.

Vacationers aren't especially interested in the retro itself, but they appreciate the break from regular work. This is often a signal of fatigue or a heavy workload. Don't treat it as a problem to fix or a person to call out. If several Vacationers appear, consider a lighter, shorter session, or ask the team whether workload needs to be on today's agenda.

Prisoner

Here because I was told to be.

Prisoners feel they have been made to attend and would rather be doing something else. This is the most important signal on the board, so thank people for being honest and never try to work out who wrote what. Several Prisoners means the planned retro is probably the wrong meeting. Shorten it, change the agenda, or ask the room openly what is getting in the way and whether the retro format itself needs to change.

When to use this retrospective

  • When the team is starting a new retrospective cadence and you want to know whether people see value in it.
  • After a production incident or stressful release, when energy and goodwill may be low.
  • Following a change of manager, team lead or team structure, to gauge how people feel about being in the room.
  • When previous retros have felt flat or actions have gone nowhere, and you suspect people are attending out of obligation.
  • At the start of a long workshop or project review, so you can adjust the agenda before investing hours in it.

Suggested icebreaker questions

  • If this meeting were a holiday destination, where would it be?
  • What is one thing you would explore if you had a free afternoon at work?

Want a warm-up your team plays, not just answers out loud? Browse free icebreakers →

Ideas and tips for your retrospective meeting

  • Keep responses anonymous and say so out loud before people add ideas. A public vote produces a room full of Explorers and tells you nothing.
  • Introduce all four labels in a neutral tone. Make it clear that Vacationer and Prisoner are valid, useful answers and that nobody will be asked to explain their choice.
  • Act on the reading. If Prisoners and Vacationers dominate, shorten the retro, swap in a different agenda, or ask the team what is going on before continuing.
  • Use ESVP when you suspect low buy-in, such as after an incident, a manager change or a new retro cadence. Running it every sprint leads to people picking Explorer on autopilot.
  • Never try to guess who wrote a Prisoner idea or single anyone out. Discuss the overall spread as a team signal.
  • For short check-ins, drop Shopper and run a three-label version to keep it to a minute or two.

Frequently asked questions

What does ESVP stand for?
ESVP stands for Explorer, Shopper, Vacationer and Prisoner. Each label describes a different attitude toward attending the retrospective, from curious and engaged through to attending only because it is required.
Where does the ESVP retrospective come from?
It comes from Norm Kerth's 2001 book Project Retrospectives: A Handbook for Team Reviews. It was later popularised in agile circles as a warm-up and safety check activity.
How long does an ESVP check-in take?
Usually 5–10 minutes. People add one anonymous idea each, then the facilitator reads out the spread and decides whether to adjust the session.
Why does ESVP need to be anonymous?
Without anonymity, most people pick Explorer because admitting to being a Prisoner in front of a manager or peers feels risky. Anonymous input is the only way to get an honest reading of buy-in.
What should I do if the team shows lots of Prisoners?
Treat it as a sign that the planned retro is the wrong meeting. Shorten it, change the agenda to address what is bothering people, or ask the room openly what is going on.
Should I run ESVP every sprint?
No. Used every sprint, it becomes routine and people start choosing Explorer without thinking. Save it for moments when you suspect low buy-in, such as after an incident or a change in leadership.
Ready to run this retrospective?Try this retrospective live