When Things Go Wrong

Problems between a manager and a direct report rarely arrive fully formed. They accumulate through small shifts in behavior that you register without noticing. The meeting where the report stopped pushing back. The deliverable that was technically on time but missing the usual care. The Slack message that used to get a quick reply and now sits for a day. None of these moments feels decisive on its own. Several of them together is a signal.

This guide walks you through the full arc of a difficult situation: reading the early signs, diagnosing the real problem, running the hard conversation, deciding whether to reposition or separate, and protecting the team on the other side. It is written for the manager who wants to handle these moments with clarity and honesty, because the alternative is the slow version that costs everyone more.

Reading the room before it falls apart

Early warning signs

Withdrawal from team discussions. Declining quality on routine work. A drop in energy during 1-on-1s. Rising friction with peers over minor issues. Longer response times. Missed details that used to get caught. A shift from proactive to reactive. None of these items is conclusive on its own. When several show up together over a few weeks, the pattern is telling you something.

Rough patch or systemic problem

Everyone has bad weeks. The question is whether what you are seeing is transient or persistent. A rough patch clears within two or three weeks once the trigger passes. A systemic problem keeps repeating in different forms. The deadline they missed last month turns into the deadline they miss this month, which turns into the retrospective where they cannot name why. When you see the same type of breakdown more than twice, stop treating it as a one-off and start treating it as a system.

Why managers see the signs late

You delay acknowledging the problem because the report was once performing well. You delay because the alternative is uncomfortable. You delay because you hope the issue will resolve itself. All three reasons are normal. All three make the eventual conversation harder and the outcome worse. The manager who catches the pattern at week four has far more options than the manager who catches it at week sixteen.

A lightweight early warning system

1. Weekly 1-on-1 check-ins with specific questions. Ask about energy, blockers, and any work that is feeling harder than it should. Generic "how are things" prompts rarely surface anything. Specific questions force specific answers.
2. Peer signal tracking. Notice what teammates are quietly routing around. Work that used to go through a report and no longer does is a signal, even when nobody has said anything out loud.
3. Output trend monitoring. Track delivery quality and timeliness across the last few months, not the last week. Trends reveal what individual incidents obscure.

Diagnosing the real problem

Most managers move directly from observing a problem to prescribing a solution. The diagnostic step between those two moments determines whether your intervention addresses the actual cause or treats a symptom. Getting it wrong wastes weeks and erodes trust on both sides.

Four sources of breakdown

Role fit. The report is in the wrong seat. Their natural strengths and the work they do every day are not aligned. A report with Analytical assigned to a customer-facing account management role will grind through every week. A report with Woo stuck in a deep-research role will quietly deteriorate. Neither person is broken. The seat is.

Skill or capability gap. The role requires something the report cannot yet do. This is a training problem, not a performance problem, and it responds to coaching, pairing, and time. The most common mistake here is treating a skill gap like a motivation problem and vice versa.

Motivation or engagement. Something outside of skill has broken the report's drive. It might be personal. It might be interpersonal. It might be structural. The cause matters less than the fact that the engine has gone cold, and engagement problems do not respond to pressure. They respond to diagnosis.

Environment. The system around the report is the actual problem. Unclear priorities, resource starvation, a toxic dynamic with a peer, a stakeholder who keeps shifting the target. When the environment is broken, swapping in a different person produces the same breakdown three months later.

Questions to ask yourself first

Before you confront the report, test yourself. Have my expectations been clear? Have I been consistent? Is anyone else on the team facing the same conditions and succeeding? Have I given enough feedback for the report to know there is a problem at all? If the answer to any of these is no, the first intervention is your own, not theirs.

Gathering signal from multiple perspectives

Talk to peers who work closely with the report. Review recent deliverables. Check the quality of the handoffs into and out of their work. Look for the gap between what the report thinks is happening and what others around them experience. The gap between internal and external view is often where the real diagnosis lives.

Strengths misalignment versus values misalignment

The distinction between these two types of misalignment determines the entire course of action. One is a positioning problem with a structural solution. The other is a compatibility problem that structural changes rarely resolve.

Strengths misalignment. The report is capable and well-intentioned. The work simply does not match what they do best. A report with Ideation stuck in a process-compliance role is frustrated every day, not because they are lazy, but because their wiring is starved. Repositioning them into a different role or a different blend of responsibilities usually resolves it.

