Activity: Rewrite Poor Feedback

Introduction

Reading about feedback is one thing. Practicing feedback is another. You can study every framework, internalize every principle, memorize every example, and still find that when the moment arrives, the words that come out of your mouth do not match the words you intended. That gap between knowing and doing is one of the most common challenges in leadership development, and it is rarely closed by reading more. It is closed by practice. Specifically, by the kind of practice where you take poor feedback, study why it fails, and rewrite it into feedback that actually works.

This article is different from the others in this chapter. It is not a conceptual exploration. It is a workshop. A hands-on, practical activity designed to build the muscle of giving good feedback by working with examples that almost every leader has either given or received at some point in their career. You will see poor feedback in its natural form, understand precisely why it fails, and walk through how to rewrite it using the SBIC framework, the principles of specificity, and the disciplines of neutral tone, factual grounding, and respect for the person on the receiving end.

The reason this activity matters is that poor feedback is rarely poor because the leader did not care. It is poor because the leader had not yet developed the habit of saying what they actually meant in a way the other person could actually use. Most poor feedback is full of vague phrases, character labels, hidden assumptions, and emotional residue. It says less than it intends to say. It causes more harm than the leader realized. And it leaves the person on the receiving end with no clear path forward. Rewriting poor feedback is how you train yourself to see those patterns in your own language before they leave your mouth.

You will work through several examples. Each one starts with poor feedback that sounds familiar. Each one is analyzed for what specifically makes it fail. Each one is rewritten using the SBIC framework, with the rewrite explained step by step so you can see how the transformation works. The goal is not for you to memorize the rewrites. It is for you to internalize the underlying pattern of transformation: from vague to specific, from character to behavior, from interpretation to observation, from verdict to conversation. Once you see the pattern enough times, you will start to see it in your own feedback, and that is when real change begins.

By the end of this activity, you should be able to look at any piece of feedback, including your own, and recognize quickly whether it is grounded in observable behavior, anchored in a specific situation, connected to clear impact, and open to genuine conversation. You should also be able to take feedback that fails on any of those dimensions and rewrite it into feedback that lands. That skill, more than any framework or principle, is what separates leaders whose feedback changes things from leaders whose feedback fades.

How to Use This Activity

Before diving into the examples, here is how to get the most from this workshop.

• Read the poor feedback first and pause. Before reading the analysis, try to identify on your own what is wrong with it. What is vague? What is interpretive? What is missing?
• Try rewriting it yourself. Take a moment to draft your own rewrite before reading the suggested version. This builds the active skill, not just the recognition.
• Compare your rewrite to the suggested one. Notice what you included that the suggestion did not, and what the suggestion captured that you missed. There is no single correct rewrite, but there are patterns that consistently make feedback stronger.
• Notice the underlying pattern. Each example will reveal one or more specific failure modes. Watch for those same patterns in feedback you have given or received in real situations.
• Practice with your own examples. After working through the examples in this article, take a piece of feedback you have given recently and run it through the same process. That is where the learning becomes personal.

The transformations you will study fall into recognizable categories. Here is a brief map of the most common ones you will see across the examples.

Example 1: The Vague Character Judgment

Poor Feedback

"You have been really negative in meetings lately. It is bringing the team down."

Why This Fails

• No situation. "In meetings lately" gives no specific moment. The person cannot recall what is being referenced.
• Character label. "Negative" describes who you are saying the person is, not what they did.
• Vague impact. "Bringing the team down" is unmeasurable and feels like accusation rather than observation.
• Hidden assumption. You are claiming to know the effect on the entire team without evidence.
• No conversation. It closes the door rather than opening one.

How to Rewrite It Using SBIC

Walk yourself through each step. What was the specific situation? Pick one. What was the observable behavior? Quote it if you can. What was the impact you actually saw, not just imagined? And how will you open the conversation?

Suggested Rewrite

