Month: March 2026

Recovering a Project

Posted on by Danny Jiménez⁩
Read 22 min

Your project is crashing and you won’t admit it. Learn why pride destroys more projects than problems, and the recovery framework that saves families when leaders get help.

Your Project Is Crash Landing and Pride Won’t Let You See It

Here’s the reality nobody wants to admit: your project is in trouble and you’re too proud to get help. You walk the site and see chaos but tell yourself it’s temporary. You see unclear task delineation, no flow, people working out of their roles, and you convince yourself you’ve got it under control. Meanwhile your schedule is dissolving, your contingency is evaporating, and you’re three months from a crash landing that will destroy relationships, burn through millions, and hurt families. But asking for help feels like admitting failure, so you keep pushing harder hoping the problem fixes itself.

Think about what pride costs on failing projects. A consultant could fly out, assess reality, map projections, and help you form a recovery plan for maybe six thousand dollars. Maybe twelve. Maybe twenty four. Even if it cost fifty thousand, what’s that compared to losing five hundred thousand in fee? Compared to losing one point two million? Compared to finishing three and a half months late and destroying your reputation? The math is obvious. But pride makes you think you should be able to handle it yourself, so you suffer silently while the project crashes.

This pattern repeats across construction with senior superintendents and project managers who would rather fail alone than succeed with help. They ignore warning signs. They reject advice. They convince themselves things will improve if they just work harder. And they crash land spectacularly because hard work doesn’t fix broken systems and increased effort without better planning just wastes money faster. The project was savable months ago with outside perspective and systematic recovery. But pride prevented the call, and now families pay the price.

The Pain of Watching Projects Crash While Leaders Refuse Help

You’ve experienced this frustration watching projects deteriorate. A hundred million dollar high profile project where you can tell something’s wrong from the moment you walk the site. Chaos everywhere. No clear geographical control. No flow. Teams working out of roles. The senior superintendent too stubborn to hear advice, too arrogant to admit problems exist. You offer help. You point out issues. And they wave you off convinced they know best.

That’s what happens when pride meets project trouble. Leaders can’t see reality because admitting problems feels like admitting incompetence. They think asking for help signals weakness instead of wisdom. They convince themselves the schedule is achievable when CPM hides the fact that logic has been dissolved and activities stacked to create false timelines. And they push teams harder, increase manpower, throw materials at problems, and watch money fly out the window while pretending everything’s under control.

The warning signs are clear to anyone looking objectively. People working out of roles. The site is unclean and disorganized. Small amounts of fee loss appear. Increased manpower required just to maintain schedule. Increased inventory. Unreconciled changes in eating contingency. Unclear path to finish. People rushing because team capacity isn’t what it needs to be for actual control. Any of these signals trouble. Multiple signals together scream emergency. But teams in trouble normalize the chaos and keep pushing.

I’ve seen this pattern repeatedly across different projects. One project: senior superintendent refused help, team too arrogant to see problems, crashed landing three and a half months late as disaster. Another project: no one taking clear ownership, everyone pointing fingers, suffering silently, finally got help and recovered with systematic approach. Third project: team asked for help proactively, prevented crash landing, finished successfully. The difference wasn’t project difficulty. It was leadership humility to get help before pride destroyed everything.

The System Hides Problems Until Crash Landing Is Inevitable

Here’s what I want you to understand. The construction industry systematically hides project problems until recovery becomes nearly impossible. CPM schedules show everything on track while superintendents dissolve logic and stack activities to create false timelines. Teams normalize chaos as temporary challenges instead of systemic failures. Pride prevents leaders from admitting they need help until the damage is catastrophic. And companies dispatch senior general superintendents to save failing projects instead of investing in training and systems that prevent problems.

It’s really hard to see if a project is going badly when CPM hides reality. Especially when schedulers or superintendents dissolve logic and stack activities unbeknownst to project managers and teams who don’t know they have no clear path to finish. The schedule shows substantial completion achievable. Reality shows you’re months behind with no plan to close the gap. And nobody wants to be the person who says the emperor has no clothes because that feels like creating problems instead of solving them.

But silence guarantees failure. Projects don’t recover through hoping harder or working longer hours. They recover through systematic stabilization, clear planning with flow, disciplined execution, and often outside facilitation that brings objective perspective. Every project I’ve helped recover followed similar patterns. Leaders finally admitted they needed help. We assessed reality honestly. We implemented systematic recovery. And we saved the project, the money, and the families.

Here’s the framework that works every time when implemented with discipline:

  • Stabilize the site immediately for cleanliness, organization, and safety through complete purging and reset
  • Organize all functional roles by geographical area, not by scope or trade, to establish control
  • Focus the team on contract work, not change order work, to finish what you’re already paid for
  • Map out a plan to finish that has flow using Takt planning to show real timeline and required resources
  • Standardize meeting systems to create flywheel consistency: weekly work planning, afternoon foreman huddles, morning worker huddles, daily project management team huddles minimum 30 minutes
  • Maintain fanatical discipline around cleanliness and safety, resisting temptation to rush and abandon standards
  • Focus team on roadblock removal daily with project executive and general superintendent enabling success
  • Scrum non-timelined work like elevator testing, life safety inspections, commissioning to get twice the work done in half the time
  • Get experienced help through consulting, facilitation, or senior leaders within your organization who can see objectively

When we do it right and set it up right, it works every time. But it requires humility to admit you need help and discipline to follow the system instead of just throwing more manpower and materials at problems.

Why Getting Help Saves More Than Just Money

Let me walk you through what happens when leaders swallow pride and get help versus when they crash land alone. First, an outside perspective sees reality you can’t see from inside the chaos. You’ve normalized the dysfunction. A consultant or experienced general superintendent walks in and immediately identifies systemic problems you’ve been rationalizing as temporary challenges. That clarity alone is worth the cost because you can’t fix what you can’t see.

Second, systematic recovery prevents the catastrophic fee loss that comes from just pushing harder. When I help projects recover, we create Takt plans that show the actual timeline. If you’ve got four months left and the real timeline is four months and two weeks, we have that conversation with the owner about what dials to turn. Maybe we will bring it in. Maybe we accept reality and adjust. But we don’t create fake sequences showing the finish in four months when physics says four months and two weeks, because lying to yourself just means you’ll throw money at impossible timelines instead of planning appropriately.

Third, flow-based planning prevents the burnout that destroys families. Projects in trouble typically respond by increasing hours, adding manpower, pushing trades harder. That approach burns people out, destroys quality, and doesn’t actually speed up finish because you haven’t addressed the systemic issues preventing flow. When we implement Takt with proper planning, we go smooth to go fast. We hold the line in steady controlled manner. We finish as early as physically possible with flow instead of just earlier on fake schedules.

Fourth, standardized meeting systems create the consistency that enables control. The afternoon foreman huddles planning next day’s work. The morning worker huddles communicating the plan to everyone. The weekly work planning coordinating trades. The daily project management huddles scrumming through roadblocks. These rhythms create visibility, accountability, and coordination that prevent small problems from becoming disasters.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. We work with builders who understand that getting help isn’t weakness, it’s protecting families by solving problems before pride destroys them.

The principle underlying recovery is simple: outpace entropy. You don’t have to fully implement every system, but you must have systems in place that correct problems fast enough to outpace the natural chaos of projects and bad behaviors on site. Communication systems with GC carpenters help you go fast. Zero tolerance for safety helps you go fast. Morning huddles reminding people of expectations help you go fast. Foreman huddles planning each day’s work help you go fast. You cannot have complacent teams that allow project chaos to move faster than your ability to correct problems.

The Challenge: Admit You Need Help This Week

So here’s my challenge to you. If you do not know 100 percent that you have control, then you don’t have control. If you can’t see easily that your project is on track, then it’s not. Meaning if you don’t know for a fact that things are going well, they’re probably not. And you need to take an honest look instead of pretending everything’s fine.

Get some help. Get some facilitation. Hire a consultant. Bring in an experienced general superintendent from within your organization. Get objective perspective from someone not invested in defending past decisions. The cost is nothing compared to the consequences of crashing. Six thousand or twelve thousand or even fifty thousand in consulting fees saves five hundred thousand or one point two million or two point five million in net fee loss. The math isn’t complicated. Pride just makes it feel like weakness to ask for help when it’s actually wisdom.

Stop suffering silently through bad projects because of pride. Your families need you to swallow ego and get the help that saves them from burnout and financial disaster. Your team needs you to admit when you can’t see clearly so someone objective can assess reality. Your company needs you to prevent catastrophic losses by investing in recovery before it’s too late.

Recovering a project always comes down to being productively paranoid, creating stability, respecting people, and making sure you have a good plan held with the team in a disciplined manner so you can control the job without needlessly throwing away money. Get the training and systems in place proactively to prevent crashes. Implement Takt, Last Planner, Scrum. Use integrated control systems. Train all field positions. But when prevention fails and you’re in trouble, get help immediately instead of crashing alone three months later.

As the principle teaches, we must outpace entropy by implementing systems that correct problems faster than chaos creates them. Pride prevents that by making leaders suffer alone instead of getting help that enables systematic recovery.

On we go.

Frequently Asked Questions

How do I know if my project is actually in trouble or just experiencing normal challenges?

If you can’t clearly see you’re on track, you’re in trouble. Warning signs include: people out of roles, site unclean, unclear path to finish, increased manpower just to maintain schedule, small fee losses appearing, rushing without actual control. Normal challenges don’t require hiding reality or normalizing chaos.

What if getting outside help makes my company think I can’t handle projects?

Companies respect leaders who prevent catastrophic losses through timely intervention more than leaders who crash alone out of pride. Asking for help early shows wisdom. Crashing late shows stubbornness that costs millions.

Won’t bringing in consultants undermine my authority with the team?

Outside perspective strengthens your leadership by providing objective assessment and systematic recovery frameworks. Teams respect leaders who get them help instead of pushing them harder through unsolvable situations created by broken systems.

How quickly can a project in trouble be stabilized?

Stabilization starts immediately with site cleanup, role organization, and meeting systems. Full recovery depends on how far behind you are, but systematic approach with Takt planning shows a real timeline within days. Honest assessment beats false hope.

What’s the minimum investment needed to get meaningful help recovering a project?

Even brief facilitation can provide perspective that saves hundreds of thousands. The question isn’t cost of help, it’s cost of not getting help. Spending five figures to save six or seven figures in fee loss and relationships is obvious math once pride stops blocking it.

 

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.

Make Your Office Environment Fun

Posted on by Danny Jiménez⁩
Read 24 min

Your stuffy trailer destroys morale daily. Learn why office environments designed like Disneyland create productivity, and how music, scents, and foosball transform teams.

Your Office Trailer Is Boring and It’s Destroying Team Performance

Here’s the question that reveals whether you’re optimizing for human beings or just tolerating them: Is your office trailer fun? Not functional. Not adequate. Fun. Does it make people happy when they walk through the door? Does it smell good, sound good, look visually stimulating? Do people want to show it off to visitors or are they embarrassed by the brown walls and cluttered desks that signal learned hopelessness? Because studies prove that happy people having fun are more productive. And your boring, stuffy office environment is systematically destroying the morale and performance you claim to want.

Think about what you’re communicating with your current trailer setup. Dusty air. Brown walls. Cluttered desks everywhere. No music because “people will waste time.” Messy spaces that nobody cleans. Zero personality. Zero joy. You’re telling your team that work is supposed to be miserable, that fun isn’t allowed, that they should check their personalities at the door and become vanilla versions of themselves to fit boring norms. And you wonder why people don’t feel engaged, don’t take ownership, don’t bring their best thinking to problems.

The pattern is predictable across stuffy office environments. People show up, do minimum required work, leave as quickly as possible. Nobody wants to tour visitors through the trailer. Nobody draws self-esteem from what others think of their workspace. Nobody feels like the company values their minds, just their ability to do mindless tasks. And productivity suffers because you’re missing the single biggest opportunity to create the culture, autonomy, and joy that drives excellence.

The Pain of Working in Spaces That Destroy Your Soul

You’ve experienced this frustration working in trailers that feel like punishment instead of places designed for human beings. You walk in and immediately feel the weight of boring brown walls, cluttered inventory nobody bothered organizing, stale air that smells like dust instead of intentional scents. There’s no music because someone decided silence equals professionalism. There’s nowhere to have fun, no space that brings joy, nothing that signals “it’s okay to be yourself here and enjoy your work.”

That’s what happens when companies optimize office environments for minimal cost instead of maximum human flourishing. They buy standard trailers with brown walls and think that’s sufficient. They tolerate clutter because “it’s a construction site” instead of maintaining spaces as clean as the work they expect in the field. They ban music and fun because some general superintendent once said “turn that off and get off the internet, people will waste time” without understanding that autonomy creates engagement, not waste.

The irony is brutal. You spend money on productivity tools, scheduling software, and process improvement while ignoring the single biggest factor affecting team performance: whether people are happy at work. Happy people are more productive. Happy people have better teaming and healthy conflict. Happy people bring creative solutions instead of just complying with minimum standards. And happiness starts with environments designed to bring joy instead of environments that systematically drain it.

I’ve run projects where the office trailer felt like Disneyland. Scented wall flowers in bathrooms. Music playing at low volume. Conference rooms remarkably designed. Craft lunchroom attached with foosball table, putting green, closet full of Nerf guns for Nerf wars. Beautiful signage on walls. Refrigerators, microwaves, spaces that made people happy to be there. When we demobilized and trailers left, the team was sad. That’s the measure of success. People were sad when the fun space left because it made work enjoyable.

The System Creates Stuffy Environments That Prevent Joy

Here’s what I want you to understand. The construction industry systematically creates office environments optimized for minimal investment instead of maximum human performance. We accept brown walls as normal. We tolerate cluttered spaces as inevitable on construction sites. We ban fun elements like music and games because we confuse professionalism with joylessness. And we create cultures where people vanilla themselves down to fit boring norms instead of bringing full personalities and energy to work.

But the best projects operate differently. They design every space in the trailer to bring joy and enable specific human interactions. They understand that office environments communicate culture more powerfully than any mission statement. And they invest in creating spaces people actually want to work in instead of just tolerating because they have to.

Here’s what office environments designed for human beings actually include:

  • Music playing at low volume with good channels that signal it’s okay to have fun
  • Scented wall plugins triggering positive mind anchors to the space instead of dust smell
  • Visually stimulating walls with intentional design, not just brown panels
  • Cleaned trailers minimum two to three times per week with everything vacuumed and wiped down
  • Open office layout with fewer walls and intentionally designed production pods for focused work
  • Wall spaces dedicated to family pictures reminding everyone why we work
  • Fun pictures and creative areas celebrating team culture
  • Intentional signage anchoring the team to having fun on the project
  • Something in the trailer that gives license to make it fun: foosball table, putting green, pool table, card games
  • Conference rooms with display pieces and remarkable design
  • Every space bringing joy and designed for specific interactions: learning, developing, planning, executing, quiet mode, conferencing

The bottom line measure of success: every space in the trailer should bring you joy. Every space is designed for human interaction. Design it like Disneyland, an aquarium, a learning center, a museum. When you go to science museums with kids, every space is designed to bring remarkable experiences. That’s how you should design office trailers. Not for minimal cost, but for maximum human engagement and joy.

I got feedback on LinkedIn from a trusted associate after one of these projects. She said: “Jason runs the most organized, positive, clean, timely and safe construction sites and offices I’ve ever worked in. He motivates all the workforce, including consultants, to perform to the highest standard with humor, humility and determination. He leads by example and appears almost omnipresent on site. Working there just plain makes me happy.” That’s the goal. Working there makes people happy. Not just tolerable. Not just functional. Happy.

