I Have to Give Difficult Feedback to Someone I Really Like - How to Address Performance or Behavior Issues Clearly and Humanely Without Turning Honesty into Coldness or Fondness into Avoidance ebook

Cover

I Have to Give Difficult Feedback to Someone I Really Like

How to Address Performance or Behavior Issues Clearly and Humanely Without Turning Honesty into Coldness or Fondness into Avoidance

Max Paradox

PROBLEM? RELAX. YOU'VE GOT THIS!

ISBN: 978-83-8483-770-2

ALL-IN Rafał Płonkowski

Table of contents

Title page

INTRO

Chapter 1 - When Liking Someone Starts Editing the Truth

Chapter 2 - The Facts Are Manageable. The Story in Your Head Is Not.

Chapter 3 - So Much Kindness That Nobody Understood the Problem

Chapter 4 - When Honesty Puts on a Suit of Armor and Frightens Everyone

Chapter 5 - The Perfect Moment Is Permanently Unavailable

Chapter 6 - The Rescue Habit: When Helping Someone Keeps the Problem Alive

Chapter 7 - The Office Feedback Committee That Forgot to Invite the Person Involved

Chapter 8 - When Charm Hijacks the Conversation

Chapter 9 - One Page, No Ambush: Preparing for the Conversation That Matters

Chapter 10 - From the First Sentence to the Final Agreement: Having the Conversation for Real

Chapter 11 - When Someone Is Trying Their Hardest and the Results Still Aren't Good Enough

Chapter 12 - You're Not Their Boss: Giving Feedback When You Have No Authority to Give Orders

Chapter 13 - When the Problem Has a Bigger Office: Giving Feedback to a Boss You Respect

Chapter 14 - The Feedback Boomerang: What If They're Right About You?

Chapter 15 - The Promise Was Excellent. The Improvement Has Gone Missing.

Chapter 16 - When Loyalty Wants You to Look the Other Way

Chapter 17 - The Feedback Was Honest. Now Your Favorite Colleague Calls You "Dear Manager."

Chapter 18 - When the Meeting Ends, the Improvement Has to Keep Working

Chapter 19 - The Quiet Warning Signs That You're Avoiding the Truth Again

Chapter 20 - You Can Like Them and Still Tell the Truth: No Script Required

Landmarks

Cover

Title page

Table of contents

Start of content

INTRO

At 9:06 on Tuesday morning, your favorite colleague walks into the office carrying a box of homemade cinnamon rolls. They are still warm. People gather around, compliments begin flying, and someone declares that the company should immediately promote this person to Head of Workplace Happiness. Unfortunately, you have scheduled a difficult conversation with the same colleague at ten. For the third time this month, their financial summaries have contained errors that other people had to discover and correct before sending them to clients. The mistakes are beginning to affect deadlines and confidence in the team's work. You know you need to address the problem. You also know that criticizing someone who has just supplied the office with excellent pastries feels like a particularly unpleasant violation of the social contract.

The problem is not the cinnamon rolls. The problem is that you genuinely like this person. You enjoy working together, appreciate their generosity, and remember the occasions when they helped you through difficult projects. You know they have talents that extend well beyond their ability to persuade an entire department to abandon breakfast plans. When you imagine discussing their mistakes, you are not simply preparing to correct a work issue. You are imagining their disappointment, the awkwardness afterward, and the possibility that a comfortable relationship will suddenly become formal and distant. You can already hear yourself saying, "It's really nothing major," even though you specifically arranged the meeting because it has become major.

This is one of the strangest difficulties in professional relationships. We often find it easier to be direct with people whose approval matters less to us. With someone we genuinely value, every sentence seems to carry additional emotional consequences. We worry that criticism will sound like rejection, that a reasonable expectation will seem unkind, or that the person will interpret one disappointing result as a judgment of their entire character. Instead of focusing on what needs to change, we become preoccupied with preventing an uncomfortable reaction. We begin editing our message before we have even delivered it. By the time the conversation happens, the central point may have disappeared beneath so many qualifications that it requires specialist equipment to locate.

