How I think
about delivery.

A contractor does not inherit risk at mobilization. It chooses much of that risk while deciding what to pursue, how to price it and what assumptions to accept.

Good portfolio governance asks more than whether a project can be won. It tests whether the client, contract, scope maturity, programme, resource profile, procurement exposure and cash cycle create a commitment the organization can deliver responsibly.

Questions that belong at the decision table

• Is the technical scope mature enough to understand interfaces and long-lead exposure?
• Does the programme reflect approvals, procurement, access, commissioning and authority dependencies?
• Which assumptions are carrying the commercial position—and who owns validating them?
• Can the organization resource the job without weakening existing commitments?
• What would have to be true for the project to finish well, not merely start?

The best time to protect margin, client confidence and delivery quality is before the organization turns an uncertain opportunity into a fixed obligation.

Most complex failures do not sit neatly inside one discipline. They appear where design packages, trades, authorities, suppliers, controls and operating requirements meet.

An interface is not only a drawing coordination issue. It may be commercial, physical, digital, procedural or organizational. A pump depends on electrical power, controls logic, drainage, access, structural support, acoustic performance, commissioning water and an operator trained to respond.

Make interfaces governable

• Name the interface and the required outcome—not only the participating parties.
• Assign one owner for closure while keeping contributors explicit.
• Track decisions, prerequisites and dates in the same operating rhythm as programme risk.
• Review constructability and maintainability with the people who will install, test and operate the system.
• Escalate unresolved interfaces while choices remain, rather than after installation makes change expensive.

Senior leaders add value by seeing across functions and contracts. They make the spaces between responsibilities visible enough to manage.

Commissioning is often scheduled near the end, but its success is determined by decisions made throughout design, procurement and construction.

Equipment can pass an individual test while the building still fails as a system. Integrated performance depends on sequences, controls, power availability, water quality, balancing, alarms, cause-and-effect, access, documentation and people who understand the intended operation.

Lead commissioning from the front

• Define the commissioning strategy and responsibilities during mobilization.
• Build system completion and prerequisites into the programme.
• Use technical submittals to protect testability, controls integration and maintainability.
• Progress from component checks to system tests and realistic integrated scenarios.
• Align witness points, records, training and authority approvals before the final testing window.

The executive role is to keep commissioning from becoming a specialist activity isolated at the end. It is the proof mechanism for the entire delivery system.

Projects become difficult to finish when completion is treated as a final phase instead of a condition designed into every package.

Late closeout problems are usually accumulated problems: incomplete approvals, unrecorded changes, missing test certificates, unresolved access, poor as-built discipline, late training plans and procurement that never secured spares or warranty information.

Create a completion architecture

• Define systems, areas, turnover packages and acceptance criteria early.
• Make document ownership and review cycles part of package responsibilities.
• Track as-built information as work changes—not as a reconstruction exercise.
• Connect snag closure to testing, records and final acceptance.
• Plan training, spares, warranties, demonstrations and defects response with the same discipline as installation.

Completion is not the absence of open work. It is the presence of an accepted, understandable and supportable operating asset.

A project team can finish construction while the owner remains unprepared to operate the asset. That gap is where reliability, safety and client confidence are lost.

Successful transition connects construction completion to operating processes. The FM team needs accurate asset information, access, training, maintenance requirements, consumables, spares, escalation contacts and confidence in how systems respond.

Design for day one of operations

• Bring maintainability and FM representation into design and coordination reviews.
• Organize asset data and O&M content around how the owner will use it.
• Train operators through systems and scenarios—not only supplier presentations.
• Define seasonal testing, warranty response and defects governance.
• Keep the project and service teams connected during the stabilization period.

Experience is not automatically organizational learning. If lessons remain in individual memories or closeout presentations, the next project pays to rediscover them.

A learning organization turns recurring insight into better bid questions, standard details, procurement strategies, commissioning plans, dashboards, training and decision rules. That conversion is a leadership responsibility.

Institutionalize what works

• Capture lessons while causes and consequences are still visible.
• Separate project-specific events from patterns that require enterprise action.
• Assign owners and deadlines for changes to standards, tools or training.
• Close the loop by checking whether the change improved later performance.
• Develop managers to explain decisions, not simply report status.