What Killing Roaches Taught Me About Construction

What Fighting a Pest Infestation With AI Taught Me About Running a Project

Here’s the deal. I recently spent several months working with AI to systematically eliminate a genuine cockroach infestation at my own house, and by the end of it, I realized I had essentially relearned every core Lean principle I already teach, just through a completely different problem. I want to walk through exactly what that process taught me, because the parallels to running a real construction project are almost too clean to be a coincidence.

How the Infestation Actually Started

A water line broke at our house, which led to a full remodel of that section, and shortly afterward, we brought in some larger used refrigerators to fit our family’s needs. Slowly, we realized we had a genuine infestation. In hindsight, the infestation almost certainly arrived with one of those used appliances, since the moment we finally removed that specific fridge, the problem disappeared for good. The common wisdom around this particular pest is bleak. Once you have them, people say you are essentially stuck living with them forever. I refused to accept that, and I decided to fight it systematically, with AI as my actual strategic partner throughout.

Lesson One: Never Fight the Enemy Everywhere

The first real lesson was refusing to spray or treat every single location at once. Real infestations concentrate around specific hiding spots, and AI kept redirecting my attention toward identifying those specific locations rather than treating the whole house indiscriminately.

This maps directly onto how a real project should be run. You do not solve every single problem on a project simultaneously. You identify the actual constraint limiting flow and focus your energy there specifically, rather than scattering effort evenly across everything that looks even slightly wrong.

Lesson Two: Intelligence Wins

Sticky traps were never actually about killing anything directly. They were reconnaissance, telling me precisely where the real activity was concentrated each night, so I knew exactly where to focus treatment the following day.

That is exactly the same instinct behind going to the Gemba, the actual place where real work happens, rather than leading purely from KPIs, dashboards, or a comfortable office removed from the real site. Genuine intelligence comes from direct observation, not from secondhand data alone.

Lesson Three: Logistics Wins

Here is the part that genuinely surprised me. Poison was not actually the biggest factor in solving this. Removing food and water sources consistently, having a home cleaned thoroughly every single day during the worst of it, and sealing every physical entry point I could find mattered far more than any single treatment applied.

Military history teaches the same lesson repeatedly. Most conflicts are decided by which side can no longer eat, communicate, move, or resupply, not simply by direct confrontation. Construction is identical. Projects fail because logistics fail. This is exactly why I no longer think of it as a simple site utilization plan, the term I grew up using early in my career. It is a genuine logistics plan, and real logistical superiority is what actually wins a project.

Lesson Four: Do Not Chase Individual Soldiers, Destroy the Base

Every individual pest represented a soldier. The actual hiding and breeding locations were the real factories behind the problem. The moment I stopped chasing individual sightings and focused entirely on destroying those underlying locations, real progress finally accelerated.

Construction runs on the exact same principle. Do not fight every individual RFI, every late delivery, every isolated mistake as its own separate battle. Fix the actual production system generating these symptoms in the first place, and trace every recurring problem back to its genuine root cause.

Watch for these signs a team is fighting scattered symptoms rather than addressing the actual root cause behind them.

• Constant reactive effort spent on individual problems that keep recurring in slightly different forms.
• No clear identification of the one or two locations or conditions actually generating most of the trouble.
• Energy spread evenly across every visible issue rather than concentrated on the genuine source.

Lesson Five: Momentum Is Fragile

This might be the single biggest lesson of the whole process. More than once, seeing even a small setback made me want to panic and escalate treatment everywhere at once. Each time, that impulse would have actually disrupted a strategy that was already quietly working.

Project teams do exactly this constantly. Things start improving, someone panics at the first sign of a hiccup, the entire plan gets changed, and all the accumulated momentum disappears. Sometimes real leadership simply means holding the line and trusting a system that is already working, even when progress feels uncertain in the moment.

I experienced this directly years ago with an early client, the very first time we implemented Lean at real, meaningful scale. Partway through, I genuinely started to panic, convinced something was not working. Someone on that team told me plainly to hold course and trust the systems we had already put in place. It took roughly eight months of patience before it clearly started working. W. Edwards Deming made a related point in his own writing, that genuine quality transformation is not instant pudding. You cannot implement Lean and expect everything to look perfect the following month.

Lesson Six: The Footprint Shrinks Before the Numbers Do

