Compassionate Employee Relations for Performance Issues

The step I take earliest in the process is ensuring the employee and I are operating from the same definition of success. That means the goals are known, shared, and transparent. Ideally, they've had a hand in creating them. This is the part that matters most: if someone joins mid-project or mid-engagement and those goals were already set, they need the explicit right to push back. Can they say the target is unrealistic, or that the tools don't support hitting it? Can we reset or restate goals collaboratively? That conversation, early, prevents so much downstream conflict. Then we establish regular check-ins so we both know where we stand against the target. And critically, we define what performing looks like, not just what underperforming looks like. Once that foundation is clear and collaborative, handling sustained underperformance becomes a conversation about what's changed or what's blocking them, not a surprise.

I run Twin Roofing (a division of Twin Metals in MA) and I've built the company since 2007 on "do the work right and stand behind it," so underperformance is a real safety/quality issue, not a vibe problem. I handle it by keeping it compassionate in tone but ruthless about the standard: we talk about the specific install output (layout, flashing, trim, cleanup), what "done" means, and what needs to change immediately.

My early step that cuts conflict is a same-day "walk-the-work" on the actual jobsite with the person—no office debates, no phone back-and-forth. We look at the roof together, I point to the exact spots that don't meet our standard, and I ask them to tell me what they see and how they'd fix it; it turns vague criticism into concrete agreement.

Example: on the Billerica Country Club job (strip, CertainTeed heather blend, new rake/fascia metal), if someone's trim work is inconsistent, we don't argue intentions—we put eyes on the rake line and fascia transitions and set a rework plan before the next section moves forward. It's transparent, it protects the finished roof, and it gives the person a fair shot because the target is visible and specific.

If it's sustained, I keep it simple: clear expectations in writing for the next phase of work, tighter check-ins, and accountability tied to the next install milestone. If they rebound, great—if not, the outcome is clear and nobody's surprised.

Sustained underperformance is one of the hardest situations a manager handles, and most managers get it wrong in the same way. They wait too long to name the problem clearly, hoping it will self correct, and then deliver the hard conversation too late, when the path to improvement is already narrower than it needed to be. The kindest version of this process is the honest one, started earlier than feels comfortable.

The approach I use is built around one principle. An employee should never be surprised by a formal performance conversation. If the first time someone hears they're underperforming is in a documented review, the manager has already failed. The documented conversation should be confirming what's already been said in writing, repeatedly, in smaller conversations leading up to it. That continuity is what makes the process feel fair, because the employee has had real time and real feedback to change before consequences arrive.

The single step early in the process that reduces conflict most is writing down the specific gap between expected performance and observed performance, in the employee's own words after the first conversation. Not the manager's words. The employee's. After the initial feedback conversation, I ask them to send a short summary of what they heard, what they think is happening, and what they plan to do about it. That document becomes the shared reference point for every conversation that follows.

This does three things. It confirms the employee actually understood the feedback, because people often hear a softer version than was delivered. It surfaces disagreement early, when it can still be discussed, rather than later when it becomes a grievance. And it creates a written record built from the employee's perspective, which changes the tone of the process from something being done to them into something they're participating in.

When the process works, most situations resolve inside it. The employee either improves, or they come to the conclusion themselves that the role isn't right, which is a much better outcome than being managed out. When the process doesn't work, the eventual parting conversation is shorter, cleaner, and less likely to end in dispute, because the written history makes the outcome unsurprising.

The underlying principle is that compassion in performance management is about being clear. People can handle hard truths delivered early with respect.

The one early step that has consistently reduced conflict: name the gap before it becomes a pattern.

Most underperformance conversations happen too late — after the manager has been frustrated for weeks and the employee has no idea anything is wrong. By that point, the conversation is loaded with accumulated resentment, and the employee feels blindsided. That dynamic almost always ends badly regardless of outcome.

At Dynaris, the practice I implemented is what I call a "gap naming" conversation — a short, specific exchange at the first sign of underperformance rather than waiting for a formal review cycle. It sounds like this: "I want to flag something I've noticed in the past two weeks and understand what's going on from your side." That framing does a few important things.

First, it's not an accusation — it's an observation that invites context. Sometimes what looks like underperformance has a clear explanation: a personal situation, a misunderstood priority, a tooling problem nobody told me about. The early conversation surfaces those explanations before they compound.

Second, it creates a clear timestamp. Both parties now know the gap was acknowledged on a specific date. That removes the "I had no idea" defense later and removes the "you knew for months and said nothing" grievance from the other direction.

