Most development conversations fail for a simple reason: they focus entirely on what an employee should do next, without ever exploring what actually makes them want to do it. The result is a plan that looks good on paper and goes nowhere in practice.
This guide gives you a practical, step-by-step structure for using employee motivation drivers, specifically motive and driver insights from assessment reports, to run development conversations that produce real, lasting change. It's written for managers who want something they can use in their next 1:1, not a psychology textbook.
Who it's for: People managers running quarterly or annual development conversations. Prerequisites: Access to employee development report outputs (ideally covering Leadership, Competencies, Drivers, and Culture). Time required: 60-90 minutes for the conversation itself, 20 minutes of preparation. Difficulty: Beginner-friendly. No psychology background needed.
When a development plan stalls, it's rarely because the employee lacks talent. It's usually because the plan doesn't connect to what they find motivating.
Drivers and motives are the internal conditions that influence whether effort sticks over time. They're not personality traits or performance scores, they're signals about the environment and type of work where someone is most likely to thrive.
A practical lens for structuring this is Self-Determination Theory (SDT). According to the American Psychological Association's review of SDT research, human motivation in work contexts centers on three core psychological needs: autonomy (a sense of choice and ownership), competence (the feeling of growth and mastery), and relatedness (meaningful connection with others). When a development plan addresses at least one of these needs, engagement tends to follow. When it ignores all three, the plan feels like homework.
Using structured driver data in your conversation replaces gut-feel guesswork with specific starting points. You're not just reacting to what an employee says they want, you're cross-referencing it against what the data suggests, then exploring together where those two pictures align or diverge.
Before you book the meeting, get three things in order.
Get consent first. Assessment outputs, including Drivers reports, are shared to support development, not to evaluate performance or place limits on opportunities. Tell the employee explicitly: "I'd like to use the results from your assessment as a starting point for our conversation, not as a verdict." If you're using Selection Lab's development outputs, which cover Leadership, Competencies, Drivers, and Culture, make clear those four areas are frameworks for reflection, not scores to be judged against.
Bring the right materials. Pull the employee's development report, note the role expectations you're trying to align to, and identify one or two driver themes you want to explore. Don't try to cover everything in one conversation.
Ask for pre-work. A day before the meeting, ask the employee to jot down: one recent achievement they felt genuinely proud of, one recurring friction in their current work, and one growth question they keep coming back to. This primes reflection and means the conversation starts with their perspective, not yours.
Use this as a working agenda you can share with the employee in advance.
Here are ready-to-use questions mapped to the three core motivation factors. Use the ones that match the employee's dominant driver themes from their report.
Autonomy-focused questions:
Competence-focused questions:
Relatedness-focused questions:
When introducing the driver data, try this phrasing: "Your Drivers report suggests [theme]. Does that feel accurate right now, or is that more context-dependent?" This keeps the data as a conversation starter, not a conclusion.
Once you know the primary driver need, match it to a concrete action type. Here's a simple reference:
Driver need Development action examples Autonomy Project ownership, defining their own learning goals, choosing their method for a deliverable, leading a small initiative Competence Structured feedback loops, a skill-building sequence with checkpoints, a stretch assignment with scaffolding, shadowing a specialist Relatedness Cross-functional pairing, formal mentoring, joining a community of practice, leading a collaborative goal with a teamWhen multiple needs show up in the report, prioritize one or two levers for the current cycle. Trying to address everything at once produces plans that are too complex to follow through on.
This happens. The driver profile suggests a strong need for autonomy, but the employee says they actually want more structure right now. Or they push back on a relatedness theme because they've had a bad experience with team dynamics.
Don't override the employee's experience with the data. Validate first: "That makes sense, context shapes this a lot. What would feel most useful to focus on given where you are right now?" Then adjust the plan accordingly.
If the disagreement is more fundamental and the employee questions the accuracy of the report overall, acknowledge the limits: "These are signals to explore, not diagnoses. What matters is what actually feels true for you." Assessment outputs, including those from Selection Lab's development reports, are designed to open conversations, not close them.
The one thing to avoid: using driver insights to restrict what someone gets to pursue. Offering someone fewer opportunities because a report suggests they're not "motivated" by a certain type of work is both unfair and a misuse of the data.
Momentum fades if there's no cadence. Two to four weeks after the plan is set, run a quick check-in using these three questions:
Track progress through conversation signals, not just task completion. Is the employee showing more energy when they talk about the work? Are they taking initiative in the area you targeted? That's real evidence the development plan is connecting to the right driver need.
If something isn't working after two check-ins, modify the action before abandoning the plan. Often the goal is right and the activity just needs adjusting. Close each review cycle by confirming the next review date and which data you'll revisit together.
Development conversations work best when they're ongoing, not annual events. When driver and motivation factors are part of your regular 1:1 rhythm, employees stop experiencing development as something done to them and start treating it as something they're building alongside you.
Most development conversations fail for a simple reason: they focus entirely on what an employee should do next, without ever exploring what actually makes them want to do it. The result is a plan that looks good on paper and goes nowhere in practice.
This guide gives you a practical, step-by-step structure for using employee motivation drivers, specifically motive and driver insights from assessment reports, to run development conversations that produce real, lasting change. It's written for managers who want something they can use in their next 1:1, not a psychology textbook.
Who it's for: People managers running quarterly or annual development conversations. Prerequisites: Access to employee development report outputs (ideally covering Leadership, Competencies, Drivers, and Culture). Time required: 60-90 minutes for the conversation itself, 20 minutes of preparation. Difficulty: Beginner-friendly. No psychology background needed.
When a development plan stalls, it's rarely because the employee lacks talent. It's usually because the plan doesn't connect to what they find motivating.
Drivers and motives are the internal conditions that influence whether effort sticks over time. They're not personality traits or performance scores, they're signals about the environment and type of work where someone is most likely to thrive.
A practical lens for structuring this is Self-Determination Theory (SDT). According to the American Psychological Association's review of SDT research, human motivation in work contexts centers on three core psychological needs: autonomy (a sense of choice and ownership), competence (the feeling of growth and mastery), and relatedness (meaningful connection with others). When a development plan addresses at least one of these needs, engagement tends to follow. When it ignores all three, the plan feels like homework.
Using structured driver data in your conversation replaces gut-feel guesswork with specific starting points. You're not just reacting to what an employee says they want, you're cross-referencing it against what the data suggests, then exploring together where those two pictures align or diverge.
Before you book the meeting, get three things in order.
Get consent first. Assessment outputs, including Drivers reports, are shared to support development, not to evaluate performance or place limits on opportunities. Tell the employee explicitly: "I'd like to use the results from your assessment as a starting point for our conversation, not as a verdict." If you're using Selection Lab's development outputs, which cover Leadership, Competencies, Drivers, and Culture, make clear those four areas are frameworks for reflection, not scores to be judged against.
Bring the right materials. Pull the employee's development report, note the role expectations you're trying to align to, and identify one or two driver themes you want to explore. Don't try to cover everything in one conversation.
Ask for pre-work. A day before the meeting, ask the employee to jot down: one recent achievement they felt genuinely proud of, one recurring friction in their current work, and one growth question they keep coming back to. This primes reflection and means the conversation starts with their perspective, not yours.
Use this as a working agenda you can share with the employee in advance.
Here are ready-to-use questions mapped to the three core motivation factors. Use the ones that match the employee's dominant driver themes from their report.
Autonomy-focused questions:
Competence-focused questions:
Relatedness-focused questions:
When introducing the driver data, try this phrasing: "Your Drivers report suggests [theme]. Does that feel accurate right now, or is that more context-dependent?" This keeps the data as a conversation starter, not a conclusion.
Once you know the primary driver need, match it to a concrete action type. Here's a simple reference:
Driver need Development action examples Autonomy Project ownership, defining their own learning goals, choosing their method for a deliverable, leading a small initiative Competence Structured feedback loops, a skill-building sequence with checkpoints, a stretch assignment with scaffolding, shadowing a specialist Relatedness Cross-functional pairing, formal mentoring, joining a community of practice, leading a collaborative goal with a teamWhen multiple needs show up in the report, prioritize one or two levers for the current cycle. Trying to address everything at once produces plans that are too complex to follow through on.
This happens. The driver profile suggests a strong need for autonomy, but the employee says they actually want more structure right now. Or they push back on a relatedness theme because they've had a bad experience with team dynamics.
Don't override the employee's experience with the data. Validate first: "That makes sense, context shapes this a lot. What would feel most useful to focus on given where you are right now?" Then adjust the plan accordingly.
If the disagreement is more fundamental and the employee questions the accuracy of the report overall, acknowledge the limits: "These are signals to explore, not diagnoses. What matters is what actually feels true for you." Assessment outputs, including those from Selection Lab's development reports, are designed to open conversations, not close them.
The one thing to avoid: using driver insights to restrict what someone gets to pursue. Offering someone fewer opportunities because a report suggests they're not "motivated" by a certain type of work is both unfair and a misuse of the data.
Momentum fades if there's no cadence. Two to four weeks after the plan is set, run a quick check-in using these three questions:
Track progress through conversation signals, not just task completion. Is the employee showing more energy when they talk about the work? Are they taking initiative in the area you targeted? That's real evidence the development plan is connecting to the right driver need.
If something isn't working after two check-ins, modify the action before abandoning the plan. Often the goal is right and the activity just needs adjusting. Close each review cycle by confirming the next review date and which data you'll revisit together.
Development conversations work best when they're ongoing, not annual events. When driver and motivation factors are part of your regular 1:1 rhythm, employees stop experiencing development as something done to them and start treating it as something they're building alongside you.
