My remit grew from maintaining the roster to questioning the promises behind it.

Mandate

Connect the employment proposition with the staffing decisions made across delivery and commercial teams.

Outcomes

• Funded the sixteen-week 2020 transition for 312 employees with an ₹8.4 Cr envelope
• Separated completion, demonstrated capability and deployment in the 240-person 2023 cloud pathway
• Retained agreed joining dates for 96 accepted offers after a 2024 customer delay

Decisions in context

I accepted the CHRO appointment with a mandate to connect decisions that had previously been discussed in separate meetings. Hiring, development and allocation each had a process, but the employee experienced their combined consequences. I built a closer working relationship with finance and delivery so that the cost and credibility of an employment commitment could be considered together. The role includes business partnering, reward, learning, people operations and workforce planning; technical acceptance and customer commitments remain with their respective owners. The 2020 mobilisation cancellation and 2024 offer decision required explicit expenditure rather than assurances that alternative work would appear. I report the unresolved cases as well as the favourable outcomes. My board exposure is executive presentation to the nomination and remuneration committee, not membership or statutory directorship. The next stage of this work is to examine whether internal release agreements are being kept in practice.

Reason for the move

Current appointment; considering a services people mandate with genuine responsibility for workforce commitments.

Mandate

Bring workforce planning, people partnering and development into one delivery-facing people remit.

Outcomes

• Replaced the 2016 single-metric emphasis after testing its effect on twelve project teams
• Completed 34 of 46 postponed mentoring sessions and reassigned owners for the remaining 12
• Introduced separate review of agreed releases, development time and account staffing assumptions

Decisions in context

The move into people leadership widened my responsibility beyond the allocation problem I knew best. I had to understand how reward, manager expectations and development arrangements affected the same staffing decisions. My most useful lesson came from a scorecard I had supported. Its utilisation emphasis encouraged managers to delay activities that the company said were important, including mentoring and internal transfers. I initially favoured better guidance, then accepted that the design itself needed revision. Working with delivery and finance, we retained commercial measures while making the associated people commitments explicit in management review. That was a correction, not a claimed transformation of the entire business. I learned to test the behaviour a measure encourages before asking managers to accept it as a fair account of their contribution. The appointment prepared me for a group role by exposing the limits of a purely planning-led view of people work.

Reason for the move

Appointed CHRO after demonstrating a broader people remit and taking responsibility for a scorecard correction.

Mandate

Distinguish credible project requirements from prospective demand and make internal movement commitments explicit.

Outcomes

• Reviewed 147 internal-transfer requests and identified 58 late releases in 2011
• Introduced requested versus agreed release dates with named handover owners
• Tracked a subsequent 142-request cohort with 24 late releases, without asserting identical circumstances

Decisions in context

I joined a growing services company whose planning conversations were moving faster than its ability to reconcile them. Sales, delivery and recruitment used different assumptions about demand, and an available person could be counted in more than one proposed plan. My team established clearer descriptions of the requirement and the conditions still outstanding. We did not pretend that every opportunity could be reduced to a dependable date. The 2011 transfer review brought a related weakness into focus: requested release dates had been communicated as though they were agreed. I coordinated the new review process and sought funding for selected handovers, while delivery leaders retained technical responsibility. The work made me interested in the management expectations behind the planning record. I moved into people leadership because better allocation information alone could not resolve incentives, development opportunities or the quality of the employee conversation.

Reason for the move

Moved into a broader people appointment after the planning work exposed recurring development and manager-incentive issues.

Mandate

Reconcile competing account requirements with confirmed availability and individual role suitability.

Outcomes

• Consolidated staffing requests from nine account teams into a common review
• Separated confirmed and tentative release dates for the planning group
• Recorded employee constraints and capability evidence alongside assignment history

Decisions in context

This was my first management appointment. I inherited colleagues who spent much of their time reconciling different versions of the same availability record. I introduced a shared review with account teams, but the more important change was in the questions we asked. A previous assignment did not describe every capability a person held, and an end date did not prove that the current manager had agreed to release them. I learned to listen to employees as well as delivery leaders. Sometimes the right answer was to challenge the proposed match rather than accelerate it. I had no authority to approve a commercial bid, and I made that boundary clear when sales colleagues sought a staffing assurance. The experience gave me a practical foundation in balancing requirements, but I wanted responsibility for the wider assumptions that created the allocation problem in the first place.

Reason for the move

Joined Samvetrik Digital to lead workforce planning at company level rather than manage account allocation alone.

Mandate

Maintain accurate assignment and release information and verify changes with accountable managers.

Outcomes

• Maintained the assignment roster for six delivery groups
• Introduced a record of who confirmed each revised release date
• Raised unresolved differences between project-end dates and actual handover expectations

Decisions in context

I began after completing my degree in June 1996. The role involved maintaining rosters, checking dates and following up with delivery managers. It was not an executive position, and I did not make hiring or project decisions. Its value was the exposure it gave me to how commitments travelled through a services business. I saw tentative dates become expected starts and learned to record the source of a change, not merely the latest value. When two managers gave different answers, I had to raise the disagreement rather than choose the answer that made the report look complete. I also learned to explain uncertainty without sounding evasive to a colleague waiting for a move. Those habits shaped the later career: identify the actual decision, establish who owns it and do not let the reporting system imply agreement that the people involved have not reached.

Reason for the move

Promoted to allocation manager after building a dependable record of coordination and judgement about unresolved commitments.