Manager involvement determines onboarding.

Telling managers it is important. It is in the handbook. It was covered in the manager training. Everyone agrees. Nothing changes, because nobody disagreed in the first place.

Reminding them. An email, a Slack nudge, a task in the HR system. This produces an effect that decays within about a month, at which point the reminder has become a thing to dismiss rather than a thing to read.

Measuring them on it. This works better than the two and produces its own problem, which is that people optimize for the measurement. A manager who is scored on completing check-ins will complete check-ins. Fifteen minutes, on a phone between two meetings, questions asked and answers not heard. The number goes up. Nothing has happened.

The common thread is that all three treat this as a motivation problem. It is not. Managers are not skipping the conversation with their hire because they do not care about their new hire. They are skipping it because at 9:40 on a Tuesday something is on fire and the new person is not on fire yet.

Worth being precise about the mechanism because it explains what does work.

A reminder is a request for attention. It arrives in an inbox alongside every request for attention that person receives and it competes with them on urgency. The new hire conversation always loses that competition, not sometimes, but because it is the only item in the queue with no deadline and no consequence attached to moving it.

Everything else in a manager’s day has someone waiting on the end. A customer, an incident, a release, a colleague who is blocked. The conversation with the person who started on Monday has nobody visibly waiting, because the new hire is new and does not yet know that they are allowed to expect it.

So the reminder is not weak because it is poorly written. It is weak because it is asking for a resource without offering any claim on it.

Two things. They only work together. This is the part most people get wrong by doing one of them.

Reserved time. Not a reminder that a conversation should happen. A block in the calendar that occupies the scarce resource directly. The distinction sounds small and it is not: a reminder competes for time, a booked slot has already taken it. When the manager looks at Tuesday morning, the conversation is not a task to fit in. It is what is happening at ten.

A stated purpose. Here is where the reserved time alone falls down. A half-hour labelled "onboarding check-in" is easy to move because nobody knows what is lost when it moves. A slot that says what it is for and what both people are supposed to come out of it with is expensive to move because moving it now has a cost.

Clear objectives from day one attached to the time. What is being covered, what the new hire should be able to do, what the manager needs to have decided. That turns a calendar block into something with content, and content is what makes it defensible against the fire at 9:40.

All of the writing on this treats manager involvement as a manager compliance problem. How do we make managers do the thing? That framing loses half the mechanism. In our experience, it is the more reliable half.

The new hire wants this conversation. They want it considerably more than the manager does because they are three weeks into a job where they are not yet sure whether they are doing well and this is the only scheduled moment where they might find out.

A new hire will not chase a vague meeting. Nobody arrives on day four and asks their manager whether they still intend to hold a check-in that was mentioned once. What a new hire will do is show up to a conversation with a stated purpose that they were told about in week one, because now it belongs to them too.

That is the mechanism. Not one person being made accountable. Two people who both know what the meeting is for and both have a reason to protect it. When the manager’s Tuesday explodes, the difference between the conversation happening on Wednesday and not happening at all is usually whether the other person noticed it was missing.

Something said plainly because the maximalist version of this advice is wrong. Things move. A production incident, a customer escalation, a manager with flu. Rescheduling happens and it is not a process failure when Monday becomes a Tuesday. The failure is when a moved conversation quietly becomes a cancelled one. That is the transition that matters and it happens when nobody on either side is holding the thread.

It is worth being clear about what a cancellation communicates because it is not neutral. Dropping a fifteen- or thirty-minute conversation with someone in their first month tells them where they sit on the priority list, and they adjust accordingly. What they adjust to is worse for everyone: they stop asking in the moment, start sending emails, or hover near a desk waiting for a gap. Both are slower, both interrupt more and neither shows up as a cost.

What we see in practice is that the combination above survives rescheduling. Both people find each other again because they know what it was for and had been expecting something from it. What does not survive rescheduling is the slot with no purpose, which moves once and then evaporates.

So measure the thing. Not whether check-ins happened on the day they were scheduled, which will make your numbers look bad for reasons that do not matter. Measure whether they happened within a reasonable window. A program where forty percent get moved, and ninety percent get held is in shape. A program where nothing is ever moved and sixty percent quietly never happened is not. Its dashboard will look better.

Book it at offer acceptance. Not on day one when the calendar is already full. At signature when there is still room six weeks out. This is also the moment when everyone involved has time to think about it.

Book the people too. The buddy, the two or three colleagues the new hire needs to know for reasons that are not social. Introductions that depend on someone remembering to make them do not happen, and the people who suffer most from that are the ones comfortable introducing themselves.

Write what each conversation is for. One line is enough. "By the end of this you should know what you own in the thirty days and who to ask when you are stuck" is a different meeting than "onboarding check-in" and it is a different meeting for both people in it.

Tell the hire the schedule in week one. All of it. Who they are meeting, when and why. This is the step that converts a manager obligation into a shared expectation. It costs nothing.

Give the buddy their instructions. Being asked to be a buddy without being told what that involves is the common way to get a well-meaning colleague to do nothing. Three specific targets: what to do and when to do them.

Watch the pattern, not the event. One moved conversation is noise. A manager whose three all moved and none were rebooked is a problem you can act on while it is still small.

If you do all of this and a manager still does not show up, you have learned something. It is not about the process.

You have learned that this manager does not consider the person’s first month to be their job. That is worth knowing. It is worth addressing directly because no system will fix it and the next hire on that team will have the same experience as the last one.

That conversation is not an HR problem. Finding out early enough to have it is.