Stop Sending Your Best People to Fix Projects

Posted on August 25, 2026August 25, 2026 by va.jason.almas@gmail.com

Read 17 min

Stop Sending Your Best People to Fix Problem Projects

Here’s the deal. There are companies that routinely send their absolute top performers to go rescue broken projects, and I understand the instinct completely. It also does real, lasting damage that most leaders never fully account for when they make that call.

I have talked about pieces of this before, but I want to walk through the entire picture this time, because the cost of this habit runs much deeper than the frustration of the person doing the fixing.

What Sending in the Fixer Actually Costs

Start with the obvious part. It demoralizes the existing team, and it wastes the time of a genuinely top tier professional on damage control instead of the work they are actually best at. Even after the fix succeeds, it still damages the company’s reputation, because the fact that a rescue was needed in the first place is itself the failure, regardless of how well the recovery goes.

There is a subtler cost too. Once an organization knows a top fixer is always available, it develops a bad habit. Bad projects get quietly tolerated, because everyone knows somebody will eventually swoop in and save it. That is not a safety net. It is a mechanism that masks waste and lets the actual root causes keep repeating, project after project.

The People Who Are Genuinely Great Never Prefer This

Here is something worth being precise about. You will never find a genuinely proficient project director, project executive, or senior superintendent who treats fixing broken projects as a preference over preventing them in the first place. If someone actually enjoys the fixer role more than they enjoy running a stable, well planned project that never needs rescuing, they are not as good as their reputation suggests.

That distinction matters, because the person constantly being sent in to fix things is usually frustrated by it, not energized by it, if they are genuinely as skilled as the organization believes. Being pulled off the work they are best at, over and over, to spend brutal hours getting a broken project back on track, is not a compliment to their talent. It is a sign the organization has built its entire risk management strategy around a small number of exceptional individuals instead of around the systems that would prevent the crisis from happening at all.

What the Existing Team Loses

Here is the part that gets missed most often. Being present on a genuinely well run project, watching it actually work the way it is supposed to, is one of the most valuable experiences in a person’s entire career. It teaches, by direct example, what good actually looks like.

Send in an outside fixer every time a project goes sideways, and the existing team never gets that experience. What they learn instead is a form of learned helplessness. Somebody else will always come save the day, so their own judgment, their own ownership, and their own accountability never get the chance to develop under real pressure. That is the opposite of what any healthy training and development strategy should be producing.

Watch for these signs your organization has built a fixer dependency instead of real prevention:

The same handful of top performers repeatedly pulled off their own projects to rescue others
Project teams that visibly relax their own standards once they know a fixer is available if things go wrong
No meaningful change to training, systems, or pre-construction process after a project required rescue

Why This Hurts the Whole Industry, Not Just One Project

The damage does not stop with the internal team. It extends to every trade partner and worker on that project site, and it sets a bad example that ripples outward into the broader industry. A construction company that constantly finds itself needing to send in a fixer does not have a properly functioning operation. It has a broken, reactive business model with a real disrespect for the people working inside it, and that is a hard thing to say plainly, but it is accurate.

What Should Happen Instead

Here is the alternative I actually recommend. If a project goes bad, the owner of the company goes to fix it personally. Top performers stay exactly where they are, on the projects that are already winning.

That single change produces several real benefits at once. Keeping your best people on your best projects reinforces good habits on those teams consistently, project after project, essentially embedding the right way of doing things directly into the culture of your strongest work. It protects the security and profit of the jobs that are already succeeding, instead of pulling attention away from them. It lets the pace at which good professionals get trained and scaled outrun the pace of reactive crisis management, so genuine capability grows faster than the fires that need putting out. And when the owner personally absorbs the pain of fixing a broken project, that owner becomes genuinely motivated to invest in training, in the right systems, and in a real pre-construction process, since most project failures trace directly back to those three gaps.

Do Not Make Someone Else Pay for Your Own Mistakes

If a project failed because the company did not train its team properly, did not install the right systems, or did not run a genuine pre-construction process, that failure belongs to leadership, not to the people executing the work. Sending a top performer to absorb the consequences of a leadership gap, while leaving the actual root cause unaddressed, means someone else keeps paying for a mistake that was never theirs to begin with. That does not make sense, and it should not be treated as normal.

Keep the overall organization stable and let leadership personally handle the occasional one-off problem, and something important happens. The motivation to actually prevent the next one increases dramatically, because the person absorbing the pain is the same person with the authority to fix the underlying cause.

Why This Should Feel Like Basic Project Management, Not a Radical Idea

I get pushback sometimes for saying things like this, as if the expectation itself is unreasonable. It should not be. The fact that preventing problems, instead of routinely rescuing them, is not treated as basic, foundational project management should genuinely concern our industry. It says something uncomfortable about how we train people and how we think about the actual job.

Recovering a broken project is not a win. There is nothing to celebrate about it, because by the time a rescue is happening, the trades and the people on that project have already lost time, trust, and stability that never should have been at risk in the first place.

Building an Organization That Prevents Instead of Rescues

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your organization build the training, systems, and pre-construction process that actually prevent projects from needing rescue in the first place, rather than relying on a small group of exceptional people to absorb the consequences of gaps leadership never fixed.

So here is the challenge. Look at your own organization’s history and ask honestly how many times a top performer has been pulled off their own work to rescue someone else’s. If that number is higher than zero, trace each instance back to its actual root cause, training, systems, or pre-construction, and fix that cause directly instead of preparing for the next rescue.

Jason Schroeder said it plainly: “Recovering projects is a victim mentality. There’s nothing winning about it because the trades and the people have already lost.” Build the systems that make the rescue unnecessary in the first place.

On we go.

FAQ

Isn’t it better to have a skilled fixer available than to lose a project entirely?
In the moment a project is already failing, yes, a skilled fixer is better than losing it entirely. The real issue is treating that fixer as an ongoing operating strategy rather than a rare exception. An organization that repeatedly needs the same solution has a systemic problem in training, systems, or pre-construction that a fixer will never actually resolve, no matter how many times they are sent in.

Why does sending a top performer to fix a project actually hurt that person’s career?
Because it pulls them away from the work they are genuinely best at, which is running stable, well planned projects, and repeatedly puts them into brutal, reactive hours cleaning up problems they did not create. Over time, an organization that relies on this pattern is signaling that it values crisis response over genuine prevention, which is a poor long term use of a top performer’s actual talent.

How does constantly rescuing projects create learned helplessness on the existing team?
When a team knows a skilled outsider will eventually be sent in if things go badly enough, their own sense of ownership over the outcome weakens. Rather than developing the judgment and accountability that come from working through problems themselves, they learn to wait for rescue, which stunts the kind of career growth that comes from experiencing a genuinely well run project firsthand.

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.

Managers Must Be Present

Posted on August 25, 2026August 25, 2026 by va.jason.almas@gmail.com

Read 16 min

If the Manager Is Not Available, That Is Cowardly Behavior

Here’s the deal. I recently ran into a customer service problem where the actual solution required getting a manager involved, and there was no manager to reach. No accountability, no accessible decision maker, nothing. It got me thinking about how often that same pattern shows up in construction, and how differently a real leader operates.

A manager who cannot be found when something goes wrong is not busy. That is cowardly behavior, and it is worth naming it plainly, because our industry tolerates it far too often.

What Hidden Leadership Actually Looks Like

Picture a service call where the front line staff genuinely cannot resolve the problem, and the only path forward runs through a manager who is simply unavailable. No escalation path. No accountability. The person on the phone is doing their best, and the actual decision maker is nowhere to be found. That experience is frustrating precisely because it reveals something true about how the organization is structured. The person with authority to actually solve the problem has made themselves inaccessible.

There is a version of this that is even worse, and I have heard it described directly. Front desk staff at some businesses will take turns pretending to be the manager when a customer complains, laughing it off once the complaint is handled. That is not an isolated bad employee. That is an organization where hiding from accountability has become normal enough to turn into a running joke.

I want to be clear that I am not one of those people who reflexively demands to speak to a manager over every minor inconvenience. This is specifically about the moments where a genuine problem exists, the front line staff genuinely cannot fix it, and there is simply nobody with the authority to actually resolve it. Those moments reveal whether an organization has real accountability built into its structure or only the appearance of it.

The Historical Example That Says It All

There is a well documented example from military history worth remembering here. During the Battle of Kasserine Pass in World War Two, the commanding officer in charge was reportedly seventy miles away in a bunker, entirely removed from the actual fighting, while his troops faced a devastating defeat. That distance from the front line is treated, correctly, as a serious leadership failure in military history, not a reasonable precaution.

Now ask yourself whether a genuinely Lean, high functioning company anywhere in the world would tolerate a manager hiding that far from the actual work. It would not. A manager’s job is not to secure comfort and distance from problems. It is to lead, to keep things flowing, and to genuinely support the people doing the work.

What Real Presence Actually Looks Like

Contrast that with the experience of a manager who walks the floor directly and asks a genuine, specific question. Are we taking care of you? That single habit, showing up in person and asking directly, is active participation. It is real leadership, visible and accountable, not hidden behind a policy or an escalation queue nobody can actually reach.

Watch for these signs a manager has become inaccessible rather than genuinely busy:

No clear path for a problem to reach an actual decision maker when the front line cannot resolve it
A manager whose presence is limited to reports and meetings rather than direct time with the people doing the work
Complaints or problems being deflected or minimized rather than escalated to someone who can genuinely act on them

Why This Applies Directly to Construction

