Your Intent Does Not Absolve Your Impact

I hear a version of this sentence in almost every difficult workplace conversation I sit in on: "That's not what I meant."

Usually, it's true. The colleague who cut you off in the meeting probably didn't mean to dismiss you — they were excited, or in a hurry, or just bad at reading the room. The manager whose feedback stung likely intended to help, not wound. In my experience, intent is rarely malicious. It's just... intent. In other words, it is a private thing, known only to the speaker.

Impact is different. Impact is what actually lands. It's the junior team member who stops speaking up because they were interrupted one too many times. It's the employee who now dreads one-on-ones because a piece of "helpful" feedback felt like a takedown. Impact doesn't care what you meant. It only cares what happened.

The gap between the two is where most workplace friction lives. And here's the uncomfortable part: when intent and impact collide, we tend to judge ourselves by our intent — and judge others by their impact. That asymmetry is corrosive. It lets us forgive our own missteps instantly while holding onto someone else's a lot longer.

Closing that gap doesn't mean assuming bad faith. It means adding one extra step to how we communicate: checking impact, not just declaring intent. If you've hurt or confused someone, "I didn't mean it that way" rarely does the work that "help me understand what happened" or “share with me how that felt” does — because it treats the other person's experience as real, not as a misunderstanding to be corrected.

Good intent should be the baseline we expect from each other. But impact is what we're actually accountable for. So the next time a conversation goes sideways — which one are you leading with?