Sometimes we respond by becoming excessively gentle. We talk about opportunities, potential, alignment, and the possibility of perhaps considering a slightly different approach at some unspecified future date. We surround the problem with compliments until the other person reasonably concludes that the meeting was largely positive. Other times, frustration builds until we decide that kindness has failed and firmness must mean becoming cold. We adopt an unfamiliar voice, sit unusually straight, and deliver our message with the warmth of an automated parking fine. Neither approach is particularly helpful. One conceals the seriousness of the issue; the other makes the relationship itself feel threatened. Both distract from the practical question of what happened and what needs to happen differently.

Avoiding the conversation may seem compassionate, especially when the other person is already working hard. Yet silence has consequences that are easy to overlook because they rarely arrive all at once. A colleague who does not know that their work is causing difficulties cannot make an informed decision about changing it. Teammates may quietly compensate, managers may become increasingly frustrated, and small problems can gradually influence important judgments about performance. Eventually, someone who believed everything was going reasonably well discovers that other people have been concerned for months. That revelation can damage trust far more than a timely, respectful conversation would have. Protecting someone's feelings today is not necessarily the same as treating them fairly over time.

The starting point is to separate a person's worth from a specific result or behavior. Someone can be generous, intelligent, hardworking, and genuinely wonderful to have around while still making mistakes that require attention. You do not need to withdraw admiration in order to identify a problem. Consider the difference between saying, "You're becoming careless," and explaining that two recent client summaries contained figures that did not match the approved source data, requiring colleagues to redo the calculations. The first statement invites an argument about personal character. The second creates an opportunity to examine a specific problem. It is possible to communicate seriousness without humiliation, and respect without pretending that the consequences do not matter.

Of course, the person receiving feedback may have information you lack. Perhaps the source data changed without notification. Perhaps two managers gave conflicting instructions, or the amount of work has grown beyond what one person can reasonably complete. Sometimes there really is a performance issue; sometimes the system surrounding the employee is producing failures that will continue regardless of how many motivational conversations you organize. Good feedback therefore requires curiosity as well as clarity. You should know enough to explain your concern while remaining willing to revise your understanding when relevant facts emerge. A difficult conversation should not be a courtroom in which you have already written the verdict and invited the defendant along for decorative purposes.

The challenge becomes even more complicated when professional authority enters the relationship. A manager has responsibilities that friendship cannot erase. A colleague working at the same level may need to discuss shared commitments without having the power to issue instructions. Giving feedback to a respected boss requires another kind of judgment because the balance of influence is different. The underlying principles remain useful, but circumstances matter. So do reasonable workloads, existing agreements, the consequences of errors, and the other person's genuine ability to make the requested change. No clever choice of words can compensate for an impossible expectation. And serious concerns involving safety, harassment, or misconduct may require appropriate formal procedures rather than an ordinary developmental conversation.

This book is about learning to make those distinctions without losing your humanity. You will learn how to identify the issue worth discussing, prepare without scripting every possible reply, explain your expectations in understandable language, and respond when the conversation does not go according to plan. There will be disagreement, embarrassment, defensiveness, uncomfortable silences, and occasionally someone who agrees so enthusiastically that you suspect they would promise to reorganize the solar system if it ended the meeting faster. The aim is not to eliminate every difficult emotion. It is to keep those emotions from preventing a useful exchange of information and a realistic decision about what happens next.

You will also encounter an inconvenient truth: delivering feedback well does not guarantee that the other person will welcome it, accept your judgment, or change their behavior. People retain their own perspectives, limitations, choices, and emotions. You can communicate honestly, listen carefully, and offer appropriate support, but you cannot manufacture agreement. Sometimes progress takes time. Sometimes your initial interpretation turns out to be incomplete. Sometimes the necessary outcome is a firmer boundary or a difficult organizational decision. Respectful communication is important precisely because the outcome cannot always be controlled. It allows you to act fairly without pretending that every uncomfortable situation has a cheerful ending.

