Mentr

Mentoring research, sourced and dated.

8 min left

Corporate Mentorship ProgramsR-05Mentr

R-05 · Corporate Mentorship Programs · Published 2026-09-02 · 1,716 words

A Practical Mentoring Plan for New Employees

Give new hires clear support from their manager, buddy, and mentor, with a sample check-in plan and an approach for small teams.

An experienced colleague helping a new employee settle into a shared workspace.

To mentor a new employee, start with the work they need help doing. Give them a named person for everyday questions, a manager who owns expectations, and a place to talk through what they are learning. Agree who handles each responsibility before putting recurring meetings in the calendar.

The plan below is a suggested approach, not a fixed onboarding standard. Adapt the timing to the role, the employee’s experience, and the support your team can provide. You can use it inside an existing mentoring program or start with a single pairing.

Give each person a clear responsibility

For this plan, divide support among a manager, an onboarding buddy, and a mentor. These are responsibilities to assign, not a requirement to recruit three different people.

Role Suggested responsibility Questions to bring to them
Manager Own the onboarding plan, priorities, training arrangements, workload, and performance feedback What should I deliver first? What does acceptable work look like? Which task takes priority?
Buddy Help with everyday processes, introductions, and finding the right person or resource Where is the current template? Who can fix my access? How does this team organize its meetings?
Mentor Help the employee reflect on situations, practice skills, and consider development goals How could I approach this conversation? What am I missing? Which skill should I work on next?

There is support for separating these responsibilities, without treating the labels as universal. The U.S. Office of Personnel Management puts the immediate supervisor in charge of orienting new employees in its federal hiring guidance. Its career development guidance describes mentoring as guidance and career advice, usually with someone outside the employee’s supervisory chain.

Microsoft Research’s remote-onboarding guidance gives buddies a role in locating resources and connecting new hires with colleagues. For software developers, it also recommends a technical mentor to help with details of the work. A mentor’s contribution can therefore start with an immediate task, rather than waiting until onboarding is over.

Keep the manager accountable for the overall plan. A buddy can help the employee find a training link, and a mentor can discuss a difficult assignment. Neither should have to guess which training is required or decide what the employee’s manager expects.

Match around a real learning need

Before choosing a mentor, ask the new employee what they would like help with. Offer examples if they have not yet worked out where they need support:

  • Understanding how decisions get made in this team.
  • Practicing a task they have not done before.
  • Adjusting to a new level of responsibility.
  • Building working relationships beyond their immediate team.
  • Talking through a situation they find difficult to judge.

Use that answer to choose someone with relevant experience and enough time to meet. Do not use job title alone as the matching criterion. For a technical goal, consider an experienced colleague who knows the work before seeking a senior leader in another function.

Offer an introductory conversation before asking either person to commit. Ask both whether the goal fits the mentor’s experience and whether the proposed schedule is realistic. Provide a named contact for changing the match, and make it clear that asking for a change is allowed.

For a new graduate, a possible goal is preparing a clear update for a team meeting. For an experienced hire, it might be understanding how to challenge a proposal in an unfamiliar organization. These are examples to discuss, not assumptions to make about people at different career stages.

Set expectations at the first meeting

Use the first conversation to agree on a working arrangement. Write down the goal, how you will meet, how to contact each other between meetings, and when you will review the arrangement.

Discuss privacy explicitly. Agree what the pair will share with the manager, such as the broad learning goal or a request for training. Decide whether notes will be kept and who can see them. Check the organization’s reporting rules before promising confidentiality, and identify where concerns should go if the mentor cannot handle them.

Do not turn mentoring into a second performance review. If the manager needs to address a missed deadline or unclear expectations, arrange that conversation with the manager. The mentor can help the employee prepare for it and think through what they want to ask.

For a ready-to-use opening agenda, see questions for a first mentor meeting. Bring a real issue to that meeting too. There is no need to postpone useful work until the pair has completed a prescribed number of introductory conversations.

Use a check-in plan you can change

Here is an illustrative plan for the first three months. The intervals are planning suggestions, not a tested formula or a promise of faster productivity.