When people said it felt like being at Disneyland, that wasn’t criticism. That was confirmation we designed environments for joy. If your trailer doesn’t feel like that, you’re missing an opportunity. The site should be clean, fun, organized with great signage and visuals. Bathrooms and lunch areas should feel remarkable. But the main thing that should feel remarkable and fun is your office trailer.

Creating Environments That Bring Joy and Performance

Let me walk you through how to transform your office environment from boring to joyful. First, address the sensory elements that affect everyone unconsciously. Music at low volume signals autonomy and fun are allowed. Scented wall plugins in bathrooms and common areas create positive associations instead of dust and staleness. Visual stimulation through intentional wall design, family pictures, team celebrations, and beautiful signage makes spaces engaging instead of depressing.

Second, maintain cleanliness as relentlessly as you maintain safety standards. Get excess inventory out of the trailer. Store it elsewhere or eliminate it. Vacuum all corners, wipe down all surfaces, clean windows. Have the trailer professionally cleaned minimum two to three times per week. When desks are messy and clutter is everywhere, that brings learned hopelessness. When spaces are clean and organized, that signals we care about this environment and the people in it.

Third, design for autonomy and trust instead of control. When general superintendents say “turn off the music and get off the internet, people will waste time,” they’re revealing they don’t trust their team. For ninety five percent of people, when you give employees autonomy, they do great things with it. It really works. Stop treating adults like children who need silence and restrictions. Create environments that assume people are professionals who will use freedom responsibly.

Fourth, create spaces specifically designed for fun and human connection. Foosball tables aren’t distractions. They’re relationship builders. Putting greens aren’t wastes of space. They’re stress relievers that help people reset between focused work sessions. Nerf gun closets aren’t childish. They’re permission to be playful and build team bonds. These elements communicate that bringing your whole personality to work is encouraged, not banned.

Fifth, design wall spaces intentionally for specific purposes. Dedicate thirty to fifty feet of wall space for family pictures. Why do we come to work? To support families. Celebrate that visually. Create areas for team celebrations, project milestones, creative thinking. Use signage to anchor cultural values. Make the trailer tell the story of who you are and what you value instead of just being generic brown panels.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. We work with builders who understand that office environments designed for joy create the productivity and engagement that stuffy trailers destroy.

The principle underlying this is equality. The best superintendents aren’t elitist. They don’t feel above workers or anyone else. They’re approachable, kind, respectful. They understand craft workers are skilled professionals who add value and deserve elevated treatment in minds, care, respect, and training. Even though we have organizational hierarchies, there’s a difference between having roles and playing boss with hierarchical elitism. Onsite workers should feel accepted entering trailers and bathrooms. They should feel comfortable speaking up. There’s no difference between them and management in position on the team. They should feel appreciated, equal, and treated with respect.

The Challenge: Make Your Office Environment Bring Joy This Month

So here’s my challenge to you. This month, transform your office trailer from stuffy to joyful. Start with sensory elements: add music, install scented wall plugins, clean everything thoroughly. Then add elements that give license to have fun: foosball table, putting green, games area. Create wall spaces celebrating families and team culture. Design every space to bring joy and enable specific interactions.

Ask yourself these questions to measure whether you’re succeeding. Is your team having fun every day? Do they find work fulfilling? Do they feel they’re accomplishing something? Do people feel appreciated with thank yous and recognition? Can they be themselves and express personalities? Are they valued for their minds, not just for doing mindless work? Does everybody in the trailer like their coworkers including their boss? Do people know their jobs are valued? Do they have fulfillment within? Do they believe in the project mission? Are they treated with respect? Do they have true sense of ownership?

More questions: Do people come through the door knowing they don’t have to check values or personalities or fun at the entrance? Or do they vanilla themselves down to fit boring norms? Do you celebrate successes with bullhorns, whistles, claps, shout outs? Are people liquidated for mistakes or turned into scapegoats? Do you share credit visually? Do people love touring others through the trailer? Do they draw self-esteem from what others think of their job and team? Friends and family thinking the job and company are cool matters more than you realize.

The measure of success is simple: you want a space like Google or Netflix where people say “you have to see our office.” When teams want to show off their workspace to visitors, when they’re proud of where they work, when the environment makes them happy instead of just tolerating it, you’ve succeeded. Happy people are more productive. More autonomy and freedom to play music, have fun, and live culture brings more productivity, more teaming, more healthy conflict, more of all the good things.

Stop accepting stuffy boring trailers as normal in construction. Design environments that bring joy. Create spaces people actually want to work in. Give teams autonomy to be themselves and have fun. And watch productivity improve because happy people perform better than people systematically drained by environments designed for minimal cost instead of maximum human flourishing.

As research consistently shows, happiness and productivity are directly connected. Investing in joy isn’t soft or wasteful. It’s the strategic decision that separates excellent teams from mediocre ones.

On we go.

Frequently Asked Questions

Won’t fun elements like foosball tables and music distract people from actual work?

Studies prove happy people are more productive. Fun elements create autonomy and trust that drive engagement. Ninety five percent of people use freedom responsibly. The productivity gains from happiness far exceed any time spent on games during breaks.

How do we justify spending money on office improvements when budgets are tight?

Compare the cost of foosball tables and wall plugins to the cost of low morale, poor productivity, and turnover. Happy environments retain people and drive better performance. The investment pays for itself through improved team effectiveness.

What if our company culture is more traditional and serious?

Professionalism doesn’t require joylessness. You can maintain high standards while creating environments people enjoy. Traditional doesn’t mean boring. Even serious companies benefit from happy teams who feel valued and trusted.

How do we maintain cleanliness standards when construction sites are inherently messy?

Professional cleaning two to three times per week is minimal investment. The site being messy doesn’t justify the trailer being messy. Clean organized offices communicate you care about people and standards, which affects how they approach field work.

What if leadership thinks fun offices are unprofessional or childish?

Show them the data on happiness and productivity. Point to companies like Google and Netflix that design for joy and dominate their industries. Ask whether they want compliant people doing minimum work or engaged people bringing creative solutions.

 

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.

Do not Mandate Software for the field

Posted on by Danny Jiménez⁩
Read 25 min

Corporate Is Forcing Software That Destroys What Field Teams Actually Need

Here’s the pattern killing productivity across construction: your IT department, process improvement team, or corporate leadership mandates software for field teams without ever asking if it actually works in the field. They choose safety walk applications that require fourteen clicks and four hours to complete what used to take twenty minutes. They force punch list software so cumbersome that superintendents stop doing daily corrections and projects get less safe. They sell to executives on features that sound impressive in boardrooms but create chaos on job sites. And when field teams push back, corporate responds with “this is company policy” instead of listening to the people who actually do the work.

Think about what this costs your projects. A superintendent who crushed projects using tools that worked perfectly gets saddled with mandated software that slows everything down. Safety observations drop from twenty five per day to four because the new system is too burdensome. Daily reports that used to take minutes now require hours navigating complex interfaces. Quality inspections that field teams completed efficiently become administrative nightmares that nobody wants to touch. And all of this happens because someone in corporate who never walks job sites decided they knew better than the people putting work in place.

The irony is brutal. Companies spend over a million dollars implementing software that reduces productivity instead of spending that money training people and improving actual field effectiveness. They pander to software lobbyists selling through corporate channels instead of letting field teams choose tools that make their lives easier and help them go home to families. And they wonder why projects struggle when they’ve systematically destroyed the productivity of the only people who create value by putting work in place.

The Pain of Being Forced to Use Tools That Don’t Work

You’ve experienced this frustration as a field leader. Corporate announces the new company standard for safety walks or punch lists or daily reports. You attend the training and immediately see it won’t work in field reality. Too many clicks. Too complicated. Optimized for data collection corporate wants instead of corrections field teams need. You raise concerns. Corporate dismisses them because IT already bought licenses and executives already committed to the vendor. And you get stuck using garbage software that makes your job harder while being told it’s an improvement.

That’s what happens when people who don’t do the work decide what tools the workers use. IT departments want systems they can manage centrally even if those systems destroy field productivity. Process improvement teams want standardization even if the standard is terrible for actual work. Finance departments want single vendor contracts even if that vendor’s tools are inferior for specific tasks. And nobody asks the superintendents, project managers, foremen, and trade partners who will actually use these tools daily whether they work.

The pattern repeats across companies. Corporate mandates a new safety walk process with cards to carry, 7,500 clicks to make, forms that take four hours. Field teams who were getting fifteen to twenty five observations daily through effective systems drop to four observations because the mandated system is too burdensome. Projects become less safe because people stop doing the work when tools make it miserable. And corporate blames field teams for not adopting the new system instead of admitting they forced garbage on people.

I’ve seen this destroy productivity on excellent projects. Teams using simple effective tools that let them focus on building get forced onto complex platforms that require constant administrative work. Superintendents who had everything they needed, P6 for master schedules, Excel for Takt, V Planner for pull planning, Smartsheet for personal organization, Bluebeam for documents, BIM 360 Glue for model access, Note Vault for daily reports, simple fast effective tools, get told they must use corporate standard platforms that combine everything poorly instead of doing specific things excellently.

The System Rewards IT Convenience Over Field Effectiveness

Here’s what I want you to understand. The construction industry systematically optimizes software decisions for IT departments and corporate control instead of field team productivity and effectiveness. We let people who never walk job sites decide what tools job site teams use. We prioritize vendor relationships and licensing simplicity over whether tools actually help people do work. And we create mandates that destroy the productivity we claim to want because we’re optimizing for the wrong things.

When I was superintendent at DPR, I had all the software I needed to do my job. And we absolutely crushed that project with full fee, quality on time, healthy people, everyone making promotions. The customer said it was the best project they’d ever had. I used maybe seventeen different applications, each one excellent for its specific purpose:

  • P6 for master schedule when using CPM
  • Excel for Takt planning and phase planning
  • V Planner for pull planning coordination
  • Smartsheet for personal organization and tracking
  • Bluebeam for documents and markups
  • CMIC for project management, actually pretty good and non-intrusive
  • BIM 360 Glue for foremen to see the model
  • Note Vault for daily reports, super easy and fast with lots of pictures
  • Text systems for daily correction tracking
  • Multiple other tools each chosen because they were best for specific tasks

People said “that’s like seventeen different softwares.” Here’s the surprise: there are hundreds of things superintendents and project managers need to know how to do. If you can’t learn the software of your trade, get out of the game. And software people, IT people, process improvement people, stop babying field teams. We’re not stupid. We can use the right application for the right activity at the right time. The problem comes when you mandate it instead of letting the best tools win.

There is zero issue with using the right application at the right time for the right process in the right way. The issue is mandating ineffective systems for everything to make it easy on IT or process improvement instead of making it effective for field teams creating value. When someone tried to tell me “don’t use Bluebeam, use this” or “don’t use BIM 360 Field for punch lists, use this,” my answer was simple: No. I’m going to use what’s quick and easy for superintendents, foremen, trade partners, and workers. This is what we’re going to do.

The role of construction managers is not simple. Someone once asked me to distill superintendent responsibilities into three main concepts. I was insulted. If you want to be a superintendent, you need to be on top of your game. You need to know personal organization, scheduling, quality, safety expertise, how to deal with people, emotional intelligence, how to hold people accountable while respecting them, personal drive, vision, and I could go on. The role is complex. So why do IT departments think we’re too stupid to use multiple applications at the right moment? We’re not. Let us use what’s right for workers, customers, and making our lives easier so we can go home to families.

Why Letting the Best Tools Win Protects Productivity

Let me walk you through why field teams should choose their own tools instead of having corporate mandate them. First, people who do the work understand what actually works in field reality. A superintendent knows whether safety walk software is fast enough to encourage observations or so burdensome it prevents them. A foreman knows whether punch list tools are simple enough to use daily or complex enough to avoid. Corporate executives in boardrooms can’t make those judgments because they don’t live in field reality where tools either enable work or destroy productivity.

Second, competition between tools drives improvement that mandates prevent. When field teams can choose between P6, Excel, Smartsheet, V Planner, and other scheduling tools, each vendor has to prove their tool is as addictive as Facebook, as useful as YouTube, as quick as Wikipedia. The best tools win through being excellent. When corporate mandates one platform, that vendor has no incentive to improve because they have captive users who can’t switch even when tools are terrible.

Third, different tasks genuinely need different tools optimized for specific purposes. Daily reports need speed and simplicity. Master schedules need logic and critical path analysis. Pull planning needs collaboration and visual management. Personal organization needs flexibility and quick access. One platform trying to do everything does nothing excellently. Seventeen tools each excellent for their specific purpose beat one mediocre platform forced on everyone.

Fourth, field team autonomy to choose tools creates ownership and adoption that mandates destroy. When superintendents select tools that make their jobs easier, they use them effectively and teach others. When corporate forces tools that make jobs harder, field teams resist, work around them, or comply minimally while resenting the burden. Autonomy creates engagement. Mandates create resistance.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. We work with builders who understand that software decisions should serve field productivity, not IT convenience or corporate control.

Here’s what needs to change. Before mandating any field software, have IT people, process improvement teams, and corporate decision makers use it in the field for real work. If IT wants to decide safety walk software, they need to go do safety walks with that software and see how they like it. If they want to dictate quality inspection tools, haul their butts out in field and do inspections. If they want to mandate punch list software, have them go out and use it for punch. Saddle them with it before saddling field teams. And if someone’s being arrogant saying this is wrong, they’re part of the problem. What they’re doing is hurting people.

The current condition is we have garbage applications being shoved down field teams’ throats. When superintendents have access to P6, Excel, V Planner, BIM 360 Field, BIM 360 Plan, Bluebeam, CMIC, BIM 360 Glue, Smartsheet, and other excellent tools, the best ones win naturally. Program developers and software companies compete to create tools people actually want to use. What we don’t need is corporate selling to executives, executives mandating tools, and field teams getting stuck with them regardless of effectiveness.

The Challenge: Let Field Teams Choose What Works

So here’s my challenge to you. Work with me. Please share this message. Please stop the reversal of progress in construction by mandating stupid software that reduces productivity. What we need is increased productivity, care for workers, and more effective tools. Instead of pandering to lobbyists selling ineffective software through corporate channels, let tools compete based on whether field teams actually want to use them.

Give field teams autonomy to choose applications that work best for their specific tasks. Let P6, Excel, Smartsheet, Bluebeam, and other vendors compete by proving their tools are excellent. Stop forcing unified platforms that do everything poorly instead of letting specialized tools do specific things excellently. And before mandating anything, require decision makers to use those tools in the field for real work to understand whether they actually help or hurt.

Trust that superintendents, project managers, foremen, and trade partners are capable of learning multiple applications. Stop babying them with simplified mandates that actually make their jobs harder. The role requires expertise in hundreds of areas. Using the right software for the right task is basic competence, not an overwhelming burden. Let the people doing the work choose the tools that help them do it well.

Check with field teams before implementing corporate software decisions. Ask superintendents whether new safety walk systems will increase observations or decrease them. Ask project managers whether mandated platforms will speed up daily reports or slow them down. Ask foremen whether punch list tools are simple enough for daily use or too complex to adopt. Listen to the people who will use tools daily instead of just believing vendor presentations in boardrooms.

Remember that software decisions affect families. When mandated tools slow down field teams, projects run longer, people work harder hours compensating for lost productivity, and families suffer. When effective tools let teams work efficiently, people go home at reasonable times. The software you mandate isn’t just a corporate decision. It’s affecting whether workers see their kids at night or miss dinner again because cumbersome systems destroyed their productivity.

As Steve Jobs said about mortality, “Almost everything just falls away in the face of death, leaving only what is truly important. You are already naked. There is no reason not to follow your heart.” The same principle applies here. What’s truly important is field teams having tools that help them build excellently and go home to families. Corporate mandates, vendor relationships, and IT convenience fall away as unimportant compared to that.

