All Articles & Blog Posts
A man and woman collaborate on her laptop, using an AI tool to enhance their work and career outcomes.

Career Development Conversations: A Manager’s Guide

Career development conversations are structured, forward-looking discussions between a manager and a direct report about where that person wants their career to go and what it will take to get there. They sit apart from performance reviews. They sit apart from weekly check-ins. Most managers are told to have them and handed nothing to run them with.

That gap is why these conversations get skipped, or turn into twenty vague minutes about growth. A manager sits down without a structure, asks what the person wants to do next, hears “I’m not sure,” and both people leave with nothing written down.

This guide closes the gap. You get a four-part structure you can run in forty-five minutes, thirty questions grouped by what they are for, a preparation prompt for the calendar invite, scripts for the three hardest answers, and the operating model HR needs to make this happen across two hundred managers rather than the handful who already do it well.

What a career development conversation is (and what it isn’t)

A career development conversation is a scheduled discussion in which a manager helps an employee define their long-term career direction, assess the gap between current skills and target roles, and agree on specific development actions. It is forward-looking, is not tied to a rating or pay decision, and typically runs 45 to 60 minutes twice a year.

Three things get confused with it, and the confusion ruins them.

  • The performance review. A review looks backward at a rating period, feeds compensation, and carries a judgment. The moment a career conversation feels like it might affect someone’s rating, they stop being honest about what they want. If you are preparing an evaluation cycle, how to prepare a performance review covers that separately.
  • The 1:1. A one-on-one is tactical and weekly, handling blockers, priorities, and status. Career direction loses every time it competes with a live deadline, which is why it needs its own meeting. For the cadence side, see how to get the most out of your 1×1 meetings.
  • The promotion conversation. Promotion is one possible output, not the subject. Lateral moves, skill depth, scope expansion, and internal transfers are all legitimate outcomes.

Development conversations use feedback as raw material but do not exist to deliver it. The art of feedback is its own discipline.

Why managers avoid these conversations

Four objections come up constantly. Each has a real answer.

  • “I can’t promise a promotion.” You are not being asked to. The commitment is to visibility and access, not to an outcome you do not control. A manager who says “I cannot promise a director role in eighteen months, and here is what would have to be true for you to be a credible candidate” is more useful than one who says nothing. Ambiguity is what people leave over, not honest limits.
  • “I don’t know their options outside my team.” Neither does your report, which is why the conversation matters. Your job is not to be a directory of every role in the company. It is to name two or three people they should talk to, then make the introduction. Brokering three conversations does more for someone’s career than reciting an org chart.
  • “I’ll trigger them into leaving.” This objection deserves the most scrutiny, and the data cuts the other way. Global employee engagement fell to 20% in 2025, with manager engagement dropping to 22%, down nine points since 2022, according to Gallup’s State of the Global Workplace 2026. People disengage inside the job long before they resign from it. The conversation you are avoiding is already happening without you, with a recruiter or a friend.

Gartner sharpens the point, naming regrettable retention as a primary productivity barrier for 2026 and noting that internal mobility rates have stayed flat despite rising investment. Keeping someone in a role they have outgrown is a stalled person occupying a seat, and the team can see it.

  • “I don’t have time.” Two conversations a year at 45 minutes is 90 minutes per person, or twelve hours for a manager with eight reports. Compare that to a single backfill: the requisition, the interview loop, the ramp.

When to have them

Run career development conversations twice a year, decoupled from the performance review cycle by at least six weeks.

The decoupling is what organizations get wrong. When a career conversation sits in the same month as calibration, employees read it as an audition and give the answer they think helps their rating. Six weeks is enough separation for the two meetings to feel like different things. March and September work well when reviews run in January and July.

Four moments justify an extra conversation.

  1. After a promotion cycle closes, whether the person was promoted or not. The two weeks after a decision lands is when someone is most open and most at risk.
  2. After a reorg. Reporting lines, scope, and adjacencies all changed. The path someone mapped six months ago may no longer exist in the shape they drew it.
  3. At the 12-month mark in a role, roughly when competence turns into comfort, and comfort is where quiet stagnation starts.
  4. When someone declines an opportunity. A turned-down project is information. Find out whether it was timing, confidence, family circumstances, or a signal that they want something different than you assumed.

How to prepare (manager and employee)

Manager prep