Construction project managers should never be hidden away at corporate, reachable only through layers of communication that slow everything down. They should be able to help solve problems directly, and they should actually be present where the work happens.

There is a pattern worth learning from Toyota’s approach to their own operations. Their leadership spends the majority of their time with vendors and suppliers, out where the actual relationships and problems live, rather than sitting at headquarters. Apply that same logic to a construction project manager, and the question becomes obvious. Why would a great project manager wait at the jobsite for problems to hit them, rather than spending real time with trade partners proactively, making sure those problems never reach the site in the first place? Packaging the train properly before it ever leaves the station prevents the crash. Waiting at the jobsite to react to whatever arrives does not.

That is the actual mark of a great leader in this industry. Time spent proactively with trade partners, building relationships and solving problems before they ever become field issues, is worth far more than time spent reacting to crises after they land.

Think about what each approach actually costs. A project manager who waits at the site absorbs every problem at its most expensive and disruptive moment, when a crew is already stopped and a schedule is already slipping. A project manager who spends real time with trade partners ahead of time catches the same problem while it still costs a phone call and a conversation instead of a delayed zone and a frustrated crew.

What Genuinely Present Leadership Looks Like in Practice

The best project managers I have personally worked alongside were out and about constantly, talking directly to foremen, solving problems in the middle of the actual work, pulling people out of their comfort zones, and genuinely building the team rather than managing it from a distance. That is what a real manager does, regardless of the specific title on their business card, whether project manager, senior project manager, or project executive. The role matters less than the behavior.

Being the chief problem solver, the chief people officer, and the chief support enabler for your own team, before ever prioritizing your own comfort or distance from the friction of daily problems, is not a nice extra quality in a leader. It is the actual job.

Building Presence Into How Your Organization Leads

None of this is really about any single bad customer service experience. It is about recognizing a pattern that shows up constantly across industries, including our own, and deciding not to tolerate it inside your own organization.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build the kind of visible, accessible, proactive leadership that prevents problems instead of just reacting to them once trade partners and crews are already stuck. A project manager who is genuinely present with the field and with trade partners, rather than hidden away reacting to reports, is one of the highest leverage investments a project can make.

So here is the challenge. Look at how accessible your own leadership actually is, whether that is you or the managers on your team. If a genuine problem showed up on your project today, is there a clear, fast path to someone with the authority to actually solve it, or would it get stuck in an escalation queue with nobody truly accountable at the other end? That answer tells you exactly where to start.

Jason Schroeder said it plainly: “If the manager’s not available, that’s cowardly behavior.” Be present, be accessible, and go find the problems before they find you.

On we go.

FAQ

How is a manager who is genuinely busy different from one who is inaccessible?
A genuinely busy manager is still reachable within a reasonable time frame and has a clear system for someone else to escalate a real problem to them when needed. An inaccessible manager has no real path for a legitimate issue to reach them at all, leaving front line staff or field crews with no way to resolve something beyond their own authority. The difference is not how much is on their calendar, but whether accountability actually exists somewhere reachable.

Why does spending time with trade partners proactively matter more than being present on the jobsite reactively?
Because problems that get resolved during a proactive conversation with a trade partner never reach the jobsite as a crisis in the first place. Waiting at the site to react to whatever arrives means every issue has already become a field problem by the time it is addressed, which is more expensive and disruptive than catching it earlier through a direct relationship with the people doing the work.

What does it look like for a construction project manager to be genuinely present rather than hidden at corporate?
It looks like regular, direct time spent with foremen and trade partners, actively solving problems in the middle of real work rather than only through emails, reports, and scheduled meetings. It also means being reachable quickly when a genuine issue arises in the field, rather than requiring multiple layers of escalation before someone with real authority actually engages with the problem.

If you want to learn more we have:

Discover Jason’s Expertise:

Kanban for the Crew

Posted on August 25, 2026August 25, 2026 by va.jason.almas@gmail.com

Read 17 min

Kanban for the Crew: Taking a Proven Office Tool Down to the Zone

Here’s the deal. Most people who have heard of Kanban or Scrum boards think of them as an office tool, something the project manager and project engineer use to track submittals and paperwork. That is true, and it is also only half the story. The same board, the same logic, and the same discipline belongs at the crew level too, inside the actual zone where the work happens.

I want to walk through both halves of this, because understanding how they connect is what makes the whole system genuinely powerful instead of just two separate tools that happen to share a name.

The Office Version, Done Right

In the Takt production system, I recommend running a Kanban or Scrum board with four columns. Backlog, meaning everything that eventually needs to get done. Sprint backlog, meaning the specific slice of that backlog you intend to work on in the current period, usually a week. In progress. And done.

Each item on the board lives on its own sticky, and that sticky carries two important pieces of information. A Fibonacci number representing the level of effort the task actually requires, and a clear description that includes a genuine definition of done. That definition of done matters more than people realize. It removes ambiguity about what the finished product actually looks like, so anyone glancing at that sticky, not just the person who wrote it, understands exactly what is expected before it can move to the done column.

This board belongs somewhere specific, in the trailer, near the project managers and project engineers, where it becomes part of the actual daily rhythm rather than a static display nobody interacts with. It ties directly into the meeting cycle the rest of the project runs on, from team meetings and strategic planning through the trade partner weekly tactical, the afternoon foreman huddle, the morning worker huddle, and crew preparation. The project delivery team itself should be standing up for five to fifteen minutes a day specifically to clear the way, meaning removing whatever is blocking the field from moving forward.

Why the Office Always Aligns to the Field

Here is the principle that keeps this whole system honest. If a project engineer is working on one submittal and the field signals that a different submittal has become more urgent, the order of the stickies changes to match what the field actually needs. The office is not a separate team working on its own priorities. It is the same team, in a different geographic location, supporting the work happening in the zones.

Watch for these signs your office Kanban board has drifted away from this principle:

Sticky priority order that has not changed in weeks despite the field’s actual needs shifting
A board that exists but is not connected to the daily huddle and meeting cycle
Stickies without a genuine definition of done, leaving room for disagreement about whether something is actually finished

That alignment, office serving field rather than field waiting on office, is the whole reason this tool works. A board that does not move when field priorities move is just decoration.

The Idea That Changed How I See Kanban

Here is something that genuinely shifted my thinking recently, and I want to give credit where it belongs. Hal Macomber challenged me to dig deeper into Kanban, and in doing that research, something clicked that I had not fully connected before.

A lot of contractors genuinely want visibility inside the installation work package itself, within a specific zone, within a specific Takt time, down to the detailed steps a crew actually needs to complete, sometimes down to the hour or even the minute. That level of granularity is exactly what a Kanban board can provide, and it does not have to live only at the office level. It can live at the crew level too.

What Crew Level Kanban Actually Looks Like

The format can flex to whatever fits the crew, electronic, physical stickies, a simple written list, or dedicated software. What matters is not the medium. What matters is that the crew has a clear, shared view of what falls into backlog, what is currently in progress, and what is genuinely done, with items moving from left to right as work actually happens.

Add a target time to each item, and the board becomes something more than a to-do list. It becomes a real production tool, giving the crew a shared, visible sense of pace inside their own zone and Takt time, the same way the office board gives project managers a shared, visible sense of pace across the whole project. A crew working from a board like this can see at a glance whether they are ahead, on pace, or falling behind on the specific steps inside their own scope, rather than only finding out at the end of the day whether the zone finished on time.

This is also where the concept genuinely earns its place next to the standing tactical order about stopping, calling, and resolving problems at the source. A crew watching its own board in real time notices a slipping pace long before a superintendent would catch it during a walk through, which means the roadblock behind that slip gets identified and raised while it is still small and cheap to fix.

Why This Matters Beyond Just Visibility

None of this is really about the board itself. It is about giving every level of a project, from the project engineer in the trailer to the crew standing in a zone, the same basic tool for seeing their own work clearly and moving it forward with intention instead of guessing.

A crew with a genuine backlog, in progress, and done structure, with clear definitions of done for each step, does not need to ask a superintendent every hour what comes next. The board already answers that. And a crew that can see its own pace against a target time can raise a problem early, the moment they notice they are falling behind, rather than discovering it only when the whole zone is already late. That is exactly the kind of early visibility that turns a roadblock into a quick fix instead of a schedule crisis.

There is also a real ownership benefit here that is easy to overlook. A crew moving its own stickies from backlog to in progress to done is actively tracking its own performance, rather than waiting to be told how the day went. That shift, from being measured by someone else to measuring your own progress in real time, tends to change how a crew relates to the work itself.

Bringing This Into Your Own Project

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build both levels of this system, the office Kanban board tied into your daily meeting cycle, and a crew level version that gives your zones the same visibility down to the hour or the step. Getting both levels working together, and genuinely aligned so the office always serves the field, is what turns this from a nice idea into a real production tool.

So here is the challenge. If your project already runs an office level Kanban board, ask whether it is genuinely tied into your daily huddle cycle and whether its priority order actually shifts when the field’s needs shift. If it does not have a crew level version yet, pick one zone this week and try it, even with something as simple as three columns and a stack of stickies, and see what changes when the crew can see their own progress clearly.

Jason Schroeder said it plainly: “We always align the office to the field.” Build both boards around that principle, and the whole system stays honest.

On we go.

FAQ

What is the difference between the office level Kanban board and a crew level one?
The office level board typically tracks larger items like submittals, procurement, and coordination tasks managed by project managers and project engineers, usually on a weekly sprint cadence. A crew level board tracks the detailed steps inside a specific installation work package, zone, and Takt time, sometimes down to the hour or the minute. Both use the same backlog, in progress, and done structure, just at different levels of granularity.