When Manager and buddy support Mentoring conversation
Before the start date Name the manager and buddy. Prepare access, an initial task, and the first-week schedule. Identify possible mentors and leave room for the employee’s preferences.
First week Explain priorities, make introductions, and resolve access problems. Discuss the employee’s experience, immediate questions, and a possible learning goal.
Weeks two to four Check that instructions and required resources are available. Give feedback on early work. Discuss a recent situation. Choose something to try before the next meeting.
Second month Review workload and adjust training or task scope. Revisit the experiment. Practice a skill or arrange a relevant introduction.
Third month Review the onboarding plan and agree what support is still needed. Decide whether to continue, change the goal, change the match, or close the pairing.

As a starting point, offer a short mentoring meeting every other week, with permission to change the frequency. Keep quick access questions with the buddy or the relevant support team. Protect mentoring time for the learning goal, while leaving space for something urgent that the employee wants to discuss.

Do not make the end of a checklist an automatic end to support. In its federal context, OPM describes orientation as an ongoing process, rather than a single event. Use the review date to ask what is still useful, not simply whether the calendar has run out.

Make each conversation useful

Try this simple sequence for a check-in:

  1. Ask the employee to describe one recent situation.
  2. Clarify what they wanted to happen and what happened instead.
  3. Explore possible explanations before giving advice.
  4. Offer relevant experience as an example, with room for a different approach.
  5. Agree on one action and what the employee will notice or record afterward.

For example, imagine a new account manager who gives a detailed project update but receives little response. The buddy can explain where meeting notes belong. The manager can clarify the purpose of the update. The mentor can help the employee practice opening with a decision the group needs to make.

At the next mentoring meeting, review how the revised update went. Ask whether the request was clearer and whether the employee got the information they needed. Avoid rating the whole relationship from a single successful meeting. Use what happened to choose the next step.

This is a hypothetical example of dividing responsibility. It does not mean every new employee needs presentation practice or that the same change will work in every meeting.

Start small if there is no existing program

For a small employer, try one willing pair before designing a company-wide system. Ask the manager to protect meeting time, confirm the goal with the employee, and name someone who can help if the pairing becomes unworkable. Organize this initial trial with a shared calendar and a brief agreement.

If the same colleague serves as buddy and mentor, make the two uses of their time explicit. For example, invite everyday questions through a team channel and set aside a separate conversation for development. Review whether the combined responsibility is manageable before adding another new hire to it.

If nobody internally has the relevant experience, consider a mentor from a professional network or another organization. Keep internal onboarding responsibilities with the manager, and agree what company information may be discussed externally.

Where a workplace mentoring program already exists, check its entry dates and available mentors. Offer interim support if the employee would otherwise wait for the next formal intake. Let them decide whether the existing program suits their goal.

Make asking for help straightforward in remote teams

Microsoft Research recommends that colleagues share their communication preferences, and that managers explain which channels to use for different kinds of questions. Turn that into a short contact guide for your new hire.

List where to ask about access, tasks, people policies, and mentoring. Agree when a message is sufficient and when a call would help. Make response expectations explicit, including what to do if the named person is unavailable. Choose meeting times that respect both participants’ working hours.

For the mentor, offer a specific invitation: bring the situation you were unsure how to handle this week. For the buddy, offer a practical one: send over any process or terminology that still needs explaining. Avoid making the employee infer what either person is willing to discuss.

Review the support, not just the meeting count

At the agreed review point, ask the employee and mentor separately whether the arrangement is useful. Use questions such as:

  • Does the employee know where to take different questions?
  • Is the learning goal still relevant?
  • Can the employee describe something they tried or understood differently?
  • Are meetings happening at a manageable pace?
  • Is another kind of support needed?

Treat answers as feedback for improving this pairing. Ask about the conversations themselves instead of judging their usefulness by attendance alone. If you also track retention or performance, do not present a change as proof that mentoring caused it without evidence that separates mentoring from other influences.

Finish the review with a decision the pair can act on: continue toward the same goal, choose a new one, arrange different support, or close the pairing. Give the employee a clear next contact in every case.