Values misalignment. The report holds a worldview that is incompatible with the team's operating principles. They may be talented, but their instincts point in a direction the team cannot follow. Repositioning rarely fixes this. The mismatch travels with them wherever you move them.

How to tell them apart. Strengths misalignment shows up as frustration and underperformance in specific types of work. The report usually knows something is off. Values misalignment shows up as conflict over how decisions should get made, what "good" means, or how people should be treated. The report often believes they are right and the team is wrong.

The gray zone. Some situations look like values misalignment but are actually the result of prolonged strengths misalignment. A report stuck in the wrong role for too long can develop an adversarial posture that reads as a values problem. Distinguish carefully before concluding. The cost of confusing the two is the difference between a report you can save with a role change and a report you lose in a repositioning that was never going to work.

The hard conversation

Most managers either avoid difficult conversations entirely or deliver them without structure, causing unnecessary damage. Both failure modes stem from the same root: the manager did not prepare.

Conversation structure

1. What happened. Describe observable behavior. Not inference. Not interpretation. The specific actions and their pattern. "In the last four weeks, the Monday status updates have been submitted late three times, and the Q3 client call on the 14th was missed without notice."
2. Impact. Explain the effect on work, team, and outcomes. Be concrete. "The late updates forced the PM to chase three people Tuesday morning, and the missed client call damaged a relationship we spent eight weeks rebuilding."
3. What needs to change. State the specific shift you are asking for. Avoid generalities. "I need the Monday updates in by 10am, every week, without exception. I need client calls confirmed in advance and joined on time."
4. Support available. Name what you will do to help, and what the report needs to bring themselves. "I can clear the Tuesday planning meeting from your calendar to give you the morning back. I need you to tell me on Friday what you have committed to for the coming week."

Managing your own emotions

Walking into a hard conversation angry or anxious changes how you deliver it, and the report will remember how you said it as much as what you said. Prepare the content in writing first. Rehearse the opening out loud. Keep your tone level even when the content is hard. If you notice your voice tightening, slow down and take an extra beat before the next sentence.

When the report gets defensive, emotional, or shuts down

Slow down. Give them space to react without rushing to fill the silence. Acknowledge the emotion without abandoning the message. "I hear you. This is hard to hear, and I still need you to know that the pattern is real." If the conversation is no longer productive, pause and reschedule rather than push through. A second conversation with a clearer head beats a first conversation that ended in damage.

The follow-up

Document what was agreed in writing within 24 hours. Send it to the report. Schedule the next check-in on both of your calendars before you close the thread. Without follow-up, the conversation becomes advice rather than accountability, and the report will walk away unsure whether anything has actually changed.

The repositioning decision

Repositioning a report within the organization can preserve genuine talent and resolve a structural mismatch. It can also function as avoidance dressed up as optimism. The distinction lies in the conditions under which you pursue it.

When repositioning works

The report has genuine strengths that the organization can use somewhere else. Their current role is a poor match and a better match actually exists. The report wants to make the move and believes in it. The values are aligned even if the fit is not. All four conditions should hold before you commit.

When repositioning fails

The move is driven by your avoidance rather than a real fit. No role actually needs what the report offers. The report's own belief in the move is weak and you are dragging them across the line. The underlying issue is values, not role. In any of these cases, repositioning postpones the harder decision by three to six months and costs everyone more.

Designing a repositioning plan

1. Define the new responsibilities in writing. Vague moves produce vague outcomes. Write the new role with the same specificity you would write a new hire brief.
2. Set success criteria. What does "working" look like at 30 days? At 60 days? At 90 days? Get concrete.
3. Establish a defined timeline. Open-ended repositioning drifts. Name the review dates before the move happens.
4. Frame it honestly. Tell the report what is at stake and why this is the next step. The worst repositioning conversations are the ones dressed up as promotions. The report hears the truth eventually, and the dressing makes it worse when they do.

Evaluating at 30, 60, and 90 days

If the signals are clearly positive at 30 days, continue. If mixed, intervene early. If negative, face the next decision rather than delaying. The extension of a failing repositioning hurts everyone involved, including the report, who deserves a clear answer rather than a slow drift into the same ending.

Making the decision to separate

The decision to separate from a report rarely happens at the right time. Most managers wait until a triggering incident forces their hand. By then, the team has absorbed months of reduced performance, and the decision feels reactive rather than considered.

Decision inputs. Gather the documented history of performance issues, the interventions you attempted, the report's response to each, peer signals, and the current state of the team. Look at the whole arc, not just the most recent incident.