Why does the definition of done matter so much on a Kanban sticky?
Because without it, different people can interpret when a task is actually finished differently, which creates disputes and inconsistency about what counts as complete. A clear definition of done removes that ambiguity, so anyone looking at the sticky, not just the person who created it, understands exactly what the finished result needs to look like before it moves to the done column.

How do you decide the right target time for a crew level Kanban item?
Target times should reflect a realistic estimate of how long a specific step actually takes within the crew’s Takt time and the zone’s overall pace, rather than an arbitrary number. Basing it on genuine production data, similar to how zone sizes and cycle times get calculated in a pull plan, keeps the board an honest reflection of pace rather than a source of false pressure.

If you want to learn more we have:

Discover Jason’s Expertise:

Cord Management Practices

Posted on August 25, 2026August 25, 2026 by va.jason.almas@gmail.com

Read 22 min

Cord Management Practices: Why Temporary Power Tells You Everything About How a Site Is Run

Cord management is not glamorous. Walk any jobsite and you will find extension cords snaking across walkways, daisy chained reels stacked three deep, and damaged cords nobody flagged because flagging them felt like more trouble than it was worth. Small stuff. Until someone trips, a tool fails mid task because the power dropped, or a cord gets pinched at a doorway and shorts out.

Here is the deal. Temporary power is one of the most overlooked systems on any construction project, and it is also one of the clearest leading indicators of how well the rest of the operation is being run. A site with cords snaking across every walkway, damaged jackets nobody replaced, and reels tangled into a pile is telling you something about its housekeeping standard, its inspection discipline, and its overall attention to detail. That signal is not subtle once you know to look for it.

The Pain of a Hazard Everyone Has Learned to Step Over

Picture a typical work area three weeks into an active phase. An extension cord runs from a panel across the main walkway to a saw station forty feet away, because the outlet closest to the work was already occupied and nobody set up a secondary drop. A reel sits half unwound near the base of a stairway, its cord looping across the bottom two steps. Somewhere near the back of the space, a cord with a visibly cracked jacket has been in use for two weeks because pulling it would mean stopping to find a replacement, and stopping felt like a bigger cost than the risk felt like a problem.

None of this happened because anyone wanted to create a hazard. It happened because temporary power gets treated as an afterthought, something that gets set up quickly at the start of a task and then left alone until the task is finished, rather than something maintained continuously with the same discipline applied to any other safety system. Everyone on the crew has walked past that cord across the stairway a dozen times. They have learned to step over it without thinking. That adaptation is exactly what makes it dangerous. The moment someone new to the space, distracted, or carrying material with both hands walks that same path, the hazard that everyone else learned to avoid becomes the incident nobody saw coming.

The Failure Pattern

The failure pattern is treating temporary power as a setup task rather than a maintained system.

Cords get run when a task starts. A reel gets pulled out, a drop gets connected, and the immediate power need is solved. What rarely happens is a plan for how that power access will be maintained as the task continues, as other trades move through the same space, and as conditions around the drop change. The cord that made sense on day one, running along a clear path to an empty work area, becomes a hazard on day five once material has been staged nearby, other crews have started working adjacent tasks, and foot traffic through that specific corridor has increased.

Because nobody owns temporary power as an ongoing responsibility, it degrades the same way any unmanaged system degrades. A cord gets moved to accommodate a delivery and never gets rerouted properly afterward. A pinch point develops where a cord crosses a door threshold repeatedly, and the damage accumulates invisibly until the jacket finally splits. A reel that was neatly wound at the start of the week becomes a tangled mess by Friday because nobody was responsible for re coiling it during the daily cleanup. Each of these small degradations feels too minor to address on its own. Together they produce exactly the chaotic power setup that signals a site running without real housekeeping discipline.

They Didn’t Fail the System

When a crew member trips over a cord, or a damaged cord causes a tool failure mid task, the instinct is to ask why that person was not paying closer attention. Why didn’t they see it? Why didn’t they report the damaged cord sooner?

The more useful question is what the site gave that person to work with. If cords are routinely run across primary walkways because no one designed a routing plan that keeps power access away from foot traffic, the crew member did not fail to notice a hazard. They were navigating a hazard that the system placed directly in their path. If a damaged cord stayed in service for two weeks, that is not one person’s oversight. That is the absence of a daily inspection practice that would have caught the damage on day one instead of day fourteen.

People adapt to whatever environment they are given. A crew working in a space with cords consistently kept off walkways, power reliably positioned near the task, and damaged equipment pulled the same day it is found will maintain that standard without much prompting, because the environment reinforces it. A crew working in a space where cords have always been in the way and damage has always gone unaddressed will adapt to that instead, and the adaptation looks like carelessness even though it is actually a rational response to an unmanaged system.

What a Lean Standard for Cord Management Actually Requires

Keeping cords off walkways is the foundation, and it requires actual routing decisions rather than hoping cords happen to end up out of the way. Overhead routing or placement along designated edges removes the trip hazard entirely rather than just minimizing it, and the decision about where cords will run should be made at the same time the work area is set up, not improvised after the fact when the walkway is already established and the cord has nowhere else to go.

Providing power near the work addresses the root cause of most of the long, snaking runs that create hazards in the first place. Drops, reels, or outlets positioned close to the actual task mean the distance a cord has to travel is short, which means fewer opportunities for that cord to cross a walkway, wrap around a corner, or stretch across a space where other crews are moving. This is the same principle behind point of use material staging applied to power access specifically. Bring the resource to where the work is happening instead of asking the work to reach across a long, exposed run to get to it.

Securing and protecting cords addresses the damage that accumulates invisibly over time. Supporting cords so they are not lying loose across high traffic areas, tying them to keep routing consistent, and shielding them from pinch points and moisture all extend the working life of the equipment while also keeping the routing itself predictable rather than shifting day to day as cords get kicked, stepped on, or repositioned informally.

Battery tool stations reduce the entire problem at its source by reducing how much temporary power infrastructure a site needs in the first place. A clean, organized charging area that maximizes cordless tool use means fewer cords running at all, which means fewer opportunities for any of the other failure modes to occur. This is not a replacement for good cord management on the tasks that still require corded power. It is a genuine reduction in total exposure.

Daily inspection is what keeps the entire system from degrading the way unmanaged systems always degrade. Pulling damaged cords immediately, rather than letting them stay in service until someone finally has time to deal with it, is the difference between a hazard caught in hours and a hazard that persists for weeks. This inspection does not need to be elaborate. It needs to be consistent, assigned to someone specific, and treated as a non negotiable part of the daily routine rather than something that happens when time allows.

Why This Is a Leading Indicator, Not Just a Safety Item

Clean power access tells you something about a site that extends well beyond the cords themselves. A team that maintains disciplined cord routing, inspects daily, and pulls damaged equipment immediately is a team that has built genuine housekeeping discipline into its daily rhythm. That same discipline almost always shows up in how the team manages material staging, tool organization, and general site cleanliness, because the underlying habit, noticing small degradation and correcting it before it compounds, is the same habit across every one of those systems.

The reverse is equally reliable. A site where temporary power looks chaotic, cords everywhere, reels tangled, damaged jackets in service, is very rarely a site that has excellent discipline everywhere else and simply happens to be sloppy about cords. Chaotic temporary power is almost always one visible symptom of a broader pattern, the same pattern that shows up in an unmanaged connex box, an undisciplined corridor, or a laydown yard nobody has organized in weeks. Cord management is easy to observe and hard to fake, which is exactly what makes it such a useful leading indicator for anyone trying to read the actual condition of a site quickly.

Signals Your Cord Management Needs Attention

Walk your active work areas and look for these patterns:

Cords crossing primary walkways or stairways rather than routed overhead or along designated edges
Long extension runs from a distant outlet instead of power positioned close to the actual task
Cords with visible damage, cracked jackets, or exposed wire still in active use
Reels left tangled or unwound at the end of the day rather than recoiled and stored
No specific person or routine assigned to inspect temporary power daily

Each of these is a small, fixable gap, and each one is worth taking seriously precisely because of what it tends to indicate about the rest of the operation.

Building the Standard Into the Daily Rhythm

A Lean standard for cord management does not require significant investment. It requires a routing decision made when each work area is set up, power positioned close enough to the task that long runs are rarely necessary, cords secured and protected from the pinch points and moisture that cause premature damage, a genuine push toward battery tool use where it is practical, and a daily inspection that treats a damaged cord as something to pull immediately rather than something to note for later. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. Jason Schroeder and the LeanTakt team treat clean temporary power as one of the fastest ways to read the real condition of a site, because a team that maintains this discipline is very rarely cutting corners anywhere else.

Walk Your Power Setup Today

Here is your challenge. Walk your active work areas today and specifically look at the cords. Where are they routed. How far is power from the actual task. Is anything damaged and still in service. Fix what you find, and build the daily inspection into your routine going forward rather than waiting for the next walkthrough to catch it.

Edwards Deming put it plainly: “In God we trust, all others bring data.” Walk the site, look at the cords, and let what you actually see tell you the truth about how the rest of the operation is running.

On we go.

FAQ

Why does cord placement matter so much if the hazard seems minor?
A single cord across a walkway is a low probability, low severity event on any given day, but the same cord crossed hundreds of times by dozens of people over weeks accumulates real exposure. Trip hazards in high traffic corridors carry more cumulative risk than the same hazard in a rarely used area, simply because of how often people encounter it.

