66% of Employees Will Leave If You Don't Do This One Thing

The Appreciation Crisis

Here is a statistic that should keep every tech leader up at night: 66% of employees say they would leave their job if they did not feel appreciated. For millennials, that number jumps to 76%.

This comes from research by the U.S. Department of Labor, which found that the number one reason people leave their jobs is not compensation, not career growth, not work-life balance — it is feeling unappreciated.

In tech, the problem is even worse. Engineers, data scientists, and product managers are in high demand. They can find a new job in weeks. The switching cost for a talented engineer is near zero. So if they do not feel valued, they leave.

And the cost of losing them is enormous. The Society for Human Resource Management estimates that replacing a salaried employee costs 6-9 months of their salary. For a senior engineer making €100,000, that is €50,000-€75,000 in recruiting, onboarding, and lost productivity.

But here is the thing: most leaders think they appreciate their teams. They just do it wrong.

The 5 Languages of Appreciation at Work

Dr. Gary Chapman (author of The 5 Love Languages) and Dr. Paul White adapted the love languages framework for the workplace, creating The 5 Languages of Appreciation at Work. Their research with over 100,000 employees revealed that people feel appreciated in fundamentally different ways — and using the wrong language is almost as bad as not showing appreciation at all.

The five languages are:

Language 1: Words of Affirmation

What it means: Verbal or written acknowledgment of someone's work, effort, or contribution.

For people who speak this language, a specific, genuine compliment means more than a bonus. They want to hear — or read — that their work matters and that you see their effort.

What it looks like in tech teams:

• "The way you refactored that authentication service was really impressive. It cut our response time in half and the code is much more maintainable now."
• A Slack message in the team channel recognizing a specific contribution
• A handwritten note (yes, physical) thanking them for their work on a tough project
• Specific praise in front of the team during standup or retrospective

What it does NOT look like:

• "Good job." (Too generic. It means nothing.)
• "Great work, team!" (Public but impersonal. The individual does not feel seen.)
• Annual performance review praise. (Too infrequent. Appreciation delayed is appreciation denied.)

Key principle: Specificity is everything. "Your error handling in the payment processing module prevented what would have been a major customer-facing bug" is 10x more meaningful than "nice work."

Language 2: Quality Time

What it means: Giving someone your focused, undivided attention.

For people who speak this language, your time is the most valuable thing you can give. They feel appreciated when you carve out time specifically for them — not multitasking, not checking your phone, not rushing to your next meeting.

What it looks like in tech teams:

• Regular, protected 1:1 meetings where you are fully present (laptop closed, phone away)
• Working alongside someone on a hard problem — pair programming, whiteboarding, debugging together
• Taking someone to coffee or lunch to hear about their career aspirations
• Attending their demo or presentation and asking thoughtful questions

What it does NOT look like:

• 1:1 meetings where you are visibly distracted, checking Slack, or answering emails
• Canceling 1:1s because "something came up" (this signals they are low priority)
• Drive-by check-ins: "Hey, quick question" while you are already walking away

Key principle: Quality time is about presence, not duration. A focused 20-minute conversation beats a distracted 60-minute meeting.

Language 3: Acts of Service

What it means: Doing something helpful that makes someone's work easier.

For people who speak this language, actions speak louder than words. They feel appreciated when you roll up your sleeves and help — not when you praise them from a distance.

What it looks like in tech teams:

• Helping a team member debug a particularly nasty issue (even though it is not your job)
• Taking meeting notes so they can focus on presenting
• Removing a bureaucratic blocker that has been slowing them down
• Covering their on-call shift when they have a personal commitment
• Setting up their development environment when they join the team

What it does NOT look like:

• Helping in ways they did not ask for or do not want (unsolicited "help" can feel like micromanagement)
• Helping once and then never again (consistency matters)
• Helping with the easy parts and leaving them with the hard parts

Key principle: Ask "How can I help?" and then actually follow through.

Language 4: Tangible Gifts

What it means: Thoughtful, personalized gifts that show you know the person.