On we go.

Frequently Asked Questions

Won’t letting field teams choose their own software create chaos with too many different tools?

Multiple excellent tools each optimized for specific tasks creates better results than one mandated platform doing everything poorly. Field teams aren’t stupid. They choose tools that work and teach each other. Competition drives improvement that mandates prevent.

How do we ensure data integration if teams use different software?

Focus on outcomes not integration. If field teams complete safety walks, punch lists, and daily reports effectively using tools they chose, that matters more than having everything in one database. Most integration problems are IT wanting centralized control, not field teams needing it.

What if field teams choose expensive software instead of our corporate standard?

Compare total cost including lost productivity. Cheap mandated software that slows teams down costs more than excellent tools that let them work efficiently. Calculate hours wasted on cumbersome systems versus money saved on licensing.

Won’t this approach require more IT support for multiple platforms?

IT exists to support field teams, not the reverse. If supporting effective tools field teams actually use requires more work, that’s IT’s job. Forcing terrible software to make IT’s life easier while destroying field productivity is backwards.

What if corporate already committed to a vendor and we can’t back out?

Learn from the mistake and don’t mandate the next one. Even with existing contracts, give field teams choice to use other tools if they’re more effective. Sunk costs don’t justify forcing continued use of software that hurts productivity.

 

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.

The Procurement Log. You are not doing this right

Posted on by Danny Jiménez⁩
Read 24 min

You’re Not Tracking Procurement Early Enough (And It’s Destroying Your Schedule)

Here’s the pattern costing you hundreds of thousands on every project: you treat procurement like paperwork instead of the supply chain management that makes or breaks your schedule. You bring materials out all at once by floor or building instead of just-in-time by area. You let project engineers manage submittals and RFIs like administrative tools instead of overseeing entire scopes from buyout through closeout. And you wonder why materials show up late, get damaged sitting on site, require constant movement creating waste, and destroy the flow you’re trying to create. The brutal truth is only about fifteen percent of projects even come close to doing procurement right.

Think about what procurement actually is. It’s not submittal processing. It’s not RFI management. It’s not tracking paperwork. Procurement is inspecting the design, coordination, visualization, approval, fabrication, delivery, proper installation, testing, and closeout of every scope of work. It’s making sure your supply chains are one hundred percent successful from the moment you buy materials through the moment contractors leave and all change orders are closed. That’s the job. And if you don’t have a procurement log that’s one hundred percent complete, tied to your Takt plan, reviewed weekly with superintendents in the room, you have massive problems.

The data is clear. Excess inventory and overproduction are the parents of all other wastes. If someone asked me to sabotage a project without anyone knowing and make them lose a million bucks, I’d talk the project engineer into bringing out more materials than needed and storing them on site. That’s it. Done. They’ll end up at least minus five hundred thousand by the time they’re finished. Because materials sitting on site get damaged, require constant movement, block work areas, slow down trades, create safety hazards, and destroy the flow that makes projects finish on time.

The Pain of Materials That Arrive Wrong or Create Chaos

You’ve experienced this frustration when procurement fails. Materials show up late delaying installation. Wrong products arrive requiring reorders. Correct materials arrive but get damaged sitting on site for months. Excess inventory blocks access creating constant movement waste. Mockups happen too late to influence design. Submittals get approved without anyone verifying they match what’s actually needed. And project teams spend their time firefighting procurement crises instead of building because the supply chain was never managed proactively.

That’s what happens when you treat procurement as paperwork instead of supply chain management. Project engineers think their job is processing submittals and RFIs. They manage tools instead of overseeing scopes. Superintendents don’t attend procurement meetings because “that’s a PM thing.” Nobody connects procurement tracking to the Takt plan showing when materials are actually needed. And materials arrive on vendor schedules instead of installation schedules, creating the chaos that destroys productivity.

The pattern repeats across projects. Materials ordered all at once by floor or building because “it’s cheaper to ship in bulk.” Never mind that storing materials on site for months costs more in damage, movement, and delays than shipping smaller just-in-time deliveries. Mockups done late as aesthetic assemblies after glass and panels are already ordered instead of early performance mockups that could influence design. Procurement logs treated as compliance documents instead of daily tools superintendents and project engineers use to track material readiness.

I remember projects where we nailed procurement. Materials arrived just-in-time by area ahead of installation with right inventory buffers. Mockups happened early enough to verify design and assembly. Project engineers and superintendents reviewed procurement logs weekly ensuring everything was on track. The flow was beautiful because materials never blocked progress or created firefighting. Compare that to projects where materials arrive wrong, get damaged sitting on site, and teams spend half their time managing chaos that proactive procurement would have prevented.

The System Treats Procurement Like Paperwork Not Supply Chain

Here’s what I want you to understand. The construction industry systematically treats procurement as administrative paperwork instead of the supply chain management that determines whether projects flow or fail. We hire project engineers to “manage submittals and RFIs” instead of “oversee scopes from buyout through closeout.” We let superintendents skip procurement meetings because we think it’s office work instead of field coordination. We order materials in bulk to “save shipping costs” without calculating what storing them on site actually costs in damage, movement, and delays.

But the best projects operate completely differently. They understand procurement is inspecting design, coordination, visualization, approval, fabrication, delivery, installation, testing, and closeout. They track materials from the moment they’re specified through the moment they’re installed and verified. They bring materials just-in-time by area, not all at once by floor. They involve superintendents in weekly procurement meetings because field leaders need to know what’s coming and when. And they tie procurement logs to Takt plans showing exactly when each scope needs materials, not to CPM schedules that hide reality.

Here’s what procurement done right actually includes:

  • Procurement log one hundred percent complete showing every scope, submittal, delivery, installation date
  • Tied to Takt plan by area and sequence, not CPM by floor or phase
  • Superintendents in weekly meetings reviewing what’s coming and addressing roadblocks
  • Materials delivered just-in-time by area ahead of right inventory buffers, never all at once
  • Project engineers overseeing entire scopes from buyout through closeout, not just managing tools
  • Mockups done early in schematic design to influence design, not late as aesthetic compliance
  • Second set of eyes verifying complex assemblies, interfaces, materials, compatibility
  • Daily tool for both office and field tracking material readiness, not compliance paperwork
  • Quality process from teaming through rolling completion all focused on supply chain success
  • Pre-mobilization meetings breaking scopes into features of work preparing submittals and JHAs
  • Pre-installation meetings reviewing materials and assembly with foremen and crews
  • Initial inspections verifying crews understand how to assemble materials correctly
  • Follow-up walks confirming product installation matches expectations throughout

When you do procurement right, materials arrive when needed, crews have what they need to work, flow isn’t interrupted, and projects finish on time. When you do it wrong, you spend hundreds of thousands moving materials around site, fixing damage from improper storage, waiting for wrong products to be replaced, and managing chaos that proactive tracking would have prevented.

The excuse I hear constantly is “we can’t afford multiple deliveries, bulk shipping is cheaper.” Stop it. You’re killing me with this. Please just be quiet and rethink your life. It might cost twenty thousand extra for multiple deliveries. But we can either spend two hundred thousand moving materials around or spend twenty-five hundred getting extra trucks. That’s pretty common sense. Just get it done. Do not under any circumstances bring materials all by floor, all by building. You cannot do it. And right now you’re thinking “well Jason’s wrong about this.” You’re not. I’m right. Just trust me on this and figure it out.

Managing Supply Chain From Design Through Closeout

Let me walk you through what procurement management actually means from beginning to end. First, understand that project engineers don’t manage tools. They oversee scopes of work from the beginning of that scope all the way through where contractors leave and all change orders are closed. One hundred percent. That’s the job. If you’re thinking of your role as “I process submittals and RFIs,” you’re failing. Your job is making sure supply chains succeed from design through installation through testing through closeout.

Second, track procurement from the moment scopes are bought. Teaming phase: ensure right scope purchased. Pre-mobilization meeting: contractor breaks scope into features of work, prepares submittals and JHAs, researches assembly. Pre-installation meeting: review materials and assembly with foremen and crews who will install it. Initial inspection: verify crews understand assembly. Follow-up walks: confirm installation matches expectations. Rolling completion: close out scope completely. Every step focused on materials and supply chain.

Third, bring materials just-in-time by area ahead of right inventory buffers. Not all at once by floor. Not in bulk because shipping is cheaper. By area in sequence matching your Takt plan. If zone three gets framing week four, materials arrive week three. If zone five gets MEP week six, materials arrive week five. Just-in-time means right before needed, not months early creating storage chaos.

Fourth, involve superintendents weekly in procurement meetings. They need to see what’s coming, when it arrives, what roadblocks exist. This isn’t “PM office work.” This is field coordination determining whether crews have materials when they need them or stand around waiting. Get those supers in weekly meetings reviewing the procurement log. If you don’t have superintendents in procurement meetings, you’re failing.

Fifth, do mockups early enough to influence design, not late as aesthetic compliance. If you’re in Phoenix, go to Field Verified Brian Melcher’s office. He’ll build mockups early for probably a tenth the cost of what you’d build on site. Most mockups happen too late. Glass already ordered. Panels already ordered. Then we assemble a hundred thousand dollar mockup and say “okay, we would have seen that when the building was up anyway.” That’s waste. Do mockups in schematic design when they can influence decisions.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. We work with builders who understand that procurement management from design through closeout prevents the million-dollar waste that treating it like paperwork creates.

Think about the quality process from this lens. Buyout ensures right scope. Pre-mobilization prepares materials. Pre-construction reviews assembly. Initial inspection verifies understanding. Follow-up walks confirm execution. Rolling completion closes scopes. It’s all about materials. All about supply chain. All about procurement. Project engineers supervise, help, assist, and support installation of materials from beginning to end. They oversee scopes even if they have geographical assignments.

The bottom line is procurement will make or break your project. If right now you don’t have a procurement log that’s one hundred percent complete, tied to your Takt plan, reviewed with six-week make-ready look ahead, with superintendents in meetings weekly, you have massive problems. That needs to be the next right thing you do.

The Challenge: Fix Your Procurement System This Week

So here’s my challenge to you, and I’m saying this with compassion but also urgency. Get those supers in weekly meetings. Get that procurement log up and running. Do not, for the love of all things holy, tie that to CPM. Make sure it’s tied to your Takt plan. Make sure you have dates. Treat it like an art form, not a science.

Stop bringing materials all by floor or building. Bring them just-in-time by area ahead of right inventory buffers. Yes, it might cost extra for multiple deliveries. But that’s nothing compared to what you’re losing moving materials around, fixing damage, and managing chaos from improper storage. Excess inventory and overproduction are the parents of all other wastes. Eliminate them.

Do mockups early in schematic design when they can influence design decisions. Not late as aesthetic assemblies after everything’s already ordered. Find vendors who can build mockups quickly and cheaply early in the process. Use them to validate design, materials, interfaces, assembly compatibility, and installation steps before committing to full fabrication.

Make procurement logs daily tools for both office and field. Not compliance paperwork filed away somewhere. The superintendent should look at it daily. The project engineer should update it daily. The PM should review it weekly. Everyone should know what’s coming, when it arrives, what’s approved, what’s being fabricated, what’s on site, what’s installed. Visibility creates accountability.

Understand that only fifteen percent of projects do this right. That means eighty-five percent are failing at something that makes or breaks schedule success. You can be in the fifteen percent by treating procurement as supply chain management from design through closeout instead of submittal paperwork. Your choice.

As the podcast teaches, life is like an old time rail journey with delays, sidetracks, smoke, dust, cinders, and jolts interspersed occasionally by beautiful vistas and thrilling bursts of speed. The trick is to thank the Lord for letting you have the ride. Procurement will never be perfect. But you can manage it proactively instead of reactively. You can prevent crises instead of fighting fires. You can create flow instead of chaos.

On we go.

Frequently Asked Questions

Won’t multiple just-in-time deliveries cost more than bulk shipping?

Multiple deliveries might cost twenty thousand more. But bulk delivery costs two hundred thousand in movement, damage, delays, and blocked access. The math favors just-in-time once you account for all costs, not just shipping invoices.

How do we convince trades to deliver just-in-time when they prefer bulk delivery?

Show them the damage and movement costs from bulk delivery. Partner with them on delivery schedules that work for both parties. Build it into contracts. Trades prefer successful projects where their work flows smoothly.

What if superintendents say procurement meetings are office work not their job?

Superintendents need to know what materials are coming and when to coordinate field work. If they skip these meetings, crews stand around waiting for materials. Make it non-negotiable that field leadership attends weekly procurement reviews.

How detailed should procurement logs be to be effective tools not just paperwork?

Detail enough to track every scope from buyout through closeout with submittal dates, approval dates, fabrication dates, delivery dates, installation dates. Tied to Takt zones and sequences. Updated daily. Reviewed weekly by full team.

What’s the first step if our procurement tracking is currently a mess?

Create the log showing every scope. Tie it to your Takt plan showing when materials are needed. Get superintendents in weekly meetings. Start tracking from where you are now. Improve incrementally but start immediately.

 

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.

Design Flow in your Project First

Posted on by Danny Jiménez⁩
Read 23 min

You’re Starting Projects Without Flow and Wondering Why They Crash

Here’s the mistake killing your schedule before work even starts: you begin with a CPM schedule instead of planning flow into your project from the beginning. You create detailed activity sequences, establish logic, calculate float paths, and convince yourself this schedule will drive coordination and completion. Then you wonder why projects drift behind, why trades can’t maintain rhythm, why your completion rate hovers around 66 percent when it should be pushing 90. The problem isn’t execution. It’s that you never designed flow into the project from day one.

Think about what happens when you show up needing help. You want Scrum implementation. You want Last Planner working. You want better team capacity and health. You want to recover the project because you’re behind schedule. Every single one of those needs would be solved if you had begun the project with a Takt plan that designed flow from the beginning. Instead you built on CPM foundation that hides problems, creates chaos, and requires heroic effort to maintain any semblance of rhythm.

The data proves this pattern. One company implementing Takt planning went from 66 percent on-time completion to 89 percent and rising within a year. Not because they tracked CPM metrics better. Not because they pushed trades harder. Because they planned flow from proposal phase, schematic design, and design development before ever creating detailed schedules. They stabilized 75 percent of their projects with rhythm and flow so they could focus on the 25 percent that genuinely needed adaptation and response to change.

The Pain of Trying to Recover Flow You Never Designed

You’ve experienced this frustration on projects that start behind and stay behind. The CPM schedule shows completion achievable if everything goes perfectly. Reality shows you’re months behind with no clear path to close the gap. Scheduling consultants provide float trends and graphics saying your schedule is in trouble. And you’re left wondering: who’s going to fix this? How do we recover?

That’s what happens when you start without flow. You can measure CPM metrics all you want. You can hire consultants to analyze your critical path. You can generate recovery schedules and updated baselines. But none of that fixes the fundamental problem that you never designed flow into the project. CPM metrics show you there’s trouble. They don’t tell you how to fix it. Because you can’t fix a CPM problem with CPM methods.

When projects need recovery, what actually works? You stabilize the site. You implement Takt planning to create rhythm. You add Last Planner to coordinate trades weekly. You Scrum teams through critical sequences. You establish morning huddles for daily alignment. You create flow that never existed because you started with activity lists instead of production rhythm. And you realize all of this pain could have been prevented by planning flow from day one.

I’ve seen this pattern across over a hundred projects implementing Takt. Companies call when projects are in trouble. They want help recovering schedule, improving team health, advancing toward completion. And every single time I wish they had begun with a Takt plan because recovery would be unnecessary. On a $180 million project, we used Acumen 360 to analyze the CPM schedule and identify recovery paths. The software showed activities to accelerate. But it was Takt planning, production rhythm, and flow in the core system that actually recovered the project by getting cores done a month earlier and moving steel up. The rhythm and flow saved it. Not CPM adjustments.

