Seeing at the Gemba

Posted on March 13, 2026March 13, 2026 by Jason Schroeder

Read 30 min

The Scheduler Who Took Two Months to Notice a Failing Project through Power BI Dashboards

There is a project scheduler sitting in a corporate office three hundred miles from the jobsite. He manages schedules for seventeen projects across the region. Every day he opens Power BI dashboards filtering data from P6 schedules. Colorful charts show float trends, variance analysis, and critical path metrics. And one day, something feels wrong about a particular project. He cannot pinpoint it. Just a feeling. So he keeps watching. Two months later, the dashboard finally flags the project. Red indicators everywhere. Schedule variance off the charts. Critical path compressed. Float consumed. And the scheduler calls the project team: we need to swarm and recover this project immediately. The team mobilizes. Consultants arrive. Recovery plans get written. And six months later, the project finishes four months late despite heroic efforts. When someone asks the scheduler what happened, he explains proudly: I noticed something was wrong and kept watching the dashboards until the data confirmed it two months later. Then we acted quickly to minimize damage. And he does not understand why people are not impressed. Because two months is not quick. Two months is catastrophic. In those two months, the project burned through contingency, destroyed relationships with trades, and locked itself into a crash landing that no amount of swarming could prevent. Meanwhile another project using Takt planning spotted a sequencing problem in four hours. Not two months. Four hours. The superintendent noticed trades stacking up visually on the Takt board. Called an afternoon coordination meeting. Adjusted the sequence. And work resumed flowing the next morning. Same industry. Same problem type. Different latency. And the gap between two months and four hours is the difference between projects that succeed and projects that fail.

Here is what happens when teams cannot see problems at the Gemba, the actual place of work. A superintendent manages a project using CPM schedules. The P6 file has 5,000 activities. Logic tied. Resources loaded. Updated weekly by a project engineer who inputs actual dates and runs recalculations. The engineer uploads the updated schedule to the project website. Sends an email announcing its availability. And assumes communication is complete. Meanwhile on the jobsite, mechanical falls three weeks behind because steel fabrication delayed. But the delay does not show up in the CPM schedule for six weeks. Why? Because the logic ties are so complex that the impact takes weeks to ripple through the network. And by the time the schedule shows the problem, mechanical is six weeks behind instead of three. Recovery costs double. Trade relationships deteriorate. And the owner starts questioning competence. Not because the team lacked skill. But because the scheduling system hid the problem for six weeks while it metastasized from manageable to catastrophic. CPM is not a visual system. It is a data system. And data systems have latency that kills projects.

The real pain is the research proving visual systems win. Studies analyzing thousands of projects show traditional project management methods using CPM achieve only 26% success rates. Absolute failures are 21%. And projects that are challenged are 53%. When teams switch to agile methods like Scrum or lean methods like Last Planner, success rates jump to 42% minimum. Challenged projects drop to 50%. And failures plummet to 8%. That is a massive improvement. From 26% success to 42% success. From 21% failure to 8% failure. And the primary difference is latency. How quickly teams see problems and decide to act. Teams that identify and begin correcting issues within five hours have dramatically higher success rates than teams that take days, weeks, or months to notice problems through dashboards and reports. Five hours is the threshold. Not five days. Not five weeks. Five hours. Because problems compound. Small issues become big issues. Big issues become disasters. And the longer you wait to act, the harder recovery becomes.

The failure pattern is predictable and expensive. A project uses CPM scheduling. The scheduler sits in a corporate office reviewing dashboards monthly. A superintendent on site notices something feels wrong. Electrical seems behind. But the CPM schedule shows them on track. So the superintendent questions his judgment. Maybe electrical is fine. Maybe I am overreacting. Two months later, electrical admits they are six weeks behind. The schedule finally catches up to reality. And the project scrambles to recover. Crash schedule. Mandatory overtime. Compressed sequences. And ultimately finishes three months late. When someone asks what happened, the answer is always the same: we did not see the problem until it was too late. Because CPM schedules hide problems instead of surfacing them. The complexity creates opacity. The data lag creates latency. And by the time dashboards show red flags, the damage is done. Meanwhile projects using Takt boards see problems the day they start. Literally. A trade falls behind by one day. Everyone sees it on the visual board. And they adjust immediately. Before the one-day delay becomes a one-week delay that becomes a one-month delay that destroys the project.

I had a recovering scheduler call me recently defending CPM. He said: Jason, you are wrong. CPM is great. I had a project where I felt something was wrong. So I kept watching the Power BI dashboards. Sure enough, two months later the project showed up flagged. We swarmed and recovered it. And I said: you just proved my point. Two months. You took two months to notice a problem that visual systems would have surfaced in hours or days. That latency is the problem. Not whether you eventually noticed. But how long it took. Because in two months, small problems become catastrophic. And recovery costs ten times more than prevention. That is why Takt planning, Last Planner, and Scrum outperform CPM. Not because the people are smarter. But because the systems have lower latency. Problems surface immediately. Teams see them at the Gemba. And they act within five hours instead of two months. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

What Seeing at the Gemba Actually Means

Gemba is a Japanese word meaning “the actual place of work.” Where the work happens. Not the office. Not the conference room. The jobsite. The production floor. The place where value gets created. Seeing at the Gemba means going to the actual place of work, observing what is happening, and making decisions based on reality instead of reports. CPM schedules remove decision-making from the Gemba. Schedulers sit in offices. Review data. Generate reports. And make recommendations based on information filtered through multiple layers of abstraction. By the time problems show up in reports, they are old news. Already damaging the project. Already compounding. Visual systems put decision-making at the Gemba. Where people can see reality unfiltered. And respond immediately.

Latency is the delay before action. Between problem occurrence and problem identification. Between identification and decision. Between decision and action. Every layer of latency allows problems to compound. A trade falls one day behind. With visual systems at the Gemba, the superintendent sees it that afternoon. Calls a coordination meeting. Adjusts the sequence. And work resumes flowing the next morning. Total latency: four hours. With CPM systems, the delay does not show up in the schedule for weeks. The scheduler notices it months later through dashboards. And recovery happens after the problem has compounded into catastrophe. Total latency: two months. Same problem. Different latency. Catastrophically different outcomes.

Signs Your System Has Too Much Latency

Watch for these patterns that signal your scheduling and coordination systems hide problems instead of surfacing them:

Problems get discovered weeks or months after they start because scheduling systems lag reality and dashboards filter information through multiple abstraction layers before flagging issues
Superintendents notice problems on site but second-guess themselves because CPM schedules show everything on track creating cognitive dissonance between reality and reports
Recovery efforts start after problems compound into crises instead of when issues are small and easily corrected because latency delays identification and decision-making
Schedulers work in offices reviewing data while superintendents work on sites unable to see schedule status visually forcing reliance on reports instead of direct observation
Teams spend more time updating schedules and generating reports than solving actual coordination problems because administrative overhead consumes capacity that should go to problem-solving
Project success depends on schedulers noticing anomalies in dashboards instead of teams seeing problems directly at the Gemba and acting immediately without waiting for corporate confirmation

These are not people problems. These are system design problems. CPM creates latency by design. Data-driven systems require data collection, processing, analysis, and reporting. Each step adds delay. Visual systems eliminate latency by making problems visible immediately at the Gemba where work happens and decisions get made.

What Visual Systems Must Accomplish

Systems that enable seeing at the Gemba must meet specific criteria. They must be visual. Not just data tables. Actual visual representations that show status at a glance without analysis. They must bring problems to the surface immediately. Not next week. Not next month. The moment problems occur. They must show clearly what the problem is to everyone. Not just schedulers. Not just superintendents. Everyone on the project team sees the same reality simultaneously. They need to be easily understood. No training required to interpret. No complex analysis. Just look and know. They need to be easily checked. Walk past the board and verify reality matches the plan. No software required. They need to be actionable. Seeing the problem immediately suggests the solution. They need to be fast. Minutes to update. Not hours. Not days. They need to be reliable. Reflect actual reality. Not aspirational plans disconnected from field conditions. And they need to begin immediately. Problems visible today. Solutions implemented today. Not two months from now.

Takt planning accomplishes this. Visual boards showing zones and trades flowing through sequences. When a trade falls behind, everyone sees it immediately. The visual gap between planned position and actual position is obvious. No analysis required. Just look. See the problem. Call a meeting. Adjust. Resume flow. Total time from problem occurrence to solution implementation: hours. Last Planner accomplishes this. Weekly work planning with percent plan complete tracking. When commitments fail, teams see it in the weekly meeting. Discuss causes. Remove constraints. Re-plan. Total time: days. Scrum accomplishes this. Sprint planning with daily standups. When impediments arise, teams surface them immediately. Remove blockers. Continue sprinting. Total time: hours. CPM fails this. Problems hide in 5,000-activity schedules. Latency measured in weeks or months. Recovery happens after damage is done.

Process Not People When Problems Surface

When visual systems surface problems immediately, leaders face choices. Blame people or fix processes. Bad leaders blame people. Good leaders blame processes and behaviors. Shaming means blaming the person and who they are. Guilt or proper accountability focuses on what they are doing. Leaders never shame. They correct bad behavior and coach for improvement. And they focus first on process failures. What went wrong structurally that allowed this problem? If you think this way, you are forced to think creatively, solve problems, improve processes, and coach for bad behavior instead of scapegoating. You must believe people are capable of amazing things with proper coaching and mentoring. You must believe there is always a level of support and process needed for people to do their best work.

When Takt boards show a trade falling behind, the question is not: why is this foreman incompetent? The question is: what process failure created this delay? Did make-ready planning miss a constraint? Did procurement delay materials? Did another trade fail to complete their handoff? Did the sequence need adjustment? Focus on process first. If behavior is the issue, address behavior directly. But never assume people failed. Assume the system failed them first. And fix the system. This builds trust. Creates psychological safety. And enables teams to surface problems proactively instead of hiding them out of fear of blame. Visual systems only work when teams trust that surfacing problems leads to solutions instead of punishment.

Why Latency Kills Projects and How to Eliminate It

Latency compounds problems exponentially. A one-day delay today becomes a three-day delay next week becomes a two-week delay next month. Because construction work is interconnected. One trade’s delay cascades to downstream trades. Access conflicts multiply. Coordination failures compound. And small problems metastasize into catastrophes. The only defense is immediate visibility and rapid response. See problems when they are small. Act before they compound. And prevent disasters instead of recovering from them. This requires systems with minimal latency. Not data systems requiring collection, processing, and analysis. Visual systems showing reality immediately at the Gemba.

Eliminate latency by putting decision-making at the Gemba. Not in corporate offices reviewing dashboards. At the jobsite where superintendents and foremen see reality directly. Use visual boards updated daily showing planned versus actual status. Takt boards. Last Planner boards. Scrum boards. Any visual system that makes problems obvious without analysis. Hold coordination meetings at the Gemba. Not in conference rooms. At the location where work happens. Where teams can point to actual conditions instead of describing them abstractly. Empower teams to make decisions within five hours of identifying problems. Not escalate to corporate. Not wait for schedulers to analyze. See problem. Decide solution. Implement. Move on. This requires trust. Autonomy. And systems designed for speed instead of control.

The research is clear. Teams that act within five hours have 42% success rates instead of 26%. Failures drop from 21% to 8%. And the primary difference is latency. How quickly problems get identified, decided upon, and corrected. CPM creates latency by design. Complexity hides problems. Data lag delays identification. Corporate review slows decisions. Visual systems eliminate latency by design. Problems surface immediately. Teams see them at the Gemba. And they act. That is why Takt, Last Planner, and Scrum outperform CPM. Not because they are magical. But because they reduce latency from months to hours. And in construction, hours matter.

The Challenge

Walk onto your project tomorrow and ask: how long does it take us to notice when trades fall behind? If the answer is “when the schedule update shows it next week” or “when dashboards flag it next month,” you have a latency problem. And latency kills projects. Switch to visual systems. Takt boards showing zones and trade flow. Last Planner boards tracking weekly commitments. Scrum boards managing sprint work. Any system that makes problems visible immediately at the Gemba instead of hiding them in data waiting for analysis. Hold coordination meetings at the jobsite. Not in conference rooms. Where teams can see actual conditions. Point to actual work. And make decisions based on reality instead of reports.

Empower superintendents and foremen to act within five hours of identifying problems. Not escalate. Not wait for corporate approval. See problem. Call meeting. Decide solution. Implement. Done. This requires courage. Trusting field teams to make decisions. Giving them authority to adjust plans. And accepting that speed matters more than perfect analysis. Because by the time you perfectly analyze a problem, it has compounded into something ten times harder to fix. Better to act quickly on eighty-percent information than perfectly on two-month-old data. The research proves it. 42% success versus 26%. 8% failure versus 21%. And the difference is latency.

As Toyota teaches: “Go and see for yourself to thoroughly understand the situation.” That is seeing at the Gemba. Not reviewing dashboards. Not analyzing reports. Going to the actual place of work. Seeing reality directly. And acting immediately when problems surface. Because construction rewards teams that reduce latency. That see problems in hours instead of months. That act within five hours instead of two months. So go. See. Act. And watch your success rates climb while your failure rates plummet. Because seeing at the Gemba is not optional. It is essential. On we go.

Frequently Asked Questions

What is the Gemba and why does it matter for construction scheduling?

Gemba is Japanese for “the actual place of work”—the jobsite where work happens. Seeing at the Gemba means making decisions based on direct observation of reality instead of reports filtered through data systems with latency.

What is latency in construction project management?

Latency is the delay between problem occurrence and action. Teams using CPM have weeks or months of latency. Teams using visual systems (Takt, Last Planner, and Scrum) have hours or days enabling faster problem resolution.

What are the project success rates for CPM versus agile methods?

Traditional CPM methods achieve 26% success with 21% failures. Agile methods (Scrum, Last Planner) achieve 42% success with 8% failures. The primary difference is latency in problem identification and resolution.

Why is five hours the threshold for problem resolution?

Research shows teams that identify and begin correcting issues within five hours have dramatically higher success rates. Problems compound exponentially, one-day delays become week-long delays that become catastrophic without rapid response.

What must visual scheduling systems accomplish to reduce latency?

Systems must be visual, bring problems to surface immediately, show clearly what problems are, be easily understood and checked, be actionable and fast, be reliable, and enable immediate action rather than delayed corporate analysis.

If you want to learn more we have:

-Takt Virtual Training: (Click here)
-Check out our Youtube channel for more info: (Click here)
-Listen to the Elevate Construction podcast: (Click here)
-Check out our training programs and certifications: (Click here)
-The Takt Book: (Click here)

Discover Jason’s Expertise:

Meet Jason Schroeder, the driving force behind Elevate Construction IST. As the company’s owner and principal consultant, he’s dedicated to taking construction to new heights. With a wealth of industry experience, he’s crafted the Field Engineer Boot Camp and Superintendent Boot Camp – intensive training programs engineered to cultivate top-tier leaders capable of steering their teams towards success. Jason’s vision? To expand his training initiatives across the nation, empowering construction firms to soar to unprecedented levels of excellence.

On we go

Finding your Why

Posted on March 13, 2026March 13, 2026 by Jason Schroeder

Read 29 min

The Vice President Who Earned $250K But Felt Miserable Every Morning Because He Never Asked Why

There is a vice president at a major construction company earning over $250,000 per year. Corner office. Parking spot with his name on it. Twenty-three years with the firm. Respected by ownership. Envied by peers. And every single morning when his alarm goes off, he feels dread. Not because the work is hard. Not because the hours are long. But because somewhere deep inside, he knows something is wrong. He climbs the ladder his entire career. Checks every box. Earns every promotion. And arrives at the top wondering why it feels empty. His wife notices. Asks if he is happy. He says he is fine. She knows better. His kids see him come home exhausted and irritable. Going through the motions. Providing financially. But absent emotionally. And when someone asks what drives him, what his purpose is, why he does what he does, he has no answer. Just stammers about responsibility and bills and golden handcuffs. Because he spent twenty-three years building a career without ever asking: why am I here? What is my purpose? Does this work align with who I am? And now he is trapped. Not by poverty. Not by lack of options. But by the weight of a life built without purpose. Success without fulfillment. Which is the ultimate failure. Because he achieved everything society said would make him happy. And he is miserable.

Here is what happens when people build lives without identifying their purpose first. A superintendent works seventy-hour weeks. Misses his daughter’s graduation. Skips family dinners. Ignores his health. And tells himself it is temporary. Just this project. Just until we finish. Just until I get promoted. Twenty years later, he looks back and realizes he spent his entire life chasing the next milestone without ever asking why. Why am I doing this? What do I actually want? What brings me fulfillment? And the answers terrify him. Because if he stops long enough to think about it, he realizes the life he built does not align with the person he wanted to be. He wanted to be present for his kids. He wanted to mentor young workers. He wanted to build things that matter. But he spent twenty years being absent, isolated, and building projects he does not remember because he never connected them to purpose. So the work felt empty. The promotions felt hollow. And the success felt like failure.

