Systems coherence: The missing dimension in complex projects

Complex projects rarely struggle because of technical difficulty alone. More often, challenges emerge from how decisions, teams, and delivery structures interact over time. This article explores the role of coherence, the often-unseen condition that allows complex systems to perform effectively. 

Almost every complex project begins with familiar structures like cost, schedule, scope, risk, and contracts. They form the backbone of our planning models and offer the comfort of what we believe we can control. Over decades, we’ve built sophisticated tools around them: risk registers, earned-value, Gantt charts, and governance frameworks. They give us an impression of order, sometimes even the sense that order can be managed into existence. 

But anyone who has lived inside a major project knows these visible structures do not reveal the full picture of how a project really behaves. Projects with very similar structures often behave wildly differently. Beneath them lies something more subtle and far more determinative. What truly matters is the system of interactions between the parts.  

Where projects actually struggle 

Once a project moves beyond concept, it starts to behave like a system, maybe even resembling a living system. Schedules shape procurement. Procurement shapes engineering. Engineering shapes construction. Construction shapes operations. Governance shapes everything. 

Different projects may vary in scope, budget, geography, politics, or technical complexity, yet the patterns of recurring challenges are surprisingly similar across industries that deliver large, complex initiatives. 

You’ve likely seen some version of these:

• Owners pushing for certainty before certainty exists
• Designers buried under shifting scope or unclear decision making
• Contractors absorbing risks they never intended to manage
• Governance frameworks that tidy accountability on paper but blur it in practice
• Regulators or external stakeholders moving on timelines unrelated to project urgency. 

These problems rarely arise because a single part is broken. They arise because something between the parts isn’t functioning as it should. As soon as teams recognize that interdependence drives outcomes, their first instinct is to seek alignment. When alignment doesn’t come easily, they may try to manufacture it. 

This is where many projects subtly go off course. Alignment, even sincere alignment, does not guarantee performance. When agreement is forced, the system becomes heavy. When agreement is too smooth, the system becomes passive. When agreement arrives too quickly, inquiry collapses. When consensus replaces curiosity, misalignment hides beneath the surface. 

A healthy system is not one without friction; it is one where friction has direction. The pushes and pulls between project participants, owner, designer, contractor, governance, create a dynamic that can either fuel momentum or drain it. Too much force between functions and the system becomes unstable; too little and it becomes lethargic. A lopsided dynamic can cause entire parts of the system to shrink in relevance while others become overextended. 

In systems language, this quality is called coherence. Projects don’t struggle because their parts are misaligned. They struggle because something in between those parts is not moving in a coherent way. Most complex projects don’t fail because any single component is weak. They fail because the components never synchronize. 

Coherence is the quiet property that allows a project to advance with purpose rather than fight against itself. 

A pattern hidden in plain sight 

Across years of work on highway and bridge programs, from small corridor upgrades to nationally significant routes, one pattern has appeared for me again and again. It’s subtle, but once you see it, you can’t unsee it: 

The finished infrastructure and the organization required to deliver it often reflect the same underlying system. 

This is not necessarily in a literal sense, but in a way that can be remarkably useful. A highway works, not because everything is perfect, but because all the elements, alignment, lanes, merges, structures, speed environments, on-ramps and off-ramps are designed to work together. Any one piece can be engineered flawlessly. But if the relationships between pieces are poorly conceived, the user experience becomes unpredictable, congested, even unsafe. 

A project system behaves in exactly the same way. Teams often fixate on their own “lane”: engineering, construction, commercial, permitting, operations, governance. Each can perform well individually, yet the flow of the project, its ease, its resistance, its sudden bottlenecks, emerges entirely from how these lanes interact. 

Here is the useful twist 

Because it is often easier to perceive system behavior in a physical object than in a complex organization, leaders can sometimes understand the project system better by studying the infrastructure system they are building. 

The metaphors practically offer themselves:

• Adding an extra traffic lane is a form of scope creep.
• Traffic merging too early or too slowly resembles stakeholders entering the project at the wrong time.
• A poorly designed interchange behaves like unclear decision pathways with congestion guaranteed.
• A bridge span with incorrect expansion joints mirrors a governance structure with no tolerance for flexibility. 

These analogies are not the point, but they can be the doorway. The deeper insight is that the infrastructure system reveals how the project system wants to operate; where flows need support, where tension is useful, where structure is missing, and where misalignment is hiding. And once project leaders learn to see coherence in the built asset, they begin to recognize where coherence is missing in the teams building it. 

How leaders can cultivate coherence 

You cannot force coherence. You cannot mandate it. But you can create the conditions where coherence naturally emerges. Three disciplines matter most: 

 

Above all, you cannot control coherence. But you can recognize it, protect it, and lead in ways that let it grow.

Why coherence drives outcomes 

In the end, the lesson is disarmingly simple. Projects don’t fail because their parts are weak. They fail because their parts never learn how to move together. 

The physical infrastructure we build reminds us of this every day. A highway works not because each lane is perfect, but because the lanes, ramps, structures, and flows are designed to cooperate. The same is true of the teams who build it. When governance, design, construction, operations, and external partners move in isolation, the project behaves exactly like a network with broken links: slow, noisy, and full of preventable friction. But when leaders consciously cultivate coherence between these groups, shared timing, shared visibility, and shared constraints, the system begins to behave differently. Risk becomes more predictable. Decisions become cleaner. Progress becomes smoother. The project stops resisting itself. 

You don’t need perfect conditions for this shift. You need alignment early, clarity often, and structures that reward cooperation. 

See the project as a system building a system. When the people constructing the highway work with the same coherence that the highway itself requires, everything changes. Delivery accelerates, risks diminish, and outcomes begin to match their intent.  

Coherence is what allows complex work to move forward without constant forcing.