如何給出有幫助的回饋，而不是含糊的回饋

如何給出有幫助的回饋，而不是含糊的回饋

「Good job.」

對方笑了，你也笑了，大家都很客氣。然後什麼都沒改變，因為沒人知道哪裡好。

「Needs work.」

對方點點頭，你也點點頭，大家心裡都沒那麼客氣了。然後什麼都沒改變，因為沒人知道需要做什麼樣的功課。

含糊的回饋在當下感覺很輕鬆，因為它簡短又安全。但它也只留給聽者一團霧濛濛的小雲，而不是一張地圖。有幫助的回饋不必很長，但它應該讓對方看見：什麼要保留、什麼要改、下一步要做什麼。

為什麼會覺得尷尬

具體的回饋會比含糊的回饋更「暴露」自己。如果你說「Good job」，你不會在任何有趣的地方出錯；但如果你說「Your second example makes the argument easier to understand」，你就是在表態了。聽者可以提問，你可能得解釋自己的理由。

而這正是具體回饋有用的原因。

在英文裡，含糊的稱讚和含糊的批評往往聽起來友善，卻不完整。它們拿來快速打氣沒問題，但當有人正想進步時就不夠了。學生、同事或朋友需要的不只是你的整體感覺，他們需要證據。

最可靠的模式是：

觀察 + 影響 + 下一步。

觀察：你看到或聽到了什麼。

影響：它對讀者、聽者、客戶、隊友或情況造成了什麼。

下一步：什麼要保留、重複、調整、刪掉、增加，或檢查。

常見陷阱

陷阱一：沒有證據的稱讚。「Great work」讓人開心五秒，然後就消失了。

陷阱二：沒有方向的批評。「This needs work」也許是真的，但它沒告訴任何人該從哪裡開始。

陷阱三：把個人喜好假裝成回饋。「I don't like it」的用處，比不上「The informal tone may not fit this client」。

陷阱四：一次給太多意見。十個建議會讓聽者僵住，挑出最重要的一兩個就好。

陷阱五：自己動手改。全部重寫也許比較快，但對方學到的比較少。

更好的說法

用於稱讚：

  • "The opening example works well because it gives the reader a real situation right away."
  • "Your answer is strong because each reason has evidence."
  • "The chart is easy to read. The labels are short, and the colors are clear."
  • "This email has a good tone: polite, direct, and not too stiff."

用於批評：

  • "The main idea is clear, but the second paragraph repeats the first. You can cut it or add a new point."
  • "The report has useful data, but the conclusion does not explain what the team should do next."
  • "The design is clean, but the button is hard to find. Making it darker would help."
  • "The answer starts well, but it needs one example to support the claim."

用於褒貶並陳的回饋：

  • "Keep the structure. Revise the examples."
  • "The tone works. The length is the issue."
  • "The content is useful. The order needs adjusting."
  • "The first half is strong. The ending needs a clearer next step."

這些說法一樣很短，差別在於它們有指向性。

錯誤／更好／為什麼

錯誤 更好 為什麼
"Good job." "Good job explaining the problem before giving the solution. That order makes the email easy to follow." 點出什麼有效，以及為什麼有效。
"Needs work." "The answer needs one example after the main claim so the reader can see your point." 給出起點和下一步。
"I don't like the design." "The design may be hard to scan because the headings and body text look similar." 把喜好變成一個可觀察的問題。
"Make it better." "Make the first sentence more specific by naming the problem and the customer." 定義出「更好」到底是什麼意思。
"This is confusing." "The timeline is confusing because the dates are not in order. Try listing them from earliest to latest." 說明令人困惑的來源，以及該怎麼修。

迷你對話

A: Is my presentation okay?

B: The structure is strong. You explain the problem, then the solution, then the result. The part to revise is the ending. It stops suddenly, so add one final sentence telling the audience what you want them to remember.

A: So the ending needs a takeaway?

B: Exactly.

A: How was my practice answer?

B: You answered the question directly, which is good. The second reason needs support. Add one example from your own experience or from the passage.

A: Got it. Keep the answer, add evidence.

A: Any thoughts on this design?

B: The colors are calm and professional. The issue is the call-to-action button. It blends into the background, so people may miss it. Could you make it darker or move it higher?

A: That makes sense.

三段式回饋的習慣

當你不確定該說什麼時，把句子分成三塊來建構。

1. 觀察：「The second paragraph repeats the first.」

2. 影響：「That makes the essay feel slower.」

3. 下一步：「Cut the repeated sentence and use that space for an example.」

合起來：

「The second paragraph repeats the first, which makes the essay feel slower. Cut the repeated sentence and use that space for an example.」

再多舉幾個：

  • "The subject line only says 'Question,' so the teacher may not know what class this is for. Add the course name."
  • "The first example is funny, and it makes the tone friendly. Keep that."
  • "The instructions use three long paragraphs, so users may miss a step. Turn them into bullets."
  • "The apology sounds sincere. The next step is to explain what will change."

當你只有十秒鐘

有幫助的回饋不一定都得寫整段。如果你只是在草稿上留個快速評論，或是在會議之間講幾句，就用同一個模式的迷你版本。

  • "Keep this example. It makes the idea concrete."
  • "Cut this sentence. It repeats the line above."
  • "Add a deadline here so the reader knows when to reply."
  • "Move this point earlier. It explains why the topic matters."
  • "Change this word. It sounds more angry than you probably intend."

這些評論很短，但並不含糊。每一句都告訴對方該保留或改什麼，以及為什麼。這就是高效回饋和懶人回饋的差別：高效回饋之所以簡短，是因為它聚焦；懶人回饋之所以簡短，是因為它根本沒下功夫。

快速練習

用觀察、影響、下一步，把每一句含糊的評論變成有幫助的回饋。

  1. "Good job."
  2. "This is unclear."
  3. "The email is bad."
  4. "Nice presentation."
  5. "It needs more detail."

解答

  1. "Good job using a real example in the opening. It helps the reader understand the problem quickly."
  2. "The second sentence is unclear because it uses 'this' without naming what 'this' means. Replace it with the specific idea."
  3. "The email may sound too abrupt because it starts with the problem before greeting the customer. Add a brief thank-you first."
  4. "Nice presentation. The slides are easy to follow because each one has one main point."
  5. "The answer needs more detail after the first reason. Add one example that shows how the problem affects daily life."

重點回顧

  • 含糊的回饋容易說出口，卻很難拿來用。
  • 有幫助的回饋會指向證據。
  • 使用觀察 + 影響 + 下一步。
  • 具體的稱讚告訴人該重複什麼。
  • 具體的批評告訴人該改什麼。
  • 一個清楚的下一步，勝過十個零散的意見。

當回饋夠具體時，它就會變得比較不神祕、也比較不針對個人。聽者不必去猜你是什麼意思，他們可以直接把作品改好。