The real pain is working hard in the wrong direction. A friend with lightning-fast intelligence and massive potential feels stuck. Not because he lacks skills. Not because opportunities are unavailable. But because he does not know his purpose. So every decision becomes guesswork. Should I take this job? Should I stay in this relationship? Should I move to this city? Without purpose as a criterion, every choice is a coin flip. And years pass making random decisions that lead nowhere coherent. Meanwhile others with half his intelligence and a tenth of his talent thrive. Not because they are smarter. But because they know where they are going. They identified their purpose. And they use it as a filter for every decision. Does this job align with my purpose? Does this relationship move me toward my purpose? Does this city enable my purpose? Clear purpose creates clear decisions. And clear decisions create clear direction. While people without purpose drift through life reacting to circumstances instead of creating outcomes.

The failure pattern is predictable and devastating. A business owner builds a successful company. Revenue grows. Employees multiply. Clients are happy. And the owner is miserable. Because he built the company to make money. Not to fulfill purpose. So every day feels like obligation instead of opportunity. Every client feels like burden instead of blessing. And every year that passes, he wonders: is this it? Is this what I am supposed to be doing? When someone asks him about his company’s purpose, he gives the elevator pitch. Services offered. Markets served. Revenue targets. But when pushed deeper—why do you do this? What drives you? What would make this meaningful?—he has no answer. Because he built a business without asking why. And now he runs a machine that produces money but not meaning. Success without fulfillment. The ultimate failure.

I facilitated an executive offsite recently with a fantastic company. Great people. Strong culture. Solid financials. And during the session, I asked the owner: why do you do this? He gave a business answer. I asked again. Why? He gave a market answer. I asked seven more times. By the eighth why, he was ready to punch me. But then something shifted. And he said quietly: to build people and families. Not to deliver services. Not to maximize profit. But to build people and families. And suddenly everything made sense. The way he treats employees. The decisions he makes. The clients he chooses. All driven by purpose he never articulated. Later we tested this with his executive team without telling them what he said. Asked them the same question seven times. And they arrived at the identical answer independently: to build people and families. That is alignment. That is what happens when purpose drives decisions even before it gets articulated. And when you finally name it, everything clicks into place. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

What Purpose Actually Means and Why It Matters

Purpose is not what you do. It is why you do it. You can fulfill purpose through any role. Print shop owner. Wilderness guide. COO. Construction superintendent. The role is just the vehicle. Purpose is the destination. But most people confuse the two. They define themselves by their job title instead of their purpose. I am a project manager. I am a superintendent. I am an engineer. No. You are a person with a purpose who happens to use project management or superintending or engineering as tools to fulfill that purpose. When the role changes, the purpose remains. And when you know your purpose, choosing roles becomes simple. Does this role enable my purpose? Yes or no. Clear criterion. Clear decision.

The “ask why seven times” exercise reveals purpose by stripping away surface answers. Why do you do this work? To make money. Why do you need money? To support my family. Why does supporting your family matter? Because I want them to be secure and happy. Why does their security and happiness matter? Because I want to build strong people who contribute to the world. Why does that matter? Because I find joy in improving lives. Keep asking until you hit something that makes you feel chills or revelation. That visceral response signals you touched something real. Something core. That is your purpose trying to emerge.

But purpose statements require litmus testing. “To improve the lives of others” sounds noble. But it allows misery. You could improve lives while ignoring your family. While destroying your health. While working for people who abuse you. Because technically you are still improving lives. But “to find joy in improving the lives of others” changes everything. Joy becomes criteria. Can I find joy improving lives in this marriage? In this job? In this role? If the answer is no, something is wrong. Either the role is wrong or your approach is wrong. But the purpose statement itself identifies the problem. That is why precision matters. Words matter. The difference between “improve lives” and “find joy improving lives” determines whether you end up fulfilled or miserable while technically achieving your purpose.

Signs You Do Not Know Your Purpose

Watch for these patterns that signal you are building a life without purpose guiding your decisions:

You achieve promotions and raises but feel empty instead of fulfilled because success without purpose creates hollow victories that satisfy ego but not soul
Every major decision feels like guesswork because you have no criteria for choosing between options that all seem equally valid or invalid
You stay in roles or relationships you hate because of golden handcuffs or fear of change rather than clear purpose pulling you toward something better
You work seventy-hour weeks and miss family moments without clear reason why this sacrifice matters or what it is building toward long-term
When people ask what drives you or why you do what you do you give superficial answers about bills and responsibility instead of deeper meaning
You envy others who seem fulfilled in their work even though they earn less money or hold lower titles because they have something you lack

These are not character weaknesses. These are symptoms of building life without purpose. And they get fixed by stopping long enough to ask why seven times and discovering what actually matters underneath the surface obligations and societal expectations.

How to Discover and Use Your Purpose

Start with the “ask why seven times” exercise. Pick something you do. Your job. Your hobby. Your service work. Ask why you do it. Then ask why that matters. Then ask why that matters. Keep drilling down. Push through the irritation. The feeling that this is stupid. The urge to give surface answers. Because purpose lives underneath the layers of obligation, expectation, and habit you built over years. When you hit something that gives you chills or makes you emotional or feels true at a level you cannot explain rationally, stop. You found something real. Write it down.

Test your purpose statement with the litmus test. Ask: if this was my only criterion for making decisions, what would be the consequences? If the consequences include misery, failed relationships, poor health, or unfulfillment, refine the statement. The purpose statement should only allow good outcomes when used as sole criterion. “Improve lives” allows sacrifice of family and self. “Find joy improving lives” does not. The second statement is better because it protects you while serving others. Purpose should never require destroying yourself to achieve. If it does, you have not found purpose yet. Keep refining.

Use purpose as criteria for every major decision. Can I fulfill my purpose in this job? In this marriage? In this city? With these people? If yes, proceed. If no, change something. Either change the situation to align with purpose or leave the situation for one that does. Because every moment spent in situations that prevent you from fulfilling your purpose is wasted. Not just unproductive. Wasted. Life is too short to spend in roles or relationships or circumstances that prevent you from becoming who you are meant to be. Purpose gives you permission to make hard changes. To leave the $250K job that destroys you. To pursue the $80K job that fulfills you. Because fulfillment is worth more than money.

Align everything with your purpose over time. You cannot change everything overnight. Bills exist. Obligations are real. But start moving. If your current job does not align with purpose, begin planning the transition. Network. Build skills. Save money. And move deliberately toward roles that align. If your marriage does not align with purpose, either fix it or leave it. But do not stay in misery indefinitely because fear of change outweighs desire for fulfillment. Every year you spend misaligned is a year you lose. And you only get one life. Make it count by aligning with purpose instead of drifting through obligations.

Why Success without Fulfillment Is Ultimate Failure

Tony Robbins teaches: success without fulfillment is the ultimate failure. And construction proves this constantly. Vice presidents earning $250K who are miserable. General Superintendents running mega projects who are burnt out. Business owners with profitable companies who hate their lives. All successful by society’s measures. All failures by fulfillment measures. Because they climbed ladders leaning against the wrong buildings. They achieved goals they never questioned. And they arrived at destinations wondering why it feels empty.

The dissonance between success and fulfillment comes from misalignment with purpose. When what you do does not align with why you exist, your brain knows. Even if you cannot articulate it. Even if you push it down and tell yourself you should be grateful. The disconnect creates stress. Anxiety. Depression. Emptiness. Because success that does not fulfill purpose feels hollow. Like eating food that has no nutrition. You can consume it. But it does not sustain you. And eventually you starve while appearing well-fed. That is what happens to successful people who are miserable. They achieved everything except what actually matters. Alignment with purpose.

The golden handcuffs trap people in misery because fear of losing money outweighs desire for fulfillment. I earn too much to leave. I have too many obligations. I cannot afford to start over. These are lies people tell themselves to justify staying in situations that destroy them. Because the truth is harder. The truth is: you can leave. You can start over. You can build a life aligned with purpose. But it requires courage. Risk. Uncertainty. And most people choose misery they know over fulfillment they do not. So they stay. Earning money. Hating life. And wondering why success feels like failure.

The Challenge

Stop right now and ask yourself: do I know my purpose? Not your job title. Not your role. Your purpose. Why you exist. What you are here to accomplish. If you cannot answer clearly and immediately, you need to do this work. Because every decision you make without purpose as criterion is a guess. And enough wrong guesses create a life you do not recognize. So ask why seven times. Drill down past the surface obligations and societal expectations until you hit something real. Something that gives you chills. Something that feels true at a level you cannot explain.

Then test it. If this was my only criterion, what would happen? If the answer includes only good outcomes, fulfillment, health, strong relationships, meaningful work—you found it. If the answer includes misery or sacrifice of things that matter, refine it. Keep working until you have a purpose statement that only allows good outcomes. Then use it. Every job opportunity. Every relationship. Every major decision. Ask: does this align with my purpose? Can I fulfill my purpose here? If yes, proceed with full energy. If no, change something. Because life is too short to spend misaligned. You only get one shot. And success without fulfillment is the ultimate failure.

As Tony Robbins teaches: success without fulfillment is the ultimate failure. So stop chasing success defined by other people’s expectations. Stop climbing ladders leaning against wrong buildings. Stop earning money in jobs that destroy your soul. Ask why seven times. Find your purpose. And build a life aligned with it. Because when what you do aligns with why you exist, success and fulfillment happen together. Not one without the other. Both. And that is when life becomes remarkable instead of tolerable. That is when you stop surviving and start thriving. That is when you finally answer the question: why am I here? And the answer pulls you forward instead of leaving you drifting. On we go.

Frequently Asked Questions

What is the “ask why seven times” exercise for finding purpose?

Start with something you do and ask why you do it. Then ask why that matters. Keep drilling down seven times (plus or minus three) until you hit something that gives chills or emotional response signaling you touched something real and core.

How do you test if a purpose statement is correct?

Ask: if this was my only criterion for making decisions, what would be the consequences? If consequences include only good outcomes (fulfillment, health, relationships, meaningful work), you found it. If consequences include misery or sacrifice, refine the statement.

What is the difference between “improve lives” and “find joy improving lives” as purpose?

“Improve lives” allows misery—you could improve lives while ignoring family or destroying health. “Find joy improving lives” requires fulfillment—if you cannot find joy, something is wrong with the role or approach, creating a built-in quality check.

Why do successful people feel miserable despite achievement?

Success without alignment to purpose creates dissonance. The brain knows when what you do does not align with why you exist, creating emptiness even when external measures (money, titles, recognition) signal success.

How do you use purpose to make decisions about jobs and relationships?

Ask: can I fulfill my purpose in this role/marriage/job? If yes, proceed. If no, either change the situation to align with purpose or leave for one that does. Purpose becomes the criterion filtering every major decision.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Relationships with Vendors, Feat. Kenny Schroeder

Posted on March 13, 2026March 13, 2026 by Jason Schroeder

Read 27 min

The Concrete Crew That Waited Ninety Minutes Because the Driver Ate Breakfast Instead of Staying in Sequence

There is a concrete crew placing a slab at a women’s prison. Temperature outside is 138 degrees. No breeze. White tilt panels reflecting heat like an oven. The concrete truck shows up ninety minutes late. Not because of traffic. Not because of mechanical failure. But because the driver stopped for breakfast on the way to the jobsite. And instead of jumping into sequence when he arrived, he parked behind six other trucks and waited his turn. By the time his load reached the pour, the concrete was setting up. The finishers scrambled. Mixed patching material in little jars hanging from their belts. Troweled wet mud while it went off underneath them. And finished a slab that required patches every few feet because one driver prioritized breakfast over service. Meanwhile across town at a different prison jobsite, Service Rock Products delivered 305 yards per hour consistently. Trucks showed up fifteen minutes early. Drivers knew exactly where to go because dispatch had site maps at the batch plant. The truck boss coordinated sequencing. The salesman directed traffic on site. And the quality control specialist ensured every load met specifications before it left the plant. No late trucks. No setting concrete. No patching jars. Just flow. Because one company understood that service is 90% of quality. And the other company treated delivery like checking out at Home Depot. Same industry. Same material. Different mindset. And the gap between them was the difference between crews finishing on time and crews working in 138-degree heat patching concrete that should never have needed patches.

Here is what happens when vendors treat contractors like transaction numbers instead of partners. A superintendent orders twenty-seven hundred yards for a large placement starting at three in the morning. Top-out crew scheduled to arrive at nine. The concrete company confirms the order. Sends trucks. But nobody coordinates sequencing. Nobody communicates with drivers about the pour plan. Nobody positions backup pumps. Nobody ensures slump consistency across loads. So trucks arrive randomly. Some too early. Some too late. Slumps vary wildly. One pump goes down because nobody planned backup. And by nine o’clock when the top-out crew arrives, the placement is only halfway complete. The superintendent is furious. The crew works until two in the afternoon instead of finishing by nine. Overtime costs pile up. Schedule slips. And the concrete company blames weather or traffic or driver availability. Never acknowledging that they treated a critical placement like any other Tuesday delivery instead of planning it like the major operation it was.

The real pain is the assumption that uploading a ticket constitutes service. A concrete plant gets an order. They batch the load. Print the ticket. Send the truck. And assume their job is done. Meanwhile the contractor needs to know: what time will trucks arrive? What is the spacing between loads? Are slumps consistent? Is the mix design verified? Are there backup trucks if one breaks down? Who is the contact if problems arise on site? Without this information, contractors manage chaos instead of flow. They check every ticket manually. Test every slump. Monitor every revolution count. And waste hours doing quality control that the vendor should handle themselves. Because great vendors do not just deliver concrete. They deliver certainty. They own quality. They communicate proactively. And they make the contractor’s job easier instead of harder.

The failure pattern is predictable and entirely preventable. A foreman orders concrete for a foundation pour. The plant confirms delivery for eight in the morning. Eight o’clock arrives. No truck. The foreman calls the plant. “Should be there soon.” Eight-thirty. Still nothing. Another call. “He’s on his way.” Nine o’clock. The truck finally shows up. No explanation. No apology. Just a driver who does not care and a plant that does not track. Meanwhile the crew has been standing idle for an hour. Labor costs pile up. The schedule slips. And the foreman wonders: why do I keep using this company? The answer is usually: because they are the cheapest. And that reveals the problem. Low price without service is expensive. Because the lost productivity, the schedule delays, the coordination chaos, and the quality problems cost far more than the few dollars saved per yard. Great contractors understand this. They pay slightly more for vendors who deliver certainty instead of paying less for vendors who deliver chaos.

Ken Schroeder was a truck boss for Service Rock Products. For decades he coordinated concrete deliveries for major projects. Hensel Phelps. Conco Construction. Cambridge Construction. And his philosophy was simple: “My sole objective here is to make you look good.” Not to deliver concrete. Not to meet minimum specifications. But to make the contractor look good. And that mindset created remarkable outcomes. One placement required 2,700 yards starting at three in the morning. Service Rock coordinated ninety trucks across two batch plants to maintain 305 yards per hour. Three boom pumps with one backup. Every truck timed perfectly. Every slump consistent. And by six o’clock in the morning, the placement was complete. Three hours ahead of schedule. The top-out crew that was supposed to start at nine showed up to find work nearly finished. Not because of heroic effort. But because Service Rock planned the operation like a military logistics campaign and executed flawlessly. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

What Great Vendor Relationships Actually Look Like

Great vendor relationships start with personal connection. Not transactional exchanges. Not arm’s-length negotiations. But actual relationships where vendors and contractors know each other, understand each other’s needs, and work together toward shared success. When Service Rock showed up on Hensel Phelps jobsites, the superintendent walked out and explained: “Here’s what we’re placing. Here’s our pour plan. Here’s our crew schedule. Here’s what we need from you.” And Service Rock responded by communicating that information all the way down to individual drivers. Total participation. Every driver knew the context. The spacing requirements. The timing constraints. And the consequences if they failed. So they did not fail. They showed up fifteen minutes early. Positioned themselves correctly. And executed the plan.

This is not theory. This is how Service Rock operated every day. They posted site maps at the batch plant showing exactly where each driver was going. They had the salesman and truck boss on site directing traffic and solving problems in real-time. They maintained backup trucks for every major placement. And they tested every mix design continuously to ensure seven-day breaks instead of waiting for twenty-one-day results. When inspectors saw Service Rock trucks on site, they relaxed. Because they knew the concrete would meet specifications. The timing would be right. And problems would get solved before they became disasters. That is what service looks like. And it is worth paying for.

How Contractors Build Strong Vendor Relationships

Be hands-on from the start. When Service Rock arrived on jobs, superintendents did not just point to the pour location. They explained the entire operation. Pour plan. Crew timing. Pump locations. Access constraints. Safety requirements. And they treated drivers like partners instead of delivery personnel. This created mutual respect. Drivers understood why timing mattered. Why slump consistency was critical. Why showing up late destroyed flow. And they performed accordingly. Because people perform better when they understand the context instead of just following orders without knowing why.

