feedback-mastery

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Feedback Conversations

反馈对话

Overview

概述

This skill provides frameworks for navigating difficult workplace conversations and delivering effective feedback. Whether you're addressing performance issues, resolving conflicts, or giving constructive feedback, these structured approaches lead to better outcomes.

Core insight: Research shows that employees who approach difficult conversations with preparation and a clear framework are 60% more likely to reach a positive resolution than those who engage without a plan.

本技能提供了应对职场棘手对话、给出有效反馈的框架。无论你是处理绩效问题、解决冲突还是提供建设性反馈，这些结构化方法都能带来更好的结果。

核心见解： 研究表明，与毫无准备就参与对话的员工相比，提前准备并使用清晰框架应对棘手对话的员工达成积极结果的可能性高出60%。

When to Use This Skill

适用场景

Use this skill when:

Preparing to give feedback to a colleague or direct report
Addressing performance issues or missed expectations
Navigating conflict between team members
Having 1:1 conversations about sensitive topics
Receiving feedback and wanting to respond constructively
Managing expectations with stakeholders

Keywords: feedback, difficult conversation, 1:1, one-on-one, performance, conflict, expectations, behavior, confrontation

在以下场景中使用本技能：

准备向同事或直属下属提供反馈时
处理绩效问题或未达预期的情况时
解决团队成员之间的冲突时
就敏感话题进行一对一（1:1）对话时
收到反馈并希望做出建设性回应时
与利益相关方管理预期时

关键词：反馈、棘手对话、1:1、一对一、绩效、冲突、预期、行为、对峙

Core Frameworks

核心框架

The Preparation-Delivery-Follow-up Model

准备-传达-跟进模型

A three-part structure for difficult conversations:

Phase	Focus	Key Questions
Preparation	Understand the issue, define goals, manage emotions	What's the problem? What outcome do I want? Am I calm?
Delivery	Open neutrally, use facts not blame, encourage dialogue	How do I start? What evidence do I have? How do I involve them?
Follow-up	Document actions, set check-ins, provide support	What did we agree to? When will we check in? How do I support?

用于应对棘手对话的三部分结构：

阶段	重点	关键问题
准备	明确问题、定义目标、管理情绪	问题是什么？我想要什么结果？我是否冷静？
传达	中立开场、基于事实而非指责、鼓励对话	我该如何开场？我有哪些证据？如何让对方参与进来？
跟进	记录行动项、设定跟进时间、提供支持	我们达成了哪些共识？何时进行跟进？我该如何提供支持？

The SBI Feedback Model

SBI反馈模型

Situation-Behavior-Impact (SBI) structures feedback to be specific, objective, and actionable:

Component	Description	Example
Situation	Describe the specific context	"During yesterday's code review..."
Behavior	State the observable action (not interpretation)	"...you interrupted Sarah three times while she was explaining her approach..."
Impact	Explain the effect on team/project/person	"...which made her hesitate to share ideas and slowed down our discussion."

Why it works: SBI removes assumptions and focuses on observable facts, reducing defensiveness.

情境-行为-影响（SBI） 框架让反馈更具体、客观且具有可操作性：

组成部分	说明	示例
情境	描述具体背景	"在昨天的代码评审中..."
行为	陈述可观察到的行动（而非主观解读）	"...你在Sarah解释她的方案时打断了她三次..."
影响	说明对团队/项目/个人的影响	"...这让她不敢再分享想法，拖慢了我们的讨论进度。"

为何有效：SBI消除了主观假设，聚焦于可观察的事实，减少了对方的抵触情绪。

Preparation Phase

准备阶段

Step 1: Understand the Issue

步骤1：明确问题

Ask yourself:

What exactly is the problem? (Be specific, not vague)
How does it impact the team, project, or company?
Have I gathered all relevant facts?
Is this a pattern or a one-time event?

自问：

具体问题是什么？（要具体，不要模糊）
它对团队、项目或公司有什么影响？
我是否收集了所有相关事实？
这是偶发事件还是模式化问题？

Step 2: Define Your Goals

步骤2：定义目标

Before the conversation, clarify what you're seeking:

Goal Type	Example
Behavior change	"I want them to submit code reviews on time"
Mutual understanding	"I want to understand what's blocking them"
Expectation setting	"I want to clarify what 'done' means for features"
Problem solving	"I want to find a solution together"

Tip: Use if-then statements to clarify stakes:

"If this behavior continues, then the project timeline will suffer, leading to missed deliverables."

对话前，明确你的诉求：

