A dated record of responsibility for construction methods

Mandate

Develop and qualify construction methods and assemblies through the complete task and the responsibilities needed for adoption.

Outcomes

• Separated material qualification from the evidence needed for an earlier site operation.
• Supported redesign of twenty-four proposed modules before the affected variant's production release.
• Limited a painting-automation recommendation after examining elapsed time and assigned labour separately.

Decisions in context

The CTO appointment gave me responsibility for the contractor's method-development and qualification capability across its project portfolio. I report to Meera Velanthi and work with Daren Chovell on the practical consequences of adoption. My authority covers development, testing and demonstrators; it is not the total expenditure of the company's projects. I lead 142 employees through five direct reports, with contractors recorded separately. The recent cases show how I use that scope: funding evidence, making trade-offs explicit and recommending a method at the scale its support justifies. Project engineers retain design and construction approvals. I have presented these choices in board discussions as an executive but hold no director appointment. The role has made me more attentive to the difference between a corporate technology recommendation and the capability needed to execute it repeatedly. It has also increased the importance of explaining what a trial has not yet established before a benefit enters a project estimate.

Reason for the move

Current executive role; considering a compatible first external board contribution.

Mandate

Connect methods, materials and trial programmes with the contractor's changing delivery needs.

Outcomes

• Brought complete-task comparisons into technology trial recommendations.
• Linked material-impact comparisons with functional quantities and stated boundaries.
• Developed four managers to lead qualification work across project and factory settings.

Decisions in context

This role combined disciplines that had previously reached management through separate technical accounts. I became responsible for how methods development, material investigations and demonstrator programmes informed the next delivery decision. I led eighty-eight employees through four direct reports by the end of the period and held twenty-nine million Singapore dollars of annual authority. The company's expansion into Vietnam added another operating context to consider; a method examined on one project did not automatically become a standard for the whole portfolio. I encouraged recommendations that stated the intended application, the conditions investigated and the work needed before wider use. I also became more involved in explaining why an apparently favourable environmental or productivity indicator could be incomplete. The appointment prepared me to lead the technology function by connecting specialist evidence with programme and financial consequences, while keeping project engineering responsibility explicit. I moved into the CTO position after developing that broader capability and the managers needed to sustain it.

Reason for the move

Promoted to CTO in January 2022.

Mandate

Coordinate the design and qualification of repeatable components across factory, transport and site requirements.

Outcomes

• Introduced full-size assembly reviews for selected repeated components.
• Added service-task questions to module design discussions.
• Assigned review ownership across factory and site interfaces before production release.

Decisions in context

Prefabrication required me to manage the consequences of moving decisions earlier. A factory could benefit from repetition only if the design, transport and site interfaces were understood well enough to support it. I worked under the director of engineering and developed three direct reports who could coordinate those perspectives rather than optimise one part of the process alone. By December 2015 the function had forty-six employees and eleven million Singapore dollars of annual authority. Full-size reviews became an important way to discuss tasks that drawings had not made tangible enough for every participant. I also brought maintenance questions into those reviews, because a component's successful assembly did not settle its later service needs. This was a construction-method responsibility, not ownership of the company's full project programme. The appointment led into the broader building-technology role as I began connecting prefabrication decisions with materials, trial design and the contractor's wider capability for adopting new methods.

Reason for the move

Appointed vice president of building technology in January 2016.

Mandate

Evaluate technical alternatives through the sequence of work and their interfaces with following activities.

Outcomes

• Added preparation and follow-on work to method comparisons.
• Connected material investigations with the operations they were intended to inform.
• Established named ownership for assumptions passed from method review to project teams.

Decisions in context

I joined Varelim to work closer to the construction decisions that used material and method evidence. The appointment required me to consider the sequence around an activity, including the preparation it needed and the work that followed. I gradually built a team of eighteen employees with two direct reports, reporting to the engineering manager. The three-point-two-million-dollar annual authority recorded here belongs to the end of the appointment, rather than the much larger technology remit I hold now. I worked with operations to compare alternatives that could each be technically plausible while creating different programme consequences. That taught me to make assumptions visible before they became instructions for another team. I also learned that a useful recommendation could narrow the application of a method instead of either endorsing it everywhere or rejecting it entirely. The progression into prefabrication followed my growing responsibility for interfaces among design, production and the practical work of assembly.

Reason for the move

Promoted to head of prefabrication in January 2010.

Mandate

Prepare and interpret material investigations under senior engineering supervision.

Outcomes

• Recorded test purpose and conditions alongside the reported result.
• Supported investigations separating acceptance questions from construction-sequence questions.
• Prepared technical handovers that retained limitations relevant to the intended use.

Decisions in context

My first appointment followed completion of a civil-engineering degree in June 1996. I worked as a contributor in a five-person technical group, with no direct reports or delegated budget. The senior materials engineer reviewed my work and helped me understand why a result had to be interpreted through the question the investigation was intended to answer. I became careful about preserving age, conditions and test purpose when preparing a technical handover. The experience did not give me authority over a customer's construction operation, and I do not describe it that way retrospectively. It did show me where a useful laboratory account could become incomplete when another team tried to use it for a different decision. I left in December 2003 to join Varelim because I wanted to work with the contractor responsible for the sequence, interfaces and programme consequences around the material choice, rather than remain only at the point where the evidence was produced.

Reason for the move

Moved to a contractor to connect material evidence with the full construction method.