Real recovery follows a specific, predictable order. Chaos becomes organized first. Only afterward do the actual underlying numbers start improving. Misreading that order, expecting numbers to improve before the surrounding chaos has genuinely settled, is exactly what causes people to believe an effort has failed right when it is actually working.

Lesson Seven: The Last Stretch Feels Disproportionately Harder

I spent far more energy, attention, and discipline eliminating the final handful of stragglers than I did addressing the first hundred. Construction recovery efforts feel exactly the same way. The finish line is consistently, emotionally harder to reach than the starting point, even though the remaining work is objectively smaller.

Lesson Eight: Internal Disagreement Can Undo Real Progress

At one point, my wife and I genuinely disagreed about removing a specific appliance I suspected was still harboring the problem. Looking back, I am not proud of how that disagreement played out, but the underlying lesson matters regardless. A team that is not genuinely united on a key decision risks losing ground it had already fought hard to gain. Internal dissension between the people responsible for a project, say a superintendent and a project manager not genuinely aligned, can quietly undo progress just as effectively as any external problem can.

Lesson Nine: The System Beats Heroics

Discipline and a genuine system mattered far more than any single burst of heroic effort on my part. I am honestly not certain I would have succeeded without consistent AI coaching specifically pulling me back from my own instinct to panic and overreact. That coaching, more than any single treatment applied, is what actually won this.

Watch for these signs a team is relying on heroic individual effort rather than a genuine, disciplined system.

• Progress that depends heavily on one person’s personal intensity or willpower rather than a repeatable process.
• A pattern of overreacting to small setbacks by abandoning an approach that was actually still working.
• No one specifically coaching the team to stay calm and trust the plan already in motion.

Lesson Ten: The Real Goal Was Never to Win Every Battle

Here is the lesson that matters most. The actual goal was never eliminating every single pest directly. It was creating an environment where they genuinely could not survive in the first place. That is exactly how I have always approached running a real Lean project. I am never trying to attack a specific person. I am trying to build an environment where bad behavior and poor systems simply cannot take hold to begin with. Real victory never came from fighting harder. It came from making the environment increasingly hostile to failure and increasingly favorable to genuine success.

Applying These Lessons to Your Own Project

None of this requires an unusual problem to learn from. The same principles apply directly to any recurring issue on a real project, identify the actual root cause, gather real intelligence at the source, protect your logistics, hold the line when momentum feels fragile, and build a genuine system rather than relying on individual heroics.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build exactly this kind of systemic discipline, addressing genuine root causes and protecting real momentum, rather than fighting the same recurring symptoms over and over without ever resolving what is actually causing them.

So here is the challenge. Identify one recurring problem on your own project that keeps resurfacing in slightly different forms. Ask honestly whether your team has actually found its real root cause, or whether you have simply been treating each new occurrence as its own isolated battle.

Edwards Deming said it plainly: genuine improvement is not instant pudding. Hold the line, trust the system you have actually built, and give it the real time it genuinely needs to work.

On we go.

FAQ

Why does the article compare a home pest infestation to running a construction project?

Because both situations reward the same underlying discipline, identifying a genuine root cause rather than treating scattered symptoms, gathering real intelligence at the actual source of the problem, and maintaining a consistent system rather than reacting emotionally to every small setback. The specific problem differs entirely, but the pattern for solving it effectively turns out to be remarkably similar.

Why does panicking at a small setback tend to make a recovery effort worse rather than better?

Because overreacting often means abandoning or disrupting a strategy that was already working quietly in the background, simply because visible progress has not yet caught up with the real underlying improvement happening beneath the surface. That premature change frequently resets momentum that had already been building, extending the overall recovery rather than shortening it.

What does the article mean by saying “the footprint shrinks before the numbers do”?

It means real recovery typically brings genuine order and organization to a chaotic situation before the actual underlying metrics show visible improvement. Expecting numbers to improve immediately, before that underlying organization has genuinely taken hold, can lead someone to wrongly conclude an effort has failed exactly when it is actually beginning to succeed.

Why does the article conclude that the real goal was never eliminating every individual problem directly?

Because sustainable success comes from building an environment where problems genuinely cannot take root in the first place, rather than fighting an endless, exhausting series of individual battles against symptoms as they appear. That same principle applies directly to Lean leadership, where the goal is building systems that prevent bad outcomes rather than personally attacking every individual mistake as it happens.