March 2026 - Page 2 of 18 - Elevate Constructionist

If You Don’t Send Your Folks to Training

Posted on March 30, 2026March 30, 2026 by Danny Jiménez⁩

Read 17 min

If You Won’t Let Your People Go to Training, You Are Running the Job Wrong

Let me be direct with you because this needs to be said clearly. If you have ever told someone on your project team that they cannot leave for training because you are too busy, you have just told the world three things: you do not know how to run a job, you do not care about the people you are supposed to be developing, and you are comfortable reproducing your own limitations in the next generation of builders. That is not a strong position to be in. And it is time we stop pretending it is acceptable.

The Pain That Plays Out Every Day

There is a field engineer in Flagstaff, Arizona. His company brought Elevate Construction in to run a Field Engineer Boot Camp. His superintendent refused to let him attend. There is a team in Birmingham, Alabama. Someone in that region wanted to bring a boot camp to their people. But when project managers and superintendents found out, they made it clear in tone, in words, in every signal they could send that leaving the job for training was not something they supported. So people did not go. And the opportunity to grow passed by.

These are not isolated stories. This happens all over the industry, constantly, and almost nobody calls it what it is: a failure of leadership.

The Failure Is in the Leader, Not the Schedule

Here is the logic that leaders use to justify blocking training. The job is busy. We cannot afford to lose people right now. We need everyone on site. The schedule is tight. What they are really saying when they run that logic is this: my project is so fragile, my systems are so thin, and my ability to manage the work is so dependent on everyone being present that I literally cannot function with one person missing for a few days. That is not a scheduling problem. That is a leadership problem.

A well-run project, managed by a leader with real systems and real clarity, can absorb a team member being absent for training. A project that cannot absorb that is already in trouble. The training absence did not cause the fragility. The fragility was already there, and the leader in that situation has just revealed it.

The System Failed Them But Now They Are Perpetuating It

I want to say something with empathy, even in the middle of being direct. Many of the leaders who block training were never developed themselves. They were promoted into roles without a real training pathway, placed into complex projects without adequate preparation, and left to figure it out through trial and error. The firefighting, the instinct to keep everyone close, the fear of letting go for even a few days that is what happens when someone was never given the foundation they needed. The system failed them. They did not fail the system. But here is where empathy has a limit: once you are in a position of leadership, you are responsible for what you pass on. Choosing to perpetuate the cycle is a choice.

What Blocking Training Actually Produces

When a leader tells their people they cannot go to training, three things happen. First, they hurt that person’s career directly. A field engineer who misses a boot camp because their superintendent blocked it loses not just the content of that training but the confidence, the connections, and the trajectory change that come with it. That is real professional harm caused by someone who was supposed to be building them.

Second, they model the behavior they claim to hate. The superintendent who complains that the industry does not develop enough strong leaders and then refuses to let their own people attend development training is producing exactly the outcome they are complaining about. You cannot build a better generation by handing them your worst habits.

Third, they demonstrate that they do not actually know how to develop people. The top three qualifications for a construction leader are not technical. They are: you genuinely love people, you know how to train them, and you know how to communicate clearly. A leader who says “I cannot let you go to training right now” has just disqualified themselves from all three. They are not developing anyone. They are extracting from people and calling it leadership.

Here are the signals that a leader is blocking training for the wrong reasons:

They frame training as a disruption to the project rather than an investment in the team
They expect people to figure out systems on their own that they themselves never learned
They have no structured development plan for the people reporting to them
Their project depends so heavily on individual presence that one absence creates instability

What Construction Leaders Are Actually Supposed to Do

Let me be unambiguous about this. The primary job of a superintendent, a project manager, or any leader in this industry is not to run around executing tasks. It is to build people who can execute at a high level consistently, inside a system that works. That means training people every single day in morning huddles, in one-on-one conversations, in structured development pathways. It means knowing how to transfer knowledge, how to articulate expectations, and how to create the kind of environment where someone can grow. If you are a leader in construction and you do not know how to train people, that is the gap that needs closing not the gap in your schedule caused by someone attending a boot camp.

The best superintendents are continuous learners. They are doing training themselves every year. They are reading, attending conferences, going to boot camps, getting Lean certifications. They hold their people to the same standard because they know what a career built on real development looks like versus one built on survival instincts inherited from an untrained generation. A trained, capable team member does not cost you more than they contribute. They protect your project, raise your standards, and reduce the fragility that makes you think you cannot afford to let anyone leave.

Connecting to the Mission

We build people before we build things. That is not a tagline. That is the sequence. At Elevate Construction, every boot camp, every training program, every book, every podcast is designed around one core belief: the construction industry gets better when its people get better. And people get better when leaders invest in them consistently, deliberately, and without the excuse of busyness. The job is always busy. The schedule is always tight. The leaders who build great teams invest in development anyway, because they understand that a trained team moves faster and safer than an untrained team scrambling from one fire to the next. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Send your people to training. Every time. Without hesitation. Let them develop into leaders who are better than the version of construction they inherited.

A Challenge for Every Leader Reading This

Look at your team right now. When was the last time someone on your project attended structured training outside of a toolbox talk? When was the last time you invested intentionally in the development of a field engineer, a foreman, or a project engineer who reported to you? If you cannot remember, that is the answer. Not the schedule. Not the budget. Not the busyness. The answer is that development is not yet structural on your project, and the people who work for you are absorbing the cost of that gap every single day.

As Paul Akers has said about Japan’s success, “Japan is Japan because of training.” The construction teams and companies that will define this industry twenty years from now are the ones investing in their people right now. Be one of them.

On we go.

Frequently Asked Questions

Is it ever acceptable to delay someone’s training for the project?

In rare cases, a genuine operational emergency might require a brief delay not a block. The standard should be that training gets rescheduled immediately, not shelved. A pattern of delaying training is the same as blocking it.

What if the project really is understaffed and cannot absorb an absence?

Then the staffing problem needs to be addressed, not the training. Using understaffing as a permanent justification for never developing people ensures the team stays understaffed and underprepared indefinitely.

How should a leader who blocked training in the past course-correct?

Acknowledge it, change the behavior immediately, and start investing in the team’s development now. The best time to build people was earlier. The second best time is today.

What makes someone qualified to lead in construction?

The top three qualifications are genuine care for people, the ability to train and develop others, and the ability to communicate clearly. Technical skill matters, but without those three, a leader extracts from their team rather than building it.

What are the best training options for construction leaders?

The Super PM Boot Camp and Foreman Boot Camp at Elevate Construction are purpose-built for field leaders. LeanTakt training develops production planning capability. Reading Elevating Construction Superintendents, The Lean Builder, and Patrick Lencioni’s books builds the leadership and systems thinking foundation that great leaders share.

If you want to learn more we have:

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

Discover Jason’s Expertise:

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

On we go

Having Schedulers Means We’re Doing It Wrong

Posted on March 30, 2026March 30, 2026 by Danny Jiménez⁩

Read 18 min

Do You Need a Scheduler? Here Is the Hard Truth

I am going to say something that might ruffle some feathers. I want you to hear me out completely before you decide whether you agree. If you need a dedicated scheduler on your construction project and I mean a person whose job is to build, update, and manage the schedule as a standalone role you are not solving a scheduling problem. You are masking a leadership development problem. And the sooner we are honest about that, the sooner we can fix the thing that actually needs fixing.

The Pain That Points Back to a Deeper Problem

Walk into the scheduling office of a typical large construction company and you will find smart, capable people doing work that should never have been separated from the project team in the first place. They are building recovery plans that the project team should be building. They are updating schedules that the superintendent and trades should be updating daily. They are running schedule update meetings that would be entirely unnecessary if the project had real production tracking in place.

Meanwhile, the superintendent on site has handed off one of their three most important responsibilities to someone else. Safety. Quality. Production planning. Those are the three things a superintendent cannot delegate. When a company creates dedicated positions to handle two of them, what they are really saying is that the superintendent in that role is not equipped to carry them. That is painful to hear. But it is the truth. And pretending otherwise is what keeps the industry stuck.

The Failure Pattern Is in How We Develop Superintendents

For too long, the industry tolerated a certain image of the superintendent. Arms folded. Too cool for the room. Does not know the software. Desk covered in clutter. Phone full. Manages by walking around and directing people loudly. That image is dead. It should have never been the standard to begin with. But because it persisted, companies compensated. They hired dedicated safety professionals to handle what the superintendent was not doing. They hired quality professionals to manage inspections and standards. And they hired schedulers to build and update the plan that the superintendent should own.

Here is the honest diagnosis: dedicated schedulers, dedicated quality professionals, and dedicated safety professionals exist at the project level primarily because we failed to build superintendents who could carry all three. That is a training failure. It is not a permanent feature of how construction has to work.

A Story That Changed How I See This

I spent time at Hensel Phelps early in my career and was always struck by one thing. The project teams did the scheduling. There was no scheduler sitting in a separate office producing a CPM file that the field could not read and did not follow. The superintendent owned the production plan because that was understood to be the superintendent’s job. The best companies I have seen operate the same way Petticoat-Schmitt, High Street Residential, Landmark, O’Shea Builders. None of them have dedicated schedulers. Their superintendents plan the work because planning the work is what superintendents are there to do.

When I worked in rooms full of project managers, I noticed that they were engaged, sharp, talking to each other, solving problems together. When I got into rooms of superintendents, too often I saw the opposite people who were closed off, defensive, unwilling to engage, not up to speed on technology or systems. That gap is not a personality difference. It is the result of an industry that stopped investing in superintendent development and then built support structures to compensate for the gap instead of closing it.

Why Dedicated Schedulers Are a Form of Waste

