From recording the question to challenging the workforce account

Mandate

Make employment arrangements workable and their consequences intelligible across a regional operating-services workforce.

Outcomes

• Introduced a bounded advance arrangement for reviewed business travel.
• Connected supervisor selection to defined role requirements.
• Brought internal pay consequences into urgent-hiring approval.
• Separated relationship disclosure from a presumption of recruitment misconduct.

Decisions in context

The CHRO remit covers twenty-one colleagues through four leads and a ₹3.1 crore administration and development budget. Our team's pay sits within the separate ₹84 crore enterprise employee-cost account. I report to the CEO and do not hold a statutory seat. The company supports fourteen client-owned plants; it does not own their capacity or give me authority over process safety and technical work. My responsibility is to examine the employment proposition and the evidence behind the people recommendation. The travel, promotion, pay and local-recruitment cases show practical costs that a central policy can leave outside its account. I have no equity holding. A possible outside role would require a review of employment, relevant relationships and the provisional twenty-day allowance, rather than assuming that a current executive title makes me available or independent for another company's board.

Reason for the move

Current appointment; exploring a first outside contribution after preparation and capacity review.

Mandate

Develop the operating account of employment and the management processes used across sites.

Outcomes

• Accepted responsibility for endorsing a zero-concern management score.
• Removed the score from eleven managers' reviews after listening exposed its limits.
• Kept reported concerns, responses and unresolved cases distinct in the corrective account.

Decisions in context

The functional director appointment gave me fifteen colleagues and ₹2.2 crore of annual administration and development expenditure. It did not include a statutory directorship. I wanted site managers to receive a clear account of people responsibilities, and the zero-concern score appeared to offer a concise comparison. Nirmal's objection should have led me to test the process before supporting the measure. The later listening exercise showed why an absent entry could not establish early resolution. I owned the approval, supported removal of the score and retained the cost of the corrective work. The experience changed how I interpret a workforce report: I ask what had to happen for the count to exist and what incentives might keep an issue outside it. Moving into the CHRO role broadened that discipline to other practical conditions of employment without erasing the earlier error.

Reason for the move

Appointed CHRO as the company required a broader executive people remit.

Concurrent appointment

Director described the people-function role only; there was no statutory board appointment.

Mandate

Connect central employment arrangements with the practical circumstances of site work.

Outcomes

• Developed a recurring route for unresolved site-employment questions.
• Brought operating circumstances into central policy discussions.
• Built management experience across local teams before enterprise people leadership.

Decisions in context

I joined a 176-person services company in September 2010, leading eleven colleagues with ₹1.2 crore annual administration and development expenditure. The company then worked in industrial resource and organic-residue services; the later fourteen-plant biogas portfolio was not already present. Site employment made the limits of a centrally written policy easier to see. A process could be formally consistent and still depend on travel, access or local explanations that the central account did not contain. I worked with operating managers to understand those conditions while keeping responsibility for technical decisions with them. The role developed my ability to explain differences without treating every local circumstance as an exception to be suppressed. It also taught me that a good account needs follow-up after the initial response, because a completed central task may leave the employee's practical question unanswered.

Reason for the move

Promoted to lead people operations across the growing services enterprise.

Mandate

Manage regional employment processes with clear ownership of requests, responses and local follow-up.

Outcomes

• Developed team responsibility alongside employee-case review.
• Examined whether field colleagues could use central processes during their work.
• Learned to distinguish consistent principles from identical treatment of different circumstances.

Decisions in context

The regional role brought eight colleagues and an ₹82 lakh annual administration budget into my remit. The employer's 240 employees and ₹38 crore revenue described the wider business rather than my personal scope. Field assignments made practical access to people processes a recurring question. A colleague could know that a route existed and still struggle to use it within the working day or understand who would respond. I learned to ask about those conditions before interpreting a delayed request as lack of interest or a quiet period as satisfaction. The role also required me to explain why a shared principle could lead to different practical arrangements. I reported to the head of people and had no statutory appointment. After more than six years, the move to site employment offered a closer relationship with the operating context behind the cases I was managing.

Reason for the move

Joined a site-services business for broader responsibility at the interface of policy and operating work.

Mandate

Record employee questions accurately and support the route from receipt to an intelligible response.

Outcomes

• Learned to separate administrative closure from the employee's understanding of an answer.
• Developed care with the access and handling of personal case records.
• Built practical experience before taking responsibility for a regional team.

Decisions in context

My first appointment began in June 1998, one month after the personnel-management master's degree. I worked under the people manager in a ninety-two-person business, without staff or spending authority. The tasks were modest but consequential: record what had actually been asked, identify the person able to respond and make sure the answer could be understood. I learned that closing a file and resolving a question were different events. An employee might understand the organisation's position and still disagree, which needed to remain possible without changing the record to make it look more settled than it was. Those early observations shaped my interest in the conditions of a process. They did not prevent my later error with the zero-concern score. The chronology retains that contradiction because professional experience should not be written as a history of inevitable good judgement.

Reason for the move

Promoted into regional people management after sustained case and coordination work.