03 Feb The Day I Finally Felt Valued (And It Had Nothing To Do With My Work)
When a leader closed the door for a personal conversation, I realized what I’d been missing my entire career…
An hour before a company-wide town hall, my boss told me the president wanted to talk. The president of a 200-person company. Me – a part-time contractor in a remote office that could probably disappear tomorrow without anyone noticing.
I was sitting there when he walked by. My boss flagged him down, invited him in, offered to stay or leave. He dismissed my boss and closed the door.
Curious, not nervous. Even though I was 50/50 on whether this was good news or bad. Somehow it didn’t really matter.
He shook my hand, pulled up a chair, and told me the company was entering a significant transition. He knew I’d been through organizational changes before—I’d mentioned them in passing. He wanted to personally check that I was okay with what was coming. And he wanted to make sure I felt secure.
This guy was managing employees, external stakeholders, clients who needed reassuring. But he took time for me.
The Big Picture
Driving home that day, listening to Storyworthy and working through my own stories, something clicked.
For the first time in my professional life – outside of my relationship with my wife – I felt valued for who I am, not what I produce.
Recognition says “your work matters.” Valuation says “you matter.”
Most engineers have experienced only the first.
Core Insight
Here’s what makes valuation different from recognition:
Recognition is transactional. You delivered the project, you get the praise. You hit your numbers, you get the bonus. You solve the problem, you get the thank-you. It’s appreciation for output.
Valuation is relational. It’s someone investing time and attention in you when there’s nothing immediate to gain from it. It’s remembering previous conversations. It’s checking on you during their own crisis. It’s treating your peace of mind as important when they’ve got bigger fires burning.
He didn’t pull me aside because I’m crushing my role in sales (I’m part-time). He did it because he knows what organizational transitions do to people, remembered I’d been through them, and cared enough to make sure this one didn’t feel isolating.
That’s the difference between being useful and being valued.
Why This Matters To You
Most technical professionals mistake appreciation for valuation. Your manager thanks you for the project? That’s recognition. Your manager checks on you during their own crisis? That’s valuation.
The difference matters because one fills the tank and one doesn’t.
You know you’re being used instead of valued if:
Promotions and raises feel hollow even when you wanted them
You’re weirdly loyal to that one manager from years ago but can’t explain why
Success feels empty despite hitting every goal
You’d leave for less money if the culture was better
Here’s what’s actually happening: you’re starving for valuation while getting fed recognition. And recognition, no matter how much of it you pile up, doesn’t fill that gap.
This explains why some work environments keep you and others burn you out, even when the work and pay are identical. The work isn’t different. How they see you is.
For Individual Contributors:
Pay attention to the difference:
Being Useful looks like:
Appreciation tied to deliverables
Time with leadership only during project updates
Generic “great work” without specifics
Bonus conversations that never mention you as a person
Being Valued looks like:
Someone remembering details from previous conversations
Time invested in you during their crisis, not just yours
Private conversations that aren’t about what you owe them
Questions about how you’re doing that aren’t followed by task assignments
You can’t demand to be valued. But you can make career decisions based on which environment you’re in.
For Leaders:
If you lead anyone, here’s what valuation actually looks like in practice:
Invest time when you have none. He had major organizational demands. He still made time. That’s the signal.
Remember previous conversations. He referenced something I’d mentioned casually months earlier. Not from notes—from actually listening.
Close the door. Make it private. Make it important. Show that this matters enough to create space for it.
Ask questions, don’t just deliver news. “Are you okay?” matters more than the information dump.
Apologize for delays when you have legitimate excuses. He apologized for not getting back to me sooner when he was managing major transitions. That’s caring about the relationship, not just the transaction.
The cost? Maybe 15 minutes. The return? I’d walk through fire for that leader and company.
Quick Action Steps
Today: Pull out your calendar from the last month. Count how many conversations with leadership were about deliverables vs. about you as a person. That ratio tells you everything.
This Week: If you lead anyone, block 15 minutes with someone on your team. No agenda about projects. Ask one question: “How are you actually doing?” Then shut up and listen without pivoting to work.
This Month: If you realize you’re only being useful, don’t quit tomorrow. But start one conversation with someone who values you (former manager, mentor, peer). Ask them what they see in other companies. Information is the first step to options.
Want more of this in your inbox? Subscribe for new issues every Tuesday.
Sorry, the comment form is closed at this time.