MetaCyberGuru English Academy
Your goal for Feedback: Giving It and Taking It
Feedback: Giving It and Taking It: Peer to peer: “The recommendation appears before the evidence, so I found the logic difficult to follow. By the end, you should be able to give correction without accusation and receive criticism without collapse or defensiveness.
Turn a label into evidence
Rewrite “You are careless with client details.” Name the observable event, its effect and the standard for the next version. Do not add praise merely to make the correction less uncomfortable.
Use observation, effect, request: Feedback: Giving It and Taking It
| Move | Example | Purpose |
|---|---|---|
| Observation | The last two client summaries used the old account name. | Describe checkable work, not personality |
| Effect | The client may think we have not updated their records. | Explain why the issue matters |
| Request | Please verify the account header against the CRM before sending the next summary. | Define the repair and future standard |
| Support | I can add the account check to the review template. | Remove an avoidable process obstacle |
Feedback changes with the relationship
Peer to peer: “The recommendation appears before the evidence, so I found the logic difficult to follow. Could we move the two findings above it?”
Manager to report: “The client update omitted the revised date. That left the customer without a decision point. Future updates need the date, owner and next checkpoint in the opening section.”
Upward feedback: “When priorities change during the meeting without a written recap, I am unsure which task to stop. Could we confirm the final order before we close?”
Receive criticism in five moves
- Pause before explaining your intention.
- Ask for one example if the comment is broad.
- Restate the issue to check that you understood it.
- Separate what you accept, what needs evidence and what may be outside scope.
- Agree the next action and when it will be checked.
You do not have to agree with every interpretation. You do need to understand the evidence before rejecting it.
Intention and effect can both be true
“I intended to be concise” and “the message sounded abrupt” can both be accurate. Treating intention as a complete defence blocks improvement. Treating effect as proof of bad intent is equally unhelpful.
A productive repair sounds like this: “I intended to keep the update short, but I can see that removing the reason made the request sound abrupt. I will add the reason and the next step.”
Feedback habits that reduce trust
- Using always, never or everyone when you have one example.
- Giving a character judgment instead of a behavioural observation.
- Hiding the correction between unrelated compliments.
- Correcting a person publicly when a private conversation would work.
- Receiving feedback as an order to accept every opinion or extra scope.
Practise both sides of the conversation: Feedback: Giving It and Taking It
- Give feedback on a report with unsupported conclusions.
- Give upward feedback about priorities changing without confirmation.
- Respond to “Your emails are confusing” by asking for a useful example.
- Separate a client’s genuine quality concern from a new feature request.
- Give specific positive feedback that the recipient can repeat.
Check the evidence and the next action
Record the conversation from both chairs: Feedback: Giving It and Taking It
Write a two-role feedback conversation, then speak both roles. In the second recording, remove one accusation from the giver and one defensive explanation from the receiver.
Reuse one earlier workplace decision: Feedback: Giving It and Taking It
Start with The last two client summaries used the old account name.
. Add one relevant move from the previous lesson, such as a clear owner, deadline, condition or reason. Remove it if it does not help the recipient act.
Ask for one concrete standard
In a safe learning or work context, replace one vague comment with: “Could you show me an example?” or “What would a successful next version do differently?”
Feedback should reduce uncertainty: Feedback: Giving It and Taking It
Describe observable work, explain the effect and request a specific change. When receiving feedback, clarify the evidence, separate intention from effect and agree the next testable action.
Save your place
Your progress stays in this browser on this device.
Share this page
Share this page with the people who will use it next.
Discussion
No comments yet. Add the first useful question or observation.
You must log in to post a comment.