Felix Bauer·
Got the same hard feedback written three ways so I could pick the framing that fit the person
Generates actionable, psychologically safe feedback using the SBI and Feedforward frameworks.
Constructive Feedback Framework Engine
You are an organizational psychologist specializing in high-performance feedback cultures. I need to deliver feedback to {{recipient_name}}, a {{recipient_role}}, about {{feedback_topic}}. The context is: {{context_description}}. My relationship to them is: {{relationship}}. Create: (1) Three versions of this feedback using different frameworks: a) SBI (Situation-Behavior-Impact), b) Feedforward (future-focused), c) Radical Candor (caring personally + challenging directly); (2) An opening script that establishes psychological safety, (3) Specific, observable examples instead of generalizations, (4) The impact of the behavior on team/project outcomes, (5) 2-3 actionable suggestions for improvement framed collaboratively, (6) A follow-up plan with check-in dates, (7) Anticipated reactions and how to respond to each, (8) A written summary that can be shared after the conversation. Keep the tone respectful, specific, and growth-oriented.
Ergebnisse
# Feedback — Tom (Product Manager) on repeatedly missing async update deadlines
Context: Tom skipped the written weekly update three sprints running, leaving engineering guessing on priorities. You are his peer lead.
## Opening (establishes safety)
"Tom, I value how you protect deep-work time, and I want us to keep shipping well together. I noticed something about our weekly updates I'd like to talk through — is now a good moment?"
## Version A — SBI
- **Situation:** the last three Friday updates.
- **Behavior:** the written priority summary didn't go out.
- **Impact:** engineering started Monday unsure what to pick up, and two tickets were duplicated.
## Version B — Feedforward
"Going forward, what would help you get the Friday summary out reliably — a template, a 15-min calendar hold, or me drafting the first version with you once?"
## Version C — Radical Candor
"I care about your success here, so I'll be direct: missing the update is starting to cost the team trust. I don't think it reflects your intent, and I want to fix the system, not blame you."
## Suggestions (collaborative)
1. A 4-line template (Done / Next / Risks / Asks).
2. A recurring Friday 16:30 reminder.
3. We pair on the first one next week.
## Follow-up
Check in after two sprints. **Anticipated reactions:** defensiveness → reaffirm intent; agreement → lock the template today. Written summary shared after the chat.
Modell: Claude Sonnet 4
26 Likes8 SavesScore: 15
1 Kommentar
Chloe Adams·
This project management prompt is going straight into my system.