How to Use a Shammy

Posted on August 4, 2026August 4, 2026 by Jason Schroeder

Read 21 min

We Must Explain What We Expect: The Communication Standard Every Construction Leader Needs

There is a moment every experienced construction leader can remember where they gave an instruction that seemed perfectly clear, watched someone execute it completely wrong, and felt the frustration of a result they did not want. The natural response in that moment is to wonder how the person could have misunderstood something so obvious. The more useful question is to ask whether what felt obvious was actually communicated. Because in construction, as in life, the gap between what was assumed and what was explained is where most quality problems, safety incidents, rework, and wasted time actually live. The instruction that felt complete usually was not. And the person who got it wrong was not failing the expectation. They were failing to read a mind.

The Pain That Shows Up Everywhere on the Project

The concrete superintendent who told two workers to move the column cages and pointed in a direction was doing what most construction leaders do most of the time: communicating the minimum and trusting that professional judgment would fill in the rest. Sometimes it does. But sometimes the column cages end up somewhere other than where they needed to go. Sometimes the forklift is not inspected. Sometimes the rigging certification is assumed rather than verified. Sometimes nobody fills out the pretask plan because nobody said to. And when the outcome is wrong, the leader’s frustration is real and the worker’s confusion is equally real, because from where they were standing, they did exactly what they were told.

The System That Normalized Incomplete Instructions

Construction has a long tradition of expecting experienced people to figure it out. The assumption is that a journeyman electrician or an experienced equipment operator does not need to be walked through every step of a familiar task. That assumption is often correct at the task execution level, but it misses the point. The specificity that matters is not about whether the worker knows how to operate a forklift. It is about whether they know which forklift, which location, which certification to confirm, which paperwork to complete, which dunnage to use, what to do with the rigging when finished, and why all of that matters to the crane mobilization happening in thirty minutes. The who and the how are often assumed. The what and the where and the when and the why are frequently not communicated at all. And the gap between what was assumed and what was said is where the result falls apart.

The Chamois Story

When Jason Schroeder was thirteen or fourteen years old working for Conco Construction, his boss Ryan handed him an expensive chamois cloth and told him to wash the truck. Ryan loved that chamois. It cost twenty-four dollars, which was significant money, and it came in a nice case. Ryan threw it to Jason and walked back inside. Jason had never used a chamois before. He went to the supply closet, got a bucket and some Dawn dish soap, soaked the chamois in suds, and started scrubbing the truck with it. It was not working great, but he kept at it. When he told Ryan the chamois was not working well, Ryan came outside, saw what was happening, and went into a full crisis, spraying and rinsing the chamois, trying to save it from the soap that had saturated it.

A chamois is not a washing cloth. It is a drying cloth. You rinse the car first with a regular rag and then you drag the chamois across the wet surface to squeegee the water off. Jason did not know that. Ryan did not say that. Ryan said wash the truck and threw him a tool whose correct use he had never explained. The result was entirely predictable, and it was not Jason’s fault. It was a communication failure. And to Ryan’s credit, after the initial frustration, he could probably see that too.

What the Column Cage Conversation Actually Looked Like

Jason was a project director when he watched a concrete superintendent tell two workers to move two column cages that were blocking a crane path. The superintendent pointed and said move those. Jason pulled him aside, not to criticize, but to show him what the instruction should have looked like from beginning to end.

It starts by getting the workers’ attention properly: asking if they have a minute, transitioning them intentionally from one task to another. Then it covers the what: these two specific column cages need to move to this specific location. Then the why: the crane path runs through here and we cannot have them in this location when the crane mobilizes. Then the how: use the forklift, but first confirm that both of you have your rigging certification and your forklift certification and are trained for this task. Then the safety requirements: complete an equipment inspection on the forklift before you start, inspect the rigging, discuss together how to rig it safely with a tagline, complete the pretask plan with both signatures before you touch anything. Then the execution detail: make sure everyone is clear of the swing radius, nobody is at risk of being struck, and the path is clear before you move. Then the finish condition: set them on dunnage so rain does not bury them in mud, return the rigging to its storage location, and park the forklift back in its designated spot.

That instruction takes about ninety seconds to deliver. It prevents a dozen different ways the task could go wrong. And it respects the workers by giving them everything they need to succeed rather than leaving them to guess at what the leader actually wanted.

Signs That Your Instructions Are Not Complete Enough

Most construction leaders have developed a communication style that works reasonably well most of the time. The gaps show up at the edges. These are the patterns that signal instructions are not landing as intended:

Workers complete a task but in the wrong location, the wrong sequence, or without the required safety paperwork because none of those specifics were stated
The same correction has to be given more than once because the standard was communicated but the reason behind it was never explained, so it does not stick
A new employee or a new foreman makes a mistake that an experienced person would not have made, and the response is frustration rather than recognition that the instruction was written for an experienced audience
A task is completed correctly but the cleanup, the storage of materials, and the return of equipment are left undone because the instruction ended at the execution and not at the finished condition

None of those are worker failures. They are all communication failures. The standard that Jason holds himself to is that if the outcome was not what was expected, the first question to ask is whether the expectation was clearly stated, not whether the worker was paying attention.

Why Over-Communication Is Not Condescending

The construction culture tends to treat detailed instructions as an insult to experienced workers. If you have to explain every step, the implication is that you do not trust the person to know their craft. But the instruction that Jason describes in the column cage example is not about whether the workers know how to operate a forklift. It is about alignment: everyone on the same page about the specific task, the specific location, the specific safety requirements, and the specific finish condition, before anyone touches anything. That alignment does not insult the worker’s expertise. It respects their time by not making them guess, respects the safety system by confirming certifications and paperwork before the risk exists, and respects the project by ensuring that the first attempt produces the right result rather than a result that has to be corrected.

As Chris put it in the comment Jason references on the LeanTakt channel: it is hard for you to understand what I expect from you if I do not tell you what I expect from you. That sentence is not complicated. It is just consistently true. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Make the Expectation Visible Before the Work Starts

The practical shift that comes from this episode is simple: before a worker or a crew begins a task, the instruction should cover all of the following. What exactly needs to be done and where the finished result should be. Why it matters to the sequence, the schedule, or the safety of the work happening around it. How to do it, including what equipment, what rigging, what certifications, and what safety documentation are required. When it needs to be done and what defines done, meaning not just the execution but the cleanup, the return of equipment, and the condition in which the area should be left. That is the complete instruction. Everything shorter than that is leaving something to chance.

This is not about micromanaging. A senior journeyman doing a familiar task does not need to be walked through every certification they already hold. But the new foreman who was just hired does. The worker who is transitioning to a task they have not done recently does. Anyone working in conditions they have not worked in before on this project does. The question to ask before giving every instruction is: does this person have everything they need to succeed, or am I assuming something I have not stated?

Edwards Deming taught that a bad system will beat a good person every time. The communication system on most construction projects is designed to communicate the minimum and trust that experience fills in the rest. A better system communicates completely, confirms understanding, and treats the gap between the instruction and the task as the moment where quality, safety, and production are either protected or exposed. Build the habit of complete instructions. The chamois story and the column cage story both end the same way when the instruction is complete: the right result, the first time.

On we go.

FAQ

Why do experienced construction leaders still give incomplete instructions?

Because experience creates the illusion that what feels obvious to the instructor is obvious to the person receiving the instruction, and construction culture has normalized the minimum rather than the complete. The gap between what was assumed and what was said is where most preventable failures happen.

What should a complete instruction include before a worker begins a task?

A complete instruction covers the what, where, why, how, safety requirements, certifications needed, paperwork to complete, and the finished condition including cleanup and equipment return. Anything shorter leaves something to chance.

How is detailed communication different from micromanaging?

Micromanaging is controlling how someone does work they already know how to do. Complete communication is making sure everyone is aligned on the specific task, location, safety requirements, and expected outcome before anyone starts. The distinction is alignment versus control.

What is the lesson from the chamois story for construction leaders?

Ryan assumed Jason knew what a chamois was for. Jason did not, and the expensive tool was nearly ruined. The person who gives an instruction owns the clarity of it, not the person who receives it.

How does complete communication connect to safety on a construction project?

Most safety incidents happen in the gap between the instruction given and the task performed. Confirming certifications, requiring pretask plans, and explaining the rigging approach before anyone picks up a tool are what close that gap before the risk becomes a consequence.

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.

Stay with It! I Promise It Is Worth It!

Posted on August 4, 2026August 4, 2026 by Jason Schroeder

Read 24 min

It Is Worth It: A Letter to Every Construction Leader Fighting Through the Hard Years

There was no energetic introduction on this episode. No framework to introduce. No production principle to teach. Just Jason Schroeder sitting in Houston, a little sick, a little tired, and a little overwhelmed by the beauty of an ordinary Saturday that turned out to be anything but ordinary. He had just posted two pictures on LinkedIn: one of himself in full superintendent gear, hard hat and safety vest and glasses, looking like he was conquering the world. The other of himself holding a sleeping baby on his chest on the couch, too tired to stay awake. And the response from the construction community told him something he already knew but needed to say out loud: a lot of people out there are right in the middle of those hard years, and they need someone to tell them it is worth it.

The Pain That Nobody Talks About at Work

The years between twenty and forty in construction can be genuinely brutal. The industry demands everything during the exact same window of life when a marriage is being built, children are being raised, school is being finished, a career is being established, and a family is trying to figure out what it is going to be. On any given week, a superintendent might be managing three hundred workers on a complex project during the day and coming home to a two-year-old who needs baths and bedtime stories and a spouse who needed a conversation that never happened because the phone kept ringing. The fires on both ends burn at the same temperature. And there are not enough hours.

The LinkedIn post Jason shared was simple and direct: for all of you struggling through these years, having little ones, changing diapers, staying up late, coaching and watching endless games, finishing school and establishing a life, I see you. I am cheering for you and your family. Do what you can to stay with it and the rewards will be priceless. The responses came from fathers and mothers who recognized themselves in those two photographs: the person trying to be a superhero at work and at home simultaneously, wondering sometimes if they are doing either one well enough.

The System That Never Accounts for the Full Person

Construction has always been better at measuring production than at seeing the human being producing it. The daily report tracks units installed and labor hours spent. It does not track the superintendent who has been sick for eight days and is still showing up. It does not track the project manager who took a red-eye flight to make a client meeting and missed their kid’s first soccer game. It does not track the foreman who is carrying something heavy at home and is still leading their crew with dignity and patience every morning. The system was designed to measure what can be measured, and the things that most determine whether a person can sustain the work over a full career are the things the system leaves out entirely.

