A promotion is usually presented as an uncomplicated sign of progress. The organisation has recognised someone, the employee has gained a title and a vacancy has been filled. For a skilled technician, the change may be more ambiguous. A supervisory role can replace the work the person values with allocation, performance conversations and responsibility for other people's decisions. Those duties matter, but they are not simply a more senior version of every technical task. If management is the only recognised route upward, the company may be asking a strong practitioner to change occupations in order to have a future.
I supported such a route in 2018. Twelve experienced technicians moved into supervisory posts because that was our main senior progression path. The list looked like evidence that we developed people internally. Later conversations showed that several colleagues wanted deeper technical practice rather than a permanent move into supervision. We reopened the arrangements. Six chose senior technical work, four continued supervising and two remained in individual review. Those results were not twelve identical success stories. They were a more accurate account of twelve people whose ambitions and circumstances did not fit a single definition of advancement.
A promotion can change the occupation
Technical strength may help a supervisor understand the work, but it does not establish that the person wants or is prepared for every part of the supervisory role. Giving feedback, allocating scarce time and addressing conduct involve different responsibilities from diagnosing a mechanical problem. The company should explain those responsibilities before the move, not rely on a title to make them desirable. A person can be ambitious about their craft while being thoughtful about whether managing others is the contribution they want to make.
Our operating sponsor worried that reopening the decisions would weaken supervisors' authority. Some members also believed that seniority ought to bring responsibility for others. I understood those concerns. A service enterprise needs capable supervisors, and a role cannot be abandoned casually whenever a difficult conversation arises. But the business also needed to examine the route it had designed. We had made one kind of responsibility the main way to recognise several kinds of contribution. The mismatch was not solely an employee's failure to adjust to a promotion.
I should have asked about the actual work earlier. What would the colleague do less of? What new decisions would they carry? What preparation and support would be available? What alternatives existed if the person wanted to deepen technical expertise? Those questions would not have supplied an automatic answer for every candidate. They would have made the choice more honest. A succession need should not quietly become a personal career prescription simply because the organisation has a supervisory vacancy to fill.
The craft route needs more than a reassuring title
We funded ₹34 lakh for role review and redesign and accepted a ₹42 lakh annual senior-craft pay envelope. The financial commitment mattered because an alternative route without funded work would have been difficult to take seriously. A new title alone might soften the conversation while leaving the same hierarchy intact: real advancement in management, and a polite label for everyone else. The technical path needed an intelligible contribution, appropriate evidence and development expectations that operating leaders could support.
That does not mean every experienced technician automatically receives a senior grade. Experience is relevant, but the enterprise still needs to define the responsibility and assess the evidence for it. Technical specialists retain authority over standards and the work that can be assigned. HR can help make the career structure fair and usable without pretending to judge every technical capability. The distinction protects the route from becoming either an entitlement based only on tenure or a vague consolation offered when someone declines a management job.
Pay is part of credibility, but not the whole of it. A person also needs to know whether senior technical work has access to development, whether its contribution is visible in planning and whether the role will survive the next reorganisation. The company must understand the work it is recognising. If the technical route exists only on a career chart while all important decisions and learning opportunities move elsewhere, employees will reasonably read the chart as a promise the operating model has not funded.
The supervisory route deserves the same seriousness. Creating a craft alternative should not imply that managing people is less demanding or merely an administrative burden. It can help the company select and prepare supervisors who understand the work they are choosing. A clearer distinction between paths makes both more honest. The enterprise can discuss what it needs from a supervisor without relying on the assumption that every accomplished technician should naturally want that role as the next rung of the same ladder.
Reconsidering a move should not erase the person's contribution
The six technical returns in our review required individual discussion and the appropriate employment process. We did not present them as automatic demotions or proof that those colleagues lacked leadership. Nor did the four continuing supervisors establish that the earlier design had been adequate for everyone. Two cases remained unresolved at the reporting point. Keeping that unfinished position visible mattered. A people decision should not be forced into a completed-programme narrative merely because the organisation wants a clean account of its redesign.
There was discomfort in revisiting announced appointments. I had supported the original structure and needed to acknowledge that before asking employees to explain why it did not fit. Otherwise, the review could have sounded like a test of whether they were grateful enough for a promotion. The company accepted a more complex structure and recurring cost. The benefit we could substantiate was a more credible choice of contribution, not a universal improvement in retention or satisfaction inferred from the fact that a new route existed.
In a future exercise I would make the difference between technical depth and people management explicit before the selection process begins. I would involve operating specialists and prospective candidates in describing the work, then ensure the chosen route has real support. A promotion count can remain useful, but it should not substitute for understanding what people have moved into and what the business is asking them to leave behind. Skilled employees should be able to grow in responsibility without having to distance themselves from the craft that makes their contribution valuable. The company's task is to build that possibility into its roles and resources, not merely applaud it in a career conversation.