What is Values-Based Recognition?

Most workplace recognition is generic: "great job," "nice work," "thanks for that." It feels good in the moment, but it doesn't tell anyone what made the work good or worth repeating. Values-based recognition closes that gap. Instead of just praising the outcome, it names the value behind it — "this shows real ownership" or "that's customer obsession in action" — so the person being recognized, and everyone who sees it, understands exactly which behavior the company wants more of. It's a natural extension of a healthy recognition program, and it's one of the most direct ways to reinforce behavioral alignment between what a company says it values and how people actually behave.

Why Tie Recognition to Values

• Values on a wall are abstract: A list of words in an employee handbook or a poster in the break room doesn't tell anyone what those words mean in practice.
• Recognition makes values observable: When a value is attached to a real moment, it stops being a slogan and becomes a concrete example other people can point to and copy.
• It closes the say-do gap: Employees quickly notice when stated values don't match what actually gets rewarded. Naming values in recognition is proof the company means what it says.
• It builds a shared vocabulary: Over time, teams start using the values themselves in everyday conversation — "that was a real ownership move" — because recognition modeled the language first.

What Values-Based Recognition Looks Like

• Generic version: "Great job handling that client call today."
• Values-based version: "You stayed on that client call an extra 20 minutes to make sure they actually understood the fix — that's customer obsession."
• Name the value, not just the outcome: The recognition should explicitly state which value was on display, not leave it implied.
• Name the behavior, not just the value: Saying "great ownership!" with no detail is still vague — pair the value with the specific action that earned it.

Common Pitfalls

• Turning it into a checkbox: If every recognition gets tagged "innovation" regardless of what actually happened, the label stops meaning anything.
• Overusing one value: Teams often gravitate toward the same easy value (like "teamwork") while values that are harder to observe, like "candor" or "ownership," go unrecognized.
• Values that don't reflect real priorities: If the values being recognized aren't the values leadership actually rewards in promotions and decisions, the practice reads as performative rather than genuine.
• Recognition without specifics: Naming a value with no concrete behavior behind it collapses back into generic praise with an extra word attached.

How HeyTaco Helps

• Tag recognition to a value: HeyTaco lets teams attach a specific company value to a taco when they give it, so appreciation and values reinforcement happen in the same moment.
• See which values show up: Because every tagged taco is visible, teams can see in real time which values are being lived out and which behaviors are earning recognition.
• Spot underrepresented values: Reporting surfaces which values are rarely tagged, giving leaders a clear signal about which parts of the culture need more visibility or investment.

Frequently Asked Questions

What is values-based recognition?

Values-based recognition is praise that explicitly names which of a company's stated core values someone demonstrated, along with the specific action they took. Instead of generic praise like "great job," it says something like "this is exactly what ownership looks like," connecting a real behavior to a value the company says it cares about.

How is values-based recognition different from general praise?

General praise acknowledges that something good happened, but it doesn't say why it mattered. Values-based recognition names the specific value on display and the specific behavior behind it, so the recognition doubles as a real-time, concrete example of what the company's values look like in practice.

How do you start a values-based recognition practice?

Start by making sure your stated values are specific and observable rather than abstract, then give people an easy way to tag recognition to a value when they give it. Encourage managers to model it first, and periodically review which values are showing up often and which are being recognized rarely.