I learned the people problem by following the dates that never quite agreed.

My first resource roster was a paper printout with dates that changed faster than I could replace it. I joined the fictional Varnelith Systems in July 1996 after completing a degree at Nirvayan Institute. The work was administrative: check a person's current assignment, confirm a proposed release and update the planning record. I had no authority to approve a project or promise a career move. I could, however, see how easily a provisional date became a commitment when it travelled from one conversation to another.

I learned to ask who had actually agreed to a release. A delivery manager might expect a person to remain for support after the formal project end. A receiving manager could already be planning a start. The employee might have been told neither. Resolving the record meant understanding the work and speaking to the people responsible for it. Accuracy was therefore more than correcting a cell. It required discovering whether the organisation had made a decision at all, and being willing to leave uncertainty visible when it had not.

In April 2001 I became an allocation manager at Varnelith. I led a small team and began working directly with account leaders on competing requirements. My mathematics background helped with capacity estimates, but it did not answer whether a proposed move was sensible for the person involved. I learned from conversations in which an employee had a relevant capability that the formal record omitted, or a legitimate constraint that a central plan treated as inconvenience. A staffing process could be orderly and still make poor decisions if its evidence was too narrow.

I moved to Samvetrik Digital in July 2006 to lead workforce planning. The company was growing its application-engineering business and needed a clearer connection between sales assumptions, delivery commitments and hiring. I did not control those functions. My mandate was to make their dependencies explicit. We distinguished work that was contracted from work that remained prospective and discussed what staffing action each justified. This sometimes made the plan less impressive. It also made it harder to explain away an avoidable gap as a sudden shortage of talent.

A 2011 internal-mobility review became a turning point. We had received 147 transfer requests, and fifty-eight releases occurred later than the dates communicated. Individual managers had defensible delivery concerns, but the combined result was a company making promises it could not coordinate. I asked for named handover plans and escalation before dates were missed. We funded ₹62 lakh of planned overlap. The next tracked cohort had 142 requests and twenty-four late releases. Different circumstances prevent a clean causal claim, but the process made the unresolved commitments discussable before the employee had to chase them.

In January 2014 I moved into a broader people leadership role. Workforce planning remained relevant, but I now had responsibility for business partnering, development and employment decisions across delivery units. I discovered the limits of my own preferred measures. A utilisation-led management scorecard I supported in 2016 discouraged some managers from releasing experienced people for mentoring and internal moves. I withdrew that single-metric emphasis after listening to project teams. The correction taught me to examine the behaviour a measure rewards before presenting it as a neutral description of performance.

I became CHRO in April 2019. The following year's cancelled mobilisation tested whether our employment commitments meant what colleagues thought they meant. We funded a defined period of paid transition for 312 employees while account teams pursued alternative work. I would not describe that as a complete redeployment success. Forty-four people still needed individual decisions at the first review. Reporting them clearly was part of the responsibility. It kept management focused on the people whose uncertainty had not been resolved by the stronger aggregate number.

My present remit covers ninety-eight people-function colleagues through five direct reports and ₹42 Cr in delegated annual expenditure. That budget is separate from the company's overall employee costs and from revenue responsibility. I report to CEO Revati Keshavan and present workforce matters to the board's nomination and remuneration committee as an executive. I have not served as a statutory director. My interest in a first external board role comes from the questions this work has raised about management assumptions, incentives and the quality of workforce information.

I remain most useful where a business is prepared to distinguish an encouraging signal from a completed outcome. A learning pathway needs evidence of capability and an opportunity to use it. A vacancy needs a real requirement. A staffing plan needs people who understand the commitment it represents. I do not expect those questions to produce an easy answer every time. I want them asked early enough for management to choose responsibly, and answered clearly enough that a colleague can understand what the company has decided about their work.