Visit vendor facilities before awarding contracts. Go inspect the batch plant. Check equipment maintenance. Talk to the batch operator. Meet the truck boss. Evaluate cleanliness and organization. Ask about quality control procedures. Request to see test results. And verify they have hot water systems for winter pours and refrigeration for summer pours. Because facilities tell you everything about how a company operates. Clean organized batch plants with well-maintained equipment and documented quality procedures produce reliable service. Dirty disorganized plants with broken equipment and no testing lab produce chaos. And you can see the difference before you sign a contract if you take time to visit.

Communicate clearly and completely every time you order. Do not just say “I need 500 yards.” Explain the pour plan. How many yards per hour do you need? What pump configuration are you using? What crew schedule are you running? What site access constraints exist? What quality requirements matter most? The more information vendors receive, the better they can serve you. Service Rock succeeded because contractors explained their needs completely. And Service Rock communicated those needs all the way to individual drivers. Creating alignment from customer to crew that eliminated surprises and enabled flow.

Develop personal relationships beyond transactions. Service Rock invited contractors to company picnics. Trained them on slump testing and cylinder preparation. Showed them the batch plant operations. And treated them like family instead of customers. This built loyalty that survived price competition. Because when you have a relationship with people who consistently make you look good, you do not switch vendors to save three dollars per yard. You stay with people you trust. Who deliver certainty? And who solve problems instead of creating them. That is worth paying for.

How Vendors Build Strong Contractor Relationships

Service is 90% of quality. Not just materials. Not just mix designs. But the complete service experience. Showing up on time. Maintaining consistent slumps. Communicating proactively. Solving problems before they escalate. And making the contractor’s job easier instead of harder. Service Rock understood this completely. They showed up fifteen minutes early for every placement. Positioned trucks correctly without being told. Tested slumps before leaving the plant. And had the truck boss on site coordinating sequencing in real-time. Contractors did not have to manage concrete deliveries. They just had to pour. Because Service Rock owned the entire service experience.

Maintain equipment obsessively. Service Rock’s trucks looked better than new vehicles. Even old trucks got stripped, sanded, and repainted regularly. Engines received monthly service. Drums stayed clean. Cabs stayed organized. And when contractors saw clean well-maintained trucks arriving on site, they relaxed. Because equipment condition signals operational philosophy. Companies that maintain equipment also maintain quality systems. Companies with broken dirty trucks also have broken quality systems. And contractors notice the difference immediately.

Implement driver grading systems that create competitive improvement. Service Rock graded every driver monthly. A, B, C, or D based on performance. At first drivers resented it. Then they got competitive. Nobody wanted to be a D driver. So they improved. They showed up on time. Maintained their trucks. Followed site protocols. And delivered exceptional service. Because the grading system created accountability and recognition. Good drivers got preferred jobs. Poor drivers washed trucks and went home. And everyone knew the difference between excellence and mediocrity was performance measured and rewarded.

Test quality continuously and share results proactively. Service Rock ran a testing lab that broke cylinders at seven days instead of waiting for twenty-one or twenty-eight day results. This gave immediate feedback on mix designs. Allowed adjustments before problems escalated. And gave contractors confidence that every load would meet specifications. When contractors asked about strength, Service Rock showed them test data. Not promises. Actual measured results from continuous testing. That builds trust nothing else can match.

Over-communicate and coordinate in real-time. For the 2,700-yard placement, Service Rock coordinated ninety trucks across two plants. The truck boss positioned trucks on site. The salesman directed traffic. The plant manager helped drivers check slumps before leaving. And everything flowed perfectly because everyone communicated constantly. No assumptions. No hoping things work out. Active real-time coordination that prevented problems instead of reacting to them. That is what separates great vendors from mediocre ones. Great vendors coordinate. Mediocre vendors just show up.

Signs Your Vendor Relationship Needs Improvement

Watch for these patterns that signal vendor relationships are destroying instead of enabling your projects:

Trucks arrive late consistently without explanation or apology forcing crews to stand idle burning labor dollars waiting for concrete that should be on time
Slumps vary wildly across loads requiring constant adjustments and creating finishing problems that should never exist with proper quality control at the plant
No vendor representative appears on site for major placements leaving contractors to manage deliveries themselves instead of having expert coordination support
Drivers do not know where to go when they arrive forcing superintendents to direct traffic instead of managing pours because vendors failed to communicate site plans
Quality problems emerge repeatedly without vendor accountability or improvement indicating systemic failures in quality control and testing procedures
Communication happens only when contractors call to complain instead of vendors proactively updating status and solving problems before they escalate

These are not material problems. These are vendor selection problems. And they get fixed by choosing vendors who understand that service is 90% of quality. Then building relationships through clear communication, personal connection, and mutual respect.

The Challenge

Walk onto your next project and evaluate your vendor relationships honestly. Do your concrete suppliers coordinate deliveries like military logistics operations? Or do they just send trucks and hope things work out? Do they test quality continuously and share results proactively? Or do you discover problems when cylinders fail weeks later? Do they show up on site for major placements with truck bosses coordinating flow? Or do you manage chaos alone while vendors collect payment? If vendors are not making your job easier, you have the wrong vendors. Not the cheapest vendors. The wrong vendors.

As Ken Schroeder taught: “My sole objective here is to make you look good.” That is what great vendors do. They coordinate ninety trucks across two plants to deliver 305 yards per hour flawlessly. They show up fifteen minutes early. They maintain equipment obsessively. They test quality continuously. And they communicate proactively. Because service is 90% of quality. And contractors who pay slightly more for vendors who deliver certainty instead of paying less for vendors who deliver chaos understand that reliability is worth the investment. Stop accepting late trucks, inconsistent slumps, and vendors who treat you like transaction numbers. Start demanding service that makes you look good. Build relationships with vendors who understand construction is a team sport. And watch your projects flow instead of fighting because everyone finally understands that great vendor relationships are not optional. They are essential. On we go.

Frequently Asked Questions

How do contractors develop better relationships with ready-mix suppliers?

Be hands-on explaining pour plans completely, visit vendor facilities before awarding contracts to inspect equipment and quality systems, communicate clearly every time you order, and develop personal relationships beyond transactions through connection and mutual respect.

What separates great concrete vendors from mediocre ones?

Service is 90% of quality. Great vendors show up fifteen minutes early, maintain equipment obsessively, test quality continuously, coordinate deliveries in real-time with truck bosses on site, and make contractors’ jobs easier instead of harder.

Why does Service Rock’s driver grading system improve performance?

Monthly grading (A, B, C, D) creates competitive improvement. Nobody wants low grades. Good drivers get preferred jobs. Poor drivers wash trucks and go home. Accountability and recognition drive performance improvements vendors and contractors both benefit from.

Should contractors visit batch plants before selecting concrete suppliers?

Always. Facilities reveal operational philosophy. Clean organized plants with maintained equipment and testing labs produce reliable service. Dirty disorganized plants with broken equipment produce chaos. Visit before you sign contracts to see the difference.

What does “service is 90% of quality” mean for construction vendors?

Quality is not just materials or mix designs but the complete service experience: showing up on time, maintaining consistent slumps, communicating proactively, solving problems before they escalate, and making contractors’ jobs easier through reliable coordinated delivery.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Communication in Construction

Posted on March 13, 2026March 13, 2026 by Jason Schroeder

Read 29 min

The Team That Spent Forty-Five Minutes Frustrated Because the Leader Never Said the Goal

There is a team sitting in a triangle formation playing a card game. Seven people. Each person holds four cards. The rules are simple: cannot talk, cannot look at other players’ cards, can only pass cards forward or backward. Each person has a sticky note and a pen for written communication. The person in front flips over their instruction sheet. It reads: “Win the game by each player getting four-of-a-kind.” Clear goal. Simple objective. But this person assumes everyone else received the same instructions. So they start playing. Passing cards. Writing notes. Asking for specific cards. Meanwhile the people in the back row flip over their instruction sheets. Their sheets say: “Win the game.” That is all. No definition of winning. No explanation of the objective. Just “win the game.” So these people sit confused. They have four random cards. They receive sticky notes requesting cards they do not understand. They pass cards forward and backward without knowing what they are building toward. And forty-five minutes later, they are frustrated, angry, and completely lost. When the facilitator finally stops the game and asks what happened, the person in front says they thought everyone knew the goal. The people in back say they had no idea what they were supposed to do. And suddenly everyone realizes: this is exactly what happens on construction projects. The superintendent knows the plan. Knows the milestones. Knows the owner’s expectations. But assumes everyone else knows too. So trades work in the dark. Frustrated. Confused. And wondering why the superintendent is upset they are not winning a game nobody explained to them.

Here is what happens when leaders assume everyone knows the plan. A superintendent starts a project. Substantial completion is August fifteenth. The owner wants LEED Gold certification. Top priority is maintaining operations in the occupied building during construction. Critical milestone is steel delivery in March to enable summer enclosure. The superintendent knows all of this. It is in the CPM schedule. Buried on page forty-seven of a seventy-six page document nobody reads. And the superintendent assumes this is enough. Trades show up. Start work. And nobody tells them August fifteenth is non-negotiable. Nobody explains LEED requires specific waste management and material documentation. Nobody mentions maintaining operations means noise restrictions and limited access windows. So mechanical schedules work that creates shutdowns. Electrical creates dust that violates clean air requirements. And steel fabrication gets delayed because nobody communicated the critical path sequencing that made March delivery essential. Six months into the project, the superintendent is furious. Trades are not performing. Schedule is slipping. Owner is unhappy. And the superintendent blames trades for not following a plan they never knew existed. When the reality is brutal: you cannot follow a plan you were never told about. The superintendent knew how to win. But never communicated it. So everyone lost.

The real pain is the assumption that sharing a CPM schedule equals communication. A project team creates a detailed CPM schedule. Five thousand activities. Logic tied. Resources loaded. Milestones identified. They upload it to the project website. Send an email announcing its availability. And assume communication is complete. Meanwhile trades open the file. See seventy-six pages of Gantt charts they cannot read. Activity codes they do not recognize. And durations that make no sense based on field reality. So they close the file. Build their own spreadsheets. And coordinate in hallway conversations instead. The official schedule becomes decoration while real coordination happens despite it. Not because of it. And the superintendent wonders why nobody follows the plan. The answer is simple: uploading a document is not communication. Explaining the plan is communication. Repeating the plan is communication. Showing the plan visually in huddles is communication. Answering questions about the plan is communication. But assuming people will read a seventy-six page CPM schedule and extract the critical information they need? That is not communication. That is abdication.

The failure pattern is predictable and entirely preventable. A foreman shows up Monday morning. The superintendent is busy. No morning huddle happened. The foreman checks last week’s notes. Assumes this week is similar. Starts work. By Wednesday, the superintendent realizes the foreman is working in the wrong sequence. Critical path activity got delayed because the foreman prioritized non-critical work. The superintendent confronts the foreman: why are you not following the schedule? The foreman says: I did not know the sequence changed. Nobody told me. The superintendent says: it is in the schedule. The foreman says: I cannot read the schedule. It is too complex. And nobody explained what changed this week. So I used my best judgment based on last week. The superintendent blames the foreman for not checking. The foreman blames the superintendent for not communicating. And the project suffers because communication failed. Not because people lacked skill. Not because the plan was bad. But because the leader assumed everyone knew what was happening without actually telling them.

I facilitate this card game at leadership off sites and boot camps. The pattern is always the same. The person in front knows the goal. The people in back do not. And teams struggle for thirty to seventy-five minutes trying to figure out what winning means while sitting in frustrated silence. Some teams never figure it out. They give up. Declare the game impossible. And quit. Other teams eventually solve it through trial and error. Lots of sticky note communication. Lots of card passing. And eventually someone in back asks the right question: what is the actual goal? Then the person in front explains: everyone needs four-of-a-kind. And suddenly the team coordinates. Shares cards strategically. And wins in minutes. The teams that win fastest? The person in front immediately communicates the goal. Sends sticky notes to everyone: “Get four-of-a-kind. Pass cards to help each other.” And the team wins in ten to fifteen minutes. Same game. Same rules. Different outcome. Because one person chose to communicate instead of assume. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

What Scaled Communication Actually Means

Scaled communication means repeating critical information seven times through multiple channels until everyone on the project knows it without thinking. Not saying it once in an email. Not uploading it to a shared drive. Not assuming people will figure it out. Actively repeating it. In morning huddles. In afternoon foreman meetings. In worker huddles. In weekly coordination meetings. In one-on-one conversations. On visual boards at the project entrance. And in every interaction until the information becomes common knowledge. What does winning look like? Substantial completion August fifteenth. Non-negotiable. Owner’s top priority? LEED Gold certification requiring specific documentation and waste management. Critical constraint? Maintaining building operations during construction with noise and access restrictions. Critical milestone? Steel delivery March first enabling summer enclosure. Repeat this information constantly. Until every trade partner, every foreman, every worker knows it without asking.

The card game teaches this principle perfectly. When the person in front assumes everyone knows the goal, teams fail. When the person in front actively communicates the goal immediately and repeatedly, teams succeed. The difference is not intelligence. Not skill. Not effort. Just communication. And construction projects operate the same way. Superintendents who assume trades know the plan watch projects spiral into chaos. Superintendents who actively communicate the plan repeatedly through multiple channels watch projects flow smoothly. Because people cannot execute plans they do not know. They cannot meet milestones they were never told about. And they cannot satisfy owner expectations nobody explained to them.

Signs Your Project Lacks Scaled Communication

Watch for these patterns that signal communication failure is destroying your project:

Trades arrive Monday morning asking what they should work on because nobody communicated the weekly plan during afternoon foreman huddles Friday
Foremen work on non-critical activities while critical path work sits untouched because nobody explained sequencing priorities or identified what matters most this week
Rework happens because trades did not know owner expectations or conditions of satisfaction that would have prevented mistakes if communicated up front
Coordination conflicts arise because multiple trades thought they had access to the same area because nobody communicated the look-ahead schedule showing sequencing
Trades feel frustrated and confused because they work in the dark without knowing project end dates, milestones, or what winning looks like
Workers ask the same questions repeatedly because answers were given once in an email nobody reads instead of repeated in daily huddles

These are not trade performance problems. These are leadership communication failures. And they get fixed by over-communicating until it feels annoying. Because if you are not slightly annoyed by how often you repeat critical information, you are not communicating enough.

Widen the Circle and Integrate the Team

Widening the circle means looping in other people who can help solve problems instead of operating as a lone wolf. Historically construction incentivized being an island. Working independently. Solving problems alone. But those days are over. Today’s focus is integration and working through the wisdom of teams. The lean concept is: do not waste the genius of the team. Leverage everyone at 100% capacity working together in unity. Great master builders tell supervisors about events not just out of obligation but to seek indispensable counsel. They ask other superintendents on other projects for advice. They stay transparent with owners. They request input from teams. They reach out when they need help. Because they realize strategic advantage and performance review success comes from integration and collaboration. Not isolation. They always widen their circle.

This applies to communication failures. When you realize trades do not know the plan, you do not blame them for not reading the schedule. You widen the circle. Pull them into coordination meetings. Explain the plan visually. Answer questions. Repeat critical information. And keep repeating until everyone knows it. You loop in foremen for afternoon huddles where tomorrow’s work gets planned together. You hold morning worker huddles where the plan gets explained to everyone on site. Not just foremen. Everyone. Because when workers know what they are building and why it matters, they perform differently. They care. They coordinate. They solve problems. And they help you win instead of working confused in the dark wondering what the goal is.

How to Scale Communication on Projects

Start with morning worker huddles. Every person on site gathers for ten to fifteen minutes. The superintendent or foreman explains the plan for the day. What are we building? What are the priorities? What are the safety concerns? What does success look like today? Workers ask questions. Clarification happens. And everyone starts work knowing what they are doing and why it matters. This eliminates the confusion that destroys productivity when workers guess what they should do because nobody told them.

Add afternoon foreman huddles. Foremen meet at three or four o’clock. Plan tomorrow’s work together. Identify handoffs. Coordinate sequences. Discuss constraints. And leave with clarity on what their crews will do tomorrow. This gives them overnight to prepare. Order materials. Coordinate access. And show up ready to execute instead of scrambling reactively in the moment. Then the morning worker huddle communicates that plan to everyone. Creating multiple information transfer points that prevent communication from breaking down between superintendent and workers.

Use visual management boards. At the project entrance, create boards showing: overall project end date, current milestone, this month’s priorities, this week’s critical activities, and owner’s top expectations. Update them weekly. Reference them in huddles. And make them impossible to miss. Because visual information reinforces verbal communication. And repetition through multiple channels drives retention better than single-channel communication ever will.

Repeat critical information seven times minimum. Once is not enough. Twice is not enough. Three times is not enough. The research is clear: people need to hear information seven times through different channels before it becomes retained knowledge. So repeat it. In huddles. In meetings. In one-on-ones. On visual boards. In emails as backup documentation. And in every interaction until it becomes common knowledge that everyone references without thinking. This feels excessive. It feels annoying. And that is how you know you are communicating enough.

