The worst development conversation I ever witnessed lasted 11 minutes. The manager pulled up a form, asked “so, where do you see yourself in five years?”, received a polished non-answer, typed something into the system, and both parties went back to their desks relieved it was over.
That conversation was technically completed. It was also completely useless. And it represents how development conversations happen in most organizations: a ritual that exists to satisfy HR’s tracking system rather than to actually develop anyone.
The irony is that development conversations, when done well, are one of the highest-impact activities a manager performs. A single conversation that helps someone see a blind spot, commit to a stretch goal, or find direction in a confusing career moment can redirect months of effort. The gap between bad development conversations and good ones is enormous, and it has nothing to do with forms or frameworks.
Why do most development conversations fail?
Three patterns kill development conversations before they start:
They’re bundled with performance reviews. When the same conversation includes “here’s your rating” and “let’s talk about your growth,” people can’t be open about their real gaps. Evaluation puts people in defense mode. Development requires vulnerability. Mixing them guarantees you get neither done well.
They happen on a schedule, not when they matter. Annual or semi-annual development conversations are like checking your car’s engine every 12 months. A lot can go wrong between check-ins. The manager who has a brief development conversation when a team member just finished a challenging project gets more value than the one who waits for the HR-mandated quarterly slot.
Managers don’t know what to do with the answers. A team member says “I want to move into product management.” The manager nods, writes it down, and neither of them knows what happens next. Without a clear connection between aspiration and action, development conversations become a list of wishes that nobody revisits.
What makes a development conversation actually work?
After observing hundreds of these conversations (and coaching managers through them), a pattern emerges. The good ones share three qualities:
The team member does most of the talking. If the manager is speaking more than 30% of the time, it’s a lecture, not a development conversation. The manager’s job is to ask the right questions, listen carefully, and help the team member think more clearly about their own growth.
It ends with a specific, small action. Not “develop leadership skills” but “volunteer to lead the next sprint retrospective and get feedback from two peers afterward.” The smaller and more specific the commitment, the more likely it actually happens.
Someone follows up. The action from the last conversation gets revisited in the next one. This single practice transforms development conversations from forgettable rituals into an ongoing growth thread that builds over time.
A framework for conversations at different career stages
Not every development conversation covers the same ground. What someone needs to hear depends on where they are.
For people in their first two years on the team
The conversation is about building competence and confidence. These team members are still figuring out what good looks like in their role. They need honest feedback about what’s working, what isn’t, and what the path from “adequate” to “strong” looks like.
Try opening with: “What part of your job feels natural to you now, and what still feels like you’re figuring it out?”
This question accomplishes two things. It validates their growing competence (the “feels natural” part) and normalizes the gaps they’re still closing. Most new team members assume they should know everything already, and naming the learning curve as expected, not shameful, opens up honest conversation.
For strong performers who’ve plateaued
These conversations are trickier. The person is good at their job. They might not see a gap because there isn’t one in their current role. The development conversation is about expanding their view of what’s possible.
Try: “If you could add one capability to your toolkit that would make you dangerous in a good way, what would it be?”
This reframes growth from “fixing weakness” to “building strategic advantage.” Strong performers respond to ambition-oriented framing much better than gap-oriented framing.
For people preparing for a role transition
Whether it’s moving into management, switching functions, or stepping into a senior individual contributor role, transitions create the richest development conversation opportunities. The person is motivated, the stakes feel real, and the gaps are concrete.
Try: “What about the new role do you think will be hardest for you, and how can we start preparing for that now?”
This grounds the conversation in honesty about the challenge ahead rather than optimistic platitudes about how they’ll be great.
For people who seem stuck or disengaged
The hardest development conversations happen with team members who’ve lost their spark. They’re not failing, but they’re not growing either. Approaching this with curiosity rather than judgment matters enormously.
Try: “I’ve noticed you seem less energized lately. I’m not bringing this up as a performance concern. I’m asking because I want to understand what would make work feel better for you.”
This framing separates development from evaluation and opens space for the person to be honest about what’s going on.
Practical scripts for common difficult moments
Development conversations often hit moments where the manager isn’t sure what to say. Here are scripts for the most common ones.
When someone shares an unrealistic goal: Don’t: “That’s not really possible here.” Do: “That’s an ambitious goal, and I respect that. Let’s break it down: what would need to be true for that to happen in the next 12 to 18 months? And what’s the first step we could take in the next 30 days?”
When someone says “I don’t know what I want”: Don’t: “Well, think about it and come back to me.” Do: “That’s completely normal. Instead of the big picture, let’s start small: in the last three months, what work made you feel most engaged? And what felt like a drain? The pattern usually tells us something.”
When someone only wants promotion: Don’t: “There aren’t any openings right now.” Do: “I hear that promotion matters to you, and I want to help you get there. Let’s identify the two or three skills you’d need to demonstrate consistently for that to be a clear decision. Then we can build a plan around those.”
When someone gets emotional: Don’t: Rush past it or change the subject. Do: Pause. Acknowledge it. “This clearly matters to you, and I’m glad you’re being honest about it. Take whatever time you need.” Then continue from where they are, not from where your agenda says you should be.
The development conversation template that actually works
Templates are useful as a starting point, not a script. Adapt this to your style and the specific person.
Before the conversation (5 minutes of prep): Review what you discussed last time. Note any observations about their work since then. Identify one specific thing you want to acknowledge and one specific area you want to explore.
Opening (2 minutes): Set the tone. “This is about your growth, not an evaluation. I want to hear what’s on your mind.” Ask one opening question and then listen.
Exploration (15 to 20 minutes): Follow their energy. If they’re excited about a project, explore what skills it’s building. If they’re frustrated, dig into what’s behind it. Your questions should help them think, not lead them to a predetermined conclusion.
Good questions for this phase:
- What’s been the most valuable thing you’ve learned in the last few months?
- Where do you feel like you’re growing? Where do you feel stuck?
- What would you like to be doing more of? Less of?
- What feedback have you gotten recently that surprised you?
Action planning (10 minutes): Narrow from broad exploration to a specific commitment. “Based on what we’ve discussed, what’s one thing you want to focus on before our next conversation?” Help them make it concrete. Identify what support they need from you.
Closing (3 minutes): Summarize the commitment. Agree on when you’ll check in on it. Thank them for being open. Mean it.
Where AI coaching extends what development conversations start
A development conversation happens maybe once a quarter. The work of development happens every day in between. This is where the conversation-to-action gap opens up, and it’s where most development stalls.
A manager identifies in a development conversation that their team member needs to work on giving upward feedback to stakeholders. Great insight. But between quarterly conversations, that team member faces a dozen moments where they could practice this skill and either freezes or forgets.
AI coaching fills this gap. When that team member needs to prepare for a difficult stakeholder conversation, they can rehearse with Risely’s Merlin beforehand. They get feedback on their approach, practice different framings, and build confidence before the real moment. The development conversation identified the goal. The coaching supports the daily practice that makes it happen.
This creates a cycle that compounds: the development conversation surfaces goals, coaching supports practice between conversations, and the next conversation reviews progress and adjusts. Each cycle builds on the last rather than starting from scratch.
Making development conversations part of your culture
The biggest mistake organizations make is treating development conversations as an HR initiative rather than a management practice. When development conversations are mandated, tracked, and reported on, they become compliance exercises. When they’re modeled, valued, and integrated into how management works, they become catalysts for growth.
Practical steps for making this shift:
Train managers on coaching skills, not conversation templates. The ability to ask good questions, listen without an agenda, and help someone think through their own development is more valuable than any form or framework. Managers who can coach will have effective development conversations regardless of the template.
Disconnect development conversations from the performance review timeline. Let managers schedule them when they make sense: after big projects, during transitions, when someone seems stuck, or when an opportunity arises. Rigid schedules create rigid conversations.
Celebrate the outcomes, not the completion. Instead of tracking “what percentage of managers completed development conversations,” share stories of people who grew, took on new challenges, or changed direction because of a conversation. Make the value visible.
Give managers their own development conversations. The single most effective way to teach managers how to have good development conversations is to have great ones with them first. Managers who experience the value personally are far more likely to create it for their teams.
Good development conversations don’t require special training budgets or new software. They require managers who care about their people’s growth, know how to ask good questions, and follow through on what they discuss. Everything else is support for that foundation. When you help your team members build personalized learning plans through genuine conversation, the impact on engagement, retention, and performance follows naturally.
Related reading: