Early in a project career, attention goes to the visible failures. The dispute that surfaces in year three. The delay that compounds through the second half of execution. The claim that arrives after practical completion.
These are the moments that feel like the problem.
They are not. They are the consequence.
The problem usually began much earlier — in a moment that felt entirely manageable at the time.
What those moments look like
They do not announce themselves. They arrive as small, practical decisions made under the pressure of a moving project.
A notice that should be sent today — but the situation is still developing. The relationship with the other party matters. Sending now might signal a posture that the project does not need yet. It can wait until the picture is clearer.
A responsibility that is slightly unclear between two parties — but both are moving forward, and raising the question now would create friction in a relationship that is currently functioning well. The project will resolve it naturally as the scope becomes clearer.
A decision that should be formally recorded — but everyone in the room understood the agreement, and the written confirmation can follow once the immediate pressure eases.
A risk that has been identified — but assigning it formally would require a conversation that no one wants to have this week. It stays unallocated, absorbed into operational momentum, managed informally by whoever is closest to it.
Each of these decisions is defensible. Each has a rationale. Each, at the moment it is made, seems smaller than the cost of the alternative.
Why they compound
Structural compromises have a specific characteristic that distinguishes them from operational problems: they do not resolve themselves.
An operational problem — a coordination failure, a resource gap, a technical issue — can often be absorbed and corrected. It affects output, not position.
A structural compromise affects position. And position, once weakened, requires effort to recover — effort that is almost always more expensive than the effort that would have been required to protect it.
Each unanchored decision slightly narrows the options available in the next difficult conversation. Each unallocated risk slightly reduces the clarity of accountability when consequence arrives. Each delayed notice slightly reduces the contractual protection available when it is needed.
They accumulate. And they accumulate in a direction — always toward a position that is harder to defend.
What strong project leaders learn to do differently
They learn to recognise these moments early. Not through exceptional foresight, but through experience — through having seen, enough times, where the story that ended badly actually began.
They learn that the friction of stopping to anchor a decision, send a notice, or formally allocate a responsibility is almost always lower than the friction of recovering position after the window has closed.
And they learn something more specific: that the moments which feel least productive — the ones that slow a conversation down, introduce a question no one wants to answer, or formalise something everyone was willing to leave informal — are often where control is actually preserved.
The principle
Most project problems are not created by dramatic events.
They are created by small structural compromises made under pressure — each rational in isolation, collectively corrosive.
Strong project leaders do not prevent problems by anticipating everything that can go wrong.
They prevent them by protecting the structural conditions that keep the project’s options open — one small, friction-generating, apparently unnecessary decision at a time.
This article is part of ACC Trust Insights and reflects on the structural decisions that determine project stability — drawn from practice in complex construction and infrastructure projects, and the pattern of small compromises that precede most significant project failures.
ACC Trust Insights is the knowledge centre for Commercial & Contract Governance, Project Delivery and Risk Management in complex projects. Each article draws on practice in construction, infrastructure and energy environments.
office@acctrust.ro