The Need to Be Seen: Why Recognition Is Not the Same as Appreciation
You spend weeks untangling a brutal bug, skipping lunch and writing exhaustive tests. The next morning, a ticket is dragged to "Done," and nobody says a word. Here is why teams starve in silence, and how to fix it.
You spend three weeks quietly untangling a brutal concurrency bug or migrating a fragile database that was on the verge of bringing production to its knees. You write exhaustive tests for every edge case, and you deploy it late at night without a single second of downtime.
The next morning in standup, the project manager scrolls past your ticket, drags it to "Done," and asks: “Okay, what's next on the board?”
Nobody says a word.
Not because your teammates are bad people, but because the corporate machine simply swallowed another unit of cognitive output and moved on. You sit back in your chair, feeling that familiar, hollow deflation in your chest. It’s not that you were expecting a brass band. You just wanted to know that someone noticed.
You wanted to feel seen.
What You Do vs. Who You Are
There is a fundamental reason why so many corporate recognition programs feel hollow: they confuse recognition with appreciation.
- Recognition is about what you do. It is positive feedback tied strictly to performance, deliverables, and measurable outcomes. Did you ship the feature on time? Did you hit the quarterly revenue goal?
- Appreciation is about who you are. It is the intentional acknowledgment of a person’s inherent worth as a colleague and a human being, independent of their immediate output.
Recognition is necessary, but it has severe structural limits: it is backward-looking, conditional, and scarce. Because it is tied strictly to outcomes, there is only so much of it to go around. If there is a single promotion or an "Employee of the Month" leaderboard, only one person can win it.
More dangerously, recognition is entirely contingent on winning. What happens when a teammate pours two months of sweat into an ambitious project that gets canceled due to a shift in business strategy? What happens when someone is having an off-week because they are quietly battling family sickness or burnout?
Under a pure recognition framework, they receive nothing. The deafening silence communicates a cold, transactional message: “You are only as valuable to us as your last deliverable.”
The Scarcity Trap of Leaderboards
When companies try to solve this by gamifying praise with public leaderboards, they accidentally make the problem worse:
Status is zero-sum. For one person to climb to the top of the leaderboard, someone else has to sit at the bottom. When praise becomes a tournament, coworkers start managing impressions instead of doing honest work. People jockey for the visible, flashy tasks, hoard documentation so they remain indispensable, and look for opportunities to sound clever in meetings.
And when a coworker receives public praise, the room tightens with quiet envy instead of rejoicing with them.
The Biology of Encouragement
None of this is soft HR fluff. It is hardwired into human biology.
In organizational psychology, the Job Demands-Resources (JD-R) model explains how burnout actually develops. Heavy workloads and difficult deadlines don't break people on their own. Human beings are remarkably resilient when they have adequate resources to support them. Burnout happens when extreme demands collide with an absence of psychological resources.
Sincere appreciation is one of the most potent psychological resources that exists:
- It lowers cortisol, allowing the nervous system to drop out of chronic fight-or-flight.
- It builds what Harvard professor Amy Edmondson calls psychological safety: the conviction that a team is safe for interpersonal risk-taking.
- When people know they are appreciated for who they are—not kept on probation based on yesterday's metrics—the paralyzing fear of failure dissolves. They can admit when they need help and focus on solving real problems.
The Quiet Habit of Saying It
You don't need an executive decree, an HR committee, or an annual review cycle to change your team's culture.
Look around your workspace today. There is almost certainly someone who quietly refactored a brittle module without making a spectacle of it. Someone who patiently answered questions in a support thread, or someone who simply showed up with kindness and diligence during a grueling sprint.
Notice them. And more importantly, don't let the thought stay trapped in your head. Tell them right in the channel:
In an industry governed by relentless speed, vanity metrics, and noisy self-promotion, choosing to pause, see the person behind the screen, and speak an honest word of gratitude is one of the quietest and most powerful virtues you can practice.
Build a culture where your team feels seen
Mellowe is designed from the ground up around positive-sum appreciation. No toxic leaderboards, no token hoarding, and zero corporate bloat.