Progression need not turn every specialist into a manager

An organisation can say that it values specialist work while offering only one visible route to higher recognition: become a manager. An experienced colleague then faces a choice that may have little to do with the contribution they make best. They can remain in the existing grade or compete for responsibility over other people. The business may lose depth in an important technical role and gain a reluctant manager, even though neither outcome was the purpose of the career discussion. I wanted to examine the structure before treating that choice as inevitable.

At Velmori, twenty-two experienced technical colleagues entered a review for a specialist progression route. Nine received specialist-grade promotions, eight continued development and five chose their existing role. The promotions added ₹28 lakh to annual pay expense. Technical leaders assessed professional readiness; HR worked on role design, reward and the explanation of the process. The result was a set of career decisions within a defined group. It did not establish better diagnostic outcomes or give HR authority to decide a person's technical competence independently.

## The structure can redirect the contribution

The first question was what advanced specialist work the laboratories actually needed. A title introduced simply to satisfy a promotion expectation would not be enough. The organisation had to describe responsibilities that differed meaningfully from the existing role and explain how the contribution would be used. Otherwise the new grade could become a payment label with no clearer account of the work. I wanted technical leadership to lead that discussion, because HR could help construct a career path without being qualified to invent the professional substance behind it.

Management work also deserved a proper description. Leading people is a responsibility in its own right, not merely a reward for being the most experienced practitioner. A specialist who prefers technical depth may be making a sound career choice by declining a management role. The company should not interpret that preference as a lack of ambition without examining whether its own structure has made ambition too narrow. Different forms of contribution can matter to the business, and their responsibilities should be clear enough that employees do not have to guess which one the organisation truly respects.

The review involved twenty-two colleagues because we had defined a particular population for this stage. It was not a promise that every experienced employee would receive a new grade, and it did not imply that people outside the group had no future path. The scope needed an explanation. Participants also needed to understand what the review could decide and who would make the relevant assessments. Unclear expectations can turn a development discussion into an assumed promotion commitment before the company has examined whether the responsibilities and readiness are present.

Nine colleagues received specialist-grade promotions. Eight continued development, and five chose to remain in their current role. Those outcomes should not be collapsed into a simple passed-or-failed division. Continuing development did not mean that a person was failing in the job they already held. Choosing an existing role could be a considered preference rather than an unsuccessful attempt to advance. I wanted the account to respect what each category actually meant. A career structure becomes less useful if every decision is translated into a status judgement the process was not designed to make.

The ₹28 lakh annual pay cost was part of the organisational choice. It needed to appear in the continuing plan, not only in the launch budget. The business was deciding to recognise a form of work it considered valuable, with responsibilities that should endure beyond the announcement. I did not attach an invented savings figure to make the proposal seem self-funding. If later evidence showed an operational effect, it would need to be examined on its own terms. The immediate decision had a role-design rationale and a known compensation consequence.

## A grade is not a professional assessment

Technical leaders retained authority for professional readiness. HR could make the review process understandable, help distinguish roles and examine the reward structure, but it could not establish competence through a grade designation. That boundary mattered in a diagnostics business, where a career announcement might otherwise be read as a broader assurance about professional work. We did not claim that the promotions improved diagnostic outcomes. The case concerned employment progression and the responsibilities attached to it, with technical assessment conducted by the appropriate people.

The boundary also protected the quality of the HR contribution. If we pretend to decide matters outside our competence, we make it harder to do the work we should own well. Employees need clear descriptions, understandable decisions and a credible route to ask about the process. Managers need to know the reward implications and how the specialist role relates to other responsibilities. Finance needs the recurring cost. Those are substantial tasks. They do not become more valuable because HR makes a professional claim it cannot support.

A career path should be examined after the launch. Does the specialist have the work described? Do managers understand how to use the contribution? Is there a development conversation for someone who is not ready for the next grade? These questions concern whether the organisational decision has become a workable arrangement. They should not be answered merely by counting promotions. A title can be issued quickly; responsibilities, expectations and working relationships need attention over time. The company should be prepared to discover that part of the design still needs revision.

Boards can ask whether the structure fits the business's needs and whether management has described its cost and professional boundaries clearly. They can examine how the organisation recognises expertise without assuming that every valuable employee should become a people manager. They should leave individual competence assessments with qualified leadership and avoid turning a remuneration discussion into a direct instruction about a particular colleague's technical standing. The oversight task is to understand the design and its consequences, including the risk of making career choices narrower than the work requires.

I would describe our decision as creating a specialist route for work we could define, reviewing twenty-two colleagues and reaching three different sets of outcomes. Nine promotions carried a recurring cost, eight development paths remained active and five colleagues chose their current role. The account is useful because it preserves those distinctions. Progression should help a business retain and develop the contribution it needs. It should not require every capable specialist to leave that contribution behind simply because the organisation has only taught itself to recognise a manager's title.