"In yesterday's sprint planning meeting, when we were discussing the new feature, you said 'this is never going to work' twice during the discussion, and you raised concerns about three different aspects of the proposal in a row without offering alternatives. I noticed that the conversation lost momentum after that, and Anjali, who had been about to share her approach, stayed quiet for the rest of the meeting. I wanted to bring this up because the concerns you raise are often valuable, but the way they came across yesterday closed the discussion rather than sharpening it. I want to understand how you saw the meeting. What was going on for you?"

What Changed

• Situation is now specific: yesterday's sprint planning meeting, the new feature discussion.
• Behavior is observable: the exact words used and the pattern of raising concerns without alternatives.
• Impact is concrete: the conversation lost momentum, Anjali stayed quiet.
• Conversation opens the door: a real question invites the other person's perspective.
• Value preserved: the rewrite acknowledges that the person's concerns are usually valuable, which separates the behavior from the contribution.

Example 2: The Generic Praise

Poor Feedback

"Great job on the project. Really appreciate everything you did."

Why This Fails

• No situation. Which project? Which moment in it?
• No specific behavior. What did the person actually do well?
• No impact. What difference did it make?
• No conversation. The praise closes the moment instead of opening reflection.
• Risk of feeling hollow. Generic praise often feels routine, which undermines its value over time.

Suggested Rewrite

"I want to name something I saw during the migration project, specifically in the last two weeks of testing. When we hit the unexpected schema issue on the staging environment, you stayed late on Tuesday and Wednesday to map out the rollback path and then walked the team through it on Thursday morning. Because of that, we shipped on time without taking the kind of risk that usually shows up in a migration of this size. I also noticed that two of the junior engineers told me afterward that watching you handle that issue was the clearest learning moment of the project for them. I wanted you to know I saw the work and what it took. How did the last two weeks feel from your side?"

What Changed

• Situation is specific: the last two weeks of testing on the migration project.
• Behavior is named: staying late, mapping the rollback path, walking the team through it.
• Impact is concrete: shipped on time, junior engineers learned from it.
• Conversation invites reflection rather than closing the moment.
• Weight added: the appreciation now carries the same care that a difficult conversation would.

Example 3: The Hearsay Feedback

Poor Feedback

"People have been telling me that you are hard to work with. You need to improve your collaboration skills."

Why This Fails

• Hearsay. "People have been telling me" gives no specific source, no specific moment, no specific behavior.
• Character label. "Hard to work with" describes a quality, not an action.
• Generic prescription. "Improve your collaboration skills" does not point to anything actionable.
• Trust damage. The person will spend the rest of the conversation wondering who said what about them.
• No conversation. It delivers a verdict based on invisible evidence.

How to Rewrite It Using SBIC

The first discipline here is to anchor the feedback in something you have witnessed directly. If you cannot, you should not give the feedback yet. Either go observe directly, or speak to the people who made the comments and help them deliver the feedback themselves. Hearsay feedback is almost always worse than no feedback at all.

Suggested Rewrite

"I want to talk about something I have observed in the last two design reviews we both attended, the one on Monday and the one on Wednesday. In both reviews, when team members shared proposals, I noticed that you would point out problems with the approach before asking questions about why they had chosen it. On Monday, when Karan was presenting the data pipeline, you said 'that will not scale' within the first minute, and on Wednesday with Meena's caching design, you said 'I would not do it that way' before she had finished the overview. What I noticed in both meetings is that the discussion that followed was shorter than usual, and in both cases the presenters did not come back with revised proposals afterward. I want to be clear that your technical instincts are usually right, but the pattern of leading with the conclusion rather than the question is closing conversations that we need to keep open. I have heard similar feedback from two other people, and I want to be honest with you about that. I would like to hear how you have been experiencing those reviews."

What Changed