Hold weekly coordination meetings with trade partners. Not just foremen. Decision-makers from each trade. Walk through the six-week look-ahead together. Identify handoffs explicitly. Discuss constraints. Remove roadblocks. And ensure everyone knows the sequence, the priorities, and what success looks like. Then those trade partners communicate back to their foremen. Who communicate to their crews. Creating cascading communication that reaches everyone instead of stopping at superintendent level while workers stay in the dark.

Why Teams Win When They Communicate

Teams only win when they communicate. And teams only communicate when they have trust, engage in healthy conflict, commit to goals together, hold each other accountable, and focus on results. This is Patrick Lencioni’s model. And it applies perfectly to construction. Trust enables honest communication. Healthy conflict surfaces problems before they become disasters. Commitment to shared goals aligns everyone toward the same outcome. Accountability ensures follow-through. And results focus keeps everyone oriented toward winning instead of personal agendas. But none of this works without communication. Because you cannot trust someone you never talk to. You cannot engage in healthy conflict if critical information stays hidden. You cannot commit to goals you were never told about. You cannot hold people accountable for plans they do not know. And you cannot achieve results when half the team works in the dark.

The card game proves this. Teams that communicate win quickly. Teams that assume people know the goal struggle for an hour and often quit. Same game. Same people. Same rules. Different communication. Different outcome. And construction works identically. Projects where superintendents actively communicate the plan finish on time with high morale and strong performance. Projects where superintendents assume people know the plan crash land with frustrated trades, missed milestones, and destroyed relationships. The difference is not complexity. Not resources. Not talent. Just communication. And the choice to prioritize it above assumptions.

The Challenge

Walk into your project Monday and ask yourself: do my trades know what winning looks like? Do they know the substantial completion date? Do they know the owner’s top priorities? Do they know this month’s critical milestone? Do they know this week’s sequencing priorities? If the answer is no, you have a communication problem. Not a trade performance problem. A leadership communication problem. And it gets fixed by over-communicating until it feels annoying. Start morning worker huddles tomorrow. Gather everyone on site for ten minutes. Explain the plan. Answer questions. And watch what happens when people finally know what they are building and why it matters.

Add afternoon foreman huddles Friday planning next week’s work. Create visual boards showing critical information at the project entrance. Repeat the substantial completion date, the owner’s priorities, and the current milestone in every meeting until people can recite them without thinking. And stop assuming people know the plan just because you uploaded a CPM schedule they cannot read. Communication is not distribution. Communication is repetition through multiple channels until knowledge becomes common. Like the card game: if the person in front assumes everyone knows the goal, the team fails for forty-five minutes in frustration. If the person in front communicates the goal immediately, the team wins in ten minutes. You are the person in front. Your trades are sitting in the back row. And they are waiting for you to tell them what winning looks like. So tell them. Repeat it. And watch your project transform from chaos to flow because everyone finally knows the plan. On we go.

Frequently Asked Questions

What is the card game that teaches communication principles?

Teams sit in triangle formation with four cards each trying to get four-of-a-kind. Front person knows the goal but people in back do not. Teams struggle for 45+ minutes when front person assumes everyone knows versus winning in 10 minutes when front person communicates immediately.

How many times should critical information be repeated on projects?

Seven times minimum through different channels before it becomes retained knowledge. Once or twice is insufficient. Repeat in huddles, meetings, one-on-ones, visual boards, and every interaction until it becomes common knowledge.

What is scaled communication in construction?

Repeating critical information through multiple channels until everyone knows project end dates, milestones, owner expectations, sequencing priorities, and what winning looks like without having to ask or guess.

Why do morning worker huddles improve project performance?

They eliminate confusion by explaining the daily plan directly to everyone on site instead of relying on foremen to transfer information, creating multiple communication transfer points that prevent breakdowns between superintendent and workers.

What does “widen the circle” mean for construction leaders?

Loop in other people who can help solve problems instead of operating as lone wolves. Great builders seek counsel from supervisors, other superintendents, owners, and teams because strategic advantage comes from integration and collaboration not isolation.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Why Put Your Needs behind Work Needs?

Posted on March 13, 2026March 13, 2026 by Jason Schroeder

Read 27 min

The Superintendent Who Missed His Daughter’s Graduation to Update a CPM Schedule That Changed Three Days Later

There is a superintendent sitting in his truck outside a high school auditorium. Inside, his daughter is graduating. Valedictorian. Full scholarship to MIT. The ceremony started twenty minutes ago. He promised he would be there. Front row. Camera ready. But this morning the project scheduler called. The CPM schedule needs updating. The owner wants a revised critical path analysis. And the superintendent has been on his laptop for three hours inputting actual dates, adjusting logic ties, and running forward and backward passes to generate a new baseline that shows the project finishing two weeks later than last month’s schedule predicted. He finally hits save. Closes the laptop. Walks into the auditorium just as his daughter accepts her diploma. She looks for him in the crowd. Does not see him. Smiles anyway. And keeps walking. Three days later, the owner changes the scope. The schedule gets revised again. All that work becomes obsolete. The superintendent realizes he missed his daughter’s once-in-a-lifetime moment for a schedule update that meant nothing. And he wonders: when did I start prioritizing a company that will replace me tomorrow over the people who will love me forever? This is not time management failure. This is a broken value system. Where companies train people to sacrifice everything for work. And where scheduling systems so ineffective that they require constant updates become excuses for missing life. CPM does not just waste time on projects. It steals moments from families. And it needs to stop.

Here is what happens when construction prioritizes ineffective systems over people. A project team spends twelve weeks building a CPM schedule. Five thousand activities. Logic tied. Critical path identified. Float calculated. Resource loaded. They present it to trades. Nobody understands it. Too complex. Too detailed. Impossible to read. So trades ignore it. Build their own spreadsheets. Track their own sequences. And the official CPM schedule becomes decoration for owner meetings while real coordination happens in hallway conversations and text messages. Six months into the project, the schedule shows substantial completion in eight months. Trades know better. The work cannot happen that fast. But the CPM says eight months. So ownership expectations get set at eight months. And when reality arrives twelve months later, everyone panics. The last four months become a crash landing. Seven twelve-hour days. Mandatory overtime. Families destroyed. Workers burned out. All because the CPM schedule lied from day one. Gave an unrealistic end date. Hid the detail. Created false hope. And nobody had the courage to say: this system does not work. We need something better.

The real pain is the productivity decline construction has suffered since adopting CPM. In 1964, one year before the AGC adopted CPM as the industry standard, construction productivity started declining. From 1964 to 2012, construction productivity decreased 0.32% annually while non-farm industries increased 3.06% annually. The net effect: since 1964, overall US productivity increased 85% while construction productivity decreased 20%. Twenty percent decline. In the only major industry using CPM as its primary scheduling methodology. Meanwhile the Construction Industry Institute found that 50-75% of labor time gets spent on waste with only 8-25% adding value. Compare that to manufacturing: 62% value generation and 26% waste. Construction is the only industry moving backward. Not because workers lack skill. Not because training is inadequate. But because push systems like CPM create variation in supply chains, change milestones daily, increase inventory, waste manpower, and drive costs up while destroying predictability.

The failure pattern is predictable and morally bankrupt. Scheduling consultants defend CPM. Software companies sell CPM tools. Professional schedulers build careers on CPM expertise. Legal teams use CPM for claims analysis. And owners demand CPM schedules in contracts. Every single one of them profits from CPM. So when someone challenges the system, they defend it. Not because it works. But because their paychecks depend on it continuing. Follow the money trail. Show me one CPM defender who does not profit from the system. One consultant who does not bill hours analyzing float trends and variance reports. One software company that does not sell P6 licenses. One legal team that does not use CPM schedules for delay claims. You will not find them. Because everyone defending CPM has financial incentive to keep the broken system alive. While superintendents, workers, and families pay the price through crash landings, mandatory overtime, and destroyed work-life balance.

I have used CPM for over twenty years. I have used Takt planning for fifteen years. I have recovered projects using flow systems to replace failed CPM schedules. And every single time someone calls me to fix a project behind schedule, the first thing I do is create a Takt plan to find the realistic end date. Then we follow that plan. Create flow. Stabilize supply chains. And finish on time. I could make far more money consulting on CPM. Teaching companies how to improve their scheduling departments. Running Acumen Fuse analysis and variance reports. But I will not do it. Because the system is garbage. It hurts people. It destroys families. And I have integrity. I will not profit from a system I know does not work just because companies are willing to pay me to help them use the wrong tool better. That is immoral. And construction deserves better. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Why CPM Fails and Always Will Fail

CPM is overly detailed but just a wild guess. It takes twelve weeks to build. Creates variation in supply chains because milestones change daily. Nobody reads it because it is incomprehensible. And it is the most soloed, non-communicative, ineffective tool construction uses. Over fifty days past substantial completion is the US industry average. Projects never finish on time with CPM. They crash land. Last four months become seven twelve-hour days destroying families while consultants who sold the CPM system profit from analyzing why the schedule failed. The system hides problems. Gives false confidence. And sets unrealistic expectations that doom projects from day one.

Takt planning creates flow. Stabilizes supply chains. Produces realistic durations. And keeps schedules high-level enough that they do not become obsolete when conditions change. CPM produces false precision. Takt produces reliable flow. CPM pushes work based on predetermined dates without regard for readiness. Takt pulls work when conditions allow it to flow. CPM creates chaos in the final months. Takt prevents crash landings by building realistic sequences from the beginning. And yet CPM persists because the people profiting from it refuse to admit it fails. While the people suffering from it lack the power to change it.

The Second Crime: Sacrificing Yourself for Companies That Will Never Care

Beyond CPM failure is a deeper problem. People sacrifice personal health, family time, spiritual needs, and mental sanity for companies that will replace them tomorrow and never think about them again. Field engineers attend boot camp. They complete work goals flawlessly. But they refuse to fill out personal goals and family goals. Why? Because they have been trained to prioritize company needs over personal needs. Every single day. At every moment. Work comes first. Family comes second. Personal health comes third. And spiritual needs get ignored entirely. This is backward. Immoral. And destructive.

The correct order of loyalty is: God, family, yourself, your health, your friends, and then companies last. There is no such thing as being loyal to a company. Companies do not deserve loyalty. They deserve excellent work during the hours you are paid. But they do not deserve your family. Your health. Your sanity. Or your life. You can be replaced. The CFO can be replaced. The project director can be replaced. Everyone is replaceable. So why sacrifice everything for an entity that will never reciprocate? Because you have been trained wrong. And that training needs to stop today.

What You Actually Deserve

You should be spiritually taken care of. Fulfilling church or spiritual commitments. You should be taking care of your body through exercise and proper health. You should have morning and afternoon routines that ground you. You should be able to take your spouse on date night. Attend your kids’ baseball games. Call friends and family. Live a remarkable life. Have Saturdays off except for rare rotation requirements. And you should be able to do all of this while going to work and performing excellently. This is not impossible. This is the baseline. If you cannot do both, you need personal organization training. Clarity on priorities. A functional morning routine. And the courage to set boundaries.

Gary Vaynerchuk says: if one person has done it, anybody can do it. If one person overcame addiction, you can too. If one person climbed that mountain, you can too. If one superintendent with eleven kids and a wife and intense church callings and mega projects can go home on time consistently, you can too. I did it. For years. On complex projects. And if I can do it, you can do it. But first you must believe it is possible. Second, you must decide you deserve it. Third, you must take massive action to get organized. And fourth, you must hold yourself accountable to protect your time the way you protect project schedules.

Excellence Not Perfection

One of the best general superintendents I ever met said: “Excellence, Jason, not perfection. We should never let the execution of perfect things get in the way of doing the right things in an excellent manner.” As builders, we must sort what is not important to focus on excellent execution of what matters. We cannot let paperwork, perfectionism, or unnecessary processes hinder us from doing what we need to do in the field to plan our work. The only exception is safety. Strive for perfection in safety. Perfect execution of policies. Perfect enforcement of site safety. Perfect safety culture. Everything else: excellence, not perfection.

Construction overwhelms anyone who tries to execute everything perfectly. Every T crossed. Ever I dotted. Every piece of paperwork filled out completely. Every task executed at 100%. You would never accomplish anything well. You could work a hundred hours per week and barely finish a portion of what needs doing. Focus on excellence, not perfection. That is how you become most effective. Vince Lombardi said: “Perfection is not attainable, but if we chase perfection, we can catch excellence.” Strive for excellence. Head toward perfection. But do not get bogged down by perfection when you need to focus on what is important.

Example: aligning anchor bolts in footings. You could use a total station to adjust one anchor bolt template by an eighth of an inch while fresh concrete hardens around fifty other unchecked anchor bolts. Or you could transfer lines onto sturdy batter boards, use a vertical laser or plumb bob, and get all fifty anchor bolts checked and placed correctly. Perfection on one means failure on forty-nine. Excellence on all means success on the project. Do not get stuck doing one or two things perfectly when it prevents you from doing everything excellently.

Where Else Are You Sacrificing Yourself?

Everywhere. You do this everywhere. When you are with your kids but checking email. When you are on vacation but taking work calls. When you promise to attend soccer games but cancel because the project needs you. When you skip honeymoons because you are too dedicated to work. When you never take PTO because you think you are irreplaceable. When you work through family vacations. When you miss graduations for schedule updates. When you prioritize chaos at work over clarity in life. This pattern shows up everywhere because you have been trained wrong. And the training must stop.

I cringe when superintendents say they never take vacation. I partially die inside when people say they never took a honeymoon because they were too busy working. I want to scream when I hear people are unhappy and unhealthy at home because they are “dedicated to work.” The person or company that puts you in that situation does not deserve you. If your company puts you in crash landings, forces you to use push systems, or tells you to sacrifice everything to get the job done, they do not deserve you. Because every single job will be like that. You will never have a day in construction where it is not “the busiest time ever.” I used to tell my wife: “I could do this with you. It’s just a busy time right now.” After the seventeenth time, she said: “You know, Jason, it’s always the busiest time. I get it. You’re never going to be here for me.” That woke me up. I decided to take care of my family and myself. And that forced me to get personally organized with clarity, mindset, and morning routines so I could do both and succeed.

The Challenge

Decide today that you deserve better. You deserve spiritual health. Physical health. Mental health. Family time. Personal time. And excellent work performance. You can have all of it. But only if you prioritize correctly. God first. Family second. Yourself third. Friends fourth. Companies last. Never reverse that order. Never sacrifice family for companies that will replace you tomorrow. Never miss graduations for schedule updates that become obsolete three days later. Never work seven twelve-hour days for four months because a CPM schedule lied about the end date.

If you work for a company that demands crash landings, find a better company. If you use CPM schedules that create chaos, demand Takt planning or flow systems that actually work. If you cannot balance work and life, get personal organization training and take massive action. You are good enough to do both. Men must provide. Women must contribute. But nobody must sacrifice everything for employers who care nothing about them. Stop putting work first. Start putting yourself and your family first. And watch what happens. Your work improves because you are healthy and focused. Your family thrives because you are present. And your life becomes remarkable because you finally decided you deserve it. Excellence, not perfection. Flow, not push. Family, not companies. This is the way. On we go.

Frequently Asked Questions

Why does Jason say CPM scheduling is garbage?

CPM takes twelve weeks to build, nobody reads it, it is overly complex, creates variation in supply chains, gives unrealistic end dates, and has correlated with construction productivity declining 20% since 1964 while other industries increased 85%.

What is the productivity data showing about construction since CPM adoption?

From 1964 to 2012, construction productivity decreased 0.32% annually while non-farm industries increased 3.06% annually. Overall US productivity increased 85% since 1964 while construction decreased 20%.

What is the correct order of loyalty in life?

God, family, yourself, your health, your friends, then companies last. There is no such thing as being loyal to a company because companies will replace you tomorrow and never think about you again.

What does “excellence not perfection” mean in construction?

Focus on excellent execution of important things rather than perfect execution of everything. Do not get bogged down perfecting one task when it prevents you from completing fifty tasks excellently.

How can superintendents balance work and family when construction demands are intense?

Get personally organized with clarity on priorities, functional morning routines, and boundary-setting skills. If one superintendent with eleven kids can go home on time consistently on mega projects, anyone can with proper organization.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Addicted to Emails?

Posted on March 13, 2026March 13, 2026 by Jason Schroeder

Read 30 min

The Project Manager Who Missed His Son’s Soccer Game Responding to Emails That Should Have Been Texts

