The pressure point in giving feedback to a high performer is usually not the whole event; it is the short moment when attention narrows and a default response takes over. The purpose here is turning observations into information someone can use. Useful feedback reduces ambiguity about what happened and what to do differently next time.
Case: when giving feedback to a high performer starts to drift
Imagine the situation begins with reasonable preparation. Then a long preamble that hides the message appears. The old pattern is using vague words such as professional or proactive without examples, which tends to create extra cost before the person even notices the pattern. The first correction is connect the behavior to its impact.
The second turning point comes when too many examples at once. At that point, use agree on one future behavior. A short line such as “What did you notice from your side?” gives the behavior a concrete form without turning the conversation into a script recital.
Three turning points to rehearse
- Before pressure rises: connect the behavior to its impact. Decide what evidence will count as a good attempt.
- At the first signal: if you notice a long preamble that hides the message, use agree on one future behavior before adding speed or explanation.
- After a wobble: use separate evaluation from development and return to the objective instead of trying to erase the mistake.
What the better version looks like
The improved attempt is not necessarily calmer. It is more structured: the person notices a long preamble that hides the message, uses connect the behavior to its impact, and checks whether the receiver can state the next step. If that evidence improves, the behavior is becoming more reliable even if the situation still feels demanding.
Why the obvious fixes can fail
Giving feedback only when something is wrong can feel sensible because it reduces discomfort quickly, but in giving feedback to a high performer it often trades short-term relief for weaker execution. The same is true of confusing disagreement with lack of understanding. A better rule is to change one controllable behavior and then review the result.
After-action review
| Attempt | Signal | Action | Evidence | Adjustment |
|---|---|---|---|---|
| 1 | a long preamble that hides the message | connect the behavior to its impact | whether the receiver can state the next step | Change one variable |
| 2 | too many examples at once | agree on one future behavior | evidence of behavior change in the next comparable situation | Keep what helped |
| 3 | What became predictable? | Repeat the reliable move | amount of rework after the feedback | Increase difficulty only if stable |
A deeper walkthrough
Before the next instance of giving feedback to a high performer, write the outcome you want on one line and identify the first moment when the situation usually becomes harder. Prepare agree on one future behavior before the event. If too many examples at once appears, do not wait for the final problem; use use examples close to the event immediately and keep the next move small. If the first move does not work, shift to separate evaluation from development rather than repeating the same response with more intensity.
What to learn from the attempt
Afterward, compare what you predicted with what actually happened. Look specifically at time from event to feedback and whether the receiver can state the next step. If the result was mixed, decide whether the issue was timing, wording, environment or difficulty. This prevents a common error: abandoning a useful method because it was used too late or in a form that was too complicated for the real situation.
Three questions to take into the situation
Before the next attempt, ask: What must be true by the end? What is the earliest sign that the situation is drifting? What one behavior would protect the most important outcome? These questions keep the plan practical. After the attempt, answer the same questions again using what actually happened rather than what you hoped would happen. The comparison is useful because it reveals whether the difficulty came from preparation, timing, information, another person’s response, or the behavior you chose. Applied to giving feedback to a high performer, keep the review tied to feedback rather than turning it into a broad judgment about ability. Write one observation from the attempt, one decision you would repeat, and one change for the next comparable situation. If you cannot name those three items, the review is probably still too general. The purpose is to leave the situation with a usable next experiment, not a longer explanation of why it was difficult.
Questions people ask
What is the earliest sign I should watch for in giving feedback to a high performer?
Use an observable signal rather than a mood label. For this article, start with a long preamble that hides the message. It appears early enough to support a different choice.
What should I measure after giving feedback to a high performer?
Choose evidence close to execution. Track whether the receiver can state the next step and evidence of behavior change in the next comparable situation for three comparable attempts before deciding whether the approach is working.
What if I forget the technique in the moment?
Shorten it. Put connect the behavior to its impact into the environment before the event and use one sentence such as “What did you notice from your side?” rather than trying to remember a full framework.