Someone posted an infographic on LinkedIn, crediting Appreciative Inquiry and David Cooperrider, organizing conversational responses into four types: "Yes, and…" (constructive), "Yes, but…" (destructive), "No" (negative), "No, because…" (borderline acceptable). The visual was clean. The message was clear. The reasoning was thin.

The framework isn't wrong in a vacuum. "Yes, and…" tends to open space. "Yes, but…" can close it. That much holds. What the infographic missed, and what a lot of content in this space misses, is that the word itself is not the unit of analysis. The intention behind it is.

"But" gets a bad reputation in coaching and facilitation circles. So does "why," in certain corners. There's a whole ecosystem of banned words and prescribed phrases built on the assumption that language has fixed effects regardless of context, regardless of relationship, regardless of timing.

It doesn't.

A well-placed "but" inside a structured dialogue can do something a gentle "yes, and…" never could: interrupt groupthink. It can create friction where friction is exactly what's needed. It can signal that someone in the room isn't going along just to keep the peace. These are not small things. In many organizational conversations, they're the missing thing.

The word doesn't carry the effect. The intent does, the timing does, the relationship does.

Destruction has a bad reputation too. The infographic flagged "destructive" as a negative axis, as if pulling something apart is inherently worse than building on it. But deconstruction is part of how change happens. You can't replace a working assumption without first destabilizing it. You can't generate genuinely new thinking in a team that never experiences useful friction. Destructive isn't a flaw. It's a function, and sometimes the most valuable one in the room.

None of this is an argument for using "but" carelessly or for friction as a default mode. The opposite, actually. The point is that awareness matters more than compliance. Knowing why you're introducing a "but," knowing what it might open or close, knowing whether this moment calls for challenge or for building, that's the skill. Following a rule about which words to avoid is a proxy for that skill, and a poor one.

This is where frameworks like the one on that LinkedIn post become limiting. They offer a legible shortcut. They work well enough for someone who has never thought about this. For anyone trying to develop genuine communicative competence, the shortcut becomes the ceiling.

The coaching and facilitation world has a recurring temptation: take something nuanced, make it visual, make it shareable, and in doing so strip out the complexity that made it useful. Cooperrider's work deserves better than a quadrant. So does the person trying to figure out how to show up in a difficult conversation.

The real question isn't which box your response fits into. It's whether you know what you're doing and why, and whether you're capable of choosing differently when the context asks for it.