The good news is that you do not need to become a naturally confrontational person. You do not need to memorize impressive management terminology or develop the ability to deliver criticism while maintaining a facial expression suitable for a corporate security photograph. You can remain warm, approachable, and occasionally funny. You can admit that a conversation is difficult while still saying what needs to be said. You can value the person sitting opposite you without abandoning the standards that protect your colleagues and your work. Over time, difficult feedback can become less of a dramatic event and more of an ordinary, if occasionally uncomfortable, part of treating people honestly.

So think about the person whose work or behavior you have been meaning to discuss. Perhaps you have been waiting for the perfect moment, hoping the issue resolves itself, or rehearsing a conversation so often that the imaginary version has become more familiar than the real one. You do not need to stop liking that person. You do not need to make them feel small. You need to give the relationship enough respect to include the truth, and give the other person a fair opportunity to respond to it.

And if they happen to bring cinnamon rolls to the meeting, enjoy one. Just remember that excellent baking is not an approved alternative to checking the numbers.

Chapter 1 - When Liking Someone Starts Editing the Truth

Daniel knows exactly what he needs to say to Nina. He has known for eleven days. Unfortunately, he also knows that Nina is one of the best people on his team, which has somehow transformed a straightforward performance concern into an emotional negotiation involving loyalty, gratitude, and the possible destruction of civilization as represented by their friendly working relationship. Every time he prepares to speak to her, another reason to postpone appears. She has just finished a demanding project. She is helping a new colleague settle in. She seems especially cheerful today, and interrupting that happiness feels unnecessarily cruel. By Thursday, Daniel has become so skilled at finding reasons not to speak that he could probably turn postponement into a consulting business.

Nina coordinates onboarding for new business customers. She is knowledgeable, patient, and exceptionally good at making people feel welcome. When a client struggles with a complicated requirement, she stays involved until the problem is resolved. When someone on the team needs help, she rarely refuses. Her customer satisfaction feedback is consistently positive. Yet there is an increasingly serious weakness in her work: she often completes important onboarding steps without recording the details in the shared system. The customer receives excellent personal attention, but when another employee needs to continue the process, crucial information is missing. Colleagues must contact Nina, repeat questions, or reconstruct decisions from scattered messages. Daniel has explained the importance of documenting handovers during team meetings, but he has never addressed the recurring problem directly with her.

The difficulty is not that Daniel lacks management experience. He can challenge suppliers, reject unrealistic demands, and negotiate unpleasant contractual conditions without losing sleep. But Nina once volunteered to cover a difficult assignment when the team was seriously understaffed. She has supported his decisions during tense projects and defended colleagues who were unfairly criticized. Those memories matter to him. Unfortunately, he has begun treating them as reasons to overlook present difficulties. In his mind, telling Nina that her handovers are inadequate feels strangely similar to announcing that everything good she has done has been forgotten. He knows this is unreasonable. Knowing that something is unreasonable, however, does not automatically stop the human brain from treating it as an emergency.

This is the first important complication in giving difficult feedback to someone you genuinely like: you may start confusing criticism of one behavior with rejection of the entire person. You know their strengths, understand their intentions, and have witnessed their contributions. Because those positive qualities are real, a negative observation seems almost disloyal. Yet people do not come in two varieties, wonderful and disappointing. A capable, generous employee can repeatedly neglect an important responsibility. A loyal colleague can make decisions that create difficulties for others. A person can deserve appreciation for previous achievements and still need to change something today. Those statements can comfortably coexist, provided you stop trying to issue a single verdict on the person's overall worth.

There is another complication, and it has very little to do with the employee's actual behavior. You may be afraid of losing your position in the relationship. Until now, you have been the approachable manager, the supportive colleague, or the trusted partner who understands. You like being that person. When you imagine delivering unwelcome feedback, you picture the relationship changing. Perhaps the other person will stop sharing ideas so freely. Perhaps casual conversations will become awkward. Perhaps they will begin treating you as an authority figure rather than someone they enjoy working with. The possibility feels like a personal loss, even when the feedback itself is entirely justified. You are no longer deciding only whether the issue deserves attention. You are deciding whether you can tolerate being temporarily less popular.

