"You're One to Talk": How Whataboutism Shuts Down Feedback in Your Retrospectives

In the retrospective, someone brings up the valuable point that "I don't think we're testing enough before deploying." The reply doesn't address the idea: "And what about you, who never update the board?" The criticism is left hanging, the team gets caught up in egos, and the original problem remains untouched. It's a tactic as old as rhetoric (very common in childhood), and it has a quiet way of emptying our conversations. Let's talk about why it appears, what it does to a team, and what we can do about it.

An Old Fallacy with a New Name

Whataboutism (the "you're one to talk" move) is a rhetorical tactic and, at the same time, an informal logical fallacy. It consists of responding to an accusation, criticism, or uncomfortable question with a counter-accusation ("and what about you?") or by shifting attention to another topic. Its defining trait is simple: the original point never gets addressed.

It's not new. Classical logic already cataloged it as tu quoque ("you too"), a variant of ad hominem: instead of refuting the argument, you point out the supposed inconsistency of the person making it. Charles Hamblin, and later Douglas Walton, describe it with precision. The English term whataboutism is much more recent. It became popular to describe Soviet propaganda during the Cold War, which answered any criticism by asking "what about the problems of the West?" Today it appears in dictionaries such as Merriam-Webster. What began as a propaganda tool slips, in a small way, into our team meetings.

A warning up front: not every "what about...?" is whataboutism. Providing relevant context or pointing out a legitimate systemic cause is part of critical thinking, and we need it. The fallacy appears when the counter-accusation is used to dodge the criticism, not to respond to it.

Where It Shows Up on an Agile Team

Our work rests on two things that whataboutism loves to hijack: feedback and accountability. Retrospectives, reviews, one-on-ones, community debates... these are all moments when someone puts something on the table that isn't working. And that's where the "you're one to talk" does its job.

"We should write more tests" meets "And what about the QA team, which doesn't review anything?" A Product Owner points out that a delivery arrived late and gets "Sure, and when I was developing, you kept me waiting three sprints for you to prioritize?" The observation, which could have opened an improvement, turns into a tally of grievances. The subject of the conversation changes; the problem stays where it was. And, worse, everyone leaves the room with the feeling of having argued a lot without deciding anything.

Why It's So Tempting (and Why It Doesn't Work)

Falling into "you're one to talk" doesn't require bad faith. It is, above all, a defensive reflex: protecting one's self-image and avoiding the discomfort of accepting criticism. Chris Argyris studied this under the name "defensive routines": both people and organizations develop automatic behaviors to avoid conversations that feel threatening, and throwing the ball back is one of the most effective.

The problem is that, however human it is, it solves nothing. As a fallacy, whataboutism fails at the essential point: even if the counter-accusation were true, it doesn't make the original criticism any less valid. Your being late too doesn't turn my delay into a non-issue. By responding this way, we transform something that was a problem to solve into a fight to win, and fights don't end with learning, they end with a scoreboard.

What It Does to the Team

The cost goes beyond one unproductive retro. The retrospective only works if we can look at problems without them turning into a hunt for culprits. That's why Norman Kerth formulated his famous "Prime Directive": assume that everyone did the best job they could, given what they knew and the resources they had. That premise exists precisely to keep the focus on the system and not on the person. Whataboutism does the opposite: every observation is received as an attack and answered with a counterattack.

That climate erodes something Amy Edmondson has been studying since 1999: psychological safety, the belief that speaking up won't carry a social cost. If every time someone raises a problem they receive a "what about your stuff?", the team quickly learns the lesson: better to stay quiet. And then we mistake that silence for agreement, when in reality it's surrender.

It's Not the Same as Providing Context

If this article should avoid anything, it's turning whataboutism into a label used to silence any nuance. It would be ironic to use the concept precisely to commit whataboutism. Pointing out an underlying cause isn't deflecting: it's digging deeper into the problem. The difference isn't in the words but in the function. The test is simple: does the response take responsibility for the point that was raised, or does it dodge by pointing at someone else?

Douglas Stone, Bruce Patton, and Sheila Heen, in Difficult Conversations, remind us that much of our clashes stem from confusing the impact of something with the intention of the person who said it. Responding to the problem, rather than defending the self, is what separates a conversation that improves things from one that only defends.

What We Can Do (at Three Levels)

There's no trick that switches off whataboutism, but there are habits that reduce it, and it helps to separate them by level of influence, because not everything is in our hands.

At the individual level, the first step is to notice the reflex before giving in to it. When you feel the urge to reply "and what about you?", try addressing the point first and setting your own issue aside: "You're right about that; let's look at the board separately." Swapping "yes, but" for "yes, and" helps, since it adds instead of counterattacking. And above all, it helps to practice what Edgar Schein calls humble inquiry: asking to understand the criticism, not to dismantle the person making it.
At the team level, this is facilitation work. Framing the retrospective as a blame-free space sets the tone from the start. Explicit working agreements ("we tackle one topic at a time; everything else goes to the parking lot") give each problem a protected turn. And whoever facilitates has a key role: gently naming the detour when it happens ("that's a different topic, we'll note it down; let's get back to what Marta was raising") and steering the conversation back on course. The structures that Esther Derby and Diana Larsen present for retrospectives help precisely to keep the focus on the system.
At the organizational level, no team dynamic survives a culture where admitting a problem is costly. Whataboutism thrives where defending yourself is safer than taking ownership. Building psychological safety is, at its core, a leadership task: it has to do with how those in charge respond when they receive criticism. A manager who answers "You're right, we'll review it" instead of "And what about what you did last month?" teaches more about the culture than any talk could. And here we must be honest about the limit: there are organizations where shifting blame is, literally, the way to survive. When "you're one to talk" is the norm and comes from above, the problem can no longer be fixed in a retro.

We fall into "you're one to talk" easily because it defends something very dear to us: the image that we're doing things well. But a team doesn't improve by winning arguments; it improves by solving problems, and for that, someone has to be willing to receive criticism without handing it back like a mirror. Noticing the reflex, addressing the point before the ego, making room before counterattacking: these small gestures change the quality of a team more than any framework.

We'd love to hear from you: do you recognize "you're one to talk" in your retros or reviews? How do you steer things back when it shows up?

Bibliography

Argyris, Chris (1990). Overcoming Organizational Defenses: Facilitating Organizational Learning, Allyn & Bacon.
Derby, Esther and Larsen, Diana (2006). Agile Retrospectives: Making Good Teams Great, Pragmatic Bookshelf.
Edmondson, Amy (1999). "Psychological Safety and Learning Behavior in Work Teams", Administrative Science Quarterly, 44(2), 350–383.
Edmondson, Amy (2018). The Fearless Organization, Wiley.
Hamblin, Charles L. (1970). Fallacies, Methuen.
Kerth, Norman L. (2001). Project Retrospectives: A Handbook for Team Reviews, Dorset House.
Schein, Edgar H. (2013). Humble Inquiry: The Gentle Art of Asking Instead of Telling, Berrett-Koehler.
Stone, Douglas; Patton, Bruce and Heen, Sheila (1999). Difficult Conversations: How to Discuss What Matters Most, Viking.
Walton, Douglas (1998). Ad Hominem Arguments, University of Alabama Press.
Merriam-Webster. "Whataboutism", online dictionary.