People Management: How Managers Decide to Coach, Reassign, or Part Ways

When you’re running a three-person team, every role carries the entire product surface. There’s no room for someone who can execute one thing well if the role requires three. So the decision to part ways or change the role isn’t about whether someone is “underperforming” in the abstract. It’s about whether they can carry the actual scope the team needs them to carry.

The practice that turned every underperformance conversation I’ve had into a clearer outcome: ask the person to describe what they think their role is, then stop talking. Count to five in your head. Do not fill the silence.

The first time I used this, the person I was managing listed four things they thought they were responsible for. The actual role required seven. The gap wasn’t effort or aptitude. It was that we’d never aligned on what “your role” meant in an organization where everyone is doing product, growth, and operations at the same time. They thought they were succeeding because they were executing against their mental model of the job. I thought they were falling short because I was measuring them against a different model I’d never articulated.

Once we had the gap visible, the conversation shifted from “you’re underperforming” to “here’s what the role actually requires, can you carry that or do we need to redesign this?” In that case, they could. We added two responsibilities to their plate, removed one that someone else could absorb faster, and the underperformance disappeared because the role finally matched what the team actually needed.

The second time I used it, the person described a role that was narrower than what we’d hired them to do, and when I walked through the full scope, they were clear they didn’t want to carry it. That’s the conversation that leads to parting ways, but it’s not adversarial when both people can see the same gap. The person left knowing the role didn’t fit, not feeling like they’d failed.

The phrase I return to when the conversation gets tense: “I need someone in this role who can do X, Y, and Z without me in the loop. Can you do that, or should we redesign the role so you’re doing what you’re best at?” It names the actual requirement and gives them the option to self-select rather than making it feel like a performance judgment.

In a three-person team, clarity is cheaper than coaching. If the role isn’t clear, coaching just optimizes the wrong thing.

Bootstrapping two companies means you can’t afford to carry people for long, but you also can’t afford to keep replacing them. So the decision framework is pretty simple: is the gap a skill problem or a will problem.

Skill problems are fixable. If someone genuinely doesn’t know how to do something and wants to learn, coaching works. I’ll get more specific with expectations, set a 30-day window with clear deliverables, and check in weekly. Most of the time if you’re precise enough about what “good” actually looks like, people surprise you.

Will problems are different. If someone knows what’s expected and consistently finds reasons why it’s someone else’s fault or why the bar is unreasonable, that’s not a coaching conversation. That’s an exit conversation, and delaying it hurts the whole team more than the person leaving.

The phrase that changed how I handle these situations: “let me show you what done looks like.” Not explaining, not giving feedback in the abstract, just showing the standard visually or with a real example. It removes ambiguity immediately. Either the person can meet that bar and now knows exactly what to aim for, or they see it and you can both tell the gap is too wide.

The moment I stopped treating underperformance as a sensitivity issue and started treating it as a clarity issue, outcomes got better for everyone, including the people who eventually moved on.

The framework we use for underperformance is a three-gap triage: is this a skill gap, a fit gap, or a signal gap? The action depends entirely on which one you’re looking at, and confusing them is where most managers cause harm.

A skill gap means the person has the raw capability and motivation but is missing specific mechanics for the role — they’d close it with structured coaching, feedback loops, and 6-8 weeks of deliberate practice. Intensify coaching. The failure mode here is exiting someone who was 90 days away from clearing the bar.

A fit gap means the person has strong capability but the shape of the role isn’t drawing on it. They’d be a top performer in a different job at the same company. Reassignment. The failure mode is running a PIP that’s essentially punishing someone for being miscast — the outcome is usually a resentful exit that the org treats as their failure when it was a placement error.

A signal gap means the person’s performance is being read wrong by the org — either because their work is invisible (usually cross-functional roles that don’t show up in dashboards) or the metrics measuring them are proxies for the wrong thing. Fix the measurement before touching the person. The failure mode is exiting someone who was actually doing the job well but couldn’t demonstrate it in the system.