目标类型	示例
行为改变	"我希望他们能按时提交代码评审"
相互理解	"我想了解他们遇到的障碍"
设定预期	"我想明确功能的‘完成’标准"
解决问题	"我想和他们一起找到解决方案"

小贴士：用如果-那么语句明确影响：

"如果这种行为持续下去，项目进度会受影响，导致交付延期。"

Step 3: Manage Your Emotions

步骤3：管理情绪

High emotional intensity reduces cognitive processing by 30%. Before the conversation:

Am I calm and in control?
Have I separated facts from personal frustrations?
Have I considered their perspective?
Can I present this without accusation?

Reframing technique:

Accusatory	Constructive
"You always miss deadlines and it slows everyone down"	"I've noticed some recent delays and want to understand any challenges you're facing"
"You never test your code properly"	"I've seen a few bugs slip through recently. Let's talk about our testing process"

高强度情绪会让认知处理能力下降30%。对话前：

我是否冷静且情绪可控？
我是否区分了事实和个人不满？
我是否考虑了对方的视角？
我能否不带指责地表达这件事？

重构技巧：

指责式表达	建设性表达
"你总是错过截止日期，拖慢了所有人的进度"	"我注意到最近出现了一些延期情况，想了解你是否遇到了什么挑战"
"你从不认真测试代码"	"我注意到最近有几个bug漏测了，我们来聊聊测试流程的问题"

Delivery Phase

传达阶段

The Three-Step Delivery Formula

三步传达公式

Open with neutrality and intent
Present the issue using facts, not blame
Encourage dialogue and solutions

以中立和明确意图开场
基于事实而非指责陈述问题
鼓励对话并共同寻找解决方案

Opening Lines That Work

有效的开场话术

Context	Opening
General	"I want to talk about something important to our team's success, and I'd love to hear your perspective."
Performance	"I've noticed some patterns I'd like to discuss. My goal is to support you, not criticize."
Conflict	"I sense there might be some tension, and I'd like to understand what's happening from your side."
Expectations	"I want to make sure we're aligned on expectations. Can we talk through how this project is going?"

场景	开场语
通用	"我想和你聊聊对团队成功很重要的一件事，也想听听你的看法。"
绩效问题	"我注意到一些模式化的情况，想和你谈谈。我的目标是支持你，而非批评。"
冲突问题	"我感觉团队里可能有些紧张情绪，想从你的角度了解情况。"
预期对齐	"我想确保我们对预期的理解一致，能聊聊这个项目的进展吗？"

Facts, Not Blame

基于事实，而非指责

Blaming	Factual
"You're not committed to this project"	"I've noticed your updates have been brief in our last three meetings. Is something affecting your workload?"
"You don't care about code quality"	"This PR had 12 bugs caught in QA. Let's talk about what happened and how we can improve"
"You're always late"	"The standup started at 9:00 and you joined at 9:15 the last three days. What's going on?"

Key principles:

Use specific examples, not generalizations ("always," "never")
Stick to observable behaviors, not assumptions about motives
Focus on impact, not character

指责式表达	事实性表达
"你对这个项目不够投入"	"我注意到在最近三次会议中，你的更新都很简短。是不是工作量方面有什么影响因素？"
"你不在乎代码质量"	"这个PR在QA环节发现了12个bug。我们来聊聊问题出在哪，以及如何改进。"
"你总是迟到"	"最近三天的站会都是9点开始，你9点15分才加入。发生什么事了吗？"

核心原则：

使用具体例子，而非概括性表述（如“总是”“从不”）
聚焦可观察的行为，而非对动机的假设
关注影响，而非个人特质

Encouraging Dialogue

鼓励对话

After stating your observation, shift to collaboration:

Situation	Dialogue Prompt
Understanding barriers	"What's been challenging about this?"
Seeking their view	"How do you see the situation?"
Finding solutions	"What would help you succeed here?"
Checking alignment	"Does this match your understanding of what happened?"

陈述你的观察后，转向协作：

场景	对话引导语
了解障碍	"这件事对你来说最大的挑战是什么？"
询问对方视角	"你是怎么看待这个情况的？"
寻找解决方案	"什么能帮你在这件事上做得更好？"
确认对齐	"这和你对事件的理解一致吗？"

Follow-up Phase

跟进阶段

Even successful conversations need follow-through to create lasting change.

即使是成功的对话，也需要后续跟进才能带来持久改变。

Follow-up Checklist

跟进清单

Document agreed-upon action items - What specifically will change?
Set check-in dates - When will you revisit this?
Provide ongoing support - How will you help them succeed?
Celebrate progress - Recognize improvements when they happen

