“Do I really need to help this person?”
That is the only question that comes to my mind before providing feedback.
Over time, I’ve found that this simple check-in has made all the difference between feedback that lands and feedback that burns bridges.
I prefer the SBI approach (Situation–Behavior–Impact) when providing feedback. It’s tangible. It’s flexible. And you get to maintain your objectivity and be human at the same time.
The one thing that no one will tell you, however, is that how you deliver the feedback will depend on the individual:
- With a more junior person, they’re probably hoping for guidance — not only what occurred, but how they might have done better in the future.
- With someone you are colleagues with or your boss, it is harder. Advice is seen as judgment. Offering a “fix” is seen as condescending.
Yet, in all instances, there is one thing that holds true:
You’re not excused merely because you find the experience uncomfortable.
If you notice something that’s worth mentioning, and you opt to say something, then your motive is what counts. And that motive should be to assist.
No assistance = no feedback
I’ve learned the hard way. I always assumed that when I gave them feedback, I could then move on. Job done. They’ll get the message. If I’m not willing to put time in to support the person brainstorming a solution, walking them through a different approach, or simply being free to discuss it through then I shouldn’t be providing the feedback in the first place.
As feedback that is not concerned is criticism. We can so readily use the term “constructive” and lose sight of the fact that genuine input is also hard work on our part.
The SBI Method Helps, but It’s Not Sufficient
SBI operates as follows:
- Situation — “During yesterday’s team meeting…”
- Behavior — “…you cut John off twice in his update…”
- Impact — “…which made it hard for the rest of us to grasp his argument.”
It provides clarity and excludes emotion from the equation — or so it does on the surface.
That’s not present here, however: ownership. If I stop there, it’s just a performance review. If I follow up with:
“Would it help if we talked about how to better share space in meetings?”
now it’s a discussion. A partnership.
Most of all, though: an expression of concern.
Check your motivation
I’ve set myself a personal rule:
If I’m not going to assist the person towards improvement then the feedback isn’t given.
Since then, it’s not about them. It’s about me desiring to be intelligent, or correct, or “professional.” That’s a slippery slope. That’s when the feedback is deadly.
The Rule that I now follow
Before you give feedback, especially to a peer or a boss, pause and ask yourself:
“Am I going to put real time into the developmental of this person?”
If the answer is no, then maybe your motivation is not so pure after all.
And if that’s the case, maybe say nothing.
Since the feedback is not simply to highlight the issue. It’s about standing with someone as they work through it.
Final Thought
Feedback isn’t a mic-drop moment. It’s an invitation to co-own a problem. The next time you’re set to provide someone with “constructive notes,” stop yourself and ask the one question that makes feedback sticky:
“Will I be there to assist?”
If the answer is yes go for it. If not, begin there first.