A scheduler at the corporate level is a signal that the company is too oriented toward litigation rather than building. A scheduler in pre-construction is a signal that the project team is not following a real collaborative planning process instead, someone is producing a schedule in a silo that the team then inherits without having built it or bought into it. And a scheduler running update meetings is a signal that the project is not doing what it should be doing every single day: checking off completed activities, tracking percent plan complete, finding root causes on misses, and managing the rhythm of the work in real time.

When Takt is being used correctly, there is no massive database to update. The macro-level Takt plans give you the project-wide KPIs. The train of trades is visible. Roadblocks are being removed ahead of the work. The trades and the superintendent are steering together daily. There is simply nothing left for a scheduler to do that the system does not already handle and handle better.

Here are the signs that a scheduler is actually masking a deeper system failure rather than solving a real problem:

The superintendent has little involvement in building or updating the schedule
Schedule update meetings are the primary mechanism for tracking progress
Foremen and workers do not know the schedule and do not reference it
Recovery plans are produced by an office function rather than the project team

What Superintendents Need to Own

The superintendent’s job is to create the environment and the rhythm for trade partners to succeed. That means three things above all else. Safety. Quality. Production planning. These are not transferable. A superintendent can absolutely have support staff for logistics, water-spider functions, field engineering, and other roles that genuinely free them to lead at the level they should be leading. Creating positions for those things makes sense. But taking safety, quality, or production planning away from the superintendent is not relieving them of burden. It is taking away the job.

Production planning specifically is the most important non-safety function a superintendent performs. The Takt plan is not a document handed to them by a scheduler. It is the tool they build with their trade partners, that they steer through Takt Steering and Control, that they use every day to protect the rhythm of the work and keep the train of trades moving. When a superintendent does not know how to do this does not know the software, has not been trained in Takt planning, cannot lead a pull plan that is a training deficit that needs to be closed. Not papered over with a dedicated position.

Connecting to the Mission

At Elevate Construction, we believe the industry’s future belongs to the trained, capable, technology-fluent, systems-thinking superintendent who owns their project completely not one who has been stripped of their core responsibilities because nobody invested in their development. We are not trying to overburden superintendents. We are trying to build superintendents who are genuinely equipped for the full scope of the role. That is what the Super PM Boot Camp is designed to do. That is what LeanTakt training produces. That is why we invest so heavily in developing field leaders who can actually carry the weight of their position with competence and confidence. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Schedulers are not the enemy. Many of them are talented and hardworking. But the position itself is a workaround for a problem that deserves a real solution: trained, capable superintendents who own their projects completely.

A Challenge for Leaders and Companies

If your company has dedicated schedulers at the project level, I want to ask you to do something uncomfortable. Instead of defending the position, trace it back to its origin. Why does it exist? What would have to be true of the superintendent on that project for the scheduler not to be needed? And then ask the harder question: are you investing in getting your superintendents to that place? Are you training them in Takt? Are you developing them in production planning? Are you setting the standard for what a modern superintendent looks like and building toward it?

If not, the scheduler is just a composite crew of a different kind. You are running the job wrong, and you have built a position to mask it instead of fix it. That is not a criticism of the people in those roles. It is a challenge to the companies that created them.

Edwards Deming said, “A bad system will beat a good person every time.” Build the system. Train the superintendent. Own the plan.

On we go.

Frequently Asked Questions

Are dedicated schedulers always a sign of a problem?

At the project level, yes they almost always indicate that the superintendent is not trained or equipped to own production planning, or that the company is not running a real collaborative planning process. Corporate support roles and pre-qualified trade scheduling are a different conversation.

What should replace the scheduler function if the position is eliminated?

A well-trained superintendent using Takt Planning and Takt Steering and Control, building the production plan collaboratively with trade partners in pre-construction and steering it daily through the meeting system. That is the production planning function it belongs to the project team, not to a separate office role.

Does this mean the superintendent has to do everything?

No. Logistics specialists, field engineers, water spiders, and other support roles that genuinely free the superintendent to lead at the right level are entirely legitimate. The three things a superintendent cannot delegate are safety, quality, and production planning everything else is open for appropriate support structures.

Why do so many companies still have dedicated schedulers?

Because the industry failed to invest in superintendent development for decades and then compensated by creating support positions. It is a structural response to a training gap and the right fix is closing the gap, not maintaining the workaround.

What does a superintendent who does not need a scheduler actually look like?

They know the Takt production system, they build the production plan with their trade partners, they track percent plan complete and root causes daily, and they steer the project through the meeting system in real time. That superintendent exists and developing more of them is the mission.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Through Email Is Defective

Posted on March 30, 2026March 30, 2026 by Danny Jiménez⁩

Read 18 min

Why Email Is Anti-Lean And What to Do Instead

I get messages all the time from builders who are doing everything right. They are ready to implement Lean. They want to respect the people on their project. They are building the systems. And then something slip a detail buried in an email chain, a critical note hidden on page three of message number seventeen and the whole thing unravels. Someone gets blamed. Someone gets defensive. And the project absorbs a problem that was entirely preventable. Not because the people were careless. Because the communication system was defective.

The Pain That Nobody Names

Here is something that happens constantly in construction and almost nobody talks about honestly. A project manager sends an important detail. A superintendent misses it. The PM says, “I sent it to you.” The superintendent says, “I never saw it.” And now two people who should be partners are playing tennis with accountability, trying to get the other one to drop the ball. Meanwhile the trade partner is waiting. The work is delayed. And the detail still has not been clearly communicated to the person who needs to act on it.

That is not a people problem. That is a system problem. And the system is email.

The Failure Is in the Process, Not the Person

When a project engineer or PM says “it is in the email,” what they are actually saying is: I created a communication that requires someone else to hunt through a thread of seventeen messages, piece together scattered information from multiple exchanges, cross-reference what was said against what was decided, and arrive at a clear action step without missing anything. That is not communication. That is delegation of cognitive labor to the recipient and hope that they do not drop any of it.

The people who get blamed when something falls through the cracks are almost never the ones who broke the system. The system was already broken before the first message was sent.

A Story From the Field

I was recently heading to Victoria, British Columbia, for a Foreman Boot Camp. The trip involved flying from Phoenix to Washington, then connecting to Vancouver, then a ferry, then a taxi to the hotel. Multiple legs. Multiple requirements. Immigration checklists. Ferry tickets. Timing dependencies at every step. I made the deliberate choice to put every single step in a Google Doc, in order, and ask someone to review it. We caught two or three mistakes before they became problems. And the entire trip went smoothly.

Now imagine if instead of a clear Google Doc, I had communicated those same requirements across fifteen separate messages, some with attachments, some with relevant details buried mid-paragraph, some referencing decisions from earlier exchanges. The probability of a missed step would have been enormous. And if something went wrong, I would have had no one to blame but the process I chose.

That is exactly what is happening on construction projects every day. The trip is the project. The steps are the details, decisions, RFIs, and requirements. And scattered email is the fifteen-message thread nobody should be counting on.

Why Email Is Structurally Anti-Lean

Lean communication has one core standard: information needed to execute should be clear, concise, and findable in one location. Email violates that standard in multiple ways that compound over time.

The first problem is fragmentation. A project manager I worked with recently made the point that inside Procore, information about a single scope item can exist in twenty-eight different locations the drawings, the specs, the manufacturer’s data, the shop drawings, the RFIs. Procore in that situation is doing what email always does: creating the illusion of a single platform while actually batching information across dozens of disconnected nodes. The worker or foreman trying to execute the work should not have to act as a human search engine just to understand what is expected of them.

The second problem is the queuing delay. When you send an email, you are not communicating. You are placing a package in a queue and hoping it gets picked up, read carefully, and acted on within a reasonable timeframe. In reality, email queues in somebody’s inbox for twenty-four to seventy-two hours before it generates a response if it generates one at all. If you are counting on email for timely decisions or quick turnarounds, you are wildly mistaken. That is not a criticism of the recipient. It is the physics of the system you chose.

The third problem is the tennis dynamic. Construction is a team sport. But email, by its structure, encourages people to play defense with information rather than share it for the benefit of the work. Sending an email becomes a way to document that you told someone rather than a genuine act of ensuring they understood. “I sent it to you” becomes a legal defense instead of a communication. That is not a team culture. That is a batching culture with documentation attached.

Here are the warning signs that email has become your communication system instead of your production system:

Important decisions live in threads that require reconstructing a timeline to understand
People regularly say “I sent that weeks ago” when a problem surfaces
Trade partners are unclear on expectations that were communicated only in writing
Field leaders are finding information across multiple platforms, tools, and message chains

What to Do Instead

The goal is simple: all information relevant to an action goes in one location, clearly formatted, before the action is expected to happen. The platform is secondary to the principle. What matters is that the person who needs to act on the information can find it, read it, and execute without hunting.

Some teams do this well on Microsoft Teams, linking everything relevant to one channel or thread even if they do not love the software. Some teams use Trello cards. Some use Google Docs or shared Google Drive folders with a clear structure. Some use Miro boards where the visual logic of the project mirrors the physical sequence of the work. In the field, sometimes the best version is a printed document brought into a meeting, reviewed together, and left with the crew. The format matters less than the commitment to one location and one clear version.

The key is to stop treating email as the place where real decisions live and start using it only for what it is reasonably good at brief notifications, scheduling confirmations, and short acknowledgments that point back to the single source of truth. Any time you find yourself writing a message that a recipient would need to archive, re-read, cross-reference, or synthesize with earlier messages to fully understand, you have already left the realm of effective communication. Get it out of email. Put it where it belongs.

Connecting to the Mission

