Constructive Feedback That Lands

By Better Wise

Feedback That Lands: The Next Step After a Clear Request

In mediation, the quickest way to turn a complaint into a conversation is to separate what happened from the story about who someone is. You have already practiced turning hints into specific, doable requests. This lesson adds the piece that makes a request feel fair: naming what you observed and why it mattered before you ask for a change.

By the end of this lesson, you can:

• Separate a camera-checkable observation from your interpretation.
• State the impact in one sentence, tied to the work or the relationship.
• End with a forward-looking suggestion the other person can act on.
• Deliver the whole sequence in under aminute or two, without hedging or softening it into a hint.
• Notice the gap between how the feedback landed and what you heard back, then adjust once.

Observation, Impact, Suggestion: The Three-Part Sequence

Think of feedback as a short, sturdy bridge with three planks. If one plank is missing, the listener has to guess, and guessing is where defensiveness starts.

Note: The sequence below is often called SBI (Situation, Behavior, Impact), with a fourth move added: the forward-looking suggestion. You do not need the acronym. You need the three sentences.

1. Observation: something a camera could record.

An observation describes behavior, not character. Compare:

The test is simple: could a camera have caught it? If yes, it is an observation. If it only exists in your head, it is an interpretation, and interpretations invite arguments about who is right.

Watch for absolutes: "always," "never," "constantly." One instance is one instance. Say how many you actually saw.

2. Impact: one sentence on the effect.

Impact answers the question the listener is silently asking: why does this matter to you and to the work? Tie it to something concrete: time lost, rework created, a decision delayed, a worry about the relationship.

• "That cost the team about an hour of rework."
• "I had to redo the schedule, which pushed the deadline by a day."
• "I left that meeting unsure whether my input was wanted."

Keep it to one sentence. Long impact statements slide into accusation.

3. Suggestion: forward-looking and doable.

You already know from the last lesson what makes a request work: specific, small, and within the other person's control. The suggestion is a request aimed at the future.

• "Next time, could you add the date prefix before saving?"
• "Could you stay through the blockers section so we can hear your read?"
• "When you give a review, could you start with one thing that works, then the concerns?"

Notice each one is phrased as a future action, not a verdict on the past.

Put together:

"In the last two planning meetings, the design review was scheduled before the engineering estimate was ready. That meant we rebuilt the timeline twice. Could we agree that design review comes after the estimate lands?"

That is about thirty seconds. It names behavior, names cost, and offers a path.

1. Say the observation: what a camera would have recorded, with no absolutes.
2. Say the impact: one sentence on time, work, or trust.
3. Ask for the forward action: small, specific, in their control.
4. Stop talking. Let them respond before you add anything else.

Tip: The fourth step is the one people skip. After the suggestion, take a breath and leave a real pause. Feedback is a two-way exchange, not a broadcast.

Practice (try it now):

Rewrite each sentence as an observation, then add an impact and a forward suggestion.

1. "You're unreliable and you keep ignoring my messages."
2. "You're too blunt in client emails."

Click to reveal a model answer

1. "In the last two weeks, I sent three messages about the vendor contract and did not get a reply for four days. That left the contract unsigned past the deadline. Could you reply within one working day, even if the answer is 'not yet'?"
2. "In two recent client emails, the opening line named the problem without any context about what was already working. The client called me to ask if we were unhappy with them. Could you open with one line on what is going well, then name the issue?"

Timing, Tone, and the Delivery Details That Decide the Landing

The same words can land as care or as attack. Delivery, not content, usually decides which.

Private first, public almost never. Correcting behavior in front of others reads as status punishment. Praise in public, coach in private, and if you must address something in a meeting, address the process, not the person.

Soon, but not hot. Waiting a month means the other person no longer remembers the moment. Speaking in the first spike of frustration means your tone carries more than your words. Aim for calm and near enough in time to be verifiable.

Ask permission when it matters. A short "Can I give you some feedback on how the handoff went?" gives the listener two seconds to brace. That tiny bit of choice measurably lowers defensiveness.

Separate the check-in from the verdict. "How did that feel from your side?" after the sequence keeps it a dialogue.

Watch your own nonverbal channel. Your volume, pace, and face must match the words. If you say "no pressure" while your jaw is tight and your arms are crossed, the body wins. That mismatch is exactly what you learned to read in the previous lesson; now you are the one being read.

Mind the channel. A short, specific observation about a missed detail usually works fine in a written message. Anything with emotional weight, ambiguity, or a history behind it belongs in a conversation where tone and face are available. You will go deeper on channel choice later in this module.

Practice (try it now):

You are about to give feedback to a colleague who has interrupted you three times in meetings. Write (a) your three-part sequence and (b) the first sentence you use to ask permission.