• Situation is grounded in two specific reviews the leader attended directly.
• Behavior is described with quoted phrases and the pattern across both meetings.
• Impact is concrete: shortened discussions, no revised proposals.
• Hearsay is handled responsibly. The leader mentions corroborating feedback but only after grounding the conversation in their own observation.
• Conversation opens space for the other person to share their experience.

Example 4: The Sandwich Without Substance

Poor Feedback

"You are doing a great job overall. There are just a few things you could work on, like being more proactive and communicating better. But honestly, you are doing really well. Keep it up."

Why This Fails

• Vague praise on both ends. Neither the opening nor the closing names anything specific.
• Vague critique in the middle. "Be more proactive" and "communicate better" point to nothing actionable.
• Mixed signal. The critique is wrapped so heavily that the person hears only the praise and walks out thinking everything is fine.
• Avoidance pattern. The sandwich is often a way for leaders to deliver hard messages without committing to them.
• No conversation. The format leaves no opening for real dialogue.

Suggested Rewrite

If both praise and constructive feedback are warranted, give them separately, with specificity and care. Do not blend them. Here is how the constructive part might be rewritten on its own.

"I want to talk about the cross-team sync we had last Thursday, specifically the part where the product team asked about our delivery timeline. When they asked when the integration would be ready, you said 'I will need to check and get back to you' for three different items in a row. The product manager followed up with me afterward asking whether the team had alignment on the timeline. I want to bring this up because the items they asked about were ones we had discussed in our planning two weeks earlier, and I think there is a real opportunity for you to come into those syncs more prepared with the information they need. How do you usually prepare for those meetings?"

What Changed

• Situation is specific: last Thursday's cross-team sync, the timeline question.
• Behavior is observable: the exact response repeated three times.
• Impact is concrete: the product manager followed up to check team alignment.
• "Be more proactive" is replaced with a specific request: come prepared with information for cross-team syncs.
• Conversation opens with a real question about how the person prepares, which invites collaboration on improvement.

Example 5: The Emotional Reaction Disguised as Feedback

Poor Feedback

"I cannot believe you sent that email without checking with me first. That was completely unprofessional."

Why This Fails

• Emotional opening. "I cannot believe you" puts the person on immediate defense.
• Character label. "Unprofessional" is a judgment, not a behavior.
• No specific impact. Why did the email matter? What happened because of it?
• Hidden assumption about intent. The framing assumes the person should have known to check.
• No conversation. It is a verdict, not an exchange.

Suggested Rewrite

"I want to talk about the email you sent to the platform team yesterday afternoon about the deadline change. The email included a new delivery date that I had not yet confirmed with the program management group, and within an hour, three of their leads forwarded it to me asking for clarification. The impact was that I spent the rest of the afternoon walking back the date with each of them, and the platform team is now uncertain whether to plan against the original date or the new one. I think there was a step missing in the process, and I want to understand what was happening when you decided to send it. Can you walk me through your thinking?"

What Changed

• Situation is anchored: yesterday's email to the platform team.
• Behavior is described factually: sending an email with an unconfirmed date.
• Impact is real and clear: forwards, follow-ups, uncertainty across teams.
• Emotion is acknowledged differently. The leader names the issue calmly without blaming, which keeps the conversation productive.
• Conversation invites understanding before judgment.

An Important Note on Timing

If the original poor feedback was given in the heat of the moment, the deeper fix is timing. When you are upset, wait. Feedback given in emotional reaction almost always lands worse than feedback given after you have steadied yourself. Twenty minutes of waiting often saves a relationship.

Example 6: The Stacked Feedback

Poor Feedback

"There is a lot I want to talk to you about. Your code reviews have been slow, your status updates are not detailed enough, you have been late to the last few standups, and I am worried about how you are coming across to the senior engineers. We need to fix all of this."

Why This Fails

• Too many issues at once. The person cannot focus on anything because everything is being raised.
• None of the items are anchored. Vague references to patterns without specific moments.
• No impact for any of them. The conversation lists problems without explaining why each one matters.
• "How you are coming across" introduces hearsay or assumption. What does that mean concretely?
• Overwhelming structure. The person hears "you are failing" rather than any actionable point.