At Elevate Construction, the phrase we use for how a project should function is this: see as a group, know as a group, act as a group. Email is structurally incapable of producing that outcome. It creates separate information experiences for every person in a chain, distributes knowledge unevenly, and generates ambiguity at exactly the moments when clarity is most needed. When trade partners do not know the expectations, they cannot execute the expectations. When foremen have to reconstruct decisions from a scattered thread, they waste time that should be spent building. Protecting people from that waste is not a technology preference. It is a respect-for-people decision. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

The workers and foremen who build the work deserve clear, organized information. Building that for them is not extra effort. It is the job.

A Challenge Before Your Next Communication Decision

The next time you are about to send an email to communicate something important, pause and ask one question: could the person who needs to act on this find it, understand it, and execute it without hunting? If the answer is no, the email is not the solution. Find the one location where it belongs, put it there, and confirm the person has it. That extra step is the difference between communication and coverage.

Edwards Deming said, “A bad system will beat a good person every time.” Email is that bad system for construction communication. Replace it, reduce it, and respect the people downstream enough to give them clarity instead of a queue.

On we go.

Frequently Asked Questions

Why is email considered anti-Lean in construction?

Email batches information across scattered messages, creates queuing delays of twenty-four to seventy-two hours, and forces recipients to reconstruct decisions from fragmented threads. Lean communication requires information to be clear, current, and in one location which email structurally cannot deliver.

What are better alternatives to email for project communication?

Tools like Trello, shared Google Docs, Miro boards, or a well-organized Microsoft Teams channel all serve the purpose when used with a one-location discipline. Even a printed document reviewed in a meeting outperforms scattered email chains for clarity and follow-through.

Is this about blaming people who use email?

Not at all. The people relying on email are often doing the best they can inside a system that was never designed for construction communication. The problem is the process, not the person.

How does poor communication affect trade partners specifically?

Trade partners arrive at the work needing clear expectations to execute well. When those expectations are buried in email threads, foremen spend time reconstructing information instead of leading their crews. That delay directly affects production, quality, and schedule.

What is the one-location principle?

It means every piece of information required to execute a task drawings, specs, RFIs, decisions, expectations lives in a single, accessible, clearly structured location before the work begins. It removes hunting, reduces errors, and respects the time of everyone on the project.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

How Does A Company’s Organizational Structure Impact Project Management

Posted on March 30, 2026March 30, 2026 by Danny Jiménez⁩

Read 20 min

How Your Company’s Organizational Structure Affects Project Management

I get WhatsApp voice messages from builders all over the world. Hundreds of people in the group. We share constantly. And one pattern shows up in those messages more than almost anything else. Someone says, “Jason, I am ready. I want to implement this. I. But I keep getting undercut every time I try.

The intent is there. The willingness is there. The knowledge is there. And none of it can move because the organizational structure of the want to do Lean the right way. I have the bathrooms ready. I want to respect the people.” And then the buts start. But my company won’t allow it. But leadership shut it down company is working against them. Understanding that structure is not optional for a Lean leader. It is one of the most important things you can know.

The Pain of Leading Without Support

There is a specific kind of frustration that comes from knowing exactly what needs to happen on a project and being systematically blocked from doing it. The PM who wants to run morning worker huddles but gets told it is not how we do things here. The superintendent who wants to involve trade partners in pre-construction but cannot get approval. The field engineer who has seen what a clean, organized, Lean site produces and is placed on a project where leadership actively discourages it.

This is not a motivation problem. These are talented, committed builders being handed handcuffs and told to perform. And the source of those handcuffs is almost always organizational the structure, the culture, the decision-making chain, and the values of the company they work inside.

The Structure Is the System

Before we name the seven things, I want to say something clearly. When a Lean-minded leader cannot implement what they know, the company’s system is the constraint. Not the leader. Not the trade partners. Not the workers. The system failed them. They did not fail the system.

That framing matters because it changes the diagnosis. The question is never “why can’t this person lead?” The question is “what in the organizational structure is blocking this person from leading well?” And that is exactly the question every builder should be asking before they join a company and every year they stay in one.

Three Companies Done Right and One That Is Not

I have worked for three companies and I want to name them directly, because each one represents a different structural philosophy and all three are legitimate. Hensel Phelps operates with a field and office guide a clear, consistent standard that is applied the same way across every project. That structure produces remarkable consistency. I personally would have struggled there because I am always evolving and trying new things, and that environment would have limited me. But for builders who thrive inside clear systems, it is an excellent home.

DPR Construction gave me the autonomy that made me who I am. Running a project at DPR was a genuine blessing. You had the freedom to implement Lean fully, to build the team the right way, to run the job the way you believed it should be run. Some owners find that inconsistency frustrating. But for leaders who need room to experiment and grow, that autonomy is the gift.

Okland Construction was a great middle ground. Clear minimum standards that defined how a project must be run, plus the autonomy to elevate and improve from there. You knew the floor. And then you could build as high as your leadership allowed.

All three of those are right ways to structure a construction company. The wrong way is when a company smothers its PMs and superintendents, shoots down every respectful Lean initiative, and undercuts field leadership at every turn. I have never seen Hensel Phelps, DPR, or Okland do that. But I have heard of other companies where it is the standard operating procedure. That kind of structure does not just limit performance. It drives good people out.

The Seven Things You Must Understand

The first is functional versus matrix structure. Every company has an org chart. Most companies also have a real hierarchy the actual people who make decisions, the actual influencers who shape culture, the actual gatekeepers of approval. If you are joining a company or trying to drive change inside one, you have to know where the real decisions are made, not just where the chart says they are made.

The second is decision-making speed. You may work for a company with excellent values and genuine support for Lean. But if a decision that should take a week takes a year, your ability to lead is throttled. Fast-moving leaders need fast-moving decision makers. Mismatched speed is its own form of handcuff, even when the intent is good.

The third is clarity of authority. You need to know what authority you have, what requires permission, and where to go to get it. When that clarity is absent, people fill the void with assumption. Some assume they can act. Others assume they cannot. And everyone wastes energy navigating ambiguity that should have been resolved at the organizational level. When people do not know who is making the decisions, they usually know it is not them and that feeling is suffocating for a leader.

The fourth is silos versus integration. Here are the signals that an organization has structural silos working against you:

Finance and accounting operate independently of project operations
Pre-construction is disconnected from field execution
People development sits in its own silo with no connection to project systems
Decisions made in one department create problems that another department absorbs without communication

Integrated companies are harder to navigate in one sense you have to work with more people, lean into healthy conflict, and build consensus. But you can actually affect change. Siloed companies will generate toxicity and fighting regardless of how talented or committed the individuals are.

The fifth is accountability clarity. The best company cultures I have seen are warm-hearted and strict at the same time. They are strict about tactics clean, safe, organized environments, respect for people, taking care of the client. They are warm and human about everything else. What breaks down is when a company has all the right values but no accountability structure to back them up. When leadership will not hold anybody to a standard, the result is milk-toast performance regardless of the intentions. A great culture without accountability is chaos with a nice name.

The sixth is field and office alignment. I genuinely do not love the phrase “field and office” because it implies two separate teams, and that separation is part of the problem. There is one project delivery team. The superintendent should not be undercut by the PM. The PM should not be going rogue around the superintendent. And both of them need a general superintendent, project executive, and cross-functional company leadership that has their back, understands who the real drivers of value are the workers and the foremen and is genuinely bought in to operational excellence. When that alignment is present, the project team can function as one. When it is not, the field and office spend more energy managing each other than building the project.

The seventh is cross-functional buy-in. This is the organizational question that determines whether Lean can actually take root. How bought-in is the company not just leadership in speeches, but in policy, in resource allocation, in how they respond when a superintendent asks to run Lean on a project to efficiency, operational excellence, and respect-for-people systems? A company that talks about Lean but flinches every time it costs something will never build the culture that makes Lean work. And the builders inside that company will spend their careers fighting the system instead of building great projects.

Why This Matters to the People on Every Project

Every one of these seven structural factors has a direct human consequence. When decision-making is slow, trade partners wait. When authority is unclear, foremen get conflicting direction. When silos run deep, supply chains break. When accountability is absent, standards erode and workers end up in unsafe, disorganized environments that nobody fights to fix. These are not abstract organizational concerns. They are the conditions that determine whether the people on that project can win. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

The goal is not to find the perfect company. The goal is to know exactly what structure you are operating inside so you can lead intelligently within it, advocate for what needs to change, and make decisions about where your career belongs.

A Challenge for Every Builder

Before your next project kicks off, ask yourself which of these seven areas is your biggest constraint right now. Not the most annoying. The most consequential. The one that, if it changed, would unlock the most of your leadership. Name it. Then decide whether you are going to work within it, work to change it, or decide this is not the right environment for the leader you are becoming.

Edwards Deming said, “A bad system will beat a good person every time.” Know your system. Respect it where it is sound. Challenge it where it is not. And build inside it with everything you have.

On we go.

Frequently Asked Questions

Why does organizational structure matter so much to a Lean leader?

Because the structure determines what you are actually allowed to do. A committed Lean leader inside a siloed, slow-moving company will spend more energy fighting the organization than building the project. Structure is the constraint most builders underestimate when they take a new role.

Is one company structure better than another for Lean implementation?

Not categorically. What matters is whether the structure gives leaders clarity, decision-making authority, and cross-functional support. Hensel Phelps, DPR, and Okland all operate differently and all produce excellent leaders because each one, in its own way, backs up its people.

What does “warm-hearted but strict” actually look like in practice?

