# How Managers Turn Performance Conversations Into Progress

- Published: 2026-11-16
- Author: [Economist Zone](https://economistzone.com/author/economistzone-com.md)
- Topics: [Q&A](https://economistzone.com/qa.md)
- Source: https://economistzone.com/qa/how-managers-turn-performance-conversations-into-progress/
- Publication: Economist Zone
- Publisher: Connectively (Terkel, Inc.)
- Editorial policy: https://economistzone.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.

### Trace Failures, Then Coauthor Runbooks

1\. Most performance problems at TradingFXVPS are system failures wearing a person's face. Before speaking to a person, I verify the plumbing (runbooks, tools, alert queues, handovers) to find the root cause of the problem that I can solve or that someone else has failed to solve previously. If it really is a person's problem, then I raise the same issue the second time it occurs. One miss is noise, two misses is a trend. I can verify the following information: timestamps and ticket logs, not slow/careless, etc.

2\. I do my conversations as blameless postmortems. We re-run one specific incident and go through it minute by minute. Instead of asking who failed, we ask where it failed. A night-shift support engineer took 40+ minutes to escalate MT5 server alerts. After re-tracing the incident step by step, he admitted that he had tried to solve the problem before and had failed, and that he had escalated because he thought the others would think he was not able to fix it. No one had ever told him that escalating was his job. We re-wrote the runbook together and included a hard rule of 8 minutes. Within a month, his median time to escalate had gone down to 6 minutes. Now he is one of the people who flag potential gaps in our runbooks before they cause an incident. Giving him ownership of the fix was way more valuable than any words of motivation.

<aside class="expert"><img src="https://featured-com-images.s3.us-west-1.amazonaws.com/profile-images/299e9201-111e-4433-ae2c-04eb367ce42d.webp" alt="Ace Zhuo" loading="lazy"><p><a href="https://www.linkedin.com/in/ace-zhuo" rel="nofollow">Ace Zhuo</a>, CEO | Sales and Marketing, Tech &amp; Finance Expert, <a href="https://www.tradingfxvps.com" rel="noopener">TradingFXVPS</a></p></aside>

---

### Compare Outcomes and Repair Handoffs

In growth businesses, underperformance often reflects a mismatch between what leadership believes is clear and what the employee can actually execute. I have learned that waiting for a formal review makes the conversation emotionally expensive. Address the issue early, when it can still be treated as course correction instead of accumulated evidence.

One productive conversation began with a simple comparison, "Here is the outcome we needed, here is what occurred, and here is where the handoff broke." That framing removed blame and exposed a bottleneck in the employee's workflow. Together, we rebuilt the sequence of work, added an earlier checkpoint, and measured the leading indicator rather than the final result. Motivation improved because progress became visible before the deadline arrived.

<aside class="expert"><img src="https://featured-com-images.s3.us-west-1.amazonaws.com/profile-images/dfd52a29-27d4-4bdb-b67c-9f64e880a4b1.webp" alt="Jason Hennessey" loading="lazy"><p><a href="https://www.linkedin.com/in/jhennessey" rel="nofollow">Jason Hennessey</a>, CEO, <a href="https://hennessey.com" rel="noopener">Hennessey Digital</a></p></aside>

---

### Use Metrics to Set Near-Term Targets

I address underperformance early by bringing the data to the first conversation, so it is about the work and not about the person. When I ran my NBN telecom contracting company in Australia, we captured every job in the field on our own software and an office admin reviewed it. That meant I could see when someone's output dropped well before it turned into a pattern, and I could start the conversation with something specific: here is what you completed this week, here is what you completed a month ago, what changed? That question opened up far more than an accusation would have. Most of the time the answer was something real, a hard site, a problem at home, a crew mate who was slowing them down, and we could fix it. When it was simply effort, the numbers made that clear without me having to argue it. The approach that turned those talks into a next step was ending with one measurable goal for the next week, agreed together, and checking it with them the following Friday. I still tell the business owners I coach the same thing. The common leak I see is paying for eight hours and getting five, and the fix is not a tougher speech. It is fair, visible numbers and a short, early, private conversation about one week's work.

<aside class="expert"><img src="https://featured-com-images.s3.us-west-1.amazonaws.com/profile-images/822feac4-8e3b-4c7f-b8ec-b0fb02614ff5.webp" alt="Ronald Osborne" loading="lazy"><p><a href="https://www.linkedin.com/in/ronaldosborne-osbornedigitalmarketing/" rel="nofollow">Ronald Osborne</a>, Founder, <a href="https://ronaldosborne.org" rel="noopener">Ronald Osborne Business Coach</a></p></aside>

---

### Inspect Commitments and Agree Future Moves

When performance falls short, I bring up the piece of work we can inspect while there's still time to improve the next one. Calling someone unreliable makes the conversation about character. A missed commitment gives us a specific question: what got in the way? I want to hear the employee's account before reaching a conclusion, then agree on what to do differently in the next assignment.

Our review process starts with the employee rating each item and identifying the colleagues who worked alongside them. HR asks those colleagues to assess the same items, with an example behind each agreement or disagreement. A questioned deadline needs an actual case; credit for helping others develop should point to particular working sessions. HR and the CTO review the accounts together and use system data to revisit uncertain points. When an employee's view differs from a documented example, we can discuss the task itself. We don't treat one colleague's impression as the final answer.

The conversation moves from the gap to the next piece of work. At grade review, colleagues, HR and the CTO explain the facts behind their recommendations for improvement. HR also meets every employee monthly in a one-to-one, so there's a regular place to discuss areas for development. If the issue is a deadline, I'd ask the employee to agree to the next commitment and how we'll tell whether it's met. The action needs to be observable, and we need a time to revisit it.

An early discussion doesn't have to sound like a verdict. Ask the employee for their reading of the specific work, put the evidence beside it, and settle on the next action together.

<aside class="expert"><img src="https://featured-com-images.s3.us-west-1.amazonaws.com/profile-images/732f12d1-adb0-47c4-a0fb-1f2666e046c2.webp" alt="Roman Surikov" loading="lazy"><p><a href="https://www.linkedin.com/in/roman-surikov" rel="nofollow">Roman Surikov</a>, Founder &amp; CEO, <a href="https://ronasit.com" rel="noopener">Ronas IT | Software Development Company</a></p></aside>

---

### Apply Keep, Stop, Start Feedback

We believe trust is protected through clear and precise feedback. Vague comments can feel personal because employees are left guessing what went wrong. Early conversations should focus on a clear situation, the expected action, and its impact. We also explain that the goal is to address small gaps before they become bigger challenges.

We find the "keep, stop, start" approach useful for guiding these discussions. We ask employees what is working, what creates friction, and what new habit could make the greatest difference. This keeps feedback constructive rather than turning it into a list of faults. In a difficult case, the employee chose the new habit and requested regular reviews, making the improvement plan feel supportive rather than punitive.

<aside class="expert"><img src="https://featured-com-images.s3.us-west-1.amazonaws.com/profile-images/5d5764e9-0315-40a2-89a4-5cb100bb71b5.webp" alt="Sahil Kakkar" loading="lazy"><p><a href="https://www.linkedin.com/in/sahilkakkar" rel="nofollow">Sahil Kakkar</a>, CEO / Founder, <a href="https://www.rankwatch.com" rel="noopener">RankWatch</a></p></aside>

---

### Anchor Dialogue to OKRs and Capital Returns

Addressing performance gaps early requires shifting the dialogue from personal critique to a neutral analysis of the delta between current output and shared organizational objectives. When feedback is framed against a pre-defined Objective and Key Result (OKR) rather than an individual opinion, it replaces defensive friction with collaborative problem-solving. Trust is maintained through absolute clarity on the scorecard; motivation survives a difficult conversation when the employee understands the target is the priority, not a judgment of their character.

A specific framework that transforms these discussions is Resource-to-Outcome Alignment. Instead of highlighting a failure, I present the current project metrics and ask: "If you were responsible for the capital investment in this delivery, what change would you make to ensure we hit our release milestone?" This pivot forces an ownership mindset. We look at the gap between target velocity and actual output as a technical bottleneck rather than a personal flaw. This removes the emotional weight and allows for a pragmatic discussion about requirements, specialized training, or shifting focus from vanity metrics to meaningful shipping milestones.

Early intervention succeeds when underperformance is treated as a risk to the collective return on effort. By anchoring performance reviews in financial and operational discipline, the path forward is built on measurable progress. This approach respects the professional's expertise while maintaining a non-negotiable standard for delivery, ensuring the individual and the organization move toward a sustainable result.

<aside class="expert"><img src="https://featured-com-images.s3.us-west-1.amazonaws.com/profile-images/886c2959-86f6-4753-87bf-122f5b2bcf07.webp" alt="Abhishek Pareek" loading="lazy"><p><a href="https://www.linkedin.com/in/abhishekpareek80" rel="nofollow">Abhishek Pareek</a>, Founder &amp; Director, <a href="https://www.coders.dev" rel="noopener">Coders.dev</a></p></aside>

---

### Surface Small Gaps and Let Staff Design Plans

Say it early and say it small. Most performance conversations go badly because the manager waited until there were five problems, then delivered them all at once. By then it feels like a verdict, and the person spends the meeting defending themselves instead of listening.

What I'd do instead is raise the first gap within a week of noticing it, in a normal one-on-one, framed around the work. Something like "This report went out with numbers that didn't match the source. Walk me through how you built it." Then actually listen. Half the time the cause is something you didn't know about. Unclear priorities, a tool nobody trained them on, a dependency that slipped.

The approach that turns it constructive is asking them to set the next step. "What would good look like on the next one, and what do you need from me to get there?" People follow through on plans they wrote. Plans handed to them get resented.

Then put a date on a check-in, two weeks out, not two months. If it improves, say so specifically. People remember criticism much longer than they remember the correction being noticed.

I'd skip the praise sandwich. People see through it and the actual message gets fuzzy.

And if the gap turns out to be skill rather than effort, treat it as a training problem. Pair them with someone strong, or give them a practice task with feedback. The tone of the whole thing changes once it's about closing a gap together.

<aside class="expert"><img src="https://featured-com-images.s3.us-west-1.amazonaws.com/profile-images/67e9da94-98de-487b-9564-ef4b10ce39a3.webp" alt="Abhishek Shah" loading="lazy"><p><a href="https://www.linkedin.com/in/abhishekrshah" rel="nofollow">Abhishek Shah</a>, Founder, <a href="https://testlify.com" rel="noopener">Testlify</a></p></aside>

---

### Review Repeat Slips Through Screen Share

If you notice the same slip twice, have the conversation that week, on a call where you both look at the work. I ask the person to share their screen and walk me through the last piece that went wrong. Neither of us looks at the other's face for most of it.

Our people are spread out, most of them remote in India. A calendar invite with a vague title does more damage there than anything said on the call, because someone spends a whole day guessing. So the invite just names the document. It sounds small, though it changes who the conversation is about.

Partway through they usually point at the problem before I do (a step skipped, a brief read differently). That becomes the next step, in their words rather than mine. Without that rule I would wait a month and call it patience.

<aside class="expert"><img src="https://featured-com-images.s3.us-west-1.amazonaws.com/profile-images/7784a8cb-b195-4d64-90ea-68942ea5add6.webp" alt="Sahil Agrawal" loading="lazy"><p><a href="https://www.linkedin.com/in/sahilagrawal26" rel="nofollow">Sahil Agrawal</a>, Founder, Head of Marketing, <a href="https://qubit.capital" rel="noopener">Qubit Capital</a></p></aside>

---

### Follow Observation, Obstacle, Reset

The best way to address underperformance early without hurting trust is to make the first conversation about clarity and support, not judgment. I have found that people shut down when they feel labeled, but they usually stay engaged when the discussion is anchored in specific work, clear expectations, and a practical next step.

As a founder operating SaaS and digital product businesses, one approach that has helped me is what I think of as observation, obstacle, reset. I start with direct observations, not conclusions: for example, "The last two project handoffs missed the agreed scope and timeline." Then I ask an open question before offering my own explanation: "What is getting in the way from your side?" That matters because the root issue is often different from what it first looks like. Sometimes it is a skills gap, sometimes unclear ownership, sometimes too many parallel priorities, and sometimes the person did not fully understand what success looked like.

The constructive part comes next. Instead of turning the conversation into a broad review of everything that is wrong, I narrow it to one immediate reset: one priority, one standard, one check-in date. For example, we might agree that for the next two weeks, every deliverable needs a written summary of scope, deadline, and dependencies before work starts. That gives the employee something concrete to succeed at quickly.

What makes this work is tone and follow-through. I try to be candid about the gap while making it clear the goal is improvement, not blame. I also avoid saving feedback for a formal review. Early, specific conversations are usually less threatening than delayed ones because they feel fixable.

In my experience, trust is damaged less by honest feedback than by vague frustration, shifting standards, or silence. When people leave the conversation knowing exactly what needs to change and believing they will be supported in changing it, motivation is much more likely to stay intact.

<aside class="expert"><img src="https://featured-com-images.s3.us-west-1.amazonaws.com/profile-images/c0bb9f95-0813-4af5-93f8-2bdcbceac898.webp" alt="Kruno Sulić" loading="lazy"><p><a href="https://www.linkedin.com/in/krunosulic" rel="nofollow">Kruno Sulić</a>, Founder &amp; SaaS Product Builder, <a href="https://www.cliprise.app" rel="noopener">Cliprise</a></p></aside>

---

### Build Collaborative Follow-Up Routines

We turned a performance discussion around by inviting the employee to help create a recovery plan. The employee had been missing follow-ups after customer meetings, which affected smooth handoffs. Instead of giving a warning, we explained the pattern and asked what system would make consistent follow-through easier. This shifted the discussion from defensiveness toward finding a practical solution.

Together, we created a simple post-meeting routine, set daily reminders, and introduced a tracker. The employee chose the order of tasks and suggested weekly reviews with us. During each review, we discussed what worked and adjusted the process without treating a missed step as failure. Follow-ups became more reliable, and the employee began sharing the routine with peers.

<aside class="expert"><img src="https://featured-com-images.s3.us-west-1.amazonaws.com/profile-images/71594457-f7b9-4358-91c6-bba0bdb7b4f7.webp" alt="Kyle Barnholt" loading="lazy"><p><a href="https://www.linkedin.com/in/kylebarnholt" rel="nofollow">Kyle Barnholt</a>, CEO &amp; Co-founder, <a href="https://www.trewup.com" rel="noopener">Trewup</a></p></aside>

---

### Address Same-Day Errors, Then Confirm Corrections

The approach I keep coming back to is talking about the work itself, on the day it slips, in private. Waiting for a review cycle lets a small miss turn into a pattern, and by then everyone is defensive.

I start with the specific result I saw and ask what got in the way. Cleaning is physical, repeatable work, so the gap is usually something concrete. A missed step, a rushed order of tasks, a supply that wasn't where it should be. When I ask first, the person usually names the cause before I do, and that keeps the conversation about the problem and off the person.

Then we agree on one change, small enough to try on the very next job. One change gets followed. Five get forgotten by the next shift.

The follow-up matters as much as the talk. I look at that same task on the next job and say so when it's fixed. Praise for the correction is what rebuilds motivation, because it shows the first conversation was about getting better and nothing more.

My cleaning teams work inside homes with nobody watching over their shoulder. That only works when people trust that a mistake gets a fair conversation. If they expect to be ambushed, they hide problems, and hidden problems are the expensive kind.

<aside class="expert"><img src="https://featured-com-images.s3.us-west-1.amazonaws.com/profile-images/f286d4a6-ed1b-49d9-bc4a-202c07771798.webp" alt="Carolyn Vasquez" loading="lazy"><p><a href="https://www.linkedin.com/in/carolyn-vasquez-42a51a44" rel="nofollow">Carolyn Vasquez</a>, Founder, <a href="https://readyrentalcleaning.com" rel="noopener">Ready Rental Cleaning</a></p></aside>

---

### Invite Realistic Pledges by Friday

An effective performance conversation leaves no doubt about the expectation, but it also leaves room for dignity. The employee should hear what needs to change, why it matters, and how progress will be evaluated. Keeping the discussion focused on the future is especially important, because people respond better when feedback feels like guidance than a permanent label.

I once asked an employee, "What commitment feels realistic by next Friday?" The question did not reduce accountability, because the required outcome was already clear. Instead, it exposed an overly ambitious plan that would likely have produced another setback. We narrowed the commitment, identified one barrier, and set a brief check-in. The employee delivered on the revised goal, which rebuilt confidence through evidence rather than reassurance.

<aside class="expert"><img src="https://featured-com-images.s3.us-west-1.amazonaws.com/profile-images/040e806e-9f00-4d27-9f67-2971f8560d17.webp" alt="Brian Hansen" loading="lazy"><p><a href="https://www.linkedin.com/in/brianghansen" rel="nofollow">Brian Hansen</a>, President, <a href="https://rocketpilots.com" rel="noopener">Rocket Pilots</a></p></aside>

---

### Discuss Misses Privately With a Clear Step

Raise it early, privately, and with one specific example rather than a general impression. The trust damage in performance conversations almost always comes from surprise. If someone hears about a problem for the first time in a formal review, they reasonably wonder what else you've been sitting on. A short, early conversation is kinder than a polished late one.

The approach that works best for me is starting with the work instead of the person. I'll say something like: here's what I expected on this, here's what happened, what got in the way? That last question matters most. Often the answer is something I caused, an unclear priority or a handoff nobody owned. In a small software company, a missed deadline is frequently a process problem dressed up as a people problem.

Then we agree on one next step and a date to look at it again. One step, rather than a performance plan with ten bullet points, because people can fix one thing. Customer support is a good example for us. With 1,700+ brokerages on Paperless Pipeline, reply quality matters, so when someone's replies slip, the next step is concrete: pick three recent tickets and rewrite one together. Most people turn it around once the expectation is clear and they don't feel ambushed.

<aside class="expert"><img src="https://featured-com-images.s3.us-west-1.amazonaws.com/profile-images/96d53074-fe56-403f-a453-cf0df8431c95.webp" alt="Dane Maxwell" loading="lazy"><p><a href="https://www.linkedin.com/in/dane-maxwell-b7105b5b" rel="nofollow">Dane Maxwell</a>, Founder, <a href="https://www.paperlesspipeline.com" rel="noopener">Paperless Pipeline</a></p></aside>

---

### Reconstruct Assignments and Codify Workflow Checkpoints

In scaled organizations, underperformance is a signal that knowledge has not become a method. People appear inconsistent when success depends on unwritten shortcuts learned through proximity. I ask the employee to walk through the last assignment, including decisions that seemed too obvious to mention.

That reconstruction has turned difficult discussions into process improvements. When a gap appears, capture the missing checkpoint in the workflow and ask the employee to test the revised version on the next comparable task. This avoids implying that every miss reflects poor effort. It also creates a fairer standard for the next person hired or moved between teams. The employee leaves with a reset, and the organization gains a stronger operating memory.

<aside class="expert"><img src="https://featured-com-images.s3.us-west-1.amazonaws.com/profile-images/a9d39bda-b03a-44ea-ab93-e90ff1a8a519.webp" alt="Dawood Bukhari" loading="lazy"><p><a href="https://www.linkedin.com/in/dawoodbukhari" rel="nofollow">Dawood Bukhari</a>, CEO, <a href="https://www.digitalwebsolutions.com" rel="noopener">Digital Web Solutions</a></p></aside>

---

### Map Timelines to Diagnose Delayed Reports

A missed commitment should be examined as a process failure before it is treated as a character failure. I ask for a timeline of the work, where momentum slowed, decisions waited, or assumptions changed. Timelines convert defensiveness into inquiry and reveal the obstacle is skill, capacity, or unclear priorities.

That approach helped in a conversation with someone whose reports arrived incomplete. The timeline showed that research was sound but the final review had no protected place on the calendar. A scheduled review window and a narrower draft created a rhythm. Accountability remained clear, yet the remedy matched the cause.

<aside class="expert"><img src="https://featured-com-images.s3.us-west-1.amazonaws.com/profile-images/c45151ff-5732-4de7-967f-7fe75284eee6.webp" alt="Reid Breitman" loading="lazy"><p><a href="https://www.linkedin.com/in/reid-breitman-7049a512a" rel="nofollow">Reid Breitman</a>, Personal Injury Lawyer, <a href="https://kuzyklaw.com" rel="noopener">Kuzyk Law Personal Injury &amp; Car Accident Lawyers</a></p></aside>

---

### Identify Order Mistakes and Test a Fix

I raise it the same week I notice it, in a short private chat that starts with what I saw rather than what I think it means. Something like: three of the cable orders you packed on Monday went out with the wrong connector type listed on the note, what happened there? That question does most of the work. Half the time the answer is a process problem I created, a confusing product name or a pick list that is easy to misread, and the conversation ends with me fixing my own mess.

The trust damage usually comes from waiting. If you sit on a performance worry for a month, you start collecting evidence, the person can feel the mood change without knowing why, and by the time you speak it feels like an ambush. Early feels awkward for about thirty seconds and then it is just two people sorting out a problem.

The approach that has worked best for me is to end with one agreed thing to try and a day to look at it again later that week. Not a list of five improvements. One change, checked soon, so the person gets a quick win and I get a clear read on whether it was a skills gap or a one-off bad week.

<aside class="expert"><img src="https://featured-com-images.s3.us-west-1.amazonaws.com/profile-images/1cba23c3-0d87-42a4-884a-a282c1e723ca.webp" alt="Jake Wardle" loading="lazy"><p><a href="https://www.linkedin.com/in/jake-wardle-942253262" rel="nofollow">Jake Wardle</a>, Founder, <a href="https://evcablehub.co.uk" rel="noopener">EV Cable Hub</a></p></aside>

---

### Employ the Sandwich Method With Self-Assessment

When an employee's performance starts falling short, I prefer to address it directly and privately. If the conversation is clearly about helping them improve rather than making them feel like they are being pushed out, it is much easier to preserve trust.

One approach that works well for me is the sandwich method. I start with what they are doing well, then explain clearly what needs to improve and why, and finish by reinforcing the strengths I know they already have. That structure helps keep the conversation constructive. The employee still understands that the issue is serious, but they also leave knowing that we see their value and believe they can improve.

Asking also how they feel about their performance and what they want to improve on is a good strategy for me, because we get to hear their assessment of themselves, the actions they plan to take, or the reasons why they're falling short on certain aspects.

<aside class="expert"><img src="https://featured-com-images.s3.us-west-1.amazonaws.com/profile-images/bd8f6abb-7e1a-411a-a2db-2608e4d52934.webp" alt="Mr Charles Liu" loading="lazy"><p><a href="https://www.linkedin.com/in/charles-liu-042b9124" rel="nofollow">Mr Charles Liu</a>, Marketing Director, <a href="https://www.cubicpromote.com.au" rel="noopener">Cubic Promote</a></p></aside>

---

### Debug Engineering Mismatches as Partners

With engineers, a performance dip is often a sign of a mismatch, not a lack of effort. A developer who flew through greenfield work gets moved onto a legacy integration, and suddenly every estimate slips. If you open with "your performance is down," you've already lost them, because they know they're working as hard as ever. So I open with something specific we can both see, then a question. For example: "Your last few pull requests needed two review rounds instead of one. What's different about this work?" Nine times out of ten, the answer points to the real problem: unclear requirements, an unfamiliar part of the codebase, something going on outside work. Then we agree on one next step, not a five-point improvement plan. Maybe it's pairing with the person who knows that module for a week, then a short check-in. People can commit to one concrete change. A list of shortcomings just makes them defensive. The conversation shouldn't feel like a verdict. It should feel like the two of us debugging the situation together.

<aside class="expert"><img src="https://featured-com-images.s3.us-west-1.amazonaws.com/profile-images/a042eae9-3a52-41a4-bdec-3c19d05846fe.webp" alt="Marina Portna" loading="lazy"><p><a href="https://www.linkedin.com/in/marina-portna" rel="nofollow">Marina Portna</a>, CEO &amp; Founder, <a href="https://jobadvice.agency" rel="noopener">Job Advice Agency</a></p></aside>

---

### Celebrate Near-Term Milestone Recovery

Tie the conversation to a specific milestone the employee can hit soon, and say up front that you will mark it when they hit it. A talk that only names the gap leaves the employee with nothing to aim at except avoiding more criticism. A talk that ends with "when the next client handoff goes out clean, we'll acknowledge it" gives them a target and a reason to believe the record will show the recovery, not just the dip.

Then follow through. Recognizing progress out loud matters most, and a tangible mark backs it up: a desk award with the milestone engraved on it tells the employee the improvement counted. Most managers recognize only the finished result.

<aside class="expert"><img src="https://featured-com-images.s3.us-west-1.amazonaws.com/profile-images/e7abec53-da6c-4e73-816f-ef0915cead8f.webp" alt="Vincent Nero CRP" loading="lazy"><p><a href="https://www.linkedin.com/in/vincentnero" rel="nofollow">Vincent Nero CRP</a>, VP of Sales and Service, <a href="https://www.awards.com" rel="noopener">Awards.com</a></p></aside>

---

### Match Development Paths to Skill Deficits

When an employee's performance falls short, I believe it is important to address it early rather than wait until the next performance review. But how we approach the conversation matters just as much as the feedback itself.

I would start with a private conversation and explain the concern using specific examples. Instead of immediately pointing out what went wrong, I would give the employee a chance to share their perspective. Sometimes, the issue may be related to unclear expectations, workload, lack of guidance, or a skill they need to develop.

Once we understand the reason, we can identify the areas where the employee needs to improve and any skill gaps that may be affecting their work. Based on that, we can suggest relevant learning opportunities that match their role and development needs, rather than giving them general training that may not be useful.

We use Skill Lake to organize learning activities and track employee progress. This helps us connect learning with the skills employees need to develop in their roles.

I believe these conversations should make employees feel supported, not judged. When managers listen, provide clear feedback, and help employees understand what they can work on next, a difficult performance discussion can become a positive step towards improvement.

<aside class="expert"><img src="https://featured-com-images.s3.us-west-1.amazonaws.com/profile-images/e49f4e2c-e4d9-483f-99ef-c8e4f5f8e159.webp" alt="Christy Maria Jose" loading="lazy"><p><a href="https://www.linkedin.com/in/christy-maria-jose" rel="nofollow">Christy Maria Jose</a>, Senior Manager - People Ops, <a href="https://www.skilllake.com" rel="noopener">Skill Lake</a></p></aside>

---

### Probe Choices Before You Name Ownership

Employees lose motivation when a manager arrives with a fixed narrative. That is the same mistake that weakens testimony in litigation, because the details that do not fit the theory are the most useful. I prepare for a performance conversation by reviewing the assignment, the instructions, and the timing, then leave room for information I may not have.

A productive opening is, "Help me understand this choice." The phrase matters only if the answer can change the plan. After listening, the discussion ends with one priority, one owner, and one deadline. That structure shows precisely what must change and how progress will be assessed.

<aside class="expert"><img src="https://featured-com-images.s3.us-west-1.amazonaws.com/profile-images/2984e3d7-02af-4def-b7bf-abd1dde21161.webp" alt="Chrissy Grigor" loading="lazy"><p><a href="https://www.linkedin.com/in/chrissygrigor" rel="nofollow">Chrissy Grigor</a>, Personal Injury Lawyer &amp; Founder, <a href="https://grigorlaw.com" rel="noopener">Grigor Law Injury &amp; Car Accident Lawyers</a></p></aside>

---

### Replace Vague Advice With Measurable Accountability

We avoid the compliment-critique-compliment approach because employees can hear it as a judgment rather than genuine feedback. A better way to begin is to acknowledge the situation and invite the employee to review the evidence with us. This creates room for an honest discussion without making the employee feel judged. It also helps both sides focus on what needs to change.

One conversation improved when we replaced the vague advice to be more proactive with a clear review of delayed decisions, missing information, and unclear ownership. The employee pointed out an issue that our dashboards had not revealed. We agreed on clear decision-making responsibilities and a review of exceptions instead of simply promising better communication. Accountability means making expectations clear, barriers visible, and progress measurable.

<aside class="expert"><img src="https://featured-com-images.s3.us-west-1.amazonaws.com/profile-images/931c441a-f6d8-4bb6-a9c8-10f8ef66caef.webp" alt="Brian Lebeau" loading="lazy"><p><a href="https://www.linkedin.com/in/brian-lebeau-b7773a1" rel="nofollow">Brian Lebeau</a>, CEO, <a href="https://atticprojectscompany.com" rel="noopener">Attic Projects Company</a></p></aside>

---

### Demand Regular Logs to Build Discipline

Every week I had a one-on-one with my direct reports, and I asked the same questions every time: what did you do, what was successful, what was unsuccessful, what will you do next week. At the lower levels it was daily tracking, sometimes even hourly.

I make everyone report, the same questions every week. Without documented proof of what you do at work, I don't know how to manage you. Only discipline changes our habits.

<aside class="expert"><img src="https://featured-com-images.s3.us-west-1.amazonaws.com/profile-image/1bf66402-2dca-4106-9373-bd7615f6a4a1.webp" alt="Luba Inz" loading="lazy"><p><a href="https://www.linkedin.com/in/luba-inz" rel="nofollow">Luba Inz</a>, Founder, <a href="https://efficiencysprint.com" rel="noopener">Efficiency Sprint</a></p></aside>

---

### Define Observable Actions Before Check-Ins

The strongest performance conversations produce a next action that can be observed without interpretation. "Communicate better" is too subjective to coach fairly. "Send the customer a written update within one business day when a timeline changes" gives both manager and employee something concrete to review.

I have learned that ending with a question improves commitment, "What will you do differently before our next check-in?" The answer reveals whether the employee understands the expectation and has a workable plan. If the response remains vague, the manager should keep refining the action instead of assuming alignment. This approach protects motivation because progress is visible. It also protects the business because the conversation produces an operational commitment, not just an apology or a general intention to improve.

<aside class="expert"><img src="https://featured-com-images.s3.us-west-1.amazonaws.com/profile-images/8465c483-80a9-4e14-a47c-8148827582fa.webp" alt="Xavier Berkness" loading="lazy"><p><a href="https://www.linkedin.com/in/xavierberkness" rel="nofollow">Xavier Berkness</a>, President &amp; CTO, <a href="https://percengage.com" rel="noopener">PERC Engage</a></p></aside>

---

### Explore Monthly Barriers Without Verdicts

After more than twenty years running a company in Hamburg, I open an early performance talk with a question about the work, never a verdict on the person. I took that habit from our numbers, where an odd line in the accounts is a question first and an accusation never. People deserve at least the same courtesy as a spreadsheet. Asking 'what got in the way this month?' brings out the real cause while the employee still feels you are on their side.

<aside class="expert"><img src="https://featured-com-images.s3.us-west-1.amazonaws.com/profile-images/1493646b-6b57-4156-9cbc-f3deb86a5e51.webp" alt="Jens Hagel" loading="lazy"><p><a href="https://www.linkedin.com/in/jens-hagel-77671549" rel="nofollow">Jens Hagel</a>, Co-Founder, <a href="https://www.yupana.de" rel="noopener">Yupana</a></p></aside>

## Related

- [How Teams Turn Workplace Disagreement Into Better Decisions](https://economistzone.com/qa/how-teams-turn-workplace-disagreement-into-better-decisions.md)
- [How to Get Delayed Cross-Functional Projects Back on Track](https://economistzone.com/qa/how-to-get-delayed-cross-functional-projects-back-on-track.md)
- [Customer Onboarding Choices That Lift First‑Week Use Without Raising Support Costs](https://economistzone.com/qa/customer-onboarding-choices-that-lift-firstweek-use-without-raising-support-costs.md)
- [How Workplace Leaders Delegate Decisions Without Losing Accountability](https://economistzone.com/qa/how-workplace-leaders-delegate-decisions-without-losing-accountability.md)