记录达成一致的行动项 - 具体要改变什么？
设定跟进日期 - 何时回顾进展？
提供持续支持 - 如何帮助他们成功？
认可进步 - 当出现改进时及时肯定

Sample Follow-up Message

跟进消息示例

markdown

Hi [Name],

Thanks for the conversation yesterday. I appreciated your openness.

**What we agreed to:**
- [Action item 1] - [Timeline]
- [Action item 2] - [Timeline]

**Check-in:** Let's reconnect [date] to see how things are going.

I'm here if you need any support. Thanks for working through this with me.

Best,
[Your name]

markdown

嗨 [姓名]，

感谢你昨天的坦诚沟通。

**我们达成的共识：**
- [行动项1] - [时间节点]
- [行动项2] - [时间节点]

**跟进安排**：我们在[日期]再沟通一次，看看进展如何。

如果需要任何支持，随时找我。感谢你和我一起解决这个问题。

祝好，
[你的姓名]

SBI Examples for Software Teams

软件团队的SBI示例

Positive Feedback

正面反馈

Code Review:

Situation: "During Tuesday's code review for the authentication module..." Behavior: "...you provided detailed comments on potential security vulnerabilities and suggested efficient fixes..." Impact: "...which strengthened our security posture and saved the team hours of debugging later."

Collaboration:

Situation: "In yesterday's architecture discussion..." Behavior: "...you asked clarifying questions and built on others' ideas instead of pushing your own solution..." Impact: "...which helped us reach consensus faster and made everyone feel heard."

代码评审：

情境： "在周二的认证模块代码评审中..." 行为： "...你针对潜在安全漏洞给出了详细评论，并建议了高效的修复方案..." 影响： "...这强化了我们的安全防护，为团队节省了后续数小时的调试时间。"

协作表现：

情境： "在昨天的架构讨论中..." 行为： "...你没有强行推行自己的方案，而是提出澄清问题并基于他人的想法进行拓展..." 影响： "...这帮助我们更快达成共识，也让每个人都觉得自己的意见被重视。"

Constructive Feedback

建设性反馈

Missed Deadlines:

Situation: "When we were finalizing the API deployment last Thursday..." Behavior: "...your testing results came in two hours after our agreed cutoff..." Impact: "...which delayed the release, risked our SLA, and caused the QA team to work overtime."

Meeting Behavior:

Situation: "In our sprint planning yesterday..." Behavior: "...you were on your phone for most of the discussion and didn't contribute when we asked for estimates..." Impact: "...which left the team without your expertise on the backend stories and made others feel their time wasn't valued."

For more examples: See

references/feedback-sbi-model.md

错过截止日期：

情境： "上周四我们完成API部署时..." 行为： "...你的测试结果比约定时间晚了两小时提交..." 影响： "...这导致发布延期，违反了我们的SLA，还让QA团队不得不加班。"

会议表现：

情境： "在昨天的 sprint 规划会上..." 行为： "...你大部分时间都在看手机，当我们询问估算时也没有参与..." 影响： "...这让团队缺少了你对后端需求的专业意见，也让其他人觉得自己的时间没有被尊重。"

更多示例：请查看

references/feedback-sbi-model.md

Common Difficult Scenarios

常见棘手场景

Scenario: Performance Issue

场景：绩效问题

Situation: A developer consistently delivers code with bugs.

Approach:

Prepare: Gather specific examples (PRs, bug counts, timelines)
Deliver: "I've noticed [X bugs in last Y PRs]. I want to understand what's happening and how I can support you."
Explore: Ask about workload, clarity of requirements, testing confidence
Collaborate: "What would help you feel more confident about code quality?"
Follow-up: Check in after agreed changes, recognize improvements

情况：某开发人员交付的代码持续存在bug。

应对方法：

准备：收集具体例子（PR、bug数量、时间线）
传达："我注意到[最近Y个PR中有X个bug]。我想了解情况，看看能如何支持你。"
探究：询问工作量、需求清晰度、测试信心等问题
协作："什么能让你对代码质量更有信心？"
跟进：在约定的改变实施后进行检查，认可改进

Scenario: Conflict Between Team Members

场景：团队成员间的冲突

Situation: Two engineers disagree on technical approach and it's affecting the team.

Approach:

Meet separately first: Understand each perspective
Find common ground: What do they both want? (Working product, good code, etc.)
Facilitate together: Focus on facts and trade-offs, not personalities
Establish decision process: How will the team decide when there's disagreement?
Follow-up: Check that the solution is working

情况：两位工程师在技术方案上存在分歧，影响了团队。

应对方法：