Strict about the non-negotiables clean, safe, organized, respectful of people. Warm and human in how you coach, develop, and work with the people inside those standards. Companies that are strict about everything produce fear. Companies that are warm about everything produce chaos.

How do you know if field and office are truly aligned on a project?

The clearest signal is whether the superintendent and PM are moving in the same direction without undercutting each other. When both feel supported by leadership above them and respected by the other, alignment is real. When either one is going around the other, the structure has failed them both.

What should a builder do if their organizational structure is blocking Lean implementation?

Name the specific constraint is it decision speed, authority clarity, silos, or accountability gaps? Then decide whether to advocate for change, work around the constraint creatively, or evaluate whether the company is the right fit for the leader you are building yourself into.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

IPD Explained: How Lean Teams Lead Differently

Posted on March 30, 2026March 30, 2026 by Danny Jiménez⁩

Read 19 min

IPD Explained: How Lean Teams Do It Differently

There is a word that keeps coming up every time I research great businesses, great teams, and great construction projects. It does not matter whether I am reading W. Edwards Deming, studying how Google works, or digging through the research behind high-performing project delivery. The word is the same every time. Integration. And integrated project delivery IPD is the methodology that takes that word and builds an entire system around it.

The Pain of Building in Silos

Walk into most construction projects and you will see the same structural disease at work. The owner is in one corner. The designers are in another. The general contractor is running a separate meeting. The trades are waiting to be told what to do. Contracts are written to protect individual parties rather than to optimize the whole. When something goes wrong, lawyers get involved before solutions do. And the result is a project built on friction, mistrust, and wasted time.

That is not a people problem. The owners, designers, contractors, and trade partners on those projects are often talented and well-intentioned. But the system they are operating inside was designed to separate them, not integrate them. When the structure pushes people into silos, people in silos is exactly what you get.

The System Built the Silos

Here is what I want builders at every level to understand: the adversarial dynamic on most construction projects is not a personality trait. It is an organizational outcome. Design-bid-build delivery puts parties into contractual positions where their interests diverge. Everybody optimizes for their own scope, their own schedule, their own margin. And when those sub-optimized pieces try to come together in the field, they collide. The schedule slips. The budget bleeds. The team fractures. And everyone points at someone else.

The system failed them. They did not fail the system.

A Story That Made This Real for Me

When I was at DPR Construction, I had the chance to work on IPD-light projects environments that used IPD behaviors even without the full integrated form of agreement. The difference was immediately visible. The kickoff was not a handshake and a slide deck. It was a structured event where the whole team built shared goals together. Communication was transparent and open cost, schedule, decisions, everything. Trade partners were involved in constructability reviews before anyone had swung a hammer, because general contractors, no matter how talented, simply do not know what trades know about how something actually gets built.

Those projects did not feel like the typical industry experience. They felt like a team. And when problems surfaced and they always do people ran toward the problem together instead of scrambling to document who was responsible.

Why Integration Is the Job of the General Contractor

When we were writing the book Elevating Construction General Superintendents, we had to distill the general contractor’s job down to its essential functions. We landed on four. First, create a clean, safe, organized, stable, and standardized environment. Second, create rhythm through the Takt plan and ensure the train of trades is moving through the project together. Third, provide the finances and resources pay trade partners on time, not late, and make sure the material and information supply chains are queuing up to enable the work. And fourth the one that ties all the others together integration. Integrated communication, integrated meeting systems, integrated teaming, integrated participation, everything integrated.

That fourth function is the one most GCs under-deliver on. They run the environment, they manage the schedule, they handle the money. But they do not always do the hard work of integrating the people. And that gap is where projects fall apart.

The Five Components That Make IPD Work

The first is shared risk and reward. This is the structural heart of true IPD. When all parties owner, designer, contractor, and key trades share in both the upside and the downside, the incentive to sub-optimize disappears. Nobody can win by making someone else lose. The Integrated Form of Agreement, or IFOA, formalizes this structure. But even teams without a formal IFOA can adopt shared-risk thinking by making every decision through the lens of what is best for the whole project, not just one party.

The second is transparency primarily in cost, but really everywhere. Transparent cost data, transparent schedules, transparent decisions, transparent means and methods. When everyone can see the same picture, the motivations that drive bad behavior in traditional delivery are simply removed. People stop gaming the system because the system is visible. And when everybody knows the goal, the structure, and the rules, alignment happens naturally.

The third is early trade partner involvement. Here is a hard truth I want builders to sit with: general contractors do not know how to do real constructability reviews without trade input. We can coordinate. We can budget. We can schedule. But the trades are the experts in how their work actually gets built. Bringing them in early during design, not just during construction produces better details, more accurate durations, fewer surprises, and a team that has already built the project once in their heads before anyone touches the field.

Here are the signals that early trade partner involvement is working:

Constructability issues are caught in design, not during installation
Trade durations in the schedule are based on real crew capacity, not guesses
Trade foremen arrive at pre-construction meetings already prepared
Design details reflect how the work is actually built, not just how it looks on paper

The fourth is joint decision-making. This is where a lot of teams struggle because the instinct is to either centralize every decision or die by committee. The answer is a clear distinction between tactical and strategic decisions. Tactical decisions cleanliness, organization, safety, the non-negotiables of how the site operates are not up for debate. They are the core values of the project and they get enforced without committee. Strategic decisions sequencing, phasing, budget allocation, design trade-offs require consensus among the parties who share the risk. You build a coalition. You work through the group. And you move forward together.

The fifth is big room collaboration. Not separate offices. Not siloed meetings. Not teams that communicate by email when they could be working side by side. Co-location, even partial, changes the speed and quality of every decision. When the owner, designer, contractor, and key trades are working in proximity, with shared visual systems and real-time data, problems get solved in minutes instead of weeks. The big room is not just a physical space. It is the physical expression of the commitment to optimizing the whole.

Optimizing the Whole Is the Point

There is a concept I love from the theory of constraints. Imagine a pipe with a bottleneck in the middle. An improvement at the far end of the pipe means nothing as long as the bottleneck remains. The only improvement that matters is the one that addresses the actual constraint. In construction, most teams are making improvements to their own pipe sections while the project bottleneck stays unresolved. IPD fixes this by orienting the entire team toward the same bottleneck, the same constraint, the same goal. We optimize the whole, not the parts.

That shift in orientation is profound. It means a designer changes a detail not because it makes their work easier but because it makes the trade’s installation faster. It means a contractor absorbs a cost in one area because it removes a bigger constraint somewhere else. It means trade partners share information about their capacity because doing so helps the schedule flow. Total participation produces total optimization. And that is what IPD, at its best, is engineered to produce.

Why This Connects to the Mission

The mission at Elevate Construction is to build remarkable people and systems that build the world. IPD is the delivery methodology most aligned with that mission because it is the one that takes the integration of people seriously. It does not just talk about collaboration. It structures the contract, the environment, the meetings, and the relationships around it. When you work in a true IPD environment, you do not just build a better project. You build better builders. People who know how to work as a team, make decisions together, and optimize for something larger than themselves. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Integration is what it is going to take to build great projects. Not better individual performance. Integration.

A Challenge for Every Builder

The next time you feel the friction of a siloed project the owner going one direction, the design team another, the trades waiting and wondering ask yourself what one step toward integration looks like. It might be a co-location session. It might be a transparent cost meeting. It might be inviting a trade partner into a constructability conversation they were never included in before. Start there. Integration compounds.

As W. Edwards Deming said, “A bad system will beat a good person every time.” IPD is the system designed so that good people can finally win together.

On we go.

Frequently Asked Questions

What is the difference between IPD and traditional design-bid-build?

Design-bid-build separates the parties into contractual positions where their interests often conflict, producing adversarial dynamics and sub-optimization. IPD integrates them through shared risk, shared reward, and co-located decision-making so everyone optimizes for the whole project, not just their own scope.

Do you need a formal IFOA to get IPD benefits?

No. Many teams use IPD-light behaviors early trade involvement, transparent cost, co-location, and joint decision-making inside CM at risk or other contract structures. The mindset and the behaviors produce most of the benefit even without the formal agreement.

Why is early trade partner involvement so important?

Because general contractors, no matter how experienced, cannot do real constructability reviews without trade expertise. Trades know how their work actually gets built, and involving them during design eliminates expensive surprises in the field.

What does “optimizing the whole” mean in practice?

It means making every decision based on what is best for the project overall, not for any individual party. A designer improves a detail because it helps the trade, not because it makes their own work easier. The bottleneck gets fixed, not the easy parts downstream from it.

How does IPD connect to Lean and Takt?

IPD and Lean are natural complements. IPD creates the integrated team and the shared goals. Takt Planning and Last Planner give that team the production system to execute with rhythm, flow, and visibility. Together they cover the full lifecycle from pre-construction alignment through field delivery.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

How Long Does It Take To Become A Project Manager?

Posted on March 30, 2026March 30, 2026 by Danny Jiménez⁩

Read 19 min

How Long Does It Take to Become a Construction Project Manager And What Actually Matters

Five to ten years. That is the honest answer to how long it takes to become a construction project manager. But here is what I want you to understand: the timeline is not the interesting part. The interesting part is what happens inside those years. Because I have seen people hit the PM title in four years and struggle badly, and I have seen people take eight years and become genuinely outstanding. The difference was never the calendar. It was what they learned, how they saw their role, and whether they built the five things that actually make a project manager effective.

The Pain That Stalls Most PMs Before They Even Start

I got a WhatsApp message from a superintendent not long ago. He said the project manager on his project was technically sharp great with computers, good with the details. But when the materials hit the site, the PM said, “I got them here. It’s yours to worry about now.” And then walked away.

