Role-Specific Onboarding: Fixing the Hardest Stage of Onboarding

On the surface, everything seems to be going to plan. The new hire shows up at the company, is greeted by HR, signs the contract, goes through health-and-safety training, picks up their equipment, and learns the basics of how the company works, its culture, and its procedures. For a few hours, sometimes a few days, they feel looked after.

And then comes the moment of handing the new hire over to their direct manager. The newcomer introduces themselves to the team and suddenly… emptiness. The manager has no time for them, and nobody on the team knows what the onboarding plan is. Sometimes the situation gets rescued by colleagues who spontaneously pitch in.

If you know this story firsthand, you probably already see where the problem lies. Not in recruitment, not in signing the paperwork, and certainly not in the color of the work uniform or the slide deck about company culture. The problem often starts the moment HR finishes its part and the baton passes to the direct manager. And they don't always know what to do with it.

These aren't isolated cases. Our report "Onboarding in Poland 2025," published in early 2025, shows that:

• 27% of Polish employees went through no role-specific onboarding at all,
• 52% never met their direct manager during onboarding,
• 12% had no one looking after them on their first day,
• 1 in 5 people received no information about the goal of their probation period,
• 22% of new hires considered leaving within the first 3 months of employment.

The data is unsettling, but it points to something important: a brilliantly organized company-wide onboarding isn't enough. The real quality of onboarding is decided in the team and with the manager—the place where HR loses control.

And it's not about a lack of willingness on managers' part. Quite the opposite—most of them mean well. But effective onboarding of a new hire is more than good intentions. It's a complex process that has to be planned, grounded not only in the context of the organization but also of the specific team, and supported by the right tools.

At Gamfi we often say that onboarding a new hire is a train made up of many cars. HR pulls it through the first stations—recruitment, pre-onboarding, paperwork. But then it has to pass the baton—and that's exactly when it's decided whether the train keeps rolling smoothly or jumps the tracks.

Neglecting role-specific onboarding is a serious gap in the onboarding process. And today we want to talk about it honestly—from an HR perspective, but with full understanding of the realities of managers' day-to-day work.

Managers mean well, but they're drowning in the day-to-day

This isn't about a lack of goodwill. Managers usually want to help the new hire step into the role. But onboarding isn't their only task—and very often it isn't even treated as a task. There's a customer to serve, a project to close, KPIs to prepare, a meeting with IT, an equipment order to place… In the middle of all that, the new person on the team is a bit like a passenger who's just boarded a speeding train—and doesn't know where to sit.

Without a clearly mapped onboarding plan, the list of tasks the new person should complete in the first weeks gets lost in the manager's flood of day-to-day duties. And without that plan, there's no structure, no priorities, and no path to full effectiveness—which is, after all, exactly what onboarding is meant to deliver as fast as possible.

The role of the direct manager in onboarding is crucial—and at the same time dramatically underrated (including by the managers themselves). The manager becomes the first point of contact, the guide, the mentor, the person responsible for preparing the new hire to perform the role. But nobody prepared them for that.

Often the manager doesn't know:

• what the company's onboarding standards are,
• what exactly they should do in the first weeks,
• how long onboarding a new hire should take,
• how the whole onboarding was designed at the HR level,
• whether and how they should also handle the social and relational side of integrating the new person into the team,
• how and when they should check whether the employee has reached independence in their role.

In the middle of all this, the new team member arrives like a passenger at a station no train pulled into. Let's step into their shoes for a moment. Imagine you join a new company. On day one you learn the basics: how the organization works, its structure, the HR systems, maybe even its culture. You get your equipment, go through initial training, and sign your documents. HR makes sure everything is buttoned up.

And then you land "on the role"—and from that moment everything depends on your manager. And that's often where the chaos begins. Because the manager:

• is in the middle of an important project and has 6 meetings a day,
• is simultaneously recruiting another person for the team,
• is reporting quarterly results to the board,
• is rolling out a new process in the CRM,
• is putting out fires that keep flaring up in the team, and so on.