How to Rewrite It

The first discipline here is to choose one issue at a time. If all four items are genuine, address them in separate conversations spread across time, not in a single overwhelming dump. Here is how one of them might be rewritten on its own.

Suggested Rewrite (Focused on One Item)

"I want to talk about code reviews, specifically the three pull requests that came to you last week. Karan's PR was open for four days before you reviewed it, Anjali's was open for five, and the platform team's integration PR was open for six. Because of that, all three of them missed their planned merge dates for last sprint, and Anjali had to rebase twice while she was waiting. I want to understand what was happening on your side last week. Was there something blocking you, or has the review load shifted in a way we should talk about?"

What Changed

• Focus. One issue, addressed clearly, instead of four blurred together.
• Situation is specific: three PRs from last week with measurable wait times.
• Behavior is observable: review delays of four, five, and six days.
• Impact is concrete: missed merge dates, rebasing costs.
• Conversation opens with curiosity about what may have been going on, rather than judgment.
• Other issues can be addressed separately in their own conversations, each with its own SBIC structure.

Example 7: The Backhanded Compliment

Poor Feedback

"You did pretty well in the presentation, considering you usually struggle with stakeholder meetings."

Why This Fails

• Praise undermined. The "considering" undoes the compliment entirely.
• Old judgment recycled. The phrase "you usually struggle" pulls past failures into a current win.
• No specific behavior. What did the person actually do well?
• No impact. What did the performance achieve?
• Net effect. The person walks away feeling worse despite the supposed praise.

Suggested Rewrite

"I want to name something specific from the stakeholder presentation this morning. When the CFO asked the hard question about cost overruns in the second half of the meeting, you paused, acknowledged the concern directly, walked them through the three drivers, and then named what we were doing about each one. The room shifted after that exchange. The CFO nodded and moved on, and the rest of the meeting felt different. I want you to know I saw that handling. It was clear, calm, and well-structured. How did that moment feel from your side?"

What Changed

• Situation is specific: the CFO's hard question in the second half of the meeting.
• Behavior is named: pausing, acknowledging, walking through drivers, naming actions.
• Impact is real: the CFO's response, the shift in the room.
• Praise stands on its own. No old judgment is dragged into the moment.
• Conversation invites reflection on the win, which helps the person internalize what they did well.

Example 8: The Anonymous Reference

Poor Feedback

"Some people on the team feel like you are not approachable. You should think about that."

Why This Fails

• Anonymous source. "Some people" creates a phantom accuser the person cannot engage with.
• Vague concept. "Approachable" is not behavior.
• No situation. When? Where? In what interaction?
• No impact. What has happened because of this?
• Closed exit. "Think about that" ends the conversation without giving the person anywhere useful to go.

The Deeper Issue

Anonymous third-party feedback is one of the most damaging forms of feedback a leader can give. It undermines trust, creates suspicion across the team, and gives the person no way to verify or act. The discipline here is to either witness the behavior yourself, or to encourage the people who raised the concern to share it directly with appropriate support.

Suggested Rewrite

"I want to share something I have noticed in the last few weeks across our one-on-ones and team meetings. In our last three one-on-ones, when team members asked you questions, you answered them quickly but did not ask follow-up questions, and you ended each conversation a few minutes early. In the team meeting on Wednesday, when Sneha asked about the testing approach, your response was 'we have already covered that,' which closed the discussion. I have also heard from two team members that they have been hesitant to bring questions to you because of how some of these exchanges have felt, and I want to be transparent with you about that. I want to understand how you have been experiencing your interactions with the team. What is your sense of how those conversations have been going?"

What Changed