To decide which gap it is, the one diagnostic I trust most is a 30-minute conversation where you ask the person: “walk me through what a great week in this role looks like to you, then walk me through what actually happens.” The gap between those two paragraphs almost always tells you which of the three you’re in. If they can describe great and it matches the job — skill gap. If they describe a great week that’s actually a different job — fit gap. If they describe great and it matches, but you don’t see it happening because you can’t see it — signal gap.

Two things I’ve learned to avoid: (1) running the PIP as documentation for the exit you’ve already decided on — this is dishonest and everyone knows it. (2) Delaying the conversation past two months of misalignment, because at that point the person has usually mentally checked out and no coaching path will land. The kindest move for someone in the wrong role is to be the first person who tells them clearly.

At Sunny Glen Children’s Home, I decide on underperformance by weighing heart for the mission against real impact on the kids. We’ve served more than 25,000 children since 1936, so I ask: does this person still show care for abused or neglected youth in our Rio Grande Valley community, and can coaching close the gap fast enough? If yes, we intensify coaching with weekly goals tied to build care, residential services, or SIL at the Allen House. If the skills fit better elsewhere, we change their role, maybe shift someone stronger with older youth into transition support. We part ways only after those steps fail and the kids’ safety or trust is at risk. Our Christian-based focus on restoring hope means we don’t quit early, but we won’t let standards slip at a CARF Accredited place like ours.

One phrase that turned a case fair and clear is “Show me how this serves the child in front of us.” It cuts through excuses and forces honest talk. A staffer kept missing follow-through on family connections. Instead of soft feedback, I used that line in our sit-down. We mapped their strengths against what our kids actually need day to day. Turns out they thrived more in hands-on residential support than admin tasks. We reassigned, coached the new piece hard, and performance jumped. That practice builds trust through clear communication and helps us prioritize when resources are tight. It’s kept our team aligned so we can keep delivering comprehensive support without drama. I’m convinced this approach protects both people and the mission better than anything else I’ve seen.

Underperformance should be handled through evidence of trajectory, not a verdict on character. In agency environments, the danger is keeping someone in a role where every week increases hidden costs, slower execution, lower morale, and weaker confidence in quality standards. We examine whether the person is closing the gap faster after each feedback cycle, or simply repeating the same pattern with better explanations. If learning speed is rising, coaching still has value. If capability appears real but misapplied, changing the role can protect both the person and the team. If trajectory stays flat, parting ways becomes a clarity decision, not a punitive one.

One practice that helped was ending reviews with, “What will be different for others if this improves?” That question made expectations concrete and gave everyone a shared standard for fairness.

On a lean team the question isn’t coaching vs role change vs exit—it’s whether the time I’m spending to close the gap costs more than the problem I hired them to solve. If the answer is yes for two review cycles running, the decision is already made; I’m just delaying it. Prolonged ambiguity about someone’s fit is itself a management failure—the runway you spend hoping they turn around is runway you’re not spending on the work.

What changed this for me was borrowing a habit from how I audit SEO systems: weekly, regardless of how the week went. I write down, in one sentence, the specific outcome the role exists to produce, and review it every week against what actually shipped—not tasks, not effort, outcome. Once that sentence is on the table, the conversation stops being about the person and starts being about the gap. Coaching, role change, or exit usually becomes obvious to both sides at the same time. That’s what makes it fair.

The best underperformance decisions come from testing elasticity. Some people improve when expectations tighten, feedback becomes more frequent, and priorities narrow. Others improve briefly, then slip the moment structure is removed. That difference matters because sustainable performance should not depend on constant supervision. If progress only exists inside a highly managed environment, the leader may be rewarding compliance rather than solving the core issue.

I use one practice called support tapering. Expectations stay clear, but oversight is reduced in stages to see whether ownership holds. That approach creates a fairer outcome because it tests real readiness, not rehearsed improvement, and it makes a role change or separation much easier to justify with confidence.

