A featured contribution from Leadership Perspectives: a curated forum reserved for leaders nominated by our subscribers and vetted by the Construction Tech Review Advisory Board.

Mercury

Hasan Turus, Engineering Manager

Better Projects Begin Before Construction

Hasan Turus

Hasan Turus

Hasan Turus is an Engineering Manager with extensive experience in complex engineering and data centre projects. His background covers electrical and mechanical infrastructure, design coordination, off-site manufacturing, construction and commissioning. He focuses on bringing design teams, manufacturers, specialist vendors and construction stakeholders together early to improve decision-making, reduce rework and deliver practical engineering solutions across the full project lifecycle.

Alignment Must Start Before Delivery

My approach to engineering leadership begins with a simple principle: bring the project stakeholders together early and help them operate as one team. On complex projects, each discipline can be technically competent and still create delivery problems if decisions are made independently. The design team may focus on technical compliance, manufacturers on production, vendors on their own equipment and construction teams on installation. Leadership is what connects those individual priorities to the same project outcome.

I start with the design team because the earliest decisions create the framework for everything that follows. Manufacturers and specialist vendors then need to be involved while those decisions can still be influenced. Construction input must also be brought into the process early enough to test whether the proposed solution can be installed, coordinated and delivered in the real project environment. The objective is not simply to invite people to meetings. It is to create a shared understanding of the design intent, the interfaces and the consequences of each decision.

Early Reviews Turn Stakeholders into a Team

Early design reviews are the key mechanism for creating that alignment. A useful review is not a presentation of a nearly completed design. It is a working session where the right people can challenge assumptions, expose interfaces and make decisions while options are still open. The discussion should connect technical intent with manufacturing capability, vendor requirements and construction reality.

“Trust does not come from team-building language alone. It develops when stakeholders see that concerns are heard, actions are followed through and decisions are made transparently.”

This approach changes the behavior of the project team. Stakeholders stop protecting only their own scope and begin to understand how their decisions affect others. Questions are raised earlier, responsibilities become clearer and risks are discussed openly. Over time, the group becomes more than a collection of companies and disciplines. It becomes a team with a common delivery purpose.

Faster Decisions Come from Shared Context

Projects often lose time not because a decision is technically difficult, but because the people required to make it are working with different information. Early collaboration creates shared context. When design, manufacturing, vendors and construction understand the same constraints, the route to a decision becomes shorter. The team can compare options based on their impact on the complete project rather than on one discipline alone.

Faster decision-making does not mean rushing. It means removing avoidable delays, repeated explanations and late escalation. Decisions made in the right forum, with the right stakeholders and at the right stage are more likely to remain stable through delivery.

In my experience on complex data center projects, particularly where off-site manufacturing is involved, early engagement between the design, manufacturing and construction teams has been critical. Decisions made during design can directly affect fabrication, transport, installation and commissioning, so resolving these interfaces can prevent significant changes later in delivery.

Less Rework Begins with Honest Challenge

Rework is usually the visible result of an earlier disconnect. A design may be technically correct but difficult to manufacture. Vendor requirements may be understood too late. A construction constraint may only become clear after installation has started. Early design reviews give the team permission to test these issues before they become physical work, cost or programme impact.

For an engineering leader, this requires an environment where challenge is welcomed. People need to be able to say that an interface is unclear, an assumption is unrealistic or a solution cannot be delivered as drawn. Raising a problem early should be treated as a contribution to project success, not as criticism of another discipline.

Trust Is Built Through the Way Decisions Are Made

Trust does not come from team-building language alone. It develops when stakeholders see that concerns are heard, actions are followed through and decisions are made transparently. When the team works through difficult issues together, people gain confidence in both the process and one another. That confidence makes future conversations more direct and productive.

This is particularly important on complex data center projects, where multiple systems, suppliers and delivery stages are closely connected. No single person or organisation can optimise the whole project in isolation. Engineering leadership therefore depends on creating the conditions for collective ownership while keeping accountability clear.

Engineering Leadership Connects the Full Lifecycle

A successful design is not only a set of coordinated documents. It must support what follows: manufacturing, installation, testing, commissioning, operation and future repeatability. Bringing stakeholders together early allows those later stages to influence the design before change becomes expensive. It also helps the team distinguish between standardisation that adds value and project-specific flexibility that is genuinely required.

My role as an engineering leader is to keep that full lifecycle visible. I want the design team to understand delivery realities, manufacturers and vendors to understand the wider system, and construction teams to understand the design intent. When those perspectives are connected early, the project becomes easier to decide, easier to build and easier to trust.

The articles from these contributors are based on their personal expertise and viewpoints, and do not necessarily reflect the opinions of their employers or affiliated organizations.
Top