The System Starts Projects With CPM That Prevents Flow

Here’s what I want you to understand. The construction industry systematically starts projects with scheduling methods that prevent flow instead of creating it. We begin with CPM in proposal phase, add detail through design, and launch construction with schedules optimized for reporting to owners instead of driving rhythm for trades. We create activity-based sequences that slam everything left with false urgency. And we wonder why projects can’t maintain flow when we never designed it in.

Even when people say “we have to use CPM because the owner requires it,” they’re missing the point. CPM was designed to be high level. It was designed to operate with correct float paths at level three detail maximum. What we’re actually doing is creating massively detailed schedules where commissioning isn’t detailed properly, float paths are wrong, complex sequences haven’t been pull planned, and the whole thing is so cumbersome you can’t use it or report on it effectively. We’re not even using CPM the way the system was designed. We’re bastardizing it into something that prevents the flow we need.

Here’s what happens when you start projects right by planning flow from the beginning:

  • Create Takt plan in proposal phase showing overall rhythm and duration
  • Develop Takt through schematic design and design development before detailed CPM
  • If owner requires CPM, build it from the Takt structure so both hold each other accountable
  • Launch construction with flow already designed, not activity lists requiring heroic coordination
  • Stabilize 75 percent of project with production rhythm so teams can focus on the 25 percent requiring adaptation
  • Reduce manpower and material counts because flow creates efficiency pushing never achieves
  • Move from 66 percent on-time completion to 89 percent and rising by designing flow first
  • When problems emerge, you’re recovering flow deviations not creating flow from scratch

The argument against this is always “but we need CPM for owner reporting” or “CPM is industry standard.” Fine. I’m not even telling you to eliminate CPM entirely if you absolutely must use it. What I’m saying is at minimum start with and hold it accountable with a Takt plan. Create the flow foundation first. Then build whatever detailed reporting schedule the owner demands on top of that foundation. But never, never start with CPM and expect to create flow afterward.

When scheduling consultants show your CPM is failing, they might recommend recovery schedules. But you’re not going to recover with those methodologies. You’ll either use pull planning and Last Planner to drive your critical path and gain time, or Scrum to accelerate critical sequences, or Takt planning to get everyone on rhythm and finish on time. But you’re not going to keep your schedule hidden in a silo and expect trade partners to magically improve coordination. Flow requires designing it from the beginning, not hoping it emerges from detailed activity lists.

Building Projects on Flow Foundation From Day One

Let me walk you through what planning flow from the beginning actually means practically. First, in proposal phase when you’re estimating costs and duration, create a one-page Takt plan showing overall rhythm. How many zones? What’s the production rate per zone? What trades work in what sequence? What’s the realistic overall duration based on flow, not just slamming activities left? This single page tells you more about project reality than hundred-page CPM schedules.

Second, through schematic design when you’re developing the approach, refine that Takt plan. Adjust zone sizes based on building layout. Confirm trade sequences based on design decisions. Validate production rates based on crew availability and complexity. Keep it visual, keep it simple, keep it focused on flow. This is when you’re designing how work will actually flow through the building.

Third, during design development before you create detailed CPM if required, finalize the Takt plan with trade partner input. Get their confirmation on crew sizes, production rates, sequence logic. Make sure manpower and material counts align with the rhythm you’re planning. This collaborative planning creates buy-in and reality-checks your assumptions before you commit to detailed schedules that are expensive to change.

Fourth, if you must create CPM for owner requirements, build it directly from the Takt plan structure. The Takt zones become schedule areas. The trade sequences become activity logic. The production rates become durations. Now your CPM and Takt hold each other accountable instead of contradicting each other. When CPM shows you’re behind, you check Takt rhythm. When Takt shows deviation, you update CPM accordingly.

Fifth, launch construction with flow already designed into every aspect of planning. Trade partners know their zones, sequences, and production rates. Weekly work planning coordinates the rhythm. Daily huddles maintain it. The schedule serves the flow instead of fighting it. And when problems emerge, you’re recovering deviations from designed flow instead of trying to create flow for the first time while also solving problems.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. We work with builders who understand that planning flow from the beginning isn’t optional if you want completion rates above 66 percent.

The species that survive aren’t the strongest or most intelligent but the ones most responsive to change. Companies that succeed adapt and respond to market conditions. But here’s the key: you can’t respond effectively to change when your entire project is chaos. By creating stability with flow on 75 percent of your work, you free up capacity to properly focus on areas that do need adaptation. Remove unnecessary variation through Takt rhythm so you can respond to necessary changes, owner requests, and inevitable challenges without everything becoming emergency.

The Challenge: Start Your Next Project With Takt

So here’s my challenge to you, and I’m pleading with you, begging you, coaching you with love not whining. Read these books if you want to get good at scheduling: The Goal by Eliyahu Goldratt, Lean Builder about Last Planner system, Scrum: Getting Twice the Work Done in Half the Time by Jeff Sutherland, and Elevating Construction Takt Planning. If you do that, you’ll have the full spectrum of scheduling knowledge. And if you must use CPM, study that too so you at least use it the way it was designed instead of the bastardized detailed mess most companies create.

Then on your next project, create the Takt plan in proposal phase. Call me if you need help. I’ll give you templates and advice for free because I want you to start right. Read the book, get familiar with the system, and create your CPM schedule from that foundation if required. When you set projects up this way, you’re positioned to win. It’s the single biggest thing you can do to avoid crash landing. You have the right overall duration, the flow is designed in, manpower and material counts are realistic, and you move forward productively.

Please, please, please begin your projects with Takt. Even if you think “we’ll never stop using CPM,” at minimum make sure you start with Takt and hold CPM accountable to it. The company that went from 66 percent to 89 percent on-time completion proves this works. The $180 million project recovered through rhythm and flow proves CPM adjustments alone don’t fix problems. Every project I help recover would have been easier if they started with Takt.

Stop trying to create flow in projects that were designed without it. Stop hoping CPM detailed schedules will magically coordinate trades into rhythm. Stop accepting 66 percent on-time completion when 89 percent is achievable by planning flow from the beginning. Design it in from day one, maintain it through execution, and recover deviations when they occur instead of trying to create what was never there.

As Charles Darwin taught, it’s not the strongest species that survive but the ones most responsive to change. Plan flow so you have the stability to respond when change comes.

On we go.

Frequently Asked Questions

What if our owner absolutely requires CPM from proposal phase and won’t accept Takt plans?

Create the Takt plan first for your own planning, then build the CPM from that structure. The owner gets their CPM reporting tool. You get the flow foundation that actually drives coordination. Both schedules hold each other accountable instead of contradicting.

How long does it take to create a Takt plan compared to CPM schedule?

Initial Takt plan takes hours, not weeks. One-page visual in proposal phase. Refinement through design. Final version with trade input before construction. Total investment is fraction of CPM development time, and the clarity you gain makes everything else easier.

Won’t trade partners resist Takt if they’re used to CPM?

Trade partners prefer Takt once they experience it because rhythm is visible, sequences are clear, and coordination makes sense. CPM confuses them with activity codes and logic they can’t see. Takt shows exactly when and where they work.

What if we’re mid-project with CPM already and can’t start over with Takt?

Create Takt plan now for remaining work. Use it to recover rhythm and coordinate completion. Even partial Takt implementation improves flow. Then commit to starting next project right from the beginning.

How do we measure success when moving from CPM to Takt-first planning?

Track on-time completion percentage before and after. The company in the example went from 66 percent to 89 percent within a year. Also measure schedule changes, manpower stability, and team feedback on coordination clarity.

 

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.

Field Representation in Leadership terms

Posted on by Danny Jiménez⁩
Read 25 min

Your Leadership Team Is All Office and No Field (And It’s Killing Your Product)

Here’s the question that reveals whether your company is optimized for what actually matters: Who’s on your leadership team? If the answer is all project managers, operations directors, and executives from the office side with zero field superintendents in executive positions, you’ve built an organization that doesn’t represent the only activity that creates value: putting work in place. You’ve optimized for project management while deprioritizing the actual product you sell. And your best field people know it, which is why they’re leaving for companies that actually value what they do.

Think about what customers actually pay for. They don’t pay you for project management. They don’t pay you for procurement or finances or preconstruction services or RFI processing or submittal reviews. Those things are necessary, yes. But they’re non-value-add. The only time you actually add value, the only time you create what customers pay for, is when you put work in place. When trades install mechanical systems. When concrete gets poured. When walls get framed. That’s the value. That’s the product. Everything else supports that product but isn’t the product itself.

So explain why the most important part of your business, the only part that adds value, is not represented on your leadership team. If superintendents and field positions deliver the actual product, why are all your executives from the office side? Why is field leadership capped at general superintendent level while project management scales to VP and executive roles? That imbalance tells everyone exactly what your company values. And it’s not the work that customers pay for.

The Pain of Decisions Made by People Who Don’t Do the Work

You’ve experienced this frustration from the field side. Your leadership team decides to implement new software that makes project engineers’ jobs easier but slows down superintendents’ daily reports, safety documentation, and field management. They choose systems optimized for office workflows that create friction for field workflows. And when you push back, they don’t understand why you’re resisting “improvements” because nobody on that leadership team actually lives in the field reality where those systems destroy productivity.

That’s what happens when leadership teams don’t represent the field. They make decisions about the product without understanding how the product gets built. They optimize for office convenience instead of field effectiveness. They focus on financial targets and project management controls while disconnecting from the craft and the workers who actually create value. And field positions see clearly that there’s no long-term career path for them because leadership doesn’t value what they do enough to give them seats at the table.

The pattern is predictable across companies without field representation. Entry-level people who would have been excellent superintendents get pushed toward project management because that’s where the career progression exists. Your best field people get dispatched constantly to fix troublesome projects instead of being in positions where they prevent problems through leadership. Project managers operate without the accountability partnership of having peer superintendents at the executive level who understand field reality. And gradually, you become brokers managing contracts instead of builders delivering work.

I’ve observed this across decades of working with different companies. The pattern is clear. Companies with field representation on leadership teams stay connected to craft, make better decisions about systems and processes, create fulfilling career paths that retain excellent field people, and maintain the accountability balance between office and field. Companies without field representation become project management heavy, lose connection to how work actually happens, and wonder why their best superintendents leave for competitors who value field leadership.

The System Creates Office-Heavy Leadership That Ignores the Product

Here’s what I want you to understand. The construction industry systematically creates leadership teams that don’t represent the actual product being delivered. We promote project managers to director and VP roles while capping field positions at general superintendent. We create career paths that incentivize talented people to move from field to office because that’s where executive opportunities exist. And we build organizations where the people making strategic decisions have never lived in the daily reality of putting work in place.

Let me walk you through the twelve consequences of not having field representation on leadership teams:

  • You become disconnected with the craft, nobody at the executive level understands the workers’ reality anymore •
  •  You make decisions that don’t deal with the product itself because you’re optimized for managing contracts, not building things 
  •  You de-incentivize field positions from being remarkable because everyone sees there’s no long-term career path that values their expertise 
  •  You push entry-level people toward project management when they might have loved being superintendents because that’s where growth opportunities exist •
  •  You become project management and corporate controls heavy, creating bureaucracy that slows field effectiveness • You stop listening to how things really work on construction projects because nobody in leadership experiences that reality daily •
  •  You lose the accountability partnership of PM and superintendent together at leadership level where they should be peers balancing each other •
  •  You begin to become brokers instead of builders, managing paperwork and contracts instead of understanding how work gets installed • 
  • You focus too much on finances and not enough on the product quality and installation effectiveness that create those finances •
  •  Craft and field workers know they’re unrepresented and feel disconnected and unfulfilled, which drives turnover of your best people • 
  • You dispatch your best field leaders to fix bad projects constantly instead of having them in executive positions where they prevent problems systemically • 
  • Field teams struggle because they need field leaders involved in leading the field, not just office leaders managing from distance

During a recent scheduling training, we did an exercise about communication. We showed how information flows from weekly work planning meetings to afternoon foreman huddles to morning worker huddles. The point was getting information all the way to the end of the line, to the actual workers installing work. When we compared typical approaches that trust foremen to communicate everything versus implementing systematic huddles that ensure information reaches everyone, it became obvious that optimizing for the field requires understanding field reality. You can’t design those systems from offices if nobody in leadership actually lives in the field.

Building Leadership That Represents What Actually Matters

Let me walk you through what changes when field positions join leadership teams at executive levels. First, strategic decisions get made by people who understand both office and field reality. When you’re choosing software systems, you have superintendents at the table who can say “that slows us down in the field even if it helps project engineers.” When you’re setting goals and priorities, you have field leaders who ensure those goals optimize for putting work in place, not just managing contracts.

Second, you create career paths that retain excellent field people. When talented superintendents see peers in VP and executive roles, they know their expertise is valued enough to build careers around it. They don’t have to choose between staying in the field they love and advancing to leadership. They can do both. That retention of field expertise compounds over time into organizational capability that companies without field leadership can’t match.

Third, you maintain the accountability partnership between project management and field leadership at every level. Project managers and superintendents work as peers on projects. That peer relationship should scale to leadership where VPs from both sides balance each other’s perspectives. When only the PM side scales to executive level, you lose that balance and create organizations optimized for managing instead of building.

Fourth, you stay connected to craft and workers. When executives came from the field and maintain relationships with field teams, strategic decisions account for how those decisions affect the people doing the actual work. You don’t lose touch with the craft. You don’t make decisions that look good on spreadsheets but create chaos on sites. You optimize for the product because leadership understands and values the product.

Here’s what field representation in leadership looks like practically. Develop people from the field to be on your leadership team, not just as advisors but as actual executives with authority. Create position levels that take people from field engineer all the way to general superintendent and then to VP and executive positions. Invite senior field positions to executive leadership roles where they make strategic decisions, not just provide input. Hold project managers accountable for delivering value in the field while holding superintendents accountable for aligning with company processes. Model a fractal organization where the PM-superintendent partnership at project level mirrors the balance at leadership level.

I recently worked with a company that promoted a senior superintendent to general superintendent level with representation on the executive team. The change was immediate. Strategic discussions suddenly included field reality. Software decisions got vetted by people who actually use them daily. Career paths became clearer for field positions. And the accountability balance between office and field improved because both sides had peer representation at the top.

Why Optimizing Office Over Field Destroys What You Sell

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. We work with builders who understand that field representation in leadership isn’t optional. It’s how you optimize for the actual product you deliver instead of just managing contracts.

Think about the role of leadership teams. Provide challenging and prioritized goals. Eliminate organizational debt by creating business plans and organizations that work. Provide all needed resources to teams. Remove impediments identified by teams. Set up organizations focused on delivering maximum value and removing waste at every step. You can’t do any of that effectively if leadership doesn’t understand and represent the field where value actually gets created.

The current condition is leadership teams don’t represent the field. People know it. Your projects suffer because decisions optimize for office convenience instead of field effectiveness. Your good people leave for companies with field career paths. Your PMs would benefit from accountability and competition with peer field leaders at executive level. And you’re missing the perspective that matters most, understanding from people who actually do the work what systems and processes and priorities create excellent products.

Here’s the principle that should guide every construction company: comfort the workers, discomfort the staff. Your job is creating stable environments and respectful circumstances for workers installing work. If managers attend meetings, complete reports, preplan, and carry out inconvenient assignments, those duties are worthwhile if they provide stability and respect in the field for workers. The ultimate success is workers having stable environments, respectful conditions, tools and equipment they need, proper information, and suitable time to work at productive rates with good quality. You can’t optimize for that without field representation in leadership.