How often should temporary power be inspected?
Daily during active phases of work, ideally as part of a broader daily site walk that also covers housekeeping and material staging. Damage that goes unnoticed for even a few days can worsen quickly, especially in areas exposed to moisture or repeated foot and equipment traffic.

Is switching to battery tools a full replacement for cord management practices?
Not entirely. Battery tools reduce how much cord infrastructure a site needs, which reduces overall exposure, but most active sites will still require corded power for certain equipment. The two practices work together rather than one replacing the other.

If you want to learn more we have:

Discover Jason’s Expertise:

Area Access And Walkways

Posted on August 25, 2026August 25, 2026 by va.jason.almas@gmail.com

Read 22 min

Area Access and Walkways: Why Your Corridors Are the Project’s Arteries

A jobsite’s corridors are its arteries. When they are clear, the project breathes. Crews flow in, materials flow through, information flows out. When they are blocked, everything downstream starts to starve.

Here is the deal. Most projects treat walkway maintenance as housekeeping, something to clean up when there is time, something that matters for appearance but not for production. That framing misses what a corridor actually does on an active jobsite. It is not a decorative pathway. It is the circulation system that every crew, every material delivery, and every piece of coordination depends on to reach the work face. When that system is blocked, the blockage does not stay local. It propagates downstream, exactly the way an artery blockage affects tissue far beyond the point of the obstruction.

The Pain of a Corridor Nobody Owns

Walk a project without a disciplined walkway standard and the pattern is familiar. Material gets dropped in the corridor because it was the closest available space when the delivery truck arrived. Debris from an active task accumulates because cleanup happens at the end of the day rather than continuously. A trade’s tools and equipment spread into the walking path because the designated staging area was full or inconvenient. None of this happens because anyone intends to create a hazard. It happens because the corridor belongs to everyone in theory, which means in practice it belongs to no one.

The cost of that ownership gap is not abstract. A foreman who needs to move a crew from one zone to another has to navigate around obstructions, adding minutes to what should be a direct walk. A material delivery that needs to reach a work face has to detour around staged items that were never supposed to be in the lane. A Takt zone handoff that depends on the next crew arriving on schedule slips because that crew spent fifteen minutes finding a clear path instead of arriving ready to work. None of these costs show up individually as a crisis. They show up collectively as a project that never quite hits the pace the schedule assumes it will.

The Failure Pattern

The failure pattern is treating corridors as leftover space rather than as designed infrastructure.

Most site logistics planning focuses on the work areas themselves, where trades will be positioned, where major equipment will operate, where staging yards will sit. The corridors connecting those areas often receive far less deliberate planning, treated as whatever space happens to remain once the primary areas are defined. That approach produces walkways that are functional in the early phases of a project, when activity is light, and progressively degraded as the project ramps up and every trade needs somewhere to put material, tools, and debris that the original plan never explicitly addressed.

Once a corridor starts absorbing overflow from adjacent work areas, it rarely self-corrects. Each additional item placed in the walkway makes the next placement feel more normal, because the standard has already been compromised. A single pallet at the edge of the path becomes two pallets, then a stack of debris waiting for removal, then a piece of equipment parked because there was nowhere else convenient to put it. The corridor degrades the same way any unmanaged space degrades: not through a single decision, but through the accumulation of many small decisions that each seemed reasonable in isolation.

They Didn’t Fail the System

When a foreman loses time navigating a blocked corridor, or a delivery gets delayed because the path to the work face is obstructed, the instinct is to look at whoever left material in the way. Why didn’t they stage it properly? Why wasn’t this cleaned up?

Before assigning that blame, it is worth asking what the project actually gave people for staging space. If the designated staging areas were undersized for the volume of material moving through a phase, trades will use the corridor because there is nowhere else to put material that has arrived and needs somewhere to sit before installation. If nobody has been assigned specific responsibility for walkway condition, and no one is checking it on a regular cadence, degradation will happen gradually and go uncorrected, not because anyone is careless, but because the system never assigned the corridor a keeper.

The trade that staged material in the walkway did not fail the project. The project failed to give that trade an adequate alternative, or failed to assign anyone the responsibility of maintaining the standard once the initial setup was complete. Fix the system and the behavior follows. Blame the individual and the same pattern will recur with the next trade, on the next task, in the same corridor.

What a Healthy Corridor Actually Requires

A functioning corridor is not simply an empty hallway. It is a designed system with specific, observable components, each one addressing a distinct failure mode.

A clear, marked pedestrian path establishes an unambiguous boundary between the walking lane and everything else. A marked line on the floor removes any ambiguity about where staging ends and passage begins, which matters because unmarked corridors invite gradual encroachment in a way that clearly bounded ones do not. Once a boundary is visible, a trade staging material two feet into the marked lane is an obvious deviation rather than a judgment call, and obvious deviations get corrected faster than ambiguous ones.

Organized material staging positioned to the side of the lane, not in it, means that material has a designated home that is not the walkway itself. This only works if the staging capacity is actually sized to the volume of material the phase requires. A staging area too small for the trades using it will inevitably overflow into the corridor, regardless of how clearly the boundary is marked, because the material still needs somewhere to go.

Good lighting and visibility address a hazard that becomes more dangerous specifically because the corridor is a high-traffic area. A trip hazard in a low-traffic zone is encountered rarely. The same hazard in a primary corridor is encountered by every crew moving through the project multiple times a day, which multiplies both the likelihood and the consequence of an incident.

No debris or clutter underfoot is the baseline condition that everything else depends on. Debris accumulates continuously during active construction, which means corridor cleanliness is not a one-time setup task but an ongoing maintenance requirement that has to be built into the daily and weekly rhythm of the project rather than treated as an occasional cleanup effort.

And an accessible work area, connected cleanly to the corridor system, ensures that the corridor is actually serving its function of getting people and material to where the work happens, rather than existing as a clean pathway that dead-ends at an obstructed or poorly connected work face.

Why This Is Production Strategy, Not Housekeeping

The instinct to categorize walkway maintenance as housekeeping comes from focusing on what a clean corridor looks like rather than what it does. A clean corridor looks like tidiness. What it actually does is protect throughput, the rate at which people, material, and information can move through the project without friction.

Every Takt zone handoff depends on the crew arriving at the next zone on schedule, and arrival depends on an unobstructed path to get there. Every material delivery to a work face depends on a clear route from the staging area or the loading dock to the point of installation. Every piece of information that needs to move from the field to the trailer, or from one foreman to another, depends on someone being able to walk the distance without detouring around obstacles. When corridors are blocked, all three of those flows slow down simultaneously, and the schedule absorbs the cost even though no single blocked corridor ever appears as a line item on any report explaining why the week ran behind.

This is exactly the same logic that governs staging materials at the point of use and maintaining a Lean Connex Box. Removing friction from the path between a resource and the person who needs it is not a courtesy. It is the mechanism by which a project actually achieves the pace its schedule assumes. Corridors are simply that same principle applied at the scale of the entire site rather than a single workstation or storage unit.

Signals Your Corridors Need Attention

Walk your project’s primary walkways and look for these patterns:

Material or equipment positioned inside the marked pedestrian path rather than in designated staging
Debris accumulating in high-traffic corridors between scheduled cleanup periods
No clear, marked boundary distinguishing the walking lane from adjacent staging or work areas
Crews or foremen regularly detouring around obstructions to reach a work face
Staging areas adjacent to corridors that are consistently at or over capacity, pushing overflow into the walkway

Each of these signals is a production cost hiding inside what looks like a cleanliness issue, and each one is addressable with the same discipline applied to any other visual management system on the project.

Building Corridor Discipline Into the Daily Rhythm

A healthy corridor system requires the same three components that keep any visual management practice functioning: a clear standard, an assigned owner, and a regular inspection cadence. The standard is the marked path, the designated staging boundaries, and the expectation of a debris-free lane. The owner is a specific person, often a superintendent or a designated field engineer, whose responsibility includes a walkway condition check as part of their regular site walk. The cadence is frequent enough to catch encroachment before it compounds, ideally daily during active phases when material and debris accumulate quickly.

When staging capacity is consistently overflowing into the corridor, the fix is not a stricter warning to the trades involved. It is resizing the staging areas to match actual material volume, because a corridor that is being used as overflow staging is telling you that the designated staging space was never adequate for the phase of work happening around it.

Protect the path, and you protect the plan. Every Takt handoff, every material delivery, every foreman’s ability to move quickly between zones depends on corridors that function the way arteries function: clear, continuous, and carrying exactly what the project needs to keep flowing. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. Jason Schroeder and the LeanTakt team treat corridor discipline as a core production input, because a blocked path costs a project the same way a blocked artery costs a body, quietly, cumulatively, and in ways that are easy to miss until the whole system is struggling.

Walk Your Corridors Today

Here is your challenge. Walk your project’s primary circulation paths today with fresh eyes. Look for anything encroaching into the marked lane, any debris that has accumulated since the last cleanup, any staging area that is clearly overflowing. Fix what you can fix immediately, and flag what needs a larger staging solution.

Taiichi Ohno taught that flow is the foundation everything else depends on, and a project cannot flow if the paths connecting its parts are obstructed. Your corridors are not the leftover space between the real work. They are part of the real work. Treat them that way.

On we go.

FAQ

How is corridor management different from general site cleanliness?
General cleanliness addresses appearance and basic housekeeping across the whole site. Corridor management specifically protects the circulation paths that crews, materials, and information depend on to move through the project efficiently. A corridor can look reasonably clean while still being encroached upon in ways that slow throughput, which is why it deserves distinct attention rather than being folded entirely into a general cleanliness standard.

