Why Your Best Tech Is About to Quit

This one is for the managers.

Not the frontline supervisors who work alongside their teams every day. The directors. The decision-makers. The people who establish the work culture, curate department budgets, and write the annual performance reviews. If you manage technology professionals, this is the conversation your best person wishes they could have with you, but won’t.

So I’ll have it for them.

Your best tech is not thinking about leaving because of the money. The money matters, but that’s not what’s discouraging them. What’s deflating their morale balloon is the slow, accumulating realization that what they do doesn’t seem to matter. Not to you, and not to the broader leadership who’ve never heard their name spoken in a meeting they weren’t invited to.

They brought you an idea a couple of months ago. It could have been a better way to handle a major software update, or a tool that could save them and their teammates hours every week, or a different approach to client support that they’d been testing quietly on their own. You listened politely. Then, in that weekly update email, you ghosted their idea and redirected the team’s attention to a customer service article you’d read about leveling up IT support. The conversation was over. Their idea didn’t get rejected. It got something worse. It got absorbed into silence.

They grit their teeth when receiving recommendations to publish Knowledge Base articles or send mass email announcements to “all users” about known issues. They understand what you’re actually building: a case that the experts are unnecessary. If every answer lives on a website or an email blast, why do you need the person who built the expertise? They see it. They just haven’t said it out loud yet.

They notice that their input is welcome when it confirms what you’ve already decided, and quietly redirected when it doesn’t. They’ve learned to read the room in your meetings the same way they read the room in their consultations. The difference is that in their consultations, reading the room makes the work better. In your meetings, reading the room means knowing when to stop talking.

Here is what your best tech wants. It’s not complicated and it’s not expensive.

They want to feel like a thinking partner, not a task-completer. They want their years of experience treated as input worth considering, not just output worth measuring. They want the autonomy to do what they know is right without being challenged by someone who isn’t immersed in the work the way they are.

And most importantly…they want you to know them. Not their job description. Not their favorite kind of doughnut for weekly staff meetings. Them. Do they do their best work in the morning or the evening? Do they have family obligations that a little flexibility would honor? Do they thrive on public recognition or would that embarrass them? Do they need a quiet office or can they think in an open floor plan? Do they want a raise, or do they want to hear you say “what you do matters to this organization”?

These are not difficult questions. But most managers never ask them. They manage the role instead of the person, and then act surprised when the person leaves.

Here is the part that should concern you most: your best tech has been doing for their clients exactly what you have not been doing for them. They sit with people. They learn how they work. They pay attention to what makes each person feel capable instead of small. They have built an entire practice around the principle that the human being matters more than the technology.

They’ve just been waiting to see if anyone would do the same for them.

More later…