That is not anyone’s fault. It is a design limitation. But naming it matters, because the leaders who understand that their people are carrying the full weight of a life, not just a job description, are the leaders who create environments where people can actually stay in this industry long enough to become excellent at it.

The Morning That Reminded Him What It Is For

On the Saturday of this episode, Jason woke up sick and tired and not feeling like himself. Katie suggested he wake the kids up and take them to Walmart to buy Nerf guns, then to the church building for a war. He loaded everyone into the beat-up fifteen-passenger van, the one with the broken air conditioning knobs and the door that does not quite work and the passenger seat that will not fully recline. The kids did not notice anything different about the van. They just piled in, giggling.

They pushed the cart through Walmart with their chore money, got yogurt and snacks and breakfast burritos from Del Taco, and then went to the church building where Jason set up chairs and tables and bases and loaded his gun. The kids fought over which team dad would be on. He kept rotating between them. The youngest had a meltdown eventually, as little kids do, and they packed up and went home. That was the whole thing. A Nerf gun war in a church gymnasium with a bunch of children and a father who was not feeling well. He calls moments like that the molecules that make up eternity.

What the Hard Years Are Actually Building

Here is what nobody tells you when you are in the middle of the hard years, working the grueling schedule, managing the project and the family and the health and the finances and the relationship all at the same time:

The moments you show up for anyway, when you are tired and sick and would rather not, are the ones your children remember most clearly
The marriage that survives the hard years does not just survive. It becomes something neither person could have imagined at the beginning, because the difficulty builds a depth that easy seasons cannot produce
The career that is built during the years when the cost is highest is the one that generates the most meaningful return, because it was earned rather than given
The identity that forms through the struggle is more durable than the one that forms through comfort, because it has been tested in conditions that revealed what it is actually made of
The friendships that form between people who have been through something genuinely hard together carry a quality of trust that no other kind of relationship produces

Jason sat in front of his house that morning, under a tree that was blossoming, with birds actually chirping, doing business meetings while the kids got ready. Not because the life was perfect. Because it was full. There is a difference between those two things, and learning to see it is one of the gifts the hard years eventually give.

The Person You Married Is Becoming Someone New

One of the most quietly remarkable things in this episode is what Jason says about Katie. He was watching a movie with her the night before and looked over and thought, I do not know you. Not as a sad thing. As an astonished thing. She was someone he had married, built a family with, struggled alongside through the launching of a business and the raising of eleven children, and she was still becoming. Still surprising him. Still revealing new dimensions of who she was.

He texted her that day: you are so much more interesting and knowledgeable. There is so much life and feistiness in you. There is something there that wasn’t there before. I do not know you but you are so interesting and beautiful. I look forward to loving you.

That is what the hard years build inside the people who stay with them. Not just in the career. In the person. In the marriage. In the family. The version of yourself that exists on the other side of those years is not the person who started them, and neither is the person you love. You are both becoming, continuously, and the becoming is the whole point.

The Fall Protection That Holds When the Scaffolding Drops

Jason closes with a construction analogy that earns its place here. He describes workers on scaffolding, some with fall protection and some without, and the scaffolding gives way. The ones without it suffer the worst injuries because they have nothing to hold on to. The ones with it survive because they are anchored to something that holds even when the platform beneath them fails.

The fall protection in a life is not a single thing. It is a category of things: the family relationships that remain when everything else is uncertain, the faith community that provides a framework of meaning when meaning is hard to find, the friendships that show up in the difficult seasons, the sacred practices that keep a person grounded when the ground beneath them is shifting, the places and people and commitments that represent something stable enough to grip when the scaffolding of normal life comes out from underneath. Nobody gets to choose whether the scaffolding falls. Everyone gets to choose what they are anchored to before it does.

The construction leader who understands this about their own life understands it about the people around them as well. The foreman who is hanging on to something right now needs a leader who can see that and respond to it with the kind of basic human presence that no production system can provide. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Hold On. The Other End of the Bridge Is Visible.

The LinkedIn post and the Nerf gun war and the packed bag and the text message to Katie and the kids squeezing hard enough to hurt: none of that is the product of a perfect life. It is the product of a life that stayed. That held on through the fights and the financial stress and the tired seasons and the impossible weeks when everything was demanding everything at once. And the paydays, as Jason puts it, are worth a million fold of any of the worst days.

To anyone in the middle of the hard years right now: you are being seen. The work you are doing at the jobsite and the work you are doing at home and the work you are doing on yourself are all the same work, and none of it is wasted, and the version of your life that is being built through the difficulty is worth every single thing it is costing. As Jason says at the end of every episode, meaning it each time: we can look forward to better days ahead. Tomorrow will be a little brighter. We can love a little more, forgive a little easier, be a little kinder, and appreciate a little bit more. That is not a small thing. That is everything.

On we go.

FAQ

Why does Jason Schroeder share personal stories like this one on a construction podcast?

Because the people who listen are not just construction professionals. They are human beings who are trying to build a career and a family and a life at the same time, and the thing they most need to hear is not always a production framework. Sometimes it is the honest acknowledgment that the hard years are hard, that other people are in them too, and that the payoff for staying with it is real. Jason’s willingness to be transparent about his own struggles is one of the things that makes the podcast feel like a conversation rather than a lecture.

What does the scaffolding analogy teach about building resilience?

The analogy teaches that resilience is not something you develop after the fall. It is something you build before it, by establishing the anchors that will hold you when the platform beneath you gives way. Family, faith, friendship, community, and sacred practice are not luxuries that make life more comfortable. They are structural elements that make recovery possible when ordinary life fails. The time to put on the fall protection is not when the scaffolding is already falling.

How do the hard years between twenty and forty apply to a construction leader’s professional development?

The same years that are hardest personally are often the years when the most important professional development happens, because the difficulty of the season forces a kind of focused prioritization that comfort does not require. The superintendent who figures out how to lead a complex project while also being present for a family is developing a capacity for managing multiple demanding systems simultaneously that becomes one of their most valuable leadership assets. The difficulty is not separate from the development. It is the mechanism of it.

What is the relationship between personal life and project culture for a construction leader?

A leader’s experience of being seen, supported, and valued at home shapes their capacity to see, support, and value the people around them at work. Conversely, a leader who is carrying enormous personal weight without adequate support will eventually express that weight in the way they lead: with less patience, less presence, and less ability to notice what the people around them are carrying. Taking care of the person produces a better leader. The project team benefits from the leader’s personal health in ways that no management framework can replace.

What is the most important takeaway from this episode for someone who is struggling right now?

Hold on. Not as a passive instruction to endure without hope, but as an active commitment to stay anchored to the things that matter while the difficult season passes. Jason’s testimony, drawn from his own experience of gut-wrenchingly hard things, is that the paydays are worth a million fold of the worst days, and that the version of life that exists on the other side of the hard years is richer and more beautiful than anything that could have been reached without going through them. The bridge has another end, and it is visible from where you are standing. Keep going.

If you want to learn more we have:

Discover Jason’s Expertise:

Live Life to the Fullest, Feat. John Coffman

Posted on August 4, 2026August 4, 2026 by Jason Schroeder

Read 25 min

Live Every Day to the Fullest: What a 23-Year Cancer Battle Teaches Construction Leaders About Life

There are podcasts about production systems, about Takt planning, about procurement and schedules and quality. And then there are conversations that make all of that feel small, not because the work does not matter, but because something larger is sitting in the room. Podcast 526 is one of those conversations. John Kaufman, a lifelong builder, Purdue-trained engineer, and one of the finest humans Jason Schroeder has known in construction, joined the show to talk about something he has been living for twenty-three years: what it means to face your own mortality and choose, every single day, to keep living. His most recent visit to MD Anderson Cancer Center in Houston ended with the news that treatment is no longer an option. And yet he got on his bicycle two days later and rode sixty-three miles. That is the kind of man he is. And what he says about life is worth stopping everything to hear.

The Problem That Shows Up Long Before the Diagnosis

Most construction professionals are excellent at managing risk on paper. They track schedule float, monitor procurement lead times, and identify quality risks before they compound. And then they go home and spend years of their actual life managing personal risk with paralysis: deferring the career move that feels too uncertain, skipping the family trip that costs more than the budget allows, declining the investment in their own development because it does not have a guaranteed return, avoiding the conversation that needs to happen because it feels too exposing to start. They are waiting to see whether the wave comes before they will agree to walk on the beach. The wave may never come. And while they wait, the sunset is happening without them.

John Kaufman has talked with people battling cancer, Parkinson’s, ALS, MS, and cardiac disease. He has designed wheelchair ramps through the Texas Ramp Project for people trapped in their homes by a four-inch step at the front door. He has sat with the sick, the grieving, and the afraid for more than two decades. And the single most consistent thing he has observed is that difficulty does not determine outcome. The response to difficulty does. Some people choose to spend the rest of their life dying. Others choose to spend the rest of their life living. Both groups have the same diagnosis. Only the choice is different.

The System That Keeps People on the Sand

This is not a personal failure. The culture that most people operate inside creates strong pressure toward safety, toward waiting for certainty before committing, toward managing the downside before pursuing the upside. That culture shows up on construction projects when teams wait for perfect conditions before starting a phase that needs to begin now. It shows up in companies when leaders defer the training investment because the budget line is tight and the return is not immediate. And it shows up in personal life when people stand at the edge of the water, watching the waves, unwilling to walk in because they cannot guarantee they will not get knocked down.

John’s gift to every person who hears this episode is a different frame entirely: the wave is coming whether you walk in or not. You do not get to choose whether the waves come. You only get to choose whether you spend the time between them afraid.

The Man on the Beach in Maui

John was in Maui early one morning, standing on the beach in the dark before sunrise, waiting for the light. A man was standing nearby. As it grew lighter John said something about what a beautiful sunrise it was going to be. The man said he wished he felt better so he could enjoy it. Something was weighing on him. When John asked, the man said he had just received a cancer diagnosis. The doctors had a protocol with a good success rate, but if it did not work, he might have two years. His doctor had told him to go ahead with the vacation and try to put it out of his mind.

John told him directly: you cannot put it out of your mind, and you should not try. But he offered something better than denial. He offered a reframe. You have been given a blessing, he said. You know you may have two years. Do you know how many people will drop over dead in those two years who were never told they had two years? Heart attacks, strokes, accidents, ordinary Tuesdays that turned out to be the last one. If someone had told them they had two years left, would they have done something different? You have been given that chance right now. You are in possibly the most beautiful place you have ever been, celebrating an anniversary with the love of your life. Do not put it out of your mind. Make memories. Do something differently. That is the gift.

Walking Between the Waves

