The Part of Onboarding Nobody Builds: Knowing Who to Lean On

Chaos is a great diagnostic tool. When everything goes sideways at once, you find out very quickly who your real support network is. Not the org chart version. The actual version: who picks up the phone, who knows the backup plan, who you can be honest with about the fact that you're lost.

Most people build that network over time, through repeated small moments of trust and reciprocity. It takes months. Sometimes longer. And in the middle of a genuinely bad week, you either have it or you don't.

New hires don't have it. They walk in on day one with zero of it. And most onboarding programs do nothing to help them build it faster.

What Chaos Actually Reveals

Think about the last time something went badly wrong at work. A deadline collapsed. A system went down. A decision needed to be made with incomplete information and no time to get more. What got you through it wasn't the employee handbook. It was knowing exactly who to call and being confident they'd actually help.

That confidence is built on two things: knowing the person exists, and knowing they're safe to go to. Both take time to establish under normal conditions. Under onboarding conditions, where everything is new and the stakes of first impressions feel high, most new hires won't reach out at all. They'll try to figure it out alone rather than look like they don't know what they're doing.

69% of employees are more likely to stay with a company for three years if they had a great onboarding experience. The research consistently points to connection and belonging as the primary driver, not information transfer. SHRM, Onboarding New Employees: Maximizing Success

Connection isn't a nice-to-have. It's the mechanism by which a new hire becomes resilient. Without it, every hard moment in the first 90 days becomes a referendum on whether they made the right choice taking this job.

The Org Chart Doesn't Tell You Anything Useful

Most onboarding programs address the "who to talk to" problem by handing over an org chart and a directory. Which is about as useful as giving someone a map of a city they've never visited and expecting them to know which neighborhoods are actually worth walking through.

What a new hire actually needs to know isn't who technically owns a process. It's things like: who is the person everyone goes to when the official channel is too slow? Who is patient with questions that might seem obvious? Who has context on a decision that isn't written down anywhere? Who should you loop in before doing something that touches their area, even if they're not on the org chart for it?

That's institutional knowledge. It lives in people's heads. And it almost never makes it into onboarding materials because the people writing those materials have had it so long they've forgotten it wasn't always obvious.

The Four Relationships Every New Hire Needs

Not every workplace relationship matters equally in those first 90 days. Research from Dr. Talya Bauer's onboarding framework identifies connection as one of the four foundational Cs of effective onboarding, alongside compliance, clarification, and culture. But connection without structure is just hope.

In practice, there are four types of relationships that meaningfully reduce a new hire's vulnerability during the adjustment period:

These don't need to be formally assigned roles. They need to be explicitly named in onboarding materials, with enough context for the new hire to understand what each person is actually for. Not just a name and a title. A sentence or two about when and why to go to them.

The Backup Plan Problem

There's a related issue that gets even less attention: new hires rarely know what the contingency looks like when something goes wrong.

Experienced employees know this instinctively. They've seen the thing break before. They know the system has a fallback, or that a certain person keeps the real documentation, or that the process everyone follows has an unofficial shortcut that everyone uses when it's urgent. New hires don't know any of that. So when something breaks, they either freeze or escalate unnecessarily, both of which cost time and erode confidence.

Good onboarding anticipates this. It doesn't just describe the normal path. It tells the new hire what to do when the normal path isn't working: who to contact, what to check, and how to know whether something is genuinely urgent or just unfamiliar.

The question most onboarding materials never answer

"If I'm stuck on something and my manager isn't available, what do I do?"

It's such a basic question. The answer at most companies is that the new hire figures it out eventually, usually by making a few wrong calls first. There's no particular reason that answer can't just be written down.

Why This Gets Left Out

Connection and contingency get deprioritized in onboarding for the same reason they get deprioritized everywhere: they feel soft. You can't put a checkbox next to "understands who to lean on." You can put a checkbox next to "completed security training."

So the checkboxes win. The compliance items, the system access, the policy acknowledgments. All of it important. None of it sufficient. A new hire who has completed every required module and still doesn't know a single person they'd be comfortable calling in a crisis is not actually onboarded. They're documented.

Being documented is not the same as being ready.

What to Actually Include

This doesn't require a restructured onboarding program. It requires adding a few things to the onboarding document that most programs currently omit.

A named guide or buddy, with a sentence about what that person is there for. An explicit escalation path for when the manager isn't reachable. A short "when things go wrong" section that covers the two or three most common failure points and what to do about each one. And a genuine signal that it's fine to not know things yet, because new hires often don't ask for help because nobody has told them it's safe to.

That last one costs nothing to include and probably does more work than everything else on the list.

The Bottom Line

The weeks that reveal whether your onboarding worked aren't the easy ones. They're the chaotic ones, the weeks when priorities shift, systems break, and context matters more than any training module could have prepared someone for. Those are the weeks when a new hire either has a support network to lean on or discovers they're on their own.

Building that network doesn't happen automatically. It happens by design. Good onboarding names the people, explains what they're for, and tells the new hire explicitly that asking for help is the right move. Most onboarding programs don't do any of that. They leave connection to chance and call it culture fit when it doesn't happen.