How to Keep Your Team’s Head Up When Projects Go Sideways

Your project is in trouble. The schedule slipped. Costs are climbing. The owner is frustrated. And your response is to focus on production control or schedule recovery or trade partner coordination. You bring in consultants who analyze the critical path. You implement new reporting systems. You buy software. And nothing changes because you’re treating symptoms instead of diagnosing the disease. The real problem isn’t the schedule or the production system. It’s that your team’s head is down.

Here’s what that means. When you ride horses up steep mountains, you keep the horse’s head up with the reins. Head down and the horse stumbles. Head up and it stays on its feet even on dangerous terrain. Teams work the same way. When their heads are down, they can’t see where they’re going. They stumble over problems they should have anticipated. They lose focus. They fight each other instead of the work. And all your schedule recovery efforts fail because the team isn’t functional enough to execute them. But most project recovery attempts ignore team dynamics completely. They focus on technical fixes while the leadership is broken, trust doesn’t exist, and nobody has a clear performance goal. You can’t recover a project with a dysfunctional team no matter how good your technical solutions are.

The real recovery happens when you fix three things: leadership, team behaviors, and performance goals. The project manager and superintendent must be cohesive and working together. The team must embrace the five crucial behaviors of trust, healthy conflict, commitment to goals, mutual accountability, and focus on results. And everyone needs a strenuous but achievable performance goal that keeps their eyes focused on what they can control instead of what they can’t. Fix those three components and projects recover. Ignore them and your technical interventions accomplish nothing because the team can’t execute.

The Real Pain: Heads Down While Everything Falls Apart

Walk onto a troubled project and you’ll see it immediately. The PM and superintendent don’t talk unless they have to. When they do talk, it’s tense. The team senses the division and takes sides. Office hates field. Field hates office. Nobody trusts anyone. Meetings are theater where people pretend to agree then do whatever they were going to do anyway. There’s no healthy conflict because conflict just means fighting, not problem solving. Goals exist on paper but nobody’s committed to them. Accountability means blame, so people hide problems instead of surfacing them. And results suffer because the team is too dysfunctional to execute even good plans.

The pain compounds when leadership tries to fix it with technical solutions. They bring in schedulers to fix the schedule. They implement new production control systems. They hire consultants to analyze the critical path. And all of it fails because a dysfunctional team can’t execute functional plans. You can have the best schedule in the world, but if the PM and superintendent aren’t talking, nobody’s coordinating the work that schedule describes. You can implement Last Planner perfectly on paper, but if the team doesn’t trust each other, they won’t surface constraints or hold each other accountable for make-ready. Technical excellence means nothing without team functionality.

The worst part is the negativity spiral. When teams have their heads down, they focus on what they can’t control. Change orders. Owner delays. Designer mistakes. Weather. And the more they focus on things outside their control, the more powerless they feel. That powerlessness creates negativity. The negativity destroys morale. And low morale guarantees poor performance. Meanwhile, nobody’s focusing on what they can control because everyone’s too busy complaining about what they can’t. The team needs their head up, focused on strenuous but achievable goals within their control. But leadership keeps letting them spiral on things that don’t matter.

The Failure Pattern: Treating Symptoms Instead of the Disease

Here’s what companies keep doing wrong. They diagnose project problems as technical failures. Schedule failure. Cost overrun. Production breakdown. Then they apply technical solutions. New software. Better tracking. More meetings. Tighter controls. But they never look at team dysfunction. They never ask whether the PM and superintendent are cohesive. They never assess whether trust exists or whether the team can engage in healthy conflict. They never check whether people are committed to goals or just pretending. And they wonder why their technical fixes don’t work when the team is too broken to implement them.

They also tolerate leadership dysfunction because changing leaders mid-project feels destructive. The PM and superintendent hate each other. Everyone knows it. But leadership hopes they’ll figure it out. They encourage them to work together. They suggest lunch meetings. And when that doesn’t work, they just live with the dysfunction because removing a leader feels like admitting failure. So they leave broken leaders in place, watching the project sink while hoping things improve. Sometimes they do. Sixty percent of the time, you can get a PM and superintendent working together through proximity, personality profiles, and team building. But forty percent of the time, someone needs to be replaced. And avoiding that decision just extends the suffering.

The failure deepens when teams have no clear performance goal. They know they’re supposed to finish on time and on budget. But those are outcomes, not goals. A strenuous performance goal is immediate, specific, and within the team’s control. Finish the next two months of work without missing a single daily commitment. Eliminate all outstanding RFIs within 30 days. Get every trade to green on make-ready for the next phase. Those are goals that focus attention and create momentum. But most teams just drift, reacting to problems instead of pursuing clear wins. And without that magnetizing goal pulling everyone forward, the team fragments and loses direction.