What is the most common cause of corridor blockage on active projects?
Staging areas that are undersized for the actual volume of material moving through a given phase. When designated staging space cannot hold what a trade needs to stage, the overflow goes somewhere, and the nearest available space is often the adjacent corridor. Fixing chronic corridor blockage usually requires resizing staging capacity rather than simply enforcing a stricter rule against using the walkway.

Who should be responsible for maintaining walkway standards?
A specific, assigned owner, typically a superintendent or field engineer, who includes corridor condition as part of a regular site walk. Shared responsibility across all trades tends to produce the same degradation pattern seen in other unmanaged shared spaces, where everyone assumes someone else will maintain the standard and nobody actually does.

If you want to learn more we have:

Discover Jason’s Expertise:

Continuous Improvement: Start with Fundamentals

Posted on August 24, 2026August 24, 2026 by va.jason.almas@gmail.com

Read 17 min

Why Continuous Improvement Fails in the US Before It Even Starts

Here’s the deal. Continuous improvement is a genuinely great concept, and it is not wrong for construction companies to talk about it constantly. The problem is that most of them are putting the cart before the horse. You cannot improve a system that was never installed in the first place, and that is exactly where almost every construction company and manufacturing plant in the United States actually stands.

The Order Nobody Talks About

Continuous improvement is not where you start. It is where you end up, after a specific sequence of foundational work has already been done. Respect for people comes first. Stability and standardization come second. Working in genuine one piece flow comes third. Flowing together, meaning pulling work through a system instead of pushing it, comes fourth. Total participation with visual systems comes fifth. Only after all five of those are genuinely in place does continuous improvement become something you can actually do.

Most companies skip straight to step six without ever building steps one through five. Floors are not painted or marked. There is no standard work. Bathrooms and basic facilities are neglected. There is no real visual management, no documented operating system, no clear business system. Nothing about the environment has been stabilized, and yet the instruction handed down is to go improve it anyway.

You Cannot Improve What Was Never Installed

Here is the honest question worth asking before adopting any continuous improvement program. Do you actually have the system installed? Not do you have good intentions, or a poster about Lean principles on the wall, but do you have a real, documented, stable system running day to day. If the answer is no, the starting point is not continuous improvement. It is installing the system in the first place.

That first move often looks like radical change, what the Japanese call kaikaku, rather than the slow, incremental improvement most people picture when they hear the word Kaizen. If you want to call installing an entire missing system continuous improvement, that is a matter of labeling. What actually needs to happen first in most American construction companies is not incremental refinement of an existing system. It is building the system that was never there.

That distinction matters because the two require completely different levels of effort and disruption. Kaizen is a small adjustment layered onto something already functioning. Kaikaku is closer to stopping and rebuilding the foundation itself, painting the floors, writing the standard work, installing the visual boards, fixing the facilities. Treating a kaikaku situation as if it only needs kaizen effort is exactly why so many improvement initiatives quietly stall out after a few months.

Watch for these signs your organization is trying to improve a system that was never actually installed:

No documented standard work for roles that have existed for years
No consistent visual management anywhere on site, beyond a schedule pinned to a wall
Basic environmental conditions, cleanliness, organization, facilities, treated as optional rather than non negotiable

Why This Foundation Comes So Naturally in Japan

It is worth understanding why continuous improvement lands so differently in a Japanese manufacturing or construction environment. It is not because the people are smarter or more capable. It is because the foundation this entire framework depends on is already firmly in place before anyone even mentions the word improvement.

Respect for people is built into the operating culture from the start. Environments are genuinely stable, with clear instructions attached to every role. One piece flow is understood deeply, largely because of the influence W. Edwards Deming had on Japanese manufacturing after World War II, and it shows in how work actually moves through a system rather than sitting in disconnected batches. Total participation is treated as a baseline expectation, not an aspiration. And visual management is valued over pure aesthetics. Walk through a Japanese train station and you will see signage and floor markings everywhere, guiding people to exactly where they need to be. It might look busy to someone used to clean, unmarked American walls, but it is genuinely organized, and it flows.

With all of that already in place, a Japanese manufacturing team can look at their system and ask a simple, honest question. What can we improve here? In most American companies, that same question runs into an immediate wall. Improve what? The chaos? The pile that will be somewhere different next month? The task everyone on the crew does a slightly different way because no standard work was ever written down? You cannot meaningfully improve something that was never actually defined.

That gap is not a matter of intelligence, effort, or work ethic. American crews are every bit as capable and hardworking as any crew anywhere in the world. The difference is entirely in what foundation they were handed to work inside, and that foundation is a leadership and systems decision, not a reflection on the people executing the work every day.

The Fundamentals the United States Needs First

If continuous improvement genuinely is more applicable in Japan right now, the honest response is not envy. It is naming exactly what needs to be built here first.

Respect for people has to be the actual starting point, extended fully and consistently to everyone on the jobsite regardless of who they are. Every environment needs to be clean, safe, and organized, with no excuse accepted for anything less, and every step of the work needs real standard work attached to it. Instead of large batch production left over from decades of economic abundance, we now genuinely need to return to one piece flow and just in time production, especially across multi-trade construction and multi-station manufacturing, where flowing together and pulling work through the system matters more than ever. And total participation has to replace the lone operator mindset that our culture tends to romanticize, the myth of one person heroically solving everything alone, which makes for compelling movies and does not reflect how real, high functioning crews actually operate.

That myth deserves a direct correction. Real ranch work, real crews, real high performing teams do not run on one heroic individual carrying everyone else. They run on total participation, coordination, and people genuinely working together toward a shared standard. The lone hero is a storytelling device. It is not a production system, and treating it like one is part of what keeps American construction from building the foundation continuous improvement actually requires.

Building the System Before You Try to Improve It

None of this is a criticism aimed at any single company. It is a diagnosis of where the American construction industry genuinely stands, and it points toward a clear, specific starting point rather than a vague call to try harder at continuous improvement.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build the actual foundation first, respect for people, stability, standard work, one piece flow, and total participation with real visual systems, before ever asking anyone to improve a system that does not exist yet. That sequence is not optional, and skipping it is exactly why so many continuous improvement efforts in this country quietly fail before they produce anything real.

So here is the challenge. Before your next continuous improvement initiative, honestly answer whether your team has documented standard work, real visual management, and a genuinely stable, respectful environment already in place. If any of those are missing, that is where the actual work starts, not with an improvement program layered on top of a system that was never built.

Jason Schroeder said it plainly: “Continuous improvement is not where we start.” Build the system first. Improvement will actually mean something once you do.

On we go.

FAQ

What is the difference between kaikaku and kaizen?
Kaizen refers to slow, incremental improvement made to an existing, stable system over time. Kaikaku refers to radical, foundational change, often needed when the basic system was never properly installed in the first place. Most American construction companies actually need kaikaku before kaizen becomes meaningful, since incremental improvement on top of a missing foundation produces very little real change.

Why does visual management matter so much to this foundation?
Visual management makes the actual state of work immediately visible to anyone looking at it, whether that is a schedule, a zone status, or simply signage showing where something belongs. Without it, problems, inconsistencies, and deviations from standard work stay hidden until they become expensive, and there is no shared, visible reference point for what continuous improvement is even supposed to improve.

How can a company tell whether it actually needs to install a system rather than simply improve one?
Check for the basics first. Documented standard work for key roles, a genuinely stable and organized physical environment, and visible systems anyone can walk up to and understand are the clearest signs a real system exists. If those are missing or inconsistent, the honest starting point is building that foundation, not layering a continuous improvement initiative on top of it.

If you want to learn more we have:

Discover Jason’s Expertise:

Don’t Just Do Something, Stand There

Posted on August 24, 2026August 24, 2026 by va.jason.almas@gmail.com

Read 17 min

Don’t Just Do Something, Stand There

Here’s the deal. There is a quote I want credit going to the right place for. Hal Macomber said it, and Adam Hoots is who reminded me of both the line and who said it. Don’t just do something, stand there. I love this quote, and I think it captures one of the most misunderstood ideas in all of construction.

Who gets credit for a good idea matters far less than whether the idea actually gets used. This one deserves to get used constantly, because it corrects a mistake that costs real money on almost every jobsite in America.

Why Keeping Everyone Busy Is a Bad Goal

Go back to Eliyahu Goldratt’s thinking on full kit and flow, and a specific truth becomes clear. People trying to look busy is a bad thing, not a good one.

Here is the example that makes it concrete. Picture a factory that needs a throughput of four parts an hour. The equipment on the line has different production rates: four parts an hour, then four, then two, then four, four, four, four. If you tell every single piece of equipment to run at its own maximum speed regardless of the others, you actually end up with something like one point two to one point eight parts an hour of real throughput. Everyone working flat out produces the worst result on the list.

If you double the capacity of that slow two part per hour machine, your throughput can reach the full four parts an hour the system needs. Alternatively, if you deliberately slow every other machine down to match that same two part per hour pace, running the faster machines only half the time, your throughput becomes two parts an hour. Slower on paper for most of the equipment, but a better real number than the chaos of everyone running full speed independently. Full speed everywhere is the worst option on the table, and matched pace beats maximum busyness every single time.

The Excavator Story That Makes This Real

Here is my favorite illustration of this, because it happens on real jobsites constantly. Picture an excavator operator on a civil crew who comes up to an unknown pipe that might or might not be in the way of the planned trench. The crew needs to figure out how to proceed, and rather than staying with the problem or stepping out of the cab to help solve it, the operator decides to go look busy somewhere else, wanting to impress the boss with visible activity.

