Five experienced credit professionals made me reconsider a grade structure I had accepted for years. They were eligible for progression, but the next available grade was tied to supervising staff. The credit leader valued their judgement on difficult cases and their ability to help less experienced colleagues. Some wanted to manage people; others wanted to deepen the professional work. Our structure treated those different aspirations as a problem for the employee to solve, usually by accepting management responsibility as the price of advancement.
The arrangement was administratively clear. Grades could be compared using team size and reporting responsibility, and managers could explain the next step without a lengthy discussion of specialist value. I had supported that clarity. Yet it did not follow that the structure reflected every contribution the lender needed. It could move a capable professional away from the work where their judgement mattered most and into responsibilities they had not chosen or prepared for. The problem was not that management work lacked value. It was that we had made it the only recognised future.
Direct reports are an incomplete measure of contribution
People management is substantial work. It includes setting expectations, discussing performance, arranging cover, addressing concerns and helping others develop. A specialist who does not want that remit is not rejecting responsibility altogether. They may be prepared to carry different responsibilities whose value is harder to express through a headcount. In credit work, that could include examining unusually complex cases, improving professional review and mentoring colleagues without becoming their line manager. The company needs to define the difference rather than rely on the prestige of the word specialist.
Finance challenged the proposal for a separate route. Would it simply create a more expensive title for work people were already doing? That was a fair question. An organisation should not add a band merely because an experienced employee would like another increment. We worked with the credit leader to specify the complexity, contribution and review expectations attached to two specialist bands. The discussion had to explain what the enterprise needed and how the role would be assessed. Without that work, a parallel ladder would have postponed the same disagreement behind more flattering language.
The evidence also had to avoid a false equivalence. I did not argue that one specialist was always worth a manager with a particular number of reports. The responsibilities were different, and their value depended on the operating model. A useful career architecture can recognise that difference while maintaining a coherent account of pay and scope. It should not require every important role to imitate the shape of another role before the company can explain why it exists. The comparison needs enough discipline to be credible without pretending that all contribution has one unit of measurement.
We eventually approved an annualised ₹28 lakh pay increase for the three colleagues who chose the new route after assessment. That amount belonged to enterprise employee expense, not the people function's own operating budget. It was a continuing cost associated with actual appointments, rather than a notional retention benefit. The company was paying for a defined contribution it wanted to sustain. I was careful not to claim that the expenditure had already paid for itself through fewer losses or prevented departures, because we did not have evidence supporting those conclusions.
Separate professional progression from delegated authority
In a lender, the distinction between career standing and decision authority needs particular care. A higher band does not automatically mean a larger lending approval limit. Credit policy, the individual's appointment and the relevant professional requirements determine the authority to make a decision. HR helps design the role and employment terms; it does not issue lending permission through a title. We explained that separation before people chose the specialist path so the new structure would not create expectations the operating model had not authorised.
The earlier review of relationship-officer roles made the same point from another direction. Seventy-eight job descriptions had combined customer development, application preparation and a limited delegated credit-decision responsibility. Credit leadership wanted clearer separation as the business changed. Some regional managers preferred the speed and familiarity of the combined role. Employees also had legitimate questions about losing a part of the responsibility they had joined to carry. A role redesign needed to address those expectations rather than call the change an inconsequential update to wording.
The company funded eight additional credit-analyst positions at ₹92 lakh annualised employee cost. Relationship officers retained their customer and application work, while designated credit roles carried the revised decisions. The change introduced staffing cost and another handover. It did not establish that every answer would become faster or that credit losses would fall. My contribution was to make the employment design support the authority model chosen by the qualified owners. That included honest conversations about careers, not a promise that every affected colleague would experience the change as advancement.
These two decisions should not be collapsed into a claim that specialisation is always preferable. Some organisations and roles may appropriately combine responsibilities, subject to their circumstances and requirements. Some people may prefer the broader management route. The lesson I take is that a career framework should not determine professional authority by accident, and an authority decision should not ignore the people whose role has changed. The two discussions need to meet, with their different owners and evidence visible. Neither can be completed solely inside the HR function.
An additional route is not a universal preference
Of the five eligible professionals, three chose the specialist route and two remained on their existing path. The two were not failed conversions or evidence that the programme had been poorly explained. They had their own preferences and circumstances. I wanted the choice to remain real, which meant accepting that an option we had spent time designing would not be the right next step for everyone. A company weakens its own language of choice if it treats declining the new route as a lack of ambition.
The appointments also did not prove retention. People can accept a role and later leave for many reasons. A management account should state what happened: three assessed appointments, two different choices and a continuing pay commitment. It can then examine how the roles work over time. If the enterprise later finds that expectations are unclear or that mentoring is not properly supported, the answer is to review the design rather than preserve a success story built around the launch count. Career architecture is an operating arrangement, not an event whose value is settled on announcement day.
I would bring that perspective to a future board discussion about capability and succession. Directors can ask whether the organisation offers credible paths for the contributions it needs, whether the responsibilities are funded and whether management understands the consequences of its preferred structure. They do not need to allocate individual grades. The useful oversight question is whether the company can explain the careers it has made possible and the careers it has unintentionally closed off. A specialist should be able to see a future in the work the enterprise values, without collecting a reporting team simply to make that future legible.