Everyone knows

You knew by week six. If you're honest, week three. There was a moment in a meeting — a wrong-shaped answer, a deadline that quietly became a discussion — and something in you filed a note it declined to read.

It's month four now. And the difficult truth about a hire that isn't working is that it is never a secret. Your best people clocked it before you did; they're the ones absorbing the redone work. What they're watching now isn't the struggling hire. It's you. Every week the situation continues, you are broadcasting, at high fidelity, what this company actually tolerates — and your strongest person is recalibrating their own plans accordingly.

You've told yourself the kind version: they need more context, the onboarding was rushed, the last project wasn't a fair test. Sometimes that's even true, which is what makes this genuinely hard rather than merely uncomfortable. But notice the asymmetry in your evidence-gathering: every good week counts, every bad one gets an explanation. You're not evaluating anymore. You're litigating, for the defense, because the verdict has a conversation attached to it that you don't want to have.

The unsayable part isn't the assessment — it's the guilt. You hired them. They moved, maybe. They have a kid, maybe. Saying "I think I made a mistake and someone else will pay for it" out loud, to anyone on the team, is impossible; it's half a firing already. So the sentence goes unsaid and the decision goes unmade, and the cost lands daily on the people carrying the slack.

Say the whole tangle somewhere safe first — the assessment, the guilt, the fear about the team's reaction, the worry that the real failure was your onboarding. Untangled, it usually resolves into something almost simple: a fair test you actually believe in, with a date. Kindness and clarity turn out to be the same move done at different speeds. The cruel version is the slow one you're doing now.