This desire to remain the good person can quietly interfere with professional judgment. Many people enter management determined not to resemble a former supervisor who criticized constantly, ignored personal circumstances, or treated employees as interchangeable parts. That determination can produce genuinely humane leadership. But it can also develop into an unspoken promise that nobody working for you will ever feel uncomfortable because of something you say. Such a promise is impossible to keep without abandoning important responsibilities. You can control whether you communicate respectfully, prepare properly, and listen fairly. You cannot guarantee that a reasonable criticism will feel pleasant. A manager who measures kindness exclusively by the absence of disappointment may eventually discover that every important standard has become optional.

Meanwhile, the cost of your silence rarely falls on you alone. Daniel's other team members have begun keeping private notes about Nina's accounts because they cannot rely on the shared system. One colleague spends additional time gathering information before covering Nina's customers. Another hesitates to accept handover responsibilities because previous experiences have involved unnecessary detective work. Nobody wishes Nina harm. In fact, most of them like her. Their frustration comes from the difference between the standard everyone is supposed to follow and what actually happens. Daniel believes he is protecting one valued relationship, but he is gradually weakening several others. The team sees the consequences even if it does not know the reasons behind his reluctance.

A useful test is to imagine the same behavior coming from a colleague with whom you have no special personal connection. Would you regard missing handover records as equally acceptable? Would you respond at the same speed? Would you require the same change? The answer may reveal an inconsistency worth examining. This does not mean ignoring individual circumstances or treating everyone as though they have identical roles and resources. Fairness requires relevant context, not mechanical uniformity. A temporary difficulty, unusual workload, or unclear instruction may justify different support. Personal affection, however, should not quietly become an unofficial exemption from responsibilities that everyone else must fulfill. Otherwise, being particularly enjoyable company becomes a surprisingly powerful addition to the employee benefits package.

Before rushing to correct that imbalance, Daniel also needs to check whether the problem is genuinely Nina's responsibility. Perhaps the documentation process is unnecessarily complicated. Perhaps employees have been told that customer interaction matters more than internal records, with no clarification about priorities. Perhaps Nina is managing significantly more accounts than her colleagues. These possibilities do not erase the consequences of incomplete handovers, but they may affect what needs to change. Liking someone should not prevent scrutiny of their work; disliking a particular outcome should not prevent scrutiny of the system surrounding it. Fair judgment means being willing to discover that the most convenient explanation was not the most accurate one.

Another subtle danger is expecting people you like to read your mind. Because Daniel and Nina have worked together for years, he assumes she understands his concerns. He has mentioned documentation during team meetings. He has sighed when information was missing. Once, while searching for a customer decision, he joked that the shared database might eventually become useful if someone introduced it to the employees. Nina laughed, reasonably interpreting the remark as a complaint about the system. Daniel remembers it as a warning. Neither has actually established a shared understanding. Familiarity creates an illusion that important expectations have already been communicated, even when they exist mainly as private conclusions inside one person's head.

To break that illusion, Daniel can identify what he wants to preserve in the relationship and what needs to change in the work. He values Nina's customer care, initiative, and willingness to help. He needs her to record decisions and complete the agreed handover information before an account changes ownership. These are not contradictory objectives. In fact, better documentation could make her excellent customer service more dependable when she is unavailable. Once Daniel stops imagining the conversation as an attack on Nina's character, the purpose becomes clearer. He is not asking her to become less thoughtful or less committed. He is asking her to make part of her work accessible to the people who depend on it.

It helps to notice what you are hoping to receive from the conversation. If your secret objective is to hear, "Of course we're still friends, and I think you're an absolutely wonderful manager," you may begin negotiating away the actual concern whenever the other person looks disappointed. You might soften the expectation, offer explanations on their behalf, or promise additional support before discovering whether any is necessary. The conversation becomes an attempt to manage your own anxiety through the other person's reassurance. A more useful objective is modest and professional: explain the concern accurately, understand the relevant circumstances, and establish what needs to happen differently. You can care about the relationship without making the other person responsible for immediately restoring your emotional comfort.

