Close a Development Conversation With an Observable Commitment

A development conversation can end two ways. It can end with a phrase like "communicate better" or "show more leadership," which sounds like progress but gives no one anything to check next week. Or it can end with a specific action, a place it will happen, and a way both people will know if it worked. As a people manager, your job in that closing minute is to push past the intention and land on the second kind of ending.

Why This Conversation Goes Wrong

Most development conversations fail at the very end, not the middle. The diagnosis part goes fine. The employee names a growth area, you both agree it matters, and the conversation feels productive. Then the meeting runs long, someone glances at the clock, and you close with something like "keep working on that" or "let's revisit this next quarter." Nobody wrote down what "that" means in practice.

Vague endings feel comfortable because they avoid conflict. Naming one small, visible action forces you to pick something, and picking something means the employee might resist it, or you might realize you do not actually know what good looks like for this skill. It is easier to end on warmth than on specifics. But warmth without a specific behavior gives the employee nothing to rehearse, and gives you nothing to notice.

There is also a matching problem. Traits like influence, confidence, or executive presence do not point to a single behavior. Two people can agree that someone needs "more presence" and picture completely different actions, one imagining a louder voice in meetings, the other imagining better written updates. If you do not convert the trait into an observable moment, you and the employee may spend a month each executing a different plan while believing you are aligned.

How to Prepare

Before the conversation, pull one recent, real example of the growth area in action, ideally one the employee already recognizes. A general trait only works when you anchor it to something that happened. If you plan to discuss someone's influence, think of the last meeting where you watched them hold back, and be ready to ask them to walk through it rather than describe it in the abstract.

Decide in advance what kind of support sits on your side of the table. Some growth areas need a skill the employee does not yet have, and no amount of practice will produce it without instruction. If the gap is technical, that is a training conversation, not a behavior conversation, and you should say so plainly rather than asking someone to improvise a skill they were never taught. If the gap is really about applying a skill they already have, an observable commitment is the right tool.

Think also about the setting where the commitment will play out. It should be a real, upcoming event, not a hypothetical one. A planning meeting next Tuesday, a client call already on the calendar, a document due this week. Something specific enough that you can both check it off or ask about it without guessing what happened.

What to Say

Rachel tells her manager, Paul, that she wants to build more influence across the product group. Paul does not let the goal stay that broad. He asks her to describe one real meeting where she wanted more influence and did not get it. Rachel describes a planning session where she had the usage numbers everyone needed, but she waited until the agenda was almost finished to bring them up, and by then the group had already decided.

Paul asks, "What could you do in the next planning session that people in the room would actually notice?" Rachel answers, "I will send the usage chart the day before, and ask for five minutes near the start to walk through one recommendation." Paul asks one more question. "What will tell either of us whether you made the case clearly?" Rachel decides she will ask two peers afterward whether they understood the decision she was pushing for.

That exchange takes under three minutes, and it produces something neither "grow my influence" nor "speak up more" could produce alone. It names a meeting, a specific action inside that meeting, and a way to check the result that does not depend on Paul's impression by itself.

Mistakes to Avoid

Do not let the commitment stay at the level of a trait. If the employee answers with "I will be more assertive," ask again for the moment and the room where that will show up. Assertive in what meeting, said to whom, about what.

Do not make the commitment so large that it cannot start before your next conversation. A commitment that depends on a project three months out gives you nothing to review soon, and the energy from the conversation fades before the action happens. Keep it small enough to attempt this week or next.

Do not promise an outcome you do not control. Telling someone this behavior will get them promoted, or will fix how a difficult colleague treats them, sets up a conversation later where the outcome did not follow and the trust between you takes the hit. The commitment is a practice attempt, not a guarantee. If someone is chasing a promotion, that is a distinct conversation about what a role actually requires, and it deserves its own discussion rather than a promise folded into this one. The post on how to Discuss a Development Goal When No Promotion Opening Exists covers that case directly.

Do not skip your own follow through. If you agree to spend ten minutes reviewing what happened, put it on your calendar before the employee leaves the room. A commitment that only the employee tracks quietly becomes a commitment nobody tracks.

How to Practice and Score It

The skill here is not knowing the theory, it is asking the right follow up question in the moment, under time pressure, when a vaguer answer would let you end the meeting sooner. That is a rehearsal problem, and reading about it will not tell you whether you actually push hard enough when a real employee gives you a soft answer like "I will just try to speak up more."

Run the conversation against a counterpart that plays a real employee, offering the kind of vague, well meaning answer people actually give. Notice whether you accept the first trait word offered, or whether you keep asking for the meeting, the action inside it, and the way you will both know it happened. Score yourself on whether the conversation ends with a date, a place, and a signal, not just a feeling that the talk went well.

DealSpeak's HR and Leadership practice conversations let you run this exact scenario with an AI counterpart and get scored on whether your closing questions actually produced an observable commitment or just a nicer sounding intention. If you manage a team where development conversations tend to surface real friction, the related post on how to Respond When an Employee Wants You to Solve a Conflict is worth practicing alongside this one.

Close

An observable commitment does not guarantee the employee's growth, and it does not need to. It gives both of you a small, real thing to look at together next time you talk. That is what turns a development conversation from a nice moment into an actual habit of improvement.