There is a project manager sitting in his truck in the parking lot at six-thirty in the evening. His son’s soccer game started at six. He promised he would be there. But three hours ago, an email chain started. The owner asked about a change order. The superintendent responded. The architect chimed in. The engineer added clarification. And the project manager has been drafting and redrafting responses for three hours. Spell-checking. Running it through Grammarly. Getting multiple sets of eyes on it. Making sure every word is perfect. Because in his mind, this email is critical. It requires precision. It demands professional polish. Meanwhile his son scores a goal. The team celebrates. Parents cheer. And there is an empty spot on the sideline where a father should be standing. At seven-fifteen, the project manager finally hits send on his fourth email in the chain. He looks up. Realizes the time. And drives to the field just as the game is ending. His son sees him. Waves. And the project manager waves back knowing he missed it. Again. Not because of an emergency. Not because the project was on fire. But because he is chemically addicted to email. And he has trained himself to believe that responding to messages is more important than being present for people. This is not time management failure. This is addiction. And it is destroying families while producing zero value for projects.

Here is what happens when office staff become email zombies instead of leaders. A senior project executive visits a jobsite for quarterly reviews. The superintendent prepared a presentation. Quality issues need discussion. Schedule concerns require decisions. And the team gathers in the conference room. The executive opens his laptop. The superintendent starts talking. And within two minutes, the executive’s eyes drift left. An email arrived. He cannot resist. He starts reading. Then responding. The superintendent keeps talking. Nobody is listening. The quality manager tries to show photos of problems. The executive nods without looking. Keeps typing. And after thirty minutes of theater, the meeting ends. No decisions made. No problems solved. No leadership provided. Just one person physically present but mentally absent. Checking email. Responding to messages. Playing digital tennis while real people with real problems sit ignored. The superintendent leaves frustrated. The team wonders why they bothered preparing. And the executive closes his laptop feeling productive because he cleared fifteen emails. Never realizing he just wasted eight people’s time and solved nothing.

The real pain is confusing busyness with productivity. Email creates the illusion of work. Every message received feels like demand. Every response feels like accomplishment. And the brain releases endorphins with each reply. This is chemical addiction. Like Pavlov’s dog hearing a bell and drooling. Except instead of food, the reward is the dopamine hit from clearing an inbox. Project managers convince themselves they are productive because they responded to fifty emails today. But what did those responses actually accomplish? Did they remove roadblocks for trades? Did they solve owner concerns? Did they mentor project engineers? Did they walk the jobsite checking safety and quality? Or did they just keep email chains alive, hitting the ball back and forth like tennis players who never actually move the project forward? Because email is not work. Communication that drives decisions is work. Leadership that removes obstacles is work. Coordination that enables flow is work. But sitting behind a computer playing email ping-pong while ignoring the people who actually build things is waste. Expensive, family-destroying waste.

The failure pattern is predictable. A project engineer sends an email asking about a submittal. The project manager reads it. Thinks about it. Drafts a response. Edits it. Checks grammar. Waits fifteen minutes to make sure it feels right. Sends it. Three hours later, the engineer still does not have an answer because the project manager is still editing. Meanwhile the engineer could have walked to the project manager’s office, asked the question verbally, and gotten an answer in two minutes. But construction has trained people to believe email is professional and conversation is casual. So teams waste hours crafting perfect messages instead of having imperfect conversations that actually solve problems. And when questioned about why they work sixty-hour weeks, project managers point to their inbox. Five hundred emails. I am drowning. I am overwhelmed. When the truth is simpler: you are addicted. And you refuse to use communication tools appropriately.

I watched one project manager get so obsessed with email perfection that he would draft responses, send them to other PMs for review, wait for feedback, edit based on comments, and then send. For a simple question about door hardware. Five people involved. Two hours invested. To answer a question that required one sentence. When I asked why he did this, he said construction requires documentation. Everything must be perfect. Legal liability demands precision. And I said no. You are overthinking your importance. This is not a legal brief. This is not a contract negotiation. This is a door hardware question. Text the answer. Move on. But he could not. Because he had trained himself to believe that email required ceremony. Preparation. Review. Approval. Like burning incense before sending messages to the gods. When reality is brutal: nobody cares about your perfectly crafted email. They care about getting answers quickly so they can keep building. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

What Email Addiction Actually Looks Like

Email addiction is when you cannot resist checking messages the moment they arrive. When notifications control your attention instead of priorities controlling your focus. When you convince yourself that responding to emails is your job instead of understanding that leading people is your job. Project managers, project executives, and directors sit behind computers all day. Eyes glued to Outlook. Responding to messages. Keeping chains alive. And never once asking: is this the highest value use of my time right now? Because email feels productive. It creates tangible evidence of work. Sent messages. Closed threads. Cleared inbox. But what did it accomplish? Did trades get the information they needed to flow? Did the owner get clarity on critical decisions? Did the team remove roadblocks? Or did you just keep yourself busy responding to noise?

The tennis analogy is wrong. One project manager used to say email is like tennis. Message comes in, hit it back into their court. Message returns, hit it back. Keep the ball moving? And this is perhaps the stupidest analogy ever created for construction work. Because tennis is two players hitting a ball back and forth while standing still. Construction is a team moving a ball down the field together toward a goal. Football. Rugby. Soccer. Where everyone coordinates to advance together. When you play email tennis, you are not moving the project forward. You are just hitting messages back and forth while the project sits stalled waiting for actual decisions and leadership. The entire team should be moving the ball together. Not one person sitting in an office hitting reply while everyone else waits.

Two Methods for Breaking Email Addiction

The self-preserving method comes from Tim Ferriss and The Four Hour Work Week. Batch emails twice per day. Check at noon and before going home. Never first thing in the morning. Create an auto-response explaining your email schedule so people respect it. Screen incoming communications. Limit outgoing. Do not let people randomly steal your time with chit-chat. Get to the point. Sidebar conversations that waste time. Avoid meetings without clear objectives. If someone requests a meeting, ask for an email first. Use phone as fallback to vet if the meeting is actually needed. Respond to voicemail by email when possible to train people to be concise. Empower others to make decisions without interrupting you. Force people to define requests before taking your time.

This method works because it protects focus. You are not constantly switching tasks. You handle email in dedicated blocks. And you spend the rest of your time doing actual work. Leading people. Walking jobsites. Removing roadblocks. Mentoring teams. The downside is batching creates delay. Messages sit unanswered for hours. And from a lean perspective, batching is waste. But from a mental focus perspective, batching prevents the constant task-switching that destroys productivity. So there is a trade-off. Batching is less lean but more protective of sustained focus on high-value work.

The one-piece flow method comes from Paul Akers. Answer emails the second they arrive. No batching. No delay. Immediate response. But here is the key: do not respond with lengthy drafted emails. Use the fastest communication method available. Voice message on Voxer. Text. WhatsApp. Group chat. Video message. Phone call. Whatever gets the answer delivered fastest. An email chain that requires twenty-five back-and-forth messages can usually be resolved with one thirty-second voice message or one two-minute phone call. Stop overthinking responses. Stop drafting novels. Stop getting multiple people to review simple answers. Just communicate. Get the answer delivered. Close the loop. Move on.

This method is leaner because it eliminates delay. Messages get answered immediately. Decisions happen faster. Projects flow better. But it only works if you stop taking yourself so seriously. If you still think every email requires professional polish, editing, and approval, you will drown. One-piece flow requires speed. Simplicity. Direct communication. And the willingness to use whatever tool gets the job done fastest instead of forcing everything through Outlook because that is what construction has always done.

Signs You Are Addicted to Email

Watch for these patterns that signal email controls you instead of you controlling email:

You check email the moment you wake up before spending time with family or doing your morning routine that grounds you for the day
Notifications pull your attention away from conversations with people standing in front of you because you cannot resist reading new messages immediately
You spend more time drafting and editing email responses than you spend walking jobsites talking to superintendents and trades solving real problems
You measure your productivity by emails sent rather than by roadblocks removed or decisions made or people developed through mentorship
You work sixty-hour weeks and blame email volume instead of recognizing you waste hours crafting perfect messages that could be texts
People standing in your office wait while you finish responding to messages because you cannot focus on them until your inbox is clear

These are not productivity problems. These are addiction symptoms. And they get fixed by recognizing email is a tool, not a job. Your job is leading people. Removing obstacles. Making decisions. Mentoring teams. Email is simply one method for doing those things. Not the only method. And usually not the best method.

What Office Positions Should Actually Do

Project managers, project executives, and directors are people positions. Not email positions. Leadership positions. Not computer positions. Daily, office staff should scale communication so teams know what is critical for project success. Remove roadblocks. Maintain prompt intimate communication with owners about changes and site conditions. Ask the right questions. Participate in safety. Do not trust safety just to superintendents. Get out of the office. Walk the project. Give a second set of eyes. Be a positive example of values, image, and personal organization you want field builders to follow. Participate in team huddles. Escalate critical issues. Check on team health weekly. Perform safety walks. Verify permits are issued properly. Review financial exposures, contingencies, budgets, status reports, job cost accounting, and projections. Ensure quality of submittals and procurement. Lead and mentor project engineers. Make sure buyout functions well. Visit the jobsite during buyout to fit scopes with current conditions. Participate in scheduling with superintendents. Own it together. Check with owners. Ensure observation and daily correction systems function. Verify projects stay clean, organized, and safe. Set up look-aheads and production tracking systems properly.

Monthly, check in with superintendents one-on-one. Meet with team members individually. Ensure projects run like businesses with good financial health and cash flow. Check change order management. Verify pay applications submit on time. Hold effective meetings. Check 3D coordination. Train teams through weekly lunch-and-learns. Be physically present. Not checking email. Provide remarkable experiences for owners. Go out of your way. Implement lean on projects. Clean trailers. Check jobsites. Fund what workers need. Constantly improve. Stabilize environments. Enforce and care for respect for people and resources.

When you read this list, notice how little of it involves email. Almost none. Because office positions exist to lead people, not respond to messages. If you spend most of your day behind a computer instead of with people, you are not doing your job. Regardless of how many emails you sent. You are addicted. And you need to break that addiction before it destroys your effectiveness and your family.

Why You Deserve Better Than Email Slavery

Think about yourself as a child. Two years old. Four. Eight. Twelve. That cute kid full of life and potential. Would you want that child to waste forty percent of their day on meaningless tasks? Would you want them to miss soccer games and family dinners because they could not stop checking messages? Would you want them to feel stressed and overwhelmed and constantly behind because they trained themselves to be at everyone else’s beck and call? No. You would protect that child. Give them boundaries. Teach them to prioritize what matters. And refuse to let others steal their time and attention. So why do you allow it now? What changed between that child and you today? Nothing. You are still that person. You still deserve protection. Boundaries. Time with family. Focus on what matters. The difference is now you are responsible for protecting yourself. And if you do not, nobody else will.

You cannot give from an empty storehouse. You cannot lead people when you are drowning in email. You cannot mentor teams when you are mentally absent responding to messages. You cannot build others up when you have not taken care of yourself first. This is not selfishness. This is stewardship. You are a resource. A valuable resource. And wasting that resource on email addiction instead of investing it in people is disrespectful. To yourself. To your family. And to everyone counting on you to lead. So stop. Break the addiction. Get control. And use your time the way leaders should: building people who build things.

The Challenge

Walk into your office tomorrow and audit your email behavior honestly. How many hours did you spend yesterday responding to messages? How many of those responses could have been texts or voice messages or phone calls that took thirty seconds instead of thirty minutes? How many times did you check email during conversations with people? How many family moments did you miss because you were drafting perfect responses to questions that deserved quick answers? Write down the numbers. Look at them. And then decide: is this who you want to be? Someone controlled by notifications? Someone who prioritizes inbox zero over family presence? Someone who confuses busyness with productivity?

As Tim Ferriss teaches: batch your email or use one-piece flow, but stop letting it control you. Set boundaries. Check twice per day. Use faster communication tools. Train people to respect your time. And spend the hours you reclaim doing actual leadership work. Walking jobsites. Mentoring teams. Removing roadblocks. Making decisions. Being present for people. Because that is your job. Not email. People. And when you get this right, something remarkable happens. Your projects flow better because you are actually leading instead of hiding behind a computer. Your teams perform better because you are present and engaged instead of mentally absent. And your family gets you back. Not perfect. But present. Which is what they have been asking for all along while you were too busy checking email to notice. You deserve better. They deserve better. So break the addiction and become the leader you were meant to be. On we go.

Frequently Asked Questions

What is the difference between batching emails and one-piece flow for email management?

Batching means checking email twice per day at scheduled times to protect focus blocks for leadership work. One-piece flow means answering emails immediately using the fastest communication method available like voice messages or texts instead of lengthy drafted responses.

Why is email addiction a problem for project managers specifically?

Project managers, executives, and directors hold people positions requiring leadership, mentorship, and jobsite presence. Email addiction keeps them behind computers responding to messages instead of walking projects, removing roadblocks, and developing teams.

What communication tools should replace lengthy email chains?

Use Voxer, WhatsApp, text messages, voice messages, or phone calls for quick answers. Most email chains requiring twenty-five back-and-forth messages can be resolved with one thirty-second voice message or two-minute phone call.

How do you know if you are addicted to email versus just being responsive?

Signs include checking email during conversations with people present, measuring productivity by emails sent rather than problems solved, working sixty-hour weeks blaming volume, and drafting responses that require hours instead of minutes.

What should project managers actually spend their time doing instead of email?

Walking jobsites checking safety and quality, removing roadblocks, mentoring project engineers, coordinating with owners, participating in team huddles, reviewing financials, ensuring schedule flow, training teams, and being physically present leading people.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Psychological Safety, Feat. Kabri & Kaitlin

Posted on March 13, 2026March 13, 2026 by Jason Schroeder

Read 33 min

The Superintendent Who Asked About Suicide and Watched Almost Every Hand Go Up

There is a superintendent on a jobsite with three hundred skilled workers. She decides to hold small group sessions. About ten workers per session. She has never talked about suicide on a jobsite before. And neither has anyone else she knows. But she has seen the statistics. Construction has the second-worst suicide rate in the United States. And she cannot ignore that anymore. So she gathers the first group. Explains why they are meeting. Shows the statistics. Some workers grumble. Why are we talking about this? This is uncomfortable. She does not back down. And then she asks one question: how many of you in this room know somebody who died by suicide? Almost every hand goes up. In every single group. Almost every hand. And suddenly the room changes. Workers start talking. About friends. Coworkers. Family members. About the pressure. The seasonal work. The inability to get therapy because of work hours. The production-driven mentality that promotes foremen who are producers instead of leaders. And the unwillingness to talk about needing help because construction culture says asking for help is weak. Just by saying the word suicide in a jobsite meeting, she normalized it. She did not solve every problem. But she opened the door. And workers who had been carrying these burdens alone realized they were not alone. That is psychological safety. Not the absence of problems. But the freedom to talk about them without fear of judgment or consequence.

Here is what happens when psychological safety does not exist on jobsites. A superintendent runs morning worker huddles. Every day at seven-thirty, workers gather. The superintendent explains the plan. Asks if anyone has questions. And nobody speaks. Because they do not feel safe. The last time someone asked a question, the superintendent made them feel stupid. The last time someone pointed out a problem, they got blamed for it. So workers stay quiet. They nod. They pretend to understand. And then they go to work confused. They make mistakes because they did not understand the plan. They create safety hazards because they were afraid to ask about the sequence. And they resent the superintendent because the huddle felt like a lecture instead of a collaboration. The superintendent wonders why productivity is low. Why quality issues keep appearing. Why workers seem checked out. The answer is simple. Without psychological safety, morning huddles are just theater. An extension of dictatorship instead of an opportunity for connection. Workers bring their bodies but not their minds. And projects suffer.

The real pain is fear preventing total participation. Paul Akers teaches that lean requires continuous improvement and waste elimination. But he emphasizes one concept above all others: total participation. Not just management participating. Not just foremen participating. Everybody. When workers feel psychologically safe, they speak up. They identify problems. They suggest improvements. They ask questions when they do not understand. And teams perform at levels impossible to achieve when people are afraid. But when fear dominates a jobsite, participation drops to maybe twenty percent. Workers show up. Do what they are told. Keep their heads down. And go home. The superintendent gets compliance but not engagement. The project gets bodies but not brains. And everyone loses. Because the workers have solutions. They see waste every day. They know which sequences do not work. But they will not share those insights if they fear being embarrassed or blamed or ignored.

The failure pattern is predictable. A company hires a diverse workforce. Women. Minorities. Different cultures and backgrounds. They check the diversity box. And then they do nothing to create a culture that supports those people. New hires arrive on jobsites where the existing crew makes comments about their gender. Their nationality. Their religion. Foremen assign them the worst tasks without training. Superintendents do not address the harassment because they do not want to make waves. And the new hires either quit or shut down emotionally. They stop participating. They stop suggesting improvements. They become hazards because they are distracted by fear instead of focused on their work. The company wonders why retention is terrible. Why diversity initiatives fail. The answer is brutal. Hiring diverse people without creating psychological safety is worse than not hiring them at all. Because you signal that you do not actually care. You just wanted to check a box. And everyone sees through that.