Third, it forces me to be specific. I can't say "you're underperforming" in a gap naming conversation — I have to say exactly what I've observed. That discipline benefits the employee (they get actionable feedback) and benefits me (it stops vague impressions from hardening into unfair conclusions).

Compassion and clarity aren't opposites. The most compassionate thing you can do for someone who's struggling is tell them early, specifically, and without drama.

As a leadership team member at The Roof Guys, I oversee crews across Texas and Oklahoma where we back our workmanship with a 10-year labor warranty. My perspective is shaped by maintaining a 24/7 emergency response and our company standard that a supervisor must be on-site at all times.

I handle underperformance by tying feedback directly to our "system-focused assessment" standards rather than personal criticism. If a technician misses a detail on a pipe boot or chimney flashing, we review the failure as a technical breach of the 10-year warranty we promise our clients.

The early step that reduces conflict is requiring high-resolution photo documentation of the decking and underlayment before any shingles are installed. This visual evidence removes the "he-said, she-said" dynamic and forces an objective comparison against our professional installation checklist.

During a recent hurricane response, we used this photo-first approach to coach a team member struggling with wind-driven rain repairs. By comparing their photos to our protocol for UL 2218 Class 4 impact-resistant materials, we identified a specific spacing issue with the fasteners, turning a performance gap into a clear, technical correction.

At Tibicle, underperformance rarely comes as a surprise because our sprint structure makes output visible every week. When someone is struggling, the data shows up in missed tasks, incomplete reviews, or recurring blockers before it becomes a serious problem.

The one step I take early that consistently reduces conflict is documenting the specific pattern before having the conversation. Not impressions. Specific sprint data. Three consecutive sprints where tasks were delayed. Two code reviews flagged for the same recurring issue. Something the person can see with their own eyes rather than dispute as a manager's opinion.

When you walk into that conversation with documented evidence instead of a feeling, the discussion shifts immediately. The developer cannot argue with their own sprint history. More importantly, they often already know something is wrong and are relieved someone is addressing it directly rather than letting it fester.

From there the conversation becomes practical. What is getting in the way and what needs to change by the next sprint review. Clear timeline, clear expectation, no ambiguity. Most performance issues I have handled this way resolved within two sprint cycles because the person finally had a specific target to hit rather than vague feedback to interpret.

At Comligo, we handle sustained underperformance by first looking for barriers, not blame. When a teacher's student ratings drop, we ask what may be getting in the way: tools, lesson clarity, workload, or burnout.

One early step that helps is a root-cause reflection. It turns the conversation from "you are failing" into "what needs to change for you to meet the standard?" Then we agree on a 30-day support plan with clear expectations. This approach has helped 75% of struggling instructors recover while keeping trust intact.

Managing operations across two busy storage facilities on Aquidneck Island means I'm constantly balancing customer experience with team accountability. When underperformance shows up—whether it's inconsistent cleanliness standards, lapses in access security protocol, or customer interactions that don't reflect our reputation—I’ve learned that waiting makes everything harder.

The one early step that consistently changes outcomes for me: I anchor the conversation to the customer impact, not the person's character. At Middletown Self Storage, our reputation in Newport, Middletown, and Portsmouth is genuinely everything—customers like Lisa and Ron have trusted us for years. So when I see a gap, I connect it directly to what a real customer would experience walking into that unit or calling for help, making the standard concrete and observable rather than abstract.

I also involve the team member in defining what "good" looks like before any formal process starts. I ask them to walk me through what the correct procedure should be. When people articulate the standard themselves, ownership shifts—and conflict drops almost immediately because they've removed the "I didn't know" exit.

The compassion piece comes from separating the person from the pattern. I make it clear I'm addressing a repeated behavior with a real operational consequence, not judging someone's work ethic wholesale. That distinction keeps the conversation productive and keeps good people from shutting down.

With over 20 years in manufacturing roles like assembly line manager and plant scheduler, I've seen that underperformance often stems from people lacking the right tools to see their own progress. My servant-hearted leadership style focuses on providing real-time visibility so team members can own their outcomes rather than feeling attacked during reviews.

The early step I take is moving the individual toward frontline ownership using Thrive's digital goal boards and real-time audits. By giving an operator direct access to their own performance data, the conversation shifts from a subjective critique to a collaborative problem-solving session based on "at-the-source" feedback.

We've seen this work with partners like Assa Abloy, who transitioned from "manual chaos" to a connected system where everyone sees the same screen. When an employee uses the Thrive HR module to track their own training matrix and certifications, they gain the clarity needed to align with company standards without a supervisor hovering over them.

