Recognition broadcasts culture

People believe the names Recognition as a broadcast system, the invisible work it misses, and why promotion is the loudest values statement you make Six essays ago, in the piece about culture and the first fortnight, I made a claim in passing and promised to come back to it: every recognition email is a tiny broadcast about what’s really rewarded here, and everyone reads it that way.

This week is the return visit, because the more time I spend inside the mechanics of workplace experience, the more convinced I am that recognition is the most misunderstood instrument in the organisational toolkit. Misunderstood not because organisations do too little of it, though many do, but because they fundamentally misread what kind of instrument it is.

Leadership thinks recognition is a reward: something sent to one person, for their benefit, to make them feel valued and perhaps stay longer. Filed under morale, somewhere below compensation in the hierarchy of retention levers, reviewed annually when the engagement survey’s recognition score comes in soft.

But watch what actually happens when the recognition email lands, the quarterly awards get announced, the shout-out gets posted. Everyone reads it. And everyone reads it twice: once for the names, and once for the pattern. Who got recognised. For what. By whom. In front of whom. And, silently but unmistakably, who didn’t, again.

Recognition isn’t a reward that happens to be public. It’s a broadcast that happens to have a recipient. And what it broadcasts, with more clarity and more credibility than any other channel the organisation owns, is the answer to the only cultural question that matters: what does this place actually value?

The wall claims. The award names.

Recall the problem we established in the culture essay: values statements have converged into the same four or five nouns across the entire economy, which means the words themselves carry almost no information. Integrity, courage, collaboration, respect. Every organisation claims them; the claims are free; and everyone inside knows the claims are free.

Recognition is where the claims stop being free, because recognition attaches names, faces and specifics to values, in public, at a cost: the cost of choosing. Every award is a selection, and every selection is a revelation. When the organisation says “collaboration matters here,”

that’s a claim. When it stands someone in front of their peers and says “this person, for this work,” it has converted the claim into a demonstration, and demonstrations are what people actually learn from.

Which is precisely why misaligned recognition is so corrosive. Put Collaboration on the wall and hand every quarterly award to individual heroics, the big deal landed solo, the crisis rescued single-handedly, and watch what the audience learns. They don’t learn that the organisation lacks collaboration. They learn something more damaging: that the wall is decorative, and heroics are the real currency. The recognition didn’t just fail to reinforce the value. It publicly repealed it, with evidence, in front of everyone. This is the same mechanism as the challenge moment from the culture essay, running on a schedule: a recurring, institutionalised event in which the organisation demonstrates, names attached, what it actually rewards.

The gap between what the wall claims and what the award names is the Promise Gap, in its most legible, most regularly published form. Most organisations issue an update every quarter without ever reading it themselves.

The invisible work problem Now the part of this broadcast system that does the quietest damage, because it operates by omission.

Every organisation runs on a large volume of work that is essential and invisible. The glue work: the person who connects the two teams that would otherwise duplicate everything.

The prevention work: the roster built so carefully that the crisis never happens, the risk flagged early enough that it never becomes a story. The care work: the colleague who carries the emotional load of a hard team through a hard year. The maintenance work:

everything that stays working because someone tends it.

Recognition systems are structurally biased against all of it, for a simple reason: recognition follows visibility, and this work is defined by producing non-events. There is no award ceremony for the outage that didn’t happen. The save is spectacular; the prevention is silent.

So quarter after quarter, the broadcast goes out, and the pattern in it says: firefighting is valued here. Fire prevention is not. Be visible, or be unthanked.

And people, being excellent learners, respond rationally. They drift toward visible work and away from invisible work, not out of cynicism but out of accurate pattern-reading. The glue starts to dry out. The prevention thins. The organisation slowly optimises itself for spectacle, and then commissions a review into why everything has become so reactive, without once looking at its own broadcast history for the cause.

If you want a single diagnostic for the health of a recognition system, it’s this: how often does it succeed in naming a non-event? An organisation that can recognise the crisis that didn’t happen has solved the hardest problem in the genre. Most never try.

Promotion: the broadcast that overrides all others Everything above applies to recognition’s loudest and least acknowledged channel.

A promotion is a recognition event of a different magnitude: it’s the organisation announcing, permanently and structurally, what it converts into power. And its broadcast strength is so high that it overrides every other signal. You can run flawless values-aligned awards all year, and one promotion that contradicts them, the political operator elevated, the corner-cutter rewarded, the person everyone knows to be unkind given a bigger team, will erase the lot.

The awards said collaboration; the promotion said otherwise; and in a contest between a certificate and a power structure, nobody in the history of employment has ever believed the certificate.

Here’s an exercise I’ve suggested to leadership teams, and I’ve never seen it land comfortably: ask people in any team to recite the last five promotions in their area and what, in their view, each one was really for. They can always do it. Instantly, in detail, with a thesis.

