From recording the next posting to questioning what the company carries forward.

Mandate

Make continuity, learning and leadership responsibility explicit in the employment choices around a regional property portfolio.

Outcomes

• Funded fourteen twelve-week handover assignments across six project completions at SGD 460,000 overlap cost.
• Resolved eighteen of 27 disputed responsibility points across nine leadership assignments; escalated nine to executive sponsors.
• Followed a 38-person capability pool through 24 project postings, nine asset roles and five agreed departures.

Decisions in context

The executive remit asks me to connect people proposals with the portfolio’s operating and financial decisions. I work with five direct reports and with leaders who hold responsibilities that my function must understand but does not own. The handover arrangement made time for explanation explicit. The capability pool preserved options while acknowledging that future assignments were uncertain. The authority review kept unresolved sponsor decisions visible rather than asking project leaders to negotiate them alone. I present these matters to the board and remuneration committee as an executive, with no director appointment. My current learning review distinguishes lessons used, lessons not yet tested and lessons judged unsuitable in a new context. That account reflects the habit I want the organisation to develop: examine experience carefully, explain the decision and avoid treating a completed report as proof of an operating result.

Reason for the move

Continuing in the role while considering a defined future executive or first-board contribution.

Mandate

Connect the employment responsibilities of delivery teams with the needs of operating assets and cross-project contribution.

Outcomes

• Established twelve peer-review assignments from 29 expressions of interest.
• Allocated SGD 240,000 annually for the assigned time and support.
• Made the receiving project’s retained decision authority explicit in each peer-review arrangement.

Decisions in context

Adding asset operations to my remit changed the questions I asked about project completion. Colleagues receiving an asset needed an account of choices whose consequences would continue after the delivery team moved on. I worked on the employment relationship between those groups, including time, responsibility and recognition. Technical acceptance and property obligations stayed with the relevant leaders and advisers. The peer-review assignments addressed another form of continuity: experienced managers helping a different team without losing the support of their own manager. We selected a smaller group than initially proposed because a defined contribution required capacity and purpose. I learned to be cautious about broad labels such as mentor when the organisation had not decided what work the role contained. The wider remit prepared me to discuss those choices alongside the cost and timing pressures of the portfolio.

Reason for the move

Appointed CHRO to lead the wider people function and contribute directly to executive portfolio decisions.

Mandate

Improve how project experience informs development assignments and learning across teams.

Outcomes

• Reviewed 46 lessons from four projects and identified eleven with clear receiving owners.
• Rewrote 21 entries with project specialists and archived fourteen without a useful action basis.
• Funded SGD 130,000 of corrective review and project participation after recognising the original process weakness.

Decisions in context

I joined Tervana to work across projects rather than support assignments within a smaller portfolio. The learning remit gave me a chance to connect experience with development decisions, but it also exposed a mistake in my approach. I asked teams to produce lessons before establishing who would use them. The resulting report looked substantial while leaving much of the receiving responsibility unclear. Correcting it required project specialists’ time and a willingness to archive material that did not support an action. I took responsibility for that redesign. The experience made me more interested in the relationship between two teams than in the size of a learning register. My function could create the conditions for that relationship and recognise the work involved; it could not certify technical conclusions or prescribe an answer for every later project.

Reason for the move

Accepted a broader people-director role spanning both development and the operation of completed assets.

Mandate

Clarify the people arrangements around assignments, local questions and movement between project teams.

Outcomes

• Recorded the continuing support expected from colleagues moving to a new assignment.
• Required receiving managers to confirm the role and reporting relationship before a posting was communicated.
• Separated personnel coordination from project technical authority in local guidance.

Decisions in context

The advisory role brought me closer to the decisions that shaped a project employee’s working week. I saw how an apparently straightforward transfer could leave a colleague answering to an old project while being assessed on a new one. I worked with managers to make those expectations explicit before the move. My three coordinators maintained the administrative record while I addressed the more complex interfaces and sought qualified advice where needed. I did not direct construction or certify project work. The value of the role lay in understanding enough context to make the employment arrangement workable. It gave me a practical foundation for later learning responsibilities, because I had seen how easily knowledge and authority could become separated when a team dispersed and everyone assumed the next manager would resolve the detail.

Reason for the move

Moved to a larger regional developer for a cross-project talent and learning remit.

Mandate

Maintain accurate employment arrangements around project-team arrivals, assignments and departures.

Outcomes

• Improved the record of assignment dates and responsible managers.
• Established follow-up for unresolved employment questions at project completion.
• Learned to distinguish an administrative posting from the responsibilities that continued after it.

Decisions in context

My first position involved the practical details around people joining and leaving project teams. The employment record had to be accurate, but I began to notice matters the standard fields did not explain. A colleague might move on a particular date while still being the only person who could answer questions about the earlier work. Another person might receive a new manager without understanding which responsibility had actually changed. I brought those questions to more experienced colleagues rather than improvise an answer beyond my authority. I had no team or delegated budget and learned through careful preparation, listening and follow-up. The role established my interest in the interval between a formal personnel action and the working arrangement it was supposed to create, an interval that remained relevant throughout the rest of my career.

Reason for the move

Promoted to a project-facing advisory appointment after developing experience of the assignment cycle.