The metaphor most people reach for when describing a serious illness is a roller coaster: ups and downs, highs and lows. John rejected that metaphor years ago. What it actually feels like, he says, is walking from a beach out into the ocean through waves. The first one hits you at the knees and knocks you around. You walk further and the next is bigger. You see it coming and turn sideways so it does not hit as hard. Sometimes a wave picks you up and shuffles you back. A big one knocks you down. In Hawaii, the shore break waves will wash you fifty feet up the beach and you just hope the water leaves you there rather than dragging you back out.

The waves can be physical, emotional, mental, or spiritual. Sometimes they are all four at once. The physical ones you can see coming. The emotional ones arrive out of a clear sky without warning and knock you flat to your knees. And then the wave washes away, and you realize you feel all right. You can stand back up. You walk on. The challenge, the one John has worked at for twenty-three years, is to walk between the waves without spending every moment afraid of the next one. Because the distance between the waves is life. Spending it in dread is giving the waves more of your time than they are entitled to take.

What Living Fully Actually Requires

John’s approach to his illness, and his challenge to every person listening, can be understood through the things he has committed to that fear would have taken away:

Riding his bicycle even when the news is devastating, because nothing changed between Tuesday when he could ride and Thursday when he still could
Walking out to watch the sunrise even when the body is not feeling its best, because the sunrise does not reschedule
Saying yes to conversations with strangers on beaches in Maui, because those conversations sometimes turn out to matter more than anything else on the trip
Designing ramps for people who cannot get out of their own homes, because usefulness does not require perfect health
Calling people back, showing up for others who are struggling, being present in the community that holds everyone together when the waves come

None of those things require a terminal diagnosis. They require a decision that today is worth living fully, made before the wave arrives, not after.

You Do Not Have to Be Dying to Live Like This

This is the turn in the episode that makes it relevant to every construction leader who has ever deferred something important because the conditions were not quite right. Jason reflects on this directly. He and Katie cashed in his entire Hensel Phelps retirement account to start Elevate Construction. With eleven children and a few thousand dollars in savings, they are building something that requires them to walk into the water every single day. There are business investments that need to be made that are gut-wrenchingly scary. The budget does not always cover what the next step requires.

And listening to John, the clarity arrives: they are doing the right thing. Not irresponsibly. Not recklessly. But fully. Walking into the water instead of sitting on the sand hoping the waves never come. The people who live that way are not foolish. They are the ones who, when they reach the end, can look back on a trail of accomplishment rather than a list of things they were going to do when the conditions improved.

What the Construction Industry Needs From Its Leaders

The same principle that John describes in living, committing to the day in front of you rather than retreating from it in fear, is the principle behind every lean system Elevate Construction teaches on projects. Here is where that parallel becomes most visible:

Takt planning requires committing to a production rhythm even when the outcome is uncertain, trusting the system rather than waiting for perfect conditions
Psychological safety requires leaders to remain present and engaged even when the project is difficult, modeling the behavior they want to see in their teams
The morning worker huddle requires someone to stand up and lead even when the day ahead is hard, because the team draws energy from the leader’s posture
Roadblock removal requires addressing problems before they become crises, which means walking toward the difficult thing rather than hoping it resolves on its own
Crew preparation requires planning for tomorrow before today is finished, because tomorrow’s success is built in the hours before it arrives

All of that is walking between the waves. All of it is choosing to live the day fully rather than managing it from a safe distance. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

We Are in It Together

John received a call two weeks before this recording from a contractor friend he had not spoken to in two years. The man had heard what was happening and called not knowing what to say. John told him: what you say matters, but what matters most is that you said something. That you showed up. That we are in it together. The wave that knocks you down is survivable when someone is there to help you stand back up and walk on.

That is the deepest thing John carries from twenty-three years of illness and community. We are not meant to walk between the waves alone. The calls matter. The showing up matters. The friend who drove to Houston and sat in the waiting room matters. The contractor who called after two years of silence matters. And the leader who notices when a foreman is struggling, who stops the meeting to check in, who sends the note that nobody required them to send, is practicing the same thing John practices on the beach: being present for someone who needs a hand getting back up.

Faith, Attitude, and the Bicycle

John’s cycling partner told him that cycling, attitude, and faith were what kept him going. John corrected the order: faith, attitude, and cycling. His doctors have noted that his fitness level has contributed to his ability to survive this long. So he keeps riding. He keeps walking into the water. He keeps facing the waves. Not because he is not afraid, but because he has decided that the beach is where he lives, and the only direction worth walking is forward. As he put it with the simplicity that only someone who has genuinely lived it can offer: do not spend the rest of your life dying. Spend it living. Make that choice.

On we go.

FAQ

What is the central lesson from John Kaufman’s story for construction leaders?

The choice to live fully is available to everyone, not just to people facing terminal illness. Most people are deferring that choice out of fear of waves that may or may not be coming, and John’s twenty-three years of living with cancer while riding his bicycle and designing ramps and watching sunrises is proof that the choice to live fully is made before the conditions are perfect, not after.

What does the wave analogy mean and how does it apply to everyday life?

Serious difficulty arrives like ocean waves rather than a roller coaster. Some you see coming and can brace for, others arrive without warning and knock you flat. The discipline is to walk between the waves without spending the distance between them in fear of the next one, because that fear gives the waves more of your life than they are entitled to take. The wave is coming whether you walk in or not. The only question is what you do with the time before it arrives.

What did John tell the man on the beach in Maui and why does it matter?

He told him that receiving a time horizon is a gift because it creates the opportunity to decide now whether to do something differently, rather than living as if time is unlimited. He encouraged him not to deny the diagnosis but to reframe it: he was in a beautiful place, celebrating something important with someone he loved, and the right response was to make memories and walk forward. The reframe is available to everyone facing difficulty, not just those with a medical diagnosis.

How does the principle of walking between the waves connect to what Elevate Construction teaches about project leadership?

Committing to a production rhythm in Takt planning, maintaining presence and energy when a project is struggling, running toward the hard thing rather than managing it from a distance: all of that is walking between the waves. The construction leader who chooses to engage fully with the difficulty in front of them rather than deferring it or minimizing it is practicing the same discipline John practices on the beach every morning.

What role does community play in John’s approach to facing difficulty?

Community is what makes getting back up after the waves possible. The contractor who called after two years of silence did not know what to say, and John told him it did not matter: what mattered was that he called, that he showed up, that they were in it together. On construction projects and in life, the decision to show up for someone who is struggling is what makes the distance between the waves walkable for both of them.

If you want to learn more we have:

Discover Jason’s Expertise:

What Are Standing Tactical Orders in Construction? (Field Leadership Guide)

Posted on August 3, 2026August 3, 2026 by Jason Schroeder

Read 17 min

What Are Standing Tactical Orders in Construction Leadership?

There is a question worth asking about every project, every company, every team: what happens when the leader is not there? Not what is supposed to happen. What actually happens based on what the team already knows, already believes, and already does by default.

If the answer is unclear, the team does not have standing tactical orders. And the absence of standing tactical orders is the absence of a culture that can sustain itself without the leader in the room.

Where the Concept Comes From

General Patton is one of the most studied military commanders in American history and one of the most controversial. But from a tactical standpoint, his results are difficult to argue with. His army moved faster and was more effective than any comparable force of the era. A significant reason for that performance was written standing tactical orders a clear, documented set of principles that every officer and soldier knew, that governed decisions at every level, and that allowed the organization to move with speed and consistency even without direct command in the moment.

Patton wrote his orders down. Everybody knew them. Communication moved faster because the culture had internalized what the commander wanted before the commander had to ask for it.

That model does not belong only to military history. It belongs on every construction project.

What Standing Tactical Orders Are

Standing tactical orders are the documented principles that govern how a leader’s team operates what they prioritize, how they make decisions, what the default behavior is when circumstances are unclear or the leader is unavailable. They are not a policy manual. They are not a list of rules. They are the philosophy of leadership expressed as operational commitments that the team has internalized deeply enough to act on without being prompted.

Every leader who takes this seriously will have their own version. The specifics will differ based on project type, company culture, team composition, and the leader’s own experience and values. What will not differ is the function: standing tactical orders tell the team what right looks like, in enough detail and with enough clarity that they can reproduce it without waiting for instruction.

Here is what one superintendent’s first draft of standing tactical orders looked like imperfect, duplicative in places, and entirely honest:

Build the team first: Before the production plan, before the schedule, before the procurement log build the team. Connect the people. Make sure every person on the project knows who they are working alongside and what they are collectively trying to accomplish. Without the team, everything else is coordination, not production.
Break teams into smaller, nimble units: Large, lumbering project structures move slowly and respond poorly. Smaller functional units each with their own assistant superintendent, their own meeting cadence, their own accountability structure can pivot, respond, and improve faster than a single monolithic team. Napoleon’s tactical genius was not in the size of his armies but in how he structured them for speed.
Win the war before going to battle: Sun Tzu made this clear: amateur generals go to battle and then seek to win. Great generals win before the battle begins. In construction, this means pre-planning, pre-planning, pre-planning. The project that starts with a macro-level Takt plan, a pull-planned phase sequence, pre-construction meetings done, and the supply chain aligned that project has already won most of its battles before the first crew mobilizes.
Keep stability in the field: Perfect cleanliness, safety, and organization held as the number one priority, not something to achieve when things calm down. A clean, safe, organized site is not the output of a well-run project. It is the prerequisite.

Root out bad attitudes and behaviors: In any organization, roughly a third of people are fully bought in, a third are neutral, and a small percentage five to fifteen percent will actively work against the culture. Not because they are bad people, but because of bad behavior or circumstances that have shaped them to respond that way. Hurt people hurt people. Those behaviors do not belong on the project. Address them without punishment but without tolerance because the culture of the whole depends on protecting it from the behaviors that erode it.
Fanatically remove roadblocks and clear the way out ahead: This is the production discipline that keeps the Takt plan alive. Not reactive roadblock management proactive, upstream, fanatical clearing of the path before the train arrives. Every day.
Lead with communication and transparency: The team cannot see the plan unless the plan is communicated. The team cannot trust the system unless the system is transparent. Leadership is not authority it is clarity, delivered consistently and honestly, until the team can see as a group, know as a group, and act as a group.

Why Standing Tactical Orders Enable Decentralized Command

One of the most powerful outcomes of standing tactical orders is that they enable decentralized command the fourth law of the builder’s planning method. When the team knows the standing tactical orders deeply enough to act on them independently, they do not need the leader in the room for every decision. The superintendent walking a different part of the site, the project manager in a meeting, the general superintendent on another project none of that creates a leadership vacuum if the team has internalized the orders.

The question to test this is simple: does everyone on the project site know the standing tactical orders and what to do as a default when the leader is not there? If the answer is yes, the culture is self-sustaining. If the answer is no, the project is dependent on the leader’s physical presence in a way that creates fragility because leaders cannot be everywhere at once, and projects do not stop moving when the leader steps away.

