Anonymous Feedback in Scrum: Trust Builder or Collaboration Killer?
How does feedback happen on your team? A Scrum team member recently shared that she receives feedback anonymously from her teammates and the business. She never knows who made which comments during the feedback process. In their organization, this is the norm. As someone with experience facilitating many feedback processes, this approach surprised me. It raised important questions for Scrum Masters and team leaders. In this post, we’ll explore the pros and cons of anonymous feedback and how it impacts team collaboration and trust.
Common Assumptions About Anonymous Feedback
Several assumptions surround the practice of anonymous feedback in Scrum. Some believe it promotes objectivity by eliminating ego. Others argue that anonymous feedback is a “cop-out”—real feedback should be delivered directly. Another assumption is that anonymous feedback truly remains confidential, with no way to trace comments back to the source. However, all of these assumptions warrant closer examination.
There is no universal answer to whether feedback should be anonymous. In highly collaborative teams, anonymity can either help or hinder progress, depending on the team’s maturity and the context. Additionally, the individuals who have access to the feedback can shape its effectiveness.
Is Anonymous Feedback in Scrum Truly Anonymous?
For feedback to be genuinely anonymous, no one with authority—including the recipient—should have access to the identities of the feedback providers. However, this ideal is often compromised. Employees often share stories of being asked to give anonymous feedback, only to later be confronted by their manager regarding their comments. Breaking confidentiality in this way erodes trust and discourages honest feedback in the future.
Leaders must be vigilant about maintaining anonymity if they advertise it as part of the feedback process. Trust is built on keeping these promises intact.
The Challenge of Guessing the Source
Even with anonymity, recipients often try to guess who said what. I worked with an executive vice president who prided himself on identifying the source of every comment in his 360-degree survey. This behavior is common because people are naturally curious about who is talking about them. While direct feedback offers more actionable insights, anonymous comments can still provide valuable input when handled correctly.
When Anonymous Feedback in Scrum Is Useful
Anonymous feedback can work well in certain contexts—particularly when the respondent pool is large enough to guarantee anonymity. Company-wide surveys are a good example. Anonymity encourages employees to share honest input, especially when feedback is gathered from different levels within an organization.
However, anonymity can also cut both ways. It may help recipients take feedback objectively without being influenced by the identity of the source. On the other hand, anonymity might also lead to unaccountable or careless feedback.
The Pitfalls of Anonymity
Anonymity does not guarantee objectivity. It may allow people to make unhelpful or vague criticisms, knowing they will not be held accountable. Limiting feedback to multiple-choice responses doesn’t solve the problem either—it only reduces detail. Detailed, thoughtful feedback is often the most actionable and valuable for recipients.
The Case for Face-to-Face Feedback
One might assume that meaningful feedback should always be given directly. As my colleague Brett Knowles once noted, “If team members can’t give direct feedback, every daily standup becomes a waste of time.” In highly collaborative Scrum teams, transparency builds trust and strengthens relationships.
However, the appropriateness of anonymity depends on the team’s maturity. A new Scrum team may benefit from anonymous feedback initially, while a mature team may rely more on direct communication. Both approaches can be useful, and Scrum Masters or team leaders should reflect on their effectiveness after each cycle.
Balancing Transparency and Anonymity
Teams shouldn’t lock themselves into rigid feedback models. Team dynamics, goals, and working conditions evolve over time. Transparency and openness remain essential in collaborative environments. However, for newer teams, anonymous feedback may serve as a useful tool to promote objectivity without the pressure of personal judgments.
True anonymity is difficult to maintain in Scrum teams since members often develop hunches about who gave specific feedback. Nevertheless, when used thoughtfully, anonymous feedback can help teams focus on content rather than personalities—especially in the early stages of collaboration.
What Is Feedback For?
The purpose of feedback is to improve team performance by helping individuals contribute more effectively. It should focus on actions rather than personal qualities. However, separating feedback on behavior from personal identity can be challenging. While the ultimate goal is to encourage open, face-to-face communication, anonymous feedback can sometimes be a helpful step toward achieving that norm.
Conclusion: When to Use Anonymous Feedback in Scrum
Anonymous feedback can either build trust or undermine collaboration, depending on how it is implemented. Scrum Masters and team leaders should carefully consider their team’s maturity, goals, and context when deciding whether to use anonymous feedback. Ultimately, the goal is to foster an environment where feedback—anonymous or not—supports continuous improvement and team growth.
Interested in Improving Your Scrum Team’s Feedback and Collaboration?
For organizations seeking to refine their approach to value delivery and build a strong, adaptive backlog. Try our Scrum Application Workshop on Team Dynamics and Feedback Systems is designed just for you. This one-day, on-site event is tailored to your company’s specific needs. It’s an applied 1-day tailored session aimed at helping teams tackle real-world challenges.
Leave a Reply