Decision Blindness

A complaint came in four months ago. Since then, four individually defensible decisions happened to the person who raised it. Nobody has examined them together — and the correction window that's still open right now is closing on a schedule the organization doesn't control.

The complaint came in four months ago. A wage concern, raised through the normal channel, handled the way these things are usually handled: HR logged it, looked into it, closed it out.

Since then, four things happened to the person who raised it. Their schedule changed. They got passed over for a project they'd specifically asked for. Their last performance rating came in lower than the one before. Nothing about any single decision looks wrong. The schedule change had a business reason. The project assignment went to someone with more relevant experience. The rating reflected a real, if modest, dip in output. Each decision, examined on its own, holds up.

Nobody has examined them together. Not the manager who made them, not HR, not anyone in the room when each individual call got made. The sequence exists. The pattern is sitting right there in four ordinary personnel decisions made over four months. And the organization is structurally unable to see it, because nothing in how decisions get reviewed ever asks the question that would surface it: does this decision follow something the person did that the law protects?

Not Malice. A Missing Question.

The instinct, once this gets named, is to assume someone retaliated on purpose. That's usually not what happened, and assuming it is gets the diagnosis wrong.

What actually happens is each decision-maker operates with a narrow, accurate, defensible view of their own decision. The manager scheduling shifts doesn't know about the wage complaint, or knows but genuinely isn't thinking about it when building next month's roster. The person assigning the project picked the more experienced candidate, full stop. None of them set out to punish anyone. What's missing isn't intent. It's a mechanism that ever asks whether this specific decision, made today, sits downstream of something the organization is legally required to treat carefully.

That gap is the actual condition. Not a bad actor. A structural blindness to sequence, built into an organization that reviews each decision in isolation and never in relation to what came before it.

Why the Window Closes Quietly

Right now, nothing has been filed. No claim, no charge, no outside counsel involved. That's not nothing, it's the most valuable thing currently true about this situation, and it's temporary.

Every additional week this sequence runs unexamined is a week where the pattern gets longer, the explanations for each individual decision get relied on more heavily, and the eventual question, did anyone notice this was happening, gets harder to answer well. The correction available right now, while the pattern is still internal and still small, is categorically easier than the correction available after the fifth decision, or after the employee's own attorney lays out the same four-month timeline that's sitting in your HR file right now, just not yet read as a sequence.

That should create urgency rather than dread: the fact that nobody has connected these decisions yet is not evidence that everything is fine. It's evidence that the correction window is still open, and that it's closing on a schedule the organization doesn't control.

How to Know If This Is What You're Looking At

A protected event happened first. A complaint, a claim, an investigation, a disclosure the law treats specifically. Something on record, with a date.

A sequence of adverse decisions followed it. Not one. A sequence, each defensible alone, accumulating over weeks or months.

Nobody has connected the timeline. This is the actual diagnostic mark. The decisions exist in different systems, made by different people, reviewed by no one against the original event. If you ask whether anyone has laid the dates side by side and the honest answer is no, that's the condition.

Why This Doesn't Get Caught in the Normal Course

Performance reviews check whether the rating is justified. Scheduling checks whether the business need is real. Project staffing checks whether the assignment makes sense. Every one of those reviews is built to ask "is this decision defensible on its own terms," and every one of those reviews will answer yes, honestly, because each decision genuinely is defensible on its own terms.

What none of those reviews are built to ask is the only question that actually matters here: regardless of whether this decision is defensible alone, does it belong to a pattern that started with a protected event. That question requires someone to hold the whole timeline at once, across multiple decision-makers and multiple systems, and nothing in a standard review process assigns that job to anyone. The blindness isn't a failure of any single review. It's the absence of the one review that would have to exist across all of them.

What Happens Next

This is not a training fix and it's not something to handle informally. The presence of a protected event followed by an adverse sequence is exactly the kind of pattern where getting the next steps right, and getting them right quickly, matters more than getting them comfortable.

The organization needs the actual timeline assembled, honestly, by someone positioned to see it whole rather than one decision at a time. That assembly itself often resolves the question one way or the other: sometimes the full sequence, once visible, has an obvious and entirely legitimate explanation that nobody had previously needed to state out loud. Sometimes it doesn't, and the organization needs to know that now, while there's still room to correct course, rather than later, after the pattern has had more time to compound and someone outside the organization has connected the same dots.

If a protected event happened and a string of adverse decisions followed it, and nobody in the building has yet laid the dates next to each other, that's the conversation to have before anything else.

The window for getting ahead of this is open right now. It won't stay open on its own.