The new hire doesn't want to be a bother, so they "observe," "get a feel for things," "learn on their own." The result? After two weeks they have only a vague idea of what actually falls within their responsibilities.

Role-specific onboarding: a no-man's-land nobody owns

What we usually call onboarding is only the introduction. Familiarizing the employee with the organization's structure, culture, values, and ways of working is an important stage—it gives broader context for their daily duties. But for the new person, that context only makes sense once it's genuinely anchored in their everyday work—that is, in the tasks of a specific role.

The manager sees it the same way. They kicked off the recruitment because they need someone who'll start delivering results "right off the bat." The pressure is clear: reach independence, effectiveness, and results as fast as possible. The trouble is that between company onboarding and actually stepping into the role stretches an area no one really takes responsibility for.

That's exactly the role-specific onboarding—the no-man's-land.

HR finishes its part on the formal side: signed contracts, granted access, a welcome pack, initial training. The employee is handed over to the team, and specifically to the manager. Except the manager often doesn't see onboarding as their job. In their head, onboarding = "a welcome to the company." And since that's already happened—well, that means HR did its part.

The result? The new person lands in the team, but with no plan of action. No clearly defined expectations. No support in the first weeks. No feedback.

The most common mistakes in role-specific onboarding—on both sides

1. No role-specific onboarding plan

Many organizations have an orderly general onboarding plan—but don't create an onboarding plan for the new hire's specific role. It's like handing someone a world map with no destination marked. The employee doesn't know where they're headed—or how to tell they've arrived.

2. Treating role-specific onboarding as a separate stage

The moment of handing the new hire over to the team is often treated as the end of onboarding. But onboarding into the role should be a smooth continuation of general onboarding—steered coherently by HR and the manager together.  

3. Reducing onboarding to knowledge transfer

Many managers focus on getting the new hire up to speed on tasks, procedures, and tools as fast as possible—"figuring out what they have to do." Preparing the workstation matters, but it isn't enough. An equally important (and often overlooked) element is introducing the employee to the team, the style of collaboration, and the unwritten rules—everything that makes up the everyday of work and shapes a sense of belonging. 

4. No systematic feedback

Without feedback it's hard to talk about growth. The new person doesn't know whether they're doing something well, and the manager doesn't know what the employee is struggling with. As a result, both sides "wait" instead of acting.

5. No success metrics

Organizations rarely measure onboarding. And yet time to independence, post-onboarding satisfaction, and retention in the first months are concrete data that show whether the process works—or merely exists.

What does good role-specific onboarding consist of?

Companies often believe that "if the new person sits next to a more experienced colleague for two days, they'll get onboarded." That's a myth. Role-specific onboarding isn't an event—it's a process that should be designed, planned, and run deliberately.

For the onboarding process to have a real impact on effectiveness and engagement, it has to include several key components:

1. Welcome and relationship-building

• welcoming the new hire to the team,
• introducing the team (including informal roles, e.g. "the CRM expert," "the account owner for client X"),
• pointing them to someone for ongoing support (e.g. a buddy, a mentor),
• a conversation about communication style and the team's rules.

2. Introduction to the scope of duties

• walking through the job description (if one exists) and clarifying the daily tasks,
• showing what a "typical workday" looks like,
• discussing expectations around outcomes and quality of work,
• showing the dependencies—who the employee gets tasks from, who they hand them to, who verifies them.

3. Setting goals for the probation period

• discussing the goals and metrics that will form the basis of the post-probation review,
• pointing out milestones (e.g. "after 2 weeks you'll have mastered X, after a month you'll be running Y"),
• defining the success criteria.
  

4. Sharing knowledge about tools and procedures

• onboarding into the tools in use (systems, apps, documentation),
• going over the applicable procedures (e.g. reporting absences, reporting, working with clients),
• access to manuals and training materials,
• where relevant, an invitation to role-specific training (internal or external).
  

5. Introduction to the business context

