Feedback Should Not Be a Surprise
Introduction
Picture a scene that happens in workplaces around the world more often than anyone would like to admit. A team member walks into a performance discussion expecting it to be largely positive. They have not heard any major concerns from their leader during the period. Their one-on-ones have felt routine. The work has been going. They sit down across from their manager, ready to discuss the year. And then the manager begins to share concerns. Specific concerns. Patterns the manager has been noticing for months. Behaviors that have affected the team. Areas where the team member has fallen short. None of it has been mentioned before. All of it is being raised now, at once, in the formal performance discussion. The team member sits there, listening, with a feeling that builds slowly into something painful. They are not just hearing feedback. They are realizing that their manager has been holding all of this back for months, and they had no idea.
This experience is one of the most damaging things that can happen in a leader-team member relationship. It is not just that the feedback is hard to hear. Hard feedback is part of work. What makes it damaging is the surprise. The realization that the leader has been seeing things, judging them, accumulating concerns, and saying nothing. The understanding that the conversations the team member thought were honest were actually being curated. The recognition that what they took as silence was actually withheld feedback that was building toward this moment. The trust that the relationship had built collapses. Not because the feedback was wrong, but because the timing made it feel like a betrayal of the daily relationship.
And here is the most important truth about this scene. It is almost never the team member's fault. It is almost always the leader's. When feedback shows up as a surprise in a performance discussion, it means the leader did not give the feedback when they should have. They saw the pattern weeks or months ago and chose, consciously or not, to wait until the formal review to bring it up. They had a hundred smaller moments where they could have raised the concern in a low-stakes conversation and instead let those moments pass. They saved up feedback as if the performance discussion was the venue for it. And in doing so, they took something that could have been a series of normal coaching conversations and turned it into a single overwhelming event that the team member experiences as ambush rather than support.
The principle at the heart of this article is simple but profoundly demanding. Feedback should not be a surprise in a performance discussion. Nothing significant that you raise in a formal review should be the first time the team member is hearing about it. Every theme you discuss should have been raised in some form during the period. Every growth area should have been named earlier, in a smaller conversation, in language they recognize. Every concern should have been surfaced when it occurred, not stored for later delivery. The performance discussion should be the integration of conversations that have already happened, not the venue for conversations that should have happened months ago. When this principle is honored, the performance discussion becomes a natural extension of the working relationship. When it is violated, the performance discussion becomes a rupture in the relationship that takes years to repair.
This article explores why feedback should not be a surprise, what it really means to honor this principle, why so many leaders fail to honor it despite knowing better, what the principle requires in daily practice, and what to do when you realize you have accumulated feedback that should have been shared earlier. It is one of the most important principles in this entire chapter, because it is the principle that determines whether the performance discussion is experienced as support or as ambush. And the difference between those two experiences is the difference between a discussion that strengthens the relationship and one that damages it for years to come.
Simple Meaning: What Does It Mean That Feedback Should Not Be a Surprise?
Feedback should not be a surprise means that nothing significant raised in a formal performance discussion should be the first time the team member is hearing about it. Every important theme, growth area, concern, or recognition should have been touched on during the period in smaller, more immediate conversations. The formal review is the integration of those ongoing conversations into a larger picture, not the moment when feedback that has been held back finally gets delivered. When this principle is honored, the performance discussion becomes a continuation of an ongoing dialogue. When it is violated, the performance discussion becomes a delivery of accumulated judgment, and the team member feels ambushed rather than supported.
Feedback should not be a surprise is one of the most demanding and most important principles in the entire practice of performance management. It does not mean that the performance discussion is dull or that it contains nothing the team member has not heard before. It means that the substance of what is discussed has been part of the ongoing conversation in some form across the period, even if the integration into a larger picture is new. The team member should be able to recognize every theme. They should not be hearing about concerns they did not know existed. They should not be discovering patterns the leader has been quietly tracking for months. They should not be receiving recognition for work the leader never bothered to acknowledge at the time. The performance discussion should feel like a thoughtful summary of a relationship that has been honest throughout, not the moment when honesty finally arrives after months of polite silence. The leader who honors this principle is making a decision, dozens or hundreds of times across the period, to have small honest conversations rather than save things up. They are choosing the discomfort of in-the-moment feedback over the larger discomfort of accumulated feedback delivered all at once. They are recognizing that the team member's trust in the relationship depends on the consistency between what is said in daily life and what is said in formal moments. And they are protecting the performance discussion itself, allowing it to be a moment of integration and forward planning rather than a venue for surprises that should have been delivered weeks or months ago. This principle is hard. It demands that leaders give feedback when it is easier not to, raise concerns when raising them feels risky, acknowledge contributions when it would be simpler to take them for granted. But it is the foundation on which everything else in this chapter rests. Without it, no amount of preparation, technique, or framework can produce a performance discussion that actually feels like support to the person receiving it.
The principle of no-surprise feedback can be understood through four essential dimensions:
| Dimension | What It Means | Why It Matters | Example |
|---|---|---|---|
| Ongoing Honesty | You raise observations and concerns when they occur, not when the formal review arrives. | Honesty in the moment is what allows the performance discussion to be integration rather than revelation. | You name a pattern of late code reviews in a one-on-one in week three, not for the first time in the annual review. |
| Continuous Recognition | You acknowledge strong work as it happens, not only when it accumulates into the formal review. | Recognition delayed loses much of its power. Real-time recognition keeps it alive. | You send a short note the day after the team member handles a difficult customer call well, not save it for six months later. |
| Themes the Team Member Recognizes | Every theme you raise in the discussion is one the team member can recall having heard about before. | Recognition of themes signals that the conversation has been ongoing, not stored. | When you raise cross-team communication as a growth area, the team member nods because you have discussed it before in smaller moments. |
| Integration, Not Revelation | The performance discussion brings together what has been said in pieces into a larger coherent picture. | The discussion's value comes from seeing the pattern, not from learning isolated facts for the first time. | The discussion connects three earlier observations into a clear theme the team member has been working on across the period. |
Why Surprise Feedback Is So Damaging
To understand why this principle matters so much, it helps to look at what actually happens to a team member when they experience surprise feedback in a formal review. The harm is not abstract. It is specific, deep, and often long-lasting.
| What Surprise Feedback Produces | Why It Happens |
|---|---|
| Loss of Trust in the Daily Relationship | The team member realizes that the routine conversations they had with the leader were not as honest as they seemed. Everything in the relationship gets re-evaluated. |
| Inability to Engage With the Feedback | The team member is so focused on the shock of hearing it for the first time that they cannot process the content. The feedback fails to land. |
| Defensive Reaction | The mind protects itself by finding reasons the feedback is wrong, unfair, or untimely. The conversation becomes a debate rather than a dialogue. |
| A Sense of Betrayal | The team member feels that the leader held back information that would have helped them earlier. The relationship is wounded. |
| Damage to Confidence | The team member starts to wonder what else they do not know. Every interaction with the leader becomes suspect. |
| Missed Opportunity for Growth | If the feedback had been given when the pattern was first noticed, months of growth could have happened. That time is now lost. |
| Hollow Recognition | If positive feedback also shows up only in the review, it feels strategic rather than sincere. The team member discounts it. |
| Long-Term Caution | The team member learns not to trust the relationship fully. They become guarded in future conversations, which limits how deeply they can be coached. |
| Damage to Team Culture | The team member tells peers. Word spreads. Others in the team start to wonder what their own leader is holding back. |
| Increased Likelihood of Departure | Many people who leave teams cite the experience of surprise feedback in performance discussions as a moment that crystallized their decision. |
The damage from a single surprise feedback experience can take years to repair, and sometimes never fully heals. The team member may stay. They may continue to perform. But the texture of the relationship has changed permanently. They are no longer fully open. They are no longer fully trusting. They are watching for signs of what the leader might be withholding next. That is the cost of surprise feedback, and it is a cost that almost no leader intends to impose but that many leaders impose without realizing what they are doing.
Why Leaders End Up Saving Feedback Despite Knowing Better
Almost no leader sets out to ambush their team member. Most leaders, if asked, would say that feedback should be given in the moment. And yet many leaders consistently save feedback for performance discussions. Understanding why this happens is the first step to changing the pattern.
| Reason | What It Looks Like | What Honesty Reveals |
|---|---|---|
| Avoidance of Discomfort | The leader notices something but decides not to bring it up because the conversation would be hard. | The discomfort gets pushed to the future, where it accumulates and becomes worse. |
| Hope That It Will Improve on Its Own | The leader sees a pattern but waits to see if it corrects itself before raising it. | Most patterns do not correct without conversation. Waiting is usually waiting for a problem to grow. |
| Belief That Reviews Are the Right Venue | The leader treats performance discussions as the official place for serious feedback. | Reviews integrate ongoing feedback. They are not the primary venue for it. |
| Uncertainty About the Pattern | The leader is not sure if what they saw is a real pattern or an isolated moment. | Naming uncertainty in the moment is more honest than waiting for certainty that may not come. |
| Concern About Being Petty | The leader worries that raising small things will seem nitpicky. | Small things raised early stay small. Small things saved up become large. |
| Time Pressure | The leader is always busy. The right moment never seems to come. | The right moment will never come if you wait for it. You have to create it. |
| Concern About Damaging the Relationship | The leader fears that frequent feedback will strain the relationship. | The opposite is true. Withheld feedback is what strains relationships. Honest feedback strengthens them. |
| Cultural Norms | The leader operates in an environment where feedback is treated as a formal event, not a daily practice. | You can model a different norm in your own relationships even when the broader culture does not. |
| Difficulty Articulating the Concern Quickly | The leader cannot put the observation into words quickly enough to raise it in the moment. | Practicing the skill of in-the-moment feedback is what makes it possible. The skill develops with use. |
| Reliance on the Review as a Forcing Function | The leader knows the review is coming and uses it as a deadline to address things. | The review should not be a forcing function for honesty. Honesty should be ongoing. |
Recognizing your own pattern is the first step to changing it. Most leaders find that they fall into two or three of these reasons more often than the others. Naming which ones are yours, and watching for them in real time, is how the change begins.
What the Principle Requires in Daily Practice
Honoring the principle that feedback should not be a surprise is not something you do in the performance discussion itself. It is something you do across the months before the discussion through dozens of small choices. Here are the daily practices that make the principle real.
Practice 1: Notice and Raise in the Same Week
When you notice something significant, raise it within the same week, not the same quarter. A pattern observed on Tuesday should be acknowledged in a conversation by Friday at the latest. Even if you cannot fully articulate it yet, you can name what you noticed and ask the team member how they see it. The act of raising it early is more important than the polish of the language.
Practice 2: Use Regular One-on-Ones as Feedback Venues
Your weekly or biweekly one-on-ones are the natural venues for ongoing feedback. Build feedback into them as a regular practice, not just project updates. Ask yourself before each one-on-one: is there anything I have noticed since we last met that I should share? Then share it.
Practice 3: Catch Strong Work in Real Time
When you notice something done well, name it quickly. A short message the same day. A specific comment in a meeting. A mention in the next one-on-one. Real-time recognition keeps the relationship calibrated and ensures recognition does not get saved for the formal review.
Practice 4: Address Small Patterns Before They Grow
When you see the early signs of a pattern, raise it then, when it is small. "I noticed in the last two meetings that you raised concerns after the decision was made. I wanted to mention it because I am not sure if it is just timing or something else." Small patterns named early often resolve quickly. The same patterns left to grow can become defining issues by the time of the formal review.
Practice 5: Make Feedback a Normal Conversation
The more often you give feedback in a calm, low-stakes way, the more normal it becomes for both of you. When feedback is part of every other conversation, the formal review carries less weight, in the best sense. It is not the venue for hard truths. It is the integration of ongoing dialogue.
Practice 6: Ask for Feedback Often
Inviting feedback from the team member, regularly and specifically, normalizes the practice in both directions. When you ask and receive feedback well, you model what you want them to experience in receiving it. This makes ongoing feedback feel like a shared practice rather than a one-way activity you do to them.
Practice 7: Document Lightly Across the Period
Keep brief notes on observations as they occur. Not exhaustive records. Just enough to remember the moment, the behavior, and the impact. These notes serve two purposes. They support your preparation for the performance discussion. And they remind you of feedback you have committed to giving so you do not let it slip.
Practice 8: Check Your Avoidance
Periodically ask yourself: what feedback am I currently avoiding? What patterns am I noticing that I have not yet named? What recognition am I taking for granted? The honest answer is almost always something. Naming what you are avoiding is the first step to addressing it.
What Should Not Be in a Performance Discussion for the First Time
To make the principle concrete, here is a checklist of things that should not be raised for the first time in a performance discussion. Each of these, if it appears as a surprise, signals that something earlier in the relationship was missed.
| Should Not Be New | Why It Should Have Been Raised Earlier |
|---|---|
| Significant Concerns About Performance | If performance has been a concern for months, the team member should know. Surprise concerns destroy trust. |
| Patterns of Behavior That Have Affected the Team | Behavioral patterns should be named when they emerge, not stored for review delivery. |
| Important Feedback From Peers or Stakeholders | If peers have raised concerns, the team member should hear about them at the time, not learn months later that others have been talking about them. |
| Major Recognition for Significant Work | Recognition that comes only in the review feels delayed. The team member needed to hear it at the time the work happened. |
| Concerns About Specific Projects or Outcomes | Project concerns belong in the project debrief or shortly after, not stored for the next review. |
| Significant Shifts in Your Assessment | If your view of the team member has changed substantially, that shift should be discussed when it happens, not revealed in a review. |
| Concerns About Career Trajectory | Career-defining feedback deserves its own conversation, not a quick mention in a packed review. |
| Documentation of Issues You Plan to Reference | If you have been keeping a record of concerns to bring up in review, you have been preparing an ambush rather than coaching. |
| Comparisons to Peers | Any feedback that involves how the team member compares to others on the team should be handled with extreme care and earlier, not packaged into a review. |
| Surprise Ratings or Significant Changes in Rating | The team member should have a sense of how they are doing throughout the period. The rating should confirm what they already know, not blindside them. |
What If You Realize You Have Saved Feedback?
Reading this article, many leaders will recognize that they have accumulated feedback they should have shared earlier. That recognition is uncomfortable, but it is also the beginning of repair. Here is what to do when you realize you have stored feedback that the team member is going to be hearing for the first time.
Step 1: Acknowledge It to Yourself
Be honest with yourself about what has happened. You noticed something earlier and chose not to raise it. That choice was understandable but not ideal. Naming it clearly to yourself helps you do the right thing next.
Step 2: Do Not Wait for the Performance Discussion
If you have stored feedback and the review is weeks or months away, do not wait. Find a low-stakes moment in the next few days to begin the conversation. A one-on-one is a natural venue. Raise the topic with appropriate framing: "I have been noticing something I want to talk about. I should have raised it earlier, and I want to do that now."
Step 3: Own the Delay
When you raise the issue, acknowledge that you should have raised it earlier. "I noticed this a few weeks ago and I should have brought it up sooner. I am bringing it up now because it matters and I want us to work on it together." That ownership matters. It signals that you are not deflecting responsibility for the delay onto the team member.
Step 4: Give the Feedback Properly
Use the SBIC framework. Ground the feedback in specific examples. Describe behavior, not character. Name the impact. Open a conversation. All the disciplines from earlier chapters apply. The fact that you delayed does not change the structure of how to deliver the feedback well.
Step 5: Engage With Their Response
The team member may be frustrated that you waited. They may push back on the substance. They may share context you did not have. Engage with all of it. Listen. Adjust if warranted. Do not get defensive about the delay or the substance. Treat the conversation as the beginning of a dialogue, not the delivery of a verdict.
Step 6: Commit to Doing Better
Make a commitment, to yourself and to the team member, that you will raise things earlier in the future. Then keep that commitment. Trust is rebuilt through repeated demonstration, not through promises. Every time you raise something in the moment rather than waiting, you rebuild the trust that the delay damaged.
Step 7: Prepare the Performance Discussion Without the Surprise
Once you have raised the previously-stored feedback, it is no longer a surprise in the formal review. The review can integrate it appropriately, as part of the ongoing conversation you have now had. That is the right shape for the discussion. The work of raising it earlier is what protects the review from becoming an ambush.
What the Performance Discussion Should Sound Like When the Principle Is Honored
When the principle of no-surprise feedback is honored, the performance discussion has a different texture. Here is what it sounds like.
When Discussing Strengths
- Leader: "One of the themes I want to name across the year is how strong you have been at facilitating technical discussions. We talked about this in March when you ran the platform review, and again in July when you led the architecture conversation. Looking across the year, this has become one of your most valuable contributions."
- Team member: "Yes, I have been thinking about this too. I feel more confident in those moments than I did a year ago."
Notice how the team member recognizes the theme immediately because it has been part of the ongoing conversation. The review is integrating, not introducing.
When Discussing Growth Areas
- Leader: "The other theme I want to discuss is cross-team communication. We have talked about this in a few one-on-ones, particularly after the platform sync in May and the integration review in August. I want to step back and look at the pattern across the year."
- Team member: "Yes, I know what you are going to say. I have been working on it, and I know it is still an area where I can grow."
The team member is not surprised. They are not defensive. They are not blindsided. They are ready to engage because the topic has been part of their ongoing development conversation.
When the Team Member Reflects
- Team member: "What I most want to say about this year is that I have appreciated how honest our conversations have been. There has not been anything in this review that surprised me, which I take as a sign that we have been talking openly throughout. That has meant a lot to me."
- Leader: "Thank you. That is what I have been trying to do. I am glad it has felt that way."
This kind of reflection is the gift the principle gives back to the leader. When you have been honest throughout, the team member feels it, names it, and values it. That feedback is one of the most affirming experiences a leader can have, and it only comes when the principle has been honored.
Practical Workplace Scenario
Scenario
A team lead named Rohit had a strong relationship with a developer named Karuna. She had been on his team for eighteen months. Throughout the year, Rohit had noticed two things. First, Karuna had grown noticeably in her ability to lead technical reviews. Second, she had a recurring pattern of waiting too long before raising risks on projects, which had caused two delivery delays that could have been avoided if the risks had been surfaced earlier.
Rohit had not addressed either of these directly during the year. He had thought about mentioning the technical leadership growth, but he wanted to "save it for the review." He had noticed the risk-raising pattern but felt uncomfortable bringing it up because Karuna was generally a strong performer. The formal annual review was approaching. Rohit started preparing his notes and realized that the two most important things he wanted to discuss were both things Karuna had never heard from him directly.
Approach 1: Delivering Both as Surprises (What Could Have Happened)
Rohit could have walked into the review and delivered both pieces of feedback for the first time. He could have opened with the recognition of her technical leadership growth, which would have landed positively but with a hint of "why are you telling me this now?" He could have then introduced the risk-raising pattern, citing the two delays. Karuna would have been blindsided. Her face would have changed. She might have asked: "Why is this the first time I am hearing about this?" Rohit would have struggled to answer. The review would have ended awkwardly. Karuna would have left wondering what else Rohit had been holding back. The relationship would have taken months to recover, and Karuna might have started looking for a different role.
Approach 2: Raising Both Before the Review (What Actually Happened)
Rohit realized what he had been doing. He decided not to wait for the review. In the next one-on-one, he raised the risk-raising pattern. He said: "Karuna, I want to bring something up that I should have raised earlier. I have noticed in the last two projects that risks came up late in the cycle when they could have been surfaced earlier. Let me share specifically what I am seeing." He gave two specific examples. He named the impact: avoidable delays and pressure on the team in the final weeks. Then he asked her how she saw it.
Karuna was quiet for a moment. Then she said: "I had been wondering if you saw it. I was not sure whether to bring it up myself. I have been struggling with when to escalate risks because I do not want to seem like I am crying wolf. But I see what you mean about the delays." They had a real conversation about how to recognize the right moment to raise risks. Karuna left with a clearer sense of how to do it.
In another one-on-one a few weeks later, Rohit raised the technical leadership growth. He said: "I want to name something I have been seeing across the year. Your ability to lead technical reviews has grown substantially. The way you ran the platform review last month was different from how you ran reviews a year ago. I want you to know I see it, and it is a real strength." Karuna smiled. She said: "That means a lot. I have felt it but I was not sure if you saw it the same way."
What Happened in the Performance Discussion
By the time the formal review happened two months later, neither of these themes was a surprise. Rohit could integrate them into the larger picture of the year. The technical leadership growth had already been improving since the conversation. The risk-raising pattern had been improving since the conversation. The review became what it was meant to be: an integration of ongoing dialogue into a coherent picture, with forward planning for the next period. Karuna left the review saying: "This was the best performance discussion I have had. There was nothing in it that surprised me, and I feel clearer about where I am and where I am going than I have in a long time."
Result
Over the following year, Karuna's risk-raising became one of her noted strengths. Her technical leadership grew further. And her relationship with Rohit became one of the strongest on the team. Months later, she told a peer: "What I appreciate about Rohit is that he tells me what he sees as he sees it. I never have to wonder what he is thinking. That makes me trust him completely."
Learning
The difference between the two approaches was not the substance of the feedback. The feedback was the same in both cases. The difference was timing. By raising the feedback before the review, Rohit transformed what would have been an ambush into ongoing development. By the time the review happened, the conversation was natural, the feedback was integrated, and the trust between them was stronger rather than weaker. That is what the principle of no-surprise feedback produces when it is honored. And the cost of raising the feedback earlier was small. Two ten-minute conversations. The cost of waiting would have been a damaged relationship and a year of recovery. That ratio is why this principle is so important.
Feedback Should Not Be a Surprise Checklist
| Practice | Yes / No |
|---|---|
| I raise observations and concerns within the same week I notice them, not in the next review. | |
| I use my regular one-on-ones as venues for ongoing feedback, not just project updates. | |
| I acknowledge strong work in real time, not save it for the formal review. | |
| I address small patterns when they emerge, before they grow into defining issues. | |
| I make feedback a normal, low-stakes part of the working relationship. | |
| I ask for feedback from the team member regularly, not just give it. | |
| I check periodically for feedback I am avoiding and address it deliberately. | |
| When I realize I have saved feedback, I raise it before the next performance discussion. | |
| I own the delay honestly when I am raising feedback I should have brought up earlier. | |
| I structure my performance discussions as integration of ongoing dialogue, not delivery of stored content. | |
| I ensure no significant theme in a formal review is the first time the team member is hearing it. | |
| I evaluate my honesty in the relationship by asking: are there things I should be saying that I am not? |
Self-Reflection Questions
Use these questions to think honestly about your own practice of ongoing feedback.
- If I think about my last performance discussion, were there any moments where the team member seemed surprised by what I raised? What does that tell me?
- What feedback am I currently holding back from someone on my team that I should be raising soon?
- What is the most common reason I delay feedback? Avoidance? Uncertainty? Time pressure?
- How often do I treat the performance discussion as the venue for feedback that should have been shared earlier?
- If I imagined my team members preparing for their next performance discussion with me, would any of them be braced for what I might say? Or would they expect the conversation to be a natural continuation of what we have been discussing?
- What feedback have I given in real time that landed well? What made it possible for me to share it in the moment?
- What recognition have I been taking for granted that I should have named already?
- How does my pattern of feedback timing affect the trust in my relationships with my team?
- What is one specific feedback conversation I have been delaying that I commit to having within the next week?
- If my team members were asked whether they ever feel surprised by what comes up in our reviews, what would they honestly say?
Key Takeaways
- Feedback should not be a surprise in a performance discussion. Nothing significant raised in a formal review should be the first time the team member is hearing about it. The discussion is integration of ongoing dialogue, not delivery of stored content.
- Surprise feedback in a performance discussion is one of the most damaging experiences a team member can have. It produces loss of trust, defensive reaction, sense of betrayal, damage to confidence, hollow recognition, long-term caution, and often departure.
- Leaders end up saving feedback for many reasons: avoidance of discomfort, hope it will improve on its own, belief that reviews are the right venue, uncertainty about the pattern, concern about being petty, time pressure, fear of damaging the relationship, cultural norms, difficulty articulating quickly, and reliance on the review as a forcing function.
- Honoring the principle requires daily practices: notice and raise in the same week, use regular one-on-ones as feedback venues, catch strong work in real time, address small patterns before they grow, make feedback a normal conversation, ask for feedback often, document lightly across the period, and check your own avoidance regularly.
- The performance discussion should never be the first time the team member is hearing about significant concerns, behavioral patterns, peer feedback, major recognition, project concerns, shifts in your assessment, career-defining feedback, documented issues, peer comparisons, or surprise ratings.
- When you realize you have saved feedback, do not wait for the performance discussion. Raise it before the next review. Own the delay. Give the feedback properly. Engage with their response. Commit to doing better. The performance discussion can then integrate the feedback appropriately.
- When the principle is honored, the performance discussion sounds different. Themes are recognized, not introduced. Growth areas are familiar, not surprising. The team member often names the experience of ongoing honesty as a defining quality of the relationship.
- The cost of raising feedback earlier is almost always smaller than the cost of waiting. Two short conversations in the moment prevent a damaged relationship and a year of recovery. The math always favors raising things sooner.
- Trust in a leader-team member relationship is built not through what is said in formal reviews but through what is said in the spaces between them. The leader who honors this principle is choosing, dozens of times across a period, the small discomforts of in-the-moment honesty over the larger damage of saved-up surprises.
- This principle is one of the most demanding in the entire chapter, because it requires leaders to do something hard often rather than something easy occasionally. But it is also one of the most foundational. Without it, no amount of preparation or technique can make a performance discussion feel like support rather than ambush.
Conclusion
Feedback should not be a surprise. It is a simple sentence with enormous implications for how a leader engages with the people they lead. It demands that you raise observations when you see them, not when the calendar requires you to. It demands that you give recognition in real time, not save it for the formal review. It demands that you name patterns when they emerge, before they grow into defining issues. It demands that you make feedback a normal, low-stakes part of the working relationship rather than a high-stakes event tied to forms and ratings. And it demands that you do all of this consistently, across months and years, because the principle is honored not through a single dramatic conversation but through hundreds of small ones.
A leader who honors this principle creates relationships where trust is sustained because honesty is sustained. Their team members do not walk into performance discussions wondering what they might hear. They walk in knowing. They have been part of the conversation throughout. The review is not a venue for revelation. It is a venue for integration. The themes they hear are themes they recognize. The growth areas they discuss are areas they have already been working on. The recognition they receive confirms what they already sensed was being valued. And the forward planning that emerges from the discussion is grounded in a shared understanding that has been built over time, not assembled in the room. That is what the principle produces when it is lived. And it is something the people who experience it remember for the rest of their careers.
The most important lesson is this: The trust you build in the daily relationship is the trust the team member brings to the performance discussion. If you have been honest throughout, they will trust what you say in the review. If you have been holding things back, they will sense it the moment something significant gets raised for the first time. The principle of no-surprise feedback is the principle of being trustworthy in small moments so you can be heard in large ones. It is the principle of caring enough about the relationship to do the harder work of ongoing honesty rather than the easier work of saved-up delivery. It is the principle of recognizing that the performance discussion is only the visible tip of a much larger practice that happens across hundreds of smaller conversations. Honor this principle, and your performance discussions will become moments your team members value. Violate it, even unintentionally, and your performance discussions will become moments they survive. The choice is made not in the review room but in every week leading up to it. Make the choice that protects the trust. Raise what you see when you see it. Recognize what you value as you value it. Name patterns when they emerge. Engage in ongoing dialogue with the people you lead, not periodic delivery to them. And let the formal performance discussion be what it is meant to be: not a venue for honesty that should have happened earlier, but an integration of honesty that has been part of the relationship all along. That is what it means to honor this principle. That is what it means to be the kind of leader whose people trust them deeply. And that is what it means to create performance discussions that, year after year, become moments of value rather than moments of fear. Let your feedback never be a surprise. Let it always be an extension of the relationship. And let that consistency be one of the quiet, defining qualities of how you lead.