The Challenge: Put Field Leaders in Executive Roles This Year

So here’s my challenge to you. Develop people from the field to be on your leadership team. Just do it. Try it for one year. If it doesn’t work, tell me it failed. But I promise you it’s game changing if you have the right people. Stop capping field careers at general superintendent while promoting project managers to VP. Create parallel paths where field excellence leads to executive leadership just like office excellence does.

Invite senior field positions to executive level leadership positions where they make strategic decisions with full authority. Create interactions where you’re listening to the product side of your company, the field side, not just the contract management side. Stay connected to craft by having leaders who came from craft and understand it deeply. Make sure field positions are represented in your leadership groups with actual authority, not just advisory roles.

Improve conditions of workers as your top priority by having leaders who understand worker reality making strategic decisions. Build position levels that take people from field engineer to executive without forcing them into office roles. And recognize that if you hold teams accountable for quality, safety, schedule, and cost equally, your leadership team should be balanced equally between field and office perspectives that understand all four.

You are being wimpy leaders if your main priority is financial goals without field representation to ensure those goals serve the product. You are being wimpy leaders if you’re not strengthening and expecting high standards from field people who deliver your product. Build complete leadership that represents what you actually sell, work in place, not just the management systems that support it.

As Peter Drucker said, “Culture eats strategy for breakfast.” Your culture shows what you value through who sits at leadership tables. When only office positions reach executive level, you’re telling everyone field work doesn’t matter enough for leadership. Change that. Put field leaders in executive roles. Represent the product you sell.

On we go.

Frequently Asked Questions

Won’t field people in executive roles lack the business knowledge needed for strategic decisions?

Field leaders at senior levels already understand business fundamentals from running projects. Add strategic business training just like you train project managers in leadership skills. The field expertise they bring is harder to teach office leaders than business knowledge is to teach field leaders.

What if we don’t have field positions ready for executive roles right now?

Start developing them immediately. Create position levels and career paths that show field excellence leads to executive leadership. Identify high potential superintendents and invest in developing them toward VP roles now.

How do we balance field and office representation without making leadership teams too large?

You don’t need equal numbers, but you need actual representation with authority. If you have three VP positions, at least one should be field. The balance comes from having both perspectives at the table.

Won’t field leaders struggle with the political and strategic aspects of executive roles?

Field leaders who’ve run large projects already handle politics and strategy at project scale. The skills transfer to company scale with proper development and support, just like project managers need development for executive roles.

What’s the first step if our company has never had field representation in executive leadership?

Invite senior field positions to strategic discussions as participants with voice. See what changes when field perspective shapes decisions. Then create one executive level position specifically for field leadership and promote someone excellent into it.

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.

No Meeting Days

Posted on by Danny Jiménez⁩
Read 22 min

Your Team Is Working 55 Hours and Producing 14 Hours of Value

Here’s the calculation that should terrify every construction leader: Your project engineer works 55 hours per week. After you account for meetings, context switching, unnecessary work that could be outsourced, answering interruptions, and babysitting complex project management systems, that engineer gets 12 to 14 hours of actual production work done. Not per day. Per week. You’re paying for 55 hours and getting 14 hours of value. The other 41 hours evaporate into waste that nobody tracks and everyone accepts as normal.

Think about what that means for your projects. The people responsible for submittals, RFIs, coordination, and field support spend 75 percent of their time on activities that don’t produce value. They’re not lazy. They’re not inefficient. They’re drowning in meetings, context switches, and interruptions that prevent them from focusing long enough to actually complete work. And your response is typically to add more people to compensate for the productivity loss instead of eliminating the waste that’s destroying everyone’s capacity.

This isn’t theoretical. I calculated this at a cancer center project by analyzing meeting systems, context switching patterns, and necessary but non-value-add work that could be outsourced. The math is brutal but accurate. And every project engineer reading this knows exactly what I’m talking about because they live this reality every week. They show up Monday morning with a task list, get pulled into meetings and interruptions all week, and finish Friday wondering why nothing got done despite working exhausting hours.

The Pain of Constant Interruption Disguised as Collaboration

You’ve experienced this frustration as a project engineer or superintendent. You start working on a submittal that requires focus and technical review. Five minutes in, someone stops by with a question. You answer, refocus, and get back into the submission. Ten minutes later, a meeting reminder pops up. You attend a coordination meeting that could have been an email. You return to your desk, try to remember where you were in the submittal, and just as you’re regaining focus, your phone rings with a field question that takes twenty minutes to resolve.

That’s what happens when organizations confuse activity with productivity. They schedule meetings constantly because meetings feel like work. They encourage open communication that becomes constant interruption. They create complex systems that require multiple people to touch every task. And they wonder why nothing gets finished despite everyone being busy all the time. Because being busy doesn’t mean being productive when 75 percent of time evaporates into waste.

The context switching alone destroys productivity in ways most leaders don’t understand. Research shows it takes 5 to 15 minutes to switch mental context from one task to another. For people who struggle with focus, it can take 30 minutes. Every time you stop working on a submission to answer a question, attend a meeting, or handle an interruption, you lose at least 5 to 15 minutes of cognitive capacity just getting back into flow state. Those minutes add up to hours, which add up to the 41 hours per week that disappear.

Here’s a chart that Felipe Engineer showed me from his Scrum training that quantifies this perfectly. When you work on one project with full focus, you get 100 percent productive time. Two simultaneous projects drops you to 40 percent each with 20 percent waste. Three projects: 20 percent each with 40 percent waste. Four projects: 10 percent each with 60 percent waste. Five projects: 5 percent each with 75 percent waste. The waste isn’t just additive. It’s exponential as context switches compound.

The System Creates Meeting Culture That Destroys Focus

Here’s what I want you to understand. The construction industry systematically creates meeting cultures that destroy the focus time required for actual production work. We schedule coordination meetings, owner meetings, corporate meetings, safety meetings, BIM meetings, and status meetings until calendars are blocked solid. We convince ourselves these meetings are necessary collaboration when most could be eliminated, shortened, or handled asynchronously without destroying everyone’s capacity to think.

After discovering the 12 to 14 hour reality at the cancer center, I started recommending no meeting days to every client. And yes, you still have the morning worker huddle and afternoon foreman huddle. But for coordination meetings, owner meetings, office meetings beyond the daily 15 minute team huddle, there are no meetings. It’s a production day where people are expected to come in and do focused work. And it transforms productivity immediately.

Even in my own business, I experience this pattern. Monday, Tuesday, Wednesday filled with meetings and travel, I accomplish some things but customers wonder where I am. Thursday and Friday as production days with no meetings, I get completely caught up. Every week, teams need at least one or two production days with no meetings where they focus and execute the work that meetings supposedly coordinate.

The resistance to no meeting days reveals what organizations really value. People say “I have corporate safety visiting certain days and need to accommodate them.” No, you don’t. Corporate positions exist to support you. You need to take care of your team first. “But our owner requires weekly meetings.” Your owner needs to be managed. No owner, whether they know it intentionally or not, wants you to fail based on their demands. They’ve paid you and expect you to do what’s right. Tell them respectfully that you need two days as no meeting days for success, then negotiate how to restructure and still create remarkable experiences for them.

Here’s what no meeting days look like practically:

  • Typically scheduled Wednesdays and Fridays, but adapt to project needs
  • Morning 15 minute huddle and afternoon foreman huddle continue for field operations
  • Zero coordination meetings, BIM sessions, owner meetings, or corporate visits unless genuine emergency
  • Everyone focuses on production work using one piece flow, finishing tasks before switching context
  • Outsource everything possible to keep teams small and focused on work only they can do
  • Corporate support schedules around production days, not the reverse
  • Owners get educated that these days protect project success, not prevent collaboration

The pushback reveals broken priorities. I’ve seen companies whose mission statements talk about creating remarkable experiences or happy environments. But those experiences only apply to customers at the expense of employees. The best companies take care of their people first, and happy people take care of customers. That’s how it actually works. Companies that prioritize customers first will burn projects to the ground trying to finish for the customer at the expense of employees, resources, and families.

Why Focus Time Isn’t Optional For Production

Let me walk you through why no meeting days transform productivity beyond just reducing meeting time. First, they eliminate the context switching waste that destroys cognitive capacity. When people know Wednesday is a production day, they batch deep work for that day instead of trying to squeeze focus between meetings. They finish tasks completely using one piece flow instead of working on five things 5 percent each with 75 percent waste.

Second, they create predictability that enables planning. Project engineers know they can schedule technical reviews, submittal work, and coordination drawing reviews for production days when they’ll have uninterrupted time to think. They stop trying to do complex work in 20 minute increments between meetings, which is where errors happen and quality suffers.

Third, they force organizations to question which meetings actually matter. When you can’t schedule meetings two days per week, you quickly discover which ones were essential and which were just habits. Most coordination can happen asynchronously through collaborative tools. Most status meetings can be replaced with visual management systems. Most owner meetings can be consolidated into the days when meetings are allowed.

Fourth, they protect team capacity by outsourcing non-value-add work. When you’re serious about production days, you identify work that’s necessary but doesn’t require your team specifically. At DPR, we used V Construct for RFI posting, distribution, drawing updates, punch list collection, and tracking work that project engineers and managers didn’t need to do personally. Keep your team small and focused on value-add work. Outsource everything else at reasonable cost so your expensive talent isn’t wasted on administrative tasks.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. We work with builders who understand that focus time isn’t a luxury. It’s how you get 40 hours of production from a 55 hour week instead of just 14.

Even in integrated project delivery big rooms, they have production pods, breakout areas, and places where teams go to focus. They have clusters for design sprints with smaller teams. At DPR’s Phoenix office, the open workspace builds culture and communication. But production pods are spaces where if you’re inside, you’re expected to be left alone to focus. They even have nap rooms where mothers can nurse, people can take phone calls privately, or someone exhausted can rest. There’s a balance between collaboration and focus. No meeting days formalize that balance.

The principle is simple: balance and stability. Teams cannot be filled with waste, cannot be overburdened, and cannot work unevenly to the detriment of schedules and families. Master builders anticipate and manage the balance and stability of teams constructing projects. That includes protecting them from meeting overload that destroys their capacity to produce.

The Challenge: Implement No Meeting Days Starting Next Week

So here’s my challenge to you. Implement no meeting days starting next week. Pick two days, typically Wednesday and Friday. Synchronize with corporate and tell them their support needs to cater to your production needs, not disrupt them. Have the conversation with your owner explaining that these days protect project success. Then stick with it for at least six weeks and measure the difference.

Track how much production work actually gets completed on meeting days versus no meeting days. Ask your team how focus time affects quality, stress, and ability to go home at reasonable hours. Watch what happens when people can finish tasks completely instead of context switching between five things with 75 percent waste. The results will prove that no meeting days aren’t optional if you want sustainable productivity.

Create meeting matrices and signage that formalize no meeting days. Make it visible to everyone including corporate and owners. Protect these days with the same vigor you protect safety requirements. Because focus time is about protecting people from the burnout that comes from working 55 hours while only producing 14 hours of value.

Right now your team gets 12 to 14 hours of production time per week. With no meeting days, you could get 24 or 28 hours. That difference transforms project performance and team welfare. It lets people go home instead of working endless hours compensating for waste. It produces better quality because people have time to think instead of rushing between interruptions. And it proves you value people enough to protect their capacity instead of just extracting their time.

As Peter Drucker wrote, “There is nothing so useless as doing efficiently that which should not be done at all.” Most meetings shouldn’t be done at all. Stop doing them efficiently and start protecting the focus time that creates actual value.

On we go.

Frequently Asked Questions

What if a corporation insists on meeting during our no meeting days?

Corporate exists to support project success, not prevent it. Educate them that no meeting days protect productivity that makes their goals achievable. If they resist, show them the 12 to 14 hour data and ask if they want to fix the problem or keep creating it.

Won’t owners refuse to accommodate no meeting days?

Most owners care about project success more than meeting frequency. Explain that these days ensure the team has capacity to deliver what the owner actually wants, quality work on time. Frame it as protecting their investment, not limiting their access.

How do we handle genuine emergencies that require meetings on production days?

Genuine emergencies are rare and obviously warrant breaking the rule. But examine whether issues labeled “emergencies” are actually just poor planning or lack of discipline. Most urgent items can wait one day until the next meeting day.

What if our calendar is already full and we can’t find two full days without meetings?

Then your schedule proves the problem exists and no meeting days are essential. Cancel and consolidate ruthlessly. Most meetings can be eliminated, shortened, or handled asynchronously. Protecting focus time requires saying no to requests that destroy it.

Won’t no meeting days reduce collaboration and create information silos?

Collaboration happens in the meetings you keep and through asynchronous tools. What reduces collaboration is exhausted people with no capacity to think clearly because constant meetings prevent them from doing work that meetings supposedly coordinate. Focus time enables better collaboration, not worse.

 

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.

Elevating Construction Superintendents

Posted on by Danny Jiménez⁩
Read 23 min

The Moments That Make Up Eternity

Here’s the question that reveals what you’re actually building: When you’re at the end of your career looking back, what will you remember? Will you remember the RFIs you answered? The submittals you processed? The schedules you managed? Or will you remember the moments when you reached down and pulled someone up who was about to fall? When you invested everything you had to help someone else succeed? When you chose people over projects and legacy over immediate results?

I’ll tell you what I’ll remember forever. A woman at a bootcamp facing a twelve-foot wall. She weighed over 350 pounds. The team was pushing her up from below. I was the only person at the top who could help haul her over. And I could see in her face that she knew she was going to fall. She knew this was impossible. She knew she was going to hit the ground and get hurt badly. But she had decided to trust her team anyway despite that knowledge.

That moment when her focus shifted from the ground to my eyes. When she decided I was her only hope and reached her hand up to me. When I made the determination that no matter what, she was getting over that wall. Even if it meant going down with her. Even if it required every ounce of strength I had left. She was not falling because I was going to give everything I had to get her over that wall.

That’s not just a training story. That’s the entire mission of Elevate Construction. By accident of being tall, by luck of being thrown into trainings with the best builders in the industry, by happenstance of getting over walls first in some cases, my vision is to help everyone else along their way. No matter what. No matter who they are or what challenges they face. We’re all going over this wall because we know how to do it and we’re going to help each other get there.

The Pain of Building Projects Without Building People

You’ve experienced this emptiness. You finish a project. It came in on time, under budget. The owner is happy. Your company celebrates. And somehow it feels hollow. Because at the end of the day, what did you actually accomplish? You moved materials around. You coordinated work. You managed a schedule. And in five years, nobody will remember any of it unless you also transformed the people who worked on that project.

That’s what happens when you measure success by projects completed instead of people developed. You optimize for outcomes that don’t matter eternally. You chase metrics that look good on resumes but feel empty in your soul. You build things that will eventually be demolished while missing opportunities to build people who will impact generations.

Think about what you actually remember from past projects. Not the technical details. Not the submittal sequences or the schedule logic. You remember the foreman you mentored who became a superintendent. You remember the laborer you taught English to who eventually became a project manager. You remember the young engineer you invested in who now runs their own company. Those are the moments that mattered. Everything else was just logistics.

The construction industry trains us to think projects are what matter. Completing work on time and budget. Hitting milestones. Delivering to owners. And all of that is necessary. But it’s not sufficient for a life well-lived. Because we will never remember the RFIs. We will never remember the submittals. We will never remember the management mechanics. We’ll remember the moments when we helped someone achieve something they thought was impossible.

The System Rewards Projects Over People

Here’s what I want you to understand. The construction industry systematically rewards project completion over people development. We promote based on how many projects you’ve finished, not how many people you’ve transformed. We celebrate schedule performance, not superintendent growth. We measure success by dollars managed, not lives changed. And that creates careers full of accomplishments that feel empty because we optimized for the wrong outcomes.

