The industry does not have a recognition problem. It has a diagnosis problem.
I opened the previous article with that observation and spent 1,500 words unpacking three failure patterns behind why organizations spend more on employee recognition than at any point in the past decade and see the metrics recognition programs are meant to influence — engagement, retention, discretionary effort — moving in the wrong direction.
If you have not read that piece, the short version is this. Recognition programs disappoint for three reasons. They arrive on calendars instead of on cadence. They spend on merchandise before defining what success looks like. And when they fail, the reflex is to blame the product when the actual failure happened upstream.
The response I found most interesting after publishing that piece did not come from HR alone. It came from leaders across HR, operations, culture, and executive teams who said, in different words, some version of the same sentence.
We knew something was off. We just did not have language for it.
Language matters. It is what turns a private frustration into a shared diagnosis.
That is why this article exists. Not to tell you what to do — the doing part comes later — but to give you a working frame for what you have been seeing. Because the three failure patterns are not three unrelated problems. They are three symptoms of one structural mistake.
Most organizations manage recognition as a series of isolated programs. They should be operating it as infrastructure.
That reframe is the whole conversation.
The failure is a leadership-category failure, not a departmental one
The first thing worth naming clearly is that this is not, at root, an HR problem.
It is easy to file broken recognition under HR because the accountability for delivery often sits there. But every organization I have worked with distributes the actual decisions about recognition across many teams. Site leaders own the moments where employees are recognized in person. Operations leaders own the participation logistics. Executive business administrators own the calendar coordination. Program managers own the execution. Community affairs leaders own the alignment with the organization's public identity. HR and employee experience leaders own the program design and the measurement. Executive leadership owns the budget.
That distribution is not a problem. It reflects how modern organizations actually work.
The problem is that when accountability distributes across many teams but the framing stays narrow, the design of the whole system falls into a gap. Every team optimizes for the piece it owns. No one is designing the system as a system.
That is the shape of the failure. It is a leadership-category failure — a category of organizational investment that has not been defined as its own category yet — and until it is, no amount of departmental effort produces the compounding result the organization expects from it.
Why conventional thinking about recognition falls short
The recognition industry has spent the past thirty years operating inside a marketing framework.
You can trace the vocabulary. Campaigns. Activations. Kits. Rollouts. Big moments. Trade publications for the promotional products industry read like advertising trade publications — because that is what they are, downstream of. Recognition, as a category of leadership spending, was born inside marketing thinking and has been extended forward on the same premise ever since. Bigger campaign. Better product. Nicer rollout. Different vendor.
That framing has produced the results the framing predicts. Episodic engagement lifts. Ambivalence about ROI. A persistent gap between what organizations spend and what recognition actually delivers.
The framing itself is where the mistake sits.
Every other operational category the leadership team already funds is understood as infrastructure, not marketing. Financial infrastructure. IT infrastructure. Safety infrastructure. Facilities infrastructure. Compliance infrastructure. Each of those categories is planned. Resourced. Measured. Maintained. Defended against cuts in the budget cycle because the compounding cost of neglecting them is understood.
None of those categories is described as programs. Programs end. Infrastructure gets maintained.
Recognition is the one leadership category still being managed episodically — as a stack of programs that rise and fall inside the annual calendar. That is what makes it uniquely fragile.
The reframe is simple to state. Once it lands, it changes almost every operating decision downstream.
Recognition is not a marketing spend. It is closer to infrastructure.
What infrastructure thinking actually changes
I want to walk through what that reframe does to specific decisions, because the abstraction only lands when it changes something concrete.
Budget conversations change.
When recognition sits in the marketing frame, it competes for attention in the annual budget review the same way any discretionary spending line does. It gets defended in terms of engagement lift or event impact or employee sentiment scores. Those defenses are real, but they run inside the marketing category and get evaluated against marketing benchmarks. Recognition often loses that argument, because engagement lift is difficult to measure precisely and short-lived to defend after the fact.
When recognition sits in the infrastructure frame, the argument shifts. Infrastructure is defended in terms of what breaks if this is under-maintained. CFOs know how to evaluate maintenance investment. They have mental models for it in every other operational category. The question shifts from "is this event worth the spend" to "can we afford to let this compound negatively for another year."
Same dollars. Fundamentally different conversation.
The vendor relationship changes.
The clearest early sign I have watched, across every enterprise engagement, that a client organization has crossed into infrastructure thinking is a change in the questions I get asked.
They stop asking "what products should we buy?"
They start asking "what should we do?"
That single shift in verb is the whole story. When the question is "what should we buy," the vendor is a merchandise supplier and the value being purchased is product selection. When the question is "what should we do," the vendor is an advisor and the value being purchased is judgment applied to the recognition system.
At that point, merchandise is no longer the product. Judgment becomes the product.
Vendors do not always survive that transition. Neither do vendor relationships. Organizations that have crossed into infrastructure thinking begin looking for partners who can operate the recognition system alongside them, not just supply pieces of it.
Measurement changes.
Marketing thinking measures the event. Attendance. Distribution numbers. Post-event survey satisfaction. Those numbers are useful for the specific activation but they do not accumulate into a picture of whether the recognition category is healthy over time.
Infrastructure thinking measures the system. Cadence adherence. Cross-cycle engagement trends. Recognition satisfaction over time, not just after a single event. Whether the program survives leadership transitions. Whether employees anticipate the next moment or would be surprised by it.
Those measures answer different questions. The questions they answer are the ones executive leadership actually wants answered.
The end-of-quarter scene
There is one scene I keep returning to across every enterprise engagement, because it captures the reframe's opposite with more clarity than anything else I can point to.
An organization approaches me near the end of a fiscal quarter or fiscal year and asks, in one form or another, the same question.
"We have budget left over. What should we spend it on?"
I heard this question so many times in the earlier stretch of my career that it stopped registering as unusual. Now I hear it as diagnostic. Because everything the current recognition frame gets wrong is inside that question.
Reactive spending. Absence of a defined outcome. The purchase substituting for the strategy. The moment when merchandise selection has already replaced recognition planning without anyone in the organization noticing the substitution happened.
Organizations that have shifted into infrastructure thinking do not ask this question. Because their recognition system is already operating on a planned cadence. There is no leftover budget searching for a purpose, because the budget was planned into recognition from the start and the cadence has been running against that plan all year.
I keep returning to this scene throughout my writing because it is the scene. If you have ever been on either side of it — the leader asking the question, or the vendor answering it — you already know what I mean.
What the reframe requires the organization to change
Two things.
First, the accountability. Recognition Infrastructure is not owned by any single department. It has stakeholders — HR, operations, executive leadership, culture, sometimes site leadership — but the definition of the system needs to be treated as a leadership-category responsibility rather than a department-level one. That means the annual planning conversation about recognition needs a table with more chairs than it usually has.
Second, the timeframe. Programs run on quarterly and annual planning cycles. Infrastructure runs on multi-year planning cycles. A recognition strategy that only lives inside a single fiscal year cannot compound. A recognition strategy that lives on a two- or three-year architectural horizon — with quarterly execution against that horizon — can. That is what infrastructure looks like when it is being operated well.
Neither of those changes is expensive. Both of them are difficult, because they cross departmental lines and force leadership teams to have conversations they have been avoiding.
The reward, for organizations that make the shift, is significant. What I have observed across client engagements is that infrastructure-based recognition compounds the same way any other well-designed infrastructure compounds. Engagement metrics accumulate rather than reset each cycle. Retention exposure decreases. Executive confidence in the category grows. The line item stops feeling defensive in the budget review.
That is the payoff for treating recognition as what it actually is.
Where this leaves us
The industry does not have a recognition problem. It has a Recognition Infrastructure problem.
Three failure patterns from the previous article. One structural mistake underneath them all. And a category of leadership investment that has been misfiled inside marketing thinking for thirty years.
Naming the category is what unlocks the operating decisions that follow. What the definition of Recognition Infrastructure formally is, and the underlying regularities that govern how it behaves inside organizations at scale, is the subject of the next article.
For now, the argument is narrower. If you have been managing recognition as a series of programs and watching each one deliver a smaller and shorter engagement lift than the last, the design is the problem. Not the merchandise. Not the vendor. Not the budget size.
The design.
And redesigning it starts with naming it correctly.
Questions to ask your leadership team
- Is our recognition system planned into annual budget, or improvised from remaining budget?
- Would our current recognition approach survive a leadership change on our team?
- Do our recognition activations compound over time — or do they reset each quarter?
- If a peer leader in another organization asked us how our recognition system works, could we describe it as a system, or would we describe it as a series of activations?
If the reframe in this article matches what you have been seeing in your own organization, the QRA assessment at getqra.com is a five-minute diagnostic that maps your current recognition system against the operating principles above. It is not a sales tool. It is a mirror. The intent is a strategic conversation, not a purchase.
Recognition Infrastructure — the operating system that ensures appreciation is delivered consistently, measured objectively, and experienced equitably across an organization.