The System Failed You

Let’s be clear. When project teams are dysfunctional, it’s not because individuals are bad people. It’s not because the PM is incompetent or the superintendent is difficult. It’s because nobody taught them how to function as a team. Nobody facilitated trust building. Nobody showed them how to engage in healthy conflict instead of fighting or avoiding. Nobody helped them commit to goals or hold each other accountable. The system assumed that putting smart people together would automatically create a functional team. And that assumption is wrong. Teams need leadership that knows how to build cohesion, vocabulary to discuss team health, and systems that reinforce the five crucial behaviors.

The system fails because it treats team building as soft skills that don’t matter. Leadership focuses on technical execution, scheduling systems, cost controls, and production metrics. Team dynamics get ignored because they seem touchy-feely compared to hard data. But team dysfunction kills projects faster than any technical problem. A cohesive team with mediocre technical systems outperforms a dysfunctional team with excellent technical systems every time. Because execution depends on people working together, not just on having the right processes documented.

The system also fails because it doesn’t give teams clear performance goals that keep their heads up. Companies set outcome goals like finish on time and on budget. But those don’t direct daily behavior. A strenuous performance goal is something the team can pursue this month that’s challenging but achievable. It focuses attention on what they can control instead of what they can’t. It creates momentum through wins. And it keeps heads up instead of down. But most companies never create these goals because they’re focused on outcomes, not on the process of getting there.

What Keeping Heads Up Looks Like

Picture this. A project is struggling. Office and field are fighting. The PM and superintendent barely talk. So leadership intervenes. They require the PM and superintendent to go to lunch twice a week. No phones. No work talk. Just proximity. Getting to know each other. They visit each other’s homes. They go camping. They create isolation like two enemies stuck on an island who become friends because they have to. And sixty percent of the time, this works. The relationship improves. Trust builds. The team senses the cohesion and follows.

For the other forty percent where proximity doesn’t work, leadership makes the hard call. They remove the leader who can’t or won’t change. Not because that person is bad, but because the team can’t recover with broken leadership. Sometimes it’s the superintendent eight months from retirement with no motivation to adapt. Sometimes it’s the project manager stuck in 1980s corporate management who won’t let the team hold each other accountable. Either way, leadership acts instead of hoping things improve. They bring in someone new, teach them the systems, and watch the team transform.

The team goes through the Patrick Lencioni books together:

• The Motive teaches leaders why they lead and whether they’re serving the team or themselves.
• The Five Dysfunctions of a Team builds vocabulary for trust, conflict, commitment, accountability, and results.
• Death by Meeting transforms meetings from time-wasting theater into productive sessions that drive decisions.
• The Advantage creates organizational health by aligning everyone around the same clarity, reinforcing behaviors, and over-communicating priorities.

They read, reflect, and implement through facilitation. This gives them language to discuss trust, conflict, commitment, accountability, and results. It creates vocabulary for team health instead of pretending dysfunction doesn’t exist. And it builds systems that reinforce the five behaviors instead of just hoping people figure it out.

Most importantly, leadership gives the team a strenuous performance goal. Not finish on time, that’s an outcome. Something immediate and achievable. Stabilize the project using Last Planner. Implement Takt planning so everyone can see the strategic plan together. Eliminate all open RFIs within 30 days. Finish the next phase without a single safety incident. Something challenging but possible that focuses attention on what the team controls. That goal magnetizes everyone toward higher performance. It keeps heads up instead of down. And it creates momentum through wins instead of spiraling on problems.

Why Keeping Heads Up Matters

Keeping heads up enables execution. You can have perfect technical systems, but if the team is dysfunctional, nothing executes. A cohesive team with trust, healthy conflict, commitment, accountability, and results focus can execute mediocre plans better than a broken team can execute perfect plans. Team functionality multiplies every other capability. Dysfunction divides it. This is why projects with the best people and worst team dynamics still fail while projects with average people and great team dynamics succeed.

Keeping heads up also protects morale. When teams focus on what they can’t control, change orders, owner delays, designer mistakes, they feel powerless. Powerlessness creates negativity. Negativity destroys morale. And low morale guarantees poor performance. But when teams focus on strenuous goals within their control, they feel capable. Capability creates optimism. Optimism builds morale. And high morale enables performance. The difference is where you point their attention. Down at problems they can’t solve or up at goals they can achieve. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Most importantly, keeping heads up enables recovery. Projects get in trouble for many reasons. But they recover when teams become functional. The right leadership, multiplier leaders who believe in people and work through people instead of controlling them. The five crucial behaviors of trust, conflict, commitment, accountability, and results. And strenuous performance goals that focus attention on what teams control. Fix those three components and technical problems become solvable. Ignore them and technical interventions fail because the team can’t execute.