I was genuinely sad when I heard that. Not because the PM was a bad person. But because he had completely misunderstood his job. He thought his role was to do things. Order materials. Process RFIs. Review submittals. And once he did the thing, his responsibility ended.

That framing produces projects that limp. Materials arrive damaged or staged in the wrong location. Nobody QCed them. Workers are tripping over them. The superintendent is managing consequences instead of building. And the PM wonders why everyone seems frustrated.

The Failure Pattern Is in the Misunderstood Role

The failure pattern for most developing project managers is not laziness or incompetence. It is a fundamental misidentification of what the job is. They believe the role is built around tasks RFIs, submittals, pay applications, supply chains. Those tools are real and they matter. But they are not the job. They are instruments in service of the actual job, which is enabling trade partners to be successful so the project can be successful so the client gets what they paid for.

A project manager who gets that right manages an entire process: buyout, executed contract, pre-mobilization meeting, pre-construction meeting, first in-place inspection, follow-up inspections, final inspections, payments, and supply chain all the way from plan to build to finish. The RFI is not the deliverable. A prepared trade partner with clear expectations, confirmed materials, and a quality plan is the deliverable. That shift in thinking changes everything.

A Story About What Good PM Leadership Looks Like

When I was project superintendent on the Bioscience Research Laboratory with DPR Construction, my project manager was Brian Young. He is a great example of what leadership maturity actually looks like in this role. He was supportive. He also held the line. He spoke up when something needed to be said. He did not put up with nonsense including from me. He walked the field. He helped me own issues rather than leaving me exposed. He was always strategically where he needed to be, and he was always building the team.

Brian never smothered me. He never went around me. But he also never disappeared. He had the rare ability to bring out the best in the people around him while still meeting the goals of the project. That is what leadership maturity looks like in practice. And I have watched people with that kind of maturity get promoted faster and perform better than anyone else in the room.

The Five Things That Actually Determine How Well You Perform

The technical mechanics of the PM role how to write an RFI, how to review a submittal, how to process a subcontractor pay application, how to use project management software you can learn most of that in eighteen months to four years. It is teachable and learnable and plenty of people come out of school and reach PM-level competence within four or five years on those tasks. But if they skip what I am about to describe, it will hurt them, and the project teams depending on them will feel it.

The first is a real understanding of construction operations. Not the version taught in some companies, where you learn to hold retainage, pay trade partners late, or rely on composite cleanup crews. That is not construction operations. That is extraction masquerading as management. I am talking about thoughtful, effective, actually good construction operations how work flows, how trade partners are prepared, how decisions in the office create or destroy capacity in the field. A PM who does not understand operations will be perpetually behind the people they are supposed to be enabling.

The second is communication. The project manager lives at the intersection of the owner, the design team, the superintendent, the trade partners, and the executive team. That intersection only produces good outcomes when the PM can communicate well not just clearly, but strategically. Two books I recommend to every PM developing this skill are How to Win Friends and Influence People by Dale Carnegie and Never Split the Difference by Chris Voss. One teaches you how to build allies and move people toward shared goals. The other teaches you how to negotiate for win-win outcomes rather than win-lose conflicts. Read both. Apply both. They will change how you show up.

The third is financial literacy. Not bookkeeping. Strategic financial thinking. A good PM understands the numbers not just to track them but to shape them to look at projections and play what I call the Monopoly game of construction finances. The goal is a win-win-win: the owner wins, the company wins, and the trade partners win. When a PM only manages the numbers reactively, cost overruns are discovered too late to do anything about them. When a PM manages them strategically, they create margin through preparation, sequencing, and smart relationships.

The fourth is leadership maturity. Here is what it is not: a PM and a superintendent constantly fighting, a PM who manages their entire work life through emails, a PM who is disrespectful to field leadership, or a PM who is emotionally reactive under pressure. Leadership maturity is the ability to work with a diverse group of people different personalities, different experience levels, different priorities while still holding to standards and meeting the goals of the project at the end of the day. Anyone can lose their composure. Anyone can decide they are done with a person or a problem. That is immature and it costs projects dearly. Leadership maturity means you stay in it, you hold the line with dignity, and you keep building the team regardless of the difficulty.

The fifth is risk management. Great PMs see what could go wrong before it does. They think in terms of readiness what does this trade partner need to be ready to execute, and does that thing exist yet? They identify constraints early, mitigate them systematically, and protect the team from surprises that were entirely preventable. Risk management is not a software function. It is a mental habit built over years of watching what happens when preparation is skipped.

Here are the signals that a PM is developing these five things well:

Trade partners leave pre-construction meetings with a clear installation work package
The superintendent and PM meet regularly and trust each other
Problems surface early in meetings rather than exploding in the field
Financial projections are updated proactively, not reactively
The PM walks the site and knows what is actually happening

The Path That Sets You Up for All of It

I never recommend going straight from college into a project engineer role. The fastest path to a great PM career runs through the field first. College, then field surveyor, foreman, or whatever entry point fits your background military, trade work, industry hire then field engineer. The field engineer role teaches you how construction actually gets built. It forces you to respect the people boots on the ground doing the work. And that respect, once built, stays with you for the rest of your career in a way that makes everything else work better. How long that field phase takes varies by person. But skipping it produces PMs who manage paper and miss the point.

Why All of This Connects to Something Bigger

When a project manager truly understands the role enabling people, preparing trades, building partnerships, leading with maturity the project becomes a different experience for everyone on it. Trade partners feel respected instead of managed. Superintendents feel supported instead of abandoned. Owners get what they paid for because the system was designed to deliver it. That is not accidental. That is what a well-developed project manager produces. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. The five to ten years is real. But more than the time, it is what you do with it. Build the five things. Go through the field. Learn from people like Brian Young who show you what leadership maturity actually looks like. The career you want is built one good decision at a time.

On we go.

Frequently Asked Questions

Is five to ten years really how long it takes to become a project manager?

Five to ten years reflects the time needed to develop real construction operations knowledge, communication skill, and leadership maturity not just technical PM tasks. You can process RFIs in eighteen months, but you cannot replace the judgment that comes from years of field-grounded experience.

Why is going through the field so important before becoming a PM?

The field teaches you how construction actually gets built and, more importantly, how to respect the people doing the building. PMs who skip this step tend to manage paper instead of enabling people, and that gap shows up on every project they run.

What is the real job of a project manager?

The job is to enable trade partners to be successful so the project can be successful so the client gets what they paid for. RFIs, submittals, and pay applications are tools in service of that goal not the goal itself.

What does leadership maturity look like for a PM?

It is the ability to work with diverse people, hold to standards, support the superintendent without smothering them, and stay constructive under pressure. It is the opposite of managing by email and avoiding hard conversations.

How does financial literacy differ from just tracking numbers?

Strategic financial literacy means shaping outcomes through proactive projection and relationship management creating win-win-win results for the owner, the company, and the trades. It is playing offense with the numbers, not just recording what already happened.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

What Lean Construction Is (And What It’s Not)

Posted on March 27, 2026March 27, 2026 by Danny Jiménez⁩

Read 17 min

What Lean Construction Is And What It Is Not

I get fired up about this topic. Not in a bad way. In a this-matters-deeply-and-I-want-you-to-get-it-right way. Because Lean has changed how I see every jobsite, every team, and every project I have ever been a part of. And when it gets misrepresented when people use the word Lean to describe something it was never meant to be it sets back the very builders and trades who deserve the benefits most. So let’s clear the air.

What Lean Actually Is

Lean construction, at its core, is the willingness to learn and implement excellent practices for the purpose of benefiting people and humanity. That is the definition. Read it again slowly. It is not about efficiency for its own sake. It is not about squeezing more out of less. It is a commitment, a posture, a way of building that starts with people and ends with people.

Here is how I break it down. Lean is about respecting people, nature, and resources in a fundamental way. It is about stabilizing your project with cleanliness, organization, and safety. It is about creating standards so that work is predictable and repeatable. It is about working in one-piece, one-process, or one-progress flow meaning we do not start anything until we are ready to finish it with full kit. It is about flowing together, trades working shoulder to shoulder collaboratively, nobody going rogue, everybody following the system together and delivering a quality product. And it is about continuous improvement, the daily habit of asking how we can do this better and actually acting on the answer.

At Elevate Construction and LeanTakt, this is not a poster on the wall. It is how we build. Continuous improvement is woven into every training, every project, every system. And when teams commit to it fully, the results are not just better schedules and budgets. They are calmer projects, cleaner sites, fewer surprises, respected trade partners, and builders who are proud of what they built.

The Pain of Getting Lean Wrong

Here is the problem. Too many companies hear the word Lean and immediately think cost reduction. They walk into pre-construction thinking about labor counts. They sit in a Lean training looking for ways to do the same work with fewer people. And then they try to implement Lean from that mindset, and it fails. Every time. Without exception.

The people on the receiving end of that failure are not the executives who misapplied the concept. They are the foremen and workers who were told a better system was coming, who got their hopes up, who maybe even started to believe the project could run differently and then watched it collapse because the intention was never right. The system failed them again. Not because Lean doesn’t work. Because Lean was never truly implemented.

The System Failed Them

I want to say something here directly. When Lean is used as cover for cutting people or reducing staff, that is not a Lean failure. That is a leadership failure dressed up in Lean vocabulary. The people caught in that crossfire were not let down by a method. They were let down by leaders who grabbed a tool without ever understanding the philosophy behind it. The system failed them. They did not fail the system.

The companies that actually win with Lean are the ones that say something like this: we are going to do what is best for our people and our clients first, and as a natural result, we will do what is best for the business. That is the order. People and clients first. Business results follow. When you flip that sequence and lead with profits, Lean will cost you more than it ever saves you.

