Gord Reynolds on Why “Complexity” Has Become Infrastructure’s Most Convenient Excuse

Few words are used more casually in infrastructure delivery than complexity. It shows up in boardrooms, project updates, post-mortems, and media briefings. Schedules slip, costs rise, risks materialize, and the explanation is almost always the same: it’s a complex project.

According to Gord Reynolds, that word has drifted far from its original meaning. What was once a legitimate description of interconnected systems has increasingly become a shield against responsibility.

“You can’t think clearly in chaos,” Reynolds says. “Clean inputs create clean outcomes.”

After decades working across public infrastructure programs, Reynolds has seen how often “complexity” is used not to describe reality, but to excuse avoidable failure. When decisions are uncomfortable, when ownership is unclear, or when trade-offs become politically inconvenient, complexity becomes the language of deferral.

When complexity replaces honesty

Large infrastructure projects are, by definition, multifaceted. They involve multiple asset owners, regulatory constraints, legacy systems, and long time horizons. None of that is in dispute. But Reynolds draws a sharp distinction between genuine system complexity and what he calls manufactured complexity.

In practice, many of the conditions that derail projects are visible early. Incomplete utility records. Undefined decision authority. Misaligned incentives. Sequencing that looks plausible on paper but collapses in the field. Accountability spread thin enough that no one truly owns the outcome.

These conditions are not mysterious. They are tolerated.

Labeling them as complexity reframes failure as inevitable rather than as the result of choices that could have been made differently. Over time, this framing becomes normalized. Projects don’t fail because the system is unknowable. They fail because the system quietly accepts ambiguity where clarity is required.

“This leads to that,” Reynolds says. “If you don’t understand cause and effect, you’re not managing a project. You’re reacting to it.”

The political convenience of calling problems complex

Complexity is appealing because it diffuses blame. When no one fully understands the system, no one can be held fully accountable. Delays become systemic. Cost overruns become structural. Missed milestones become unfortunate but expected.

The result is a slow erosion of responsibility.

When complexity becomes the default explanation, incentives stop aligning with outcomes. Effort is rewarded more than effectiveness. Oversight focuses on compliance artifacts rather than execution readiness. Meetings multiply, while decisions stall.

Reynolds is blunt about the cost of this mindset.

“Don’t admire the problem,” he says. “Solve it.”

Admiring complexity allows organizations to appear thoughtful while avoiding action. It encourages detailed analysis that never quite resolves into ownership. It replaces hard decisions with sophisticated narratives that explain why decisions are difficult.

Complexity versus executability

Reynolds does not argue that infrastructure should be simplified to the point of naïveté. Ambitious projects will always involve uncertainty. But ambition is not the same thing as unmanageability.

A project can be complex and still be executable.

Executability depends on clarity. Clear data. Clear standards. Clear decision rights. Clear accountability. When those elements are present, complexity becomes something to manage rather than something to hide behind.

“If you can’t point to the person responsible when something goes wrong,” Reynolds notes, “then no one was ever really responsible.”

That test is uncomfortable, but revealing. In many projects, responsibility exists in theory but dissolves in practice. Complexity becomes the explanation for why no one could have acted sooner, even when the warning signs were visible.

Why dismantling the complexity narrative matters now

Infrastructure investment is increasing in scale and urgency. Governments are spending more, projects are larger, and the tolerance for failure is shrinking. In this environment, the cost of tolerated dysfunction grows exponentially.

Continuing to explain failure through complexity undermines public trust. It signals that lessons are not being learned and that preventable mistakes are being repeated under a more polished vocabulary.

Reynolds argues that leaders who want different outcomes must challenge complexity as a blanket explanation and insist on clarity where it matters most. That means asking uncomfortable questions earlier. It means tracing cause and effect instead of managing impressions. And it means accepting that ambiguity is often a choice, not a constraint.

Reclaiming responsibility from complexity is not about pretending infrastructure is simple. It is about refusing to confuse difficulty with inevitability.

Complexity is not the enemy of infrastructure delivery. Avoidance is.

Until complexity stops being used as a convenient excuse, many projects will continue to fail quietly long before anyone is willing to say why.