Kirk Kendall | Why Industrial Projects Succeed or Fail Before Construction Begins

Kirk Kendall

Walk onto any industrial construction site and you'll see visible signs of success or failure. Cranes moving smoothly, crews working in rhythm, materials arriving exactly when needed. Or you'll see the opposite: confusion, delays, equipment sitting idle, frustrated superintendents trying to solve problems that spiral into more problems.

Here's what most people don't realize: that success or failure was largely determined before the first shovel touched ground.

Kirk Kendall has spent his career in industrial construction—aquaculture facilities, airport infrastructure, heavy industrial programs—and he's watched this pattern repeat. The projects that ran smoothly, that finished on time and on budget, they all shared something in common. They weren't necessarily the ones with the best weather or the most experienced crews. They were the ones where someone had done the hard thinking upfront.

"Good projects feel inevitable," Kirk says. "When you walk on site and watch teams execute, it looks like it's just happening naturally. That's because the real work happened months earlier—in the planning, in the systems, in the preparation."

What does that preparation actually look like? It's not just a thick binder of Gantt charts gathering dust in a trailer. It's the project manager who sits down with the site superintendent and walks through the entire construction sequence—not in meetings, but standing on the actual ground, looking at where material will stage, where cranes can reach, where weather will hit first. It's the engineer who challenges the design early because she sees how it affects construction logistics. It's the safety team that builds hazard management into the schedule, not bolted on afterward.

Kirk spent eight years as a commissioned Engineer Officer with the Canadian Forces, leading construction operations during deployment in Afghanistan. Military operations taught him something that transferred directly to industrial projects: preparation removes panic. When your team has trained for a scenario, when they understand not just their role but how it connects to the bigger operation, they execute. When they haven't, even experienced people start making errors.

One project that stands out: a large aquaculture facility expansion. The scope was tight, the timeline aggressive, and the site conditions were genuinely challenging. Most teams would have approached it by starting construction and solving problems as they arose. Instead, Kirk's team spent weeks in pre-construction, mapping out the site logistics in detail, identifying supply chain constraints, and building flexibility into the schedule at the critical points where they knew surprises might hit. They didn't avoid all problems. But because they'd thought through the likely scenarios, they had response strategies ready. The project came in ahead of schedule.

Compare that to a different project where the team got pressured to start early. The schedule looked good on paper, but the pre-construction work was rushed. Materials arrived before they could be staged. Subcontractors showed up before the site was ready. The team spent months in reactive mode, constantly shuffling, replanning, managing conflicts between trades. They finished, but the margin for error was gone. Weather delays that would have been absorbed in a well-planned schedule became critical.

The difference? One team did the thinking upfront. The other one paid for it in chaos.

This extends beyond logistics. It's about contract clarity. It's about understanding your supply chain. It's about identifying the technical risks before they become construction issues. It's about building relationships with stakeholders early so that when complications arise, you're problem-solving as partners, not adversaries.

Industrial projects are complex. There are regulatory requirements, environmental considerations, equipment constraints, weather, supply chains, multiple specialized trades. You can't eliminate every variable. But you can eliminate uncertainty. You can know what you don't know.

Kirk's philosophy is straightforward: strong execution comes from repeatable systems. Those systems start in planning. The best project managers don't just manage the present—they manage the future. They're asking the hard questions early. What happens if this supplier fails? Which part of the schedule is actually critical? Where will our team face their biggest decision points? How do we stage this work so that one setback doesn't cascade into ten?

Success on site is performance. But the thing that makes performance possible is what happens in those offices and conference rooms months before anyone breaks ground. It's the discipline to think it through thoroughly, to test the plan against reality, and to build execution systems that let your team do their best work.

That's not glamorous. It doesn't show up in photos. But watch a well-planned project run, and you'll see the evidence of it everywhere. And watch one that skipped that work, and you'll understand exactly what was missing.

The construction industry is learning, slowly, that the high-performing teams aren't the ones with the best excuses for delays. They're the ones who did the thinking upfront.