Est. 1993

Chief Human Resources Officer · Singapore / Southeast Asia

2026-09-07 edition

Leon Halim

A development company should remember more than the buildings it completes.

Section · Speaking & conversations

Conversations for the people who commission, carry and inherit the work.

01

Who will use the lesson after the project team leaves?

40-minute keynote with audience discussion · Development executives, project leaders and learning teams

I examine the gap between recording a project lesson and making it useful to another team. The session begins with an invented review that produced a substantial document but few clear receiving owners. Participants consider how to identify the decision a lesson might inform, preserve the reasoning behind an earlier choice and recognise when a different context calls for a different answer. I discuss the employment arrangements needed for explanation, including funded time before experienced colleagues move fully into new assignments. The talk does not offer technical project guidance or suggest that a learning report can certify an engineering conclusion. Its purpose is to help leaders test the relationship between the person who knows the experience and the person expected to use it. I include the cost of correcting my original process and the distinction between a lesson examined, an action taken and an operating result that would need separate evidence.

02

Making the case for capability between assignments

50-minute executive workshop · CHROs, finance directors and property portfolio leaders

I invite participants to examine a fictional five-month gap affecting an experienced project group. The workshop compares the capability being preserved, the cost of retention, the uncertainty in prospective work and the alternatives management could consider. Attendees develop a concise decision account that separates committed assignments from plausible opportunities. They also define useful work during the interval and the evidence to be reviewed before the arrangement ends. The exercise does not assume that retention is always the right answer or that every project cycle should use the same approach. Individual employment matters remain outside the public discussion and require appropriate local advice. I use the final reconciliation of the fictional group to show why a programme report should follow temporary categories to actual outcomes. The intended benefit is a clearer management argument, with enough detail for financial challenge and an employment message that does not turn an uncertain pipeline into a promise.

03

The sponsor decision hidden inside a leadership role

45-minute facilitated conversation · Project sponsors, asset leaders and organisation-design practitioners

I explore what happens when a capable project leader is expected to reconcile responsibilities that the sponsors themselves interpret differently. The session uses nine invented assignments and a set of disputed decision points to move the discussion beyond titles and broad accountability statements. Participants distinguish questions that can be clarified through management agreement from those governed by investment, technical or contractual arrangements. I explain why a people document can record authority but cannot create it outside those underlying responsibilities. The conversation also addresses the pressure to declare a role programme complete while consequential questions remain open. Attendees consider an interim escalation route and the evidence an executive sponsor needs to decide. This is not a legal interpretation of joint-venture agreements or a standard delegation model. It is a practical examination of how an organisation keeps responsibility for its own unresolved choices instead of allowing them to become a private burden on the appointee.

04

Recognising the colleague who helps another project think

35-minute talk followed by a peer discussion · Experienced project managers, people leaders and asset teams

I discuss the difference between inviting experienced colleagues to mentor and giving them a contribution they can perform alongside their main assignment. The fictional example selects twelve defined peer-review roles from 29 expressions of interest, with time allocation and support. Participants examine the receiving team’s question, the contributor’s capacity and the boundary between advice and decision authority. I also consider how to explain non-selection without implying that the remaining colleagues have nothing useful to offer. The talk treats informal cooperation as valuable while distinguishing it from a sustained responsibility that requires preparation and follow-up. It does not attribute an entire project result to one reviewer or present a new title as evidence that learning occurred. The practical question is whether the organisation’s recognition changes the conditions under which a contribution can be made, including the way the person’s own manager allocates work and assesses performance during the assignment.

Short speaker biography

I am Leon Halim, a fictional CHRO working across Southeast Asian property development and operating assets. I examine how organisations retain experience, assign responsibility and fund continuity between projects. My speaking examples include a learning process I had to repair, with the costs and limits of each decision kept visible.

Standard speaker biography

I am Leon Halim, the fictional CHRO of Tervana Developments, based in Singapore with regional teams. My career began in project personnel coordination in 1993 and developed through project advice, talent and learning, and people leadership across development and assets. I now lead 42 colleagues through five direct reports. I speak about the receiving owner of a project lesson, capability during gaps between assignments and the sponsor decisions hidden inside a broad leadership role. My examples preserve technical and investment authority with the relevant specialists. I hold no directorships; my board exposure is through executive presentations. The employers, events and speaking proposals in this profile are invented.

Extended speaker biography

I am Leon Halim, a fictional people executive whose work connects development projects with the organisation that remains after them. I began at Marovek Estates in July 1993, coordinating personnel arrangements around project teams. An advisory role brought me closer to assignments and the responsibilities that continued when a colleague moved. I joined Tervana Developments in 2006 to lead project talent and learning, later extended my remit to operating assets and became CHRO in April 2020.

My current function includes 42 colleagues through five direct reports and SGD 8.7 million of delegated annual expense. The employer’s 1,650 direct employees exclude contractor workforces, and its revenue is separate from my financial authority. I am interested in the arrangements that let one team’s judgement inform another team’s work: a receiving owner, funded explanation, clear authority and recognition for the person making the contribution.

My proposed sessions examine project lessons, capability between assignments, sponsor responsibilities and experienced peer review. I include a process I helped design badly and then corrected, rather than present every intervention as successful from the start. Technical acceptance, investment decisions and contractual interpretation remain with appropriately qualified colleagues. I have executive exposure to a board and remuneration committee, with no director appointments. This biography, its institutions and its proposed appearances are fictional material demonstrating how a leadership website can explain a specific professional perspective.

An invitation

Contact

I would welcome a mandate involving people continuity across development and operating assets, particularly where management wants to examine what the organisation learns between projects. I am open to a carefully considered first board role and to conversations with project, asset and people leaders together. An initial enquiry should describe the business and the responsibility involved, without sending confidential project agreements, employee records or technical material that cannot be shared publicly.

Open to
  • Board appointments
  • Advisory roles
  • Speaking invitations
  • Executive opportunities

office@leonhalim.example