If the pre-project phase creates the illusion that a project is ready to move forward, the design and construction phase is where that illusion collides with reality. It is at this point that earlier decisions – made formally, insufficiently examined, postponed, or simply ignored – begin to reveal their consequences.
In practice, design is often viewed as little more than the stage where ideas are put on paper. In reality, its role is far broader. Design is meant to:
- verify whether previously approved decisions are technically feasible,
- coordinate engineering and infrastructure systems into a coherent whole,
- identify conflicts before construction begins,
- create a robust and executable delivery model.
In other words, design is not simply about turning ideas into drawings. It is the stage where uncertainty should be identified and eliminated. Yet this is precisely what often fails to happen.
When the pre-project phase has been handled only superficially, the design team is forced into a role it was never meant to play. Instead of refining solutions, designers spend their time searching for missing baseline information and resolving contradictions. Faced with significant constraints, they are often compelled to patch together workable solutions that address immediate issues while ignoring their wider consequences, rather than developing rational and optimized alternatives.
As a result, designers work in an environment where the fundamentals are constantly shifting:
- the client’s requirements continue to change,
- technical specifications are repeatedly revised,
- land ownership, permits, and regulatory approvals remain unresolved.
All of this drives up project costs, yet the blame frequently falls on the designers, who are accused of proposing “unjustified” or “inefficient” solutions. In reality, design ceases to be a structured engineering process and turns into an endless effort to adapt working drawings to a problematic reality that the project itself has created.
This leads to the next major gap. The intended sequence: baseline data and project requirements are established first, followed by design development. What actually happens: design progresses while the project’s fundamental assumptions are still being clarified.
The inevitable consequence is a growing number of iterations, revisions, and repeated approvals. From the outside, however, everything appears to be under control:
- there is a schedule,
- project stages are formally defined,
- design packages continue to be issued,
- coordination meetings take place.
Yet having a process does not necessarily mean having control. This becomes particularly evident in project scheduling. Under a well-managed approach, the design schedule should account for:
- the logical sequence of design disciplines,
- review points for intermediate decisions,
- coordination between engineering disciplines,
- the timing of baseline information and regulatory approvals.
In practice, however, the schedule often degenerates into nothing more than a list of document submission deadlines. Design performance is judged not by the robustness or quality of engineering decisions, but by whether deadlines are met. This creates an extremely dangerous dynamic. The more unstable the project becomes, the greater the pressure to maintain the schedule.
As a result, problems are not resolved. They are simply pushed into the construction phase. Consequently, construction typically begins with unresolved issues already embedded in the project:
- design decisions remain only partially coordinated,
- project documentation is still unstable,
- changes continue throughout execution,
- the project budget remains uncertain.
From this point onward, the cost of every modification rises dramatically. Changes that could have been resolved during design through revised calculations and updated documentation now become:
- demolition and rework of completed construction,
- equipment downtime, labor inefficiencies, and unnecessary movement between sites,
- disruption to construction sequencing,
- declining workmanship and lower overall project quality,
- repeated rescheduling of material deliveries,
- overstocked warehouses, along with increased risks of material damage or theft,
- growing conflict between project participants.
This is the point where project management fundamentally shifts from managing the project to reacting to its consequences.
The transition is especially visible in the way changes are handled. In a well-managed project, every change follows a structured process, with its impact on schedule, cost, technical solutions, and future operations carefully assessed before implementation.
In reality, changes are often introduced directly into construction:
- “to avoid stopping the work,”
- “to save time,”
- “the documentation can be updated later.”
As a result, the design documentation starts chasing the work already underway, documenting reality after the fact instead of defining it. This is one of the most critical moments in the entire project lifecycle. Beyond a certain point, mistakes become physically embedded in the asset itself – in the concrete, engineering systems, structural elements, and spatial layouts.
Once that threshold has been crossed, the project loses its ability to respond to change at a reasonable cost. Yet the appearance of control often remains:
- construction continues,
- crews remain on site,
- contractors are working,
- progress reports are submitted.
In reality, management is no longer focused on achieving the best possible outcome. Instead, it becomes an exercise in limiting the damage caused by earlier decisions. These are fundamentally different management models.
In the first, management prevents problems.
In the second, management spends its time containing crises and putting out fires.
Another important consequence emerges as well. The longer a project remains in reactive mode, the more dependent it becomes on individual people, informal arrangements, and manual intervention. Rather than becoming more resilient, the system compensates for its own instability through constant supervision and hands-on control.
As a result, many construction projects ultimately rely not on well-designed processes, but on a handful of exceptional specialists who keep the project alive through personal intervention. Such a model scales poorly and is almost impossible to replicate because it depends on crisis managers rather than on an effective management system.
Ultimately, even a completed facility does not necessarily represent a successful project. Final costs, delivery schedules, operational performance, and the volume of hidden problems may differ dramatically from what was originally expected.
By now it should be clear that construction is not the stage where a project is created. Construction is the stage where previously made decisions become physical reality. And there is no guarantee that those decisions were the right ones.
In the next part, we will examine what happens after construction is complete – during operation, maintenance, and modernization – where the true cost of decisions made during the earliest stages of the project lifecycle finally becomes visible.


