Awareness Isn't Action
A few weeks ago, in a department-wide call, a leader I respect said something that's been sitting with me ever since.
We were talking, in passing, about how promotion decisions get made – about proximity, about who gets seen, about who happens to be in the room when the room matters. And this leader acknowledged, openly and without prompting, that proximity bias and recency bias are real. That people who are physically near decision-makers tend to fare better than people who aren't, regardless of the work itself.
I appreciated the honesty. Then came the second half of the sentence: because we're aware of it, it's already accounted for.
I want to sit with that claim for a moment, because I think it's more common than we realize, and more dangerous than it sounds.
The comfort of naming
Naming a bias feels like doing something about it. It has the shape of insight – the vocabulary of self-awareness, the tone of intellectual honesty. And there's a reason it feels that way: naming usually is the first step toward fixing something. We're taught that awareness precedes change, so it's natural to mistake the first step for the whole journey.
But awareness and correction are not the same act, and treating them as equivalent quietly does something else: it closes the conversation rather than opening it. Once a bias has been named out loud, by someone with authority, it becomes much harder to point to its effects later without sounding like you're relitigating something that was already “handled.” The naming becomes a kind of immunity – not from the bias itself, but from being challenged about it.
I don't think this is usually cynical. I think it's usually sincere. Most leaders who say something like this believe it. That's what makes it worth examining rather than dismissing.
What awareness doesn't do
Here's the part that systems thinking makes uncomfortable and useful at the same time: bias isn't a property of a person's intentions. It's a property of a structure, operating whether or not anyone in it means harm.
If the structure rewards proximity – more informal access, easier support, more face time with the people who decide who gets seen – then knowing that the structure rewards proximity doesn't change what the structure does. The reward keeps flowing to whoever is closest, exactly as before. Awareness changes what's in someone's head. It doesn't change what the system does with the people inside it.
I watched this play out in a smaller, almost domestic way. A “voluntary” in-office program was promoted around the same conversation – voluntary in name, but with a quiet asymmetry underneath it: people who happened to share an office with a particular decision-maker had a noticeably easier time getting support for almost anything, compared to people who didn't. Nobody designed that on purpose. It's just what proximity does, by default, when nothing structural counteracts it. The acknowledgment of bias and the unexamined program sat right next to each other, in the same conversation, and neither one moved the other.
What would actually count
If awareness were going to do real work, it would show up as a structural change, not a sentence. Something like: decisions reviewed by someone outside the immediate circle of proximity. A defined, visible process for how remote contributions get weighed against in-person ones. A named metric for what the “voluntary” program is actually meant to produce, checked against whether it produces it.
None of that happened here. What happened was a true statement about bias, followed by a false conclusion about what that statement accomplished.
What changed
I'm not writing this to call out one leader, or one decision, or one program. The honest version of this essay isn't about them – it's about how easy this trap is to fall into, for any of us, the moment we're the one with influence over who gets seen.
So here's the question I'd actually want a reader to sit with, slowly, rather than nod past: the next time you catch yourself naming a bias out loud – in a hiring decision, a promotion cycle, a performance review, a budget call – ask what changed structurally as a result of naming it. Not what you said. What you built, removed, or redesigned.
If the answer is nothing, the bias didn't go anywhere. It just got a more comfortable name.