Summary: So the next time you find yourself struggling with how to resolve underperformance in this area, ask yourself three questions. Will this person’s documented pattern of impact on guest experience and property readiness across several stays get better? In short, is this person taking ownership of the feedback provided previously? If so, then why? Is this a coachable skill or process gap, but one that this person is clearly willing and able to work through? Or has it become evident that the person’s strengths really and truly map better to other tasks (inventory restocking, specialized maintenance coordination, etc.)? Could the person’s quality of work, response times, and guest notes really and truly be predictable and consistently good?

If the root cause of the issue is a coachable skill or process gap, and this person is clearly willing to work through it, then subsequent steps are to provide intensified support via joint walkthroughs, detailed checklists, and scorecard follow-ups. This is best achieved through close daily check-ins and quality assurance audits prior to the next guest’s arrival.

If the person’s strengths really and truly map better to other tasks or responsibilities, then the next step is obviously to examine whether and how to adjust the person’s role. Finally, if after all support has been given, and with a reasonable amount of time, this person’s quality of work, response times, and guest notes have failed to improve or are inconsistent at best, then these folks must go. They simply can’t be trusted to provide a predictable quality of service. After all, the owner’s financial success rests squarely on the shoulders of your entire team.

Practice: The next time you’re faced with a tough decision about someone who should be doing better, always try to begin with an extremely objective side-by-side review of the facts. Tell them candidly: “Let’s pull the photos, checklists, and guest notes from your recent turnovers and compare them directly to the standards.” Have a large whiteboard handy and go through each scorecard in close sequence. Have them point out each positive and negative thing they can come up with. As you listen, you’ll be amazed by how quickly shortfalls look man-made; many of them really are.

Third month of check-ins with someone on my marketing team and I noticed I was writing notes after the call instead of during it. I was not coaching him by then, I was building a file. Now I go into these asking whether I am coaching the person or documenting them. If the honest answer is documenting, the decision is already made and I owe them that conversation now, not in 60 days. Some of the underperformance here turned out to be a role nobody wanted to rename. We moved 2 people sideways last year. Neither knows I nearly went the other way.

What I can’t settle is timing, because you can sit with someone for 6 months and call it fairness when it might just be me dodging a conversation. How do you tell which one it is while you are still in it?

Watch the account load before judging the performance. A strategist or rep carrying more than five active accounts will look like they’re underperforming even when the real problem is capacity, not skill. The practice that turned unclear cases into fair outcomes: check workload against results before deciding on coaching or an exit. If output dropped after their account count rose, the fix is redistribution, not a warning. If output was already weak at a normal load, that’s a real underperformance case and coaching should start immediately with a short, specific timeline. Mixing those two causes together is what makes underperformance conversations feel unfair. Separate capacity problems from skill problems first. It turns a vague conversation into a specific, defensible one, for the manager and the employee both.

To decide between coaching or role realignment vs separation for non-clinical employees, I focus on effort and adaptability. When an employee demonstrates high levels of effort in conjunction with temporary barriers requiring coaching, then coaching is indicated. When an employee demonstrates strong organizational alignment but is experiencing difficulty as it relates to their assigned tasks, role realignment is suggested. If an employee has demonstrated consistent poor performance relative to clearly stated expectations via written guidelines, separation is the best option to protect the organization’s operational efficiency. My most used management technique is a weekly 15-minute check-in to ensure alignment using the question, “What are the specific resources or support needed from leadership to meet this benchmark?” Using this question places the accountability for providing the required tools on management, while placing accountability for executing those requirements on the employee. The clarity provided by this type of question removes all ambiguity, which allows for measurable and equitable performance-based decisions.

The turning point in underperformance cases usually comes when the conversation moves from impressions to evidence. If someone keeps falling short, I review whether expectations were explicit, whether they had the tools to succeed, and whether improvement followed prior coaching. Organizations built around high standards often win because performance is defined in precise terms, with little room for ambiguity. That same discipline works in people management, especially when emotions start clouding judgment.

One practice has been especially effective, a mutual expectations memo written after the conversation, not before it. It captures what success now requires, what support will be given, and what timeline applies. That document creates fairness for both sides and makes the next step, coaching, reassignment, or separation, far clearer.

Most managers quickly fire underperforming employees missing their specific targets. But I always ask if the person lacks basic context or genuinely lacks the raw ability required for the job. Anyone who has dealt with this knows firing destroys team morale.

