How to draft difficult feedback messages (with templates)

This is the playbook for the message you've been re-typing in your head — the one you've started writing and deleted three times. Whether it's a Slack note, a 1:1 talking point, or the opening line of a hard conversation, the structure is the same: what you're seeing, the impact, the ask. Below, the structure plus seven templates for situations managers run into most.

If you want the broader methodology context, the Accountability Dial™ guide covers when to escalate and which stage you're in. This piece focuses on the drafting — the actual sentences.

The three-beat structure

Every difficult feedback message — whether it's two sentences or two paragraphs — has the same shape.

Beat 1 — What I'm seeing. Specific, observable, recent. Not "you've been disengaged lately" — "In the last three sprint reviews you've been quiet during the planning portion." Names the behavior, not the inferred state of mind.

Beat 2 — What the impact is. In the team's or the work's terms, not your terms. Not "I felt frustrated" — "The team is making planning decisions without your input, which means the design choices we've been making lately don't reflect your view of the work." The impact is what makes Beat 1 worth raising.

Beat 3 — What I want. Specific behavior, specific date or cadence. Not "be more engaged" — "I'd like you to bring at least one design concern or proposal into the next two sprint plannings, and I want us to look at how it's going at our 1:1 on the 28th."

That's it. Every difficult message is some version of those three beats. The drafting failures are usually:

• Skipping Beat 1 (going straight to impact, which feels like an attack with no evidence)
• Skipping Beat 2 (which makes Beat 3 feel arbitrary)
• Hedging Beat 3 ("you might want to think about" — never request, never accountable)

The five drafting mistakes that undo the message

1. The apologetic opener

"I hate to bring this up, but…" / "I know you've got a lot on your plate, and I really appreciate everything you do, but…"

What you mean: I want to soften this so they don't feel attacked. What lands: You're not sure this is worth raising. So neither am I.

The fix: open warm, but not apologetic. "I want to talk about something I've been noticing." Plenty of softening. Doesn't telegraph that you're not committed to the message.

2. Vague impact

"It's affecting the team." / "This is creating friction."

What you mean: trust me, this matters. What lands: this is your subjective read. I can argue back.

The fix: name the specific second-order effect in observable terms. "Three engineers have asked me whether they should route around you for design review." Now there's nothing to argue.

3. Hedged ask

"It might be worth thinking about…" / "Maybe we could try…"

What you mean: I want to leave room for them to push back. What lands: This isn't a real request. Compliance is optional.

The fix: state the ask directly with a date. "By next sprint planning, I need to see [specific change]. We'll re-check at our 1:1 on the 28th." If they want to push back, they can — but you're not opening the door for them.

4. The post-script disclaimer

"I just want to make sure we're on the same page." / "Obviously this isn't a huge deal, just wanted to flag it."

What you mean: I want to soften the close. What lands: I'm half-taking back what I just said.

The fix: stop talking after Beat 3. The silence is part of the conversation. Don't fill it with disclaimers.

5. The Slack-message wall of text

What you mean: I want to be thorough. What lands: defensive, scripted, distancing.

The fix: if it's longer than four short paragraphs, it should not be a written message — it should be a scheduled conversation, prefaced with one Slack note. "Hey — want to grab 30 minutes today? I want to talk about something I've been noticing." Save the substance for the live exchange.

Seven templates

Each follows the three-beat structure. Adapt the specifics to your situation — these are starting points, not deliverables.

A. Missed commitments (recurring)

Hey [name] — I want to talk about the sprint commitments. In the last three sprints, [specific], [specific], [specific]. The result is that the team is now planning around you not landing your commits, which means we're scoping the work smaller than it should be. From here, I need every commitment you make in planning to land in the sprint or be re-scoped before the standup. We'll re-check at our 1:1 on the 28th.

B. Tone in shared channels

Hey — I read your reply in #product earlier and want to mention it. The phrasing came across sharper than I think you meant — Aria flagged it to me, and I noticed two more this week. Even if that wasn't the intent, it's making people hesitate to bring early-stage ideas into the channel. From here, I'd like you to either DM the person directly when you have a hard pushback, or pause and re-draft in the public channel. Happy to talk if it'd help.

C. Underperforming high-context role

I want to talk about [project X]. Here's what I'm seeing: [three specific instances]. The impact is that [team / customer / dependency] is [specific second-order effect]. I want to understand what's going on for you, and I want us to align on what changes from here. Can we set 30 minutes today or tomorrow?

D. Quiet disengagement

Hey — I've been noticing you've been quieter in our last few 1:1s and in [channel]. I'm not assuming what it means, but I want to check in. Is something going on? I want to make sure I understand what you need from me right now.

(Beat 1 is gentler here intentionally — disengagement is a Mention or Invitation, not yet a Conversation.)

E. Standard not being met (after Mention)

A few weeks back I mentioned [X]. I want to come back to it. I'm seeing [specifics that show the pattern continued]. The impact is [specific]. From here, I need [specific change], by [date]. If [the behavior] continues after that, the next step is [specific consequence]. I'm telling you this directly because I want you to succeed here, and I want you to know exactly where the line is.

(This is a Boundary. State it once. Don't litigate.)

F. Peer-level feedback (you don't manage them)

Hey — I want to flag something from the [meeting / project]. When [specific], [specific impact on me / on shared work]. I'm not raising it as a complaint, I'm raising it because I want to keep working well together. Is there a way we can adjust [specific] going forward?

G. Upward feedback (to your own manager)

[Manager name] — I want to bring something into our 1:1 next week. In [meeting / decision], [specific], and the impact on me / the team was [specific]. I want to understand your thinking, and I'd like us to align on how we handle [similar situations] going forward.

What to do after you've drafted

Three things, in order:

1. Read it out loud. If you wouldn't say it that way in person, rewrite it. The most common drafting failure is writing in a register you'd never speak in.
2. Cut 20%. Almost every draft is too long. The shortest version that lands all three beats is the strongest version.
3. Send the recap. If it's a live conversation, send a 2-sentence Slack note within an hour summarizing the agreement. If it's a written message that's the whole exchange, that is the recap.

How Ren handles this

Ren reads the context from your Slack and Teams, identifies the moment that calls for one of these messages, and drafts the three beats in your voice — based on the methodology, with the specifics already filled in from what's actually happened. The drafts stay in Tier 1 — private to you. Only the outcomes — did the conversation happen, did it resolve — roll up.

It collapses the 90 minutes of internal stalling into 90 seconds of editing. That's the actual unlock.

Take the three-minute product tour to see Ren draft a hard message in real time, or talk with us about a deployment.