The distinction matters even more when the person involved is a friend outside work. Perhaps you joined the same organization years ago, supported each other through difficult periods, or regularly spend time together socially. A workplace disagreement may then appear to threaten something beyond the office. It is sensible to acknowledge that complication rather than pretend the relationship is purely transactional. But friendship does not automatically authorize one person to impose professional costs on others. Nor should management responsibilities be exercised through private emotional pressure. You can explain that your working relationship matters to you while keeping expectations grounded in the actual responsibilities of the role.

If you are not the person's manager, the same principle applies within different limits. You cannot necessarily require a colleague to follow your preferred method, but you can explain how their behavior affects shared commitments and request a workable agreement. Your right to express an issue does not depend on holding a more senior job title. Your authority to impose a particular solution might. Understanding that difference prevents the conversation from turning into a struggle for control. A colleague who genuinely respects you may be willing to reconsider something once they understand its consequences, but they should not have to accept your judgment merely to demonstrate loyalty.

You also need room for an outcome that is less emotionally satisfying than you hoped. Nina might feel disappointed that Daniel did not speak sooner. She may disagree with the importance he places on documentation or reveal that some requirements were never properly explained. She might need time to think. None of these responses automatically proves that the conversation was a mistake. Equally, Daniel should not assume that his concern is correct simply because he has finally gathered the courage to express it. Being willing to listen and revise an inaccurate judgment is part of respecting someone. Being willing to maintain a justified expectation despite temporary disappointment is another part. Both are necessary.

Imagine that Nina responds, "I thought you were happy with how I handled these customers." Daniel can acknowledge the truth in that statement without withdrawing the concern. "I am happy with the care you give customers. I should have been clearer earlier that the handover records are also part of the job, and the missing information has been creating problems for colleagues." That response neither denies her strengths nor pretends the documentation issue is insignificant. It also accepts his contribution to the misunderstanding. The conversation may remain uncomfortable, but the discomfort now serves a recognizable purpose rather than becoming something both people frantically attempt to escape.

Of course, nobody needs to schedule a corrective conversation every time a friend uses an unfamiliar spreadsheet layout or chooses a different way to organize their desk. People have their own styles, and not every variation is a performance concern. Before speaking, consider whether the behavior affects an agreed expectation, another person's work, a meaningful result, or an important standard. If the only issue is that someone does things differently from you, the most reasonable response may be to leave them alone. Your appreciation for a colleague should not excuse significant problems, but your responsibility for standards does not make you the official curator of everybody else's personality.

The central challenge, then, is not learning to like people less. It is learning to stop treating affection as a reason to withhold information they may genuinely need. Daniel does Nina no favor by allowing her to believe that excellent customer relationships compensate indefinitely for incomplete handovers. He does his other colleagues no favor by quietly assigning them the cost. And he does himself no favor by spending each week rehearsing a conversation that becomes more difficult with every avoidable complication. He can respect Nina, recognize her contribution, and still ask for better documentation. The relationship may need to accommodate a moment of discomfort, but that is not the same as losing it.

Being liked is a pleasant part of working with people. It should not become the hidden condition for telling them the truth. If your affection for someone is genuine, give them the courtesy of knowing where things stand while there is still a reasonable opportunity to improve. You do not have to deliver the message with perfect confidence, and they do not have to receive it with delight. You simply have to stop confusing a good relationship with a relationship in which nothing difficult is ever said. The former can support honest conversations. The latter eventually needs an increasingly elaborate filing system for everything nobody has dared to mention.

Chapter 2 - The Facts Are Manageable. The Story in Your Head Is Not.

"Marcus has stopped paying attention." That is the conclusion Isabel reaches at 9:18 on Wednesday morning, shortly after receiving a complaint from a conference organizer. Thirty participants have arrived for a professional workshop and discovered that their assigned room is locked. Nobody appears to know where they should go. The organizer is understandably irritated, the participants are wandering around the building, and someone has already suggested that the event should have been held elsewhere. Marcus was responsible for coordinating the morning setup. Isabel likes him enormously, but this is not the first time something has gone wrong during an event. She decides that his relaxed attitude is becoming a professional problem. By the time she reaches his office, she has assembled a compelling explanation involving carelessness, excessive confidence, and possibly an unfortunate allergy to checking schedules.

