Why Career Development Fails When Nobody Asks What the Employee Actually Wants
A manager tells someone they are ready for more. More responsibility, a bigger remit, a seat at a table they have not sat at before. The employee nods, says thank you, and then does nothing with it for six months. From the outside, this looks like reluctance or a lack of drive. From the inside, it usually looks different. No one ever asks whether this particular kind of more is what they actually want, and quietly, without ever raising it directly, they resist a move that was handed to them rather than built with them.
This happens more often than organisations like to admit, and it explains much of the gap between how much money and time gets spent on career development at work and how little of it seems to change day-to-day behaviour. Career development is not short of frameworks, appraisal forms, or good intentions. What it lacks is early, honest agreement on what the person on the receiving end actually wants more of. The ten points below are not a checklist to work through in an afternoon. Read them as one connected argument, because that is what they are.
1. Treat "more" as a negotiation, not an instruction
Development offered as an instruction produces compliance at best and quiet resistance at worst. Neither gets you what you actually wanted when you made the offer. The alternative is slower and less tidy: ask what the person wants more of before deciding what to give them. That single change, checking before assigning, is the difference between an opportunity that gets taken up with energy and one that gets nodded at and left untouched.
This is not about handing over the decision entirely. The organisation still has a genuine say in what it needs and when. The difference is where the conversation starts. An instruction starts with the organisation's answer already decided, and asks the person to accept it. A negotiation starts with a question, finds out what the person actually wants, and only then works out where that overlaps with what the business needs. The end result can look identical on paper: the same new title, the same new responsibility, but one version was built with the person and the other was simply delivered to them.
2. Notice what happens when nobody asks
People who were never asked what they wanted tend to stop volunteering it. The first time someone is handed an opportunity that does not fit, they usually still try to make it work. The second or third time, something quieter happens. They stop raising their hand at all, and a manager reading that silence as contentment is almost always reading it wrong. This is harder to spot than open disagreement, and considerably more expensive over time, because by the time it shows up as a resignation letter, the disengagement itself has been sitting there unnoticed for months.
What makes this particularly easy to miss is that the person rarely becomes a worse performer in the meantime. They keep doing the job competently, meet their targets, and give no obvious signal that anything has shifted. What changes is smaller and less visible: they stop putting themselves forward for the next thing, stop mentioning what they would actually like to be doing, and start treating the role as something to manage rather than something to grow into. A manager who only checks whether output has dropped will miss this every time, because output was never the part that changed.
3. Understand why managers get this wrong with such confidence
Part of the answer is that managers are often confident about something they have got wrong. WorldatWork's 2026 State of Rewards study, which surveyed 1,316 managers and employees between January and February 2026, found that sixty-eight per cent of managers reported being extremely or very confident that they understood what their employees value. The same research found managers overestimated their employees' desire for traditional advancement by 15 percentage points, while underestimating how much people value flexibility by 14 points, benefits by 8, and paid time off by 6.
Worth noting, this was not a representative sample of the wider workforce. The respondents came through WorldatWork, HRCI and ITLN databases, the majority worked in HR or people operations, and the sample leaned towards the United States. Treat it as one credible, well-conducted study rather than a universal figure, because that is what it is.
What makes the finding worth building an argument around is not the mismatch alone. The same research found career development was among the strongest predictors of whether someone stayed, despite being one of the areas employees rated least satisfying. Employees dissatisfied with their career development were around 1.9 times more likely to say they were extremely unlikely to stay. That turns a question about being misunderstood into a question about retention, and it is a good deal harder to shrug off. It is the same underlying trust gap I have written about before in relation to what a team performance consultant changes, where confidence and accuracy pull apart in exactly this way.
4. Get specific about what you want, not what gets offered
One of the biggest mistakes I see professionals make is accepting the first shape an opportunity arrives in, rather than stating what they actually want and letting the offer be built around that. A written plan helps here, but not the kind that lists vague ambitions such as becoming a better leader. Something specific works harder: leading the client relationship on one particular account for the next quarter, or taking ownership of a process that has been drifting without a clear owner. A specific ask is something a manager can actually say yes to, kept to one page, dated, reviewed every few months. The point of writing it down is not the document itself. It is the discipline of naming what you want clearly enough that somebody else could act on it.
Vagueness costs more than people realise. A general statement such as wanting more responsibility gives a manager nothing to respond to except their own assumption of what that might mean, and that assumption is usually shaped by whatever the organisation happens to need filled at the time. A specific ask removes that guesswork. It tells the manager exactly what would count as a yes, and it means the person making the request has done the harder work themselves, working out what they actually want, rather than leaving that work for somebody else to do on their behalf.
5. Ask for the conversation directly
Working with leaders across different sectors, I often see the same avoidable gap: people wait for an annual review to raise what they want next, and by the time it arrives, the moment for that particular opportunity has already passed to someone else. A twenty minute conversation booked specifically to talk about direction, not delivery, does more work than any appraisal form. Come with a proposal rather than a general sense of feeling overlooked. If your organisation has no structure for these conversations, that is not a reason to wait for one to appear. It is a reason to request the conversation yourself, on your own terms, before the next round of opportunities gets handed out without you in the room. A Team & Leadership Workshop is one way to build this kind of conversation into how a team already operates, rather than leaving it to chance.
Booking it yourself feels more exposed than waiting to be asked, and that discomfort is usually what stops people from doing it. It can help to separate the conversation from any single outcome. The purpose is not to walk out with a guaranteed yes. It is to put your direction on record with the person who makes these decisions, so the next opportunity that fits gets considered with you in mind rather than decided in a room you were never part of.
6. Look for readiness where the organisation isn't already looking
An organisation can underestimate someone because it only sees the version of them its own environment has allowed to develop. Someone may be building judgement, confidence and the ability to carry real responsibility through voluntary work, caring responsibilities, a side business, or something entirely outside their job description. If career development only measures what has already been shown in the existing role, an organisation can miss what has been growing elsewhere.
I did not learn to stop running from bigger responsibility inside a job. I learned it by starting a business, where nobody was going to hand me the next stage of my own development because I hadn't asked for it clearly enough. Running something myself, making the decisions, and living with the consequences taught me I had more in me than I had been given room to use at work. That knowledge did not stay contained to the business. It started to filter into how I showed up in my part-time role too, and it changed something basic about how I handled the moments that used to make me want to disappear.
I still feel a flicker of panic when something large and uncertain lands in front of me. What changed is what happens next. I no longer run from it. I sit with it, usually for about a day, and ask myself plainly what actually needs to happen here. More often than not, once I have worked through that, the answer is that this is good for my career and worth doing, and the panic loosens its grip once I have made the decision rather than avoided it. That sequence- panic, process, decide- is not dramatic, and it is not something an appraisal form would ever capture, but it is closer to how real readiness gets built than most official programmes assume.
7. Separate readiness from willingness
These get treated as the same thing, and they are not. Someone can be entirely equipped to take on something bigger and simply not want it, and organisations routinely misread "I don't want that role" as "I'm not confident enough yet." Those are two completely different development problems, and solving the wrong one wastes everybody's time. You need to ask the first person what they actually want. The second person needs support, not a different offer dressed up as encouragement. Confusing the two is exactly how a well-intentioned development conversation ends up going nowhere.
The mix-up usually comes from a good instinct taken too far. Managers are told to encourage people and push past self-doubt, so a firm no gets treated as something to work around rather than something to believe. But someone who has genuinely thought it through and decided a role is not for them is not the same as someone hesitating out of nerves, and repeating the offer to the first person only reads as not having listened the first time. The way to tell the difference is simple enough: ask what is behind the no. An answer about fit, timing or interest is a decision worth respecting. An answer that circles around not feeling ready is a different conversation entirely, and worth having properly rather than assuming.
8. Stop treating promotion as the default evidence of growth
If promotion is the only thing counted as progress, most development conversations will keep missing what people actually want. Growth can mean greater autonomy, deeper expertise in an existing specialism, a different kind of work altogether, broader influence without a change in title, leading a project without managing people, or a more complex set of decisions inside the same role. None of these show up on an org chart the way a promotion does, which is exactly why they get overlooked so often, despite frequently being what someone wanted all along.
Part of the problem is how organisations measure their own success at developing people. A promotion is easy to count and easy to report upward, so it becomes the metric even when it is not the outcome that matters most to the individual. Someone who gains real autonomy over how they work, or who deepens a specialism until they are the person others go to, has developed just as genuinely as someone who moved up a grade, but that kind of progress rarely appears on the same dashboard. Widening what counts as growth is not lowering the bar. It is measuring something closer to what people actually experience as moving forward.
9. Match the offer to how someone actually creates value
A question underneath all of this rarely gets asked directly: what kind of greater responsibility fits how this person creates value in the first place? The technically strong specialist does not automatically need people management as their next step. Someone whose real contribution is analysis and judgement may want a deeper expert path rather than a broader one. Someone energised by connecting people and coordinating across a business may genuinely want the wider responsibility that others would turn down.
Creating value is rarely just about doing good work quietly and trusting it to speak for itself. It depends on being seen doing it, not performatively, but visibly enough that the right people have a clear picture of what someone actually contributes. It also depends on a track record others can point to, evidence built up over time that makes trust an easy decision rather than a leap of faith. Someone can be doing genuinely strong work and still be overlooked for the next opportunity, simply because too few people were in a position to notice it or vouch for it when the decision was being made.
The better equation is what the person wants, where they naturally create the most value, and what the organisation actually needs, and career development sits in the overlap between the three, not in any one of them alone.
10. Know when structured support helps
Structured support becomes useful when the person and their manager keep circling the same assumptions without getting anywhere new. An impartial third party can test what someone says they want against the evidence already sitting in their experience, their strengths, and how they actually behave under pressure or opportunity.
A Strengthscope assessment with 360 feedback is one way of putting that evidence on the table directly, showing where someone's own sense of their strengths matches, or does not match, how others actually experience them. That outside view is difficult to replicate from inside the relationship, particularly once a manager and their report have settled into a familiar, slightly stuck version of the same conversation.
Review the fit, not just the plan
A plan without a review date is a wish, and most reviews only check whether the actions got done. The more useful question is whether what is being offered still matches what is actually wanted, because both sides of that move over time. Two or three honest check-ins a year, each asking what has changed and whether the current direction still fits, will teach a person more about where they are heading than any single annual conversation manages to.
What good career development actually looks like
Good career development does not begin with the opportunity an organisation happens to have available. It begins with understanding what the person wants to develop, where their strengths and readiness already sit, and where that overlaps with what the organisation genuinely needs.
Sometimes that produces a promotion. Sometimes it produces more autonomy, a different project, deeper expertise, or a direction the org chart was not built to accommodate. Occasionally, an honest conversation reveals that the person's real next step sits somewhere else entirely, and that is not a failed conversation. It is the only kind worth having. The important part, every time, is that the development was chosen with the person, rather than done to them.
If you want to build career conversations across your team that create real ownership instead of quiet resistance, that is exactly what our Team & Leadership Workshop is built around.
By Paula Donnan
Strength at Work | Better judgement. Stronger leadership. Higher performance.
If this is affecting you, book in for a free 30-minute initial briefing to discuss the way forward.
Comments