But here’s the truth that defeats that logic: behind every job, every team, every success are people. Behind those people are families. Behind those families are children. Behind those children are hundreds and thousands of descendants who will be affected by what we do today. When you help someone succeed, you’re not just changing one life. You’re changing entire family trees. That’s the leverage that projects alone can never provide.

Think about the Elevating Construction Superintendents book now available on Audible, Kindle, and paperback. Someone left this review: “This is truly the best educational tool I have ever had the pleasure to learn from throughout my career in construction. All of the best skills are laid out in here that I have admired in great supers I’ve worked with.”

That book exists because I spent seven years flying around the country over 500 times teaching field engineers, observing superintendents, distilling lessons learned from the best builders in the industry. It exists because at a research laboratory project, we finished on time and under budget with a great team where everybody made career progress. And at the end, I realized all the information was scattered. It needed to be in one place so people could access what I’d been privileged to learn.

That book represents the decision to give others what I was given first. Not because I’m good or righteous. Because I made a choice. I tanked a huge retirement fund to start this business. Everything is now invested in helping others succeed. Because I had a moment at a wall where someone trusted me with their hand, and I decided right then that for the rest of my life, I would help everyone else over whatever walls they’re facing.

Building Legacy Instead of Just Projects

Let me walk you through what it means to build people instead of just completing work. First, you have to accept that the moments you remember aren’t the management moments. They’re the human moments. When grown men with beards and tattoos come up crying saying you saved their marriage. When someone tells you they’ve never spent this much time with their kids. When people say their project is going excellent and this training changed their life. Those are paydays. That’s why we’re here on earth. That’s the legacy we’re attempting to leave.

Second, you have to understand that cultural creation determines rise and fall more than anything else. Will and Ariel Durant wrote that in The Lessons of History—civilizations rise and fall based on their culture, not just their technical achievements. What is the culture of superintendents? Is it command and control that’s been rightly demonized? Or is it something better that we’re building together through respect for people and commitment to developing the next generation?

Third, you have to give without expecting return. I share information I was given first. I teach what I learned from mentors. I pass on training I received from companies that invested in me. Not to get credit or recognition, but because that’s how knowledge compounds across generations. When you help someone over the wall, you enable them to help the next person. That’s how industries transform.

Here’s what building legacy looks like in practice:

  • Invest in people even when it costs you time and resources because that investment compounds eternally
  • Remember that behind every worker is a family whose future depends on whether we develop that person or just use them
  • Measure success by lives changed and people developed, not just by projects completed and budgets met
  • Share knowledge freely because you were given knowledge first, and passing it forward is how the industry improves
  • Make the decision that no matter what, you’re helping others succeed even if it requires everything you have

These aren’t soft extras you add when projects are going well. These are the foundations that determine whether your career mattered or just happened.

Why Moments Are the Molecules of Eternity

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. We work with builders who understand that the purpose of building projects is building people, and that legacy is measured by hands reached down to help others up, not just by structures completed.

Think about the wall story one more time. I wasn’t the person directing traffic. I wasn’t the leader of that exercise. But I was first over the wall and in position to help. And when someone needed help who was about to fall, I made the decision that she was getting over that wall no matter what. That moment of connection when she trusted me with her hand created a bond I’ll never forget. And it represents every interaction we have at Elevate Construction—reaching down to help people over walls they think are impossible.

Moments are the molecules that make up eternity. Not projects. Not accomplishments listed on resumes. Moments when you chose people over convenience. When you invested in someone’s growth instead of just extracting their labor. When you helped them believe they could do something they thought was impossible and then gave everything you had to make sure they succeeded.

The vision of Elevate Construction is that field builders can be more effective, lead better, and live remarkable lives. Not just complete more projects or manage bigger budgets. Actually transform their effectiveness, their leadership, and their lives. Because if we don’t have enough time to bless other people’s lives, we’re just wasting our time. We’re optimizing for outcomes that won’t matter when we look back.

The Challenge: Choose One Person This Week

So here’s my challenge to you. This week, choose one person to invest in. Not because it advances your project. Not because it makes your job easier. But because helping that person succeed is the legacy you want to leave. Maybe it’s teaching a laborer English. Maybe it’s mentoring a field engineer toward becoming a superintendent. Maybe it’s helping someone believe they can do something they think is impossible.

Reach down your hand. Make the commitment that no matter what, you’re helping that person succeed. Give them what you were given first. And understand that the moment you create there will matter more than any submittal you process this week. That’s not diminishing the importance of doing good work. That’s recognizing that good work serves people, and when we forget that, we lose what actually matters.

Share the Elevating Construction Superintendents book. Share this podcast. Not for my benefit, but so more people can access information that helps them succeed. Rate it well so more people see it. Tell others about it. Because every person who reads it and transforms their effectiveness is another hand reached down to help someone else. That’s how knowledge compounds. That’s how industries transform. That’s how legacies get built.

Until we get that this is all about people, we don’t get it. That’s not criticism. That’s invitation. An invitation to understand that your career will be measured by people helped, not projects completed. By families preserved, not just schedules met. By lives transformed, not just budgets managed.

As Maya Angelou wrote, “People will forget what you said, people will forget what you did, but people will never forget how you made them feel.” The moments you create when you help someone over a wall they think is impossible—those are the molecules that make up eternity.

On we go.

Frequently Asked Questions

How do I balance helping people develop with the pressure to complete projects?

The pressure to complete projects exists because of how we measure success. But projects completed without people developed just creates more pressure next time because you haven’t built capacity. Investing in people isn’t separate from completing projects. It’s how you complete projects sustainably instead of just surviving them.

What if I don’t feel qualified to mentor or develop others since I’m still learning myself?

You don’t need to be an expert. You just need to share what you were given first. The laborer I helped learn English didn’t need me to be perfect. They needed someone willing to invest time and care about their success. Share what you know. Help where you can. That’s enough.

Won’t focusing on people over projects hurt my career advancement?

Short-term thinking says yes. Long-term reality says leaders who develop people create more capacity, inspire more loyalty, and build better results than those who just manage projects. Companies eventually recognize that developing people is how you achieve sustainable excellence, not just temporary success.

How do I measure whether I’m actually helping people or just making myself feel good?

Ask them. The feedback from people whose lives changed tells you whether your investment mattered. But even simpler: are they achieving things they couldn’t before? Are they developing capabilities that compound over time? Measurement comes from transformation, not activity.

What if I invest in someone and they leave the company or the industry?

Then you’ve still changed their life and their family’s trajectory. The purpose isn’t retaining people for your benefit. The purpose is helping them succeed in whatever path they choose. If they leave better than they arrived, you’ve succeeded at what actually matters.

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.

Drifting into Failure, Part 1

Posted on by Danny Jiménez⁩
Read 22 min

Your Success Is Creating the Conditions for Catastrophic Failure

Here’s the uncomfortable truth about why disasters happen in construction. They don’t occur because things are going badly. They occur because things have been going well for so long that people stop looking for problems. Comfort creates complacency. Success breeds hubris. And somewhere in that drift from vigilance to confidence, organizations move slowly toward catastrophic failure without anyone noticing until it’s too late.

Think about the Challenger space shuttle explosion. The Deepwater Horizon oil spill. The Tenerife airport disaster where two 747s collided on a runway killing 583 people. None of these happened because people were reckless or incompetent. They happened because organizations drifted into failure over time. Small decisions that seemed acceptable in the moment accumulated into conditions where disaster became inevitable. And nobody spoke up loudly enough or early enough to stop the drift.

This concept of drifting into failure should terrify you if your project is going well right now. Not because success is bad, but because success creates the exact conditions that allow drift to happen unnoticed. When everything’s working, when schedules are on track, when incidents haven’t occurred in months, that’s precisely when you need productive paranoia. That’s when you need to ask whether your calm is genuine safety or just good luck that hasn’t run out yet.

The Pain of Not Knowing You’re Drifting

You’ve experienced this pattern without recognizing it. Your project runs smoothly for weeks. No major safety incidents. No schedule disasters. Quality looks good. And gradually, small things start slipping. Someone skips a step in the JHA process because nothing’s gone wrong lately anyway. A foreman doesn’t verify training credentials because this crew has been here for months. A superintendent doesn’t stop work when something feels off because production pressure is intense and nothing bad has happened yet from similar decisions.

None of these individual decisions feels catastrophic. Each one seems reasonable given the circumstances. Everyone’s doing their best with the information and incentives they have. But collectively, these small decisions are moving the organization toward conditions where catastrophic failure becomes possible. And because the drift happens slowly, nobody recognizes the danger until something terrible happens and everyone looks back wondering how they missed the obvious warning signs.

That’s what makes drift so dangerous. It’s not a sudden departure from safety. It’s a gradual normalization of deviation where what used to be unacceptable slowly becomes normal. You start by accepting small shortcuts under pressure. Then those shortcuts become standard practice. Then people forget there ever was a different standard. And nobody speaks up because nothing bad has happened yet and speaking up feels like overreacting.

The Challenger explosion happened because NASA gradually normalized the risk of O-ring failure in cold temperatures. Launch after launch succeeded despite O-rings showing concerning damage. Until one cold morning when the accumulated risk manifested catastrophically. Deepwater Horizon happened because BP gradually normalized risky decisions in pursuit of production targets. Small safety compromises accumulated until the conditions for disaster existed. Tenerife happened because multiple small communication failures and judgment calls accumulated on a foggy day until two planes occupied the same runway.

The System Creates Environments That Suppress Speaking Up

Here’s what I want you to understand. Drift into failure isn’t primarily about individual bad decisions. It’s about systems and cultures that create environments where people don’t speak up about concerns, where warnings get dismissed as overreacting, where production pressure overrides safety paranoia, and where success creates complacency that stops people from looking for problems.

Think about the structural conditions on your projects. Do you have environments where people are incentivized to speak up about concerns? Where you actually stop and fix work as you go? Where safety is genuinely prioritized over production when they conflict? Where people who raise issues are praised instead of labeled as difficult? Or do you have environments where people perceive that speaking up doesn’t matter, where warnings are seen as overreacting, where schedule pressure trumps safety concerns?

The bureaucracies on the Challenger launch, on the Deepwater Horizon rig, in the Tenerife airport tower didn’t intentionally create conditions for disaster. They created systems where human beings came to work, made decisions they thought were acceptable based on their perceptions and assessments, and interacted with those systems as best they knew how. But the systems weren’t designed to receive warnings effectively. The culture didn’t make it safe to stop work over concerns. The incentives favored production over paranoia.

That’s the pattern in construction too. We create project cultures where people aren’t incentivized to speak up. Where Lean ideas don’t get surfaced daily. Where we don’t actually stop to fix work as we go. Where we prioritize production over quality. Where people who raise safety concerns get labeled as obstacles to progress. And in those environments, nobody feels safe bringing up problems, and nobody perceives that speaking up would matter anyway. So risks accumulate silently until something catastrophic happens.

Jim Collins describes this in “How the Mighty Fall” as stage three: denial of risk and peril. Internal warning signals begin mounting, but external results remain strong enough to explain away disturbing data. Leaders discount negative information, amplify positive data, and put optimistic spins on ambiguous situations. People in power blame external factors for setbacks instead of accepting responsibility. The vigorous, fact-based dialogue that characterizes high-performance teams dwindles or disappears completely.

Building Cultures That Prevent Drift

Let me walk you through what prevents drift into failure. First, you need productive paranoia instead of complacency. Productive paranoia means staying vigilant about risks even when everything seems fine. It means checking JHAs and pre-task plans and silica exposure and fall protection not because incidents are happening but precisely because they’re not happening yet. It means asking whether your current calm represents genuine safety or just luck that hasn’t expired.

Unproductive paranoia is anxiety without action, fear without facts, worry without solutions. Productive paranoia is realistic assessment of data, honest evaluation of risks, and disciplined response to warnings even when everything seems okay. The difference matters enormously because unproductive paranoia creates paralysis while productive paranoia creates protection.

Second, you need values-based cultures where safety is genuinely core, not just something you say in orientations. When safety is truly a value, it doesn’t get sacrificed for production targets. It doesn’t get deprioritized when schedules are tight. People who raise safety concerns get praised, not criticized. And the organization stops work when conditions drift toward risk regardless of schedule pressure.

Third, you need Lean cultures where people speak up about problems daily. Where you stop to fix what bugs you instead of working around issues. Where every team member has authority to declare breakdowns when they see waste, confusion, or risk. Where the culture reinforces surfacing problems early instead of hiding them until they become crises.

Here’s what drift prevention looks like in practice:

  • Regular safety walks where leaders actively look for problems instead of just confirming everything’s fine • Systems that incentivize speaking up about concerns instead of punishing people who raise issues • Fact-based dialogue about risks that doesn’t get dismissed as overreacting or explained away with optimistic spins • Authority to stop work when conditions feel wrong, even if nothing bad has happened yet from similar conditions • Productive paranoia that questions whether calm represents safety or just accumulated luck

These aren’t extras you add when you have time. These are the disciplines that prevent the slow drift toward conditions where catastrophic failure becomes possible.

Why Comfort Is Your Biggest Risk Factor

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. We work with builders who understand that success and comfort create the exact conditions where drift happens unnoticed, and that productive paranoia is the only protection against slow movement toward catastrophic failure.

Think about Benjamin Franklin’s observation about distinguishing sunrises from sunsets. Painters throughout history found it difficult to tell the difference between the two because they look so similar. The only thing that distinguishes them is what comes next. After a sunrise comes a day full of activity, progress, connection, and hope. After a sunset comes darkness. What matters isn’t the moment itself but what follows.

That same principle applies to your current project state. If things are going well right now, that moment could be a sunrise leading to continued excellence or a sunset preceding disaster. What determines which it is isn’t the current state but what you do next. Do you use this period of calm to get complacent and stop looking for risks? Or do you use it to practice productive paranoia and ensure your success continues?

Most organizations treat calm as permission to relax vigilance. They stop checking as carefully. They normalize small shortcuts. They dismiss concerns as overreacting because nothing bad has happened lately. And that’s exactly how drift happens. The calm wasn’t a sunrise leading to continued success. It was a sunset preceding the darkness of catastrophic failure that accumulated while everyone was comfortable.

The Challenge: Get Productively Paranoid This Week

So here’s my challenge to you. Think about what you’re doing in your culture that either suppresses people speaking up and noticing risks, or encourages problems to surface early. Are things going well on your project right now? Great. Have you become complacent? Are you productively paranoid enough?

This week, do safety walks where you actively look for drift. Check whether JHAs are being followed or just signed. Verify whether pre-task plans are meaningful conversations or pencil-whipped paperwork. Ask workers what they’d do in an emergency and see if their answers match your procedures. Look at silica exposure, fall protection, and any area where small compromises might be accumulating silently.

Take every safety concern seriously. Don’t discount what people say. Don’t push things under the rug. Don’t explain away warnings with optimistic spins. If you’re comfortable and in your comfort zone, get out of it temporarily and find out whether you’re complacently allowing failure to drift into your organization without noticing.

Be productively paranoid. Because the alternative is drifting slowly toward catastrophic failure while thinking everything’s fine because nothing bad has happened yet. And by the time you realize you’ve drifted, it’s too late to stop what’s coming.

As Jim Collins writes, “The signature of mediocrity is not an unwillingness to change. The signature of mediocrity is chronic inconsistency.” Don’t let success create inconsistency in your vigilance. Stay productively paranoid. Prevent the drift.

On we go.

Frequently Asked Questions

How do I practice productive paranoia without creating fear or paralysis in my team?