A Story From the Field

On one of my best projects, we implemented Lean to its fullest extent. We had morning worker huddles every single day. We taught the eight wastes. We gave out mission coins to workers who could recite them. We modeled improvements to foremen first and then to the whole crew. We gamified the recording of improvement videos and ended up with over 160 documented improvements still on YouTube today.

That did not happen because the company wanted to reduce headcount. It happened because the team believed in the people doing the work. Workers are brilliant. Given the right environment, the right clarity, and the right respect, they will improve anything you point them at. When you walk a clean, safe, organized site with a crew that is engaged and improving daily, you are seeing what Lean actually looks like. Not a spreadsheet. A culture.

What Lean Is Not

Let’s name it plainly because the industry is full of the misconceptions and the people paying the price are the ones doing the building.

Lean is not cutting people. It is not removing jobs. It is not replacing humans with software or eliminating the roles that field teams need. Anyone using Lean as a justification for workforce reduction has fundamentally misunderstood or deliberately misrepresented what Lean is. We do not have a labor shortage in this industry. We have a training problem. We have a respect-for-people problem. We have an unwillingness to invest in developing the people who are standing right in front of us waiting to be taught.

Lean is not bureaucracy. It is not added work. When Lean is implemented correctly, it reduces the cognitive load on every person on the project. It creates standards so people do not have to guess. It creates visual systems so people can see what is happening without having to be told. It removes the friction that makes the work harder, slower, and more frustrating than it needs to be.

Here are the things Lean is not, stated directly:

A quick-fix tool or a single software solution
A single method applied in isolation without a systems mindset
Classical management relabeled with Lean terminology to sell work
Rush, push, and panic dressed up in better vocabulary
Something compatible with CPM-only scheduling or throwaway culture

Lean is also not something you implement for the wrong reason and expect to survive. If the motivation behind your Lean effort is profit improvement or headcount reduction, walk away from it. Do not give it a bad name. The builders and trades who genuinely need what Lean offers deserve leaders who come to it honestly.

Why It Matters to Every Builder

Here is what is at stake. The construction industry has a massive opportunity to become what it was always capable of being: a profession that attracts talented people, develops them well, treats them with dignity, and produces remarkable work. That future is available. It is not theoretical. It is happening on projects right now where Lean is being implemented the right way, with the right intention, for the right reasons.

When Lean works, projects are calmer. Foremen are not firefighting every morning. Workers know what is expected and have what they need to deliver it. Families are protected because the people building the work are protected. That is not a side effect of Lean. That is the point of it. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. The proof test for Lean is simple: are your projects calmer? Is the site clean? Are the trades respected? Are outcomes predictable without heroics? If yes, you are building toward what Lean is meant to produce.

A Challenge for Every Builder

Before your next project kicks off, ask yourself what your real motivation is for implementing Lean. Not the answer you would give in a meeting. The honest one. Is it to bless the lives of the people on your project? Is it to create an environment where workers can win? Is it to protect families by protecting flow? If the answer is yes, you are ready. Lean will reward that commitment with results that no shortcut-seeking approach ever produces. As W. Edwards Deming said, “A bad system will beat a good person every time.” Lean is how you fix the system. Not the people. Never the people.

On we go.

Frequently Asked Questions

What is the simplest definition of Lean construction?

Lean construction is the willingness to learn and implement excellent practices for the purpose of benefiting people and humanity. It is built on respect for people, stability, one-piece flow, visual systems, and continuous improvement.

Why does Lean fail when companies use it to cut costs or reduce staff?

Because the foundational philosophy of Lean is respect for people. When the motivation is cost reduction or headcount reduction, that philosophy is absent from the start, and without it, the tools and methods have no foundation to stand on.

Is there really a labor shortage in construction?

Not in the way most people frame it. We have people. What we have is a training problem and a respect-for-people problem. When workers are developed, valued, and given a system that supports them, retention and performance both improve significantly.

How do I know if Lean is actually working on my project?

The proof test is practical: calmer projects, cleaner sites, fewer surprises, respected trade partners, and predictable outcomes without heroics. If your site is cleaner, your foremen are more prepared, and your crews know the plan, Lean is taking hold.

Can Lean work with CPM scheduling?

CPM as a standalone scheduling system is fundamentally incompatible with Lean because it does not show flow, trade sequencing, or zone-by-zone capacity. Lean-based scheduling systems like Takt and Last Planner are designed to make the plan visible, executable, and respectful of the people doing the work.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Advanced Logistics Queuing

Posted on March 27, 2026March 27, 2026 by Danny Jiménez⁩

Read 20 min

Why Logistics Kitting Is the Most Underused Productivity System in Construction

Walk onto most construction projects and within five minutes you’ll see it. Cardboard scattered across hallways. Materials piled near the stairwell that nobody ordered moved. A journeyman wandering two floors looking for a fitting that arrived three days ago but nobody knows where it went. The job is moving, but it’s grinding. And the crew doing the actual installing is burning time and energy on work that should have been solved before they ever picked up a tool.

That’s not a people problem. That’s a logistics problem. And it’s costing projects more than most teams realize.

What Most Projects Call Logistics

Here’s the honest picture on most job sites. A truck shows up. Someone calls the foreman. A couple of laborers get pulled off their work to help unload. The materials land in the nearest open space. The packaging stays on because no one has time to deal with it. The pallet gets broken down by whoever needs a piece first. And by the end of the day, what arrived as a complete delivery has been scattered across three floors, half of it still in cardboard, half of it missing from the count because nobody verified the delivery in the first place.

That pattern repeats every delivery day, on every project, until the site is a maze of material piles and packaging waste. Crews adapt by spending twenty minutes at the start of each task finding what they need. Leaders adapt by calling it normal. And the schedule absorbs the invisible hours as if they simply don’t exist.

They do exist. They show up as overtime, rework, and frustrated trades who feel like the project is working against them instead of for them. The system failed them. They didn’t fail the system.

A Different Way to See the Problem

Early in my career, I remember standing on a large federal project watching a crew stop installing mid-morning because the materials they needed for the next run were somewhere in the building but nobody could say exactly where. The foreman started walking. Twenty minutes later he came back with the wrong size. That’s a full-time tradesman fully loaded cost on the payrol burning half an hour on a logistics problem that a well-designed system could have solved the day before.

That moment crystallized something for me. The material delivery problem in construction is not a purchasing problem or a coordination problem in the traditional sense. It’s a system design problem. We have never intentionally designed how materials move from the truck to the hands of the worker. We just let it happen and then manage the chaos. That has to change.

What Advanced Logistics Queuing Actually Is

The concept is called advanced logistics queuing, and it treats the movement of materials from the delivery truck to the zone of install as a deliberate production system not an afterthought. The image at the top of this post maps it out clearly. Every element has a role and a location. Nothing is random.

It starts at the gate. Delivery trucks enter the project site and route directly past the project management trailer so that field engineers can perform materials inspections before anything moves. This is not a bureaucratic step. It’s a quality gate. Verifying materials at the point of entry checking counts, checking specs, identifying damage takes fifteen minutes and prevents three days of downstream problems. One project I worked on routed deliveries so they queued near the deck of the trailer, making it seamless for the office team to inspect before anything touched the yard. That one design decision eliminated weeks of RFI delays that used to come from wrong materials reaching the zone.

From there, materials move into the unpacking and kitting logistics area. This is where the real work happens outside the building. A yard forklift unloads the truck onto unpacking stations where the team removes all packaging, cardboard, and shipping materials. Debris removal dumpsters are staged in the yard for immediate disposal, compacting, and recycling. Nothing goes into the building wrapped in cardboard. Nothing carries packaging waste onto a finished floor. This is “nothing hits the floor” thinking applied to logistics the work area stays clean, and materials arrive in the condition they’ll be used, not the condition they were shipped in.

Here is where most projects stop and where great projects are just getting started.

Watch for these signals that logistics has not been designed on your project:

Crews are breaking down pallets in hallways and stairwells
Packaging and cardboard waste is accumulating inside the building
Foremen are making unscheduled trips to staging areas mid-task
Materials are staged by delivery date rather than by zone and crew need
Workers are searching for materials that are somewhere on site but unlocated

Kitting: Putting the Right Materials in the Right Place Before Work Starts

After unpacking, materials are sorted and loaded onto kitting pallets. Each pallet is built for a specific zone. Zone 1 gets exactly what Zone 1 needs for the Takt window. Zone 2 gets exactly what Zone 2 needs. Nothing extra goes into the zone. Nothing gets sent early just because it arrived. The pallet is built the way a kit gets built completely, intentionally, in advance.

This is Point-of-Use Storage and Kitting in practice. Jason Schroeder teaches this as a core Lean principle: eliminate walking, searching, and re-handling by delivering complete work packages to the place of install. When kitting works, the crew doesn’t become the supply chain. The supply chain has already done its job before the crew touches a tool.

Once the kitting pallets are staged, telehandlers deliver them directly to the work area. Visual indicators on the pallets or the zone board communicate readiness, so trades know exactly what has arrived and where it sits before they walk to the zone. There is no guessing, no hunting, no forty-five-minute material chase to start the morning.

The Water Spider Role

The people who operate this logistics system are called Water Spiders. This is a formal role, not an informal assignment. Water Spiders are logistics specialists whose entire job is to feed crews what they need, just in time, at the place of work. They shake out materials, manage the kitting area, coordinate delivery sequencing, and keep the zones supplied so the trade workers can focus entirely on installing.

