A strong performer is called into a promotion discussion. Their targets are on track, their technical knowledge is solid and clients trust their answers. Yet the role goes to someone else.
The feedback is frustratingly vague: "You need to demonstrate more leadership."
This gap is common because the evidence that helps someone get hired is not always the evidence used to promote them. A hiring decision may focus on whether a person can do the work. A promotion decision asks a broader question: what happens around this person when the work becomes uncertain, shared or difficult?
That is where behaviour becomes visible.
Skills get work done. Behaviour shapes how the work gets done
Skill answers questions such as: Can you analyse the data, manage the account, write the code or run the operation?
Behaviour answers different questions. Do you raise a risk before it becomes a crisis? Can you disagree without making the room unsafe? Do you take responsibility for an outcome while still giving others credit? When priorities change, do people get clarity from you or more confusion?
These are not personality preferences. They are observable actions in a work context. A quiet employee can show strong leadership. An outgoing employee can avoid accountability. Confidence, fluency and visibility are not reliable substitutes for behaviour.
The higher the role, the more work gets done through other people. That changes the promotion test. Individual expertise still matters, but it must sit alongside judgement, trust and the ability to help a team perform.
Five behaviours that often matter at the next level
Every role needs its own criteria, but these five areas give managers a useful starting point.
Ownership before escalation
Ownership does not mean solving everything alone. It means defining the problem, trying the next sensible step and escalating with context. A promotable employee can say what happened, what they have checked, what decision is needed and what could happen next.
Judgement under uncertainty
Senior work rarely arrives as a complete instruction. Look at how the person separates urgent from important, asks for missing information and makes a reversible decision when waiting would be more costly.
Response to feedback
The question is not whether someone enjoys criticism. Few people do. The useful evidence is what they do after hearing it. Can they clarify the concern, test a different approach and return with a better result?
Trust across the team
Trust shows up in small moments: sharing information early, keeping commitments, naming a mistake and handling confidential matters carefully. It also shows up in whether colleagues can challenge the person without expecting retaliation.
Working through others
A future manager should not need to be the smartest voice in every discussion. Notice whether they explain context, delegate a real outcome, make room for another person's idea and help colleagues learn without taking the work back at the first wobble.
Turn vague promotion feedback into evidence
"Show more leadership" is too broad to act on. Replace it with a short evidence plan.
Start with the next role, not the employee's current reputation. Choose three behaviours that the role genuinely requires. For each one, describe what good behaviour would look like in a normal week and during pressure.
For example, if the role requires cross-functional ownership, evidence could include:
- confirming who owns each decision before a project begins
- raising a dependency while there is still time to respond
- resolving a disagreement without bypassing the people involved
- providing a concise update that helps stakeholders act
Then give the employee a real opportunity to demonstrate those behaviours. A stretch assignment, meeting to lead or difficult handover is more informative than asking them to "be more strategic" for three months.
Review the evidence on an agreed date. What did the person do? What changed because of it? What still needs practice? This makes the promotion conversation more useful even when the answer is not yet yes.
Where behavioural insight and graphology can help
Managers often see only the behaviour that reaches them. An employee may be confident with clients but hesitant in conflict, or highly dependable until several priorities compete. A structured behavioural assessment can suggest themes worth exploring before a development conversation.
Handwriting analysis, when used in a workplace setting, should be treated as a source of prompts rather than a promotion verdict. A report might encourage questions about decision-making, stress response, feedback or collaboration. The manager should then test those themes against work examples and invite the employee's view.
A useful conversation sounds like this: "This theme suggests you may prefer time to process a difficult decision. Does that fit your experience? When has that helped you, and when has it slowed the team down?"
The employee can agree, disagree or add context. Performance evidence, role requirements and a fair promotion process remain essential. No assessment should become a shortcut around them.
A 30-day promotion-readiness experiment
Choose one behaviour, one work situation and one review date.
Suppose an employee needs to strengthen delegation. For the next month, ask them to lead a small project without becoming the default owner of every task. They should define the outcome, assign decision rights, agree check-in points and let colleagues solve problems within those boundaries.
At the end of the month, review more than the final result. Did the team understand the goal? Were decisions made at the right level? Did the employee intervene because risk required it, or because another person's method felt unfamiliar? Ask the team member receiving the delegation what helped and what created friction.
One month will not settle every promotion decision. It will produce better evidence than waiting for an undefined feeling of readiness.
Make promotion criteria visible before the vacancy opens
Employees should not discover the behavioural requirements of a senior role only after being rejected for it. Publish the criteria, use the same language in development conversations and give people access to assignments where they can practise.
Managers also need to check their own bias. Visibility can be mistaken for impact. Familiarity can be mistaken for trust. A person who works like the current leader may feel "ready" even when a different style would serve the team better.
The fairest promotion decisions combine role-specific behaviour, repeated work evidence and a conversation the employee can understand. Skills may have opened the first door. The next door depends on how those skills affect the people and decisions around them.
Conclusion
If a capable employee is not ready for promotion, name the behaviour that the next role requires, show what evidence would demonstrate it and create a real chance to practise. That turns a vague judgement into a development plan.