# How HR Leaders Make Performance Conversations More Constructive - Published: 2026-11-03 - Author: [CHRO Daily](https://chrodaily.com/author/chrodaily-com.md) - Topics: [Q&A](https://chrodaily.com/qa.md) - Source: https://chrodaily.com/qa/how-hr-leaders-make-performance-conversations-more-constructive/ - Publication: CHRO Daily - Publisher: Connectively (Terkel, Inc.) - Editorial policy: https://chrodaily.com/editorial-policy/ - AI use: The perspectives in this article were written by the named contributors and submitted through Connectively. Connectively's automated system selected them and used AI to write the headline, introduction, section headings, summary sections, and illustration, and to make minor edits for clarity. Articles are assembled and published automatically. Report errors to corrections@connectively.us. ### Track Metrics and Diagnose Root Causes 1\. Blindsiding is a monitoring failure, not a people failure. If someone only finds out at review time that they are slipping, then the manager was the broken alert. The way we work at TradingFXVPS is that every role has 2-3 numbers agreed with the individual prior to commencing work. These numbers typically relate to Ticket Resolution Time, Escalation Rate and Client Follow-up within 24 hours. Each person has their own dashboard to monitor their progress against these numbers. If any of the numbers for a particular individual drift over 2 weeks then a conversation will take place to discuss reasons for decline. Typically the individual themselves will have noticed the drift prior to the conversation taking place and will have several possible reasons for the decline which can be discussed with the manager to establish root cause prior to any conclusions being reached. In my case I would have hoped that my support tech had been as aware of my declining situation as I had been and we could have had several conversations prior to him departing the business several weeks later to begin a far better-sized support function where his skills would be valued far more. He informed me on his departure that he had no idea I was as unhappy as I had been. 2\. Most performance talks turn into trial-like proceedings. So I turn them around and run them like an outage postmortem. I write up a one-page document to send out 24 hours in advance outlining what happened, the numbers, and how the client was affected. In the actual talk I just retrace the events as they happened on the timeline and then start to investigate the root cause. Most of the time I find that the root cause is something to do with me (bad handoff, terrible tooling, wrong shift timings, etc.). But we leave the talk with one thing to fix, one person to hold accountable and a date when to recheck. This way, treating performance issues as broken processes to debug, is so much healthier than treating them as people issues. --- ### Treat Friction as Operational Data Performance problems rarely begin on the day output falls. They usually appear earlier as friction, repeated rework, delayed decisions, or colleagues quietly compensating. Treat those signals as operational data, not gossip. A manager who waits for quarterly metrics has already allowed the team to absorb the cost and the employee to lose valuable course-correction time. I favor a reset conversation that asks what good looks like, what is blocking it, and what will change by the next checkpoint. The manager should state which support or tradeoff changes on their side. Accountability without examining the environment is often theater. A dated checkpoint converts concern into an experiment, and its result guides the next decision fairly. --- ### Address Patterns Within the First Week I address performance concerns in the first week I see a pattern, not after a formal review blindsides someone. At my telecom company the early signal was usually the same: a new hire looked busy in the field but the office reviews kept flagging incomplete job records. I pulled them aside privately within days, put the specific jobs on the table, and asked what was getting in the way rather than opening with a verdict. That conversation stayed constructive because it was concrete and early. We agreed on one fix, often a clearer SOP for closing work in the software, and a check in seven days later. Most people corrected course. When they did not, the later decision was fair because nothing was a surprise. Waiting until someone feels ambushed is not kindness. It is delayed honesty that costs both of you trust. --- ### Set Explicit Improvement Milestones I raise a performance concern in a one-to-one while the employee still has time to respond. We agree on the specific points that need improvement and set a follow-up check. If a manager waits until a final verdict to say what has been troubling them, the employee loses that chance and the decision feels like a surprise. In one leadership decision, I agreed improvement points with the person and reviewed the results a month later. I then ended their employment. I took over some of the oversight myself and joined the project managers' working groups so I could see how the work was going. The earlier conversation had given that person an explicit opportunity to show progress. It also gave me agreed points against which to make the decision, rather than a vague impression formed afterward. I find it more constructive to discuss evidence on both sides of the concern. In our reviews, the employee goes through each item first and identifies colleagues they've worked with. Those colleagues give examples when they confirm or dispute an assessment; HR and our CTO check doubtful points against system data. If a manager raises missed deadlines, they should be able to discuss a real missed deadline and hear the employee's account of what happened. Then we can talk about what needs to change while the manager remains responsible for the decision. Bring the first concrete concern to the next private conversation, agree what progress would look like, and schedule the check before you leave. --- ### Ask Curious Questions Before Correction I run a fully remote team across eight countries, so we have had to build fair, early feedback into the system. People feel blindsided when feedback gets saved up for a formal review. We make it the weekly rhythm instead. Managers run short check-ins, and small corrections happen as they come up, in private and respectfully. By the time a bigger concern needs raising, it is never the first time the person has heard of it. And the comment stays on the action or the missed standard, never on the person. What makes the hard conversation more constructive is the order I do it in. Before correcting anything, I get on a call and ask the person to walk me through their own thinking. "Talk me through how you approached this. Are you happy with it?" Often their answer shows the instruction was unclear and the fix was mine. When the miss was genuinely theirs, they usually spot it themselves, which lands far better than being told. Go in curious, not with loaded guns. --- ### Pair Concerns With Confident Support I really think that the angle you take with these conversations about performance makes all the difference. If you simply tell your employee that they aren't performing well enough and need to do better, that's not going to have a positive impact. Sure, they may learn that they aren't performing at the appropriate level, but they are going to leave the conversation feeling discouraged or embarrassed, and that's going to be terrible for morale. So, what you want to make sure you do instead is bring up your concerns about their performance followed by a strategy for improvement and a genuine acknowledgement that you believe in them. You want to sound and be positive, and you want them to leave the conversation feeling confident and inspired. --- ### Map a Path Back to Green The best way to stop employees from being left in the dark is to see performance management as an ongoing feedback process, rather than as an event scheduled periodically. It loses its significance as a tool for coaching when feedback is separated from the concrete work by different time periods, and residents see it simply as a complaint with logical defensive impulses occurring at this point. From my experience of managing operations globally, identifying the issue in performance within two days makes it possible to change the discussion from having a disciplinary character to being purely pragmatic. This swift resolution avoids the building up of minor issues leading to serious operational problems that call for formal interventions. I noticed that the anxiety caused by performance evaluations is a consequence of communication lag. That is why we concentrate on narrowing down the gap between what we produced and what we asked for rather than on discussing the competencies of a certain employee. Instead of discussing an employee's general competence, we analyse the concrete deliverable and figure out which resources or adjustments need to be done so that we could close that gap. One of the conversation techniques that has been working well in our operations centers is having the focus on the path to green. We start the conversation by stating where we are at the moment and move on to the discussion of what needs to be done in order to return to the desired level. By talking about future actions and achievements, we are maintaining the high quality ethos without undermining trust in the relationships between managers and their subordinates. The existence of clear expectations and continuous feedback guarantees that when the formal evaluation takes place, there are no surprises, since the employee has already had dozens of chances to correct their performance. --- ### Hear Their Read Before Yours In February a writer on our team missed 2 small deadlines in a row. I raised it that same week as an observation, with both dates attached. Then I asked for her read before giving mine. Her read was that the briefs kept changing after she started. That was true and partly my fault. At around 60 people everyone knows everyone. A concern raised 3 months late lands like an ambush, with the whole team guessing at the backstory. Holding my own read back until she had given hers is the part I find hardest. You would probably get the same talk 3 months later anyway, only with far more to defend on both sides. --- ### Set a Two-Week Response Plan I address performance concerns early through short, regular check-ins that make feedback routine rather than a surprise. As founder of Cyber Techwear I keep conversations concrete and focused on observable behaviour, not personality. When an issue appears I state the specific example, ask what's getting in the way, and agree on one clear short-term action with a fixed follow-up (typically two weeks). That structure turned a missed-deadline pattern into a clear action plan and a calmer, more constructive conversation. --- ### Use Visual Proof, Then Ask Nobody should hear about a problem for the first time in a review. My rule is that the first conversation happens the same week I notice a pattern, while it's still small enough to fix with one adjustment. That only works if the standard is written down before anything goes wrong. Our cleaners work from a room-by-room checklist, and every room gets a before and after photo. When something slips, we're both looking at the same picture and the same line on the list. Nobody has to argue about whose memory is right. The practice that has made hard conversations easier is opening with the photo or the checklist line and then asking, "Walk me through what happened here." I ask it and stop talking. People usually name the cause themselves, whether that's a rushed schedule or a step they didn't know existed. Often the fix turns out to be mine to make. After that I agree on one specific change and a day to look again. The follow-up date matters because the person knows exactly when I'll check and what I'll be looking at, so a later review holds nothing new. --- ### Limit Corrections to One Commitment I use early performance conversations to reduce ambiguity before it becomes resentment on either side. The discussion should happen near the event, but not in the heat of frustration. Taking enough time to gather facts helps ensure the message is accurate, balanced, and useful. Employees deserve clarity about what happened and why it matters. A practice that consistently improves the outcome is asking for one commitment, not several. Too many corrective actions can leave someone discouraged and unsure where to start. Select the behavior with the greatest effect, define when it should occur, and revisit it soon. Once that adjustment becomes consistent, additional development can follow. This approach makes improvement feel achievable while still maintaining clear expectations. --- ### Run Measurable Improvement Experiments Difficult performance discussions become less threatening when the employee hears the concern close to the work itself. Delayed feedback creates a false sense that the work met expectations, then turns a manageable correction into a trust issue. I use concrete moments, including what happened, what outcome was expected, and what impact followed. Rather than asking someone to broadly "improve," agree on an experiment. For example, an employee may send a decision summary before execution, request feedback earlier, or use a checklist for recurring work. The manager should define how progress will be recognized, not only how failure will be judged. That matters because performance conversations should produce evidence of improvement, not merely documentation of concern. Clear experiments also make support visible and accountability credible. --- Deleted by user --- ### Examine Systems Before You Assign Blame Early intervention is credible when the manager can show that expectations were made executable. A concern about quality is weak if the employee never received an example, a decision boundary, or a definition of done. In operations, ambiguity compounds quickly, so leaders need to examine the system before assigning the problem to the person. I encourage managers to begin with a comparison between the process and the work that arrived. This shifts the conversation from "you are underperforming" to "this part of the process broke, let's understand why." It preserves dignity while making accountability concrete. The outcome should include a correction and a manager commitment, such as approvals or escalation access. --- ### Tie Reviews to Work Cycles I recommend tying feedback to the work cycle rather than the review calendar. Managers should set expected results, decision authority, and mid-project checkpoints to compare work against requirements. For difficult conversations, having the employee walk through their plan for the next task keeps discussions practical and avoids debates over intent. The planning and feedback process should use the current job description, individual goals, and unit goals as the basis for an ongoing conversation about job expectations and job performance. Outcomes should be specific, observable, and measurable. Once expectations are agreed upon, they become a point of reference against which you can measure the employee's progress over time. Team members should know, preferably at the beginning of the project, that a progress review will be taking place. This review helps determine whether the work is on track, off course, or needs changes and adjustments in order to move to the next stage. Understanding root causes is believed to help everyone decide future action. The approach should be open, honest and detailed. It's a chance to offer feedback that will help employees meet their goals and inform new ones. The performance review should be an interactive discussion between you and the employee. As with any project, it's essential to take time to evaluate your progress. Keep the feedback conversation centered on what will make the employee most successful going forward. You could even schedule another meeting to see how the employee is progressing with their tasks. --- ### Invite Employee Views After Observations In sports, a coach doesn't wait until the end of the season to tell a player their footwork is off. Feedback comes after practice, while the play is still fresh. Performance at work deserves the same rhythm. Blindsiding usually happens when small concerns go unspoken for months and then arrive all at once. Regular, direct feedback prevents that. On our team, people know where they stand, so a hard conversation builds on things already discussed. The practice I lean on is starting with what I've observed and then asking for their view before offering mine. Picture someone whose sponsor follow-ups have started slipping during a busy event season. Opening with "I've noticed a few follow-ups running late. What's going on from your side?" invites an explanation. Maybe they're overloaded. Maybe a process is broken. Either way, you're solving it together. Fairness comes from making it safe to fall short and learn. When people trust that one rough stretch won't define them, they tell you the truth early, and that's when problems are easiest to fix. --- ### Request a Reverse Brief A reverse briefing helps clarify expectations before performance is judged as poor. The concern and desired result are explained first, followed by a request for the employee to restate the expectation in their own words. They also explain how they would make decisions when priorities conflict. This makes any misunderstanding easier to identify. The practice tests whether the manager has communicated clearly instead of making assumptions. If the employee's explanation differs from the intended standard, the manager must clarify expectations before raising the issue further. If both understand the standard, the discussion can focus on barriers, skills, or follow-through. Employees leave with a clear decision rule, while managers gain a fair basis for follow-up. --- ### Check Fairness Through Shared Agendas I recommend a brief fairness check before raising performance concerns, ensuring requirements are job-related and consistently applied. During discussions, I use a shared agenda focused on a specific upcoming work product, setting one observable near-term outcome and review date to demonstrate progress constructively. Before making any decisions about an employee's next steps, you need to review their performance and discuss your concerns with them. The discussion should include some examples of the performance issues you're addressing and a plan to improve. Remember that the point of the meeting is to establish the facts, not catch people out. Regardless of an employee's classification and title, coaching is the foundation of the performance improvement process. In a performance management cycle, coaching means providing ongoing feedback and support to the employee throughout the year. During the meeting, an agenda can be used to help keep the conversation moving forward and on time. Now you need to include your employee in this discussion. Give them an opportunity to share their perspective on each area being discussed. Finally, a follow-up review is a chance to see what has changed and to check that recommendations have been put into practice. --- ### Require Clear Expectation Restatements The test of a constructive performance conversation is whether the employee can explain the next expectation without the manager in the room. If the outcome is only that someone feels warned, the discussion was incomplete. I end by asking the employee to restate the expected result, the key constraint, and the point when they should escalate. That practice is especially valuable in bathroom projects, where a cabinet dimension can be correct while door clearance still fails. Performance standards have similar dependencies. A person may complete an assignment, yet miss the handoff, verification, or timing that makes it useful. Restating the standard surfaces those dependencies before they become repeated frustrations. --- ### Build Rapport Through Monthly One-On-Ones I found that regular, focused one-on-ones help make performance conversations feel expected rather than sudden. I held 30-minute monthly meetings to review performance and discuss what resources each person needed. Each employee also brought one win and one frustration, giving us a balanced starting point for candid discussion. We talked about personal and professional goals, too, so the conversation included their development and not just their output. That ongoing dialogue creates room to raise concerns, clarify expectations, and discuss support early. --- ### Gauge Sustainable Support Through Daily Talks One practice that helped me was making a performance review a short period of frequent conversations. In one case, I met with a remote developer each night during a ten-day review. That made the amount of management the person needed much clearer than a single review meeting would have. By my estimate, the developer's productivity improved about tenfold during that period. The experience showed me that more management could make a substantial difference. It also exposed a second question: could our team sustain that level of support? Ultimately, the arrangement did not work out. We were a small team and did not have the bandwidth to keep providing that much ongoing management. The temporary improvement was real in my assessment, but it did not establish a sustainable working arrangement. My lesson is to use early, frequent conversations to understand both the performance concern and the support required to address it. Be candid about what the organization can provide. A constructive review should help both sides understand what would have to change, rather than leave expectations unstated until a final decision. --- ### Cite Behaviors, Then Offer Support When performance concerns emerge, I address them early by talking about a specific observed behavior, not a general impression. In a health club that sounds like: "On Tuesday and Thursday this week, the 5 a.m. opening checklist was not completed, and members waited at the desk." That is fair because the employee hears exactly what I saw, when I saw it, and what good looks like instead — no surprises, no labels about attitude. The practice that makes these conversations constructive is ending with the support question: "What is getting in the way, and what do you need from me to fix it?" Sometimes the answer is training, sometimes a schedule problem, sometimes something personal. Then we agree on one measurable change and a short date to check it together. Handled that way, the first conversation is coaching, not a warning — and if it ever has to become a warning, the employee cannot honestly say they were blindsided. --- ### Announce Topics Before Meetings I try to take the surprise out of performance concerns by explaining how I'll raise one long before there's anything to raise. When someone starts working with us, I tell them that if something isn't working, they'll hear it from me first, privately and early, over two short conversations rather than one. That way, when a real concern does come up, the process is already familiar, even if the news isn't. The first conversation is only for describing what I've noticed, and we meet again the next working day to agree what changes. Hearing a concern and fixing it are two different jobs, and in my view asking someone to do both in one sitting tends to get a defence rather than a plan. --- ### Verify Comprehension Before Departure My rule for fairness is that nothing should appear in a formal review that wasn't already said plainly and privately, close to when it happened. Early doesn't have to mean harsh; it means specific: one recent example, what good would have looked like, and a moment for the person to give their side before I reach any conclusion. Back in 2020 I said that, for me, success had come to mean maturity and growth above all, and I think a performance conversation deserves the same yardstick: it went well if the person grows from it, not if anyone won the point. For the hard ones, I'd ask the person to restate in their own words what they heard before anyone leaves the room, because a concern that was misunderstood might as well never have been raised. Surprises in a review are a failure of the manager long before they're a failure of the employee. --- ### Disclose Topics and Separate Facts I'd tell the person what the conversation is about when I book it, rather than raising it once they've sat down, because the surprise is usually what makes someone feel blindsided. At a small online store, a one-line note such as "I'd like to talk about the price updates that have been reaching the site late; bring anything that would help me understand them" gives them time to think and to arrive with their side of it. In the meeting, I'd keep two steps apart: first agree on what actually happened, then discuss what to do about it, because people defend themselves hardest when the facts and the fix are argued at once. On timing, my test for fairness is simple: if something is serious enough to appear in a formal review, it's serious enough to raise the same week it happens. ## Related - [Build Manager Confidence for Tough Workplace Conversations](https://chrodaily.com/qa/build-manager-confidence-for-tough-workplace-conversations.md) - [How HR Leaders Turn Employee Feedback Into Trust](https://chrodaily.com/qa/how-hr-leaders-turn-employee-feedback-into-trust.md) - [Employee Listening in HR: Turning Feedback into Credible Action](https://chrodaily.com/qa/employee-listening-in-hr-turning-feedback-into-credible-action.md) - [How HR Leaders Strengthen New-Hire Onboarding](https://chrodaily.com/qa/how-hr-leaders-strengthen-new-hire-onboarding.md)