Suppose a credible concern about one of your strongest performers reaches your desk. You haven't established what happened, but you're already calculating what losing them would do to the quarter.
That calculation matters. It answers a different question.
You need to decide what the concern warrants. You also need to manage the company's dependence on this person. Let the second decision govern the first, and you can end up demanding more evidence, accepting weaker explanations or simply waiting longer because the employee is valuable.
I'd keep those decisions separate: examine the concern fairly, and plan for business continuity alongside it. Neither requires deciding in advance that the person must go.
When success changes your response
A person's results can influence how you interpret conduct that has little to do with those results. Your own good experience with them can also be genuine without being the whole picture. Colleagues may be working around behavior you never see.
Notice when you spend more time explaining why the employee is essential than checking what happened. Their contribution is real. It doesn't resolve the concern.
Nor should the complaint resolve it. Challenging work, direct feedback and disagreement can be uncomfortable without being mistreatment. You need to establish the behavior and context, not choose a personality label.
Fair doesn't mean identical
Different pay can be justified by contribution, specialized skills and the responsibilities of the role. Working arrangements can reflect legitimate individual needs. Accommodations aren't prizes for exceptional performance.
Ordinary autonomy isn't a prize either. If someone meets the business requirements using a method you wouldn't have chosen, the difference alone isn't a performance problem.
Consider a senior engineer who misses a routine meeting. An agreed written update may make attendance unnecessary. Skipping an applicable release review raises a different question. The job title doesn't tell you which case you have; the actual arrangement and its consequences do.
The useful distinction is between a reason for different treatment and a reason not to examine conduct. A legitimate difference needs criteria you'd apply to another person in comparable circumstances. Being willing to defend it isn't enough. The rationale has to fit the facts.
A bigger reward doesn't entitle someone to mistreat colleagues or ignore obligations that apply to their role.
Work through one postponed case
Choose one case you've delayed. Make a short written record to support the decision and its follow-through.
First, a boundary: concerns involving harassment, discrimination, safety or dishonesty need prompt handling through the relevant organizational process, with HR, legal or safety expertise as appropriate. Don't put them into a routine coaching window or wait for a pattern to develop.
1. Record the concern and your response. Separate what has been reported, what you know and what remains uncertain. Include when you learned of it and what you've done since.
Then compare your response with what you'd do for a less commercially important employee in comparable circumstances. Would you ask for the same evidence and act at the same pace? A different answer calls for scrutiny of your judgment; it doesn't prove the employee did anything wrong.
If you hired or repeatedly defended this person, ask an authorized reviewer who isn't invested in that earlier decision to challenge your reasoning. Don't make your own confidence the only safeguard.
2. Identify the applicable expectation. Is it reasonable, clear and relevant to this role and arrangement? For an ordinary performance issue, don't turn a previously unstated preference into a past violation. Clarify it going forward. If the expectation itself is wrong, change it for comparable situations rather than creating a private escape route for one person.
Disagreement isn't itself a breach. Take safety, ethical or legal objections through the appropriate process rather than treating them as defiance.
3. Check the account, including the conditions. Hear the employee's explanation and examine relevant records and other accounts. New information deserves investigation even when it arrives with irritation.
Check workload, authority, competing instructions and incentives. A missed commitment isn't automatically a character flaw. A structural problem and an individual breach can coexist.
Ask affected colleagues what work has been delayed, repeated or avoided. Don't turn this into a vote on whether they like the person. Extra preparation for a demanding review may improve the work; concealing a problem to avoid humiliation is different. Those answers are leads to examine, not proof of what caused the problem.
4. Choose the response the facts support. Preserve a justified arrangement. Clarify an unclear expectation. Repair a workload or authority problem you control. If the review finds no breach, don't manufacture one to demonstrate toughness.
If the facts substantiate a breach of a reasonable, applicable standard, specify the behavior required, useful support, follow-up and proportionate consequences. If incentives reward the behavior you're asking someone to change, correct that conflict alongside the individual response.
Consistency means using the same relevant criteria, not imposing identical sanctions. Severity, circumstances and prior history matter. Revenue contribution isn't a reason to skip the process. Check disciplinary decisions with the appropriate internal expertise and applicable policies.
5. Review what changes. Set a follow-up date suited to the issue's risk and to when the behavior can be observed. An apology or completed coaching session isn't the same as changed conduct. Check whether you delivered your own commitments, too.
If the problem continues, reassess the support and follow through on appropriate consequences. Don't quietly restart the clock because the next quarter needs to go well.
Manage the dependency separately
If losing the person would put customers or delivery at risk, make that risk concrete. Which commitments depend on them? Who could cover? What knowledge needs to be shared? Build a continuity plan without treating departure as a foregone conclusion.
That planning isn't permission to leave others exposed while you wait. It's work you should own alongside a fair response, not a bargain in which the employee keeps an exemption until you find a replacement.
Keep personnel details private. Explain the relevant principles and working expectations to the team, not the contents of someone's file.
None of this guarantees retention, restored trust or better performance. It may confirm that the arrangement was sound or that your expectation was the problem. It may require a consequence you'd rather avoid.
The point isn't to prove you can confront a star. It's to reach a decision you can justify from the facts and then carry it out, even when the person matters.
Working through this with your own team?