Productive paranoia is fact-based risk assessment, not anxious worry. Frame it as discipline that protects people, not fear that paralyzes them. Look for actual risks systematically and address them methodically. The goal is informed vigilance, not constant panic. Teams respect leaders who take safety seriously enough to stay vigilant even when everything seems fine.

What if my team thinks I’m overreacting by looking for problems when things are going well?

Explain the drift into failure concept. Share examples like Challenger or Deepwater Horizon where disasters happened after long periods of success. Help them understand that comfort is when drift happens most easily. The teams that prevent catastrophic failure are the ones that stay vigilant during calm, not just during obvious crises.

How do I know if warning signals are legitimate risks or just noise?

Investigate every concern seriously enough to determine which it is. The Challenger engineers raised legitimate warnings that got dismissed as overreacting. The culture that dismisses warnings to avoid “overreacting” is the same culture that drifts into catastrophic failure. Better to investigate ten false alarms than miss one legitimate warning.

What if production pressure makes it impossible to stop and address every potential risk?

Then your production targets are creating drift toward failure. If the system only works by accepting risks that shouldn’t be accepted, the system is broken. Production achieved by accumulating risk isn’t sustainable success. It’s borrowed time before accumulated compromises manifest catastrophically.

How often should we do these productive paranoia checks?

Continuously. Make it part of daily leader standard work, not something you do quarterly when you remember. The drift happens gradually through small daily decisions. Prevention requires constant vigilance, not periodic audits. Build productive paranoia into how you operate, not something you add when you have time.

 

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.

Capability vs. Productivity, Feat. Adam Hoots

Posted on by Danny Jiménez⁩
Read 23 min

Your Safety Platform Wasn’t Built by Builders (And Workers Know It)

Here’s the problem with most construction safety technology. It was designed by people who’ve never stood in the field with mud on their boots trying to complete a pre-task plan on a tablet while trades are waiting to start work. People who think fourteen data fields and dropdown menus and dependencies are reasonable because they’re optimizing for data collection in corporate offices, not behavioral change on job sites. And workers know immediately when a platform wasn’t built by someone who understands their world.

Caitlin Frank knows this because she grew up on job sites, became a superintendent, and watched safety systems fail not because people don’t care but because the tools don’t work for how construction actually happens. She watched daily safety plans get pencil-whipped because nobody understood what was being asked. She saw workers show up with no idea whether they were trained for their tasks. She experienced the disconnect between who signed a COVID checklist and who was actually on the pre-task plan with no one cross-referencing to verify everyone went through proper procedures.

So she built eMod Safety with a principle most tech companies miss completely: if the platform creates so much friction that it interferes with real-time behavioral change in the field, you’ve failed regardless of how much data you collect. Because safety isn’t about compliance reports that look good in corporate offices. It’s about sending people home uninjured every single day. And that requires tools simple enough that superintendents and foremen actually use them when it matters, not systems so complex they get abandoned when schedule pressure hits.

The Pain of Safety Theater That Doesn’t Protect Anyone

You’ve seen this pattern destroy good intentions. Your company implements a new safety platform. It has incredible features. Robust data collection. Detailed analytics. Integration with your project management software. And within two weeks, field teams have found workarounds to avoid using it because clicking through dropdown menus and filling mandatory fields takes longer than the actual safety conversation they’re trying to have.

So what happens? Daily safety plans get pencil-whipped. Someone fills out the form quickly just to check the box without engaging with what’s actually happening on site. Workers show up and nobody verifies they’re trained for their tasks because the system for checking credentials is buried in a different module that requires three logins and a tutorial. Emergency procedures don’t get communicated clearly because the onboarding was fifteen minutes and a quick video that nobody retained.

And the dangerous part is everyone thinks they’re being safe because the compliance data looks good. Reports show high completion rates. Dashboards display green checkmarks. But ask workers what to do in an emergency and they have no idea. Ask foremen if they know which workers are qualified for which tasks and they’re guessing. The system optimized for data collection at the expense of actual protection, and nobody realizes the drift into failure until something terrible happens.

Caitlin describes this as the fundamental question her CEO always asks: are we safe or are we lucky? Before they created eMod, their company had great safety ratings. But they didn’t have transparency into whether those ratings reflected genuine safety practices or just good fortune that nothing bad had happened yet. The data looked fine, but they couldn’t see whether people actually understood procedures, whether training was effective, whether behavioral changes were happening in real time.

The System Creates Technology Field Teams Can’t Use

Here’s what I want you to understand. The construction technology industry systematically creates safety platforms that field builders don’t want to use. Not because field teams don’t care about safety, but because the platforms were designed by people optimizing for corporate data needs instead of field usability. They add features that look impressive in sales demos but create friction in actual daily use.

Think about the typical pattern. A technology company develops a safety platform. They talk to executives and safety directors who describe what data they wish they had. Then they build systems that collect that data through extensive forms, dropdown menus, required fields, and integration touchpoints. They never spend a week in the field watching how superintendents actually work, what information they need in the moment, or what level of complexity they can handle while managing fifty other priorities.

The result is platforms that require fourteen clicks to document a simple safety observation. Systems where you can’t figure out if everyone on site today has been through proper orientation without navigating three different modules. Tools that collect incredible amounts of data that goes to corporate offices where no real-time decisions get made and no feedback loops exist to drive actual behavioral improvement.

Caitlin built eMod differently because she’s a superintendent who understands field reality. She knows that if a platform interferes with real-time human interaction about safety, you’ve lost. She knows that workers need to understand immediately who to contact in an emergency, where to go, what procedures to follow. She knows that superintendents need instant visibility into who’s trained for what tasks without navigating complex interfaces. And she knows that feedback loops matter infinitely more than data warehouses.

The platforms built by field builders look different. They’re simpler. They focus on the information that drives decisions today, not comprehensive data collection for future analysis. They make it faster to do the right thing than to skip it. And they create transparency that helps teams see drift before it becomes disaster.

What Field-Builder-Designed Safety Actually Looks Like

Let me walk you through what changes when superintendents design the safety tools instead of corporate tech teams. First, onboarding becomes an opportunity for human connection instead of paperwork processing. Caitlin talks about how construction misses the moment when workers are a captive audience during orientation. Instead of creating meaningful social connection and actually teaching emergency procedures, we rush through fifteen minutes and a video, slap a sticker on them, and send them to the field where they can’t answer basic questions about what they just learned.

Field-builder-designed onboarding recognizes that moment matters. It creates systems where orientation is memorable, where workers actually retain emergency contacts and procedures, where the social group forms in ways that make speaking up about safety concerns feel natural instead of risky. Because builders know that safety culture gets established in those first interactions, not through compliance forms filled out later.

Second, daily safety plans become conversations instead of paperwork. The current condition is plans get pencil-whipped because they’re disconnected from actual work. Workers fill forms that nobody references again. But when builders design the system, daily safety plans connect directly to who’s on site, what tasks are happening, what hazards exist today specifically. The plan becomes a tool for the actual safety discussion, not a compliance document that gets filed and forgotten.

Third, training verification becomes instant and clear. Superintendents need to know immediately whether the person standing in front of them is qualified for the task they’re about to do. Not after navigating menus and checking multiple systems. Right now, in the moment, with a glance. Field-builder-designed platforms make that information accessible because builders know decisions happen in seconds on site, not after researching credentials.

Fourth, emergency procedures become clear and actionable. Workers know exactly who to contact and what to do without having to remember from a video they watched weeks ago. The information is accessible when panic happens, not buried in a system nobody trained them to navigate under stress.

Here’s what this looks like in practice:

  • Simple interfaces that require minimal clicks to document observations or verify training status • Real-time visibility into who’s on site, what they’re trained for, and what tasks are happening • Feedback loops that give teams daily and weekly data they can actually act on immediately • Integration that works with how field teams actually operate, not how corporate thinks they should operate

These aren’t luxury features. These are the essentials that determine whether a platform drives behavioral change or just creates compliance theater.

Why Feedback Loops Matter More Than Data Collection

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. We work with builders who understand that safety technology should make protection easier, not create more administrative burden that distracts from actual risk management.

Think about the difference between data collection and feedback loops. Data collection gathers information that goes somewhere for future analysis. Feedback loops create information that drives immediate decisions and behavioral change. Most safety platforms optimize for the former. Field-builder-designed platforms optimize for the latter.

Caitlin emphasizes this distinction constantly. Her goal isn’t collecting comprehensive data about safety practices. Her goal is sending one person home safe who wouldn’t have gone home safe without the platform. That requires feedback loops where teams see immediately what’s working, what’s not, and what needs to change. Not reports generated next month showing trends from last quarter.

The current condition is platforms that tie into databases and project management systems and developer preferences instead of reverse-engineering from field needs. They create beautiful dashboards that executives love but don’t drive different behavior when a foreman is making split-second decisions about whether someone is qualified for a task. That’s the disconnect that gets people hurt.

When builders design platforms, they start with the behavioral change they want to create and work backwards to the minimal viable interface that drives that change. They don’t add features that look impressive but create friction. They don’t collect data that goes nowhere. They don’t optimize for corporate preferences at the expense of field usability.

The Challenge: Demand Tools Built by Builders

So here’s my challenge to you, and Caitlin’s challenge too. The construction industry is changing. The way we viewed construction ten years ago and the way we’ll view it in ten years will be completely different. Technology will be part of that change. But it has to be technology built by people who understand field reality, not corporate developers optimizing for data collection.

Reach out to companies like eMod Safety that were created by superintendents solving real problems. Give field-builder-designed platforms a chance even if you’re skeptical of technology. Because the goal isn’t adopting technology for its own sake. The goal is what Caitlin describes as her personal mission: if she can send one person home safe who wouldn’t have gone home safe otherwise, she’s done her job.

Stop accepting safety platforms that create compliance theater. Stop tolerating systems that require fourteen clicks to document simple observations. Stop using tools that optimize for corporate data needs at the expense of field usability. Demand platforms built by people who’ve stood in mud with boots on managing fifty priorities while trying to keep everyone safe. Those tools exist now. Use them.

As Antoine de Saint-Exupéry wrote, “Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away.” Safety platforms built by field builders achieve perfection through simplicity that drives behavioral change, not complexity that collects data. That’s the difference between tools that protect people and tools that just look good in reports.

On we go.

Frequently Asked Questions

How do I know if a safety platform was actually built by field people?

Ask who designed it and what their background is. Field-builder platforms have simplicity and focus on behavioral change over data collection. If the demo requires tutorials and the interface has dropdown menus for everything, it probably wasn’t built by someone managing field operations daily.

Won’t simpler platforms collect less data and limit our ability to analyze trends?

Field-builder platforms collect the data that drives decisions, not comprehensive data that goes nowhere. The question isn’t how much data you collect but whether it creates feedback loops that change behavior. More data that nobody acts on doesn’t improve safety. Less data that drives daily decisions does.

What if my company has already invested in a complex safety platform?

Evaluate whether it’s actually driving behavioral change or just creating compliance theater. If field teams are finding workarounds or pencil-whipping forms, the investment isn’t protecting people regardless of cost. Sometimes the right decision is admitting a platform doesn’t work and finding tools that do.

How do I convince executives to switch to simpler, field-focused platforms?

Show them the gap between compliance reports and actual field behavior. Ask workers what they’d do in an emergency and compare their answers to what procedures say. Demonstrate that current platforms optimize for data that looks good in reports but doesn’t protect people in real time.

What’s the first step to improving safety technology on my projects?