• explaining the significance of the role and how the new hire's role fits into the company's processes,
• discussing who the department works with and how (e.g. contact with IT, sales, marketing),
• sharing information about the products/services they'll work with, the competition, and the market environment.
  

6. A plan for the first day and the first weeks

• a schedule of tasks for week 1, month 1, and beyond,
• indicating what the employee should observe, who to meet, what knowledge to fill in,
• adding "trial" tasks with increasing independence.
  

7. Regular meetings and two-way feedback

• scheduling 1:1s (e.g. weekly),
• giving feedback—constructive, specific, supportive,
• encouraging questions and the sharing of doubts,
• signaling when onboarding will be wrapping up—and what changes that brings.

8. Social onboarding

• including the employee in team meetings and daily rituals (dailies, weeklies),
• inviting them to informal initiatives (e.g. a coffee together, a Slack channel),
• building a sense of belonging.

9. Checking readiness for independent work

• assessing whether the employee understands their tasks and can carry them out independently,
• identifying areas that need support,
• summarizing the probation period—against the goals set earlier.

That's a lot, isn't it? Now you can see how many things—often underrated and scattered—go into good role-specific onboarding. It's not "tossing in a few tasks to start," but a comprehensive process: from knowledge transfer, through goal-setting, to relationship-building and integrating into the team's culture. For a manager who's running projects, accountable for results, and managing people all at once, that's a huge challenge. That's why HR should act as the navigator in this process—providing the structure, tools, and clear framework that help the manager bring the new hire into their role step by step.

What can HR do to help managers?

First—accept reality. Managers won't design onboarding plans from scratch. They won't create checklists and organize training if they don't have the tools to do it.

Second—provide ready-made support that lifts off the manager the burden of planning and coordinating everything on their own. HR should create the conditions in which the manager has everything they need to do it well.

In role-specific onboarding, HR can create and streamline:

• templates for onboarding plans for different roles,
• checklists of actions assigned to roles (HR, manager, buddy, IT),
• a calendar with reminders about key activities,
• metrics for onboarding progress and outcomes (e.g. surveys, pulse checks),
• ready-made scripts for feedback conversations.

‍

A command center for role-specific onboarding in an onboarding app

Company-wide onboarding, coordinated by HR, is a relatively centralized process—one training, one message, many participants. But at the transition to role-specific onboarding, onboarding starts to branch out—it reaches different teams, managers, departments, and specifics. That's exactly where the process becomes most complex, because it requires standardization and flexible tailoring at the same time. 

That's why HR's role isn't only to design the whole thing, but also to merge these scattered paths into a coherent experience—and tools that automate the process are practically irreplaceable for that job.

This is where Gamfi comes in. With our onboarding platform you can design and automate the entire flow of onboarding into the role—from the first meeting with the manager to the conversation that wraps up the probation period.

With the Gamfi onboarding platform:

• The manager gets a ready-made action plan in the form of a clear checklist tailored to the role and the team.
• The app automatically reminds the manager about key tasks exactly when they should do them (e.g. scheduling a feedback meeting, handing over tools, bringing the new hire into the team's rhythm).
• The manager can delegate some tasks to the buddy—and track whether they've been done.
• They have a view of progress—they can see what stage of onboarding each team member is at, where bottlenecks appear, and how satisfied the employee is.
• They get instructions and prompts—e.g. how to run a 1:1 or give constructive feedback.
• Tasks and content are tailored to the department's specifics, while keeping consistent standards across the whole organization.
• HR has access to data that shows what works and what needs adjusting—so onboarding can be not only planned, but continuously improved.

Want to help new employees? Help the manager

The biggest trap in onboarding is the assumption that "it'll just happen." That once the manager "welcomes the new person," everything will go smoothly. But it doesn't work that way.

It's worth thinking about onboarding a new hire as an experience the organization designs—from the start, through familiarizing the employee with their tasks, to the end of the probation period.

If you want onboarding that genuinely works, don't ask: "Did our manager onboard the new person?" Ask: "What did we do to make it easy for them to do it well?"

‍