Latest / Hiring & Firing with Fexingo: Recruitment, Performance, and Workforce Decisions / The Silent Tax of Unstructured Onboarding
Transcript
- Lucas: Let’s talk about the moment a new hire actually becomes a productive member of your team. Most managers think that happens when they hand over the login credentials and schedule the first one-on-one. But the data suggests the real clock starts ticking the day after orientation ends. If the structure collapses then, you aren’t just losing time; you are losing the competitive edge you paid for during recruitment. Luna: So you’re saying the handoff from hr to the direct manager is where the value leaks out? Lucas: Exactly. It’s not that the hr department does a bad job sending the welcome packet. It’s that the hiring manager assumes the new person will figure out the unwritten rules by osmosis. In a complex organization, those rules are rarely obvious. I’ve seen teams spend six weeks waiting for a junior analyst to accidentally replicate a reporting error that had been corrected three years ago, simply because no one explicitly taught them the new protocol. Luna: That sounds like a failure of documentation rather than personality. Lucas: It’s a failure of intention. Documentation exists, but it’s static. Onboarding isn’t about reading a wiki page; it’s about behavioral calibration. When a new person joins, they are hyper-vigilant. They watch how people speak in meetings, who gets interrupted, and what mistakes get laughed off versus what ones get flagged. If the team doesn’t actively model the right behaviors in those first ninety days, the new hire mirrors whatever dysfunction they see. Luna: And once that mirror image sets, it’s incredibly hard to reverse later. Lucas: Right. You can correct technical skills with training modules. You cannot easily correct cultural fit if it was misaligned from week two. Let’s look at the financial side of this drift. Research consistently shows that poor onboarding reduces employee engagement by up to fifty percent. That isn’t just a soft metric about happiness; it translates directly to output quality and error rates. Luna: Fifty percent seems steep. Is that across all roles or just high-skill positions? Lucas: It holds true across most knowledge work sectors. The difference is visibility. In a factory, a mistake is physical and immediate. In an office, a mistake might be a slightly misaligned sales pitch or a delayed project update. Those errors compound quietly. By the time the quarterly review comes around, the manager realizes the new hire has been working at half-capacity for four months, wondering if they should fire them or promote them. Luna: So the manager is flying blind until it’s too late to fix the trajectory. Lucas: Precisely. And here is the kicker: the new hire feels equally lost. They know they are underperforming, but they are afraid to ask questions because they don’t want to look incompetent. So they stay silent, make assumptions, and produce mediocre work. The manager sees the mediocre work and thinks the hire was a bad decision. Meanwhile, the hire thinks the manager is impossible to please. Everyone loses. Luna: That cycle destroys trust before the probationary period even ends. Lucas: It does. Which brings us to the solution, which is surprisingly simple but rarely implemented. Structured check-ins. Not the vague 'how are things going?' question that happens once a month. I’m talking about weekly, agenda-driven conversations that focus exclusively on integration, not just task completion. The manager needs to ask specific questions about roadblocks, clarity of expectations, and relationship building within the team. Luna: Does that require more time from busy managers who are already swamped? Lucas: It requires thirty minutes a week. That is the investment. If a manager spends three hours a week coaching a new hire properly in the first month, they save dozens of hours correcting mistakes in the second and third months. It is arithmetic. You pay now or you pay later with interest. The cost of fixing a cultural misalignment is exponentially higher than the cost of establishing norms early. Luna: I like that framing. It turns onboarding from an administrative chore into a strategic investment. Lucas: Exactly. And let’s address the elephant in the room regarding remote work. Remote onboarding makes this dynamic worse because the casual learning opportunities vanish. You can’t overhear a phone call to learn how a client handles objections. You can’t watch a senior colleague format a deck to understand aesthetic standards. In a remote environment, you have to be deliberate about sharing context that used to happen organically. Luna: So the burden shifts entirely onto the manager to broadcast that context. Lucas: Yes. And many managers aren’t equipped for that. They assume transparency is automatic. It isn’t. You need protocols. For example, requiring every meeting recording to be shared with notes, or mandating that new hires shadow two different stakeholders per week. These are small structural changes that replace the invisible curriculum of the office. Luna: Shadowing sounds like it could disrupt workflow if not managed well. Lucas: Only if you treat it as an interruption. Frame it as learning. Tell the team, 'we are bringing in Alex to observe our client calls so we can standardize our approach.' Suddenly, shadowing becomes a quality assurance tool for the whole department, not just a favor for the new hire. It elevates the entire team’s awareness of their own processes. Luna: That reframes it nicely. It stops being about babysitting and starts being about excellence. Lucas: Spot on. Now, I want to pause here for a quick word about how this show stays on the air. A handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that is literally what funds making these episodes. No ads, just community support keeping the research sharp. Luna: It really helps us dig into these deeper structural issues without chasing clicks. Lucas: Thanks for considering it. Back to the mechanics of retention. Once those first ninety days are stable, you hit the next critical juncture: the first performance review. This is where most organizations fail again. Luna: Because they wait too long to give feedback? Lucas: They wait too long to calibrate expectations. If the first review is six months out, the new hire has been operating on guesswork for half a year. Even with good check-ins, ambiguity creeps in. The review shouldn’t be a surprise assessment of past behavior; it should be a calibration session for future goals. It’s the point where you say, 'here is what you did well, here is where we missed marking the path, and here is what we expect next quarter.' Luna: So the review becomes a planning tool rather than a judgment tool. Lucas: Ideally, yes. But in practice, it often becomes a complaint box. Managers dump all their accumulated frustrations into one hour. That is toxic for morale. It signals that the manager wasn’t paying attention during the interim. If the first review feels like a shock, the onboarding process was broken, not the employee. Luna: Which circles back to the idea that management is continuous, not episodic. Lucas: Always. Let’s look at a specific case study from a mid-sized logistics firm that turned this around. They implemented a ninety-day roadmap before the new hire even started. They assigned a buddy, not a mentor. A buddy is peer-level, focused on navigation and social integration, while the manager handles performance. This separation ensures the new person has someone safe to ask dumb questions without fearing it will impact their evaluation. Luna: That psychological safety piece is huge. People hide ignorance when they feel judged. Lucas: Exactly. And the buddy system scales better than you think. One buddy can support two or three new hires simultaneously. It distributes the load and creates a cohort effect. New hires bond with each other, which increases retention significantly. They have peers to vent to and celebrate with, creating a micro-community within the larger company. Luna: So the social fabric is part of the operational efficiency. Lucas: It is. Loneliness is a primary driver of turnover in the first year. When people feel isolated, they look for exits. Structured onboarding combats isolation by design. It forces connections that wouldn’t happen naturally. It turns strangers into colleagues, and colleagues into teammates. Luna: I wonder if smaller startups struggle with this more because they lack formal hr structures. Lucas: They do, but ironically, they have more flexibility to fix it. Startups can build onboarding into their DNA from day one. They don’t have legacy bureaucracy to untangle. If a startup founder treats onboarding as a core product feature, they win. If they treat it as overhead, they burn cash replacing people constantly. The math is the same regardless of company size. Luna: It’s interesting that you call it a product feature. Most founders see it as a cost center. Lucas: Because they measure the wrong things. They measure time to hire, not time to productivity. time to hire is easy to optimize with aggressive recruiting. time to productivity is hard because it depends on internal culture. If you only optimize for speed, you get fast hires who churn fast. That is a false economy. Slowing down the first month saves you months of re-recruiting later. Luna: So the goal is slower entry, faster ramp-up. Lucas: Precisely. Invest heavily at the start, then coast on momentum. If you invest lightly at the start, you spend the rest of the year patching leaks. It’s the difference between building a foundation and slapping paint on a crumbling wall. Both look similar initially, but one holds up under stress. Luna: And that stress test usually arrives during the first major crisis or deadline. Lucas: Always. When pressure hits, people revert to habit. If the habit was formed correctly, the team performs. If the habit was formed incorrectly, the team fractures. You can see the quality of onboarding in how a team handles a tight deadline. Do they collaborate seamlessly, or do they step on each other’s toes? That dynamic is set in those first few weeks. Luna: It really highlights how much of leadership is actually architecture. Lucas: It is. You are architecting the environment in which people behave. If the environment is ambiguous, behavior will be erratic. If the environment is clear and supportive, behavior will be consistent and high-quality. The trick is maintaining that clarity when the team grows and the noise level increases. Luna: Do you think ai tools can help automate some of that structural consistency? Lucas: They can handle the administrative heavy lifting—scheduling, document distribution, policy acknowledgments. But they cannot handle the human calibration. An ai bot can tell a new hire where the bathroom is, but it can’t teach them how to navigate office politics or read the room in a negotiation. The tech supports the process, but the human connection drives the outcome. Luna: So the tech frees up the manager to focus on the nuanced stuff. Lucas: Exactly. Use technology to remove friction, not to replace empathy. If you use ai to reduce the admin burden, you should see your managers spending more time in those meaningful one-on-ones. If they are spending less time, you have solved the wrong problem. You have optimized for efficiency instead of effectiveness. Luna: That distinction between efficiency and effectiveness is crucial in any business operation. Lucas: It is. And it applies everywhere, from supply chains to sales pipelines. But nowhere is it more visible than in how we treat the people joining our ranks. We hire them for their potential, but we retain them based on their experience. If the experience is poorly designed, the potential goes to waste. Luna: A powerful way to end the thought. Potential means nothing without the right vessel to hold it. Lucas: Agreed. The vessel is your culture, built brick by brick in those first ninety days. Make sure the mortar is strong.