Kaybree explains it perfectly: “If that person is distracted by something that’s going on outside of work, or they’re distracted by the fear that they’re the apprentice that’s getting comments all day long about their gender or their nationality or their religion, then they are not able to focus on the task. And they are a hazard for the entire crew.” This is not soft skills. This is production strategy. When workers feel safe, they focus on their work. They ask questions when they do not understand. They report problems before they become disasters. And they go home at the end of the day instead of working late to fix mistakes caused by fear. Psychological safety improves schedule performance. It improves budget performance. It improves physical safety. Because people operating at one hundred percent awareness are safer and more productive than people operating at sixty percent because thirty percent of their brain is managing fear. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

What Psychological Safety Actually Means

Psychological safety is freedom from fear to ask questions, make mistakes, and speak up without embarrassment or punishment. It is not creating a perfect environment where everyone is happy all the time. It is creating an environment where people feel free to bring their challenges. Personal or professional. Where they can say they do not understand without being made to feel stupid. Where they can point out problems without being blamed for those problems. And where they can ask for help without being labeled weak. This matters because construction culture has historically been macho. Asking for help is weakness. Admitting you do not know something is failure. Talking about feelings is unacceptable. And that culture kills people.

Construction has the second-worst suicide rate in the United States. Not because construction workers are weaker than other professionals. But because the industry has risk factors other industries do not have. Seasonal work that creates financial instability. Work hours that make accessing therapy impossible. A production-driven mentality that promotes people because they produce instead of because they can lead. And a culture that says if you are struggling, you should handle it alone. Workers feel like burdens on their families and coworkers. They believe people would be better off without them. And they see no way out. Just talking about suicide in a jobsite meeting normalizes it. Saying the words out loud gives people permission to acknowledge the problem exists. And that creates space for people to ask for help before it is too late.

How Fear Destroys Projects

Watch for these patterns that signal psychological safety does not exist on your jobsite:

Workers sit in meetings with arms crossed looking grumpy and refuse to participate or ask questions even when confused about the plan
One-on-one conversations reveal workers understand less than they pretended to understand in group settings because they were afraid to ask
Quality issues and safety incidents happen repeatedly because workers were afraid to point out sequence problems or missing information before execution
New hires quit within months especially women and minorities because harassment goes unaddressed and they feel unwelcome
Foremen promoted for production skills struggle to lead because they were never taught how to support people or manage pressure
Workers maintain personal spreadsheets and trackers because they do not trust the official plan or feel ownership of coordination
Superintendents spend days fighting fires and solving problems workers could have prevented if they felt safe speaking up earlier

These are not people problems. These are culture problems. And they get fixed by managers intentionally creating environments where fear does not dominate.

Words Matter More Than You Think

Language shapes culture. The words managers use either create safety or reinforce fear. Kaybree challenges: “Stop saying committed suicide. It perpetuates a false understanding that the person was weak or chose to do something they shouldn’t have done.” Say died by suicide instead. This sounds small. But it matters. Because committed suicide implies guilt or weakness. Like the person made a selfish choice. But people who die by suicide believe they are burdens. They believe others would be better off without them. They are making what feels like the only choice available. Changing language from committed to died removes judgment. And that opens space for conversation.

The same principle applies everywhere. Stop calling them subcontractors. They are trade partners. Because partners collaborate. Subcontractors get pushed around. Stop saying workers are the problem. The system failed them. Because blaming people destroys psychological safety while diagnosing system failures creates opportunities for improvement. Stop saying someone is being dramatic when they raise concerns. They are identifying risks the superintendent missed. Because dismissing concerns as drama teaches people to stay quiet. And quiet people do not prevent disasters. Managers who want psychological safety must audit their language. What words reinforce fear? What words create space for honesty? And what changes cost nothing but produce massive returns?

Connection before Correction

Before correcting someone, connect with them first. Control your own emotions. Understand their perspective. And then coach instead of criticizing. This comes from parenting research but applies perfectly to construction. When a worker makes a mistake, the superintendent has choices. Option one: publicly criticize them. Make them feel stupid. And ensure they never speak up again. Option two: connect first. Pull them aside. Ask what happened. Listen to their answer. Understand the system failures that set them up for that mistake. And then coach them on how to prevent it next time. The first option destroys psychological safety. The second builds it.

Caitlin models this perfectly: “I say good morning to every single person that I walk by. I want them to be seen. I want them to know that they’re heard. When I ask them how they’re doing, how their weekend was, I’m not asking just to be polite. I actually care.” This is not soft skills. This is leadership. Because workers who feel seen and heard give discretionary effort. They suggest improvements. They identify problems early. And they care about the project’s success because the superintendent cares about them. Connection creates trust. Trust creates participation. And participation creates results impossible to achieve through fear and control.

The Manager’s Responsibility to Get Educated

It costs nothing to be kind and inclusive. But kindness without knowledge creates incomplete safety. Managers must actively educate themselves on what impacts their people. What is racism? What is sexism? How would that person feel? What is trans phobia? What is homophobia? Why should you spend time thinking about this? Because your people belong to these groups. And anything you can do to support your people pays back in their performance. This is not optional. Superintendents scan jobsites for physical risks every morning. They should also scan for psychological risks. Are workers being harassed? Are they distracted by home pressures? Are they afraid to ask questions? And managers cannot identify those risks without understanding what creates them.

Kaybree is blunt: “As a manager, I think it is your first responsibility to understand what impacts your people.” Do not ask someone from a marginalized group to educate you. That is insulting. It puts the burden on them to do your work. Go do your own research. Learn about the experiences of women in construction. Minorities in construction. LGBTQ workers. And people struggling with mental health. Read articles. Watch documentaries. Attend trainings. And then use that knowledge to create environments where everyone can focus on their work instead of managing discrimination or harassment or fear. This is production strategy disguised as empathy. Because diverse teams outperform homogeneous teams when psychological safety exists. And they fail when it does not.

Actionable Steps to Build Psychological Safety

Start with small concrete actions that create immediate impact:

Check your healthcare coverage for Employee Assistance Programs. Many companies offer EAP benefits that provide free counseling and mental health resources. Find out what exists. And then tell your crews those resources are available. Normalize using them. Visit preventconstructionsuicide.com. Download a toolbox talk. And add it to your next safety meeting. Just saying the word suicide in a jobsite context normalizes the conversation. You do not need to become a therapist. You just need to acknowledge the problem exists and resources are available.

Address mental health in your safety plans. Not just physical safety. COVID created anxiety for everyone. Some workers worry about family members. Some face financial pressure. Some struggle with isolation. Ask how people are doing. And mean it. Not just as politeness. Actually care. Listen to their answers. And when someone shares a struggle, connect them with resources instead of dismissing their concerns. Add mental health to your toolbox talks. To your JHAs. To your weekly safety topics. Because distracted workers create physical hazards. And psychological safety prevents distraction.

Put yourself out there for difficult conversations. The first conversation about suicide will be rough. The first time you address harassment will be uncomfortable. But the more you practice these conversations, the easier they become. And this is how culture changes. Not through posters or training videos. Through repeated real conversations where managers demonstrate that it is safe to speak up. Visit pre-apprenticeship programs. Talk to high school students. Show them construction is a viable career path. Especially women and minorities who may not know construction is an option. Because representation matters. When young women see female superintendents, they realize they can do it too. When minorities see diverse crews, they know they will be welcomed.

Create multiple information transfer points. Takt plans for flow. Weekly work planning for commitments. Afternoon foreman huddles for daily coordination. Morning worker huddles where the plan gets communicated directly to everyone on site. Not just foremen. Everyone. Because workers who understand the plan can execute it safely and efficiently. Workers who do not understand but are afraid to ask create chaos. And hold people accountable for connection. Not just production. Ask superintendents: do your workers feel safe asking questions? Do your foremen know how to support people under pressure? Do you address harassment immediately? Because production without safety is failure. And safety includes psychological safety.

How Diverse Teams Win When Safety Exists

Intentional hiring of women and minorities makes sense. Diverse teams outperform homogeneous teams in studies across industries. In hospitals. In tech companies. And in construction. Teams with different perspectives identify problems others miss. They innovate solutions homogeneous groups never consider. And they serve diverse clients better. But intentional hiring fails without cultural support. You cannot hire a woman onto a crew that makes sexist comments and expect her to succeed. You cannot hire a minority worker onto a jobsite where harassment goes unchallenged and expect retention. Intentional hiring requires intentional culture change. And that starts with psychological safety.

Kaybree clarifies: “Intentional hiring will fail if it does not come from an organization that intends to change and support a culture that will support those people. It will fail if it’s communicated as checking a box.” Hire diverse people because they bring value. Different skill sets. Different perspectives. Different experiences that make projects better. Then create environments where those people can thrive. Address harassment immediately. Provide mentorship. Give opportunities for growth. And hold managers accountable for retention not just hiring. Because checking diversity boxes without creating safety is worse than not hiring at all. It signals you do not actually care. And everyone sees through that.

The Challenge

Walk into your next safety meeting and add one topic: mental health. Print a toolbox talk from preventconstructionsuicide.com. Spend ten minutes talking about it. Ask how many people know someone who died by suicide. And watch what happens. You will not solve every problem. But you will normalize the conversation. And that creates space for workers to ask for help before it is too late. Check your language. Are you saying committed suicide or died by suicide? Are you calling them subcontractors or trade partners? Are you blaming people or diagnosing system failures? Make the changes. They cost nothing.

Say good morning to every person you pass. And mean it. Ask how they are doing. Actually listen to the answer. Connect before you correct. Control your emotions before coaching someone on a mistake. Get educated on what impacts your people. Racism. Sexism. Trans phobia. Homophobia. Mental health stigma. Because you cannot create safety for people whose experiences you do not understand. Put yourself out there for difficult conversations. They will be uncomfortable at first. But they get easier. And this is how construction changes. Not through policies. Through repeated real conversations where people feel safe being honest.

As Caitlin said: “Even though we’ve seen the industry grow and change in the last five years and become much more inclusive, we’re still not there. We’re still always going to have to work at this.” So keep working. Keep learning. Keep creating environments where people feel safe asking questions, making mistakes, and bringing their whole selves to work. Because psychological safety is not soft. It is a production strategy that protects people, improves performance, and allows families to see their loved ones come home safe. Challenge yourself. Educate yourself. And lead the change construction desperately needs. On we go.

Frequently Asked Questions

What is psychological safety and why does it matter in construction?

Psychological safety is freedom from fear to ask questions, make mistakes, and speak up without embarrassment or punishment. It matters because fear prevents participation, impacts focus, and creates both physical and psychological hazards on jobsites.

How does lack of psychological safety create physical safety hazards?

Workers distracted by fear or harassment cannot focus fully on tasks, creating hazards for entire crews. Workers afraid to ask questions make mistakes and unsafe decisions because they pretend to understand plans they do not actually understand.

What is the correct way to talk about suicide?

Say “died by suicide” instead of “committed suicide.” The word committed implies guilt or weakness, while died removes judgment and opens space for honest conversation about mental health.

How can superintendents address mental health on jobsites?

Check healthcare coverage for Employee Assistance Programs, visit preventconstructionsuicide.com for toolbox talks, address mental health in safety plans and meetings, and normalize conversations about pressure and struggles workers face.

Why do diverse teams outperform homogeneous teams only when psychological safety exists? Diverse teams bring different perspectives that identify problems and create solutions homogeneous groups miss. But diversity fails without psychological safety because harassment and fear prevent people from contributing their unique insights and experiences.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Applied Scheduling Systems, Feat. Franco w/ IPSUM

Posted on March 13, 2026March 13, 2026 by Jason Schroeder

Read 26 min

The Superintendent Who Clicked Twelve Times to Record One Safety Observation

There is a superintendent who uses project management software that costs his company over one million dollars per year. Every morning he walks the jobsite checking quality and safety. He sees an issue. He pulls out his tablet. And he starts clicking. Click to open the app. Click to navigate to safety. Click to select the checklist. Click to find the right category. Click to add a new item. Click to describe it. Click to assign responsibility. Click to set a deadline. Click to attach a photo. Click to confirm. Click to save. Click to sync. Twelve clicks later, he has logged one observation. And it took three minutes. Meanwhile the worker who caused the issue has moved to a different floor. The foreman who needs to address it is coordinating another trade. And the safety manager who should be notified will not see the report until tomorrow because the system does not send real-time alerts. The superintendent wonders why nobody uses the software. The answer is simple. It was not designed for the field. It was designed by people who have never built anything. And it serves corporate reporting instead of project execution. So workers ignore it. Foremen avoid it. And superintendents suffer through it because they have no choice.

Here is what happens when scheduling and planning tools do not serve the field. A project manager builds a CPM schedule in Primavera P6. It has 5,000 activities. It shows critical path. It calculates float. And it means absolutely nothing to the trades actually building the project. When the superintendent asks a foreman what they are working on this week, the foreman pulls out a spreadsheet. Not the CPM schedule. A personal spreadsheet tracking their crew’s work. Because the CPM schedule is incomprehensible. It shows activities in codes trades do not recognize. It uses durations trades cannot commit to. And it changes every week based on logic ties that have nothing to do with field reality. So trades build their own systems. Superintendents maintain separate trackers. And the official schedule becomes theater for owners while the real coordination happens in hallway conversations and text messages. This is waste. Massive waste. Of time, energy, and money. And it happens because scheduling tools serve executives and owners instead of the people actually building.

The real pain is the gap between master schedules and workers. The old system worked like this: CPM network schedule at the top. Three-week look-ahead in Excel. And workers in the field. Between the master schedule and the workers, there was nothing. Just a superintendent running around pointing fingers and fighting fires. Last Planner System improved this dramatically. Master schedule with milestones. Phase planning using pull planning to reach those milestones. Make-ready look-ahead to align materials, information, and manpower. Weekly work planning where trades commit. And workers executing. But even with Last Planner, there is still a gap. Between the weekly work plan and the worker, teams rely on foremen to transfer information. And when foremen are overwhelmed or communication breaks down, workers show up not knowing what they are supposed to do. This creates chaos. Wasted motion. Rework. And families suffering because projects that should finish on time drag on for months.

The failure pattern is predictable. A company invests in expensive project management software. They train people how to use it. And nobody adopts it. Because the software requires twelve clicks to do what should take one. Because it generates reports executives want instead of information workers need. Because it was designed by developers who never spent a day on a jobsite. So workers create workarounds. Spreadsheets. Text chains. Sticky notes. And the official system becomes a compliance exercise instead of a coordination tool. The company wonders why their million-dollar investment produces zero value. The answer is brutally simple. The software does not serve the people building the project. It serves the people selling the software. And until that changes, construction will keep wasting money on tools nobody uses.

Franco Giacuinto understands this problem completely. He founded Epsom to build scheduling software that actually serves the field. Not corporate reporting. Not owner dashboards. The field. And his philosophy is simple: if software is not as easy to use as YouTube, Facebook, or texting, field workers will not adopt it. So Epsom focuses on making scheduling visual, collaborative, and simple. Master schedules that create flow using Takt planning instead of CPM. Look-ahead that integrate with weekly work planning. Mobile apps where workers can update progress without clicking through endless menus. And analytics that show teams what is actually happening instead of generating useless reports. Franco spent a year on jobsites learning how construction actually works before building anything. And that discipline of listening before building separates companies that create value from companies that create expensive theater.

This matters because construction cannot afford to keep using broken scheduling systems. CPM does not work. Ninety percent of projects finish late. Not because teams are incompetent. But because the scheduling methodology pushes work based on predetermined dates without regard for whether trades are ready. This creates chaos. Superintendents spend their days fighting fires instead of leading. Workers wait for direction instead of executing. And families suffer because projects that should finish in twelve months drag to eighteen while everyone works sixty-hour weeks trying to recover schedules that were broken from day one. The system is immoral. Schedulers and consultants making six figures know CPM does not work. But they keep selling it because it pays their bills. And projects, workers, and families pay the price. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

What Integrated Control Actually Looks Like

The integrated control system starts with Takt planning. Not CPM. Takt creates flow and rhythm across the entire project. It stabilizes supply chains. It staggers work so trades are not stacked on top of each other. And it produces better overall durations than CPM while keeping schedules high-level enough that they do not become obsolete the moment conditions change. From the Takt plan, teams identify milestones. Then they use phase planning to coordinate work between those milestones. For complex coordination where handoffs are unclear, teams use pull planning. For standardized work where sequences are known, teams use simple coordination instead of wasting time on pull planning theater.

Next comes make-ready planning. Six-week look-ahead where teams identify constraints and remove roadblocks before they delay work. This feeds into weekly work planning where trades commit to what they will accomplish. But here is where most systems fail. They stop at the weekly work plan. And they rely on foremen to transfer information to workers. The integrated control system does not stop there. It adds afternoon foreman huddles where foremen plan the next day together. This gives them overnight to prepare. To order materials. To coordinate access. And it creates time for thinking instead of forcing foremen to plan reactively in the moment. Then it adds morning worker huddles where every person on site gathers for ten to fifteen minutes. The superintendent or foreman explains the plan for the day. Workers ask questions. And everyone starts work knowing exactly what they are supposed to do and why it matters.

