Structured Feedback System

Say the hard thing so it’s heard — not defended against.

Structured Feedback System

What this fixes

There’s something you need to say to someone - but you’ve been putting it off. The problem usually isn’t knowing what to say. It’s worrying about how they’ll take it.

The moment feedback feels like an attack, people stop listening and start defending themselves. This tool helps you turn the message into a signal about behaviour instead of a judgement about the person, so the conversation leads to one agreed change instead of an argument.

How this works

Imagine this: a lead needs to tell a talented engineer that they talk over people in reviews. Said as “you’re dismissive”, it’s a character verdict - and the engineer defends. Said as “in yesterday’s review, you cut across Sam twice before he finished; he stopped offering ideas - how did that look from where you were sitting? Next time, can we hear each person out before responding?”, It’s a signal about behaviour, and the conversation stays open.

Prepare the conversation in four beats: observation, impact, invitation and forward-ask. Observation describes what happened, not who the person is. Impact explains why it matters. The invitation pauses to hear their perspective. The forward-ask agrees on one thing to do differently next time.

The invitation is the key. It keeps the conversation human instead of sounding like a judgement. Finish only when you’ve agreed on one specific change.

This is preparation, mostly solo. You work out the four beats before the conversation; the conversation itself is where it lands.

Time required

Solo ✓   About 15–20 minutes to prepare, then the conversation itself.

The time required is indicative and will depend on how hard the message is and how much you rehearse.

Read the short preparation guide first - about 6–8 minutes. It is a downloadable PDF on this page.

When to use

Bring one real conversation you’ve been avoiding - a specific person and a specific thing you need to say.

Use it whenever:

  • there’s hard feedback you keep meaning to give but haven’t
  • you’ve softened a message so much it stopped meaning anything
  • a pattern needs to change, and no one has named it out loud
  • you want to say the hard thing without damaging the relationship

Not the right tool if: you’re on the receiving end of hard feedback - for staying steady while you take it, use Steady Receive (the other side of the same conversation). If it’s a live two-way disagreement rather than one message to deliver, use Alignment Under Conflict Lab; if there’s a decision to settle, use Trade-off Conflict Resolver.

What you get

  • The hard message delivered - and actually heard
  • One specific change the other person agrees to
  • The relationship is intact, sometimes stronger

You’ve done it well when: the other person can restate your feedback without getting defensive and commits to one concrete change - and you’d both be comfortable talking again tomorrow.

What you’ll notice

  • How much of the fear was about their reaction, not the message
  • That an observation lands where a verdict would have bounced
  • The invitation changes the tone - it stops being one-way

Why this works

People learn when they feel safe enough to listen. Judgements trigger defence; specific observations don’t. By focusing on behaviour, explaining its impact, inviting their perspective and agreeing on one change, the conversation stays focused on learning instead of blame. (Based on principles of behavioural feedback and threat response in difficult conversations.)

What you need

One real conversation. A specific person and a specific thing you’ve been needing to say - not a general intention to “give more feedback”.

The preparation sheet (supplied). Where you draft the four beats - observation, impact, invitation, forward-ask - and the one change to land. Prepared before the conversation; kept for reference, not read aloud.

A quiet few minutes. This is preparation, not performance - somewhere you can think the message through before you have it.

Optional: a colleague to rehearse with. For an especially hard message, saying it out loud to someone first takes the edge off the delivery.

Steps

  1. Name the observation (4 min). Write the specific thing you saw - behaviour, not character. “You cut across Sam twice”, never “you’re dismissive”. If you can’t point to a moment, you’re not ready to deliver it.
  2. Name the impact (3 min). Write the concrete effect it had - on the work, the team, or you. Keep it factual, not accusatory: “he stopped offering ideas”, not “you shut everyone down”.
  3. Prepare the invitation (3 min). Write a genuine question that hands them the floor - “how did that look from your side?”, “does that fit your view?”. You’ll pause here in the conversation and mean it.
  4. Prepare the forward-ask (3 min). Write one specific thing to do differently next time - small, concrete, doable. This is what you’re steering toward, not a list of grievances.
  5. Have the conversation. Deliver the four beats in your own words - observation, impact, invitation, listen, then the forward-ask. Keep it human; never read the structure out like a form.
  6. Land one change (2 min). Before you finish, make sure they’ve named one specific thing they’ll do differently. If they haven’t, you’re not done.

Output / Takeaways

You leave with:

  • The hard message delivered and heard
  • One specific change the other person committed to
  • A relationship that survived the conversation

Important rules

  • Observation, never a verdict - the specific behaviour, not who they are
  • Keep it human - the structure guides you; never read it out as a script
  • Always invite before you ask forward - pause, and mean the question
  • You’re not done until they’ve named one change - the change is the output

Planning to facilitate this activity? Access the resources below to get started.

MIndn
Execution must be smooth. Not chaotic or stressful.
Built by Witmer.