Discuss a Development Goal When No Promotion Opening Exists

An employee sits down and says they want to grow, and they want to know what comes next. You do not have an open role to offer them. That gap between ambition and opportunity is where these conversations usually fall apart. Handle it well and the employee leaves with real work to do and trust in you intact. Handle it badly and they leave thinking you dodged the question, or worse, that you made a promise you cannot keep.

Why This Conversation Goes Wrong

Most managers default to one of two bad moves. The first is false comfort. You tell the employee something vague and hopeful, like there might be an opening soon, because you want the conversation to end on a positive note. That sentence gets repeated back to you in six months when nothing has changed, and now you have a trust problem on top of a staffing problem.

The second bad move is the flat no. You tell the employee there is nothing available right now, and you leave it there. That answer is honest, but it treats a development conversation as if it were only a job posting question. The employee did not just ask about an opening. They asked what they need to build. If you answer only the availability question, you miss the actual request underneath it, which is guidance on their growth.

Both mistakes come from treating the conversation as one you have to resolve on the spot, when it is really the start of an ongoing plan.

How To Prepare Before You Sit Down

Before the conversation, separate two things that often get tangled together, the role and the skill. A promotion is a staffing decision that depends on budget, structure, and timing you may not control. A skill is something you can help someone build right now regardless of what openings exist. Decide in advance that you will talk about the second thing, not make promises about the first.

Think through what you already know about this person. What have they done well. What feedback have they gotten, from you or from peers. What gap sits between where they are and the role they want. If you do not have a clear answer, ask them directly what kind of responsibility interests them and what experience they already have. Their answer tells you what to look for.

Then scan your actual work for something real. A stretch assignment only helps if it has a clear scope, a named person who owns the final decision, and a date to review how it went. An assignment without those three things turns into extra work with no evidence attached, and evidence is the entire point.

If your organization has a formal career framework or leveling guide, pull it up before the meeting. Vague reassurance is worse than none. Pointing to the actual criteria the organization uses gives the employee something concrete to work toward instead of your best guess.

What To Say In The Conversation

Start by naming the ambition without agreeing to a timeline. Nina opens with the direct version of the question. She says, "I want to become a team lead this year. What do I need to do?"

Carlos does not promise an opening, and he does not shut the conversation down either. He says, "I cannot promise an opening this year. What I can do is help you build the experience that will matter if one comes up." He points to something specific. "You have run our weekly queue well for months. Would you like to lead the next two queue reviews, gather input from the team, and bring me a recommendation afterward?"

Nina pushes for more before she commits. "Yes, I would like that. Could I also sit in and watch how you handle it when people disagree in those meetings first?"

Carlos agrees and sets a boundary around what they will evaluate. "We can set that up. After your second meeting leading the review, we will sit down and look at what you learned and how the group responded to you."

Notice what happened in that exchange. Carlos answered the real question, which was about capability, not the surface question, which was about title. He gave her something to do this week, not a date on a calendar. And he set a review point so the conversation has a natural next step instead of dissolving into silence until she asks again.

Mistakes That Undermine The Conversation

Do not let the meeting end without a concrete assignment attached to a date. Good intentions fade fast, and an employee who leaves with only encouragement will read your silence over the following weeks as a soft no.

Do not frame the stretch work as a test she has to pass to earn a promotion. That framing turns every difficult moment in the assignment into a threat instead of a learning opportunity, and it pushes people toward hiding problems rather than raising them.

Do not confuse this conversation with a conflict conversation. If the employee's frustration is really about a peer or a process breakdown, the skill you need is different, and it helps to read Respond When an Employee Wants You to Solve a Conflict so you do not try to solve the wrong problem with a development plan.

Do not skip the follow up. The most common failure is not the initial conversation. It is the absence of the second one. Put the review date on your calendar in front of the employee, not after they leave.

How To Practice And Score This Conversation

This conversation is hard to get right on the first try because it asks you to hold two things at once, honesty about constraints and genuine support for someone's growth. Most managers lean too far in one direction under pressure.

Before you have the real conversation, run it once with a counterpart who pushes back the way a real employee might, including someone who gets frustrated or asks you to commit to a timeline you cannot promise. DealSpeak's HR and Leadership practice conversations are built for exactly this kind of rehearsal, and the scoring after the exchange tells you whether you actually named a specific opportunity, set a review date, and avoided vague promises about future roles.

Score yourself on three things after any version of this conversation, real or practiced. Did you name one capability the employee should build. Did you attach one specific piece of work to that capability. Did you set one date to look at evidence together. If you can answer yes to all three, the conversation did its job even without a role to offer. If the employee also mentioned feeling disconnected from the team lately, that is worth a separate look, and Explain the Next Step After an Engagement Survey covers how to carry that kind of signal into its own conversation.

Where This Leaves You

You cannot manufacture a role that does not exist, and you should not pretend otherwise. What you can do is hand someone real work, a clear way to be seen doing it well, and a date to talk about what you both learned. That is a plan an employee can act on today, which is more useful to them than a promise about a year from now.