How Anonymity Works in Unpack
In Unpack, cards are anonymous by default. When a participant creates a card during the reflect phase, no other participant, including the facilitator, can see who wrote it. This design choice is intentional: it removes social pressure and allows team members to share honest feedback without fear of judgment or repercussion.
Anonymity is set at the team level and applies uniformly to every card in every retro on that team. There is no per-card opt-in or opt-out — a team is either fully anonymous or fully attributed. Other retro activities such as check-ins, votes, and action item assignments are always attributed to their respective participants regardless of this setting.
What Anonymity Covers
Here is exactly what is and is not anonymous during a retrospective:
Anonymous by default
- Card authorship — Other participants cannot see who wrote a card. Cards appear on the board without any author attribution.
- Card edits — When you edit your own card, no other participant sees that an edit was made or by whom.
Not anonymous
- Check-in responses — Mood and energy check-ins are attributed to each participant. This is by design, as check-ins are meant to be a visible pulse on team well-being.
- Vote totals — While individual vote attribution is hidden, the total vote count on each card is visible to all.
- Discussion contributions — Live conversation during the discuss phase is naturally attributed. Participants speak openly during this phase.
- Action item ownership — Action items are assigned to named individuals for accountability.
Anonymity is about the written feedback on cards. It creates a safe space for honest input during the reflect phase, while later phases transition to open, attributed collaboration.
Why Anonymous Feedback Matters
Research on team dynamics consistently shows that anonymous feedback channels produce more honest and diverse input than attributed ones. Here is why anonymity is Unpack's default:
Reduces social pressure
Team members often self-censor when they know their name is attached to feedback. Junior team members may hesitate to criticize a process championed by a senior colleague. Anonymity removes this barrier and lets the content of the feedback stand on its own merits.
Surfaces difficult topics
Some of the most valuable retro insights come from uncomfortable truths that people would not share if they had to put their name on it. Issues like interpersonal friction, process failures, or leadership blind spots are more likely to surface when participants feel protected.
Levels the playing field
Without names on cards, feedback from an intern carries the same visual weight as feedback from a tech lead. Ideas are evaluated on their substance, not on who said them. This leads to more equitable discussions and better outcomes.
Builds trust over time
Paradoxically, anonymous feedback builds trust. When team members see that their anonymous concerns are taken seriously and lead to real changes, they develop greater confidence in the retro process. Over time, many teams naturally become more open and some choose to reveal their identities voluntarily.
Facilitator View vs. Participant View
Anonymity is consistent across all roles by default. The facilitator sees the same anonymous cards that participants see. This is a deliberate design decision to maintain trust in the process.
What the facilitator sees
- All cards on the board without author information (same as participants).
- Aggregate vote counts, but not who voted for what.
- Readiness status showing how many participants are ready, but attribution is shown to help manage timing.
- Check-in responses with participant names (check-ins are not anonymous).
What participants see
- All cards on the board without author information.
- Their own cards, subtly marked so they can identify and edit them.
- Vote counts (after the vote phase ends).
- Their own remaining vote allocation during the vote phase.
The facilitator has no special access to card authorship data. Unpack does not provide a "reveal all authors" feature to the facilitator. This protects participant trust and ensures the anonymous feedback mechanism cannot be bypassed.
Configuring Card Author Visibility
Anonymity is a team-level setting, managed from the team's Settings page. Only facilitators and organization admins can change it. The setting takes effect immediately and applies to every existing and future retro on the team.
- Hide names — anonymous (default) — Cards never show who wrote them. Best for honest, low-pressure feedback.
- Show names — Cards show the author's name and avatar. Use only when the team has explicitly agreed to attributed feedback.
Switching to "Show names" fundamentally changes the dynamic of the retro. Only use it when the team has explicitly agreed. Flipping this setting without team buy-in can damage trust and reduce the quality of feedback. Past cards on the team will also start showing their authors.
Best Practices for Anonymous Feedback
- Keep the default. Unless your team has a specific reason to change it, anonymous cards produce better feedback for most teams.
- Remind the team. At the start of the reflect phase, the facilitator should remind participants that their cards are anonymous. This reassurance encourages more candid input.
- Do not try to guess authors. Even if writing style makes authorship obvious, do not call it out. Respecting the anonymity norm is essential for maintaining trust.
- Address all feedback equally. Give every card the same consideration during discussion. Do not dismiss feedback just because you do not know who wrote it.