Click to reveal a model answer

(a) "In the last three team meetings, when I was describing the new workflow, you finished my sentences and moved to your own points. I stopped explaining and the group missed the part about the reporting delay. Could you let me finish the sentence before responding?"

(b) "Can I raise something small about how the meetings have been going?"

A strong answer keeps the observation camera-checkable, the impact to one sentence, and the suggestion within the other person's control.

Feedback Delivery: What to Say

Formats, channels, and how to complete a feedback sequence correctly:

• Observation: _____
• Interpretation dressed as fact: _____ rather than an observable behavior
• Impact: _____
• Suggestion: _____
• Why "always" and "never" weaken feedback: _____
• Best moment to give corrective feedback: _____

Mediator's Field Notes

A few rules of thumb I have collected from watching hundreds of these conversations go sideways and then get repaired.

• Say it in under two minutes. If your feedback needs five minutes of setup, you are building a case, not offering feedback. Write it out first and cut it in half.
• One issue at a time. Bundling three complaints feels efficient and lands as an ambush. Pick the one that matters most now.
• Do not sandwich with vague praise. A generic compliment before bad news makes people brace at every compliment afterward. Use honest, specific appreciation if it is real, then the feedback.
• Drop the word "just." "I just wanted to mention" shrinks your own message before it arrives.
• Check understanding, not agreement. "Does that make sense the way I described it?" is fair. "You agree, right?" demands compliance.
• Expect a reaction, not a thank-you. A pause, a flush, or a defensive first sentence is normal. Give it room; defensiveness often fades in a minute if you do not argue with it.
• Repair your own slips. If your tone comes out sharper than you planned, name it: "That came out harder than I meant. Let me say the impact more clearly."
• Common mistake: turning the suggestion into an ultimatum. "You need to fix this" is a threat, not a request. Keep it as something they can choose to act on.

Bringing It Together

Here is the pattern in one line:

1. Start with _____ that a camera could record.
2. Follow with _____ about the work or the relationship.
3. Close with _____ aimed at the future.
4. Then _____.

The core skill of this lesson: observation, impact, suggestion, pause. Four moves, thirty seconds, and a relationship that is still intact when you finish. Whether the other person changes the behavior is not fully in your hands. Whether they walk away feeling judged as a person, or feeling clear about a specific thing to try, largely is.

Next up is the checkpoint for this module, where you will pull together reading nonverbal signals, making clear requests, and giving behavior-focused feedback into one practice round.

Front: What makes the observation part of feedback camera-checkable? Back: It describes behavior someone could have seen or recorded, with no interpretation or character judgment.

Front: Why do 'always' and 'never' weaken feedback? Back: They pull the conversation into arguing about frequency instead of focusing on a change in behavior.

Front: What should the impact sentence be tied to? Back: Something concrete: time lost, rework created, a decision delayed, or trust affected.

Front: What makes a forward-looking suggestion doable? Back: It is specific, small, and within the other person's control.

Front: What should you do right after delivering the suggestion? Back: Stop talking and pause so the other person can respond before you add anything.

Front: Where should corrective feedback usually be given? Back: In private, one issue at a time, with a direct message rather than a public correction.

Front: Why ask permission before giving feedback? Back: A brief heads-up gives the listener a moment to prepare and lowers defensiveness.

Front: Why avoid the vague-praise sandwich? Back: Generic praise before criticism makes the listener brace at every compliment afterward.

Front: What is a fair way to check understanding? Back: Ask whether the feedback made sense as described, not whether the person agrees.

Front: How should you read a defensive first reaction? Back: As normal, and often temporary: give it room instead of arguing with it.

Front: When is written feedback usually fine? Back: For short, specific observations about a missed detail with no emotional weight behind them.

Front: When does feedback belong in a conversation? Back: When it carries emotional weight, ambiguity, or history, because tone and face matter.

Front: What is the purpose of the suggestion in the sequence? Back: To turn a past problem into a specific, doable future action the person can take.

Front: What is the correct order of the four moves? Back: Observation, impact, suggestion, then pause for the response.

Wrapping Up: The Three Planks and the Pause

• An observation is behavior a camera could catch. If it lives only in your head, it is an interpretation, and interpretations start fights.
• Impact is one sentence on what the behavior cost, tied to work, time, or trust.
• The suggestion points at the future: small, specific, within the person's control.
• Delivery decides the landing: private first, soon but calm, a quick request for permission, and a real pause afterward.
• Call back to the two-part habit: read the nonverbal signals, then make the request concrete. This lesson just puts a reason in front of the request.

Next you will bring all of it together in the module checkpoint, where you practice reading tone and body language, turning hints into clear requests, and delivering feedback in one continuous scenario.