That recital, not the values page, not the awards program, is the organisation’s operative values statement as its people have received it. If you want to know what your culture actually teaches, don’t read your wall. Read your promotion history the way your people already have.

The cheapest lever, and how it gets ruined Now the good news, because this essay has one, and it’s substantial.

Recognition is the highest-leverage experience instrument in the building precisely because of everything above. It’s a broadcast channel you already own, it publishes on a schedule, everyone reads it, and it costs almost nothing. Specific, timely, sincere acknowledgment, this person, this work, this value it demonstrated, this difference it made, outperforms expensive engagement programs consistently, and any manager can produce it any day of the week.

Among all the levers this series has covered, spans, windows, ninety-day designs, this is the only one available by Friday, free.

Which makes it especially painful to watch organisations ruin it, and they ruin it the same way every time: by proceduralising it. Recognition targets for managers. Nomination quotas.

Values-moment KPIs. The moment gratitude becomes rostered, its information content inverts: the audience can tell noticed from scheduled at a glance, and scheduled recognition doesn’t read as “the organisation values this work.” It reads as “the organisation values appearing to value this work,” which is worse than silence, because it adds insincerity to the omission. This is the scripted-sincerity trap from the moments essay, in its most common habitat. You cannot KPI your way to being genuinely seen.

The design principle, as ever in this series, is conditions over scripts: don’t mandate recognition, make noticing possible. A manager with a humane span, who actually knows what their people did this month, will recognise well without a program. A manager with twenty-five reports and a quota will produce exactly what the quota measures: volume, without eyes.

The counterargument: recognition breeds politics The seasoned objection, from people who’ve watched recognition programs curdle: “Public recognition creates politics. People perform for the award. The same charismatic few win everything, quiet contributors are overlooked, and some people genuinely hate being publicly recognised at all. You’re proposing more of a game that’s already rigged.”

Every clause of that is a real failure mode, and none of it is an argument against the thesis.

It’s an argument about broadcast quality.

Yes, people perform for awards, which is precisely the point: recognition shapes behaviour, and the only question is whether it shapes it toward the values or toward the spectacle. A rigged broadcast that rewards visibility and charisma isn’t evidence that recognition doesn’t work. It’s evidence that it works perfectly, and is currently teaching the wrong curriculum. The fix is aiming, not silence: recognise the glue, the prevention, the non-event, and watch what people start performing instead.

Yes, the same few win everything, when recognition is sourced from what’s visible at altitude. Sourced closer to the work, from peers, from the manager who actually sees, the distribution changes, because the invisible work is only invisible from far away.

And yes, some people would rather not be named on a stage, and honouring that is part of the same respect the recognition claims to express. Recognition isn’t a format; it’s an act of accurate seeing. For one person that’s the all-staff email. For another it’s two private sentences that prove someone actually understood what the work took. The broadcast to the audience still happens either way, because patterns show even when individual moments are quiet.

What to do with this on Monday

Audit the broadcast history. Pull six months of formal recognition, awards, shout-outs, and the last year of promotions. Map each against the stated values. The mismatches are your operative culture, already published, already read by everyone but you.

Recognise one non-event this week. Find a crisis that didn’t happen and name the person whose work is the reason. Do it publicly and specifically. It will be the most-discussed recognition of the quarter, because it breaks the visibility bias in front of everyone.

Make specificity the standard. Retire “great job.” The format that carries information is: this work, this value it demonstrated, this difference it made. If the recogniser can’t fill in those three, they haven’t noticed anything; they’ve just emitted warmth.

Read the next promotion as a broadcast before you make it. One question in the decision meeting: “What will everyone learn about what we value when this name is announced?” If the honest answer contradicts the wall, you’re about to publish a repeal.

Fix noticing before adding programs. If recognition is thin, check spans and load before buying a platform. Unseen work can’t be recognised, and no software notices on a manager’s behalf.

The sentence to keep

Your values claim what matters. Your recognition names it. People believe the names.

Every quarter, your organisation publishes its real values statement, with evidence, to a full readership. The only choice is whether it’s edited or accidental.

Next week: the final perspective in this twelve-week series, and the reason all of it now matters more than it ever has. Somewhere tonight, a candidate is asking an AI what it’s like to work at your organisation. The answer is being assembled from everything this series has covered, and you can’t brief the model.

If your organisation’s last five promotions tell a different story from its wall, you already know which story your colleagues believe. Reply or comment with the value your recognition system actually teaches. Honest answers only; the pattern-reading is the point.

Shehzad Bhanji writes The Promise Gap, a weekly perspective on the relationship between organisational promises and lived experiences. Across a 25-year international career spanning marketing, customer experience, employer brand, HR technology and people experience, he has worked across Australia, Asia, Europe, the Middle East and Africa.