When "We Know It When We See It" Stops Working

Every year, a leadership team sits down to pick who gets recognized. The culture award, the values champion, the shout-out at the all-hands. And every year, the same quiet question hangs over the table: on what basis?

At one company, the group tasked with choosing the culture champions got so stuck they made a proposal. Put the names in a hat and draw one. They were not being lazy. They had no written standard for what a culture champion did, so picking one person over another felt arbitrary, political, or both. A hat was the honest version of the process they already had.

That is what an employee recognition program becomes when it runs on instinct instead of defined behavior. "We know it when we see it" sounds like discernment. In practice it is a lottery with extra steps, and everyone watching can feel it.

The short version

• Recognition without stated criteria reads as favoritism. Gallup found companies "need to state specific standards for awards to avoid any backlash."
• Most people are not getting recognized at all. Only one in three U.S. workers strongly agree they received recognition in the past seven days, and those who feel overlooked are twice as likely to say they'll quit within a year.
• "We know it when we see it" is not a standard. It is the absence of one, dressed up as taste.
• The fix is not a better nomination form. It is naming the specific behaviors worth recognizing, so the reward points at something anyone can see and repeat.

Why does recognition turn into a lottery?

Because a value is not a criterion. "We celebrate teamwork" tells no one what teamwork looks like on a Tuesday. So, when it is time to choose, the manager falls back on gut feel, recent memory, or who spoke up in the last meeting. Different managers use different yardsticks. The result feels random to the people receiving it and unfair to the people who don't.

Gallup's research is blunt on this: without stated standards, recognition invites backlash. Reward the wrong person, or the same person too often, and you fail to motivate anyone. Worse, you quietly tell your best people the game is rigged.

"We know it when we see it" is not a standard

A newly hired CEO, the first ever brought in from outside a century-old, family-owned company, described the gap to us with unusual precision. His company had good values. People believed in them. What they did not have were the behaviors that told anyone how to produce the experience those values described. Recognition ran on a phrase every leader has said out loud: we know it when we see it.

His own correction is the whole point in one line. It is not luck, and it is not "we know it when we see it." You define it.

That is the move most companies skip. They write the values, frame them, and assume the behaviors are implied. They are not. "Integrity" does not tell a warehouse team what to do when a shipment is wrong. A behavior does: "We own our mistakes and fix them fast." One of those you can recognize. The other you can only admire.

Do employee recognition programs work?

They work when the thing being recognized is specific, visible, and the same for everyone. They fail when it is a vibe.

The failure mode is not lack of budget or bad intentions. It is vagueness. A program built on "who felt like a culture fit this quarter" drifts toward the loudest, the most senior, or the manager's favorite, because those are the signals available when no behavior is named. A program built on defined behaviors gives everyone the same target and the same shot at hitting it. The recognition stops being a popularity contest and starts being evidence.

What good employee recognition criteria look like

Good criteria are behaviors, written as actions, that any person in the company could observe and point to. Not "positive attitude." Instead: "Assume positive intent." Not "goes above and beyond." Instead: "Do it right the first time."

CultureWise calls these Fundamentals. There are usually 25 to 40 of them, each one a specific, coachable behavior, practiced one per week. When your recognition program is built on named behaviors like these, three things change:

• Nominations get concrete. "I'm recognizing our billing lead because on Thursday she caught a billing error, called the client before they noticed, and fixed it by end of day." That is a behavior, a moment, and an impact. Not a personality.
• Managers stop guessing. The standard is written down and identical across teams, so recognition in the east office means the same thing as recognition in the west one.
• The reward teaches. Every time you recognize a named behavior in public, you show the whole company what good looks like. Recognition becomes a weekly lesson, not a monthly raffle.

How to build an employee recognition program on defined behaviors

1. Name the behaviors first. Before you design nominations, points, or awards, define the 25 to 40 behaviors that describe how your best people operate. Written as verbs. Observable. This is the Culture by Design methodology's starting move, and it is the step most programs never take.

2. Tie every recognition to a named behavior. No free-floating "great job." Each shout-out points at a specific behavior, so the reward and the standard are the same thing.

3. Give managers a shared language. A simple structure like SBI (situation, behavior, impact) lets anyone give recognition that lands on an action instead of a mood. "In yesterday's client call (situation), you slowed down and made sure everyone understood the plan (behavior), which is why they signed off on the spot (impact)."

4. Put it on a rhythm. Recognition holds when it is weekly and woven into how you already operate, not saved for an annual banquet nobody remembers by February.

5. Make it visible. When recognition is public and tied to a named behavior, one thank you teaches a hundred people. That is the point of doing it out loud.

Run this, and the hat goes back in the closet. Nobody has to draw names, because the criteria are written on the wall and everyone can see who met them.

What to do Monday

• Ask the hat question. If you had to pick a culture champion this week, could you name the written behavior that decides it? If not, that gap is your real problem, not the nomination form.
• Pull one value and test it. Take a value you recognize people for and ask, "What is the specific behavior?" If you can't answer in a sentence a new hire would understand, it is not a criterion yet.
• Rewrite one recognition. Take your last "great job" and redo it as situation, behavior, impact. Notice how much more it teaches.

What are good employee recognition criteria?

Specific behaviors written as actions, not values or traits. "Own your mistakes and fix them fast" is a criterion. "Accountability" is not. Good criteria are observable enough that any coworker could point to a moment someone lived them.

How do you create an employee recognition program that feels fair?

Start by naming the behaviors worth recognizing before you build any mechanics. When every recognition ties back to a written behavior that is the same for the intern and the VP, fairness stops being a matter of trust and becomes a matter of record.