The Paper Tiger

Everyone already knows this person shouldn't still be on the team. The conversations have happened more than once — in one-on-ones, in hallway asides, in performance reviews that somehow, every cycle, come out fine. The personnel file describes one employee. The conversations describe a completely different one.

Everyone already knows this person shouldn't still be on the team. The conversations have happened more than once: in one-on-ones, in hallway asides, in performance reviews that somehow, every cycle, come out fine.

That last detail is the one that matters. Not poor, not strong, fine. A rating that closes the topic without actually addressing it, written by a manager who has said, privately, multiple times, that this isn't working. The personnel file describes one employee. The conversations happening around that file describe a completely different one. Both versions have been allowed to exist simultaneously for long enough that nobody quite remembers when the gap opened up.

How the Fine Reviews Add Up

The instinct is to assume someone is being dishonest: falsifying reviews, covering for a friend, protecting themselves from a difficult conversation. That's sometimes part of it, but the more common mechanism is smaller and more forgivable than outright dishonesty.

Each individual review gets written under real pressure to avoid conflict, document fairly, and not torpedo someone's career over what might be a bad stretch. Taken one at a time, every soft rating has a defensible reason. Taken together, across enough cycles, they've built a file that bears no resemblance to the pattern everyone around the situation can describe in detail. Nobody decided to create a fictional record. They each decided, individually and repeatedly, that this particular review wasn't the moment to be the one who said it plainly.

Why the Severity Doesn't Wait for a Trigger

This is one of the few conditions in the diagnostic that doesn't consider a severity range. By the time it's visible from the outside, it is already entrenched, because what makes it visible is the gap between record and reality having existed long enough to compound. There's no early or mild version of this to catch before it matters. If the gap exists at all, it has already been building. The moment it surfaces, it shows that it's been true for a while.

What Happens When the Moment to Act Finally Arrives

Eventually something forces the question: a project failure, a complaint, a new manager inheriting the file fresh. Whoever has to act discovers the actual problem isn't the underperformance itself. It's that the documented record provides no support for acting on it.

A termination or serious intervention built on a file full of fine reviews carries significantly elevated risk of looking unsupported, discriminatory, or retaliatory, regardless of how accurate the private consensus is. The organization is left choosing between two bad options: building a paper trail from scratch under time pressure, which is never smart, or acting without one and either absorbing the legal exposure or paying unnecessary sums in exchange for a release of claims. Either path costs more and moves slower than it would have if any single review, or any document, for that matter, along the way had simply said what everyone already believed.

The Gap You'd Actually See

Private consensus and written record tell two different stories. Ask several people informally and you'll get one consistent account. Read the file and you'll get another. That gap, sustained across more than one review cycle, is the condition itself.

Soft ratings have accumulated specifically to avoid confrontation, not because performance was genuinely adequate. The manager writing them can usually tell you this directly, if asked privately and without judgment.

Nobody can point to when the gap started, only that everyone's known for a while. Like several conditions in this taxonomy, there's rarely a clean origin point: just an accumulation that became impossible to ignore at some point nobody marked.

Why a Single Honest Review Doesn't Solve It

Once this gets noticed, the instinct is to fix the next review: finally write what's actually true. That helps going forward, but it doesn't retroactively repair the file, and a sudden sharp drop after a string of fine ratings raises its own questions about what changed, rather than closing the gap cleanly.

What's actually needed is a deliberate reconciliation: an honest accounting of the actual pattern, documented properly, even though it means acknowledging that prior reviews understated what was really happening. That's an uncomfortable thing for an organization to put in writing about its own management practice, which is exactly why it tends not to happen until something forces it.

Where to Start

The conversation with the manager is the starting point, not as blame, but as the accurate source of information the file is missing. From there, the path is three steps.

Step one: document what's actually true, now. The manager writes a contemporaneous account of the specific performance concerns, behaviors observed, patterns noted, conversations that happened informally, with dates attached wherever possible. This isn't a formal performance improvement plan yet. It's an honest written record of what has been true and for how long, signed and dated now, before anything else moves.

Step two: create a real-time record going forward. From this point, every conversation about performance gets written down and confirmed: a follow-up email or documented note at the time it happens, not reconstructed later. "As we discussed today..." followed by the actual content. This is how a credible record gets built: by capturing the present in real time, not by reconstructing the past.

Step three: if a formal process is warranted, start it now. A performance improvement plan or written warning, grounded in the contemporaneous account from step one and the ongoing record from step two, gives the organization a documentable basis for whatever decision eventually follows. Started now, it reflects an organization that took the issue seriously once it was formally recognized. Started after something forces it, it looks like exactly what it is.

None of this is complicated. All of it requires someone deciding that the discomfort of saying it plainly, in writing, today, is smaller than the cost of continuing to manage it around the edges.

A file that finally tells the truth is worth more than one more cycle of fine.