Spend twenty minutes before the meeting on four things.

  • Re-read the last two conversations and the commitments made. Nothing kills credibility faster than forgetting what you promised in March.
  • Review their recent work for evidence, not impressions. Pull two or three examples of what they did well and where they got stuck.
  • List every internal role, project, and person you could connect them to. You want raw material, not a recommendation.
  • Check what you know about openings, headcount, and budget, and mark which of it you can share.

What not to do: decide in advance what their career should be. Managers who arrive with a plan run a meeting where the employee’s job is to agree, which produces compliance and no information.

Employee prep

Paste the prompt below into the calendar invite at least three days ahead. Three days lets people think. Three hours produces improvisation.

This is a career conversation, not a performance review. Nothing here affects your rating or your pay. Before we meet, jot down rough answers to four things and send them over, or just bring them: (1) What do you want to be doing in two to three years, even if you are unsure? (2) What work in the last six months are you proudest of, and why? (3) What is currently in your way? (4) What is one thing you want me to do differently to help? Bullet points are fine.

A four-part structure for the conversation

Use the AROC structure: Aspiration, Reality, Options, Commitment.

AROC builds on GROW, the coaching model developed by Sir John Whitmore and colleagues in the 1980s that nearly every university HR guide on this topic references. Two things changed. GROW opens with Goal, meaning a goal for the session; career conversations need a longer horizon, so AROC opens with Aspiration. 

GROW closes with Will, the coach’s motivation to act, which fits a coach with no authority. A manager has authority and owns half the actions, so AROC closes with Commitment: written, owned, and dated on both sides.

1. Aspiration

Purpose: surface direction before constraints get introduced. Say nothing about feasibility yet.

  • “Forget what’s available here. What do you want to be doing in three years?”
  • “What kind of problems do you want to be known for solving?”
  • “Do you want to go deeper in what you do now, or wider into something new?”

Failure mode: correcting the aspiration in real time. The instant you say “that’s probably not realistic,” you will get safe answers forever. Write it down and test it in the next section.

2. Reality

Purpose: establish shared evidence about where they are now, using specifics rather than adjectives.

  • “What in the last six months are you proudest of, and what specifically did you do?”
  • “Here’s where I see your strengths, with two examples. Does that match how you see it?”
  • “Between where you are and the role you described, what’s the honest gap?”

Failure mode: turning this into a feedback session. One piece of forward-looking, evidence-based feedback is useful. A list of development areas becomes an unscheduled review and destroys the trust the first section built.

3. Options

Purpose: generate more than one path, including paths that lead away from your team.

  • “There are three ways I can see to get there. Tell me what I’ve missed.”
  • “Who here already does what you want to learn? Would an introduction help?”
  • “What would a lateral move buy you that a promotion wouldn’t?”

Failure mode: offering exactly one option, almost always the one that serves your headcount. If every path keeps the person on your team, you are not developing them. An internal mobility strategy gives managers something concrete to point at.

4. Commitment

Purpose: convert the conversation into three to five actions with owners and dates.

  • “Let’s agree on three things. What are you taking, and what am I taking?”
  • “By when? Put a real date on it.”
  • “What should be different by the time we meet again in six months?”

Failure mode: all the actions belong to the employee. If the manager owns nothing, the person correctly reads the meeting as theatre. Take at least one yourself and make it visible, like a named introduction by a specific date.

30 career conversation questions

Pick four to six per conversation. All thirty turns the meeting into an interrogation.

Aspiration

  1. If you could design your role two years from now, what would be on your calendar that isn’t today?
  2. Whose job in this company would you want to try for a month, and what part of it appeals to you?
  3. What kind of problems do you want to be known for solving?
  4. When you eventually leave here, what do you want to have learned?
  5. Do you want to go deeper in what you do now, or wider across something new?
  6. What did you think this career would look like when you started, and what’s changed?

Strengths and evidence

  1. What work from the past six months are you proudest of, and what specifically did you do?
  2. Which parts of your job do people come to you for without being told to?
  3. What comes easily to you that others seem to find hard?
  4. What feedback have you received more than once, from more than one person?
  5. Where are you stronger than your current role lets you show?
  6. If I had to argue your case for a bigger role, what evidence would I use?

Obstacles

  1. What’s getting in the way of the work you actually want to do?
  2. What are you spending time on that someone else could do?
  3. What have you wanted to raise with me and haven’t?
  4. Where do you feel stuck, and how long have you felt that way?
  5. What would have to change for you to still be here in three years?
  6. Is there anything about how this team works that limits you?