How to Create Standing Tactical Orders

This is the part where the work is personal. The principles above are examples a starting point from a superintendent’s first draft, not a template to be copied exactly. Standing tactical orders that work are the ones the leader has actually thought through, believes in deeply enough to defend, and has communicated clearly enough that the team can repeat them without looking them up.

Here are the questions that shape effective standing tactical orders:

What does this team do first, always, before anything else? What is the non-negotiable standard that governs the environment cleanliness, safety, organization? What does the team prioritize when two important things are competing for attention? How does the team make decisions when the leader is absent? What behaviors are absolutely not tolerated, and what happens when they surface? How does the team communicate with what frequency, in what format, to whom?

The answers to those questions are the standing tactical orders. They do not have to be perfect on the first draft. The superintendent’s first draft had duplications and was slightly out of order. That draft still governed a project team that operated with clarity and consistency because the leader believed in what was written and communicated it until the team internalized it.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

The Challenge

Write the standing tactical orders for your project, your team, or your company this week. Not a mission statement operational principles that the team can act on as a default. Publish them. Communicate them in the morning worker huddle. Post them in the trailer. Ask team members to recite them. And then watch what happens to the project’s capacity to sustain itself, solve problems, and protect its culture even when the leader is somewhere else.

The best commanders do not win through their constant presence. They win by building teams that carry the standards forward without being asked. That is what standing tactical orders make possible.

As Taiichi Ohno says, “Without standards, there can be no improvement.”

On we go.

Frequently Asked Questions

What is the difference between standing tactical orders and a company policy document?
Policy documents govern compliance. Standing tactical orders govern culture. A policy tells people what they are not allowed to do. Standing tactical orders tell people what the leader expects them to do by default how to make decisions, what to prioritize, what the standard looks like so that the team functions with clarity and consistency without requiring constant direction.

How detailed should standing tactical orders be?
Detailed enough to be actionable, concise enough to be memorable. A list of seven to ten principles that every team member can recall and apply is more valuable than a comprehensive document that no one reads. The test is whether someone new to the team could read the orders and immediately understand how this leader runs a project.

How do standing tactical orders connect to decentralized command?
They are the enabling mechanism. Decentralized command only works when every member of the team understands the mission and the standards well enough to make good decisions in their sphere independently. Standing tactical orders communicate those standards explicitly and repeatedly until they are internalized at which point the team can act without waiting for permission, and the leader can trust that the culture holds even when they are not in the room.

If you want to learn more we have:

Discover Jason’s Expertise:

What Is Lean Construction? A Field Builder’s Guide to The Lean Way

Posted on July 31, 2026July 31, 2026 by admin

Read 21 min

What Is Lean Construction? A Field Builder’s Guide to the Lean Way

There is a word that gets thrown around in construction more than almost any other right now Lean. Lean training. Lean projects. Lean culture. And in most cases, the teams using the word have grabbed one or two tools from the Lean toolbox and called it a transformation. Pull plans on sticky notes. A morning huddle. Maybe a Takt schedule. And then they wonder why the project still feels chaotic, why the trades are still disengaged, and why the results are not what the books promised.

The tools are not the problem. The sequence is. Lean is a framework of six principles that must be built in a specific order because each one is a prerequisite for the next. Skip the foundation and everything built on top of it eventually falls.

This is the Lean way. Not a toolset. A way of building.

Principle One: Respect for People, Nature, and Resources

Everything starts here. Not just as a value statement as a production standard. Respect is visible. Walk onto a project where genuine respect is present and you will know it within the first thirty seconds. The site is clean, safe, and organized. The superintendent is in the morning worker huddle connecting with every worker on the job not managing from a trailer. Leaders pick up trash as they walk the site. Workers are safe to speak up without fear of retaliation. The bathrooms are beautiful, the lunch areas are maintained, the onboarding and orientation are real, and there are monthly barbecues or events that signal the team is valued as human beings not just as production units.

Respect also means that when someone needs to leave the project whether for performance or conduct it is never handled as punishment. It is handled as a decision made in the interest of the whole team, delivered with dignity. Throwing people away is not an option in a system built on respect.

Without this foundation, nothing else in the Lean framework holds. The tools look right but feel hollow. The trades stay guarded. The team never fully buys in. And the first moment of pressure reveals that the system was never actually rooted in anything.

Principle Two: Stability and Standardization

Stability cannot be skipped. It cannot be rushed past to get to the more interesting Lean tools. Without stability, there is no environment in which flow, participation, or continuous improvement can exist because instability consumes all available attention just managing the chaos.

Stability means 5S sort, straighten, shine, standardize, sustain applied to the site environment until clean, safe, and organized is not a goal but a baseline. It means standard work at the crew level, where everything done in a zone is documented visually so that quality is not dependent on memory or individual judgment. It means the meeting cadence is consistent, the supply chain is reliable, and the crew arrives to a ready environment rather than a treasure hunt.

One of the most important observations from studying how Lean systems succeed or fail is this: a stable project looks boring. The deliveries are coordinated. The huddle covers predictable topics. The zones are clean and the handoffs are routine. And occasionally, a leader craving the adrenaline of firefighting abandons the system because it stopped feeling urgent. Then the fires return. And they look back and cannot understand how the project that was running so well deteriorated so fast. Stability is the fastest, most productive, most profitable way to run a project. It just requires the discipline to protect it when it stops feeling exciting.

Principle Three: One-Piece and One-Process Flow

Once stability exists, the next step is one-piece flow doing one thing at a time, completely, before moving to the next. In construction terms: plan the work, build it right, finish as you go. One zone. One process. One handoff complete before the next zone begins.

Batching is the enemy of this principle. Batching means starting many things simultaneously, advancing all of them partway, and then finding that all of them need rework or attention at the same time. It feels productive lots of things are moving. But none of them finish cleanly, handoffs are incomplete, and the team spends more total time managing the overlap than they would have spent doing things sequentially in the first place.

One-piece flow at the crew level means each crew completes their scope in a zone fully, to the quality standard, verified before handoff before moving to the next zone. It means a project engineer processes one submittal through to completion before starting the next. It means a foreman resolves one roadblock before picking up the next. The discipline of focus produces results that multitasking never matches.

Principle Four: Flowing Together on a Takt Time

Once one-piece flow is established at the individual and crew level, the next question is whether everyone is flowing together at the same pace. Not just whether individual crews are working well whether the train of trades is moving through the building in a coordinated rhythm, all going the same speed, the same distance apart, in the same direction.

This is the Takt Production System. The pace is set not by the fastest crew or the most optimistic estimate, but by the slowest constraint in the system because the speed of the whole train is governed by the speed of the slowest car. Optimizing constraints, building the right zone count, pacing the supply chain to match the production rhythm all of this comes from the Takt plan and serves the goal of the entire team flowing together.

Pulling information, materials, and resources just in time to support that rhythm is the pull component. Nothing arrives early enough to create congestion and nothing arrives late enough to stop the train. Everything is timed to the production system.

Principle Five: Total Participation and Visual Systems

A team that cannot see the plan cannot participate in it. Visual systems are the mechanism that makes total participation possible because when the plan, the problems, the constraints, and the status are all visible to everyone, the genius of the whole team can be applied to the work, not just the genius of whoever is at the top of the org chart.

See as a group. Know as a group. Act as a group. That is total participation. It is the principle most consistently underperformed in Western construction culture, where individual heroism and siloed decision-making are deeply embedded. Working together collaboratively not because it is mandated but because the systems make it natural and safe is what separates high-performing project teams from ones that are technically capable but never quite synchronized.

Visual systems make this real: the zone map on the crew board, the weekly work plan posted at the work area, the installation work package available in the zone, the huddle board visible to everyone at the morning gathering. When information is visual and shared, participation is not a culture initiative. It is a production outcome.

Principle Six: Quality and Continuous Improvement

Quality is the output of everything that came before it. When people are respected, the environment is stable, work flows one piece at a time, the team moves on a consistent rhythm, and everyone can see and participate quality is the natural result. Defects surface because the system sees them. Problems are solved because the team has the capacity and the visibility to solve them. Continuous improvement becomes possible because there is stability to improve on.

Here is the logical chain that makes the sequence non-negotiable: quality and continuous improvement require total participation. Total participation requires visual systems that let the team see together. Seeing together requires flow. Flow requires one-piece process. One-piece process requires stability. And none of it matters without a foundation of respect.

Here are the six principles in their proper sequence each one building on the one before it:

Respect for people, nature, and resources the foundation that makes every other principle possible
Stability and standardization the clean, safe, organized environment that allows the system to be seen and improved
One-piece and one-process flow completing work fully, zone by zone, before moving forward
Flowing together on a Takt time the whole train moving at a consistent rhythm, pulling what it needs
Total participation with visual systems see as a group, know as a group, act as a group
Quality and continuous improvement the natural outcome of a system built correctly from the ground up

Why This Matters for the First Planner, Takt, and Last Planner Systems

The builder approach the learning habit, personal organization system, short and long-term habits, planning method, meeting system, and the Lean way is not a collection of independent best practices. It is a preparation sequence. Building these habits and principles into people before asking them to implement the First Planner System, the Takt Production System, and the Last Planner System is what determines whether those systems take root or fail on contact with the first difficult week of execution.

We build people before we build things. That sequence is the whole point. Lean cannot be implemented by a team that has not internalized respect and stability. The Takt plan cannot be protected by a team that has not built the habits of daily drawing study, six-week look-ahead, and pre-construction discipline. The Last Planner System cannot generate real commitments from foremen who have never experienced a project team that actually supported them.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

The Challenge for Every Builder

Walk your project this week and evaluate it honestly against all six principles in order. Is there genuine respect present, visible in the environment and felt by the workforce? Is the site stable, clean, safe, and organized? Is work flowing one piece at a time with clean handoffs? Is the whole team moving together on a rhythm? Can everyone see the plan and act on it together? Is quality being built in rather than inspected for?

The answer to those questions tells you exactly where to start. Not at the top of the list at the first principle where the answer is no. Fix that. Build on it. Move to the next one. That is how Lean takes root in construction not with a training event or a new software, but with the honest, disciplined, sequential building of a system that respects the people inside it and protects them every day they show up to build.

As Jason Schroeder says, “Lean is the willingness to learn and implement excellence for the benefit of people and humanity.”

On we go.

Frequently Asked Questions

Why must Lean principles be implemented in a specific order?
Because each principle is a prerequisite for the next. Stability cannot exist without respect. Flow cannot exist without stability. Total participation cannot exist without visual systems that make the plan visible to everyone. And continuous improvement cannot exist without total participation. Skipping or reordering the sequence produces a system that looks like Lean but does not perform like it.