There is one complication. Marcus had prepared the correct room according to the schedule available to him. The venue management team had moved the workshop overnight because of an unexpected maintenance issue, but the notification went to an administrative mailbox that Marcus could not access. The room was changed, the signs were not updated, and the organizer was given conflicting information. Marcus did miss an opportunity to verify the final room allocation that morning, but the broader problem was considerably more complicated than Isabel's original conclusion. Had she begun by accusing him of no longer caring about his responsibilities, the conversation would probably have become an argument about his dedication. Instead, the useful questions concerned how schedule changes were communicated, who confirmed them, and what morning checks were realistically required.

Our minds are remarkably efficient at turning incomplete information into coherent stories. We see an unwanted result, connect it to something we remember, and produce an explanation that feels convincing because it makes sense. The explanation may even be correct. Unfortunately, feeling certain about a story does not make every part of it an established fact. Isabel knew that participants had been sent to the wrong location. She knew that Marcus was responsible for coordinating the event. She did not know why the original arrangement had failed. Those three statements belong to different categories, and treating them as interchangeable would have created an unnecessarily hostile conversation.

One of the most useful distinctions in difficult feedback is the difference between what happened, what you believe caused it, and what you think it says about the person involved. The first may be established through records, direct observation, or reliable accounts. The second requires examination. The third often involves a much larger judgment than the available information can support. "The workshop started twenty minutes late" describes an outcome. "Marcus did not check the room assignment" identifies a possible contributing action that requires confirmation. "Marcus is irresponsible" turns the situation into a judgment about his character. Each step adds assumptions. The danger appears when we skip those steps and present the final conclusion as though it were the original observation.

This habit becomes particularly troublesome with people we know well. Familiarity gives us valuable context, but it also provides a collection of memorable incidents from which we can construct almost any story we prefer. If Marcus has previously forgotten a minor detail, Isabel may interpret the workshop problem as another example of his lack of attention. If he has rescued several difficult events, she may instead excuse everything without investigation. Neither reaction guarantees fairness. Past experience should inform questions, not eliminate the need to examine the current situation. The fact that someone has occasionally made mistakes does not establish the cause of every future difficulty. Equally, a strong record of achievement does not make new problems imaginary.

Language often reveals when interpretation has begun replacing observation. Words such as "lazy," "careless," "unprofessional," and "uncommitted" can feel wonderfully efficient because they summarize an entire concern in a single adjective. Unfortunately, they also force the recipient to defend an identity rather than discuss an action. If Isabel says, "You've become careless," Marcus may respond by listing occasions when he worked late, supported colleagues, or handled difficult clients. Those examples may be entirely true without resolving the workshop problem. A more productive opening would identify the delayed start and ask how the room allocation was confirmed. There is no need to pretend that the incident was harmless. Precision allows the discussion to remain serious without expanding it into a debate about Marcus's worth as an employee.

The words "always" and "never" create a similar difficulty. "You never check the final arrangements" sounds decisive until Marcus produces evidence of six events where everything was checked correctly. Suddenly the conversation is about whether the word "never" was mathematically defensible. You do not need absolute language to establish that a problem deserves attention. If the final arrangements were missed on two specific occasions, say so. If you cannot identify a recurring pattern, avoid presenting one as an established fact. A single significant incident may justify action on its own, particularly when the consequences are serious. Exaggeration does not make the case stronger. It merely gives the other person an additional statement to dispute, often successfully.

A further distinction concerns the effect of a behavior. You may feel embarrassed, irritated, or disappointed by what happened, but your emotional response is not necessarily the complete organizational impact. Isabel can reasonably explain that participants waited, the organizer complained, and the workshop started late. She should be more cautious about claiming that the venue has permanently lost the client's trust or suffered a major financial loss unless she has evidence. Forecasting a possible consequence is legitimate when clearly presented as a risk. Describing a feared consequence as an accomplished fact is something else. In difficult conversations, dramatic predictions can make a manager sound impressive for approximately fifteen seconds before someone asks for the supporting details.