先分别沟通：了解每个人的视角
寻找共同点：他们的共同目标是什么？（可用的产品、优质代码等）
共同沟通：聚焦事实和取舍，而非个人性格
建立决策流程：当出现分歧时，团队如何做决策？
跟进：检查解决方案是否有效

Scenario: Unrealistic Expectations

场景：不切实际的预期

Situation: Leadership wants a feature in half the time needed.

Approach:

Prepare: Data on similar past work, breakdown of required tasks
Deliver: "I want to make sure we're aligned on what's realistic. Here's what I'm seeing..."
Present trade-offs: "We can hit that date if we [reduce scope/add people/accept risk]"
Collaborate: "What's most important here - the date or the full feature set?"
Document: Get agreement in writing to avoid future misalignment

For detailed scripts: See

references/difficult-conversation-scripts.md

情况：领导层要求在一半的时间内完成某个功能。

应对方法：

准备：收集过往类似工作的数据、任务分解信息
传达："我想确保我们对实际可行的方案达成共识。这是我目前了解到的情况..."
呈现取舍："如果要在那个日期交付，我们需要[缩减范围/增加人手/接受风险]"
协作："这里最关键的是什么——交付日期还是完整功能？"
记录：将共识以书面形式确认，避免未来出现误解

详细脚本：请查看

references/difficult-conversation-scripts.md

Receiving Feedback Well

如何妥善接收反馈

When you're on the receiving end:

当你是反馈接收方时：

During the Conversation

对话中

Listen fully - Don't prepare your defense while they're talking
Ask clarifying questions - "Can you give me a specific example?"
Paraphrase to confirm - "So what you're saying is..."
Acknowledge impact - Even if intent was different: "I can see how that affected you"
Don't get defensive - Thank them for raising it

认真倾听：不要在对方说话时准备辩解
提出澄清问题："你能给我一个具体例子吗？"
** paraphrase确认理解**："所以你的意思是..."
认可影响：即使初衷不同，也要说："我能理解这对你造成了影响"
不要抵触：感谢对方提出问题

After the Conversation

对话后

Reflect honestly - Is there truth in the feedback?
Identify actions - What will you do differently?
Follow up - Let them know what you're changing
Ask for ongoing feedback - Show you're committed to growth

诚实反思：反馈中有合理之处吗？
确定行动：你会做出哪些改变？
跟进：让对方知道你的改变
请求持续反馈：表明你致力于成长

Quick Reference: Difficult Conversation Checklist

快速参考：棘手对话清单

Before

对话前

During

对话中

After

对话后

Companion Resources

配套资源

```
references/feedback-sbi-model.md
```
- Full SBI framework with more examples

references/difficult-conversation-scripts.md

- Opening lines and responses

```
references/expectation-alignment.md
```
- Managing stakeholder expectations

```
references/feedback-sbi-model.md
```
- 完整SBI框架及更多示例

references/difficult-conversation-scripts.md

- 开场话术与回应示例

```
references/expectation-alignment.md
```
- 利益相关方预期管理

feedback-mastery

Original

Translation

Feedback Conversations

反馈对话

Overview

概述

When to Use This Skill

适用场景

Core Frameworks

核心框架

The Preparation-Delivery-Follow-up Model

准备-传达-跟进模型

The SBI Feedback Model

SBI反馈模型

Preparation Phase

准备阶段

Step 1: Understand the Issue

步骤1：明确问题

Step 2: Define Your Goals

步骤2：定义目标

Step 3: Manage Your Emotions

步骤3：管理情绪

Delivery Phase

传达阶段

The Three-Step Delivery Formula

三步传达公式

Opening Lines That Work

有效的开场话术

Facts, Not Blame

基于事实，而非指责

Encouraging Dialogue

鼓励对话

Follow-up Phase

跟进阶段

Follow-up Checklist

跟进清单

Sample Follow-up Message

跟进消息示例

SBI Examples for Software Teams

软件团队的SBI示例

Positive Feedback

正面反馈

Constructive Feedback

建设性反馈

Common Difficult Scenarios

常见棘手场景

Scenario: Performance Issue

场景：绩效问题

Scenario: Conflict Between Team Members

场景：团队成员间的冲突

Scenario: Unrealistic Expectations

场景：不切实际的预期

Receiving Feedback Well

如何妥善接收反馈

During the Conversation

对话中

After the Conversation

对话后

Quick Reference: Difficult Conversation Checklist

快速参考：棘手对话清单

Before

对话前

During

对话中

After

对话后

Companion Resources

配套资源

Recommended Reading

推荐阅读