• Situation is specific: one-on-ones over the last few weeks, a particular Wednesday meeting.
• Behavior is observable: short answers, no follow-ups, early endings, the exact phrase used.
• Impact is concrete: team members hesitating to bring questions.
• Anonymous concerns are handled with care: mentioned as additional input, but the conversation is grounded in the leader's direct observation.
• Conversation invites the person to share their own experience, which often reveals context the leader did not have.

Example 9: The "You Should" Lecture

Poor Feedback

"You should be more confident in meetings. You need to speak up more. You should not let people talk over you."

Why This Fails

• Prescription without observation. The leader is telling the person what to do without anchoring it in anything specific.
• "You should" framing. It positions the leader as instructor rather than collaborator.
• Confidence is internal. Telling someone to "be more confident" is not actionable.
• No conversation. The format leaves no space for the person to share what is actually going on for them.
• Risk of patronizing. The advice may not match what the person actually needs, especially if the leader has not asked.

Suggested Rewrite

"I want to talk about the architecture review yesterday. During the discussion about the data layer, I noticed that you had a strong opinion early on, you mentioned to me before the meeting that you thought the proposed approach had a scaling issue, but in the meeting itself, when Vikram pushed back on a different point, you did not bring it up. The decision ended up going in a direction that I think will hit the exact issue you were worried about. I want to understand what happened. Was the moment hard to find, or was something else going on? I want to figure out how to make sure your perspective lands in those rooms, because it is valuable and we are losing it."

What Changed

• Situation is specific: yesterday's architecture review, the data layer discussion.
• Behavior is observable: a strong pre-meeting opinion that did not surface in the meeting.
• Impact is real: a decision that will likely hit the issue the person foresaw.
• "Be more confident" is replaced with a real question about what made the moment hard.
• Conversation treats the person as a partner in solving the problem, not a student to be corrected.
• Tone values the person's contribution rather than diminishing them.

Example 10: The "Always" and "Never"

Poor Feedback

"You never take initiative. You always wait for me to tell you what to do."

Why This Fails

• Absolute language. "Always" and "never" are almost always inaccurate and invite immediate disagreement.
• Character framing. The feedback describes who the person is rather than what they did.
• No situation. No specific moment to engage with.
• No impact. Why does this matter?
• Defensiveness guaranteed. The person will spend the conversation finding counterexamples.

Suggested Rewrite

"I want to talk about how we have been working together over the last few sprints. In the last three sprint plannings, I noticed that the items you took on were the ones I specifically suggested, and when there were open items that needed someone to step in, I had to assign them rather than seeing them picked up. In the same period, I also noticed that when I asked what you wanted to work on, the answer was usually 'whatever you need.' The impact I see is that I am making more decisions about your work than I would like to, and I think you have more ownership in you than is showing up in these moments. I want to understand what is going on. Is the work itself unclear, is something blocking you, or is this a pattern you would also like to shift?"

What Changed

• "Always" and "never" are gone. The rewrite describes a specific time window with specific patterns.
• Situation is anchored: the last three sprint plannings.
• Behavior is observable: which items were taken, what was said when asked.
• Impact is honest: the leader is making more decisions than they want to.
• Conversation opens space for the person to share what may be going on.
• Trust preserved. The leader expresses belief in the person's ownership, which keeps the conversation generative.

Patterns to Internalize from These Examples

Across all ten examples, several patterns appear again and again. These are the patterns to internalize, because they will help you transform almost any piece of feedback into something stronger.

Your Turn: Try Rewriting These Yourself

Below are several pieces of poor feedback for you to practice rewriting on your own. For each one, do the following. Identify what makes it fail. Imagine a specific situation that the feedback could have been anchored in. Describe the behavior in observable terms. Name the impact clearly. And open a conversation with a real question. Then compare your rewrite to the principles from earlier examples and notice what improved.

Practice Feedback to Rewrite

1. "You are not a team player."
2. "You are doing fine."
3. "You are too aggressive in your emails."
4. "You lack attention to detail."
5. "You are not strategic enough."
6. "You are great. No notes."
7. "You take feedback poorly."
8. "You are not visible enough to senior leadership."
9. "You need to be more of a leader."
10. "You should care more about quality."

