When Waiting for Problems Becomes the Problem

Here’s the deal. When Bannon arrived at the job site and asked Peterson what he’d done to prepare for the incoming lumber, Peterson said something that should make every superintendent wince: “We’ll be ready for it as soon as it gets here.” That’s not preparation. That’s hope disguised as a plan. And hope has never built a single project on time.

Most of us have been Peterson at some point in our careers. We tell ourselves the materials will show up when they’re supposed to. The trades will figure it out. The railroad won’t be a problem. And then one day we’re standing in the middle of a disaster we could have prevented if we’d just looked three moves ahead instead of staring at today’s work.

The Pain You Know Too Well

You’ve felt this before. The schedule looked fine two months ago, and then suddenly you’re sixty days out and everything’s collapsing. The owner adds changes nobody scoped properly. Trades are stacking on top of each other because sequencing fell apart. Materials show up with nowhere to stage them. And now your foremen are making reactive decisions because there is no plan anymore.

This is the pattern that destroys projects and people. Small unforced errors compound over time because nobody was watching three weeks ahead. Nobody was building relationships before they needed them. Nobody was staging the work before the materials arrived. Everyone was waiting for problems to show up instead of anticipating them when there was still time to solve them cleanly.

I’ve walked projects where five trades were colliding in the same zone and nobody could explain how it happened. The answer is always the same: the system failed to create visibility, and leadership failed to look ahead. People weren’t lazy or incompetent. They just didn’t know what they didn’t know, and nobody taught them how to be productively paranoid.

The System Didn’t Teach Them to Think Three Moves Ahead

Here’s what I want you to understand about Peterson. He wasn’t a bad superintendent. The problem was that the system never taught Peterson to anticipate. Nobody showed him how to process future problems while everyone else was still focused on today. He was doing exactly what most construction culture rewards: staying busy, reacting to issues, and hoping things work out.

Bannon arrived and immediately started calculating the space available for incoming lumber. He was thinking about how to pile different sizes so each would be ready at the hands of the carpenters when the morning whistle blew. He was asking about the railroad relationship before it became a crisis. He was processing political dynamics and stakeholder management while Peterson was just waiting for lumber to arrive.

That’s not natural talent. That’s learned behavior. Bannon had developed what I call productive paranoia. He was constantly scanning for what could go wrong, not because he was anxious or pessimistic, but because he understood that problems are easier to solve before they become emergencies. And he knew that protecting his people meant making strategic moves early when he still had options, not desperate moves late when all the good choices were gone.

What Bannon Saw That Everyone Else Missed

When Bannon asked Peterson about the railroad, Peterson said they hadn’t had much trouble. That answer should terrify you. It means Peterson saw a potential stakeholder issue and decided it wasn’t worth thinking about because it hadn’t become a crisis yet. Meanwhile, Bannon was already processing how to handle the political situation when two hundred thousand feet of lumber needed to cross those tracks.

Watch what happens when the railroad representative shows up. Bannon doesn’t yell or throw his hard hat. He’s firm, confident, and diplomatic. He tells his foreman to get the men back on the work. Then he turns to the railroad representative with a stern but respectful tone and says he expects the railroad won’t be blocked or delayed in any way. The representative leaves satisfied because Bannon showed he cared about the railroad’s concerns without compromising his project’s needs.

This is the interpersonal skill set that separates good superintendents from great ones. Technical competence isn’t enough. You have to navigate political situations, manage stakeholder relationships, and solve problems without creating new enemies. Bannon could have made that railroad representative his adversary. Instead, he made him someone who felt respected and heard.

Why Early Strategic Moves Save Your People

General Patton had a conversation with Bradley during World War II about casualties. Bradley was frustrated about losses, and Patton asked him to consider how many more casualties they would have had if they were still slugging through the mud instead of moving quickly. The point was brutal but necessary: sometimes taking calculated action early prevents catastrophic damage later.

The same principle governs construction projects. If we can make strategic moves in the first part of the job that don’t require workers to work too fast, too long, or unsafely, we should make those moves. Maybe it costs money to add shifts or bring in additional crews. Maybe it requires creative thinking to solve a permitting issue before it becomes urgent. These moves look like overkill when the schedule still shows green. But there will come a time at the end of the project when you’re in a crash landing and people will be unsafe, the work will be unclean and unorganized, and you won’t have any good options left.

The reason this matters so deeply is because we’re not just managing schedules. We’re protecting people. We’re protecting families. Every time we prevent a crash landing through early strategic action, we’re preventing the burnout and safety compromises and relationship damage that comes when projects spiral. That’s not soft leadership. That’s production strategy. That’s respect for people translated into operational decisions.

Teaching Your Team to Be Productively Paranoid

