The Onboarding Budget Was Cut. Your New Hire Was Never Pricing It.

I was sitting at my desk in my home office. Just another Tuesday morning. A Slack message came in from a new hire, Jim, buried in his onboarding feedback: “Tina often tells me, just because it’s been done one way doesn’t mean it always has to be done that way.” I had to read it a few times before it sunk in. Tina is a technical writer. I don’t remember ever teaching her that sentence directly.

I have said some version of that line for decades, since a C++ developer I can no longer name taught it to me while tuning SQL queries at my first programming job. I have repeated it in one-on-ones and process meetings across every team since, long enough ago that I stopped hearing myself say it. Tina had picked it up years before she formally joined the team, absorbed the way you absorb a phrase from someone you’re around often enough: never assigned, never trained. She was passing it forward as her own line to a new hire who had no idea it traced through her, through me, back to a developer whose name has already passed into legend.

There was nothing at stake in that Slack message. Nobody needed anything from me. It was entirely unexpected, and a grin spread across my face that had nothing to do with the actual content of the feedback he’d submitted. It brightened the rest of that day. What stayed with me wasn’t the sentence itself, it was the proof inside it: whatever I actually do, consistently, without being told to, is what travels. Nothing about that transmission required a budget, an HR program, or anyone’s sign-off. It required only that I kept doing it.

That is not the story most managers tell themselves about onboarding. The common version, the one that gets repeated in exactly the rooms where budgets get cut, is that a thin onboarding budget explains a thin onboarding experience: no formal curriculum, no dedicated buddy program, no structured ninety-day plan, and there is only so much one manager can be expected to do about it. Every technical leader who has ever had a headcount freeze land on their team knows this reasoning by heart, and almost none notice they’re using it to excuse the parts of onboarding that were never bought or paid for at all.

When a manager accepts that framing, they do not just accept a thinner formal program. They quietly stop contributing everything that was never on finance’s ledger to begin with: showing up consistently, repeating what actually matters until it holds, being present for the parts that cost nothing but attention. A new hire doesn’t experience that absence as the company under-investing this year. They experience it as their manager, specifically, choosing not to, and they read it fast: not months in, weeks, because presence and absence travel through the identical channel, proximity and repetition. One of them is just running nothing through it.

The Qualtrics 2026 Global Employee Experience Trends Report puts a number on how far that reading travels: only 44% of new hires now intend to stay with their organization more than three years. The report’s own framing is blunter than most: “new hires arrive engaged but leave jaded.” That number gets misread almost every time it’s reported: a comp problem, a market problem, occasionally a culture problem at the company level. Closer to the ground, it is a compounding spiral. A new hire who reads their manager’s absence correctly does not just leave quietly; they become the informal warning system for the next hire, telling them which managers are worth trusting before the org chart does. Enboarder’s 2025 HR Leader Survey found 60.8% of HR leaders reporting that 90-day turnover had worsened over the past year, even as onboarding checklists kept getting marked complete on paper. The checklist was never what anyone was actually pricing.

The leaders who hold onto their best new hires through a budget freeze are not the ones who found extra funding somewhere. They are the ones who stopped letting the funding decision decide what they, personally, were still willing to do.

Separate what’s resourced from what’s authored. The resourced layer is whatever HR built and finance approved: formal, budgeted, and mostly outside any one manager’s control. The authored layer is what a manager does on their own initiative, consistently enough that it requires no approval to keep running: the principle repeated until it becomes air in the room, the presence that doesn’t wait for a scheduled check-in, the consistency a new hire can set their expectations by. This is closer to what LeadershipOS™ calls Culture as System Memory than it is to any training curriculum: not what gets written on a slide, but what the system has actually, repeatedly signaled will hold true. The resourced layer can run thin. The retention outcome does not have to follow it down, if the authored layer is designed on purpose instead of left as whatever is left over once the checklist is finished.

Think about your most recent hire, whenever that was. What have you personally done for them that required no budget, no HR program, and nobody’s approval, and could they name it back to you if you asked them right now?

I write about structural leadership for technical leaders in high-stakes operating environments. The full operating model is in LeadershipOS™: http://TheLeadershipOSBook.com

---

I write about structural leadership for technical leaders in high-stakes operating environments. If you're reading this outside the daily email, subscribe free: https://technicalleader.coach/daily-email