Watch what actually happens next. Diesel gets burned for no productive reason. Equipment takes wear and tear it did not need to take. The work done elsewhere is now uncoordinated and has to be reworked, because it was not planned as part of the sequence. A pile that got moved during that detour is now sitting in the wrong spot, blocking something else. The equipment risks breaking down doing unplanned work. And once the original crew is ready to continue, they now have to wait for the operator to come all the way back and get reoriented to the actual problem, on top of whatever finished work got run over or disturbed during the detour.

All of that dollar waste happened because staying busy felt more valuable in the moment than standing still and solving the actual problem. It was not.

Watch for these signs someone is optimizing for looking busy instead of for flow:

A worker or piece of equipment relocating to unrelated work the moment the original task hits an unknown or a problem
A crew treating idle time as inherently bad, even when the alternative is uncoordinated, unplanned activity
Finished work getting disturbed or reworked because someone needed something to do in the meantime

Stop, Call, Wait

There is a phrase worth adopting directly from this. Stop, call, wait. Sometimes having a worker actually wait is the better outcome. Sometimes a foreman not actively working is the better outcome. Sometimes a zone sitting temporarily idle is the better outcome, because the alternative is pushing ahead without full kit or without a clear plan, and pushing a defect or an uncoordinated decision down the line is far more expensive than the appearance of lost time in the moment.

This connects directly to something worth holding as a standing habit on any project. If you see, hear, or sense something is not right, the correct response is to stop, call the right people in, and wait for a real answer before proceeding, not to keep moving in some other direction just to avoid looking idle.

Why “Don’t Just Stand There, Do Something” Gets Us in Trouble

Here is the instinct working against us. Our default in the United States tends to run the opposite direction. Don’t just stand there, do something. That instinct, so deeply ingrained that it feels like common sense, is exactly what produces the excavator story above, over and over, on jobsites everywhere.

The correct instinct runs the other way. Don’t just do something. Stand there until you actually know what you are supposed to do, which comes down to preparation, doing the work correctly the first time, and staying in a genuine flow rather than filling time with activity that has not been thought through. Worrying more about whether the work is actually flowing than whether everyone looks occupied is the entire shift in mindset this quote is pointing toward.

Resource Efficiency vs Flow Efficiency

There is a real framework behind why this works, described by researcher Niklas Modig as the distinction between resource efficiency and flow efficiency. Resource efficiency asks whether every person and every piece of equipment is being used as much as possible. Flow efficiency asks whether the actual work is moving smoothly and completely through the system.

Those two goals are not the same, and optimizing for the first one frequently damages the second. A jobsite obsessed with resource efficiency keeps everyone visibly busy and produces uncoordinated rework, wasted material, and wear on equipment that did not need to happen. A jobsite that genuinely prioritizes flow efficiency accepts that a worker standing still, a foreman not actively swinging a tool, or a zone temporarily unworked can be exactly the correct state, because the actual measure of success is whether work moves cleanly through the system, not whether every second looks productive on the surface.

Building This Into How Your Team Operates

None of this works if it stays a clever quote nobody actually applies under pressure. The instinct to look busy runs deep, and it takes real discipline, and real permission from leadership, to let a crew stop and wait when that is genuinely the correct move.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams build the discipline to prioritize flow over the appearance of busyness, including giving crews explicit permission to stop, call, and wait when a real problem shows up instead of filling the gap with unplanned activity. That permission has to come from leadership directly, because nobody wants to be the person standing still if they think it will be read as laziness.

So here is the challenge. Think about the last time someone on your project filled idle time with unplanned activity rather than stopping to solve the actual problem in front of them. Calculate honestly what that decision actually cost in rework, wasted material, or lost coordination. That number is usually a lot larger than the cost of simply standing there and waiting for the right answer.

Jason Schroeder said it plainly: “Stop, call, wait.” Sometimes the most productive thing a worker can do is exactly nothing, until the real problem gets solved.

On we go.

FAQ

Isn’t it always better to keep workers and equipment busy to maximize productivity?
No, and this is the core misunderstanding the quote addresses. Keeping every resource maximally busy regardless of the actual bottleneck in the system frequently produces worse total throughput than intentionally matching pace to the true constraint. A factory or jobsite optimized purely for resource utilization can end up slower overall than one that accepts some idle time in exchange for coordinated, planned flow.

What should a worker actually do when they hit an unexpected problem instead of finding other work to look busy?
Stop, call the right people in to look at the problem, and wait for a genuine resolution before proceeding, rather than moving to unrelated work in the meantime. Staying present with the problem, or stepping in to help solve it directly, avoids the uncoordinated rework, wasted material, and equipment wear that come from filling the gap with unplanned activity elsewhere.

What is the difference between resource efficiency and flow efficiency?
Resource efficiency measures whether every person and piece of equipment is being used as much as possible at any given moment. Flow efficiency measures whether the actual work is moving smoothly and completely through the system from start to finish. Optimizing heavily for resource efficiency often damages flow efficiency, since keeping everyone busy regardless of coordination tends to produce rework and waste that slows the overall project down.

If you want to learn more we have:

Discover Jason’s Expertise:

Trades Following the System

Posted on August 24, 2026August 24, 2026 by va.jason.almas@gmail.com

Read 16 min

Trades Should Follow the System, Not Be Punished for Failing

Here’s the deal. A general contractor has to be genuinely firm about the environment, the cleanliness, the safety, the organization, and the logistics on a jobsite, while also being genuinely warm and caring toward the people working inside that system. People assume those two things contradict each other. They do not, and understanding why is one of the most important distinctions a GC can make.

There is a specific line worth drawing clearly. Care intensely whether trades are following the system. Never punish them for failing or making an honest mistake. Those are two completely different things, and treating them as the same thing is where a lot of leadership goes wrong.

Firmness and Warmth Come From the Same Place

People sometimes accuse me of running hot and cold. Nice with the small stuff, harsh with everything else. That is not accurate, and I want to explain why, because the explanation matters more than the accusation.

I send people home for zero tolerance violations because I respect them. I shut down crews to clean because I respect them. I hold a firm line on deliveries because I respect them. I also do barbecues because I respect them. I run worker huddles because I respect them. I shake hands and pick up trash myself because I respect them. Every single one of those actions, the firm ones and the warm ones, comes from the exact same source. A genuinely clean, safe, organized environment where bad behavior is not tolerated is one of the most respectful things you can give the people working on your site. It is not the opposite of caring about them. It is what caring about them actually looks like in practice.

Your Contractor Not Showing Up Is Your Problem

Here is where I get direct with general contractors specifically, because this is where I see the most excuse making. If a trade partner is not showing up to pull plans, pre-construction meetings, on time arrivals, or huddles, that is not a mystery to shrug at. You picked the wrong contractor, and it is your job to fix it.

There is a moment worth picturing here. Somebody complains that their trade partner will not show up to huddles, as if that is simply a fact of nature they have no control over. The honest response is closer to being reminded of your own job title. You are the general contractor. If a trade partner is not participating in the systems your project runs on, that falls squarely inside your authority to address.

Do not tell me you cannot modify the contract. You can. Do not tell me you cannot change the trade partner you are working with. You can do that too. Getting the right people on the bus, and structuring the contract so it actually works for everyone involved, is not one job among many for a general contractor. It is the job.

Watch for these signs a GC is avoiding a decision that is genuinely within their authority to make:

Blaming a trade partner’s absence from huddles or planning sessions as unfixable rather than addressing it directly
Treating the existing contract as untouchable rather than something that can be modified when it is not working
Continuing to work with a trade partner who consistently will not participate in the collaboratively built system, without ever considering a change

The Distinction That Actually Matters

Here is the principle underneath all of this, and it is the one worth remembering above everything else. I worry whether a trade is following the system. I do not worry whether they are making mistakes or failing.

Leaders who never actually control their site or hold trades to a real system end up with only one tool left when something goes wrong: blaming and punishing people for failing or for honest mistakes. That is what happens when the system itself was never enforced in the first place. There is nothing else left to point to except the person, so the person absorbs consequences that should have belonged to a missing system.

I run this differently. As long as a trade is genuinely following the collectively decided, collaborative system, everything else gets fixed together. If they are failing at a piece of the work, I will help. If they made a mistake, I will help fix it. The one thing that will not be tolerated is refusing to follow the system the whole team agreed to build together. That is the actual line, and it is a very different line than punishing effort, mistakes, or honest struggle.

Why This Distinction Protects Psychological Safety

This connects directly to something worth holding onto from a different angle. A team cannot take real interpersonal risks, admit mistakes, or ask for help if doing so gets punished the same way as refusing to follow the system does. Collapsing those two categories into one destroys the very trust that lets people surface problems early instead of hiding them until they become expensive.

Separating them clearly does the opposite. Trades know they can come forward with a mistake or a struggle and get real support, because that is not the thing being enforced with zero tolerance. What is being enforced with zero tolerance is refusal to participate in the shared system everyone helped build. That distinction is exactly what lets a jobsite be both genuinely disciplined and genuinely safe for the people working on it at the same time.

What Holding This Line Actually Looks Like

None of this works as a slogan. It requires a general contractor to actually know the difference in the moment, and to respond accordingly instead of defaulting to blanket punishment or blanket permissiveness.