Compassion in operations means replacing lagging indicators with instant visual cues that allow a person to self-correct. This transparency reduces conflict because the software acts as a neutral partner, highlighting exactly where the process is failing so we can fix the system together.

Underperformance becomes combustible when companies rely on impressions instead of operating standards. A compassionate process starts with precise expectations, recent examples, and a realistic improvement window. Transparency matters because people can handle bad news better than mixed signals. Consistency matters because exceptions create resentment across the broader team.

The early step I have found most effective is manager alignment before the first meeting. Leaders should agree on facts, desired outcomes, and available support before speaking. That prevents contradictory messages, emotional escalation, and unnecessary backtracking during the process. Employees respond with less resistance when the organization sounds coherent and fair.

As co-owner of a Bozeman property management firm, I oversee a portfolio with a 98% occupancy rate and a 48-hour maintenance response guarantee. Managing high-stakes rentals across Southwest Montana requires aligning my team with these specific, measurable performance benchmarks.

I handle underperformance by using our online owner portal to provide total transparency on where maintenance timelines or tenant communications are lagging. We approach these gaps as local partners rather than a corporation, focusing on how a delay in a Big Sky or Livingston repair impacts the property's long-term value.

The early step I take is performing an internal audit modeled after our "free rental analysis" to determine if the issue is a market shift or an operational failure. Comparing real-time activity against our 48-hour response standard removes ambiguity and ensures we are meeting the professional-grade management our owners expect.

I handle sustained underperformance by running a simple, shared Customer Success playbook that sets clear standards, owners, SLAs, and escalation steps. We make issues visible and transparent by recording outcomes and misses against a single health score and reviewing them on one shared dashboard so everyone sees the same facts. The one early step I take to reduce conflict is to trigger the agreed health-score threshold with a named owner and a documented runbook action. That named handoff focuses conversations on concrete next steps rather than blame and keeps the response aligned with company standards.

My biggest best practice is to define performance expectations early and making them as clear and measurable as possible from day one.

Along with this, I normalize talking about performance consistently from the jump. That establishes this as a normal part of the role, so if or when underperformance does happen, it removes a lot of the ambiguity and emotion from the conversation. Instead, it becomes closer to a conversation looking at clearly defined expectations that have already been aligned on. I find that allows me to be both direct and compassionate at the same time.

Overall, I think transparency is respect with your team. When people always know where they stand, it creates a more grounded, fair environment and leads to overall better outcomes for all.

Performance rarely collapses in someone's first month. So I always evaluate a person based on their full track record with us, not just the last two or three weeks. Context matters, and a rough patch looks completely different against a strong history.

We run consistent 1-on-1s where everything can be discussed openly. Employees also know they can take PTO whenever they need it, no questions asked. That combination builds the kind of working relationship where problems surface early instead of quietly building into something bigger.

When performance drops for a legitimate reason, that context usually comes out in conversation. When it is deliberate disengagement, it shows up clearly against the backdrop of the rest of the team. The two situations look very different, and handling them the same way is a mistake.

The best move is usually pulling someone aside to talk privately. Let them explain their side before trying to fix anything. When we started Jacksonville Maids, I noticed that simply asking questions instead of assuming things stopped a lot of fights before they began. It sounds simple, but actually listening changes the whole dynamic. Don't guess what happened. Just ask.

I approach financial advising by prioritizing a deep understanding of each client's "goals, fears, values, and long-term vision" over mere market performance. When confronted with sustained underperformance, my initial action is always to pivot the discussion back to these fundamental personal objectives.

This crucial early step involves revisiting the core "real-life circumstances" and aspirational goals we outlined together from the beginning. By asking specific, clarifying questions, we effectively reconnect clients to their underlying purpose for pursuing financial growth.

This re-grounding helps clients contextualize market fluctuations, like those detailed in our March and April 2025 Market Updates, within their larger, personalized strategy. It fosters confidence and clarity, allowing us to collaboratively refine practical action plans aligned with their true priorities instead of reacting with generic advice.

Most of my work is in wellness, but I've noticed that small goals and frequent check-ins are what actually fix nagging issues. When we start, I like to pick just one specific thing to tackle. It almost always lowers the stress immediately. That kind of simple start is exactly how we get the work to stick.

If an employee is underperforming consistently, it will never be because I didn't try to address the issue. I'm very conscious of the fact that my human capital is my most important and costly resource, and I'm going to do everything I can to get my money's worth. That means keeping those underperformers on staff and helping them improve rather than wasting money on another round of hiring. The less formal this support is, the better. Performance improvement plans have been given a bad name by companies that use them as a precursor to firing someone.