This creates multiple information transfer points. Takt plan stabilizes supply chains. Phase planning coordinates milestones. Look-ahead remove constraints. Weekly work planning creates commitments. Afternoon foreman huddles coordinate daily execution. Morning worker huddles communicate plans directly to workers. And suddenly the gap between master schedule and worker disappears. Workers are not waiting for direction. Foremen are not scrambling reactively. Superintendents are not fighting fires. And projects finish on time because information flows all the way from strategic planning to tactical execution without breaking down.

Signs Your Scheduling Software Does Not Serve the Field

Watch for these patterns that signal your tools create waste instead of value:

Workers maintain personal trackers and spreadsheets instead of using the official scheduling system because it is too complicated
Superintendents spend hours updating schedules that nobody reads instead of leading coordination and removing constraints
Software requires multiple clicks to perform simple tasks like logging observations or updating progress creating friction instead of flow
Trades cannot understand the master schedule so they coordinate through text messages and hallway conversations instead
Project managers waste time generating reports for executives instead of solving problems that prevent workers from executing
The official schedule shows work starting but trades are not ready so chaos follows because the system pushes instead of pulls

These are not adoption problems. These are design failures. And they get fixed by building tools that serve the people actually building instead of the people buying software licenses.

Why CPM Must Be Dethroned

CPM is a push system. It schedules work based on predetermined dates without regard for whether downstream trades are ready to receive it. This creates chaos. Mechanical gets pushed into a space before electrical finishes rough-in. Drywall gets pushed onto a floor before MEP inspections pass. And finishes get pushed before the building is watertight. The result is rework, delays, and workers standing idle while superintendents scramble to coordinate what should have been coordinated during planning. CPM consultants know this. But they keep selling it because analyzing float trends and generating variance reports pays six figures. And they do not care that their tools destroy projects and harm families. This is immoral. And it must stop.

Franco Giacuinto is blunt about this: “If the industry hasn’t improved and ninety percent of projects are still behind, why do you keep thinking that CPM is the way to go?” The answer is inertia. Companies have always used CPM. Consultants have always sold CPM analysis. And nobody wants to admit that the emperor has no clothes. But the truth is brutal. CPM does not work. It never worked. And the only reason it persists is because the people profiting from it do not suffer the consequences. Superintendents suffer. Workers suffer. Families suffer. While schedulers and consultants cash checks.

The alternative is flow. Takt planning creates predetermined sequences and staggers. But unlike CPM, Takt does not predetermine when work happens months in advance. It predetermines how work flows. What follows what? At what rhythm. And it manages supply chains so materials, information, and manpower arrive when needed instead of whenever procurement feels like delivering. Then pull planning coordinates complex handoffs. Make-ready planning removes constraints. And weekly work planning creates commitments. This is how projects finish on time. Not through CPM analysis. Through flow, coordination, and commitment. And software that serves this workflow instead of fighting it.

What Great Scheduling Software Actually Does

Great scheduling software makes the process easier, not harder. It connects master schedules to look-ahead to weekly work plans without requiring workers to maintain separate trackers. It visualizes information so trades can see what is happening instead of decoding activity codes. It allows mobile updates so workers can report progress without clicking through twelve menus. And it generates analytics that show what actually matters: Are constraints being removed? Are commitments being kept? Is work flowing? Not float trends. Not variance reports. Real metrics that drive real improvement.

Franco explains Epsom’s philosophy: combine scheduling and planning into one vertical instead of treating them as separate worlds. Build high-level schedules that create flow. Generate look-ahead from those schedules automatically. Allow teams to collaborate on weekly work plans within the same tool. Track constraints and commitments. And produce analytics that show executives how projects are actually performing instead of how they should be performing according to baseline schedules nobody believes. This eliminates waste. Engineers stop wasting hours updating spreadsheets and P6 files. Superintendents stop maintaining parallel systems. And trades get information they can actually use to execute instead of reports designed for owner dashboards.

The key is listening. Franco spent a year on jobsites before building anything. He watched how people actually work. He identified where systems break down. And he designed tools that solve those problems instead of forcing field teams to adapt to software designed for executives. This discipline separates companies that create value from companies that create expensive theater. Because software that does not serve the people using it is waste. Regardless of how impressive the features sound in sales presentations.

The Challenge

Walk into your next scheduling meeting and ask one question: does this tool serve the people building the project or the people selling the tool? If your software requires twelve clicks to log one observation, it does not serve the field. If your master schedule is incomprehensible to trades, it does not serve the field. If your system generates reports executives want instead of information workers need, it does not serve the field. And if it does not serve the field, stop using it. Find tools built by people who actually understand construction. Who spent time on jobsites? Who listened before building? And who design for flow instead of compliance.

As Franco said: “Challenge yourself. Don’t think that because it’s been done for years or because the company works that way, that’s the only way of working. Be open to collaborating differently, working differently, changing the process.” CPM has failed for decades. Last Planner improved coordination but still leaves gaps. And integrated control systems that combine Takt planning, make-ready coordination, and worker huddles deliver what construction actually needs: stable projects where people go home on time and families are protected. Stop tolerating broken systems because they are familiar. Start demanding tools that actually work. Because construction deserves better. Workers deserve better. And families counting on paychecks and parents coming home deserve better. Challenge the process. Demand change. And build projects that flow. On we go.

Frequently Asked Questions

Why does CPM scheduling not work for construction projects?

CPM pushes work based on predetermined dates without regard for whether trades are ready, creating chaos when mechanical gets pushed before electrical finishes or finishes start before buildings are watertight.

What is the integrated control system?

Takt planning for flow and milestones, phase planning for coordination, make-ready look-ahead for constraints, weekly work planning for commitments, afternoon foreman huddles for daily coordination, and morning worker huddles communicating plans directly.

Why do workers maintain separate trackers instead of using official scheduling tools?

Official tools are too complicated, require too many clicks for simple tasks, and generate reports for executives instead of providing information workers need to execute their work.

What makes great scheduling software different from typical project management tools?

Great software serves people building the project instead of people buying licenses, making coordination as easy as texting while eliminating waste instead of creating compliance exercises.

How do you close the gap between master schedules and workers?

Create multiple information transfer points from Takt plans through look-ahead, weekly work planning, foreman huddles, and worker huddles so information flows from strategic planning to tactical execution.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Pull Planning

Posted on March 13, 2026March 13, 2026 by Jason Schroeder

Read 29 min

The Team That Debated MEP Coordination for Three Weeks Instead of Pull Planning It in One Day

There is a project with complex MEP rough-in on twelve floors. The superintendent knows coordination is critical. So he schedules meetings. Mechanical shows up with their plan. Plumbing has a different sequence. Electrical wants access first. Fire protection needs specific areas clear. And for three weeks they debate. Who goes first? Who follows whom? What are the handoffs? Nobody commits to anything because nobody trusts anyone else’s timeline. So work stalls. Trades sit idle. The schedule slips. And after three weeks of meetings that produce nothing, the superintendent finally makes unilateral decisions and pushes everyone into the space. Chaos follows. Mechanical blocks plumbing. Electrical cannot access what they need. Fire protection gets delayed. And rework piles up because nobody coordinated handoffs. Meanwhile another project faced the same challenge. But instead of debating, they ran a one-day pull planning session. Every trade showed up. They worked backward from the milestone. They identified handoffs. They committed to durations. And they left with a coordinated sequence everyone agreed to. That project started MEP rough-in immediately while the first project was still debating. Same problem. Different approach. One team used pull planning. The other drowned in meetings. And the gap was not resources or complexity. It was understanding when and how to use the right planning technique.

Here is what happens when teams confuse planning techniques. A superintendent hears about pull planning and thinks it is the same as phase planning. So he schedules a pull planning session for standard repetitive work that everyone already knows how to sequence. Carpenters show up confused. We have been framing walls for twenty years. Why are we putting stickies on a board? Electricians are frustrated. This is wasting time. We know what to do. And the session becomes theater. People go through the motions. They put up stickies. But nobody commits because the work did not need pull planning. It needed simple coordination. Three hours wasted. Trust damaged. And the team leaves thinking pull planning is bureaucratic nonsense. The superintendent wonders why lean techniques do not work. The answer is simple. He used the wrong tool for the job. Pull planning is brilliant for complex coordination where handoffs are unclear. It is wasteful for standardized work everyone already understands. And teams that do not know the difference burn credibility trying techniques that do not fit the problem.

The real pain is the lost coordination. Pull planning done correctly forces trades to identify handoffs explicitly. Mechanical commits: we need structural complete, sprinkler drops installed, and electrical conduit roughed in before we can hang duct. Plumbing commits: we need walls framed and mechanical overhead complete before we can run drain lines. Electrical commits: we need structural open and mechanical coordination complete before we can pull wire. Every handoff gets documented. Every constraint gets addressed. And when someone says they need something, the responsible party either commits to providing it or flags that they cannot. This creates clarity. Everyone knows what they are giving and what they are receiving. And when work starts, it flows because handoffs were negotiated up front instead of discovered mid-execution.

The failure pattern is predictable. A team hears about pull planning at a conference. It sounds great. Collaboration. Commitment. Visual management. So they schedule a session. But they skip preparation. Nobody does homework. Nobody understands the rules. And when people show up, the facilitator tries to explain pull planning while simultaneously running the session. Chaos follows. People do not understand the backward pass. They put up activities in random order. Nobody identifies constraints. Handoffs get missed. And after four hours, the team has a wall full of stickies that mean nothing because nobody committed to anything. The facilitator wonders why pull planning failed. It did not fail. The preparation failed. Pull planning requires homework, facilitation, and trust. Without those elements, it is just expensive theater that wastes time and burns credibility.

I learned pull planning at the cancer center with Last Planner System. Then at DPR on the Bioscience Research Laboratory. And I have done it backwards from milestones, forward, on physical boards, in Excel, in vPlanner, in Smartsheet, with stickies, dry erase, slats, cards, and laminated cards. I have run sessions in person and virtually during COVID. And here is what I know. Pull planning works brilliantly when you need it. And it wastes time when you do not. The key is knowing when each planning technique fits. Master schedules with milestones work best as Takt plans because Takt manages flow and staggers. Phase planning between milestones can use pull planning when coordination is complex and handoffs are unclear. Weekly work plans and daily plans use make-ready and constraint removal. And you choose the technique that fits the problem. Not the technique that sounds impressive.

This matters because construction cannot afford to waste time on planning theater. Projects need real coordination. Real commitments. Real handoffs. And pull planning delivers that when used correctly. But when teams confuse techniques or skip preparation, they get theater instead of coordination. Trades sitting in rooms putting stickies on walls without understanding why. Leaders facilitating sessions without preparation. And projects that leave with pretty boards but no actual commitments. This destroys credibility for lean methods. Because when pull planning fails due to poor execution, teams conclude that lean does not work. When the truth is simpler. The tool was either wrong for the job or implemented poorly. And both problems are fixable. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

What Pull Planning Actually Is

Pull planning is a technique for phase planning where trades work backward from a milestone identifying handoffs and committing to durations. It is not the same as phase planning. Phase planning is what you do. Planning phases of work up to milestones. Pull planning is how you do it when coordination is complex. You can phase plan with flow using Takt. You can phase plan with pull planning when handoffs are unclear. You can phase plan with traditional methods. The technique changes based on the problem. But the goal remains constant: plan the phase between milestones so work flows without delays.

The key to pull planning is working backward. Start with the milestone on the right. What is the last activity before we reach this milestone? Mechanical says: final connections and testing. What do you need before you can do that? We need all equipment installed, all duct hung, all controls wired. Who provides that? Our crew handles equipment and duct. Electrical handles controls. So electrical puts up a sticky: wire mechanical controls. What do you need before you can do that? We need mechanical equipment locations finalized and conduit roughed in. Who provides that? Mechanical provides locations. We rough our own conduit. And the backward pass continues. Each activity identifies what it needs. Each need becomes a predecessor activity. And the chain builds backward until you reach the phase start.

David Amstot and Dan Fauchier explain in Lean Project Delivery: “It is far better to discover the issues in planning than during work execution.” That is the power of the backward pass. When mechanical says we need sprinkler drops installed before we can hang duct, and fire protection says we cannot install drops until structure is complete, and structure says we will not be complete for three more weeks, you discover the problem now. On stickies. Where fixing it costs nothing. Instead of discovering it in the field when mechanical shows up ready to hang duct and realizes sprinkler drops are missing. Now the problem costs money and schedule. Pull planning shifts problem discovery left into planning where solutions are cheap.

How to Run Pull Planning Correctly

Preparation is everything. Before the session, every participant must do homework. Use a pull planning worksheet that asks: What are your major activities for this phase? What is the approximate duration of each activity? What do you need before each activity can start? Who provides what you need? Participants fill this out before the session. They think through their workflow. They identify constraints. And they show up ready to negotiate instead of discovering their needs live during the session. This cuts session time in half and doubles quality because people have already thought through their sequences.

Setup requires clear rules. Choose your medium: physical board with stickies, Bluebeam session, Concept Board, or vPlanner. Create swim lanes. Common options include geographical lanes showing different floors or areas, discipline lanes showing each trade, or package lanes showing design or procurement packages. Assign colors to each discipline. Mechanical gets blue. Plumbing gets green. Electrical gets yellow. Fire protection gets red. And create a milestone card on the right side of the board showing the phase end date and conditions of satisfaction. Everything works backward from this milestone.

The backward pass follows specific steps. Start with the milestone. Ask: what is the last activity before we reach this milestone? The responsible party creates a sticky with: activity name, crew size, duration in days, and ID number. Then ask: what do you need before this activity can start? List constraints on the sticky. Then ask: who provides what you need? That party creates predecessor stickies. Continue backward until the phase start. Every sticky must have: organization doing the work, activity description, duration, ID number linking to downstream activities it enables, and constraints that must be resolved before work starts. Activities longer than ten days get broken into smaller subtasks. This creates accountability and enables flow.

After the backward pass comes the forward pass. Work left to right verifying logical sequence. Check for opportunities to compress schedule by reallocating resources to critical path activities. Verify handoffs are clear and achievable. And confirm everyone commits to their durations assuming they receive what they need. This is where trust matters. People must believe others will deliver what they promise. Without trust, commitments are hollow. So if trust is low, take time to build it before running pull planning. Because pull planning without trust produces pretty boards but no actual coordination.

Signs You Need Pull Planning vs Other Techniques

Use pull planning when coordination is complex and handoffs between multiple disciplines are unclear:

Major MEP rough-in on complex buildings where mechanical, plumbing, electrical, and fire protection must coordinate sequences tightly
Design phases where architects, engineers, and consultants must hand off deliverables in specific sequences to meet milestones
Site logistics on tight urban sites where multiple trades share limited laydown and access requiring precise sequencing
Complex architectural finishes where multiple specialty trades must coordinate in specific sequences to avoid rework
MRI or clean room installations where sequencing and contamination control require extremely tight coordination between trades
Any work where asking “what do you need before you can start” produces answers that require negotiation between multiple parties

Do not use pull planning for standardized repetitive work where everyone already knows the sequence and handoffs are clear. Framing standard floors does not need pull planning. The sequence is known. Use simple coordination instead.

Common Pull Planning Mistakes That Kill Results

Watch for these patterns that turn pull planning into wasteful theater instead of productive coordination:

Skipping homework so participants show up unprepared and discover their workflow live during the session wasting hours
Facilitating sessions without clear rules so people put activities in random order instead of working backward systematically
Using pull planning for simple work that does not need it and burning credibility when people see it as bureaucracy
Creating beautiful boards but never using them afterward so commitments evaporate and coordination fails anyway
Running sessions without trust so commitments are hollow and people do not actually believe others will deliver
Confusing pull planning with phase planning and thinking they are the same thing instead of understanding pull planning is one technique for phase planning

These mistakes are fixable. Send homework templates before sessions. Train facilitators on the backward pass. Use pull planning only when coordination complexity justifies it. Hold teams accountable to use the plans they create. Build trust before running sessions. And understand that pull planning is a tool in the toolbox, not the only way to plan.

The Virtual Pull Planning Method

Virtual pull planning works when setup is correct. Create a shared digital workspace: Bluebeam session, Concept Board, or vPlanner. Send pull planning worksheets before the session asking participants to list activities, durations, and needs. Set up swim lanes showing disciplines, areas, or packages. Create a color legend. And establish ground rules: work backward from the milestone, identify constraints explicitly, commit to durations assuming needs are met, and negotiate handoffs until everyone agrees.

During the session, start with the milestone. Have the final trade create their last activity. Ask what they need. Have responsible parties create predecessor activities. Continue backward systematically. Use ID numbers linking activities so you can track which predecessors enable which downstream work. And after the backward pass, run the forward pass left to right checking logic and identifying schedule compression opportunities. Then export the plan into your scheduling tool or use it directly for make-ready planning.

The advantage of virtual pull planning is documentation. Physical boards with stickies disappear. Virtual boards persist. You can update them. Share them. And reference them during execution. The disadvantage is engagement. People zone out on video calls. So facilitate actively. Call on people. Ask questions. Keep energy high. And limit sessions to three hours maximum. Brains cannot handle longer virtual coordination sessions productively.