We hired a writer for our marketing team and she struggled to produce articles matching the tone of our legal buyers. I asked her to stop writing completely and focus strictly on interviewing our actual users. She possessed amazing conversational skills for this new task.

Here is another thing I have noticed about building a very strong team.

In my experience, employees excel when you match their natural strengths directly to the daily pain points of your target buyers. She started listening closely to the specific complaints of our law firm customers. Then she built our content around the exact customer voice.

As CEO of Netsurit I built the Dreams Program to put people first, which gives me a direct way to handle long-term shortfalls without guesswork. We start every performance talk by revisiting an employee’s stated personal goals, then check whether coaching can close the gap or if the current role simply blocks those goals.

This single step usually shows the right path. If the mismatch is clear after honest goal review, we explore a role shift inside the company while culture stays intact, the same approach that worked through our acquisitions. If alignment still fails, parting ways becomes the fair next move rather than endless coaching.

The phrase I use is “Does this work still move you toward the dreams you set?” It shifts the conversation from blame to fit and has produced clearer outcomes in every case I’ve applied it.

I stop assuming people are lazy and just ask what is blocking them. After we fixed a few bad scripts or lightened the load, I saw people turn around completely. It proved my snap judgments were usually wrong. I keep a one page 30-60-90 day plan and check in weekly to see if they are hitting the targets. This makes it obvious if we should keep coaching or move on.

I hate catching people off guard, so I lay out the problem, the help I can offer, and a deadline. Then I ask what they actually want. More coaching? A different seat? Or is it time to go? I picked up this approach at Joymore. It sounds intense, but being direct cuts the stress. One engineer moved from front-end to back-end work and things just clicked.

I just tell people straight up what the job needs now. It clears the air and shows if they need training or a different role. I tell them their past work counts, but the job has changed. I tried this with a long-time employee fighting new software. By acknowledging their experience while being clear about the new demands, the talk felt fair instead of like a punishment. They actually picked up the tools after that.

Managing team performance is crucial for strategic success. Decisions about coaching, role changes, or termination require careful assessment of individual skills, team dynamics, and business goals. Analyzing underperformance involves identifying constraints, whether external resources or internal motivations, and using performance metrics to inform actions.

Coming from a role where precision and accountability are non-negotiable in our industry, I’ve learned to separate capability from fit early. When someone consistently falls short, I ask myself: “Is this a skill gap I can close in 60 days, or a mismatch in how they work?” If it’s the former, I double down on coaching with clear weekly checkpoints. If it’s the latter, I have the honest conversation about finding a better fit, either internally or externally.

One practice that changed outcomes for me: the “Red-Yellow-Green” check-in. Every two weeks, I ask the person to self-assess where they are on key deliverables using those three colors. It forces self-awareness and gives me a real-time read on whether they see the gap. When someone consistently marks themselves green but the work says red, that’s a clarity problem we can address directly. When they mark yellow and ask for help, that’s coachable. It turns vague underperformance into a shared, measurable conversation, and it’s led to fair decisions on both sides.

I’ve become much slower about putting a label on someone’s performance. Earlier in my career, if a study wasn’t moving as smoothly as it should, my first instinct was to look at the person responsible for that part of the work. Over time, I realized that approach can miss what’s really going on.

There was one coordinator who seemed to need help with almost every new task. It would have been easy to think they just weren’t keeping up. Then one afternoon, while we were reviewing study files together, I noticed they had created their own checklist with pages of handwritten notes. They weren’t confused—they were trying to remember dozens of small requirements because they didn’t have a clear process to follow.

We scrapped the notebook and built a simple workflow that the whole team could use. A few weeks later, they didn’t need nearly as much support, and interestingly, other coordinators started using the same workflow because it made their jobs easier too.

That experience stayed with me. Now, before I decide someone is underperforming, I ask myself whether I’m looking at a people problem or a process problem. More often than I’d expected, improving the process has helped the person improve as well. It’s a question that’s saved me from making a lot of unfair assumptions over the years.