For each one, write your rewrite before reading any commentary you might find elsewhere. The act of constructing the rewrite is what builds the skill. Reading other rewrites can refine your sense of pattern, but only your own writing trains the muscle that matters in the actual moment of giving feedback.

A Workplace Scenario: Rewriting in Real Time

Scenario

A team lead named Devika was preparing for a quarterly check-in with one of her direct reports, an engineer named Arjun. She had drafted some notes on what she wanted to address. Reading them back, she realized they sounded exactly like the poor feedback patterns she had been working to move away from. Her draft included phrases like: "Arjun has been disengaged this quarter," "He needs to take more ownership," and "I am hearing concerns about his collaboration." She paused before the meeting and decided to rewrite her notes using the patterns from this workshop.

Approach 1: Delivering the Draft as Written (What Could Have Happened)

Had Devika walked into the meeting with her original draft, the conversation would likely have gone poorly. Arjun would have heard character labels, not behaviors. He would have asked who had raised concerns and felt undermined by the anonymous reference. He would have defended himself against "disengaged" and "lacking ownership" because those words feel like attacks rather than observations. The meeting would have ended without resolution, and the relationship would have taken a hit.

Approach 2: Rewriting Before the Meeting (What Actually Happened)

Devika sat with her draft for twenty minutes and rewrote it. "Disengaged" became "in our last four one-on-ones, you had no agenda items prepared, and when I asked what you were working on, the answers were brief." "Needs to take more ownership" became "in the last sprint planning, when we discussed who would pick up the migration work, you waited for me to assign it rather than volunteering." "Hearing concerns about collaboration" became "in the design review last Wednesday, I noticed you did not respond to two questions from junior engineers, and I want to talk about what was going on for you in that meeting."

By the time she walked into the meeting, her notes were grounded in specific situations, observable behaviors, real impact, and questions she actually wanted answers to.

How the Meeting Went

The conversation went very differently from how it would have with the original draft. Arjun listened to each specific observation without becoming defensive. When Devika asked what had been going on, Arjun shared that he had been managing a difficult personal situation at home for the last six weeks and had been struggling to bring his full energy to work. He had not told anyone because he did not want it to affect how he was seen. Devika listened. She thanked him for telling her. They agreed on adjusted expectations for the next two weeks, talked about what kind of support might help, and made a plan to revisit in a month.

Result

The conversation that Devika had feared would be hard turned into one of the most meaningful conversations she had ever had with Arjun. Because the feedback was grounded in specific behavior rather than character judgment, Arjun was able to share the real context without feeling attacked. Because the conversation was open rather than a verdict, the relationship grew stronger. And within six weeks, Arjun's engagement in his work had visibly returned, with Devika's support and a shifted approach to his workload during a hard season.

Learning

The skill of rewriting poor feedback is not just for written notes. It is for the way you think about feedback in your own head before you ever open your mouth. The patterns you internalize through this kind of practice become the patterns your brain reaches for in real moments. And that is when the work pays off, not in the rewrite itself, but in the way it changes how you talk to people in the moments that matter.

Rewriting Feedback Checklist

Self-Reflection Questions

Use these questions to think about your own patterns when giving feedback.

1. What character labels do I find myself reaching for most often? What specific behaviors usually sit behind them?
2. When did I last give feedback that I now realize was vague or character-based? How would I rewrite it?
3. Do I tend to stack multiple issues into one conversation, or do I focus on one at a time?
4. How often do I give feedback in emotional reaction rather than after I have steadied myself?
5. What is my default opening when delivering hard feedback? Is it grounded in observation or in judgment?
6. Do I treat positive feedback with the same care and specificity I bring to constructive feedback?
7. When I use "always" or "never," what am I really trying to communicate? How could I say it more accurately?
8. Have I ever given feedback based on hearsay? How could I have grounded it in my own observation instead?
9. What is one piece of feedback I am preparing to give in the next week? How would I rewrite it using the patterns from this workshop?
10. What pattern from this activity do I most want to internalize before my next feedback conversation?