What does total participation mean in a construction context?
Total participation means every person on the project from the superintendent to the newest apprentice can see the plan, understand their role in it, and contribute to improving it. It is enabled by visual systems and a culture of respect where speaking up is safe and valued. In Western construction, this is the principle most commonly missing, and its absence is why most Lean rollouts underperform.

How does the Lean way connect to the Takt Production System?
The Takt Production System is the operational expression of the fourth Lean principle flowing together on a Takt time. But it cannot function without the first three principles already in place. Teams that implement Takt without establishing respect, stability, and one-piece flow first find that the plan does not hold because the foundation beneath it was never built.

If you want to learn more we have:

Discover Jason’s Expertise:

How to Run Jobsite Huddles That Don’t Waste Time (Meeting System)

Posted on July 30, 2026July 30, 2026 by admin

Read 20 min

How to Run Jobsite Huddles That Don’t Waste Time

There is a statement worth writing on the wall of every project trailer: good meetings are the price we pay for alignment. Not a cost to be minimized. An investment in the only thing that makes a construction project actually work a team that is moving together, in the same direction, toward the same plan, at the same time.

The meeting and huddle system is not a calendar of recurring events. It is a production system. When it flows correctly, information moves from the macro plan all the way down to the crew standing in a zone, every day, without gaps. When it does not flow when meetings are scattered, redundant, or disconnected from each other the project loses alignment, and alignment loss is a production problem, not just a communication problem.

Why Meeting Flow Is the Real Issue

The most common meeting failure in construction is not that teams meet too much or too little. It is that the meetings do not flow. Information produced in one meeting does not automatically connect to the next. The look-ahead produced in the trade partner weekly tactical is not the same document the crew sees in the field. The plan committed to in the weekly work plan does not match what gets communicated in the morning huddle. The roadblocks identified in the afternoon foreman huddle are not resolved by the team daily huddle the next morning.

Each meeting should feed the next. The macro-level Takt plan governs the strategic planning meeting. The strategic planning meeting aligns the milestones and supply chain that the trade partner weekly tactical pulls from. The trade partner weekly tactical creates the look-ahead and weekly work plan that feeds the afternoon foreman huddle. The afternoon foreman huddle creates the day plan that makes the morning worker huddle meaningful. This is not a communication chain it is a production cascade, and the cascade only works if every meeting does its job and passes the right output to the next level.

The Strategic Meetings: Team Weekly Tactical and Strategic Planning

The team weekly tactical is the weekly alignment meeting for the project delivery team. It covers coverage and PTO so the team knows who is available to support the trades. It covers schedule, quality, finances, and safety with safety anchoring the front of the agenda, not the back. But the core question driving this meeting is whether the project delivery team has the balance, coverage, and capacity to actually support the trades throughout the week. If the answer is no, the meeting has not done its job.

The only purpose of a general contractor is to support the trades. Not to manage them. Not to direct them from a trailer. To support them to clear their path, provide their resources, coordinate their integration, and make sure every zone they enter is ready for them to install. If the project delivery team cannot do that for the coming week, the meeting needs to solve it before the trades arrive.

The strategic planning and procurement meeting is where the PM, superintendent, and schedulers align the macro-level Takt plan tracking milestones, confirming supply chains are paced to support the production rhythm, and ensuring buffers are in place where the plan needs them. This meeting is forward-looking. It is not a status review. It is a strategic confirmation that the system is pointed in the right direction and the logistics are lined up to support it.

The Trade-Facing Meetings: Trade Partner Weekly Tactical and Foreman Huddle

The trade partner weekly tactical is the most important recurring meeting for connecting the plan to the field. This is where the six-week look-ahead and weekly work plan are produced not invented from scratch each week, but filtered from the pull plan and the production plan that was built collaboratively with the trades when the phase was planned. The industry gets this wrong consistently. The look-ahead and weekly work plan are filters, not new creations. If they require significant rework each week, the pull plan was not done right, or the production plan has drifted from reality.

This is the meeting where trade partners specifically the foremen, the last planners weigh in and buy in. When a foreman participates in building the weekly work plan, they are not just acknowledging a schedule. They are making a commitment. That commitment is real because they shaped it. And when they walk onto the site the next morning, they know what they committed to and why. That is the difference between a plan the crew executes and a plan the crew ignores.

The afternoon foreman huddle, held the day before not the morning of is where the next day is planned in full detail. Daily reports come in. Roadblocks are identified, discussed, and solved. Permits are collected confined space, hot work, whatever the next day’s work requires. Foremen leave that meeting with everything they need to mobilize their crews the next morning without a single call back to the office.

This meeting must happen the day before. Planning the day of is not planning. It is rushing and rushed planning produces rushed work. The foreman who walks into the morning worker huddle already knowing the plan, having resolved the roadblocks the night before, can deliver a morning communication that is clear, confident, and worth the five minutes everyone is giving it.

The Field Meetings: Morning Worker Huddle and Crew Prep Huddle

The morning worker huddle is where the whole project comes together workers walking from the parking lot to the huddle area, gathering for five to seven minutes before splitting off into their work. Not longer. Five to seven minutes, tightly run, with four specific purposes: connection and social group building, two minutes of training on a relevant topic, communication of change points for the day, shoutouts for performance worth recognizing, and a clear statement of the day’s plan.

That plan exists because of everything that happened the day before. The afternoon foreman huddle built it. The foreman carried it to the morning worker huddle. The crew receives it as something real not improvised, not approximate, but the actual plan for the actual day. The morning worker huddle is the delivery mechanism. The work to make it valuable happens the afternoon before.

After the morning worker huddle, crews split to their crew preparation huddle gathering near their gang box, conics box, or work area to prep for the day individually and as a crew. This is where the installation work package from the pre-construction meeting lives the visual checklist and quality standard that shows exactly what good looks like in this zone, for this scope, at this stage.

The Office-Field Integration: Team Daily Huddle

The team daily huddle is where the office and the field combine. Project engineers and project managers stand up for five to ten minutes, aligned around a scrum board, prioritizing the tasks that support the field getting materials to workers, providing information, solving design conflicts, resolving permissions and jurisdictional requirements, removing roadblocks. The office is not separate from the field. The office exists to serve the field. This meeting makes that real every day.

Here is how the full meeting system cascades from strategy to crew:

Team weekly tactical: project delivery team alignment on coverage, milestones, safety, and capacity to support trades
Strategic planning and procurement meeting: macro Takt plan review, supply chain confirmation, milestone alignment
Trade partner weekly tactical: six-week look-ahead and weekly work plan filtered from the pull plan, built collaboratively with foremen
Afternoon foreman huddle (day before): daily reports, roadblock resolution, permit collection, day plan confirmed
Morning worker huddle: five to seven minutes, connection, two-minute training, change points, shoutouts, day plan communication
Crew preparation huddle: crew-level prep with installation work package and quality visual at the gang box
Team daily huddle: office-field scrum standup, roadblock removal, field support tasks prioritized

What Flows and What Doesn’t

The test of the meeting system is whether information flows without loss. The macro plan should be visible in the strategic meeting, filter into the trade partner weekly tactical, compress into the weekly work plan and look-ahead, distill into the day plan, and land on the crew board in the zone. If any link in that chain breaks if the weekly work plan does not match the look-ahead, if the afternoon huddle did not resolve the roadblocks before the morning worker huddle, if the crew prep huddle has no installation work package the system has a leak. The crew in the zone is the ultimate end point of everything this system produces. They should be able to walk into their zone, look at their crew board, see their weekly work plan and daily activities with visuals, reference their installation work package, and build the work in that Takt time without having to ask a single question.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

The Challenge of Running It Right

The meeting and huddle system is scalable. On a project in the $1 to $150 million range, the system described here is the right size. On a mega project, each functional area may run its own system, with the same meetings operating fractally at the functional area level. Smaller projects compress the system but do not eliminate it the minimum is always the trade partner weekly tactical and the daily huddle, with the rest scaled to the project’s complexity.

The meeting system does not run itself. It runs because a leader on the project takes it seriously, holds every meeting to its format, ensures the outputs feed the next level, and refuses to let the system drift into general conversation, status reporting, or complaint sessions. Every meeting has a specific output. Drive for that output. Leave with it. Pass it to the next meeting. That is the discipline that keeps the project in rhythm.

As Jason Schroeder says, “Plan it first, build it right, finish as you go.”

On we go.

Frequently Asked Questions

Why must the day be planned the afternoon before not the morning of?
Because planning in the morning of means the crew is already assembled and waiting while the plan is being made. That is wasted production time and it produces rushed, incomplete plans. Planning the afternoon before means roadblocks are resolved overnight, permits are already collected, and the morning worker huddle communicates a real plan rather than improvising one in front of the crew.

Are the look-ahead and weekly work plan created from scratch each week?
No and this is one of the most common mistakes in the industry. The look-ahead and weekly work plan are filters from the pull plan and the production plan built collaboratively with trades during phase planning. They should require minimal rework each week because the sequence and commitments were already established. If the look-ahead requires significant creation each week, the pull plan was not done adequately.

How does the team daily huddle connect the office and the field?
The team daily huddle is a five-to-ten-minute scrum standup for the project delivery team engineers and project managers where the day’s support tasks for the field are prioritized. It is not a field meeting. It is the mechanism by which the office team orients itself around what the field needs today: materials, information, RFI answers, permit confirmations, and roadblock resolution. The office exists to serve the field, and this meeting makes that orientation explicit every single day.

If you want to learn more we have:

Discover Jason’s Expertise:

How to Plan Construction Work the Right Way (The Builder’s Method)

Posted on July 30, 2026July 30, 2026 by admin

Read 21 min

How to Plan Construction Work the Right Way: The Builder’s Method

There are methods for planning that show up in military strategy, business leadership, and high-performance teams around the world — and when you strip them down to first principles, they come back to the same core pattern. Build the team. Simplify the mission. Prioritize and execute. Decentralize command. These are the laws of combat, taught by Jocko Willink and Leif Babin through Extreme Ownership — and they apply to construction planning at every level, from company strategy all the way down to a single crew task.

This is the builder’s planning method. And if you apply it consistently, everything else in the builder approach — the learning habit, the personal organization system, the short and long-term habits — gets compounded.

The Pattern Most Teams Miss

Before getting into the four laws, consider what happens when teams try to solve complex problems without a structured planning framework. They silo. Individuals or small groups go off and work independently on their piece without aligning with the whole. The loudest voices dominate, and the introverts who often have the clearest view of the problem stay quiet. Nobody appoints a leader. Nobody articulates the mission clearly. Everybody has their own version of what success looks like. And then they wonder why the result is fragmented.

