From answering employee questions to changing the arrangement

Mandate

Connect employment arrangements with the actual resources and responsibilities of skilled field work.

Outcomes

• Introduced company-funded travel routes with a ₹1.2 crore revolving provision and an 18-trip initial pilot.
• Funded ₹46 lakh annual cover around defined modified-duty and pending-return arrangements.
• Supported a customer nonrenewal involving ₹1.8 crore annual revenue after revised worker-support terms were declined.
• Scheduled 96 weekly mentoring hours across eight mentors with ₹54 lakh annual cover.

Decisions in context

The CHRO remit brings the employment consequences of field-service decisions into discussion with the CEO and operating leaders. I lead twenty-one HR colleagues through three leads and remain a nonmember employee of the cooperative. The function expense is distinct from the company's overall employee cost. My recent work concerns how journeys are funded, how returning colleagues receive usable work arrangements, what support a technician can expect in a difficult customer interaction and how mentoring time enters the service plan. Mina and other operating owners retain their technical and assignment responsibilities. I want the enterprise to understand what it asks people to carry before the arrangement becomes routine. The role has strengthened my ability to connect an individual employment consequence with a commercial or operating choice, without treating a funded policy as proof that every colleague's experience has been resolved.

Reason for the move

Current people-leadership responsibility; exploring an initial company-board contribution.

Mandate

Develop employment and career arrangements for a growing skilled-service workforce.

Outcomes

• Led fifteen colleagues within ₹2.3 crore functional expense.
• Reopened the twelve-person supervisory progression exercise after identifying a mismatch in career choices.
• Supported six senior-technical returns, four continuing supervisors and two pending individual reviews.
• Funded role redesign at ₹34 lakh and a ₹42 lakh annual senior-craft pay envelope.

Decisions in context

This role made me responsible for the people function and its contribution to workforce planning. The 2018 progression decision became an important correction in my record. I had supported supervision as the main senior route for experienced technicians, then learned that several colleagues wanted a deeper craft contribution instead. Reopening the arrangements required individual discussion and operating input, not a simple reversal of every appointment. The business accepted redesign cost and a recurring pay envelope for credible senior technical work. I learned to distinguish the organisation's need for supervisors from a person's chosen direction, and to avoid using a promotion total as the whole account of career development. The experience shaped my later CHRO work because it showed how an apparently positive programme can conceal a cost or sacrifice that the company has not asked people about clearly enough.

Reason for the move

Appointed CHRO with a broader enterprise people remit.

Mandate

Make people support usable for colleagues working away from the central office.

Outcomes

• Managed nine HR colleagues within ₹1.1 crore annual expense.
• Connected field managers with the responsible people and professional-advice routes.
• Kept member ownership distinct from the employment arrangements affecting nonmember colleagues.

Decisions in context

Joining the cooperative brought me closer to the practical conditions of field work. A person could be carrying out an assignment far from the office while a policy assumed easy access to a manager or an administrative desk. I worked with regional operating colleagues and reported to the head of people. The ownership structure also required care: technician membership was important, but it did not describe every employee's relationship with the enterprise. I wanted people processes to work for nonmembers as well as those with an ownership voice. My responsibility was regional HR support within the stated team and expense scope, not technical certification or control of the whole service operation. The experience helped me understand how an employment arrangement has to travel with the work, rather than remain clear only to the team that wrote it centrally.

Reason for the move

Promoted to lead the people function.

Mandate

Help managers understand the individual consequences of proposed employment arrangements.

Outcomes

• Led five colleagues within ₹38 lakh annual expense.
• Brought unresolved individual questions back to the manager able to decide them.
• Distinguished administrative completion from an agreed and understood employment arrangement.

Decisions in context

As a people partner I moved from preparing records to helping managers discuss the choices those records described. I led five colleagues and worked under the people-services director. The role required a clearer distinction between explaining an existing arrangement and deciding what it should become. I learned to preserve an employee's actual question when it moved between functions, especially when a standard category did not capture the practical concern. Relevant advisers and managers retained their own authority. My interest increasingly lay in distributed work, where a central assumption could have a large effect on a person carrying out an assignment elsewhere. That interest led to Qelmorsi. I wanted to understand the operating plan early enough to influence the employment arrangement, rather than receive the individual consequences only after the main business choice had already been made.

Reason for the move

Joined a field-service enterprise to work closer to operating decisions.

Mandate

Prepare accurate records and help employee questions reach the appropriate decision-maker.

Outcomes

• Joined after the May 1998 social-work degree.
• Supported records and conversations in a 48-person firm.
• Escalated questions beyond administrative authority rather than provide unsupported answers.

Decisions in context

I began in July 1998 with practical administrative work under a supervisor. I prepared records, organised conversations and helped colleagues find the person responsible for a question. The role did not authorise me to decide employment terms or provide specialist advice. It did show me how easily an unresolved concern could look completed once a form had moved to the next stage. I learned to ask whether the employee understood what had been agreed and whether someone actually owned the remaining decision. That habit became more useful as my responsibilities grew. The early role was modest in scale, but it established a distinction I still use: a process can be orderly for its administrators while failing to give the person affected a usable answer. I wanted later people work to retain that person's practical question rather than lose it inside a successful-looking record.

Reason for the move

Promoted into people-partner work with a small team.