When a trade is not participating in huddles, pull plans, or the agreed system, that gets addressed directly, and if it continues, that becomes a contract and staffing decision, not an ongoing complaint. When a trade is participating fully and still runs into a mistake, a failure, or a genuine struggle, that gets met with real help, not punishment. Holding both of these at once, firm on participation and supportive on outcomes, is what actually produces a site that is disciplined, safe, and genuinely respected by the people working there.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams build exactly this distinction into how they lead, holding trades firmly to the system while genuinely supporting them through the mistakes and struggles that come with real work. That combination is what actually earns long term trust from trade partners, not fear of punishment for every misstep.

So here is the challenge. Look at your own project and ask honestly whether you are enforcing participation in the system, or whether you are quietly punishing trades for failures and mistakes instead. If it is the second one, that is exactly where to recalibrate, starting with your very next conversation with a struggling trade partner.

Jason Schroeder said it plainly: “I worry if a trade’s following the system, not if they’re making mistakes or failing.” Hold that line clearly, and you get a site that is both disciplined and genuinely safe for the people on it.

On we go.

FAQ

What should a GC actually do if a trade partner will not participate in huddles or planning sessions?
Address it directly and specifically, rather than treating it as an unavoidable trait of that trade. If direct conversation does not resolve it, recognize that modifying the contract or changing which trade partner is being used is genuinely within a general contractor’s authority. Continuing to tolerate non-participation while complaining about it is a choice, not an unavoidable circumstance.

Why is punishing mistakes the same way as punishing non-participation actually harmful?
Because it removes the distinction between a trade genuinely trying and failing, which deserves support, and a trade refusing to engage with the system at all, which deserves a direct response. Collapsing both into the same punishment discourages people from admitting mistakes or asking for help, since doing so carries the same risk as outright refusing to participate, which ultimately hides problems instead of surfacing them early.

Does being firm about system participation conflict with genuinely caring about the trades on a project?
No, and treating them as opposites is the actual mistake. A clean, safe, organized environment with real participation in shared systems is itself a form of respect for the people working there, since it protects their safety and their time. Genuine warmth toward people and genuine firmness about the system they operate within come from the same underlying respect, rather than existing in tension with each other.

If you want to learn more we have:

Discover Jason’s Expertise:

Why Capital One Saved Our Construction Business?

Posted on August 24, 2026August 24, 2026 by va.jason.almas@gmail.com

Read 16 min

What My Banking Fight Taught Me About Running a Construction Business

Here’s the deal. Nobody teaches contractors that the bank you choose can be the difference between growing your business and watching it stall right when the work is finally there. I learned this the hard way, and I want to walk you through exactly what happened, because if you run a growing construction company, you are probably one large payroll cycle away from hitting the same wall I did.

Where This Actually Started

Years ago, when my wife Kate and I were first married, I was genuinely irresponsible with credit. That part is entirely on me. I let debt climb to around sixty thousand dollars across a handful of cards, starting from an original balance closer to fifteen thousand. One of those cards in particular had a habit of turning a ten dollar late fee into a spiral of interest rate increases and penalties, and I let it compound instead of getting ahead of it.

We eventually learned about debt stacking, the approach popularized by Dave Ramsey, paying off the largest balance first and rolling that payment into the next one. We got out of debt completely and stayed there. The problem was that being debt free is not the same as having good credit. My score sat around six hundred forty even after we had cleaned everything up, simply because we had not built any positive credit history to replace the debt we paid off.

The Bank That Actually Helped Build the Business

One bank was willing to work with us at that stage when nobody else would. A credit building card, used carefully and paid on time, took our credit score from six hundred forty up to eight hundred thirty, and it has hovered around eight hundred five ever since. That single relationship is what eventually let us qualify for enough credit to actually start the business.

Where It Got Genuinely Difficult

Here is where the real lesson for contractors starts. Like most people starting a company, our early banking relationship was with a large, familiar national bank. They were fine for basic credit cards. They were not willing to extend a business line of credit, even a modest fifty thousand dollars, despite our business running four million dollars in revenue with six hundred thousand dollars in accounts receivable and genuinely strong credit backing it up.

That was not a one time no. We were three or four years into the business by the time we applied, with real financials behind us, and the answer stayed the same. Nothing, nothing, nothing.

Solving It the Hard Way

We ended up working with a smaller regional bank, First Fidelity Bank in Phoenix, who was willing to extend a line of credit starting at twenty five thousand dollars, then fifty thousand, then seventy five thousand, based on a proper loan application and the appropriate lien filing. That bank was not strong on credit cards, so we ended up managing two separate banking relationships just to keep both sides of the business functioning, credit cards through the large national bank, and a line of credit through the smaller regional one.

Watch for these signs your current bank does not actually understand construction cash flow:

Your business is denied a line of credit despite strong revenue, real accounts receivable, and a solid credit history
Your bank will not use your accounts receivable as part of your creditworthiness at all
You are managing two or more separate banking relationships just to cover different financial needs

The Point Where the Business Was Actually at Risk

Eventually payroll reached one hundred eighty thousand dollars a month, with revenue climbing toward seven million and beyond. At that scale, a business genuinely needs a real line of credit to bridge the gap between paying crews and collecting on invoices. We were told no again. No line of credit, nothing, despite the numbers behind us being stronger than they had ever been.

That is a genuinely dangerous place for a growing construction company to sit. We were facing an actual choice between turning down new work or risking the business running out of cash at some point during a normal payroll cycle, purely because the banking relationship could not keep pace with legitimate, documented growth.

What Finally Changed Things

A business relationship representative reached out directly, took the time to actually understand the business, and made an offer that initially sounded too good to be true, enough that we spent weeks verifying it was legitimate before moving forward. The bank was willing to use our accounts receivable as real collateral, despite construction sitting in our business name, something other banks had specifically refused to do. The result was a six hundred thousand dollar line of credit at seven and a quarter percent interest, renewing at that same rate, with no penalty for using it only when actually needed.

That relationship did more than solve a cash flow problem. It came with a real customer service team standing behind the account and continued to help build credit over time, on top of the line of credit itself. At the exact moment the business was choosing between turning away work or risking insolvency, that banking relationship is what let us keep going.

Why This Matters Beyond One Company’s Story

None of this is really about praising or criticizing a specific bank for its own sake. It is about a pattern that affects contractors constantly and rarely gets discussed openly. Construction businesses carry a specific cash flow profile, real payroll due on a fixed schedule, real accounts receivable often collected weeks or months later, and plenty of banks are simply not built to underwrite that reality, regardless of how strong the underlying financials actually are.

A contractor turning down profitable work because a bank will not extend reasonable credit is not a business failure. It is a banking relationship failure, and it is worth treating that distinction seriously before assuming the problem sits with your company rather than your bank.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow, and a stable, well capitalized business behind those field teams is just as important to that stability as any schedule or system. A construction company that cannot make payroll because of a banking gap will not have the chance to apply any of the rest of what we teach.

So here is the challenge. If your business has ever been denied a reasonable line of credit despite strong revenue and real accounts receivable, do not assume that answer reflects your company’s actual creditworthiness. Shop that relationship the same way you would shop a major subcontract, and look specifically for a bank willing to underwrite construction cash flow rather than treat it as a red flag.

Jason Schroeder said it plainly, describing the banking relationship that turned things around: “Capital One is like Tony Robbins to me. Literally saved my life, built my business.” Find the banking partner that actually understands your business, and treat that relationship with the same seriousness you give any other system that keeps your company running.

On we go.

FAQ

Why would a bank refuse a line of credit to a business with strong revenue and receivables?
Some banks apply lending criteria that do not account well for construction specific cash flow patterns, particularly the gap between fixed payroll obligations and accounts receivable that may take weeks or months to collect. Even strong revenue and a solid credit score do not guarantee approval if a bank’s underwriting model does not use accounts receivable as collateral or views construction as higher risk regardless of the specific business’s financial strength.

What is debt stacking, and how does it actually work?
Debt stacking, sometimes called the debt snowball method and popularized by Dave Ramsey, involves paying minimum payments on all debts while directing any extra available money toward the single largest balance first. Once that balance is paid off, the payment that was going toward it rolls into the next largest balance, creating a snowball effect that accelerates as each debt gets eliminated.

Why did a low credit score persist even after becoming debt free?
Because a credit score reflects a history of credit use and repayment, not simply the absence of current debt. Paying off debt entirely without maintaining any active, well managed credit accounts can leave a score stagnant or low, since there is no ongoing positive repayment history being reported. A credit building product used carefully and paid on time is often necessary to actively rebuild that history afterward.

If you want to learn more we have:

Discover Jason’s Expertise:

Advanced Work Packaging (AWP)

Posted on August 24, 2026August 24, 2026 by va.jason.almas@gmail.com

Read 23 min

Advanced Work Packaging Done Right: Give the Field the Right Work, Ready, at the Right Time

Advanced Work Packaging should not be complicated. At its best, it is simple. Give the field the right work, in the right sequence, with the right materials, at the right time, with the roadblocks removed before the crew arrives. That is the whole game.

Here is the deal. AWP has a reputation for being a megaproject bureaucracy, buried under acronyms, oversized packages, disconnected planners, and beautiful documentation that still does not help the foreman on Monday morning. That reputation is deserved on a lot of projects, not because the underlying idea is flawed, but because the system got built for the document instead of the crew. AWP was never meant to be paperwork. It was meant to create flow, and the difference between those two outcomes is entirely a matter of execution discipline.

The Pain of a Package That Isn’t Actually Ready

Here is what happens on a project running AWP badly. A crew shows up Monday morning with an Installation Work Package that looks complete on paper. The drawings are attached. The scope is defined. The package has gone through review. And then the crew discovers that half the material listed is not actually on site, or is on site but staged in the wrong location, or the permit required to start work has not been submitted, or a predecessor task that this package depends on is only ninety percent complete rather than fully done.

