When a Job Becomes an Identity: Helping Capable People Build Room to Grow
A capable employee is offered a different assignment. The work uses many of the same strengths, the manager sees it as an opportunity, and the organization needs someone dependable. Yet the employee hesitates. They ask repeatedly whether their title will change, who will report to them, and whether the move means they have fallen behind.
It is tempting to call this resistance to change. That label may be convenient, but it can obscure the question the person is actually asking: if I am no longer recognized for this role, what will make me valuable here?
Consider that situation as an illustration, not a diagnosis. An employee may have perfectly reasonable concerns about pay, workload, fairness or an unclear brief. A good manager does not assume an identity problem before addressing those facts. But once the practical questions are understood, there is another conversation worth having: how can someone remain committed to their work without making one position the entire definition of their worth?
Start by Separating the Problems
Security, competence and belonging are different concerns. A change can threaten all three, but they need different responses. Someone worried about income needs clear information about compensation and contractual arrangements. Someone worried about capability needs an honest view of the work and the support available. Someone worried about losing standing needs to understand how their contribution will be recognised.
A motivational speech cannot replace a clear answer about salary. Training will not settle an unresolved reporting relationship. A new title will not help when the employee has been given responsibility without authority. Before discussing confidence or purpose, make the assignment understandable.
Ask three questions: What would change in practice? What is not changing? What has not yet been decided? Write down the answers. If an answer is unknown, identify who owns the decision and when an update is expected. Uncertainty should not be disguised as reassurance. People can work with an acknowledged gap more honestly than with a promise their manager cannot keep.
Broaden the Language of Contribution
A title is a useful description of a position, but it is a poor inventory of everything someone can do. Managers can help employees describe their contribution in terms that survive a change of department, system or reporting line.
Instead of stopping at “I am the program manager,” ask what the person actually makes possible. Perhaps they turn competing stakeholder requests into an agreed scope. Perhaps they identify dependencies before they disrupt delivery. Perhaps they explain technical issues so decision-makers can act. These are not empty positive labels; they are activities that can be illustrated with evidence.
Use a recent assignment to build a short contribution record. What was the situation? What did the employee do? What changed as a result? What part of that work could be useful somewhere else? Keep the account proportionate and acknowledge the contributions of others. The exercise is not a request to turn every task into a heroic achievement.
This can also expose gaps. Someone may have considerable coordination experience but little direct exposure to budgeting. Another may be technically strong but need support in difficult stakeholder discussions. A useful record makes those development needs visible without reducing the person to them.
Create Experiments, not Dramatic Reinventions
A conversation about career growth does not have to end with a promotion, a transfer or a resignation. It can end with a bounded experiment. The point is to gather evidence about a possible direction before anyone makes an irreversible decision.
For example, a delivery coordinator interested in business analysis could facilitate one requirements session with an experienced colleague. A technical specialist interested in management could lead a small planning exercise without immediately acquiring a team. A manager who wants to return to specialist work could contribute to a defined technical review while keeping their current responsibilities clear.
Every experiment needs a purpose, a time boundary, support and a review point. What is being tested? Who will coach the employee? What existing work will be reduced or reassigned? What evidence would suggest that the new direction is worth pursuing?
That question about existing work matters. Development should not quietly become an additional job performed at night. If an organization asks someone to test a new responsibility while maintaining an already full workload, it should acknowledge the trade-off and make room for it. Otherwise, the experiment may measure endurance rather than suitability.
Be explicit about what the experiment does not promise. It may offer useful experience without guaranteeing a vacancy or pay increase. Saying that clearly at the start is more respectful than allowing an employee to build a career plan around an implication no one intended to honor.
Make the Conversation Safe Enough to be Useful
An employee is unlikely to discuss uncertainty candidly if every hesitation is treated as a lack of ambition. Equally, the manager cannot promise confidentiality without limits or suggest that business requirements no longer apply. The task is to create a realistic conversation, not a private world outside organizational responsibilities.
A useful opening is: “I would like to understand what you want to keep doing, what you want to learn, and what you do not want to lose in this change.” That is different from asking the employee to declare a complete five-year plan. It leaves room for uncertainty and for priorities that may have changed.
Do not demand personal disclosure. An employee can explain a need for predictable hours without giving a detailed family history. They can say they are not ready for travel without defending every reason. Focus on the working arrangement, what can reasonably be accommodated, and the decisions each party needs to make.
The conversation should produce a record both people recognize: the employee's priorities, the organization's needs, the next action and the date for review. Avoid writing interpretations such as “afraid of change” when the person actually raised a specific concern about workload or location. Record the concern in terms that allow someone to act on it.
Recognize Contribution Without Creating Dependence
Praise can be helpful and still be imprecise. “We could not function without you” may sound generous, but it is an awkward message to give someone who needs to delegate, take leave or develop beyond their current assignment. It can make growth feel like disloyalty.
Be more specific. Name the decision they improved, the process they clarified or the colleague they helped become more capable. Recognize effective handover and documentation, not only the person who repeatedly rescues a failing process. When knowledge is shared, the employee has more room to move and the team is less dependent on one individual.
The same principle applies to feedback. Critique the work without turning the mistake into a description of the person. “This report did not make the decision clear” gives someone something to improve. A sweeping judgment about their leadership or intelligence is much harder to use. Standards can remain demanding without making every review a verdict on identity.
A Practical Ninety-Day Approach
In the first month, clarify the present role and build the contribution record. Discuss the employee's priorities, practical constraints and one area they want to explore. Select a modest experiment and agree what will be deprioritized to make it possible. Document who can answer questions about pay, role scope and progression.
In the second month, run the experiment with regular, brief feedback. Look at the work itself. What did the employee find engaging? Where did they need help? What did colleagues or stakeholders actually observe? Separate enthusiasm from evidence, and distinguish an unfamiliar task from a task that is genuinely a poor fit.
In the third month, review the findings together. The answer may be to continue, adjust the experiment, seek a different assignment or improve the existing role. None of those outcomes is automatically a failure. A useful experiment can show that a proposed path is less attractive than expected, avoiding a larger commitment that would have been difficult to reverse.
Measure the process with a few practical questions. Were role expectations clearer? Did the agreed development activity happen within a manageable workload? Is there evidence of a new capability or a clearer preference? Was the promised review held? Do not claim success solely because the employee stayed, agreed enthusiastically or stopped raising concerns.
When the Organization Cannot Offer the Next Step
Sometimes the desired role does not exist. Sometimes budget, location or business priorities make a move impossible. Honest limits are part of good management. Explain the constraint without pretending it is a judgment about the employee's potential.
Offer only what can actually be delivered: useful feedback, a realistic development assignment, access to an appropriate internal contact, or a clear account of how future opportunities will be considered. Do not keep someone waiting indefinitely with vague suggestions that an opening is almost certain.
There is a tension here. Managers are accountable for delivery, and losing a strong employee can create a real operational problem. But treating that person as permanently indispensable is not a development strategy. Build a transition plan, improve the documentation and prepare others to take responsibility. A team becomes more durable when capability can move without leaving a vacuum.
The Aim Is Not Detachment
Healthy professional identity does not require people to stop caring about their work. Pride, ambition and commitment can remain. The aim is to give those qualities a wider foundation than one title, one manager's approval or one organization's current structure.
For a manager, the most useful contribution may be surprisingly ordinary: clearer facts, more precise feedback, a manageable experiment and a promise kept at the next review. Together, those actions give an employee a way to explore growth without being asked to abandon responsibility.
The question is not simply whether someone is ready to change. It is whether the working conditions, information and support make thoughtful change possible. That is a question managers can do something about.
Seun Mafaa is consultant, author and speaker. He advises leaders on artificial intelligence (AI), responsible adoption, governance and the workforce changes that follow new technology. His books and conversations ask the same question from another angle: what happens to people when the world around them changes?