When to Flow, Pull, or Push

The hierarchy is simple: flow where you can, pull when you cannot, and push when you must. Flow is best. Takt planning creates predetermined sequences and staggers that manage supply chains and enable continuous workflow. Use flow for standardized repetitive work where the sequence is known and stable. Pull is second best. Use pull planning for complex coordination where handoffs are unclear and need negotiation. Pull creates commitments that enable flow once sequences are established. Push is last resort. CPM schedules that push work based on predetermined dates without regard for downstream readiness create chaos. Use push only when flow and pull are impossible.

Most projects need all three. Master schedules work best as Takt plans managing flow and milestones. Phase planning between milestones uses pull planning when coordination is complex. Weekly work plans use make-ready and constraint removal. Daily plans use huddles and real-time coordination. And you choose the right tool for each level. Not the tool that sounds impressive. The tool that fits the problem. That is how championship teams plan. They know when each technique works. And they use techniques appropriately instead of forcing every problem into one solution.

The Challenge

Walk into your next coordination challenge and ask: does this need pull planning? If handoffs are complex and unclear, schedule a session. Send homework worksheets asking participants to identify activities, durations, and needs. Set up the board with swim lanes and color coding. Facilitate the backward pass systematically working from milestone to phase start. Run the forward pass checking logic. And then use the plan. Hold people accountable to commitments. Update it when conditions change. And reference it during execution. Because pull planning only works if you actually use what you create.

As Amstot and Fauchier said, “It is far better to discover the issues in planning than during work execution.” So discover them. Run pull planning when you need it. Skip it when you do not. And remember the hierarchy: flow where you can, pull when you cannot, and push when you must. Because construction rewards teams that choose the right tool for the job. Not teams that force every problem into one technique regardless of fit. Know your tools. Use them appropriately. And build projects that flow instead of fighting. On we go.

Frequently Asked Questions

What is the difference between pull planning and phase planning?

Phase planning is planning work between milestones. Pull planning is one technique for doing phase planning when coordination is complex and handoffs need negotiation between multiple parties.

When should you use pull planning vs Takt planning?

Use Takt for standardized repetitive work where sequences are known and stable. Use pull planning for complex coordination where handoffs are unclear and need negotiation.

How does the backward pass work in pull planning?

Start with the milestone, identify the last activity, ask what it needs, have responsible parties create predecessor activities, and continue backward systematically until reaching the phase start.

What information goes on each pull planning sticky or tag?

Organization doing the work, activity description, crew size, duration in days, ID number linking to downstream activities, and constraints that must be resolved before starting.

Why do pull planning sessions fail?

Most failures come from skipping homework preparation, facilitating without clear rules, using pull planning for work that does not need it, or creating plans that never get used afterward.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Fail Forward Faster

Posted on March 13, 2026March 13, 2026 by Jason Schroeder

Read 28 min

The Team That Debated for Three Weeks What Could Have Been Tested in Three Days

There is a project team deciding where to locate temporary bathrooms. The superintendent suggests one location. The project manager thinks another spot is better. The foreman has a third opinion. And for three weeks they debate. They draw diagrams. They run scenarios. They discuss traffic patterns and worker convenience and material delivery conflicts. And nobody makes a decision because nobody wants to be wrong. So the bathrooms do not get ordered. Workers use facilities two buildings away. Productivity drops. Morale tanks. And after three weeks of endless discussion, they finally pick a location. It works fine. But it could have been tested in three days. They could have placed temporary fencing, walked the routes, asked workers for feedback, and made the decision in seventy-two hours. Instead they spent three weeks paralyzed by fear of failure. Meanwhile another project tested three bathroom locations in one week, picked the best one, and moved on. Same problem. Different approach. One team failed forward fast. The other team drowned in analysis paralysis. And the difference was not intelligence or resources. It was willingness to test, learn, and adapt instead of debating endlessly hoping for perfect certainty that never comes.

Here is what happens when teams fear failure more than they value speed. A superintendent sees a forming problem. The drawings show a conflict. He knows it needs to be resolved. But instead of gathering the team and making a decision, he waits. He emails engineering. He calls the architect. He schedules a meeting for next week. And while he waits for perfect information, the forming continues. By the time the decision finally happens, the conflict is built into the structure. Now it requires expensive rework instead of a simple adjustment. The delay cost ten times more than making the wrong decision would have. Because even if the superintendent had guessed wrong initially, catching it during forming would have been cheap. But waiting for certainty meant the mistake got locked in concrete. This happens on every project. Teams delay decisions hoping for more information. But construction does not wait. Work continues. And delays turn small problems into expensive disasters.

The real pain is the opportunity cost. Every day spent debating is a day not spent building. Every meeting spent rehashing the same options is coordination that did not happen. Every decision delayed because nobody wants to be wrong is progress lost forever. And this compounds. One delayed decision creates bottlenecks. Bottlenecks create more delays. And suddenly the entire schedule slips because the team was too afraid to fail forward fast. This does not just affect timelines. It affects people. Workers standing idle waiting for decisions get frustrated. Foremen trying to coordinate without clarity burn out. And families suffer because projects that should finish in twelve months drag to eighteen because teams spent six months debating instead of testing.

The failure pattern is predictable. A team faces a decision. Should we use this hoist location or that one? Should we stage materials here or there? Should we pour this concrete now or wait for better weather? And instead of testing the decision quickly, they debate endlessly. They cover the same ground ten times. They second-guess every option. And nobody commits because committing means accepting responsibility if it goes wrong. So they stay in analysis paralysis. Hoping that if they debate long enough, perfect certainty will emerge. But it never does. Construction is full of variables that cannot be predicted. Weather changes. Deliveries get delayed. Trades run behind. And teams that wait for perfect information before acting never act at all. The system failed them by never teaching that speed matters more than perfection. And that testing beats debating every single time.

I run a training exercise called opposing lines. Two teams face each other in a grid. Everyone must move to the opposite end. But you can only move forward or jump around someone facing you. Not around teammates. And if two people from the same team end up side by side ahead of their start position, the game resets. Kids solve this in ten minutes. They fail fast. They try something. It breaks. They reset and try again. Adults take forty minutes. Because they overthink it. They strategize. They debate. They second-guess. And I have to go into drill instructor mode yelling at them to just try something and learn from failure instead of standing there brain-fogging themselves into paralysis. The lesson is brutal but necessary. Teams that fail forward fast win. Teams that debate endlessly lose. And the gap between success and failure is not intelligence. It is willingness to act, learn, and adapt.

This matters because construction cannot afford paralysis. Projects have deadlines. Budgets have limits. And teams that spend weeks debating what could be tested in days lose to teams that move fast, fail safely, and adapt quickly. This is not about reckless decision-making. This is about understanding when speed matters more than certainty. And on most construction decisions, speed wins. Because the cost of being wrong is lower than the cost of delay. If you test a bathroom location and it does not work, you move it. Cost: minimal. Time: days. But if you debate for three weeks, you lose three weeks of productivity that you can never recover. The teams that understand this principle finish projects on time under budget with high morale. The teams that fear failure finish late over budget with burned out workers. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

When to Fail Forward Fast

Here is where failing forward fast creates massive value. Mockups. Build it. See if it works. Adjust. Do not debate for weeks whether the mockup will be perfect. Build it imperfectly and learn. Job hazard analyses. Brainstorm risks as a team. Write them down. Revise them. Do not wait for perfect safety plans. Draft them and improve through feedback. Takt plans. Put the schedule on one sheet of paper. Make it visible. Get input from multiple people. Iterate quickly. Do not lock yourself in a room for weeks trying to perfect it. Draft schedules and budgets. Get them out to the team early. Even if they are rough. Because rough drafts invite collaboration. Perfect drafts invite silence. And collaboration catches problems that perfection hides.

Preconstruction is where fail forward fast pays the biggest dividends. Test layouts. Try different logistics plans. Model coordination conflicts. And do it all on paper where mistakes are cheap. This is safe failure. You are not pouring concrete. You are testing ideas. And ideas that fail on paper save disasters in the field. Too many teams treat preconstruction like it needs to be perfect. So they delay. They overthink. They polish plans that should be tested rough. And they lose the opportunity to fail forward fast when failure costs nothing. Then they get to the field and discover problems they could have caught with quick tests during planning. Now failure costs thousands. This is backwards. Fail fast during planning when it is safe. Execute confidently in the field because you already tested everything.

But here is the critical disclaimer. Do not fail with safety. Do not fail with high-risk items. Fail on paper. Fail in planning. Fail in draft form. Fail in collaboration. Fail in meetings. Do not fail by pouring bad concrete. Do not fail by installing unsafe scaffolding. Do not fail by skipping fall protection. The whole point of failing forward fast is catching problems before they become disasters. So you fail in lift drawings. You fail in forming plans. You fail in coordination reviews. And by the time you pour concrete, you have already caught every mistake on paper where fixing it costs nothing. Teams that confuse fail forward fast with reckless execution miss the point entirely. This is about speed in planning so you can have confidence in execution.

The Risk Profile Framework for Decisions

Research shows that fast decisions are not always better than slow decisions. And slow decisions are not always better than fast decisions. What matters is matching decision speed to risk profile. Here is how it works. Every decision has a window. At the beginning of that window, you can debate safely. Gather input. Consider options. But at some point, the risk profile changes. The cost of waiting exceeds the cost of being wrong. And when that happens, you must decide immediately. The mistake most teams make is missing when the risk profile changes. So they keep debating long after delay became more expensive than error.

Example. A wall was formed incorrectly. You can ask engineering to redesign it. Or you can tear it out and rebuild it right. At the beginning, you have time to explore both options. But at some point, the schedule impact of waiting makes tearing it out the obvious choice. Even if engineering could fix it, the delay costs more than the rework. That is when the risk profile changed. And teams that miss that moment lose massive value. Because they keep debating when they should be acting. The framework is simple. Take the time to make the decision slowly up until the point when your risk profile changes and it becomes riskier to wait any longer. Then decide immediately based on the best information available.

Jim Collins teaches that team unity after decisions matters more than perfect consensus before decisions. Meaning you can have two or three dissenting votes. People who preferred a different option. But if everyone leaves the meeting violently and radically willing to support the decision even though it was not their first choice, the team will succeed. If people leave the meeting quietly resenting the decision and planning to undermine it, the team will fail. So the goal is not unanimous agreement before the decision. The goal is unanimous commitment after the decision. And leaders must check for this. Before you leave the meeting, ask: Can everyone support this decision even if it was not your first choice? If the answer is yes, execute with confidence. If the answer is no, you have people who need to select themselves off the bus. Because teams cannot succeed when members sabotage decisions they did not vote for.

Signs You Are Stuck in Analysis Paralysis

Watch for these patterns that signal your team fears failure more than they value speed:

Decisions that should take days stretch into weeks because nobody wants to commit without perfect information
The same topics get rehashed in multiple meetings with no progress toward resolution or action
Draft plans never get released because teams keep polishing instead of testing and iterating
Workers sit idle waiting for decisions while leaders debate endlessly in conference rooms
Small problems become expensive disasters because delays allowed them to get built into the work
Team members second-guess decisions after they are made instead of unifying to execute them

These are not signs of thorough planning. These are signs of paralysis. And they get fixed by building cultures that value speed and testing over perfection and certainty.

The Culver’s vs In-N-Out Lesson

Here is a perfect analogy for how batching creates waste while flow creates value. Culver’s drive-through works like this. You order at the speaker. You pay at the window. Then they tell you to pull forward and someone walks your food out later. This looks fast. The line moves quickly. But it is theater. Because while you are sitting in the parking lot waiting, someone is walking in and out bringing food, forgetting napkins, going back for sauce. The process is detached. And detaching order from payment from delivery adds massive waste. Extra walking. Extra motion. Defects. Over-processing. And by the time you get your food, it is cold. Because the system optimized for the appearance of speed instead of actual throughput.

In-N-Out works differently. You order. You pay. You get your food. All at the same window. One piece flow. The line looks longer. But that is the true rate of throughput. And when you get your food, it is warm. Because the process stayed connected. This is the difference between batching and flow. Culver’s batches. Take orders fast. Process payments fast. Deliver food slow. In-N-Out flows. Complete each transaction fully before starting the next. And flow wins every time. Because disconnecting steps creates waste that batching can never eliminate.

Construction makes the Culver’s mistake constantly. Go frame this area fast. Come back later to finish it. This creates waste. Workers travel back and forth. They forget materials. They cannot complete tasks efficiently because the process is detached. The better approach is the In-N-Out method. Plan first. Gather everything needed. Complete the work fully before moving to the next area. One piece flow. Finish as you go. This looks slower at first. But it eliminates the waste of returning to incomplete work. And it produces warm food instead of cold food. Meaning when workers finish, it is actually done. Not partially done waiting for someone to walk back and forth fixing defects.

The Challenge

General George Patton said: “A good plan violently executed today is better than a perfect plan next week.” That is the challenge. Stop waiting for perfect certainty. Start testing imperfect plans. Because construction rewards speed more than perfection. And teams that fail forward fast beat teams that debate endlessly every single time. So walk into your next decision and ask yourself: Has the risk profile changed? Is waiting now more expensive than being wrong? If the answer is yes, decide immediately. Get diverse opinions. Have healthy conflict. Make the decision clear. And then unify. Even if some people preferred different options, everyone must leave committed to executing violently.

Build mockups quickly. Draft JHAs and iterate. Release rough Takt plans and improve them through collaboration. Test logistics in preconstruction when mistakes cost nothing. And fail forward fast on paper so you can execute confidently in the field. Because the teams that win are not the teams that never make mistakes. They are the teams that make mistakes quickly, learn from them cheaply, and adapt faster than everyone else. Stop debating bathroom locations for three weeks. Test them in three days. Stop polishing plans that should be tested rough. Stop second-guessing decisions after they are made. And stop letting fear of failure kill momentum.

As the principle states: Master builders are always flexible and nimble. Make decisions slowly with the consensus of the team but act quickly when a decision is made. No plan will long sustain engagement with the enemy. So build alternatives. Stay adaptive. And move fast. Because in construction, a good plan violently executed today beats a perfect plan next week. Every single time. On we go.

Frequently Asked Questions

What does fail forward fast mean in construction?

Test decisions quickly in safe ways like mockups, draft plans, and preconstruction coordination where mistakes are cheap instead of debating endlessly hoping for perfect certainty that never comes.

When should teams make decisions slowly vs quickly?

Make decisions slowly until the risk profile changes and waiting becomes more expensive than being wrong, then decide immediately based on best available information.

How do you prevent reckless decision-making while moving fast?

Fail forward fast on paper and in planning where mistakes cost nothing, then execute confidently in the field because you already caught problems during safe testing.

What is the difference between batching and flow?

Batching disconnects process steps creating waste like Culver’s separating order/payment/delivery, while flow completes each transaction fully like In-N-Out producing better results faster.

How do you unify teams after decisions are made?

Check that everyone can support the decision even if it was not their first choice, requiring violent and radical commitment to execute instead of quiet resentment and sabotage.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

General Offerings

Company Offerings

Systems

SUBSCRIBE NOW !

Subscribe to our newsletters and stay updated!

Important Scam Alert: Fake Elevate Construction Job Emails

Related Books

The First Planner System: The Project Planning System for Executives, Project Managers, and Superintendents in Pre-construction - Book 2

Pull Planning For Builders: How to Pull Plan Right, Respect People, and Gain Time (The Art of the Builder)

The Ten Improvements to Production Planning: What Lean Builders Can Do To Improve Short Interval Planning (The Art of the Builder)

Related Books

The First Planner System: The Project Planning System for Executives, Project Managers, and Superintendents in Pre-construction - Book 2

Built to Fail: Why Construction Projects Take So Long, Cost Too Much, And How to Fix It

Related Books

The First Planner System: The Project Planning System for Executives, Project Managers, and Superintendents in Pre-construction - Book 2

The 10 Myths of CPM: How The Critical Path Method Systematizes Disrespect for People

Calumet "K"

faq

General Training Overview

Superintendent / PM Boot Camp

Takt Production System® Virtual Training

Onsite Takt Simulation

Foreman & Field Engineer Training

Testimonials

Testimonials

agenda

Day 1

Foundations & Macro Planning

day2

Norm Planning & Flow Optimization

day3

Advanced Tools & Comparisons

day4

Buffers, Controls & Finalization

day5

Control Systems & Presentations

faq

UNDERSTANDING THE TRAINING

VALUE AND RESULTS

PLANNING AND SCHEDULING TOPICS

APPLICATION & TEAM ADOPTION

VIRTUAL FORMAT & ACCESSIBILITY

faq

GENERAL FAQS

CURRICULUM & OUTCOMES

LOGISTICS & FORMAT

PRICING & VALUE

SEO-BASED / HIGH-INTENT SEARCH QUESTIONS