Key Takeaways

• Poor feedback is rarely poor because the leader did not care. It is poor because the leader had not yet developed the habit of saying what they actually meant in a way the other person could actually use.
• Rewriting poor feedback is one of the most effective ways to build the muscle of giving good feedback. It trains you to see the patterns that fail and to construct the patterns that work.
• Common failure modes include vague generalizations, character judgments, missing impact, absolute language, hearsay, stacked issues, generic praise, sandwich structures, emotional reactions disguised as feedback, and one-way verdicts.
• The transformation from poor feedback to strong feedback follows a consistent pattern: anchor in a specific situation, describe observable behavior, name concrete impact, and open the conversation with a genuine question.
• Replace adjectives with verbs. Replace absolutes with specific time frames. Replace hearsay with direct observation. Replace prescriptions with questions. Replace blended sandwiches with separate, clear moments.
• Strong feedback preserves the dignity of the person on the receiving end. It treats them as capable of growth, not as a problem to be processed.
• Focus on one issue at a time. Stacking multiple concerns overwhelms the conversation and reduces the chance of any of them leading to real change.
• Wait when emotional. Feedback given in reaction almost always lands worse than feedback given after the leader has steadied themselves.
• Apply the same care to positive feedback that you apply to constructive feedback. Generic praise is a missed opportunity. Specific recognition is what people remember.
• The real value of this activity is not memorizing the rewrites. It is internalizing the underlying patterns so that in the real moment of giving feedback, your brain reaches naturally for specificity, observation, impact, and conversation rather than for judgment, hearsay, and verdict.

Conclusion

Rewriting poor feedback is one of the most practical and powerful exercises a leader can do. It bridges the gap between knowing what good feedback looks like and being able to produce it under pressure. It trains your eye to spot the failure modes that show up most often in your own language. It builds the habit of constructing feedback that is grounded, specific, and respectful. And over time, it transforms how you think about feedback long before you open your mouth, which is exactly where the change has to happen.

A leader who has done enough of this kind of practice walks into feedback conversations differently. They do not scramble for words. They do not reach for character labels. They do not hide behind vague phrases. They have internalized the pattern of saying what they saw, when they saw it, what it caused, and what they would like to understand from the other person. That pattern becomes natural, not rehearsed. It becomes the way they think, not just the way they speak. And the conversations that follow are clearer, kinder, and more likely to lead to real change.

The most important lesson is this: Feedback is a skill, and like every other skill, it is built through deliberate practice. You do not get better at feedback by giving more of it. You get better at feedback by reflecting on what you said, noticing where it fell short, and rewriting it into something stronger. That rewriting can happen on paper, in your head before a meeting, or in real time as you catch yourself reaching for a character word and choose a specific behavior instead. The leaders whose feedback consistently lands well are not the ones who were born with the skill. They are the ones who treated every conversation as a chance to practice. They noticed when their feedback was vague and asked themselves how to make it specific. They noticed when their feedback was character-based and asked themselves what behavior they had actually seen. They noticed when their feedback was a verdict and asked themselves how to open a conversation instead. Over years, those small acts of noticing and rewriting became a way of thinking, and that way of thinking became the foundation of their leadership. You can build the same foundation. Start with the examples in this article. Then start with your own feedback. Take something you said recently and ask yourself how you would say it differently now. Write it out. Compare the versions. Notice what improved. Then bring that awareness into the next conversation, and the next, and the one after that. Slowly, almost without noticing, you will become the kind of leader whose feedback people actually want to receive. Not because the words are perfect, but because the words tell the truth in a way that respects everyone in the room. That is the skill this activity is designed to build. And it is one of the most valuable skills a leader can carry through a career.