ESVP Explorer Shopper Vacationer Prisoner
Anonymous or private check-in on engagement before deeper retro topics.
Explorer
Curious and eager to discover—wants to engage fully.
Shopper
Open if something compelling shows up—somewhat selective attention.
Vacationer
Present but not deeply invested—along for the ride.
Prisoner
Would rather be elsewhere—important signal for psychological safety follow-up.
This board is for demo purposes only. Your responses are not saved. Close or refresh the page to clear all cards. Do not add any sensitive information.
What is ESVP Explorer Shopper Vacationer Prisoner?
ESVP—Explorer, Shopper, Vacationer, Prisoner—is an engagement check-in format originally described by Esther Derby and Diana Larsen in their seminal book "Agile Retrospectives: Making Good Teams Great" (2006). Unlike most retrospective formats that focus on sprint content, ESVP measures something more fundamental: how engaged are the participants in the retrospective itself? It is typically used as an opening activity before a deeper retrospective format, though it can stand alone as a team health diagnostic.
The four roles represent a spectrum of engagement. "Explorer" describes someone who is curious, eager, and wants to engage deeply—they came to discover something new. "Shopper" describes someone who is open-minded but selective—they will engage if something compelling emerges. "Vacationer" describes someone who is present but not invested—they are happy to be away from their desk but not particularly engaged in the retro content. "Prisoner" describes someone who would rather be elsewhere entirely—they are in the room only because attendance is mandatory.
ESVP is diagnostic, not judgmental. A room full of prisoners is not a personal failure—it is a signal that the retrospective format, frequency, or outcomes need to change. The check-in gives the facilitator real-time data about engagement that they can use to adjust their approach on the fly. If half the room is vacationers, the planned deep-dive retro might need to become a lighter, more energizing format.
When to use ESVP
ESVP is most valuable as a pre-retro check-in when you suspect engagement may be low or when you want to calibrate your facilitation approach based on real data. Use it at the start of a retrospective, before launching into the main format. It takes only five to ten minutes and provides invaluable insight into the room energy.
This format is especially useful when retrospective fatigue has set in—when the team has been running retros for months or years and the format may have become routine. It is also valuable after organizational changes that may have affected team morale, or when new members have joined and you want to understand their engagement level. Teams of any size can use it, though the data is more meaningful with five or more participants.
Use ESVP periodically—every four to six retros—rather than at every session. If you run it every time, the check-in itself becomes routine and people answer on autopilot. It has the most diagnostic value when used sparingly and when the results are genuinely acted upon. Avoid it when you are certain the team is highly engaged—unnecessary check-ins can feel patronizing.
How to facilitate ESVP
Present the four roles and ensure everyone understands each one without judgment. Emphasize that all roles are valid data points, not personality assessments: "This is about how you feel right now about this specific meeting, not about who you are as a person." Then run the check-in anonymously—this is critical. Use paper ballots, anonymous polls, or a digital tool that hides individual responses.
Collect and display the aggregated results. Show a simple bar chart or count: "We have three explorers, four shoppers, two vacationers, and one prisoner." Then facilitate a brief meta-discussion: "What does this distribution tell us? What would help move more of us toward explorer?" This discussion is where the real value lives—not in the data itself, but in the team conversation about engagement.
If the results show mostly explorers and shoppers, proceed with your planned retro format with confidence. If there are significant vacationers or prisoners, adapt on the fly: consider a more energizing format, shorter timebox, or direct conversation about what is making the retro feel unproductive. Destroying the ballots or responses after the session is important—ESVP data should inform the moment, not become a permanent record of individual engagement.
Tips for getting the most out of ESVP
Anonymity is non-negotiable. The moment someone fears their "prisoner" vote will be identified, the data becomes worthless because people will self-censor to avoid looking disengaged. Use a method that makes attribution truly impossible. For remote teams, anonymous polls in tools like Slido or Mentimeter work well. For in-person teams, identical paper slips folded and collected in a hat maintain anonymity.
Do not treat prisoner results as a problem to solve in the moment. Instead, treat them as valuable diagnostic data. If you consistently get prisoners, the issue is likely structural: retros are too long, too frequent, do not produce results, or the team has unaddressed issues that make reflection feel pointless. Address these root causes between sessions rather than trying to convert prisoners during the retro itself.
The most powerful ESVP moment happens when the team discusses how to move people from vacationer/prisoner toward explorer/shopper. This meta-conversation about retrospective design often produces insights that improve every future retro. Common discoveries include: retros need to be shorter, action items need better follow-through, the format needs more variety, or the team needs to see that retro insights actually lead to change.
Variations and adaptations
For remote teams, use an anonymous polling tool with real-time results displayed on screen. The reveal moment—when the bar chart populates—creates a shared experience that establishes emotional connection at the start of the retro. Consider showing the results as a trend over multiple sessions: "Last time we had six shoppers. This time we have four explorers and two shoppers. What changed?" Trends tell a richer story than snapshots.
For async teams, send the ESVP poll 30 minutes before the synchronous retro begins. Display the results at the session start. This approach respects async preferences while still providing the facilitator with engagement data before the session. If the poll results show low engagement, the facilitator has time to adjust the planned format before the live meeting.
A popular variation replaces the four fixed roles with a simple numeric scale from one (would rather be elsewhere) to five (excited to be here). This captures the same engagement data with less labeling, which some teams prefer. Another adaptation uses ESVP as a closing check-in as well: "Were you an explorer, shopper, vacationer, or prisoner at the start? How about now?" The before-and-after comparison measures whether the retro itself was engaging and provides direct feedback on the facilitator effectiveness. A third variation uses ESVP for meetings beyond retros—standups, planning sessions, or demos—to build a broader picture of meeting engagement across the team's routine.
Run Retrospectives in CodeKudu
CodeKudu includes dozens of retrospective board templates, anonymous feedback, AI summaries, and action items that sync to GitHub Issues, Jira, and Linear.