For people who speak this language, a well-chosen gift communicates "I was thinking about you, I know what you care about, and I went out of my way to show it."

What it looks like in tech teams:

• A book on a topic they mentioned they wanted to learn about
• A conference ticket for an event in their area of interest
• A high-quality mechanical keyboard because you noticed they care about their setup
• A gift card to their favorite restaurant after a tough sprint
• New gear for a hobby they mentioned in a team outing

What it does NOT look like:

• Generic company swag (a branded t-shirt does not communicate personal appreciation)
• Cash bonuses without context (money is appreciated but does not make people feel known)
• Gifts given only during holidays or milestones (the unexpected gift is more meaningful)

Key principle: The thoughtfulness matters more than the price. A €15 book you specifically chose for them means more than a €100 gift card.

Language 5: Physical Touch (Appropriate Physical Presence)

In the workplace, this language is adapted to mean appropriate physical presence — being physically present, showing up, and using appropriate professional touch like a handshake or a pat on the back.

What it looks like in tech teams (especially remote ones):

• Showing up in person for important moments (even if you are usually remote)
• A firm, warm handshake when meeting in person
• Sitting next to someone during a meeting as a sign of solidarity
• Attending team gatherings and being present (not just showing face and leaving)
• For remote teams: turning on your camera, leaning in during video calls, being visibly engaged

In remote-first environments, this language translates to visible presence and engagement — the digital equivalent of "being there."

The Appreciation Mismatch Problem

Here is why most appreciation efforts fail: leaders express appreciation in THEIR language, not the recipient's language.

A CEO whose primary language is Words of Affirmation will send praise emails and give public shout-outs. This works great for employees who share that language. But for an engineer whose language is Acts of Service, all those nice words ring hollow. What that engineer wants is for the CEO to remove the blocker that has been preventing them from shipping for three weeks.

The data bears this out. Chapman and White's research found that only 5-10% of employees feel most appreciated through the same language as their manager. This means 90-95% of the time, your default appreciation style is mismatched with your team member's preference.

Implementing the 5 Languages in Your Team

Step 1: Identify Each Person's Primary Language

There are two ways to do this:

Option A: Direct conversation. In your next 1:1, ask: "When you think about a time you felt really appreciated at work, what happened? What did someone do?" Listen carefully. Their answer reveals their language.

Option B: The MBA Inventory. Chapman and White created the Motivating by Appreciation (MBA) Inventory — a formal assessment tool. It takes 10 minutes and produces a ranked order of all five languages.

Step 2: Create an Appreciation Profile for Your Team

Build a simple document:

Step 3: Build Appreciation into Your Routines

• Weekly: Express appreciation to at least 2 team members in their preferred language
• Sprint end: Recognize specific contributions using the right language for each person
• Quarterly: Have a dedicated appreciation conversation in each 1:1
• Annually: Review and update the appreciation profiles

Step 4: Teach the Team to Appreciate Each Other

Appreciation should not only flow from manager to report. Peer-to-peer appreciation is equally powerful. Share the framework with your whole team. Let people self-identify their language. Create team norms around expressing appreciation.

The ROI of Getting Appreciation Right

Companies that get appreciation right see measurable results:

• 21% higher profitability (Gallup, companies with engaged employees)
• 41% lower absenteeism (Gallup)
• 59% lower turnover (Gallup, in high-turnover organizations)
• 10% higher customer satisfaction (Bain & Company)

For a team of 10 engineers with average salary of €80,000:

• Replacing 2 engineers per year (typical for low-appreciation teams): €100,000-€150,000
• Cost of implementing appreciation practices: Essentially €0 (it is a behavior change, not a budget line)
• Net savings: €100,000-€150,000 per year

Appreciation is not soft. It is the highest-ROI investment a leader can make.

How Hyperion Consulting Builds Appreciation Cultures

At Hyperion Consulting, we help tech leaders build teams where people feel valued, stay longer, and perform better. Our leadership coaching integrates the 5 Languages of Appreciation into practical, sustainable leadership habits.

Ready to stop losing your best people? Book a free consultation to discuss building an appreciation-driven culture.