Talk to superintendents and foremen about what information they actually need in the moment to make safety decisions. Ask what creates friction in current systems. Then find platforms designed around those real needs, not around comprehensive data collection that serves corporate offices.

 

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.

    faq

    General Training Overview

    What construction leadership training programs does LeanTakt offer?
    LeanTakt offers Superintendent/PM Boot Camps, Virtual Takt Production System® Training, Onsite Takt Simulations, and Foreman & Field Engineer Training. Each program is tailored to different leadership levels in construction.
    Who should attend LeanTakt’s training programs?
    Superintendents, Project Managers, Foremen, Field Engineers, and trade partners who want to improve planning, communication, and execution on projects.
    How do these training programs improve project performance?
    They provide proven Lean and Takt systems that reduce chaos, improve reliability, strengthen collaboration, and accelerate project delivery.
    What makes LeanTakt’s training different from other construction courses?
    Our programs are hands-on, field-tested, and focused on practical application—not just classroom theory.
    Do I need prior Lean or takt planning experience to attend?
    No. Our programs cover foundational principles before moving into advanced applications.
    How quickly can I apply what I learn on real projects?
    Most participants begin applying new skills immediately, often the same week they complete the program.
    Are these trainings designed for both office and field leaders?
    Yes. We equip both project managers and superintendents with tools that connect field and office operations.
    What industries benefit most from LeanTakt training?
    Commercial, multifamily, residential, industrial, and infrastructure projects all benefit from flow-based planning.
    Do participants receive certificates after completing training?
    Yes. Every participant receives a LeanTakt Certificate of Completion.
    Is LeanTakt training recognized in the construction industry?
    Yes. Our programs are widely respected among leading GCs, subcontractors, and construction professionals.

    Superintendent / PM Boot Camp

    What is the Superintendent & Project Manager Boot Camp?
    It’s a 5-day immersive training for superintendents and PMs to master Lean leadership, takt planning, and project flow.
    How long does the Superintendent/PM Boot Camp last?
    Five full days of hands-on training.
    What topics are covered in the Boot Camp curriculum?
    Lean leadership, Takt Planning, logistics, daily planning, field-office communication, and team health.
    How does the Boot Camp improve leadership and scheduling skills?
    Yes. You’ll learn how to run day huddles, team meetings, worker huddles, and Lean coordination processes.
    Who is the Boot Camp best suited for?
    Construction leaders responsible for delivering projects, including Superintendents, PMs, and Field Leaders.
    What real-world challenges are simulated during the Boot Camp?
    Schedule breakdowns, trade conflicts, logistics issues, and communication gaps.
    Will I learn Takt Planning at the Boot Camp?
    Yes. Takt Planning is a core focus of the Boot Camp.
    How does this Boot Camp compare to traditional PM certification?
    It’s practical and execution-based rather than exam-based. You learn by doing, not just studying theory.
    Can my entire project team attend the Boot Camp together?
    Yes. Teams attending together often see the greatest results.
    What kind of real-world challenges do we simulate?
    Improved project flow, fewer delays, better team communication, and stronger leadership confidence.

    Takt Production System® Virtual Training

    What is the Virtual Takt Production System® Training?
    It’s an expert-led online program that teaches Lean construction teams how to implement takt planning.
    How does virtual takt training work?
    Delivered online via live sessions, interactive discussions, and digital tools.
    What are the benefits of online takt planning training?
    Convenience, global accessibility, real-time learning, and immediate application.
    Can I access the virtual training from anywhere?
    Yes. It’s fully web-based and accessible worldwide.
    Can I access the virtual training from anywhere?
    Yes. It’s fully web-based and accessible worldwide.
    What skills will I gain from the Virtual TPS® Training?
    Macro and micro Takt planning, weekly updates, flow management, and CPM integration.
    How long does the virtual training program take?
    The program is typically completed in multiple live sessions across several days.
    Can I watch recordings if I miss a session?
    Yes. Recordings are available to all participants.
    Do you offer group access or company licenses for the virtual training?
    Yes. Teams and companies can enroll together at discounted rates.
    How does the Virtual TPS® Training integrate with CPM tools?
    We show how to align Takt with CPM schedules like Primavera P6 or MS Project.

    Onsite Takt Simulation

    What is a Takt Simulation in construction training?
    It’s a live, interactive workshop that demonstrates takt planning on-site.
    How does the Takt Simulation workshop work?
    Teams participate in hands-on exercises to learn the flow and rhythm of a Takt-based project.
    Can I choose between a 1-day or 2-day Takt Simulation?
    Yes. We offer flexible formats to fit your team’s schedule and needs.
    Who should participate in the Takt Simulation workshop?
    Superintendents, PMs, site supervisors, contractors, and engineers.
    How does a Takt Simulation improve project planning?
    It shows teams how to structure zones, manage flow, and coordinate trades in real time.
    What will my team learn from the onsite simulation?
    How to build and maintain takt plans, manage buffers, and align trade partners.
    Is the simulation tailored to my specific project type?
    Yes. Scenarios can be customized to match your project.
    How do Takt Simulations improve trade partner coordination?
    They strengthen collaboration by making handoffs visible and predictable.
    What results can I expect from an onsite Takt Simulation?
    Improved schedule reliability, better trade collaboration, and reduced rework.
    How many people can join a Takt Simulation session?
    Group sizes are flexible, but typically 15–30 participants per session.

    Foreman & Field Engineer Training

    What is Foreman & Field Engineer Training?
    It’s an on-demand, practical program that equips foremen and engineers with leadership and planning skills.
    How does this training prepare emerging leaders?
    By teaching communication, crew management, and execution strategies.
    Is the training on-demand or scheduled?
    On-demand, tailored to your team’s timing and needs.
    What skills do foremen and engineers gain from this training?
    Planning, safety leadership, coordination, and communication.
    How does the training improve communication between field and office?
    It builds shared systems that align superintendents, engineers, and managers.
    Can the training be customized for my team’s needs?
    Yes. Programs are tailored for your project or company.
    What makes this program different from generic leadership courses?
    It’s construction-specific, field-tested, and focused on real project application.
    How do foremen and field engineers apply this training immediately?
    They can use new systems for planning, coordination, and daily crew management right away.
    Is the training suitable for small construction companies?
    Yes. Small and large teams alike benefit from building flow-based leadership skills.

    Testimonials

    Testimonials

    "The bootcamp I was apart of was amazing. Its was great while it was happening but also had a very profound long-term motivation that is still pushing me to do more, be more. It sounds a little strange to say that a construction bootcamp changed my life, but it has. It has opened my eyes to many possibilities on how a project can be successfully run. It’s also provided some very positive ideas on how people can and should be treated in construction.

    I am a hungry person by nature, so it doesn’t take a lot to get to participate. I loved the way it was not just about participating, it was also about doing it with conviction, passion, humility and if it wasn’t portrayed that way you had to do it again."

    "It's great to be a part of a company that has similar values to my own, especially regarding how we treat our trade partners. The idea of "you gotta make them feel worse to make them do better" has been preached at me for years. I struggled with this as you will not find a single psychology textbook stating these beliefs. In fact it is quite the opposite, and causing conflict is a recipe for disaster. I'm still honestly in shock I have found a company that has based its values on scientific facts based on human nature. That along with the Takt scheduling system makes everything even better. I am happy to be a part of a change that has been long overdue in our industry!"

    "Wicked team building, so valuable for the forehumans of the sub trades to know the how and why. Great tools and resources. Even though I am involved and use the tools every day, I feel like everything is fresh and at the forefront to use"

    "Jason and his team did an incredible job passing on the overall theory of what they do. After 3 days of running through the course I cannot see any holes in their concept. It works. it's proven to work and I am on board!"

    "Loved the pull planning, Takt planning, and logistic model planning. Well thought out and professional"

    "The Super/PM Boot Camp was an excellent experience that furthered my understanding of Lean Practices. The collaboration, group involvement, passion about real project site experiences, and POSITIVE ENERGY. There are no dull moments when you head into this training. Jason and Mr. Montero were always on point and available to help in the break outs sessions. Easily approachable to talk too during breaks and YES, it was fun. I recommend this training for any PM or Superintendent that wants to further their career."

    agenda

    Day 1

    Foundations & Macro Planning

    • Introduction to Takt Production System® principles
    • CPM vs TAKT comparison
    • Macro planning, zoning, and density analysis
    • Quantities and production rates
    • Hands-on application to participants’ projects with LeanTakt PM experts

    day2

    Norm Planning & Flow Optimization

    • Review and refinement of Day 1 work
    • Pull planning and sequence optimization
    • Work packaging for balanced flow
    • Project integration session with LeanTakt PM coaching

    day3

    Advanced Tools & Comparisons

    • Macro work packaging and example walkthrough
    • Calculator Norm for production optimization
    • Stacking comparison to avoid trade conflicts
    • Hands-on application to participants’ own schedules

    day4

    Buffers, Controls & Finalization

    • Review of Day 3 implementation
    • Buffer management strategies and placement
    • Takt control principles and steering methods
    • Project plan finalization with expert guidance

    day5

    Control Systems & Presentations

    • Takt steering, control systems, and real project examples
    • Participant project presentations with LeanTakt PM feedback
    • Wrap-up, feedback, and action planning for post-training implementation

    faq

    UNDERSTANDING THE TRAINING

    What is the Virtual Takt Production System® Training by LeanTakt?
    It’s an expert-led online program designed to teach construction professionals how to implement Takt Planning to create flow, eliminate chaos, and align teams across the project lifecycle.
    Who should take the LeanTakt virtual training?
    This training is ideal for Superintendents, Project Managers, Engineers, Schedulers, Trade Partners, and Lean Champions looking to improve planning and execution.
    What topics are covered in the online Takt Production System® course?
    The course covers macro and micro Takt planning, zone creation, buffers, weekly updates, flow management, trade coordination, and integration with CPM tools.
    What makes LeanTakt’s virtual training different from other Lean construction courses?
    Unlike theory-based courses, this training is hands-on, practical, field-tested, and includes live coaching tailored to your actual projects.
    Do I get a certificate after completing the online training?
    Yes. Upon successful completion, participants receive a LeanTakt Certificate of Completion, which validates your knowledge and readiness to implement Takt.

    VALUE AND RESULTS

    What are the benefits of Takt Production System® training for my team?
    It helps teams eliminate bottlenecks, improve planning reliability, align trades, and reduce the chaos typically seen in traditional construction schedules.
    How much time and money can I save with Takt Planning?
    Many projects using Takt see 15–30% reductions in time and cost due to better coordination, fewer delays, and increased team accountability.
    What’s the ROI of virtual Takt training for construction teams?
    The ROI comes from faster project delivery, reduced rework, improved communication, and better resource utilization — often 10x the investment.
    Will this training reduce project delays or rework?
    Yes. By visualizing flow and aligning trades, Takt Planning reduces miscommunication and late handoffs — major causes of delay and rework.
    How soon can I expect to see results on my projects?
    Most teams report seeing improvement in coordination and productivity within the first 2–4 weeks of implementation.

    PLANNING AND SCHEDULING TOPICS

    What is Takt Planning and how is it used in construction?
    Takt Planning is a Lean scheduling method that creates flow by aligning work with time and space, using rhythm-based planning to coordinate teams and reduce waste.
    What’s the difference between macro and micro Takt plans?
    Macro Takt plans focus on the overall project flow and phase durations, while micro Takt plans break down detailed weekly tasks by zone and crew.
    Will I learn how to build a complete Takt plan from scratch?
    Yes. The training teaches you how to build both macro and micro Takt plans tailored to your project, including workflows, buffers, and sequencing.
    How do I update and maintain a Takt schedule each week?
    You’ll learn how to conduct weekly updates using lookaheads, trade feedback, zone progress, and digital tools to maintain schedule reliability.
    Can I integrate Takt Planning with CPM or Primavera P6?
    Yes. The training includes guidance on aligning Takt plans with CPM logic, showing how both systems can work together effectively.
    Will I have access to the instructors during the training?
    Yes. You’ll have opportunities to ask questions, share challenges, and get real-time feedback from LeanTakt coaches.
    Can I ask questions specific to my current project?
    Absolutely. In fact, we encourage it — the training is designed to help you apply Takt to your active jobs.
    Is support available after the training ends?
    Yes. You can access follow-up support, coaching, and community forums to help reinforce implementation.
    Can your tools be customized to my project or team?
    Yes. We offer customizable templates and implementation options to fit different project types, teams, and tech stacks.
    When is the best time in a project lifecycle to take this training?
    Ideally before or during preconstruction, but teams have seen success implementing it mid-project as well.

    APPLICATION & TEAM ADOPTION

    What changes does my team need to adopt Takt Planning?
    Teams must shift from reactive scheduling to proactive, flow-based planning with clear commitments, reliable handoffs, and a visual management mindset.
    Do I need any prior Lean or scheduling experience?
    No prior Lean experience is required. The course is structured to take you from foundational principles to advanced application.
    How long does it take for teams to adapt to Takt Planning?
    Most teams adapt within 2–6 weeks, depending on project size and how fully the system is adopted across roles.
    Can this training work for smaller companies or projects?
    Absolutely. Takt is scalable and especially powerful for small teams seeking better structure and predictability.
    What role do trade partners play in using Takt successfully?
    Trade partners are key collaborators. They help shape realistic flow, manage buffers, and provide feedback during weekly updates.

    VIRTUAL FORMAT & ACCESSIBILITY

    Can I access the virtual training from anywhere?
    Yes. The training is fully accessible online, making it ideal for distributed teams across regions or countries.
    Is this training available internationally?
    Yes. LeanTakt trains teams around the world and supports global implementations.
    Can I watch recordings if I miss a session?
    Yes. All sessions are recorded and made available for later viewing through your training portal.
    Do you offer group access or company licenses?
    Yes. Teams can enroll together at discounted rates, and we offer licenses for enterprise rollouts.
    What technology or setup do I need to join the virtual training?
    A reliable internet connection, webcam, Miro, Spreadsheets, and access to Zoom.

    faq

    GENERAL FAQS

    What is the Superintendent / PM Boot Camp?
    It’s a hands-on leadership training for Superintendents and Project Managers in the construction industry focused on Lean systems, planning, and communication.
    Who is this Boot Camp for?
    Construction professionals including Superintendents, Project Managers, Field Engineers, and Foremen looking to improve planning, leadership, and project flow.
    What makes this construction boot camp different?
    Real-world project simulations, expert coaching, Lean principles, team-based learning, and post-camp support — all built for field leaders.
    Is this just a seminar or classroom training?
    No. It’s a hands-on, immersive experience. You’ll plan, simulate, collaborate, and get feedback — not sit through lectures.
    What is the focus of the training?
    Leadership, project planning, communication, Lean systems, and integrating office-field coordination.

    CURRICULUM & OUTCOMES

    What topics are covered in the Boot Camp?
    Takt planning, day planning, logistics, pre-construction, team health, communication systems, and more.
    What is Takt Planning and why is it taught?
    Takt is a Lean planning method that creates flow and removes chaos. It helps teams deliver projects on time with less stress.
    Will I learn how to lead field teams more effectively?
    Yes. This boot camp focuses on real leadership challenges and gives you systems and strategies to lead high-performing teams.
    Do you cover daily huddles and meeting systems?
    Yes. You’ll learn how to run day huddles, team meetings, worker huddles, and Lean coordination processes.
    What kind of real-world challenges do we simulate?
    You’ll work through real project schedules, logistical constraints, leadership decisions, and field-office communication breakdowns.

    LOGISTICS & FORMAT

    Is the training in-person or virtual?
    It’s 100% in-person to maximize learning, feedback, and team-based interaction.
    How long is the Boot Camp?
    It runs for 5 full days.
    Where is the Boot Camp held?
    Locations vary — typically hosted in a professional training center or project setting. Contact us for the next available city/date.
    Do you offer follow-up coaching after the Boot Camp?
    Yes. Post-camp support is included so you can apply what you’ve learned on your projects.
    Can I ask questions about my actual project?
    Absolutely. That’s encouraged — bring your current challenges.

    PRICING & VALUE

    How much does the Boot Camp cost?
    $5,000 per person.
    Are there any group discounts?
    Yes — get 10% off when 4 or more people from the same company attend.
    What’s the ROI for sending my team?
    Better planning = fewer delays, smoother coordination, and higher team morale — all of which boost productivity and reduce costs.
    Will I see results immediately?
    Most participants apply what they’ve learned as soon as they return to the jobsite — especially with follow-up support.
    Can this replace other leadership training?
    In many cases, yes. This Boot Camp is tailored to construction professionals, unlike generic leadership seminars.

    SEO-BASED / HIGH-INTENT SEARCH QUESTIONS

    What is the best leadership training for construction Superintendents?
    Our Boot Camp offers real-world, field-focused leadership training tailored for construction leaders.
    What’s included in a Superintendent Boot Camp?
    Takt planning, day planning, logistics, pre-construction systems, huddles, simulations, and more.
    Where can I find Lean construction training near me?
    Check our upcoming in-person sessions or request a private boot camp in your city.
    How can I improve field and office communication on a project?
    This Boot Camp teaches you tools and systems to connect field and office workflows seamlessly.
    Is there a training to help reduce chaos on construction sites?
    Yes — this program is built specifically to turn project chaos into flow through structured leadership.

    agenda

    Day 1

    Agenda

    • Intro to Camp
    • Set Expectations
    • Morning Routine
    • Plan Day
    • Explain "Why"
    • Teams Intros + Yells + Expectation
    • Focus, Physiology, Words + Yells
    • Blocks to Leadership
    • 50 Million
    • Biggest Thing
    • Choose Your Word
    • Marketing Exercise
    • Interview for the Project
    • PO Homework and Close the Day

    Outcomes

    • Understand how to get into a proper state to lead
    • Understand how to dig deep to find the confidence to lead
    • Team work and collaboration
    • Understand marketing
    • Understand how to interview for and win a project

    Day 2

    Agenda

    • Morning Routine
    • Day Planner
    • Plus & Delta
    • Macro Takt planning
    • Setup jobs + Signs + Logistics
    • Explain the IPCS™
    • Detailed logistics training
    • Team balance & health training

    Outcomes

    • Learn the IPCS™ understand how to integrate the entire project from start to finish with First Planners™ and Last Planners® through the Takt Production System®
    • Learn how to review a project
    • Learn advanced logistics
    • Learn team balance and health

    Day 3

    Agenda

    • Morning Routine
    • Day Planner
    • Plus & Delta
    • Review How Big Things Get Done
    • Review IPCSTM
    • Fix (Schedule, zone, logistics, trailer, org & procurement)
    • Fresh Eyes Meeting
    • Pre-Con Overview
    • TAKT SIMULATION
    • Recap and Review

    Outcomes

    • Understand why and how to plan
    • Understand the benefits of using a Takt production plan
    • Learn the steps to proper pre-con that sets the project up for success
    • Learn how to review a project in a Fresh Eyes Meeting
    • Learn flow from Takt planning

    Day 4

    Agenda

    • Morning Routine
    • Day Planner
    • Plus & Delta
    • Opposing Squares
    • Pull Plan
    • Takt Remaining
    • Norm Update
    • Re Zoning
    • Risks & Pre-Con Align
    • Meeting System
    • Problems
    • Recap

    Outcomes

    • Understand the Norm level Takt plan for weekly/daily planning
    • Benefits and outcomes of rezoning strategies
    • Using meetings to feed information through the system and to the Foremen

    Day 5

    Agenda

    • Morning Routine
    • Day Planner
    • Plus & Delta
    • Huddle I.D.S
    • Day Plan
    • Worker Huddle
    • Norm Update
    • Team Huddle
    • Lean Systems Recap
    • Feedback Exercise
    • Final & Close

    Outcomes

    • Know what information is needed and how to get it to the Workers
    • Better understand how to give feedback and why it’s crucial for everyone
    • How to problem solve as a team
    • Understand how all systems tie together
    • Know how the information gets all the way to the worker
    • Have perfect clarity on the individual’s personal organization planner