There is a team exercise that illustrates this perfectly. Two opposing lines of people have to swap sides without breaking specific rules — and it seems nearly impossible until the group follows a simple sequence: appoint a leader, understand the mission, gather information, make a plan, communicate that plan, then execute. Every time a team follows that sequence, they solve the puzzle. Every time they skip it, they stay stuck.

The pattern is the same on a construction project. Complexity does not require heroics. It requires a structured approach applied consistently by people who know their role within it.

Law One: Cover and Move — Build the Team

Cover and move is the first law of combat. In military terms, it means one element covers while another moves — mutual support, working together toward the objective. In construction terms, it means building a team where everyone knows what they are responsible for, who they are supporting, and how the whole moves together.

This is not about org charts. It is about function. Does every person on the project team know what they are covering and what they are moving toward? Does the superintendent know the project manager’s priorities and vice versa? Do the foremen know what the superintendent needs from them and what they can expect in return? Does the trade partner know the GC is working for them — and does the GC act that way?

A team that covers and moves together does not produce isolated wins. Every person’s role is understood as a contribution to the shared objective. When one element is pinned down, another covers. When one person is overloaded, the team adjusts. The project delivery team functions as a unit, not as a collection of job titles doing separate work.

Building this team is the most important thing a leader does before the project starts. And it is never a one-time effort. The team is built and maintained through every meeting, every huddle, every interaction — through the clarity of mission, the quality of training, and the consistency of support.

Law Two: Simplify — Make the Mission Clear and Visual

The second law is simplify. The mission must be so clear that every person on the team can state it without hesitation. Not a mission statement from a framing meeting that nobody remembers. The actual objective — what the team is trying to accomplish in this phase, this week, today — stated clearly enough that every crew member can verify whether they are contributing to it.

Simplicity means eliminating ambiguity. In construction, ambiguity is everywhere. Drawings that contradict each other. Sequences that were never communicated to the foremen. Material deliveries that were confirmed to the PM but never communicated to the crew waiting for them. These are all failures of simplicity. They happen when the mission is assumed to be understood rather than made explicit.

The visual component matters as much as the verbal one. One look away — one glance at the Takt plan, the daily huddle board, the zone map, the weekly work plan — should tell a crew member exactly where they are, what they are doing, and what comes next. If the plan requires explanation every time someone looks at it, the plan is not simple enough.

Standard work lives here too. When the standard for a task is documented visually and accessible at the point of work, the crew does not need to ask. They look. They execute. They verify. That is the power of a simple, visual mission.

Law Three: Prioritize and Execute — First Things First

The third law is prioritize and execute. In the heat of a project, when multiple problems are surfacing simultaneously, the instinct is to react to everything at once. That instinct is productive-feeling but counterproductive in practice. Trying to solve five problems at the same time means none of them gets the attention required to actually solve it.

Prioritize and execute means detaching from the emotional weight of every problem and making a clear-eyed decision about which one matters most right now. What is the constraint that is limiting flow most severely? What is the roadblock that is closest to touching the field? What decision, if made in the next hour, would protect the most production downstream? Solve that one. Then reassess. Then solve the next.

This ties directly to the Lean principle of one-piece flow applied at the leadership level. Do the most important thing. Finish it. Move to the next. Context switching — jumping between five unresolved issues — is as destructive at the leadership level as batching submittals is at the project engineer level.

Triage is not retreat. It is precision. The leader who can calmly assess a chaotic field situation, identify the most critical intervention, and execute on it without being pulled in five directions at once is the leader whose project stabilizes fastest.

Law Four: Decentralized Command — Let People Own Their Sphere

The fourth law is the one most misunderstood in construction: decentralized command. In an industry with deeply embedded top-down authority structures, the idea that everyone should act in their own sphere sounds like chaos. It is the opposite.

Decentralized command does not mean everyone does whatever they want. It means everyone understands the mission clearly enough to make good decisions within their area of responsibility without waiting for permission on every action. The foreman who has been in the pre-construction meeting, understands the conditions of satisfaction, has a clear installation work package, and knows the quality standard can make real-time field decisions that protect the mission — because they understand the mission.

The alternative is centralized command — every decision flowing up to the superintendent or the PM before anything happens in the field. This creates bottlenecks, slow responses, and a workforce that stops thinking because thinking is not their job. It is also exhausting for the leader at the top of the chain, who cannot possibly process every decision that a complex project requires.

The right delegation model is clear. When giving a mission to someone, do not throw it over the wall and say “go handle this.” Give them the mission, explain why they are the right person for it, and ask them to come back with a plan. Review the plan together — what have they considered, what gaps exist, what do they need? Then confirm they have what they need and let them own it. Hold them accountable — not with punishment, but with the support, training, and clarity that makes genuine accountability possible.

Here are the four laws applied to a single construction task or project planning situation:

Cover and move: Identify who is responsible for what, confirm mutual support between roles, and ensure the team is moving together toward the objective
Simplify: State the mission in a single sentence, make it visual, confirm standard work is accessible at the point of execution
Prioritize and execute: Identify the most critical constraint or roadblock right now, solve it completely, then reassess
Decentralized command: Confirm the team understands the mission well enough to act without waiting, assign ownership with support, not just instruction

Leadership as Clarity, Training, and Support

The planning method lands differently when leadership is understood correctly. Leadership is not authority. It is not volume or title. Leadership is clarity — defining the mission clearly enough that people can execute it. Leadership is training — equipping people with the skills and knowledge to carry out the mission at the required standard. And leadership is support — being present, removing obstacles, and backing up the people who are carrying out what was asked of them.

That definition comes directly from Japan — from the study of how the best production leaders operate in the systems they are responsible for. When a team member takes ownership of a mission because they were trusted with it, trained for it, and supported throughout it, accountability becomes real. They own the outcome because they built the plan. And the leader owns the outcome because they built the conditions that made success possible.

That is not soft. That is the most effective leadership model in any production environment — including construction.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

The Challenge

Take one task or one challenge on your project this week and run it through the four laws. Who is covering what? Is the mission simple and visual? What is the single most important action right now? Who can own this within their sphere, with the right support behind them? The answers to those four questions will sharpen the plan and produce a better outcome than any amount of reactive improvisation.

The builder’s planning method works at every level — company, department, project, phase, crew, task. The framework does not change. The scale does. Apply it with discipline and it will change the way everything gets planned, communicated, and executed.

As Jason Schroeder says, “If the plan requires burnout to succeed, the plan is broken, not the people.”

On we go.

Frequently Asked Questions

How does the builder’s planning method relate to the Takt Production System?
The four laws provide the human leadership framework that makes Takt function. Cover and move ensures the team supports each other across roles. Simplify ensures the Takt plan is visible and clear at every level. Prioritize and execute ensures constraints and roadblocks are addressed in the right order. Decentralized command empowers foremen as last planners who can make field decisions that protect the rhythm.

What is decentralized command and why does construction need it?
Decentralized command means that everyone understands the mission well enough to make good decisions in their sphere without waiting for permission. Construction needs it because the field moves faster than any central command can process. Foremen who understand the mission and have been trained and equipped to carry it out make better real-time decisions than ones who wait for direction on every issue.

How do you hold someone accountable without punishment?
By giving them a mission they participated in building, training them to execute it, and providing the support they need throughout. Accountability built this way is internalized — the person owns the outcome because they owned the plan. Punishment-based accountability produces compliance at best and resentment at worst. The builder’s planning method produces genuine ownership.

If you want to learn more we have:

Discover Jason’s Expertise:

Three Long-Term Habits That Build Great Construction Leaders

Posted on July 29, 2026July 29, 2026 by admin

Read 19 min

Three Long-Term Habits That Build Great Construction Leaders

There are leaders in construction who seem to stay ahead no matter what the project throws at them. Their schedules hold. Their trades are prepared. Their phases close out on time. And they keep getting promoted not because they are louder or more aggressive, but because the project works when they are running it.

The difference is almost never talent. It is discipline. Specifically, the discipline of three long-term habits done consistently, on every phase, without exception. These are not short-term wins. They are the behaviors that compound over a career and separate the builders from the brokers.

Habit One: Pull Plan Every Phase Three Months Out

Every phase of work needs a pull plan a collaborative, reverse-scheduled sequence built with the trade partners who will do the work, from the milestone backward, three months before that phase begins.

A pull plan done well accomplishes four things simultaneously. It establishes the right sequence the order in which trades and activities must flow based on what the work actually requires, not what someone assumed it would require from a desk. It optimizes system constraints the limiting factors in the production system that cannot be eliminated but can be designed around. It establishes the buffers needed to give the plan a realistic chance of hitting the milestone. And it creates buy-in because the foremen and trade partners who built the plan are committed to it in a way that an inherited plan never produces.

The pull plan is also broken down by zone not a single solid sequence across the whole phase, but the sequence validated zone by zone, so that the time required in each zone is grounded in reality and the flow of trades through the phase is visible. The industry habit of pulling a whole area as one continuous line is not a pull plan. It is a list. Lists do not produce flow. Zone-by-zone sequencing does.

Three months is not arbitrary. It is the minimum lead time required to act on what the pull plan reveals to order materials, onboard trades, hold pre-construction meetings, verify production rates, and clear roadblocks before they reach the field. Pull planning two weeks before a phase starts produces a pretty picture and no time to use it.

Habit Two: Hold Pre-Construction Meetings for Every Trade

Pre-construction meetings are the mechanism that turns a plan into a prepared crew. Every single trade needs one not a group meeting where all trades receive general instructions together, but a dedicated meeting for each trade, three weeks before they mobilize into their first zone.

The purpose of the pre-construction meeting is to get everything collected for the installation work package before the crew ever steps foot in the zone. That means the scope is reviewed in detail. The sequence is walked through. The conditions of satisfaction are defined what does good look like, what does finished look like, what does quality look like for this specific crew in this specific zone. The crew gets a single visual installation guide they can take into the field and reference without hunting for information.

This is also where full kit is confirmed. Does this crew have everything they need? Labor committed and ramped to the right size. Materials confirmed on their delivery schedule. Tools and equipment staged. Permits and permissions in place. Layout ready. RFIs answered. When the pre-construction meeting closes, the answer to all of those questions should be yes or there should be a clear action plan for making it yes before the crew mobilizes.

When pre-construction meetings are skipped, crews show up to treasure hunts. They ask where to go, what to do, what the plan is. They find missing information, uncleared substrates, materials that were not delivered, and conditions they were never told to expect. The first week of every phase on a poorly planned project is a recovery week not a production week. Pre-construction meetings eliminate that waste before it happens.