Separating what you feel from what you know. Write two lists. What do you know based on evidence? What do you feel based on history, loyalty, or guilt? Make the decision from the first list. Share the second list with a peer or coach who will push back on you.

The two futures test. Describe in writing what the team looks like in six months if the report stays. What will they be doing? What will have improved? What will still be broken? Then describe in writing what the team looks like in six months after a respectful separation. What becomes possible? What becomes harder? The comparison usually makes the decision obvious.

The exit

Once the decision is made, execution determines whether the separation is handled with clarity and respect or creates lasting damage for the report, the team, and you.

Logistics. Coordinate with HR before the conversation. Prepare the paperwork. Plan the sequence of the day. Know what you will and will not discuss.

Delivering the message. Be direct in the first 60 seconds. The report deserves to know immediately what the conversation is about. Avoid long preambles that create false hope. State the decision, give the primary reason in one or two sentences, and move to the logistical content.

What to offer and what not to offer. Offer dignity, clarity, logistical support, and an honest reference where warranted. Do not offer false reassurance, an extended renegotiation of the decision itself, or promises you cannot keep.

Communicating with the team. The team will notice the same day. Say something clear and true. Respect the departing report's privacy while giving the team enough to understand what is happening and to reset expectations for their own work. Silence creates worse stories than the truth.

Protecting the team through a departure

A departure creates a disruption that extends beyond the vacant seat. The remaining team members experience the change through their own lens: their workload, their security, their relationship with the person who left, and their confidence in your leadership.

The questions they will not ask directly

"Could this happen to me?" "Did leadership handle this fairly?" "Is my workload about to double?" Address these questions without waiting to be asked. You do not need to share the details of the departure to answer them. You need to say out loud what kind of team this is and what kind of manager you are.

Redistributing work

1. Critical and time-sensitive. Assign immediately with clear ownership and support. Do not leave the redistribution implicit. Say the names out loud.
2. Important but can wait. Hold briefly and reassign with intention. Use the pause to match the work to the right strengths rather than defaulting to whoever is nearest.
3. Can be stopped or descoped. Use the moment to cut work that was not serving the team anyway. A departure is a rare opportunity to remove a commitment that no longer earns its keep.

Watching for secondary effects

One departure sometimes triggers others. Watch for signs of disengagement in the reports most affected by the change. Check in 1-on-1 with everyone on the team within the first week after the exit. The quiet reports are the ones you need to check on most, because the loud ones will tell you what they think without being asked.

The honest retrospective

A separation that produces no learning is a separation that will repeat. Within 30 days of the departure, conduct a structured review of the entire arc: hiring, onboarding, management, intervention, and exit.

Classify the failure.

• Hiring failure. The wrong person was selected at the start.
• Onboarding failure. The person was set up poorly in their first 90 days.
• Management failure. Feedback, expectations, or interventions got missed or mishandled along the way.
• Environmental failure. The role or team context made success impossible regardless of who sat in the seat.

Most separations have elements from more than one category. Name them clearly rather than settling on a single explanation that lets you off the hook.

The manager's own work

Every difficult employee situation reveals information about your own tendencies, blind spots, and defaults. The manager who uses these situations only as data about the report misses half the available learning.

If separations or performance issues follow the same pattern across multiple reports, the variable is you. That is not a failure verdict. It is a development signal. Find a peer, a coach, or a mentor who will tell you what you are missing. Run your own strengths through the same filter you use on your reports. A manager high in Harmony will delay hard conversations by default. A manager high in Command will end them too quickly. A manager high in Responsibility will take on work that belonged to the report and then resent them for not doing it. Your strengths are shaping the situations you keep walking into, whether you see them or not.

Practical next step

Pick the most uncomfortable situation on your team right now. Open a blank document and write three things: what you have actually observed in the last four weeks, what you have told the report about it, and what the report has said back to you. If the second column is empty or thin, the first intervention is yours. Have the conversation this week, using the four-part structure in this guide, and document what you agreed on within 24 hours.

Difficult employee situations are a structural feature of management, not a failure of management. Every team, given enough time, will produce a situation where a person and a role are mismatched, where performance declines, or where a separation becomes necessary. The goal is not to avoid these situations. The goal is to handle them with enough clarity, preparation, and honesty that everyone involved emerges intact: the person moving on, the team moving forward, and the manager who will face the next one better prepared.

---

Parallax interpretations are independent and not affiliated with Gallup or CliftonStrengths. CliftonStrengths is a registered trademark of Gallup, Inc.