The package existed. It was documented. It went through the process. And it still failed the crew, because documentation and readiness are not the same thing. A package that lists what materials are needed is not the same as a package that confirms those materials are physically present, staged, and accessible. A package that names a predecessor task is not the same as a package that verifies the predecessor is genuinely complete. The gap between “documented” and “ready” is exactly where AWP breaks down on most projects, and it breaks down invisibly, because the paperwork looks fine right up until the crew is standing there with nothing to do.

The Failure Pattern

The failure pattern is treating package creation as the finish line instead of treating package readiness as the actual deliverable.

Most AWP implementations put enormous energy into the engineering and planning phases. Engineering Work Packages get built with drawings, models, specs, and quantities. Procurement Work Packages get built identifying what needs to be bought and delivered. Construction Work Packages get built dividing the field scope by area and discipline. All of that work is real, necessary, and often done well. Then the system hands off an Installation Work Package to the field and assumes the upstream planning guarantees downstream readiness.

It does not. A package can be planned correctly and still arrive at the crew incomplete, because planning and verification are different activities. Planning determines what should happen. Verification confirms that what should happen actually has happened, in the field, in physical reality, before the crew’s clock starts. Projects that skip the verification step and rely on the planning step alone are the projects where AWP becomes bureaucracy: extensive documentation that never quite translates into a crew starting work without interruption.

They Didn’t Fail the System

When a crew shows up to an incomplete package and loses the morning waiting on missing material or an unresolved predecessor, the instinct is to look at whoever assembled the package. Why didn’t they check? Why wasn’t this caught?

The honest answer is usually that nobody’s job was specifically to verify full kit readiness before the package was released to the field. Engineering did their part. Procurement did their part. Construction planning did their part. Each function completed its own piece and handed it forward, trusting that the next function would catch anything incomplete. Nobody owned the final checkpoint that confirms, physically and specifically, that every element of the package is actually present and ready before a crew is scheduled against it.

That is not a person failing to do their job. That is a system with no assigned owner for the step that matters most. Build that ownership into the process and the failure disappears. Leave it unassigned and the same gap will repeat on every package, regardless of how skilled or careful any individual planner happens to be.

The Path of Construction Drives Everything

Advanced Work Packaging starts with the Path of Construction, the real sequence the work wants to be built in, driven by the physical and logical constraints of the actual build rather than by an arbitrary planning convenience. This is the foundation everything else aligns to. Get the Path of Construction wrong, and every downstream package inherits that error, no matter how well each individual package is documented.

From the Path of Construction, the system aligns through five package types, each answering a specific question. The Engineering Work Package answers what are we building, providing the drawings, model, specifications, and quantities that define the scope. The Procurement Work Package answers what needs to be bought, delivered, and staged, translating design intent into material that physically exists on site. The Construction Work Package answers how the field scope divides by area and discipline, organizing the larger sequence into planning units that make sense for coordination. The Installation Work Package answers what one crew needs to install, safely and completely, sized specifically to a crew’s actual capacity for a defined period of work. And the Commissioning Work Package answers whether the finished system actually works, closing the loop from design intent to verified, functioning system.

Each package type builds on the one before it, and the alignment between them is what makes the whole system coherent. A CWP that does not trace cleanly back to the Path of Construction creates confusion downstream. An IWP that does not trace cleanly back to its CWP creates the same problem at a smaller scale. The alignment is not bureaucratic overhead. It is what keeps every level of the system pointed at the same actual sequence of work.

Full Kit Is the Whole Point

Here is the requirement that separates AWP done right from AWP done as paperwork. The package is only valuable if it is ready. Not mostly ready. Not “we will figure it out in the field” ready. Not “the material is somewhere onsite” ready. Ready means full kit.

Materials physically present and staged at the point of use, not merely ordered or somewhere in a laydown yard. Tools available and positioned for the specific installation task. Information current and accurate, matching field conditions rather than an earlier revision. Access confirmed, meaning the crew can physically get to the work location without obstruction. Permits secured and in hand before the crew arrives, not in process. Predecessors genuinely complete, verified rather than assumed. Roadblocks removed, meaning every known obstacle between the crew and productive work has been cleared in advance.

Every one of those six elements has to be true simultaneously for a package to be genuinely ready. Five out of six is not full kit. It is a package with a gap, and that gap is exactly where the crew loses time, exactly the kind of loss this factory has covered before in staging materials and workface planning. The difference with AWP is scale: a staging gap on a single task costs a crew minutes. A full kit failure on an Installation Work Package can cost a crew an entire morning, because the package was supposed to be the crew’s complete instruction set for the day, and an incomplete instruction set means the crew has nothing productive to fall back on.

Why Pairing AWP With Takt Planning Completes the System

AWP defines what work is packaged and confirms that it is ready. Takt planning defines the rhythm and location that work moves through. Paired together, the system gains something neither one produces alone: work that is not just packaged, but packaged to the beat of production, by location, in the order the field actually needs it.

Without Takt, a well-built AWP system can still produce packages that are individually ready but poorly sequenced against the actual rhythm of the project, arriving too early, too late, or out of step with the crews working adjacent zones. Takt planning gives AWP its cadence, ensuring that full kit packages arrive exactly when the production rhythm calls for them, no earlier and no later. That pairing is what turns AWP from a documentation exercise into a genuine production system, because the packages are not just complete, they are timed.

Signals Your AWP System Has Become Paperwork

Look for these patterns on your current project:

Installation Work Packages are released to the field with material listed as needed but not confirmed as staged and present
Crews regularly discover incomplete predecessors or missing permits after their package has already started
The path from Engineering Work Package through Installation Work Package involves multiple disconnected planners with no single owner verifying alignment
Packages are sized larger than what a single crew can complete in the planned duration, creating ambiguity about what “done” means
Nobody has a specific responsibility for confirming full kit readiness before a package is scheduled to the field

Each of these signals the same underlying gap: documentation exists, but verification does not, and that gap is exactly where AWP degrades into bureaucracy.

Building the Verification Step Into the System

The fix is not more documentation. It is assigning a specific ownership role for full kit verification, someone whose job is to walk through every element, materials, tools, information, access, permits, and predecessors, and confirm each one is physically true before the package is released. That verification should happen close enough to the scheduled work date that conditions have not changed since the check, but early enough that any gap found can still be closed before the crew is scheduled against the package.

This is the same discipline behind make-ready planning and workface planning that this factory has covered before, applied specifically at the packaging level. The principle does not change. The work should meet a clean, prepared, fully ready environment every time it begins, because a crew that starts with a complete package stays in flow, and a crew that starts with a gap spends the day recovering from a failure that upstream planning should have caught. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. Jason Schroeder and the LeanTakt team pair Advanced Work Packaging with Takt planning specifically because packaging without rhythm is paperwork, and rhythm without full kit readiness is a schedule that looks good on paper and fails in the field.

Build One Prepared Package Before You Build a Hundred

Here is your challenge. Take one upcoming Installation Work Package and walk it against all six full kit elements yourself, physically, before it goes to the field. Materials staged. Tools available. Information current. Access confirmed. Permits in hand. Predecessors truly complete. Fix whatever gap you find before the crew is scheduled against it.

Design, make, transport, build. One source of truth. One clear path. One prepared package at a time. That is what separates AWP as a practical field system from AWP as documentation nobody trusts. Start with one package done right, and let the discipline scale from there.

On we go.

FAQ

What is the single biggest reason AWP implementations fail on real projects?
The most common failure is treating package documentation as the deliverable instead of package readiness. A package can be planned, drawn, and specified correctly and still fail the crew if materials, permits, access, or predecessor completion were not physically verified before release. Documentation and readiness are different things, and most failed AWP systems only ever achieved the first one.

How is full kit different from a standard material list on a work package?
A material list identifies what is needed. Full kit confirms that materials are physically present, staged at the point of use, along with tools, current information, confirmed access, secured permits, and verified predecessor completion. Full kit is a verification standard, not a planning document, and it requires someone to physically check field conditions rather than trust that the plan was executed as written.

Who should be responsible for verifying full kit readiness before a package is released?
A specific, assigned owner, distinct from the engineering, procurement, and construction planning functions that build the package. This role’s job is to confirm, close to the scheduled work date, that every full kit element is genuinely true in the field. Without a single owner for this checkpoint, verification tends to fall through the gaps between functions that each assume someone else already checked.

If you want to learn more we have:

Discover Jason’s Expertise:

General Offerings

Company Offerings

Systems

SUBSCRIBE NOW !

Subscribe to our newsletters and stay updated!

Related Books

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

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

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

Related Books

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

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

Related Books

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

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

Calumet "K"

faq

General Training Overview

Superintendent / PM Boot Camp

Takt Production System® Virtual Training

Onsite Takt Simulation

Foreman & Field Engineer Training

Testimonials

Testimonials

agenda

Day 1

Foundations & Macro Planning

day2

Norm Planning & Flow Optimization

day3

Advanced Tools & Comparisons

day4

Buffers, Controls & Finalization

day5

Control Systems & Presentations

faq

UNDERSTANDING THE TRAINING

VALUE AND RESULTS

PLANNING AND SCHEDULING TOPICS

APPLICATION & TEAM ADOPTION

VIRTUAL FORMAT & ACCESSIBILITY

faq

GENERAL FAQS

CURRICULUM & OUTCOMES

LOGISTICS & FORMAT

PRICING & VALUE

SEO-BASED / HIGH-INTENT SEARCH QUESTIONS