Habit Three: Look Ahead Planning Six Weeks Out Consistently

The six-week look-ahead is not a document. It is a discipline. The question it asks is simple: what would have to be true in six weeks for that work to go well? And then it demands action on whatever the answer reveals.

Six weeks is the right window because it provides enough lead time to act on problems before they reach the weekly work plan. If something surfaces in the look-ahead as missing a submittal not approved, a trade not yet confirmed, a piece of equipment not yet ordered, a pre-construction meeting not yet scheduled there are four weeks before that item reaches the weekly work plan to resolve it. Four weeks of lead time to prevent a problem that would otherwise derail a week of production.

The goal of the look-ahead is a weekly work plan that is roadblock free. Not mostly free. Not close to free. Free. When the look-ahead is done with discipline reviewed weekly, acted on immediately, updated as the work progresses the weekly work plan becomes a commitments document, not a hope document. The trades can make real commitments to what they will complete because the path has been cleared ahead of them.

Procurement belongs in this system too. The delivery of materials, the release of fabrication orders, the submittal approval dates all of it should be visible on the same production plan, linked to the phase and zone where the materials are needed. When procurement is integrated into the look-ahead and the pull plan, supply chain surprises stop happening because someone was tracking the chain far enough ahead to see the gap before it became a crisis.

Why These Three Root Causes Keep Showing Up

Research into the root causes of constraints and roadblocks on construction projects reveals a consistent pattern. The most common root causes the things that, if they had been different, would have prevented the problem from ever reaching the field are the same three things every time.

An incomplete pull plan. A missing or inadequate pre-construction meeting. An improper look-ahead planning process. Those three gaps account for the overwhelming majority of the constraints and roadblocks that derail construction phases.

Weather can be a roadblock. Change orders can be a roadblock. Failed inspections can be a roadblock. But look at what prevents even those disruptions from compounding into project-level problems: pull planning that built contingency into the sequence, pre-construction meetings that identified and prepared for the most likely issues before the work started, and look-ahead planning that caught the emerging problem with enough lead time to develop an alternative.

The three long-term habits are not just best practices. They are the root-cause prevention for the vast majority of what goes wrong on construction projects.

Here are the conditions the three habits create when followed consistently:

Pull plans three months out ensure sequences are validated collaboratively, constraints are optimized, and buffers are built in before execution begins
Pre-construction meetings ensure every crew enters their zone with full kit, a clear visual standard, and zero ambiguity about what the work requires
Six-week look-ahead planning ensures the weekly work plan is roadblock free because problems were identified and resolved weeks before they could touch the field

The Phase Is the Core Unit

Understanding why these habits matter requires a clear mental image of what a construction phase actually is. The phase is the core unit of Lean construction, of advanced work packaging, of everything done on a project site. Time moves across the top. Zones appear down the left side. Trade crews move through those zones, adding value to the building what Nicholas Modig calls the grow unit.

Each wagon in that phase is a construction work package. Each zone within the wagon is where an installation work package lives the specific scope of work a crew completes in one zone before handing off and moving to the next. That is the resolution at which the three long-term habits operate. Pull planning validates the sequence across zones. Pre-construction meetings prepare the crew for each wagon. Look-ahead planning ensures the track ahead of the train is clear before the train arrives.

When all three habits are in place, the phase runs as designed. When any one of them is missing, the phase absorbs the gap in delays, rework, trade stacking, or production loss that the team spends the rest of the phase trying to recover.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

The Career Case for These Habits

Leaders who follow the three long-term habits consistently get promoted. Not because they network better or perform better in meetings. Because their projects work. Their phases close on time. Their trades are prepared. Their schedules hold under pressure because the preparation was done far enough ahead to absorb variation without crisis.

That track record is visible. Owners notice. Companies notice. And over a career, the leader who does these three things on every phase builds a reputation that no amount of personality or self-promotion can replicate because the results speak louder and last longer than any individual win.

Do these three things. Do them on every phase. Keep doing them when pressure mounts and the instinct is to skip preparation and just push forward. That is when the discipline matters most. And that is when the habit separates the great builders from everyone else.

As Jason Schroeder says, “Respect for people is not soft it’s a production strategy.”

On we go.

Frequently Asked Questions

Why does pull planning need to happen three months before a phase starts?
Because three months is the minimum lead time needed to act on what the pull plan reveals. Materials need to be ordered, trades need to be confirmed and onboarded, pre-construction meetings need to be scheduled, and production rates need to be verified.

How is a pre-construction meeting different from a general coordination meeting?
A pre-construction meeting is trade-specific, held three weeks before that trade mobilizes, and focused entirely on collecting everything needed for that trade’s installation work package. It is not a general overview of the project. It results in a single visual installation guide the crew takes into the field. General coordination meetings happen at the team level.

What makes a look-ahead planning process effective versus just going through the motions?
An effective look-ahead process produces action, not just observation. Every gap identified in the six-week window missing submittal, unconfirmed crew, unordered material, unscheduled pre-construction meeting generates a specific action assigned to a specific person with a specific deadline. The test of whether the look-ahead is working is whether the weekly work plan is genuinely roadblock free.

If you want to learn more we have:

Discover Jason’s Expertise:

How to Enable Designers for Better Construction Outcomes

Posted on July 29, 2026July 29, 2026 by admin

Read 18 min

What Happens When You Don’t Enable the Designers

There is a pattern in construction that almost everyone has experienced and almost no one has named precisely: design react. The project team waits for design to come in, receives whatever the architects and engineers have produced, discovers it does not fit the budget or the schedule, and then starts cutting. Scope gets reduced. Systems get downgraded. Features the owner expected disappear. The team calls it value engineering. It is not. It is the lop and chop the expensive, demoralizing, trust-destroying consequence of leaving the design team alone instead of enabling and steering them.

Enabling the designers is the third phase of pre-construction. And when it is missing, the consequences are not theoretical. They are systematic, predictable, and expensive.

What Enabling the Designers Actually Means

The design team is not the enemy. Designers are capable, creative professionals with a difficult responsibility producing complex, coordinated documents that multiple disciplines must agree on while satisfying owner requirements, code requirements, and budget targets that are often in tension with each other. That is hard work. It does not go well when they are left to do it in isolation.

Enabling the designers means actively supporting them so they can succeed. It means not leaving them hanging and not letting the design drift unchecked until it becomes something the owner cannot afford and the project team cannot build.

In practice, enabling the designers requires four specific capabilities from the project delivery team.

The first is real-time budget control. Not a three-to-six-week wait for a trade partner to price something out. Not an estimating process that runs parallel to design on a time delay. An in-house estimating capability that tracks the budget in real time as the design develops so that the team knows, at any moment, whether the design is within reach or trending toward the lop and chop. Without this, the budget is a fiction until GMP proves it false.

The second is real-time scheduling. When Takt is the production system, the schedule can be updated and adjusted as the design evolves. The macro-level plan from phase two remains the anchor. As design decisions are made, their impact on the production sequence is visible immediately. Without this, design decisions get made in a vacuum, with no one asking whether the building can actually be built in the available time with the systems being specified.

The third is continuous model checking. Reviewing a design at milestones schematic design complete, design development complete is not constructability review. Real constructability review means being in the model as it develops, checking coordination between disciplines before conflicts get embedded, asking builder questions at every phase: how are we going to sequence this? Where is the crane going? How does this foundation interact with the existing structure? How does the MEP routing work given the structural ceiling conditions? These are builder questions. They require a builder in the room, not just an architect presenting drawings.

The fourth is helping the design team work as an integrated team. Architects often run ahead and leave the engineers behind. One firm completes their scope while others are still three weeks away. The mechanical engineer and the structural engineer have never resolved the conflict between their systems because no one organized the meeting where they would. Enabling the designers means running the meeting structure, the communication system, and the coordination cadence that actually integrates the design team rather than waiting for integration to happen organically, because it will not.

What Happens Without It

The pattern that plays out when this phase is skipped is consistent enough to be called predictable.

The architect runs ahead. They complete their portion on schedule. Then the team waits on the engineers structural, mechanical, electrical, plumbing each producing independently without full coordination. Milestones slip because the integrated review that would have caught conflicts and driven decisions never happened. The design arrives late, riddled with coordination problems, and partially unbuildable as drawn.

Design assist contractors and trade partners the people whose expertise could have solved problems in the design phase when changes are cheap are brought in but not listened to. Their input stays on the margin because there was no structured process for integrating it into the design decisions.

The facilities team that will eventually operate the building is frustrated before construction even starts. The systems are not coordinated the way the building will actually be used. Features that maintenance needs were not on anyone’s radar because no one organized the conversation with the end users during design.

And the budget is wrong. Not slightly wrong significantly wrong. Because no one was tracking it in real time, the design grew to include what the designers thought was appropriate, not what the budget could support. By the time the number is known, the project is committed to a scope it cannot afford. The options are: surprise the owner badly enough to damage the relationship permanently, or hand the construction team an unbuildable project and tell them to make it work.

Neither option is acceptable. Both are preventable.

Designers Are Partners, Not Problems

The mental model that treats design as something that happens to the construction team a deliverable that arrives, gets reviewed, and gets built is the root of this failure. Design is a production process. It has inputs, a sequence, interdependencies, milestones, and a delivery requirement. It should be managed like a production process, with the same rigor applied to a construction phase.

That does not mean controlling designers or treating them as subordinate. It means bringing the same respect, partnership, and system-thinking to the design engagement that the best projects bring to every other part of the production process.

Here are the conditions that break down when designers are not enabled:

Milestones miss because no integrated team meeting structure kept the disciplines coordinated and on pace
Budget accuracy deteriorates throughout design because no real-time cost tracking caught the drift before it became a crisis
Constructability problems get built in because no builder was reviewing the model as it developed, asking builder questions at every phase
Design assist trade partners are ignored because there was no structured mechanism for integrating their expertise into design decisions
The facilities team and end users are surprised by the building they receive because their needs were not integrated into the design process
The project team inherits a GMP surprise that damages the owner relationship and forces cuts nobody wanted to make

The Alternative

The alternative is not complicated. It is disciplined. The project delivery team stays close to the design team throughout the design phase not waiting, not reacting, but actively supporting, checking, and steering. Control estimates are maintained in-house with the capability to update them quickly as design decisions are made. The Takt-based schedule is used to evaluate design decisions against the production reality, not just the calendar. The model is checked regularly by people who know how the building will be built. The design team’s meeting and communication systems are organized and run by the project delivery team so that integration is not left to chance.

This is not the design team’s job alone. It is a shared production responsibility. The contractor’s role during design is not to wait for documents. It is to enable the team producing them to hit the targets that the production system requires.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

The Project the Owner Deserves

