Progression can change the wrong part of the job
I have met technical colleagues who accepted a management role because it was the only credible route to a higher grade. Some became effective managers and enjoyed the change. Others spent less time on the work they did best while struggling with responsibilities they had never wanted. The organisation then faced two losses: a specialist contribution had diminished, and a team had acquired a reluctant supervisor. Calling the move a promotion did not make it a good decision for either party.
A specialist career route can address that problem, but it can also become an attractive label attached to an unchanged hierarchy. I am interested in the actual work that grows as technical standing increases. Does the person handle more complex problems, contribute across sites or help develop other practitioners? What decisions can they influence, and where does their responsibility end? Unless these questions have answers, a senior specialist title may offer temporary reassurance while leaving the employee and manager uncertain about what has changed.
Evidence must belong to the discipline
The people function has an important role, but it should not claim knowledge it does not possess. I can help design the process, examine pay relationships and make the criteria understandable. I cannot independently judge the technical quality of an engineering contribution. That responsibility belongs to qualified leaders and assessors in the discipline. The partnership works when each side is prepared to do its own work, including explaining why an apparently impressive contribution does or does not meet the proposed level.
In 2024, our fictional business opened a specialist track to ninety-six eligible technical employees. Eligibility meant that someone could apply; it did not mean that an appointment was promised. Fourteen people received an initial appointment, and nine applications required further evidence. Some eligible employees did not apply. These distinctions mattered because an announcement could easily have created an expectation of broad automatic progression. We chose a more demanding launch, with individual explanations and a defined opportunity for further review.
The reward decision was equally important. The first appointments added RMB 1.1 million to annual pay costs. Finance asked whether the track could be funded by reducing management positions. That might become a relevant question in an organisation review, but it was not a sufficient basis for the specialist framework. We first needed to understand the technical contribution and the management work still required. If a new career route is justified only by an assumed reduction elsewhere, its purpose can be distorted before the first appointment is made.
Existing managers had reasonable concerns. A parallel route can make comparisons less simple, particularly where a specialist earns as much as someone with a team. I do not believe reporting-line size should be the sole measure of contribution. I also do not think managerial responsibility becomes less demanding because another route exists. We had to explain the different forms of accountability and review cases where the scope of a management role had itself changed. A framework is more credible when it can withstand those questions without dismissing them as resistance.
One applicant challenged the explanation of the additional evidence requested. The assessment outcome did not change, but the panel acknowledged that its written explanation was too abstract. That was a useful correction. A person cannot reasonably prepare for a later review if the feedback consists of broad statements about needing greater impact. The response should identify the kind of contribution that remains unproven and the opportunities available to demonstrate it. It should not prescribe a theatrical project undertaken solely to satisfy a promotion process.
Opportunity is part of the fairness problem. Employees at a large or visible site may have easier access to complex assignments than colleagues elsewhere. A process can use consistent criteria and still produce unequal chances to meet them. I ask operations how development opportunities are distributed and whether a promising specialist can gain exposure without accepting an impractical relocation. There may be limits to what the business can offer, but those limits should be discussed before an unsuccessful applicant is told that the missing experience is entirely an individual responsibility.
The framework also needs a view of teaching. A highly capable practitioner may contribute through helping others understand difficult work, but mentoring should not become an unlimited unpaid obligation attached to seniority. The organisation must allocate time and recognise the activity. Nor should every specialist be assumed to have the same aptitude for instruction. We need to distinguish technical depth, practical teaching and line management rather than collapse all three into an idealised senior employee who can do everything without support.
The first appointment is not the final test
I consider the first appointments a beginning, not a completed transformation. After a year, we should ask whether the responsibilities described at appointment have actually been available. Has the specialist been used only as extra capacity for routine work? Has their cross-site contribution created confusion with local managers? Has a title become a substitute for resolving a pay inconsistency? These are design questions that deserve revision. The framework should not be protected from evidence merely because considerable effort went into launching it.
For an executive team, the wider issue is whether the organisation can recognise more than one way of becoming valuable. A management-only hierarchy may be simple to administer, but simplicity can be expensive when it pushes people away from their strongest contribution. A specialist route adds complexity and cost. I would accept both when the work justifies them, while rejecting the idea that every experienced employee needs a new senior title. Progression must remain connected to a contribution the business can describe and support.
I want a technical colleague to be able to discuss a future without first apologising for not wanting a large team. That conversation should include ambition, reward, learning and the responsibilities that come with greater standing. It should also permit an honest decision that the current role is the right one for now. A useful career system gives people meaningful alternatives and makes the consequences understandable. It does not replace one compulsory staircase with another set of titles that everyone is expected to climb.