The principle behind the Water Spider is simple and powerful. Value-adding workers should be adding value. Installers should be installing. When an electrician, pipefitter, or carpenter spends a meaningful portion of the day doing logistics work moving materials, breaking down deliveries, searching for parts the system is robbing the project of its most expensive resource. The Water Spider absorbs that burden and returns it to where it belongs: a specialized logistics role that costs far less than the value it protects.

This is how Lean projects eliminate material chaos and create real installation flow. The procurement feeds production. The supply chain is zoned. Just-in-time means the crew has exactly what they need at the place of work when they need it. When logistics flows, production flows. When logistics breaks down, everything breaks down not because the trades failed, but because the system failed to feed them.

Why This Connects to Dignity and Flow

There is a human dimension to all of this that gets lost in the logistics conversation. When a skilled tradesperson spends hours every day searching for materials, waiting for deliveries, or working around packaging waste, that is not just inefficiency. It is disrespect. It says the system doesn’t value their time. It says their craft matters less than the chaos that surrounds them. It burns people out quietly, day by day, until they either check out or leave the trade entirely.

Protecting logistics is protecting people. When the system delivers exactly what the zone needs, when the zone needs it, crews can perform at the level they were trained for. They can take pride in the installation. They can finish the zone completely before moving to the next one. They can go home at a reasonable hour because the day wasn’t eaten by supply chain problems. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. That work starts with designing the system right from the gate to the zone.

Build the System That Feeds Your Crews

Here is the challenge I want to leave you with. Look at your next project during preconstruction and ask one question: have we designed how materials will move from the delivery truck to the hands of the installer? Not “where is the laydown yard?” That’s a location decision. The design question is: how does a material get inspected, unpacked, kitted by zone, and delivered to the place of work without a tradesperson ever having to leave the zone to find it?

If you can answer that question clearly before the project mobilizes, your crews will feel the difference on day one. LeanTakt and Elevate Construction have seen what happens when logistics is treated as a production system rather than an afterthought. The zones stay clean. The crews stay in flow. The schedule holds. Taiichi Ohno, the father of the Toyota Production System, said it best: “All we are doing is looking at the timeline from the moment the customer gives us an order to the point when we collect the cash. And we are reducing that timeline by removing the non-value-added wastes.” In construction, logistics waste is one of the biggest wastes we have. And it’s one of the most fixable.

On we go.

Frequently Asked Questions

What is advanced logistics queuing in construction?

Advanced logistics queuing is a deliberate system for moving materials from the delivery truck through inspection, unpacking, kitting, and zone delivery without bringing packaging waste or unorganized material into the building. It treats material flow as a designed production process, not a random site activity.

What is kitting and why does it matter?

Kitting is the process of sorting and staging materials onto zone-specific pallets before they enter the building. Each zone receives exactly what it needs for its Takt window. Kitting eliminates searching, re-handling, and crew downtime caused by missing or misplaced materials at the point of install.

What is a Water Spider in Lean construction?

A Water Spider is a dedicated logistics support role whose job is to supply crews with what they need, just in time, at the place of work. The role exists so that value-adding trade workers stay installing rather than doing logistics tasks. It’s a structural advantage that protects production pace and crew focus.

How does logistics kitting support the Takt Production System?

Takt requires trades to move through zones on a steady rhythm. If materials aren’t ready in the zone when the trade arrives, the rhythm breaks. Kitting by zone ensures the supply chain matches the Takt plan, so each zone is fed in the right quantity at the right time and the train of trades stays moving.

Where do material inspections happen in this system?

Inspections happen at the delivery entry point, before materials reach the unpacking area. Routing trucks past the project management trailer gives field engineers the opportunity to verify counts, check specifications, and identify damage before anything moves deeper into the site preventing downstream quality and schedule problems.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

The Crew Preparation Huddle

Posted on March 27, 2026March 27, 2026 by Danny Jiménez⁩

Read 20 min

What the Crew Preparation Huddle Actually Does And Why It Changes Everything

Here’s the deal: all that planning you did the pull plan, the look-ahead, the weekly work plan, the preconstruction meeting none of it matters if the person actually doing the work cannot see it. That’s the hard truth. And most job sites are built in a way that guarantees the worker never gets there.

Walk any large project and ask a journeyman what the plan is for today. Not what the foreman mentioned in the parking lot the actual plan, the sequence, the quality standard, the coordination handoff with the trade coming behind. Most of the time, the answer is a shrug. Not because the worker doesn’t care. Because the system was never designed to tell him.

The plan lives in someone’s laptop. The schedule is a 76-page PDF that no one in the field can read. The quality standard is in a binder in the trailer. The zone map is on a screen three floors above the work. The information exists. It’s just completely inaccessible to the person who needs it most. And that single failure cascades into rework, stacking trades, safety pressure, and exhausted crews pushing to the finish line every single week.

The Pattern That Created This Problem

Construction has been designed, for decades, as a top-down information system. Leadership creates the plan. Management communicates the plan. Workers execute the plan. And somewhere in that chain, the plan gets filtered, simplified, and eventually reduced to “just start over there and work your way down.”

The people closest to the work have the least access to the information about the work. And then we wonder why quality fails. Why coordination breaks down. Why the same problems repeat zone after zone, floor after floor. The system produced those outcomes, not the workers. A bad system will beat a good person every time. The workers showed up ready. The system wasn’t ready for them.

The System Failed Them

The workers on your projects are skilled professionals electricians, pipefitters, carpenters, ironworkers. People who have spent years mastering their craft. They show up every day ready to produce. The problem is the system keeps them in the dark. It filters, fragments, and delays the information they need, then holds them accountable for outcomes the system made impossible. The system failed them. They didn’t fail the system.

Early in my career, I was a field engineer at a project at Whole Foods world headquarters. Two rod-busting crews, same size, same experience, same tools and materials. One was always ahead. The other was always behind. I asked the foreman of the crew that was consistently ahead what was going on. He said, “Jason, look at that other foreman. What’s he doing?” The other foreman was tying rebar head down, working right alongside his crew. The foreman next to me said, “That’s the problem. He’s working his time bar. When he hits a roadblock, his crew hits a roadblock. I bring materials and information to my crew all day long. I get out ahead of them.” That stuck with me for my entire career. The foreman’s job is not to be the hardest worker in the crew. It’s to be the best preparer. And preparation only works when the information is right there visible, accessible, in the zone, before the work starts.

Why This Matters Beyond Productivity

When workers can’t see the plan, they guess. Guessing in construction leads to rework. Rework leads to schedule compression. Schedule compression leads to stacking trades. Stacking trades leads to safety incidents and exhausted crews. Every one of those outcomes has a human cost. Schedules compress and families lose evenings. Trades stack and workers cut corners under pressure.

This is not just a productivity issue. It’s a respect issue. A family issue. A dignity issue. If we are serious about protecting workers and protecting the families that depend on those workers coming home whole then getting the right information into the field, every single day, is the whole game. Flow over busyness. Clarity over chaos. The plan has to reach the crew.

What the Crew Preparation Huddle Is and How It Works

The Crew Preparation Huddle is a short, structured daily meeting where the crew gathers in the zone, around a visual crew board and prepares for the work together. Not a safety toolbox talk in a parking lot. Not a general announcement with no connection to the crew’s specific scope. An actual, practical, plan-the-day session that involves the people doing the work, built around information they can see and act on immediately.

The crew board is the anchor of the entire system. It moves with the crew. On the front sits the look-ahead plan, the weekly work plan, production visuals, and zone maps that crews can mark up with magnets or dry-erase markers. This is not information buried in a schedule it’s in the zone, readable by the workers who are about to do the work. On the back sit Installation Work Packages, crew prep meeting guides, feature-of-work expectations, and visual quality standards for how the work should be done. The quality checklist built in the preconstruction meeting three weeks ago? Right there. The visual standard for a proper installation? On the board that travels with the crew.

Watch for these signals that the Crew Preparation Huddle is missing or broken on your project:

Workers are unclear on today’s scope and sequence when the day starts
Quality failures are discovered after the work is complete, not before it begins
The same coordination breakdowns repeat week after week in different zones
Foremen are working alongside crews instead of planning ahead of them
Lean habits like 5S and waste identification feel like GC programs, not crew practices

The huddle agenda is deliberate from start to finish: shout-outs, safety training, a review of the last day or zone, a reflection and improvement session, day planning, a Lean training topic, stretch and flex, a walk of the work area, filling out the pre-task plan, and a 5S check with a look for the eight wastes. Each step serves a purpose. The review of yesterday builds a culture of continuous improvement. The Lean training topic even two minutes builds a crew that understands the system they’re working inside. The walk of the work area creates shared situational awareness before a single tool is picked up. In a Takt production system, this daily crew-level visibility is what keeps zones flowing on rhythm and handoffs clean.

What Total Participation Actually Looks Like

Jason Schroeder teaches that visual systems exist for one reason: total participation. Visual management is a core Lean principle a work environment that is self-explaining and self-improving because the right information is visible to everyone who needs it. The Crew Preparation Huddle is that principle made operational at the crew level. The board doesn’t just display information. It creates a daily ritual where the crew engages with the plan, improves the plan, and owns the plan.

Total participation in practice means leaders come to the board instead of workers going to the trailer. Problems get raised by the crew before they become roadblocks. Zones finish completely because handoff expectations are visible and understood by everyone. The plan gets better every day because the people doing the work are the ones improving it. Lean is impossible without standard work at the crew level and standard work is impossible without visibility. If workers cannot see the plan, reflect on it, and improve it, there is no total participation. There is only managed execution from a distance. As Jason teaches, everything visual so that we have total participation that’s not a nice-to-have. It is one of the six foundational pillars of Lean in construction.

Dignity, Respect, and the Reason All of This Matters