Owners hire design and construction teams because they trust those teams to deliver what they need on time, on budget, and with the quality and functionality they were promised. When the design phase is left to drift without active enablement, that trust is put at risk from the first week of design. The owner does not know that the budget is tracking wrong. The owner does not know that the systems are not coordinated. The owner does not know that the milestones are slipping. They find out at GMP, or worse, during construction when fixing it is maximally expensive.

Enabling the designers is not overhead. It is the production investment that protects the owner’s trust, the project’s budget, and the team’s ability to deliver what was promised. The team that does this well produces projects that close out on time, on budget, with satisfied owners who want to work with them again.

That is the standard worth building toward.

“Strive for continuous improvement, instead of perfection.”

Not on the approved list. Correcting before delivering:

As W. Edwards Deming says, “It is not enough to do your best; you must know what to do, and then do your best.”

On we go.

Frequently Asked Questions

What is the difference between a real constructability review and what most teams call a constructability review?
A real constructability review involves builders actively working inside the design model as it develops asking how systems will be sequenced, where cranes go, how the foundation interacts with adjacent structures, and whether the specified systems can actually be installed in the space provided. What most teams call a constructability review is marking up a set of drawings and noting what is not finished yet. Those are not the same thing.

Why does design react happen so often if everyone knows it leads to the lop and chop?
Because most project delivery teams do not have the in-house estimating capability, the Takt-based scheduling infrastructure, or the model-checking discipline to enable real-time design steering. Without those tools, the team’s only option is to wait, react, and cut. Developing those capabilities is what changes the default from design react to active enablement.

How should the project team organize the design team’s meeting and communication systems?
The same way a production system is organized on a construction site with a clear meeting cadence, defined milestones, a short-interval planning method (Last Planner or Kanban for design work), and transparent communication across all disciplines. The design team should not be left to self-organize. The project delivery team should run the coordination infrastructure and hold the integrated team accountable to the shared milestones.

If you want to learn more we have:

Discover Jason’s Expertise:

Why Construction Teams Must Set Targets Before Design Begins

Posted on July 29, 2026July 29, 2026 by admin

Read 19 min

What Happens When You Don’t Set the Targets in Pre-Construction

The pre-construction process has five distinct phases. Most teams rush through the first, skip the second entirely, and then wonder why the project is in trouble by the time construction starts. This blog is about the second phase building the design team and setting the targets and specifically what happens when it is missing.

The short answer: design misses milestones, budgets get blown, the project gets value-engineered into something worse, and the team inherits an unbuildable mess they never agreed to build. None of that is inevitable. All of it is preventable. But prevention requires doing the work that most teams skip.

Why Design Teams Are a Production Problem

Design is not a naturally efficient process. The technology has improved dramatically programs like Revit and Civil 3D have increased drawing speed by ten, fifty, sometimes a hundred times compared to hand drafting. But productivity has declined. Not because designers are less capable, but because most design teams operate in silos, communicate through email, batch their work, and function as disconnected specialists rather than an integrated production team.

This is the environment the project team is stepping into when they engage the design phase. Even the most progressive design teams will struggle with co-location, dedicated sprint work, and getting away from the batching habits that slow everything down. Knowing that in advance is not pessimism. It is a prerequisite for designing an engagement strategy that actually works.

If the team skips the step of building the design team and setting targets, the default takes over. The design team operates the way they always operate in silos, on their own schedule, with their own priorities and the project gets whatever comes out of that process, on whatever timeline it produces, with whatever budget it lands at. That is not a production system. It is hope with a design contract attached.

What Building the Design Team Actually Means

Building the design team is not a social event. It is a production setup. The pre-flight kickoff is where the work happens identifying with all stakeholders what success looks like, defining conditions of satisfaction, organizing how the team communicates, establishing the meeting structure, setting up the integrated team framework, agreeing on the scheduling method for design work (Last Planner, Kanban, or another short-interval system), and aligning on milestones.

None of that is possible if the team skips this phase. And without it, there is no shared definition of success, no common communication standard, no agreed milestone structure, and no integrated team just a collection of firms each doing their own thing, hoping that it assembles into something buildable at the end.

The other critical output of this phase is target setting. Not vague aspirational goals specific, right-to-left targets built from the macro-level Takt plan. This is the moment when the team stops designing whatever the design team feels like designing and starts designing what the project actually needs to be, by when it needs to be built, for what the owner can actually afford.

Why the Macro Takt Plan Must Come First

The macro-level Takt plan is the anchor of the entire design and pre-construction effort. Everything works from right to left from the project end date back through every milestone, every design phase deadline, every procurement trigger, every buyout date, every package release. The macro gives the team the total project duration. The total project duration enables a realistic budget. A realistic budget prevents the team from designing something the owner cannot afford.

This is the sequence that most teams skip. They start designing. They design what feels right or what the design team proposes. Then late in the process at or near GMP they discover the budget is broken. And what happens next is the thing everybody in construction has experienced and nobody wants to repeat: the chop-and-lop process falsely called value engineering.

Value engineering has a legitimate meaning. It is the discipline of finding better ways to achieve the same function at lower cost, without reducing quality. What most teams call value engineering is not that. It is cutting scope, reducing quality, and eliminating features that the owner thought they were getting after the owner thought the project was finalized. It is a disrespect to the owner, a failure of the pre-construction process, and a consequence of not setting targets from the beginning.

When the macro-level Takt plan is in place at the head of the design process, the budget is set honestly. The design milestones are real. The procurement lead times are built into the sequence. The long-lead items are identified and ordered on time. The design team knows exactly when each phase or construction work package must be complete not as a vague deadline but as a production requirement that the macro plan makes visible.

What Breaks Down Without This Phase

The consequences of skipping the targets phase are not subtle. They cascade.

Design milestones get missed because no one set them in a way that was connected to the construction production system. Design assist contractors and trade partners the people whose expertise should be informing the design are not listened to because their input was not structured into the process. The design comes out with coordination problems, details that cannot be built as drawn, and specifications that exceed the budget without anyone realizing it until it is too late.

The macro-level Takt plan is missing, so the team has no honest basis for the overall project duration. The duration gets estimated by intuition or by copying a previous project and both of those methods produce a number that does not reflect the actual production reality of this project, with these trades, in this location, at this scope.

Without the right duration, the budget estimate is wrong from the start. Too much was designed. The team now has two choices saddle the project team with an unbuildable project and tell them to make it work anyway, or surprise the owner with a number they never saw coming and risk losing the client relationship permanently.

Here are the conditions that break down when the targets phase is skipped:

Design teams operate without shared milestones tied to the production system, so they miss dates and no one has leverage to enforce them
Budget is set before the production duration is known, so it is almost always wrong
Design is completed without target value delivery, meaning the team designs what they want rather than what the budget can accommodate
Long-lead procurement is not triggered on time because the macro Takt plan that would have revealed the lead time requirements was never built
The team inherits an unbuildable or unaffordable design at the worst possible moment just before construction starts

What Setting Targets Actually Enables

When the targets phase is done well, the entire pre-construction effort runs on a foundation of honesty. The macro-level Takt plan shows the team how long the project actually takes. That duration enables a budget that reflects reality. The budget guides design so that the team is always designing toward something buildable and affordable. Design milestones are set in reverse from the construction production requirements not from the design team’s preferred schedule so that the design effort is actually synchronized with when the builders need the information.

The integrated design team has a meeting structure that works not a calendar full of disconnected reviews, but a cadence that mirrors the Last Planner or Kanban rhythm, with pull plans for design phases, six-week look-aheads for design deliverables, and weekly commitments that the whole team can see and hold each other to.

That level of organization is not overkill. It is the minimum standard for a complex, multi-discipline design effort where every missed commitment cascades into procurement delays, construction delays, and budget exposure.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Construction Is More Complex Than Manufacturing

One more thing worth naming clearly. There is a tendency in manufacturing and Lean circles to look at construction as a simpler application of production principles. It is not. In manufacturing, the production system the factory is built once, and then the same product flows through it repeatedly. The production system improves with each cycle.

In construction, three things happen simultaneously: the product is designed, the production system is built, and the product is manufactured. Every project requires building the factory and the product at the same time, with a design that is changing underneath the production system as it is being built. That complexity demands a higher level of pre-construction discipline not less. The macro-level Takt plan, the integrated design team, and the target-setting process are not overhead. They are the production engineering for the most complex delivery system in any industry.

Start with the macro. Work right to left. Set real targets before the design gets ahead of the budget. Build the design team like a production team. And protect the project from the chop-and-lop consequences that follow when this phase is missing.

As W. Edwards Deming says,”In God we trust; all others must bring data.”

On we go.

Frequently Asked Questions

What is target value delivery and why does it matter in design?
Target value delivery means designing toward a defined budget target rather than designing freely and then cutting to fit the budget afterward. When the macro-level Takt plan establishes the production duration and the duration informs the budget, the design team can make decisions throughout the design process that keep the project within reach rather than discovering at GMP that the design must be gutted.

Why does the macro Takt plan need to come before the budget is set?
Because the budget must reflect the real production duration, and the real production duration can only be known from a Takt-based analysis of how the trades will flow through the building. Budgeting before the macro plan is estimating by assumption. The result is almost always a budget that does not match the project either too tight or structured around a timeline that is not achievable.

What happens to design assist contractors if the targets phase is skipped?
They are brought in but not listened to. Without a structured process for integrating their input into the design milestones and conditions of satisfaction, their expertise stays on the margin. The design team proceeds without the production insight that design assist contractors provide and the constructability problems they would have caught show up in the field instead, where fixing them is far more expensive.

If you want to learn more we have:

Discover Jason’s Expertise:

General Offerings

Company Offerings

Systems

SUBSCRIBE NOW !

Subscribe to our newsletters and stay updated!

Related Books

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

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

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

Related Books

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

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

Related Books

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

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

Calumet "K"

faq

General Training Overview

Superintendent / PM Boot Camp

Takt Production System® Virtual Training

Onsite Takt Simulation

Foreman & Field Engineer Training

Testimonials

Testimonials

agenda

Day 1

Foundations & Macro Planning

day2

Norm Planning & Flow Optimization

day3

Advanced Tools & Comparisons

day4

Buffers, Controls & Finalization

day5

Control Systems & Presentations

faq

UNDERSTANDING THE TRAINING

VALUE AND RESULTS

PLANNING AND SCHEDULING TOPICS

APPLICATION & TEAM ADOPTION

VIRTUAL FORMAT & ACCESSIBILITY

faq

GENERAL FAQS

CURRICULUM & OUTCOMES

LOGISTICS & FORMAT

PRICING & VALUE

SEO-BASED / HIGH-INTENT SEARCH QUESTIONS