Productive paranoia isn’t something you’re born with. It’s a discipline you develop through practice and intentional coaching. When I’m walking to a job site with a foreman or assistant superintendent, I’m not just looking at today’s work. I’m narrating what I’m seeing three weeks out. I’m asking questions like, “That steel delivery is scheduled for two weeks from now, but I don’t see the crane access cleared yet. What happens if it shows up and we’re not ready?”

Over time, this becomes second nature. Your team starts thinking about work that’s coming instead of just work that’s here. They start asking what could go wrong before it does. They start building relationships with stakeholders before they need favors. And suddenly you have a field leadership team that prevents crises instead of just responding to them.

Here’s what productive paranoia looks like in practice. These are the quiet disciplines that prevent loud emergencies on Monday morning:

•  Scanning three weeks ahead every Monday and asking what could derail the schedule before it’s urgent 
•  Building relationships with inspectors, utility companies, and stakeholders before you need approvals
•   Staging materials and preparing work areas before deliveries arrive instead of scrambling when trucks show up
•   Processing crew capacity and trade availability for next month instead of assuming everything will work out

These habits don’t feel urgent when you’re doing them. That’s exactly why they work. You’re solving problems when solving them is still easy, not when it requires heroics and overtime and safety compromises.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. We work with builders who want to protect their people while delivering exceptional results, and we teach the practical disciplines that turn reactive leaders into strategic ones.

The other thing Bannon demonstrated was hands-on knowledge of the work. The book describes how he knew from long experience how to pile different lumber sizes so each would be ready when needed. He was out there giving a hand here, an order there, always good-humored though brisk, and always inspiring the crew with his own activity. He wasn’t hiding in the trailer. He was leading from the front.

This speaks to why I love self-perform work and why I encourage people to come up through craft positions or field engineer roles. When you’ve built with your hands, you understand what your crews are facing. You know what good sequencing looks like. You know the difference between busyness and flow. That knowledge isn’t optional for great superintendents. It’s foundational.

Building Better Standards While Learning from the Past

I need to address something about the book we’re discussing. “The Calumet K” was written in 1901, and there’s a section where the superintendent says they can’t have any women on the job. That language and attitude are unacceptable by today’s standards. It costs us nothing to support women and minorities in construction. Nothing. When I see a woman superintendent or project manager succeeding, I have genuine joy because I know that diversity makes our teams statistically more likely to win and do well.

Any time you have diversity on your teams, you have a higher statistical chance of success. That’s not political correctness. That’s data. We should all be acting appropriately one hundred percent of the time, creating environments where even children could be on the project site. Good language, respectful behavior, no inappropriate conduct, and genuine support for everyone who wants to build a career in this industry. That’s not soft. That’s smart business and basic human decency.

The Challenge: Make Your Strategic Moves Now

So here’s my challenge to you. What’s the strategic move you’ve been avoiding because you’re not in crisis mode yet? What’s the problem you can see coming but you’ve been telling yourself you’ll deal with it later? What’s the stakeholder relationship you need to build before you need it?

Don’t wait for the crash landing. Make your moves now, while you have options. Be productively paranoid. Anticipate problems. Protect your people by making the hard decisions early, when making them is still a choice instead of a desperate reaction. As W. Edwards Deming said, “It is not enough to do your best; you must know what to do, and then do your best.” Knowing what to do means seeing problems before they arrive and solving them before they become crises.

On we go.

Frequently Asked Questions

What’s the difference between productive paranoia and just worrying about everything?

Productive paranoia is disciplined anticipation with specific action attached. You’re dedicating time to look three weeks ahead, identify potential roadblocks, and assign someone to solve each one before it becomes urgent. Worry paralyzes you, while productive paranoia creates a checklist of preventive moves and executes them systematically.

How do I convince leadership to invest in early strategic moves when we’re not behind yet?

Frame it as risk mitigation with specific dollar amounts. Calculate the cost of a crash landing including overtime, rework, safety incidents, and burned-out workers. Then compare that to the cost of adding a shift now or staging materials better. Track outcomes and show leadership the disasters you prevented.

What if my team doesn’t have experience to anticipate problems like experienced builders do?

Then teach them by modeling it every day. Narrate your thinking when you walk the job together. Ask them to present a three-week look-ahead every Monday that includes potential problems and mitigation strategies. Over time this becomes second nature.

How do I balance productive paranoia with trusting my team without micromanaging?

Productive paranoia targets systems and processes, not individual people. You’re verifying that the system for tracking deliveries exists and is being followed, not checking whether a specific person did a specific task. When you find a missing system, create it, train people on it, and trust the system.

What are the most common warning signs a project is heading for a late-stage crash landing?

Watch for small delays that aren’t being recovered, deferred decisions like open RFIs, relationship friction being ignored, material long-lead items that haven’t been confirmed, and crew capacity assumptions that haven’t been verified. Any of these in combination means make strategic moves immediately.