Prepare a Constructive Feedback Conversation with a Teammate Using SBI

Get a ready-to-say feedback script with an opening line, a situation-behavior-impact statement, one clear request, and calm replies to defensive reactions.

You getOpening line, situation-Behavior-Impact script and the request

Prompt

Prompt
You are an experienced team lead who coaches people to give direct, fair feedback.

I need to give constructive feedback to a teammate. First, ask me these numbered questions in one message and wait for my answers:
1. What happened? Describe one or two specific recent moments.
2. What effect did it have on the work, the team or you?
3. What do you want them to do differently?
4. What is our working relationship, and how do they usually react to criticism?

Then write my script. Rules:
- Describe behavior as a camera would record it; no labels like "lazy" or "careless".
- Each impact names a concrete cost: hours, rework, a missed deadline or extra load on someone.
- The request is one specific action with a time frame, asked as a question.
- Keep the opening under 60 words so it sounds spoken, not written.
- Replies to defensive reactions acknowledge first, then return to the request without arguing.

Output format:
1. Opening line
2. Situation-Behavior-Impact script
3. The request
4. Table: Reaction | What they might say | What I say back (4 rows)
5. Close and follow-up plan

End with one line on assumptions you made or anything missing that could weaken the conversation.

Example output

Example for: a product designer giving feedback to a peer developer, Marco, who shipped two UI changes without design review.

1. Opening line

"Marco, do you have 15 minutes? I want to talk about how design review fit into the last two releases. I think we can fix it quickly, and I'd like your view too."

2. Situation-Behavior-Impact script
  • Situation: In the March 4 and March 18 releases.
  • Behavior: The checkout button restyle and the new filter panel were merged without a design review ticket or a Figma link in the pull request.
  • Impact: QA flagged 6 spacing and color issues after launch. I spent about 5 hours on fixes, and Priya had to push the onboarding update back two days to make room for them.
3. The request

"Starting with the next sprint, could you add me as a reviewer on any pull request that changes visible UI, and give me one working day to respond before merging?"

4. Defensive reactions
ReactionWhat they might sayWhat I say back
Deadline pressure"We had to ship. There wasn't time.""That makes sense, the deadlines were tight. That's why I'm offering a one-day turnaround. Would that work for you?"
Minimizing"They were tiny changes.""Some were small, I agree. Together they still cost about 5 hours of rework. Can we include anything visible, even small?"
Blame shift"You're hard to reach.""Fair point, and I'll work on that. If I don't reply within a day, go ahead and merge. Does that seem fair?"
Silence(no response, short nods)"I've done most of the talking. How does this look from your side?"
5. Close and follow-up plan
  • Repeat the agreement in one sentence: "So, I'm a reviewer on UI pull requests, with a one-day window."
  • Thank him for hearing it out.
  • Send a two-line Slack summary the same day.
  • Check in after the next release (around April 1) to see whether the process works for both of you.

Assumption: you have no authority over Marco's work, so the request is phrased as an agreement between peers. If his manager set the deadlines, you may need to raise the review step with that manager as well.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Asking about the teammate's usual reaction to criticism lets the model write replies for the pushback you are most likely to get.
  • The camera-test rule removes labels, so the feedback is about actions and is harder to argue with.
  • A single time-bound request asked as a question gives the conversation a clear goal and a way to check progress later.

Use before a 1:1 where you need to raise a problem with a peer or report. Have one or two concrete examples ready. Works in ChatGPT, Claude or Gemini; rehearse the script aloud afterward.

Common edits

  • Change the output for written feedback, such as a Slack message or email, instead of a spoken conversation.
  • Add a fifth question about something the teammate does well, so the script can open with genuine credit.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Productivity