Skills and gaps

  1. What’s the gap between what you can do today and what your target role requires?
  2. Which of those gaps can you close on the job, and which need real training?
  3. What skill are you avoiding because it looks hard or boring?
  4. Who inside the company already does what you want to learn, and have you spoken to them?
  5. What would you need to see yourself do to believe you were ready?
  6. What part of your current work is becoming less valuable, and what replaces it?

Next steps

  1. What one project next quarter would move you toward this?
  2. What do you want me to do differently to support this?
  3. Who else needs to know about your ambitions for them to be real?
  4. What’s the smallest version of this you could start in the next two weeks?
  5. What should we check on when we meet again in six months?
  6. If nothing changes between now and then, what will that tell us?

Employees preparing for their side of this can work through how to get promoted before they arrive.

What to do when the answer is no

Most guides stop before this. These three cases are where managers actually lose people.

They want a promotion that isn’t coming. Say so in one sentence, early. Then separate the two reasons, because they need different answers. If it is a readiness gap, name the two or three things that would change your assessment and put dates on them. If it is structural, meaning no open role and no budget, say that plainly. 

Dressing up a headcount constraint as a skills problem is the fastest way to lose someone’s trust, because they will eventually find out. When the ceiling is structural, your job shifts to helping them find scope elsewhere.

They want a role they’re not ready for. Do not say no and do not say yes. Define the evidence. “Here are the three things I’d need to see you do. Here’s a Q3 project where you could do the first one.” 

That converts a subjective judgment into a test the person can run, with a real chance to fail at something visible. If they clear the bar, you have your answer. If they do not, so do they.

They want to leave your team. Your reaction in the first ten seconds decides whether anyone tells you this again. Help them, visibly. Make the introduction. Tell them what you will say if the hiring manager calls. 

Agree a transition timeline that protects delivery. A manager known for exporting talent gets the first pick of internal candidates. Talent hoarding is visible to everyone except the hoarder. Career coaching and employee retention covers the economics behind that trade.

Turning the conversation into a plan

End every conversation with three to five commitments. Fewer than three and nothing changes. More than five and nothing gets done.

  • Each needs a named owner, a date, and a definition of what finished looks like. “Explore the analytics team” is not a commitment. “Coffee with the analytics lead by 15 October, arranged by me” is.
  • Split ownership deliberately. The employee takes two or three, such as a course, a proposal, or shadowing a colleague. The manager takes at least one that only a manager can do: an introduction, a stretch assignment, a name raised in a talent review.

Record them in the system your organization already uses for goals or one-on-ones. A separate document nobody opens is worse than nothing, because it creates the appearance of a process. 

Then surface them as a standing two-minute item on the next monthly 1:1 agenda. Keep it lighter than a full individual development plan, which is a separate artifact with a longer horizon.

How HR scales this across managers

Getting two hundred managers to do this consistently is a different problem from teaching one to do it well. Four things move the number.

  • Enable, do not just distribute. A template mailed to managers changes nothing. The skill gap is in handling the hard answers, not running the agenda. Sessions where managers rehearse “the promotion isn’t coming” out loud, with a peer playing the employee, do more than any document. New managers need this most and get it least, which is why first-time manager coaching and becoming a manager for the first time belong in the enablement path.
  • Publish a shared question bank. When every manager improvises, quality varies by manager rather than by employee need. A common bank raises the floor without scripting anyone.
  • Attach a light completion metric. Track that the conversation happened and commitments were recorded. Do not grade the content. The moment HR audits quality, managers write for the auditor.
  • Measure four things. Internal mobility rate, regrettable attrition among high performers, the engagement item on whether someone talks to me about my progress, and the share of open roles filled internally. SHRM’s 2026 Talent Trends Report found that 42% of HR professionals reported difficulty retaining full-time employees in the previous twelve months, while job rotation programs rated 93% effective at closing talent gaps sat below 25% adoption. The capability exists. The routing does not.

Managers cannot point people toward paths nobody has mapped, which is where skills-based career development does work a template cannot. The end state is not a compliant manager population. It is a culture of career ownership where employees arrive with a point of view and managers know what to do with it.

Career development conversations fail for an unglamorous reason: nobody gave managers a structure, and nobody gave them a script for the moment the answer is no. Fix those two things and the rest follows. To make this consistent across a manager population rather than a handful of naturals, explore our employee career development programs or talk to our team about manager enablement.

Leave a Reply

Your email address will not be published. Required fields are marked *

Share with friends

©2026 PathWise. All Rights Reserved
magnifiercrosschevron-down