The paradox is easy to see once you name it. Companies are spending more on employee recognition than at any point in the past decade, and the metrics recognition programs are meant to influence — engagement, retention, discretionary effort — have moved in the wrong direction. Recognition budgets have grown. Recognition results have not.

This is not a spending problem. It is a diagnosis problem.

What follows is not a study. It is a set of patterns I have watched recur. They emerge from nearly four decades in the printing, branded merchandise, and promotional products industry, and from the past five years of closely working with enterprise clients — Microsoft foremost among them — to plan, budget, execute, and measure employee recognition through branded merchandise. Recognition Infrastructure is the frame that emerged from those years — from watching the same failure patterns repeat across organizations of every size and industry.

When something well-funded consistently fails to produce the outcome it was designed for, the honest first move is to question whether the underlying design is correct. Most organizations don't. They increase the budget, add a new platform, hire a vendor, refresh the merchandise. The activity looks like progress. The result rarely follows.

Across those enterprise engagements I have observed the same three failure patterns repeatedly. They cut across industry, headcount, and recognition maturity. They explain, better than any single data point, why recognition programs disappoint despite their growing investment.

Pattern one: Recognition is event-driven, not system-driven

Most organizations recognize their employees around occasions. Holidays. Service anniversaries. Employee appreciation days. Product launches. Kickoffs. Year-end celebrations. The organization believes it has a recognition program. What it actually has is a recognition calendar — a list of dates on which recognition happens, followed by long stretches of silence between them.

The pattern is legible when described plainly. Recognition arrives when the calendar demands it. Employees receive appreciation not because they have done something specific worth appreciating, and not because the organization has established a cadence in which appreciation is expected — but because the date has arrived. Recognition-by-occasion is administratively convenient. It solves the question of when to do this by outsourcing the answer to the calendar. It does not, however, produce the organizational effect that recognition is intended to produce.

Employees remember recognition-by-occasion for what it is: a company activity that happened around a date. They rarely remember it as a signal that leadership sees them, values their work, or is investing in their continued participation. The moment lasts as long as the merchandise does. Then it recedes.

The alternative is not more moments. It is fewer moments, executed on a predictable cadence. Predictability creates expectation. Expectation creates trust. Trust compounds into culture. Occasion-driven recognition cannot produce that compounding effect no matter how large the individual moment is, because the compounding depends on the pattern, not the peak.



The organization believes it has a recognition program. What it actually has is a recognition calendar.

Pattern two: The purchase becomes the objective

The second pattern is subtler, and more expensive.

Organizations spend meaningful dollars on recognition merchandise before defining what success looks like. The buying moment substitutes for the strategic work of establishing the outcome the recognition program is meant to influence. The decision that gets made is what to buy. The decision that should have been made — what behavior or business outcome are we trying to change — is left implicit. Often it is never made at all.

This pattern is most visible at the end of a fiscal year or quarter. Departments discover unspent budget. HR or a manager is asked to convert the surplus into "something employees will appreciate." The purchasing conversation becomes: "What should we spend this money on?" — when the conversation should have been: "What recognition outcome are we trying to create?"

The two questions produce dramatically different decisions. Organizations that plan recognition into the annual budget make different decisions about product mix, cadence, participation, and measurement than organizations attempting to spend leftover budget under deadline pressure. Reactive spending selects merchandise. Planned spending designs a program.

The transferable principle worth naming plainly: recognition planning influences merchandise selection. Merchandise selection rarely improves recognition planning. Any organization whose recognition strategy begins at the moment of purchase has already lost the leverage that recognition, done well, is capable of producing.

Pattern three: The failure happens upstream of the product

When recognition programs disappoint, the reflex is to blame the merchandise. The shirts weren't premium enough. The tumblers were the wrong color. The kits didn't feel special. The vendor didn't deliver quality.

My observation is that merchandise is almost never the actual failure point. When activations underperform, the root causes almost always occur before the first item is ordered. The pattern shows up as:

  • Unclear or unstated recognition objectives at the outset
  • Lack of executive alignment on what the program is supposed to signal
  • Inconsistent internal communication before, during, and after the activation
  • Poor participation planning, resulting in low turnout regardless of product quality
  • Insufficient measurement discipline, so the program cannot demonstrate what it accomplished
  • Reactive budgeting, which forces timing and scope into the wrong shape

Merchandise, in this frame, is the visible artifact of a system that failed months earlier. Improving the merchandise addresses the artifact without addressing the system that produced it. This is why refreshing the vendor, upgrading the product mix, or increasing the per-employee spend produces such consistently disappointing results. The intervention is downstream of the actual failure.

The organizations most likely to see returns on recognition are the ones willing to look upstream first. What did we decide this program should accomplish? Who did we align with? How did we communicate it? How did we measure it? These questions are structural. They are, unglamorously, the actual work.

The deeper problem: recognition decays

The three failure patterns share a single underlying principle, which is worth naming clearly because it changes what organizations should do about recognition.

Recognition decays. Like any business system, its impact diminishes over time unless it is intentionally reinforced through a consistent cadence. Isolated recognition moments produce short-lived engagement lifts that revert to baseline — sometimes below baseline — once the moment is over and the silence resumes. A predictable, planned cadence prevents that decay by creating expectation, trust, and cumulative organizational weight.

The mistake most organizations make is not that they recognize their employees too little in any single moment. It is that they mistake isolated moments for sustainable systems. The moment is the visible thing. The system is the invisible thing. Organizations invest in visible things.

The evidence, in aggregate, is that HR leaders in high-performing organizations don't need more creative ideas for recognition. They don't need better products. They don't need a bigger vendor. They need a repeatable operating system — a process that produces recognition on cadence without requiring the department to reinvent recognition every quarter.

Ideas are the input. Systems are what turn ideas into results.

Where this leaves us

The industry has treated employee recognition as a marketing spend for the past thirty years. Campaign here. Big activation there. Trend piece in the trade magazine about the next generation of gift options. That framing has produced the results the framing predicts: episodic engagement lifts, real ambivalence about ROI, and a persistent gap between what organizations spend on recognition and what recognition delivers.

The framing itself is wrong.

Recognition is not a marketing spend. It is not a series of gestures. It is not a program in the sense that a wellness program or a training program is a program. Recognition, done in a way that produces the outcomes organizations expect from it, is closer to infrastructure — the operating system through which appreciation is delivered consistently, measured objectively, and experienced equitably across an organization.

The reframe — what a system-based approach to recognition requires organizations to change — is the subject of the next article. For now, the argument is narrower: the industry does not have a recognition problem. It has a diagnosis problem. The failure patterns are consistent. The cause is deeper than any of them. And no amount of additional spending, on the current design, will produce a fundamentally different result.

Questions to ask your leadership team

  • Is our recognition strategy event-driven or system-driven?
  • Could we clearly define what success looks like before purchasing recognition merchandise?
  • If our recognition budget doubled next year, would we spend it differently — or simply spend more?
  • What evidence would we present to demonstrate our recognition program is working?

If the patterns in this article match what you have observed in your own organization, the QRA assessment at getqra.com is a five-minute diagnostic that scores 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.