The Crew Preparation Huddle is ultimately about respect respect for the worker’s skill, judgment, and intelligence. Respect for the crew’s ability to improve a process when given the right tools and information. Respect for the families who depend on stable, predictable work.

When we design systems that bring the plan to the worker visually, accessibly, every morning we are not just improving production metrics. We are saying to every person on that crew: you deserve to know what we’re building today, and your opinion on how to build it better matters. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. That mission is simple: we’re building people who build things.

A Challenge for Builders

Here’s what I want you to do next week. Walk up to a journeyman on your project and ask: “What are you building today, and how does it connect to what the next trade needs from you?” If the answer is confident and clear, your system is working. If the answer is a shrug, you know exactly what to fix. Run the Crew Preparation Huddle consistently. Bring leaders to the board. Train the crew every day even for two minutes. Reflect, improve, and plan again tomorrow. Do that for thirty days and watch what happens to your project, your quality numbers, and the energy of your crews. W. Edwards Deming said it plainly: “A bad system will beat a good person every time.” The Crew Preparation Huddle is how you fix the system one crew, one zone, one day at a time.

On we go.

Frequently Asked Questions

What is the Crew Preparation Huddle, and how is it different from a safety meeting?

The Crew Preparation Huddle is a structured daily meeting where a crew gathers in their work zone to review yesterday, improve the process, plan the day, cover safety, walk the area, and look for waste. It is specific to that crew’s work package and zone not a general announcement. The purpose is preparation, not compliance.

What is on the crew board, and why does it move with the crew?

The front holds the look-ahead, weekly work plan, production visuals, and markable zone maps. The back holds Installation Work Packages, meeting guides, and visual quality standards. The board moves with the crew because the plan needs to be where the work is not in a trailer three floors away.

How does the Crew Preparation Huddle support Lean construction?

Lean requires visual systems for total participation, and the Crew Preparation Huddle makes that real at the crew level. Lean is impossible without standard work and visibility at the crew level. If workers cannot see, reflect on, and improve the plan, total participation doesn’t exist.

What role does the foreman play during and after the huddle?

The foreman facilitates the huddle, then spends the rest of the day planning and preparing work ahead of the crew not working alongside them. A foreman who gets ahead of the crew ensures they never stop. The huddle sets the crew up for a full, uninterrupted day of production.

What are the 8 wastes and why do crews look for them daily?

The 8 wastes in Lean construction are defects, overproduction, waiting, non-utilized talent, transportation, inventory, motion, and extra processing. Looking for them daily builds the habit of continuous improvement at the field level, turning workers into active problem-solvers not passive executors.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Respect for People: The Foundation That Makes Lean Construction Work

Posted on March 27, 2026March 27, 2026 by Danny Jiménez⁩

Read 16 min

Respect for People: The Foundation That Makes Lean Construction Work

Most construction companies say they value people. Walk the average jobsite for one day and you will see the truth. Not because the people are bad. Not because the leaders do not care. But because the system they inherited was designed around a different assumption entirely that people are costs to control, not capacities to develop. And until that assumption changes, every Lean tool you implement is building on sand.

The Pain That Lives on Every Jobsite

Here is the pattern that plays out on projects running under the old command-and-control mindset. Labor gets tracked obsessively as a cost rather than as a capacity. Workers get measured instead of the waste in the system getting measured. People are caught failing rather than being set up to succeed. Leadership shows up through pressure, criticism, and stress. And the results are predictable. Turnover is high. Quality suffers. Schedules slip. People disengage. The team stops bringing problems to the surface because the surface is not safe.

The painful part is that this is not a malicious system. Most of the leaders perpetuating it were trained inside it. They were told that tight control and high pressure are what drive results. Nobody ever stopped to ask what the workers were experiencing on the receiving end of that philosophy, or what it was doing to the quality of their thinking, their commitment, and their willingness to give the project their best.

The Failure Is in the System, Not the People

When turnover is high, the instinct is to ask what is wrong with the people leaving. When quality suffers, the instinct is to ask who made the mistake. When schedules slip, the instinct is to push harder. Every one of those instincts is pointing in the wrong direction. The correct question is always: what in the system made this outcome inevitable? The workers showed up to an environment built around catching them failing instead of helping them succeed. The foremen operated in a culture that punished problems instead of surfacing and solving them. The system failed them. They did not fail the system.

A Story That Changed How I See Leadership

I have been on jobsites where the morning worker huddle was the most respected fifteen minutes of the day. Where workers knew what was happening, knew the safety focus, knew the plan, and knew that if they had a problem, raising it would result in action not blame. On those projects, something remarkable happens. Workers start improving things without being asked. Foremen start surfacing roadblocks before they become crises. The team begins to function as one social group instead of a collection of separate subcultures waiting for the shift to end.

I have also been on jobsites where none of that was true. Where workers felt expendable, where feedback loops ran in one direction only, and where the only leading indicator anyone measured was labor cost per hour. On those sites, you could feel the tension from the parking lot. The system was telling people every single day that they did not matter, and those people responded exactly the way you would expect anyone to respond to that message.

The difference between those two experiences is not the workers. It is not even the schedule. It is whether respect for people is structural on that project, embedded in the environment, the meetings, the coaching, and the expectations or whether it is a laminated value statement on the trailer wall that nobody takes seriously.

What the Lean Mindset Actually Looks Like

The shift from command-and-control to Lean leadership is not about being softer or lowering expectations. It is about understanding what actually produces results. The Lean mindset develops capability instead of demanding output. It treats accountability as an act of care setting clear expectations, following through consistently, and doing it with dignity rather than humiliation. It guides instead of corrects, meaning the goal is to improve the process, not to shame the person. And critically, it fixes systems rather than blaming people, because in a healthy Lean environment, when something goes wrong, the first question is always what in the system allowed that to happen.

Here is what changes when this mindset takes hold on a project:

Trust between trades and leadership rises measurably
Stress levels drop because people are not hiding problems
Flow improves because roadblocks surface early when they can still be solved
Quality rises because workers bring their best thinking instead of just their hands

These are not soft outcomes. They are production outcomes. They show up in the schedule health, the punch list count, the safety record, and the morale of the team as they carry it across the finish line. Respect for people is not a values statement. It is a production strategy.

Why Tools Fail Without This Foundation

Takt Planning, Last Planner, and the Kanban Method are powerful systems. I believe in them deeply and have seen them transform projects. But here is something I want every builder reading this to understand clearly: those tools only work when the people within them feel respected. A Takt plan on a project where workers do not trust leadership becomes a schedule that trades quietly ignore. A Last Planner pull session on a project where foremen are afraid to surface constraints becomes a room full of optimistic commitments that nobody intends to keep. The tool is only as strong as the cultural foundation it sits on.

Lean tools require honest input, real commitment, and the willingness of every person on the project to surface what is actually happening in the field. None of that is possible in a command-and-control environment. You will not get people’s best thinking when they do not feel safe giving it. And without their thinking, you do not have continuous improvement. You have compliance and compliance produces mediocrity, not excellence.

Connecting to the Mission

At Elevate Construction, the phrase we come back to is this: we build remarkable people who build remarkable things. That is not a slogan about construction. It is a belief about the sequence. You build the person first. The person builds the project. When people are developed, respected, and given systems that support them, quality and flow are the natural consequence. Families are protected because the workers building the project are protected. Schedules hold because the teams running them are stable. Safety improves because people feel safe enough to stop and say something when something is wrong.

This is what the image at the top of this post is really saying. Clean environments, shoulder-to-shoulder coaching, systems designed for human success, an empowered and smiling workforce those are not perks. They are the foundation that everything else stands on. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

A Challenge Before Your Next Project Meeting

Walk your project today and ask yourself the honest question. Not the version you would say in a leadership meeting. The real one: do the people on this site feel respected? Not just employed. Not just managed. Respected. Do they have clean facilities? Do they know the plan? Do they feel safe raising a problem? Does leadership show up shoulder to shoulder, or does it show up to inspect and correct?

When we put people before the product or the profit, the product and profit take care of themselves. That is not idealism. That is the most practical truth in construction. Build the foundation right, and everything you stack on top of it will hold.

On we go.

Frequently Asked Questions

What does “respect for people” actually mean on a construction site?

It means creating an environment where workers have clean facilities, clear plans, and a leadership team that develops capability rather than just demanding output. Respect is structural it shows up in how the site is run every single day.

How is accountability compatible with a respect-for-people culture?

Accountability in a Lean culture is an act of care, not punishment. It means setting clear expectations and addressing performance with dignity, because treating people as capable adults who deserve clarity is the most respectful thing a leader can do.

Why do Lean tools fail when the culture is command-and-control?

Because tools like Takt Planning and Last Planner depend on honest input from the field. When people do not feel safe surfacing problems, the tools become theater instead of production control.

What is the difference between guiding and correcting?

Guiding focuses on improving the process so the same mistake does not repeat. Correcting focuses on the individual who made it. The first produces learning and loyalty. The second produces defensiveness.

How do you know if respect for people is actually embedded in your project culture?

Watch the leading indicators: do foremen surface problems proactively, is the site clean, and does the team move together as one group? When those things are true, respect is structural not just a value on a poster.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Subscribe Now !

Sign Up & Start Learning

The Foundation of Construction Excellence

© 2026 elevate construction ist LLC All Rights Reserved. |

SUBSCRIBE NOW !

Subscribe to our newsletters and stay updated!

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

agenda

Day 1

Agenda

Outcomes

Day 2

Agenda

Outcomes

Day 3

Agenda

Outcomes

Day 4

Agenda

Outcomes

Day 5

Agenda

Outcomes