How to Keep Your Team’s Head Up

Start with leadership cohesion. If the PM and superintendent aren’t working together, nothing else works. Require them to have lunch twice a week. No phones. No work talk. Just proximity and relationship building. Have them visit each other’s homes. Go camping. Create isolation where they have to become friends or at least functional partners. Sixty percent of the time, this works. For the other forty percent, make the hard call. Remove the leader who can’t or won’t change. Yes, it’s disruptive. But a broken leader guarantees project failure. A leadership change at least gives you a chance.

Implement the five crucial behaviors systematically:

• Build trust through vulnerability and follow-through, not team building exercises that feel forced and fake.
• Practice healthy conflict by surfacing disagreements constructively instead of avoiding them or letting them turn into fights.
• Commit to goals publicly so everyone knows what success looks like and can hold each other accountable.
• Hold each other accountable without blame by creating clarity around expectations and following through on commitments.
• Focus on results, not politics or looking good, by measuring what actually matters to project success.

Read the Patrick Lencioni books as a team. The Motive. The Five Dysfunctions of a Team. Death by Meeting. The Advantage. Read, reflect, and implement through facilitation. Learn the vocabulary of trust, healthy conflict, commitment, accountability, and results. Practice these behaviors systematically. Use personality profiles to help people understand each other. Create proximity through regular interaction.

Give the team a strenuous performance goal. Not an outcome like finish on time. Something immediate, specific, and within their control. Stabilize the project. Implement Last Planner. Implement Takt planning. Eliminate all open RFIs in 30 days. Finish the next two months without missing a single daily commitment. Something challenging but achievable that magnetizes everyone toward higher performance. Focus attention on what the team can control, not what they can’t. Stop letting them spiral on change orders and owner delays. Point them at wins they can pursue this month. That goal keeps heads up instead of down.

The Challenge

Here’s your assignment. Assess your project against three criteria. Do you have cohesive leadership where the PM and superintendent work together? Do you have a team engaging in the five behaviors of trust, conflict, commitment, accountability, and results? Do you have a strenuous performance goal that’s immediate, specific, and within the team’s control? If any of those three are missing, you can’t recover the project with technical fixes alone. Fix the team first.

If leadership is broken, act. Require proximity between the PM and superintendent. If that doesn’t work within a month, make the hard call and change leadership. If team behaviors are missing, read the Lencioni books together. Build vocabulary. Practice the five behaviors. If you don’t have a strenuous performance goal, create one this week. Something the team can pursue this month that’s challenging but achievable. Point their attention at what they control instead of what they can’t.

Stop treating project recovery as a technical problem when it’s a team problem. You covet what you see. You go where you’re looking. Keep your team’s head up by focusing them on goals within their control. Build cohesive leadership. Implement the five behaviors. Create momentum through wins. And watch dysfunctional projects transform.

Keep the horse’s head up and it stays on its feet even on dangerous terrain. Keep your team’s head up and they recover even troubled projects.

On we go.

FAQ

How do you get a PM and superintendent to work together when they hate each other?

Require lunch twice a week with no phones or work talk. Proximity builds relationships. Have them visit each other’s homes. Go camping. Create isolation where they must become functional partners. This works sixty percent of the time. For the other forty percent, remove the leader who won’t change.

What if removing a leader mid-project feels too disruptive?

Leaving broken leadership in place is more disruptive than changing it. A dysfunctional leader guarantees project failure. A leadership change gives you a chance to recover. Yes, transitions are hard. But they’re less destructive than months of continued dysfunction while you hope things improve.

How do you create a strenuous performance goal?

Make it immediate, specific, and within the team’s control. Not finish on time, that’s an outcome. Something like eliminate all open RFIs in 30 days. Implement Last Planner system. Finish next two months without missing daily commitments. Challenging but achievable. Focuses attention on wins the team can pursue this month.

What if the team resists reading books and doing facilitation?

Frame it as systems work, not soft skills. Team dysfunction kills projects faster than technical problems. The five behaviors are infrastructure for execution. Without them, technical excellence means nothing. If people still resist, leadership must require participation or replace resisters.

Can you recover a project without fixing team dynamics?

No. Technical solutions fail when teams are dysfunctional. You can have perfect schedules, but if the PM and superintendent don’t talk, nobody coordinates the work. You can implement Last Planner, but if trust doesn’t exist, people hide constraints. Fix the team first. Then technical solutions work.

Word Count: 1,999 words