More Detail Isn’t Always Better

Posted on September 29, 2026September 29, 2026 by va.jason.almas@gmail.com

Read 17 min

Why Wanting More Detail in Your Schedule Is Usually an Escape

Here’s the deal. A company we support, genuinely committed to Takt and Lean, has one superintendent who has fought the transition every step of the way. Grumpy, closed off, resistant to Takt, resistant to pull planning, resistant to nearly all of it. I actually think that resistance is fine, even healthy, as long as the rest of the team is genuinely on board and moving forward, which in this case they are. What is worth examining is the specific reason he gave for rejecting it, because that reason reveals something important about how a lot of superintendents think about scheduling.

Why He Rejected the Takt Schedule

His stated complaint was simple. I do not like the Takt schedule. I just need the detail. On the surface that sounds like a reasonable preference. It is not accurate, and here is why.

A properly built Takt plan actually contains more detail and more logic than a traditional CPM schedule, just presented far more simply. The real issue was not a lack of detail at all. It was an inability to adjust from a time by deliverable mental model, the format CPM has trained an entire generation of builders to think in, over to a time by location format, which is structurally different and genuinely better, but does require a real mental shift to use comfortably.

Detail Is an Escape

Here is the core idea worth sitting with. Wanting more detail is often an escape. It is an excuse. It is, at its root, an insecurity, and understanding why changes how you should respond the next time someone demands more detail before they will trust a plan.

There is a well known saying, if I had more time, I would have written a shorter letter. I genuinely love that line, because it captures something true about sophistication. Writing something simple, clear, and elegant actually requires more skill than writing something long and dense, not less. The same principle applies directly to scheduling. Genuine sophistication in planning means being able to express a schedule in time by location format at a high level, with the real detail inherent in how the plan is packaged, rather than needing every granular item spelled out visually before anyone can trust it.

Detail Belongs on a Rolling Wave, Not All at Once

There is a second piece to this worth understanding clearly. Detail is supposed to increase as you actually approach a specific phase. That is what pull planning and detailed work packaging are for, adding real, trade informed detail in a rolling wave as each phase gets closer, rather than demanding exhaustive detail for the entire project up front.

People who insist on heavy detail early, without trade input, are usually doing something different than genuine planning. They are letting their own anxiety run unchecked, relying on detail that has not actually been verified as accurate, simply because generating it makes them feel less worried in the moment.

Watch for these signs that a request for more detail is really an anxiety response rather than genuine planning discipline:

Detail requested far in advance of the phase it actually applies to, with no trade partner input yet available.
Detail so granular that the rest of the team can no longer actually read or use the plan.
Detail treated as proof a schedule is correct, without any real verification that it is achievable.

Why More Detail Does Not Actually Solve Anything

Here is the honest problem with piling on detail early. Even once you have it, so what. Having more detail does not mean the plan is right. It does not mean it can actually happen. It just means somebody got the anxiety out of their own head, and that relief does not help anyone else, because the rest of the team usually cannot even parse a schedule buried in that much granularity.

It gets worse from there. Even if that excessive detail happened to be accurate, it still would not matter, because trades have not actually bought into it yet. A schedule only becomes real once it has been verified as genuinely achievable by the people executing it, and no amount of detail generated in isolation, without trade input, can substitute for that verification.

There are really three separate failure points stacked on top of each other here, and each one alone is enough to undermine the value of that extra detail. It might not be accurate. Even if accurate, the rest of the team often cannot read a schedule buried in that much granularity. And even if both accurate and readable, it still has not been verified as achievable by the trades who would actually have to execute it. Detail solves none of those three problems on its own.

Why the Most Detail Obsessed Supers Are Often the Weakest

I want to say something direct here, based on real experience. Some of the least effective superintendents I have worked with were the ones constantly demanding more and more detail. That pattern usually traces back to a specific gap, not a character flaw.

It looks like this. I do not know how to orchestrate this at a high level in rolling waves. I do not know how to coordinate effectively. I do not know how to work collaboratively with trade partners to build genuine buy-in. I do not have a real system installed. So instead, detail gets piled on top of detail, over and over, because generating detail feels productive even when it is not actually solving the underlying gap. Detail becomes the escape hatch for a missing skill set, not evidence of genuine competence.

Where Detail Actually Belongs

None of this means detail itself is bad. If you genuinely need more detail, put it where it actually belongs. Detail it out visually. Detail it in drawings. Detail it on your logistics maps. Those are the places granular information genuinely helps, because they are built to hold that level of specificity without burying the overall plan.

What you should not do is dump a mountain of unverified, trade uninformed detail directly into the schedule itself, because that does not make the schedule more accurate. It just makes it harder for anyone else to actually read and trust.

Building Genuine Confidence Instead of Chasing Detail

None of this is really about one grumpy superintendent. It is about recognizing a pattern that shows up across this industry constantly, mistaking volume of detail for genuine planning competence.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build the real skills that make a high level, time by location plan genuinely trustworthy, rolling wave detailing, collaborative trade buy-in, and real coordination discipline, so nobody on your team needs to escape into unnecessary detail to feel secure about a schedule.

So here is the challenge. The next time someone on your team insists a plan needs more detail before they will trust it, ask a direct follow-up question. Is this detail actually verified with trade input, or is it simply detail for its own sake? That single question tends to reveal whether the request is genuine planning discipline or an anxiety response dressed up as one.

Jason Schroeder said it plainly: “Detail does not mean that it’s right, and it does not mean that it can happen.” Build genuine confidence in your plan instead of chasing detail as a substitute for it.

On we go.

FAQ

Does a Takt plan in time by location format actually contain less detail than a traditional CPM schedule?

No, and this is a common misconception. A well built Takt plan, particularly using dedicated software, typically contains more logic and more genuine detail than a traditional CPM schedule. The difference is that Takt presents that detail at a higher, more readable level, rather than spreading it across an activity list most people cannot mentally parse once it grows past a few hundred items.

Why should detail increase in a rolling wave rather than being fully specified at the start of a project?

Because detail specified too early, before the relevant trade partners have had a chance to provide real input, is essentially an unverified guess, regardless of how granular it looks. Adding detail through pull planning as each phase actually approaches ensures that detail reflects genuine trade input and real conditions, rather than one person’s early assumptions about how the work will actually unfold.

Why does the article connect excessive early detail to insecurity rather than diligence?

Because detail generated without trade input or verification does not actually make a plan more accurate, it simply relieves the discomfort of uncertainty for the person creating it. When that detail cannot be used or trusted by the rest of the team, and has not been confirmed as achievable, it functions more as a coping mechanism for anxiety about the unknown than a genuine planning tool.

If detail does not belong directly in the schedule, where should it actually go?

Detail belongs in supporting documents built to hold it well, such as detailed drawings, visual work packages, and logistics maps. These formats are designed to carry granular information without burying the overall plan, which is exactly what happens when that same level of detail gets forced directly into a schedule meant to communicate flow and sequence at a readable level.

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.

Data, Risk, and Authority

Posted on September 29, 2026September 29, 2026 by va.jason.almas@gmail.com

Read 17 min

Data, Risk, and Authority: How to Actually Resolve a Disagreement in Pre-Construction

Here’s the deal. Somebody recently described a real situation to me. A superintendent had gone through a fresh eyes review during pre-construction, the kind of session where an outside team looks at a plan with genuinely fresh perspective before construction starts. The review team came across as forceful and dismissive of his ideas, wanted things done a different way, and the whole experience left him nervous rather than genuinely collaborative. His question was simple and fair. How much authority should the fresh eyes team actually have over the superintendent when they disagree?

That question deserves a real answer, not a vague appeal to teamwork. Here is the actual hierarchy I use.

If We Have Data, Use the Data

There is a line I genuinely love, even though I recognize it can sound a little sharp if said the wrong way. If we have data, let’s go with data. If all we have is opinions, let’s go with mine. Said with the right tone, that is not an authoritarian power move. It is an honest statement about what should actually break a tie, and data comes first, before anyone’s personal preference, mine included.

In practice, that means when two people disagree during pre-construction, the first move is never simply picking whoever argues more forcefully. It is asking whether a historical reference class exists, whether a real what-if scenario can be modeled, or whether actual research can settle the question. If the data exists, let it decide, regardless of whose idea it happens to support.

This step alone resolves more disagreements than people expect, precisely because it changes what the conversation is actually about. Instead of two people defending their own instincts, the room shifts toward jointly investigating what the evidence actually shows, which tends to defuse the personal tension that makes disagreements feel adversarial in the first place.

If It Is Genuinely Risky, Take the Safer Path

When no clear data exists to settle a disagreement, the next question is risk. If one option carries genuine potential to put the business, the company, or actual people at real risk, that risk should decide the outcome, again regardless of personal preference. A safer option beats a slightly more convenient one every time real risk is on the table.

Watch for these signs a disagreement is actually being resolved by force of personality rather than this hierarchy:

A decision made simply because one person pushed harder or louder in the room.
No attempt to check historical data or model a what-if scenario before settling an argument.
Risk to the business or to people treated as a secondary concern rather than a genuine deciding factor.

Past Data and Risk, Default to the Superintendent and PM

Once you have genuinely checked for data and ruled out significant risk, and a real disagreement still remains, my honest default leans toward letting the superintendent and project manager make the call. That is not because their opinion outranks everyone else’s by default. It is because somebody has to make the decision, and the people accountable for actually running the project are a reasonable default when the choice is otherwise a genuine toss-up.

Notice that this is explicitly a default, not a rule applied automatically in every case. The next distinction below explains exactly when that default should shift toward the broader team instead, which is where this hierarchy actually gets interesting rather than simply restating a standard chain of command.

The What Versus the How

Here is a distinction that changes how this actually plays out in practice, and it comes up constantly in my own thinking. What we are doing on a project is fundamentally a company leadership decision. How we are doing it, the actual means and methods, belongs mainly to the people with boots on the ground, the trade partners actually executing the work.

That distinction matters directly for the fresh eyes scenario that started this whole conversation. If a disagreement is genuinely about means and methods, with no real data available and no significant risk difference between the two approaches, meaning it is close to a coin flip either way, my instinct leans toward letting the team closest to that decision make the call themselves, rather than the superintendent or PM overriding it by default.

Why Letting the Team Decide Actually Matters

That preference is not just about being nice or building consensus for its own sake. It connects directly to a real leadership principle worth taking seriously. Jocko Willink’s laws of combat, built around the extreme ownership framework, make a specific point. If a team made the plan themselves, they genuinely own it, and they can be held properly accountable for how it plays out.

That accountability only holds up if the team actually had real input into the decision in the first place. Override a team’s means and methods call by default, even when data and risk genuinely do not favor either side, and you quietly remove their ownership over the outcome. Then, when something does not go perfectly, holding them fully accountable for a decision they never truly made becomes much harder to justify.

Applying This Back to the Fresh Eyes Scenario

Go back to the original situation. A superintendent felt steamrolled during a fresh eyes review, not genuinely collaborated with. Run that disagreement through this hierarchy honestly, and the fix becomes clear. Start by asking whether real data actually existed to settle whatever the disagreement was about. If it did, that should have decided the outcome regardless of who felt strongly about it. If no data existed, ask whether real risk was genuinely at stake. If it was not, and the disagreement was really about means and methods with the two options roughly equivalent, the superintendent’s team, the people who would actually own executing the plan, deserved real weight in that decision, not a forceful override from reviewers who would not be the ones held accountable for how it went.

A fresh eyes review is genuinely valuable when it surfaces real data or real risk nobody had considered yet. It becomes counterproductive the moment it turns into simply overriding the field team’s judgment on a genuine toss-up decision, because that erodes the very ownership that makes accountability meaningful later.

Building This Hierarchy Into Your Own Team

None of this requires a formal policy document to implement. It requires a shared, genuinely understood order of operations that everyone in a room actually applies consistently, rather than defaulting to whoever argues the loudest or holds the most senior title.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build genuine decision making discipline around data, risk, and authority, so pre-construction reviews and fresh eyes sessions actually build ownership instead of quietly eroding it.

So here is the challenge. The next time a genuine disagreement comes up in pre-construction or during a fresh eyes review, walk through this hierarchy out loud with the room. Is there real data? Is there real risk? And if neither settles it, is this a means and methods question that genuinely belongs to the people who will own executing it? That simple sequence turns a personality contest into an actual decision process everyone can respect afterward.

Jason Schroeder said it plainly: “If we have data, let’s go with data. If all we have is opinions, let’s go with mine.” Said with the right intent, that is not arrogance. It is a genuine commitment to letting evidence, not force of personality, decide.

On we go.

FAQ

Why should data outrank even a senior leader’s strong opinion when resolving a disagreement?

Because personal conviction, no matter how confident, is not the same thing as verified evidence, and a historical reference class or a modeled what-if scenario reflects reality more reliably than anyone’s gut feeling, regardless of their seniority. Prioritizing data over opinion protects a project from decisions driven by whoever argues most forcefully rather than what actually tends to work.

What is the actual difference between a “what” decision and a “how” decision?

A “what” decision covers the overall direction or goal a project is working toward, which generally belongs to company leadership. A “how” decision covers the specific means and methods used to accomplish that goal, which generally belongs to the people actually doing the work, since they carry the practical knowledge and the eventual accountability for how well that method performs.

Why does letting a team make its own means and methods decision matter for accountability later?

Because genuine accountability depends on genuine ownership, and a team that never actually got to make a real decision cannot fairly be held fully responsible for how that decision turned out. Letting the team closest to the work make a genuine toss-up call preserves their ownership over the outcome, which is exactly what makes holding them accountable later fair and meaningful.

When does a fresh eyes review in pre-construction become counterproductive?

It becomes counterproductive when it shifts from genuinely surfacing new data or risk the original team had not considered into simply overriding the field team’s judgment on a decision that was really a toss-up. A fresh eyes review adds real value when it changes the actual inputs to a decision. It causes harm when it just replaces one opinion with another more forceful one.

If you want to learn more we have:

Discover Jason’s Expertise:

Lean Onboarding Series – Cycle Times

Posted on September 29, 2026September 29, 2026 by va.jason.almas@gmail.com

Read 15 min

No Championship Team Runs a Play for the First Time in the Big Game

No football team wins a championship by running a play for the very first time during the big game itself. Championship teams win with plays they have practiced over and over, precisely because that repetition is what reduces their mistakes and sharpens their execution under pressure. The same logic applies directly to construction task durations, and understanding why requires a genuine production principle worth knowing directly: Kingman’s formula.

The Real Pain: The “Ideal” Duration Is Never the Real Duration

The real pain is a common planning mistake: taking an idealized crew working at one hundred percent productivity and using that number as the actual committed task duration. No real crew operates that way, especially not on a task they are encountering for the first time. Planning around that idealized number, rather than a genuinely realistic one, sets a schedule up to miss its own targets from the very start.

The Failure Pattern: Committing to the Optimistic Number Instead of the Realistic One

The failure pattern is promising a task duration based on the best-case scenario, rather than honestly accounting for the real variation and below-ideal productivity every crew genuinely experiences, particularly early in an unfamiliar task. That optimistic commitment feels aggressive and efficient on paper. In practice, it consistently produces schedules that cannot actually be met.

This Isn’t Pessimism, It’s Kingman’s Formula

None of this is about assuming the worst or doubting a crew’s genuine capability. Kingman’s formula is a real, established production principle that accounts mathematically for two specific factors: the real variation a crew will experience, and their actual productivity level, which is rarely, if ever, a full one hundred percent, especially on a task they have not yet fully mastered.

From Four Days to Five and a Half

Here is a concrete example worth understanding directly. A task might look like it should take four days for an ideal four-person crew working at full, one hundred percent productivity. Once real, expected variation gets factored in, honestly, that same task is more realistically closer to four and a half or four and three-quarters days. Once the crew’s actual productivity level gets factored in as well, particularly if this is a newer or less familiar task for them, the honest duration climbs further still, closer to five and a quarter or five and a half days.

That final number, not the original idealized four days, is the genuinely realistic duration worth planning around.

Why It Matters: What You Promise Shapes What You Can Actually Deliver

This matters because of what happens when durations get packaged into a schedule or a Takt wagon. Committing to the optimistic four and a half day estimate, rather than the honest five to five and a half day reality, sets the entire plan up to fail before work even begins, not because the crew performed poorly, but because the original plan was never actually realistic in the first place.

A few signs help reveal when a planned duration has quietly skipped past Kingman’s formula, and they are worth checking honestly:

A task duration was calculated using an idealized crew size and one hundred percent productivity, without any real accounting for variation.
The crew assigned to a task is encountering it for the first time, with no adjustment made for their inevitably lower initial productivity.
Repeated missed durations on similar tasks keep getting treated as isolated incidents rather than a pattern worth genuinely correcting in future planning.

Teach the Framework: Start Realistic, Then Improve

The practical guidance worth adopting directly is this: commit to the honest, realistic duration from the very beginning, then work to gain buffer and genuinely improve from that starting point, rather than beginning with an optimistic number and hoping the crew simply hits it. This mirrors exactly how a football team actually improves: practicing the same play repeatedly, using each repetition specifically to reduce variation and increase productivity, gradually earning back real time through genuine practice rather than assuming that time exists from the very first attempt.

A few practical steps help apply this directly to setting and improving task durations:

Calculate an honest starting duration that accounts for both real variation and a crew’s actual, not idealized, productivity level.
Treat repeated practice of a similar task type as the genuine mechanism for improvement, not a hopeful assumption baked into the first attempt.
Track actual performance against the realistic starting duration, using any real gains as genuine buffer rather than assuming that buffer upfront.

Turning This Into Daily Practice

When planning task durations, honestly account for both real, expected variation and a crew’s actual productivity level, especially for new or unfamiliar work. Treat repeated practice of the same task type as the real mechanism for earning back time and building genuine buffer, the same way a football team improves specific plays through repetition, rather than assuming that improvement will simply happen on its own from the first attempt.

Connecting It Back to Building People, Not Just Projects

None of this happens without leaders willing to plan honestly around real variation and real productivity, rather than defaulting to an idealized, best-case number that sets a crew up to fail before they even begin. Building that realistic planning discipline directly into how durations get set is exactly what allows genuine improvement to happen over time, rather than repeating the same missed commitments project after project.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams build the kind of realistic scheduling discipline that actually holds up under real-world conditions.

The Challenge

So here is the challenge worth carrying into your next scheduling conversation: check whether a planned task duration accounts honestly for real variation and actual crew productivity, or whether it quietly assumes an idealized best case that was never realistic to begin with. As Jason put it plainly, a real task duration is “not just the task, it’s also the variation they experience and the productivity level of the crew.” On we go.

FAQ

What is Kingman’s formula, translated for construction?

It is a production principle stating that a task’s true duration depends not just on the ideal time an ideal crew would need, but also on the real variation that crew will experience and their actual, often below-ideal, productivity level. This produces a more honest, realistic estimate than simply assuming best-case performance.

Why does a task’s “ideal” duration rarely match its real duration?

An idealized duration assumes a crew working at full, one hundred percent productivity with no variation, which rarely reflects real working conditions, especially for a task a crew has not yet fully mastered. Accounting honestly for both variation and actual productivity typically extends the realistic duration well beyond the idealized estimate.

Why does the football team analogy matter for understanding task durations?

Just as a championship team wins by executing plays they have practiced repeatedly, rather than running a brand-new play for the first time in a critical moment, a construction crew improves task performance specifically through repeated practice of similar tasks. Real improvement in cycle time comes from that repetition, not from optimistic assumptions made before the work has even begun.

What happens when a schedule commits to an optimistic duration instead of a realistic one?

The plan tends to miss its own targets, not because the crew performed poorly, but because the original estimate never genuinely accounted for real variation and actual productivity levels. This creates a pattern of missed commitments that gets mistakenly treated as a performance problem rather than a planning one.

How can a team actually improve its task durations over time?

By starting with an honest, realistic duration and then genuinely practicing and repeating similar tasks, a crew can gradually reduce variation and increase productivity, earning back real time as genuine buffer. This approach produces lasting improvement, unlike assuming that buffer exists from the very first attempt at a task.

If you want to learn more we have:

Discover Jason’s Expertise:

Lean Onboarding Series – Bottlenecks

Posted on September 29, 2026September 29, 2026 by va.jason.almas@gmail.com

Read 16 min

Forming a Bridge on Level Three

On one project, an elevated concrete deck sat on level three with nothing underneath it, no level one or level two to support conventional formwork. The crew had to build high-bay formwork towers, laced and braced together to support a deck suspended well above open space, essentially forming something closer to a bridge than a typical floor. Work had been moving smoothly from deck to deck until it hit this one zone, where everything genuinely slowed down, not because anyone was doing anything wrong, but because the nature of that specific scope was simply harder than everything around it.

The Real Pain: Assuming a Slow Trade or Zone Means Someone’s Doing Something Wrong

The real pain is the natural, mistaken assumption that a slow-moving trade or a difficult zone automatically reflects poor performance. In reality, some scopes of work are inherently slower by nature, regardless of how skilled the crew handling them actually is. Complex mechanical systems, with piping, ductwork, hangers, devices, and controls all needing to tie together, tend to move more slowly simply because of how much genuinely has to happen. Taping drywall requires real drying and sanding time no crew can rush past. Specialty flooring often takes considerably longer than something like basic carpet tile. None of this reflects a problem with the people doing the work.

The Failure Pattern: Fixing a Bottleneck Once and Assuming You’re Done

The failure pattern is treating bottleneck-hunting as a single, one-time fix rather than an ongoing, continuous process. Once one bottleneck gets genuinely optimized or resolved, a new one reliably emerges somewhere else. This is not a sign that the original fix failed. It reflects a real, consistent pattern worth understanding directly: every project will have bottlenecks, whether in a trade, a specific zone, or even in the flow of information or materials to the site.

A few common places bottlenecks tend to show up on a construction project are worth naming directly:

Inherently complex trade scopes, like mechanical systems or specialty finishes, that require more time by their very nature.
Specific zones with unusually difficult conditions, like complex formwork or challenging site logistics.
The flow of information or materials reaching the project site, which can bottleneck just as easily as physical work itself.

This Isn’t About Blaming the Slow Trade, It’s About Recognizing Where Real Improvement Lives

None of this is about calling out a trade as bad or incompetent. Even the most skilled, capable crew in the world can still be the bottleneck, simply because of the nature of their specific scope of work. The real purpose of identifying a bottleneck is not assigning blame, it is knowing exactly where to focus genuine improvement effort next.

Not All Bottlenecks Are Bad: The Hot Sauce Bottle

Here is a useful reframe worth understanding directly. Picture a hot sauce bottle and a beer bottle, each with a differently sized neck, deliberately designed that way on purpose. Put a hot sauce bottle’s narrow neck on a beer bottle, and drinking it becomes frustratingly slow. Put a beer bottle’s wider neck on hot sauce, and you get far more than you actually wanted, possibly a mouth full of unexpected heat. Bottlenecks are not inherently bad. They exist to regulate flow appropriately, and the goal is sizing them correctly for what actually needs to move through them, not eliminating every constraint indiscriminately.

Why It Matters: Pushing Harder Doesn’t Widen the Hose

This matters directly because of a simple, physical truth worth carrying into every constrained situation on a project. Picture a garden hose with its spray nozzle only partially open. No amount of additional water pressure behind that nozzle increases how much water actually comes out the other end. The only way to genuinely increase that flow is to open the nozzle itself, widening the actual constraint.

The same logic applies directly to a bottleneck trade or zone. Pushing harder, adding pressure, or throwing more resources at the system around a bottleneck does not speed anything up. Only genuinely optimizing, adding capacity to, or otherwise widening the actual bottleneck itself produces real improvement.

Teach the Framework: The Law of Bottlenecks

A genuine, recognized principle applies here, worth stating plainly: every project will have bottlenecks. Once an identified bottleneck gets optimized, improved, or removed, a new one will reliably emerge to take its place. This means bottleneck-hunting is a continuous, ongoing process, never a single milestone to check off and move past permanently.

The practical response follows directly from this law. Once a bottleneck trade or zone is identified, whether that means speeding up a slow process, adding another crew, or otherwise adjusting its productivity rate, real effort should go toward genuinely widening that specific constraint. Once that bottleneck improves, the next one should be actively sought out immediately, rather than assuming the work of improvement is finished.

A few practical steps help identify and address a genuine bottleneck once it is found, and they are worth naming directly:

Confirm the constraint is genuinely inherent to the scope or zone itself, rather than a symptom of poor preparation or a lack of resources elsewhere.
Focus real effort specifically on widening that bottleneck, additional capacity, faster methods, more crews, rather than simply adding pressure to the surrounding system.
Once that bottleneck improves, immediately begin looking for the next slowest trade, zone, or process, since another one will reliably emerge.

Turning This Into Daily Practice

Build a consistent habit of asking directly, what is our slowest trade, zone, or process right now, rather than assuming last month’s fix solved the problem permanently. When a genuine bottleneck is identified, direct real effort toward widening it specifically, rather than pushing more general pressure, more people, more urgency, onto the system as a whole.

Connecting It Back to Building People, Not Just Projects

None of this happens without leaders willing to treat bottleneck-hunting as a genuine, ongoing discipline rather than a problem to solve once and move past. Building that continuous improvement habit directly into how a project runs is exactly what keeps real progress happening long after the first obvious constraint gets resolved.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams build the kind of ongoing bottleneck identification that drives genuine, sustained improvement.

The Challenge

So here is the challenge worth carrying onto your next project: identify your current slowest trade, zone, or process, focus real effort on widening that specific constraint, and then immediately start looking for the next one. As Jason put it plainly, “The only thing you can do to increase the flow is to open up that nozzle and open up that bottleneck.” On we go.

FAQ

Does being a “bottleneck trade” mean that trade is performing poorly?

No. Some scopes of work, like complex mechanical systems or specialty finishes requiring real drying time, are inherently slower by nature regardless of how skilled the crew handling them is. Identifying a bottleneck is about knowing where to focus improvement effort, not assigning blame to the people doing the work.

Why does fixing one bottleneck just reveal another one?

This reflects a genuine, consistent pattern in how projects function: once one constraint gets optimized or resolved, a new one reliably emerges somewhere else in the process. Bottleneck-hunting is therefore a continuous, ongoing discipline, not a single fix to complete and move past.

Why doesn’t adding more pressure or resources to a bottleneck actually speed it up?

Much like a garden hose with a partially closed nozzle, additional pressure behind a genuine constraint does not increase the flow coming out the other side. Real improvement only comes from directly widening the actual bottleneck itself, whether through added capacity, faster methods, or additional crews.

Are all bottlenecks something that should be eliminated?

Not necessarily. Some constraints exist deliberately to regulate flow appropriately, much like a hot sauce bottle and a beer bottle have differently sized necks on purpose. The goal is sizing a bottleneck correctly for what actually needs to move through it, not eliminating every constraint indiscriminately.

Where besides trades and zones can bottlenecks show up on a construction project?

Bottlenecks can appear in the flow of information or materials reaching the project site, not just in physical trade work or specific zones. Any point where flow slows down relative to the rest of the project deserves the same kind of attention and improvement effort.

If you want to learn more we have:

Discover Jason’s Expertise:

Lean Onboarding Series – Variation

Posted on September 29, 2026September 29, 2026 by va.jason.almas@gmail.com

Read 14 min

Fifteen Things From One Small Decision

Picture a concrete crew about to set forms for a wall. Somewhere along the way, a designer, an owner, or a superintendent decides to change that plan. That single decision sets off a real cascade: the forms have to come back down, tools and materials get hauled back to the laydown yard, the crew gets rerouted to something else entirely, a new set of lift drawings has to get pulled, new supplies and formwork have to be gathered, the crew has to reorient to an unfamiliar task, and the concrete delivery itself has to be canceled or rescheduled.

That is not an exaggerated list. One small change genuinely ripples into at least fifteen distinct downstream effects, and in some cases closer to a hundred.

The Real Pain: Variation Doesn’t Just Cost What It Looks Like

The real pain is that a change which seems small and entirely reasonable in the moment, a minor design tweak, a quick directive from an owner, a last-minute call from a superintendent, actually costs far more than its surface appearance suggests. The visible change is only the first domino. Everything it knocks over afterward rarely gets counted in the moment the decision gets made.

The Failure Pattern: Treating Variation as an Occasional Inconvenience Rather Than the Real Enemy

The failure pattern is treating each individual disruption as a one-off inconvenience to simply work around, rather than recognizing variation itself, regardless of where it originates, as the real, ongoing threat to a project’s actual duration. Waste and variation are the genuine enemy on any construction project, not the people caught in the middle of managing their consequences.

A few common sources of variation are worth actively watching for and preventing, and they are worth naming directly:

Design changes or owner directives introduced after work has already been planned and prepared.
Superintendent-directed changes that stem from a lack of proper preparation rather than genuine necessity.
Unseen roadblocks or defects that could have been caught and prevented earlier in the planning process.

This Isn’t About Perfect Long-Range Planning, It’s About Protecting the Day and Week You’ve Already Set

Here is an important clarification worth stating directly: nobody is expected to nail a plan set months or years in advance down to the exact hour or minute. That standard is unrealistic, and it is not actually the point being made here. The real, far more achievable standard is protecting the weekly work plan, and especially the day plan, once it has genuinely been established and prepared with the team.

Day-Type Compartments

Once a day plan is set collaboratively with foremen, workers and foremen should be able to execute that plan largely undisturbed, living within what is worth calling a day-type compartment. That means design changes, owner directives, or superintendent-driven adjustments should not be intruding into a day that has already been planned and prepared, unless genuinely unavoidable. Protecting that boundary is what actually makes consistent execution possible.

Why It Matters: The Law of Variation

This matters because of a real, recognized production principle worth understanding directly: the more variation a project experiences, the longer its actual duration becomes. This is not simply intuition or a Lean preference, it reflects a genuine pattern observed across production systems broadly. The concrete crew example demonstrates exactly why this holds true in practice: a single change does not cost only its own direct impact, it costs the full ripple of everything that change forces to be redone, rerouted, or rescheduled.

Teach the Framework: Preventing Variation Is the Actual Job

The core reframe worth internalizing directly is this: the primary purpose of foremen and superintendents is to actively prevent variation from happening in the first place, not simply to manage it gracefully once it occurs. Whether variation originates from an external design change, an unseen roadblock that could have been caught earlier, or an outright defect, the actual job is prevention, not damage control after the fact.

A few practical habits help protect an established day plan from unnecessary variation, and they are worth adopting directly:

Treat a genuinely prepared and communicated day plan as something to actively defend, not something easily reopened for convenience.
When a change genuinely must happen, account honestly for its full ripple cost, not just its immediate, visible impact.
Focus real energy on catching roadblocks and potential defects well before they force a disruptive, last-minute change.

Turning This Into Daily Practice

Once a day plan is genuinely set and prepared with the team, actively protect it from unnecessary intrusion rather than treating it as easily revisable. When a change truly cannot be avoided, take the time to genuinely account for its real, full ripple effect rather than treating it as a small, isolated adjustment. That honest accounting is often what reveals just how costly even a seemingly minor decision actually turns out to be.

Connecting It Back to Building People, Not Just Projects

None of this happens without leaders willing to treat variation as the genuine enemy it actually is, rather than an unavoidable cost of doing business to simply manage as it comes. Building that discipline directly into how day and weekly plans get protected is exactly what keeps a project’s real duration from quietly stretching out change by change.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams build the kind of planning discipline that actively prevents variation instead of just reacting to it.

The Challenge

So here is the challenge worth carrying into your next planning conversation: before approving a change to an already-established day or week plan, count the real, full ripple effect it will actually cause, not just its surface-level impact. As Jason put it plainly, “When variation increases, the duration increases.” On we go.

FAQ

Why does a single small change on a project cause so many downstream effects?

A change to an already-planned task, like re-forming a wall, forces a cascade of reversals: materials get hauled back, crews get rerouted, new drawings and supplies get gathered, and deliveries get rescheduled. What looks like one decision in the moment often ripples into fifteen or more distinct consequences.

Does reducing variation mean a project’s entire schedule needs to be planned perfectly months in advance?

No. The realistic standard is protecting the weekly work plan, and especially the day plan, once it has genuinely been established and prepared with the team, not achieving flawless long-range prediction. Long-range plans naturally evolve, but a properly prepared day plan deserves real protection from unnecessary disruption.

What does it mean to live within a “day-type compartment”?

It means that once a day’s plan has been set collaboratively with foremen, workers should be able to execute that plan largely undisturbed by external changes, design revisions, owner directives, or last-minute superintendent adjustments. Protecting that boundary is what actually makes consistent, reliable execution possible.

Why is preventing variation considered more important than managing it well?

Managing variation gracefully still absorbs the full ripple cost of whatever change occurred, while genuinely preventing that variation from happening in the first place avoids the cost entirely. The core responsibility of foremen and superintendents is catching roadblocks and unnecessary changes before they force a disruptive adjustment.

Where does variation typically come from on a construction project?

Common sources include design changes or owner directives introduced after work has already been planned, superintendent-driven adjustments stemming from a lack of preparation, and unseen roadblocks or defects that could have been identified earlier. Actively watching for and addressing these sources ahead of time is central to reducing overall project duration.

If you want to learn more we have:

Discover Jason’s Expertise:

Lean Onboarding Series – Finishing as You Go!

Posted on September 29, 2026September 29, 2026 by va.jason.almas@gmail.com

Read 15 min

Rushing Through Just to Come Back and Do It Again

Why would anyone rush through a building doing work they already know they will have to come back and redo, just to buy themselves extra time to fix it later? It makes no real sense, and yet this exact pattern has been normalized across the industry for decades: push hard, get ahead of schedule, and plan on spending months afterward punching out everything that was never actually finished the first time.

The Real Pain: Production Isn’t Activity, It’s Completion

The real pain starts with a basic misunderstanding of what “production” actually means. It is not a measure of how much effort or activity happened on a project site. It is a measure of how much work actually got finished, completely, without needing a return trip. Effort that requires coming back and doing it again is functionally worthless effort, no matter how busy it looked in the moment.

The Failure Pattern: Optimizing for Your Own Convenience Instead of the Full Zone

The failure pattern shows up clearly in a common, understandable instinct. A fire sprinkler trade partner, for example, might want to run through an entire building installing just the main lines, since that work uses the same tools and the same lift, and switching to valves, branch lines, or drops feels like it slows things down. The reasoning sounds efficient. It is not, because the trades waiting behind that crew need the full scope, mains, valves, branch lines, and drops, completed within each zone before they can properly begin their own work.

This Isn’t About Working Slower, It’s About What Actually Counts as Progress

None of this is an argument for working more slowly or being less efficient. The fastest crews on a real project are never the ones that move through a building quickest in the moment. They are the ones that finish completely as they go, because real speed only counts when a crew never has to come back and do the same work twice.

The Concrete Crew That Left a Mess Behind Them

Here is a vivid, real illustration worth understanding directly. A concrete crew, carpenters and laborers casting walls, columns, and decks, can move through a building fast, and often prioritizes exactly that: cast it, strip it, move to the next pour. Left unaddressed, that speed creates a real mess. Concrete runout spills onto the floor and hardens before anyone deals with it. Chamfered corners on columns go unpatched. Honeycombing and holes in the concrete never get addressed. Formwork, tools, and lumber get left scattered, and the area never gets properly swept.

A genuinely good concrete crew handles all of this differently, and immediately. They strip forms, seal the concrete, patch open holes right then, and chip and scrape wet cement runoff before it has any chance to harden. The difference in outcome is stark: when the first crew leaves a mess behind, the dedicated finishing and patching crew that follows has to spend two to three times their originally budgeted cost simply cleaning up and correcting what should have been finished the first time through.

Why It Matters: A Versatile Crew Beats a Specialized One Moving Through Too Fast

This matters directly for how crews should actually be structured. Rather than optimizing narrowly around one piece of scope using a single set of tools, the better approach is building a more versatile, diverse crew genuinely capable of completing the full scope of work within a zone before moving forward. That crew composition may feel less specialized or efficient from one trade’s narrow perspective. It protects every trade working behind them and keeps the overall project’s flow genuinely intact.

Teach the Framework: The Daily Finish-Check

A specific, concrete standard belongs at the center of this practice: before a crew leaves a zone, has the work actually been quality-controlled to the point that it will not require rework? Have gang boxes, materials, and equipment been fully demobilized from the area? Has the space been swept and cleaned, left genuinely better than it was found? Is the work one hundred percent ready for the next trade to begin? Both the general contractor and every trade partner need to commit to inspecting this daily, and zones provide exactly the right unit of measurement to make that inspection meaningful and consistent.

A few concrete signs help confirm a crew is genuinely finishing as they go rather than rushing ahead to fix things later, and they are worth checking directly:

Materials, tools, and debris are cleared from a zone immediately, rather than left behind for someone else to handle.
Punch list time for a given zone runs no more than about one to two weeks, rather than stretching into months as an accepted cost of doing business.
The trade following behind consistently finds the substrate and conditions they need already genuinely ready, rather than incomplete.

Turning This Into Daily Practice

Treat any extended punch list period, well beyond a week or two per zone, as a genuine warning sign that something went wrong upstream, not as a normal, expected cost of doing construction. Build crews versatile enough to complete a full scope of work within a zone before moving forward, rather than optimizing narrowly for one convenient piece of that scope at the expense of the trades waiting behind them.

Connecting It Back to Building People, Not Just Projects

None of this happens without leaders willing to redefine what real production actually means, prioritizing genuine completion over the appearance of speed and busyness. Building that discipline directly into how every trade approaches their work within a zone is exactly what protects schedule, budget, and the people depending on a properly finished substrate to do their own work well. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams build the kind of finish-as-you-go discipline that eliminates costly, avoidable rework.

The Challenge

So here is the challenge worth carrying onto your next project: before your crew moves to the next zone, ask honestly whether the work is genuinely finished, or whether you are simply planning to come back and fix it later. As Jason put it plainly, “Production is not go through this as fast as I can and then come back and finish it later. Production is how fast can I go through this and finish it while we go.” On we go.

FAQ

Why does “production” mean something different than simply doing a lot of work quickly?

Real production measures how much work actually gets completed without requiring rework, not how much activity or effort happened in a given period. Work that has to be redone later represents wasted effort, regardless of how fast or busy it initially appeared.

Why shouldn’t a trade partner run through an entire building completing only the easiest part of their scope first?

Trades working behind them need the full scope, not just the easiest portion, completed within each zone before they can properly begin their own work. Prioritizing one trade’s convenience over completing the full zone creates roadblocks and delays for everyone working downstream.

What does the concrete crew example teach about finishing as you go?

A crew that immediately strips forms, seals concrete, patches holes, and cleans up runoff before it hardens avoids creating a mess that a separate finishing crew later has to fix at two to three times the original budgeted cost. Finishing completely the first time is dramatically cheaper than rushing ahead and returning to correct it later.

What should a crew confirm before leaving a work zone?

The work should be quality-controlled and unlikely to require rework, materials and equipment should be fully demobilized, the area should be swept and cleaned, and everything should be genuinely ready for the next trade to begin. Both the general contractor and trade partners should inspect zones daily against this standard.

How much punch list time is reasonable for a properly finished zone?

Roughly one to two weeks per zone is a reasonable maximum, and anything significantly beyond that suggests work was not genuinely finished the first time through. Extended punch list periods stretching into months should be treated as a warning sign, not an accepted cost of construction.

If you want to learn more we have:

Discover Jason’s Expertise:

Lean Onboarding Series – Leveling Work

Posted on September 29, 2026September 29, 2026 by va.jason.almas@gmail.com

Read 15 min

Don’t Order Everything in the Store

Imagine feeding a family on Thanksgiving by calling a restaurant and asking them to send over everything currently in the store. That would be absurd. Instead, you would order a meal genuinely portioned to the actual number of people eating. Dividing a construction project into zones deserves that exact same intentional portioning, based on the real amount of work involved, not an arbitrary carve-up by floor or wing simply because it looks like an even split on paper.

The Real Pain: Throwing More at the Problem Doesn’t Create Flow

The real pain comes from a set of common but mistaken instincts. Adding more labor above what a task actually needs does not create flow. Throwing extra money at a struggling area does not create flow. Bringing out more materials than the current moment requires does not create flow either. None of these familiar moves produce the thing they are meant to fix. What actually creates flow is something else entirely: leveling.

The Failure Pattern: Equal Zone Sizes Instead of Equal Zone Work

The failure pattern is dividing a building into zones based on equal square footage, rather than equal work content. A zone packed with dense, complex work crammed into the same footprint as a zone with comparatively light work creates a real imbalance, even though the square footage looks perfectly fair on paper. That imbalance breaks the very rhythm flow depends on.

This Isn’t About Equal Zones, It’s About Equal Work

Here is the key clarification worth understanding directly: zone size can, and often should, vary considerably. What actually needs to stay level is the real amount of work or effort contained within each zone. A smaller zone with dense, complex work and a much larger zone with lighter, simpler work can both be genuinely leveled, as long as they represent roughly the same actual effort and duration to complete.

A few things belong on the list of what should actually be leveled to create real flow, and a few common but mistaken substitutes are worth naming directly:

Level the amount of work density within each zone, not the physical square footage of the zone itself.
Level the crew capability and effort within a sequence of trades, not simply the number of workers assigned.
Never substitute more labor, more money, or more early materials for genuine leveling, since none of these actually solve the underlying imbalance.

The Person Paying in Pennies

Picture a supermarket checkout line where most customers move through in about five minutes each, one after another, a steady, predictable rhythm. Then one customer arrives with a cart’s worth of items, scans everything, and pulls out several thousand pennies to pay. That single transaction turns five minutes into twenty, and everyone behind them simply waits, stuck, while the entire line grinds to a halt.

The fix is not to accept that delay as unavoidable. Either break that transaction into smaller batches, paying with coins across four separate, faster transactions instead of one enormous one, or remove the bottleneck entirely by directing that customer to pay somewhere else. Either way, the line cannot simply absorb that bottleneck and keep flowing normally.

Why It Matters: The Train Only Moves as Fast as the Slowest Trade

This matters because of a simple, familiar truth from traffic: cars on a highway only move as fast as the slowest car ahead of them. A sequence of trades moving through a construction project works exactly the same way. The entire train only moves as fast as its slowest trade, regardless of how efficiently every other trade in that sequence performs.

This is precisely why leveling work within a zone, making sure crew capability and effort are genuinely matched to the actual work required, matters just as much as leveling work density between zones. A single overloaded trade, left unaddressed, will drag down the pace of every trade behind it.

Teach the Framework: The Five Concepts That Actually Create Flow

Real flow rests on five concrete, connected ideas, replacing the false levers of adding more labor, money, or materials. Trades move in a common direction. They stay the same distance apart. They move at the same speed. The amount of work density within each zone stays leveled, even as zone sizes themselves vary based on that density. And crew capability within the sequence of trades stays leveled too, meaning a bottleneck trade gets broken into multiple crews, or otherwise sped up, rather than being allowed to stall everyone behind it.

A few practical questions help confirm whether zones are actually leveled by real work content rather than simply by size, and they are worth checking directly:

Does this zone contain roughly the same amount of actual work and effort as the others, regardless of its physical footprint?
Is any single trade in the sequence consistently running slower than the others, creating a bottleneck the rest of the train has to wait behind?
Could a slow trade be split into multiple smaller crews to match the pace of the rest of the sequence, rather than simply accepting the delay?

Turning This Into Daily Practice

When dividing a project into zones, ask directly about actual work density rather than defaulting to equal square footage out of habit or convenience. Watch closely for any trade consistently running behind the rest of the sequence, and treat that as a genuine bottleneck worth actively addressing, whether by splitting that trade into multiple crews or otherwise adjusting their pace, rather than letting the entire line of trades slow down to match it.

Connecting It Back to Building People, Not Just Projects

None of this happens without leaders willing to plan zones around real work content rather than convenient, equal-looking square footage, and willing to actively address bottleneck trades rather than simply absorbing the delay. Building that discipline directly into how a project gets sequenced is exactly what turns a good schedule on paper into genuine, sustained flow on the ground.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams build zones and sequences leveled by real work content, not just convenient geometry.

The Challenge

So here is the challenge worth carrying into your next zone-planning session: stop measuring zones by square footage alone, and start asking whether the actual work inside each one is genuinely leveled. As Jason put it plainly, “I don’t care about the shape or size of the zones. I care about whether or not we have an equal amount of work zone by zone.” On we go.

FAQ

Why doesn’t adding more labor, money, or materials actually create flow?

These common instincts address the appearance of a problem without addressing its actual cause, which is usually an imbalance in how work is distributed across zones or trades. Real flow comes specifically from leveling, matching direction, distance, speed, and work density, not from simply adding more resources to a struggling area.

Why should zone size vary instead of staying equal?

Zones sized purely by equal square footage can end up with very different amounts of actual work packed into them, creating hidden imbalances even though the sizes look fair on paper. Leveling the actual work density, and allowing zone size to vary accordingly, produces a much more genuinely balanced sequence.

What does the supermarket checkout line analogy teach about leveling trades?

A single slow transaction, like paying with thousands of pennies, can back up an entire line even when every other transaction moves quickly and smoothly. The fix is either breaking that slow transaction into smaller pieces or removing it from the line entirely, the same logic that applies to a bottleneck trade within a construction sequence.

Why does a sequence of trades only move as fast as its slowest trade?

Just as traffic only moves as fast as the slowest car ahead of it, a train of trades moving through zones can only progress as quickly as its most overloaded or understaffed trade allows. Addressing that bottleneck directly, rather than accepting the resulting delay, is essential to maintaining real flow.

What are the five key concepts that actually create flow in construction?

Trades moving in a common direction, staying the same distance apart, moving at the same speed, working within zones that have a leveled amount of actual work density, and maintaining leveled crew capability within the sequence of trades itself. Together, these five concepts replace the mistaken belief that more labor, money, or materials alone can produce real flow.

If you want to learn more we have:

Discover Jason’s Expertise:

Lean Onboarding Series – Smaller Batch Areas

Posted on September 29, 2026September 29, 2026 by va.jason.almas@gmail.com

Read 14 min

The Rule of Thumb That Was Wrong

Early in one superintendent’s career, the standard guidance for breaking a building into zones, sometimes called sequences or, in manufacturing terms, batch areas, was fairly simple: roughly ten thousand square feet for straightforward work like a slab on metal deck, and somewhere between twelve and eighteen thousand square feet for more complex areas. That rule of thumb, widely taught and widely followed, turns out to be genuinely incorrect. There is a more precise, mathematically grounded way to size zones, and it produces meaningfully different, better results.

The Real Pain: Bigger Zones Feel Safer, But Slower Is Slower

The real pain is a natural, understandable preference for larger work zones. More space feels safer, gives a crew more room to maneuver, and creates a comforting sense that the area ahead is genuinely ready before moving into it. That feeling, however reasonable it seems, does not actually correlate with real production speed, and in fact tends to work directly against it.

The Failure Pattern: Confusing Comfort With Productivity

The failure pattern is requesting larger zones because they feel more comfortable and secure, not because they actually produce more completed work faster. That is a genuine confusion between emotional comfort and mathematical reality, and it costs real time on the overall schedule.

This Isn’t Guesswork, It’s a Real Formula

None of this is simply a Lean preference or a matter of opinion. It rests on real, established production science, including a foundational concept from manufacturing and queueing theory known as Little’s Law, long used to help optimize batch sizes and production flow across countless industries. Construction scheduling, particularly Takt planning, has its own direct mathematical relationship that mirrors this same underlying principle.

The Formula: Wagons Plus Zones Minus One, Times Takt Time

Here is the actual formula worth understanding directly: the number of Takt wagons plus the number of Takt zones, minus one, multiplied by the Takt time, equals the overall project duration. Holding the amount of work and total square footage completely constant, adjusting only the number of zones reveals something striking.

Picture a floor with forty thousand square feet, broken into four original zones. Plugging that zone count, along with the packaged work activities and Takt time, into the formula produces a specific overall duration, say, as an illustrative example, two hundred days. Now increase the zone count on that exact same floor, same total work, same square footage, from four zones to six, eight, or ten, meaning each individual zone gets smaller as there are more of them. The formula produces a meaningfully shorter duration each time, potentially bringing that same two hundred days down to one hundred sixty, one hundred forty, or even one hundred twenty.

Why It Matters: Faster Means More Profitable for Everyone

This matters because smaller, properly right-sized zones are not simply an academic exercise, they translate directly into a shorter overall project duration. A shorter duration means more profit, for the trade partner completing the work and for the general contractor running the project. This is a genuinely rare situation where following the actual math benefits every party at the table simultaneously, rather than requiring a trade-off between speed and profitability.

A few things become clear once this formula is actually applied honestly to a real project, and they are worth naming directly:

Reducing zone size while holding total work constant reliably shortens the calculated overall project duration.
This relationship is mathematically consistent, not simply a matter of preference or Lean philosophy.
Larger zones requested purely for comfort or a feeling of security work directly against this mathematical advantage.

Teach the Framework: There Is a Point of Diminishing Returns

An important caveat deserves equal attention here: smaller is not infinitely better. There is a genuine point of diminishing returns where zones become too small to work practically, and pushing size down purely for its own sake stops producing real benefit. The actual goal is right-sized zones, determined deliberately through real collaboration between the general contractor and the last planners, the foremen and lead persons who understand the practical realities of the specific work involved.

Turning This Into Daily Practice

Resist the instinct to request a large work zone purely for the emotional comfort of feeling secure that the area ahead is ready. Instead, build genuine visibility and disciplined tracking of whether the next, smaller zone ahead is actually being prepared, materials staged, prior trades finished, inspections complete. This replaces the emotional comfort of a large buffer area with real, concrete tracking that provides the same peace of mind without sacrificing the schedule advantage that smaller zones genuinely produce.

A few practical steps help apply right-sized zoning without losing the sense of security a larger area once provided:

Establish clear, visible tracking of readiness in the zone immediately ahead, even when it is smaller and closer than teams are used to.
Collaborate directly with the general contractor and last planners to determine the actual right size for a given project, rather than defaulting to old, oversized rules of thumb.
Watch for genuine diminishing returns, recognizing when zones have become impractically small rather than assuming smaller is always strictly better.

Connecting It Back to Building People, Not Just Projects

None of this happens without trade partners and general contractors willing to trust the actual math over old habits and comfortable assumptions. Building that trust, and the disciplined tracking systems that make smaller zones genuinely workable, is exactly what turns a mathematically sound idea into real, measurable schedule improvement.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams right-size zones and batch areas using real, proven production science rather than outdated rules of thumb.

The Challenge

So here is the challenge worth carrying into your next zone-planning conversation: question the instinct to request a larger area purely for comfort, and ask instead what the actual math says about the right size for genuinely faster, more profitable work. As Jason put it plainly, “Smaller sequences, smaller zones, smaller batch sizes will always be faster.” On we go.

FAQ

Why does reducing zone size actually shorten a project’s overall duration?

Using the Takt duration formula, the number of wagons plus the number of zones, minus one, multiplied by Takt time, increasing the zone count while holding total work constant produces a meaningfully shorter calculated duration. This is a mathematical relationship, not simply a Lean preference or opinion.

Why do people naturally prefer larger work zones if smaller ones are actually faster?

Larger zones create a comforting feeling that the area ahead is genuinely ready and provide more physical room to work, which feels safer even though it does not correlate with actual production speed. This preference reflects emotional comfort rather than mathematical reality.

Is there a limit to how small work zones should be made?

Yes. There is a genuine point of diminishing returns where zones become impractically small, so the real goal is right-sized zones determined through collaboration between the general contractor and the last planners, not the smallest possible size purely for its own sake.

How can a trade partner feel confident about readiness without requesting a large buffer zone?

Building genuine, disciplined tracking of whether the next, smaller zone ahead is actually being prepared, materials staged, previous trades finished, provides the same confidence a large buffer area once offered. This replaces emotional comfort with real, concrete visibility into actual readiness.

Why does smaller zone sizing benefit both the trade partner and the general contractor?

A shorter overall project duration, produced by right-sized zones, translates directly into more profit for both parties, since faster completion reduces overall project costs and overhead. This is a case where following the actual math benefits everyone involved rather than requiring a trade-off between speed and profitability.

If you want to learn more we have:

Discover Jason’s Expertise:

Lean Onboarding Series – The Last Planner System

Posted on September 29, 2026September 29, 2026 by va.jason.almas@gmail.com

Read 16 min

Five Tools, One Cascade

The Last Planner System is often described in a single sentence, foremen help plan the sequence, but the real system is a full cascade of connected planning tools, each one feeding directly into the next. Understanding that whole cascade, from the master schedule all the way down to tomorrow’s daily huddle, reveals why the system actually works as well as it does.

The Real Pain: Planning That Never Reaches the People Doing the Work

The real pain shows up when planning stays trapped at a high level, disconnected from the daily reality of the people actually executing it. A master schedule full of milestones means very little to a foreman on site if nothing connects that big-picture plan down to what needs to happen tomorrow. Without a genuine cascade linking those levels together, foremen and lead persons end up reactive by default, managing whatever surfaces each day rather than genuinely prepared for it.

The Failure Pattern: Skipping Straight From Master Schedule to Daily Chaos

The failure pattern is jumping directly from a distant master schedule to daily improvisation, with nothing genuine connecting the two. Without the middle layers, phase planning, a real look-ahead window, a collaboratively built weekly work plan, a project effectively has a destination but no real route for getting there day by day.

This Isn’t Just a Scheduling System, It’s a Culture Shift

The mechanical cascade of tools is only half of what the Last Planner System actually requires. The other half is genuinely cultural: leaders willing to abandon command-and-control thinking and siloed leadership, and instead actually listen to and respect the opinions, planning, and wisdom of the last planners, the foremen and lead persons closest to the real work. Without that cultural shift, even a technically well-built cascade of schedules becomes just another set of documents nobody genuinely trusts or engages with.

Where Foremen Should Actually Spend Their Time

Here is a specific, practical point worth naming directly: foremen and lead persons should spend the majority of their real planning time inside the six-week make-ready look-ahead window specifically, proactively identifying and removing roadblocks well before they ever affect the actual work. This is where genuine leadership happens, not reactively managing whatever crisis appears each morning, but actively looking ahead and clearing the path in advance.

Why It Matters: Not All PPC Targets Are the Same

This matters because of a genuinely important, specific detail worth understanding directly: percent plan complete, the score tracking how many committed activities actually happened on time as planned, carries a different realistic target depending on what system Last Planner sits on top of. Layered onto a traditional CPM schedule, the realistic target sits around eighty to eighty-five percent. Layered onto a genuine Takt plan, the target rises to a full one hundred percent.

That gap reveals something important about the underlying reliability of each approach. A Takt-based system can sustain a dramatically higher standard of commitment reliability than CPM ever reasonably can, precisely because of the structure and discipline built into Takt planning itself. Settling for an eighty percent standard when a project could realistically be running at one hundred percent leaves real, genuine improvement sitting on the table.

Teach the Framework: The Full Cascade Explained

The cascade begins with the master schedule, covering the entire project and establishing its real milestones. From there, phase plans get built using pull planning techniques, bringing in lead persons, foremen, superintendents, and project managers to collaboratively establish the right sequence and duration for a specific phase of work. That collaborative sequencing is exactly what the term “last planners” refers to, the last people in the planning cycle, most often foremen, sometimes lead persons or superintendents, refining the plan based on real, ground-level knowledge.

From the phase plan, information filters into the six-week make-ready look-ahead plan, sometimes run at three, four, five, or even twelve weeks depending on the project, though six weeks remains the most common window. This tool exists specifically to make upcoming work genuinely ready, confirming labor, materials, tools, equipment, and information are actually in place, and surfacing anything not yet ready as a roadblock that needs active removal well in advance.

From there, the weekly work plan captures collaborative commitments from every trade, including the general contractor’s own self-performed work, covering at minimum the coming week, ensuring nobody ends up stacked on top of each other and that the plan is genuinely executable. Finally, the daily huddle brings the foreman and superintendent together to confirm a clear, executable plan for the very next day.

A few things happen consistently throughout the weekly and daily layers of this cascade, and they are worth naming directly:

Roadblocks get identified and removed fanatically at every level, treated as a leading indicator worth constant attention.
Percent plan complete gets tracked honestly, with real root cause analysis on any commitment that was not met.
Corrective action gets taken directly with the team based on what that root cause analysis actually reveals.

Turning This Into Daily Practice

Audit your own project honestly against this full cascade. Does a genuine master schedule exist, connected to real phase plans built through collaborative pull planning, feeding into an actively maintained six-week look-ahead, translated into a real weekly work plan, and confirmed daily through a genuine huddle? Missing any one of these layers leaves a real gap between big-picture planning and what actually happens on site each day.

Make sure foremen and lead persons are genuinely spending real time inside that six-week look-ahead window, proactively hunting for roadblocks rather than only reacting once problems have already surfaced. And track percent plan complete honestly, treating a missed commitment as a genuine opportunity for root cause analysis rather than simply a number to record and move past.

A few signs confirm a project has genuinely built this full cascade rather than skipping straight to daily improvisation, and they are worth checking directly:

Foremen can describe specifically what is coming in the next six weeks, not just what is happening today.
Weekly work plans get built collaboratively with real trade partner input, not handed down as a finished document.
Percent plan complete gets tracked consistently, with real conversations happening about why commitments were or were not met.

Connecting It Back to Building People, Not Just Projects

None of this happens without leaders willing to build the full cascade deliberately, and just as importantly, willing to genuinely listen to and trust the wisdom of the last planners closest to the actual work. Building both halves of this system, the mechanical cascade and the cultural shift, is exactly what turns Last Planner from a scheduling technique into a genuinely different way of running a project.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams build a genuine Last Planner cascade, from master schedule all the way down to daily execution.

The Challenge

So here is the challenge worth carrying onto your next project: check whether your own planning cascade genuinely connects the master schedule all the way down to tomorrow’s daily huddle, and identify which layer is missing if it does not. As Jason put it plainly, real Last Planner means we “listen to and respect the opinions, the planning, and the wisdom” of our last planners. On we go.

FAQ

What are the five main tools in the Last Planner System cascade?

The master schedule establishing overall project milestones, phase plans built through collaborative pull planning, the six-week make-ready look-ahead plan, the weekly work plan capturing collaborative commitments, and the daily huddle confirming tomorrow’s executable plan. Each tool feeds directly into the next, connecting big-picture planning to daily execution.

Who exactly are the “last planners” in this system?

They are the last people in the planning cycle, most often foremen, though sometimes lead persons or superintendents, who bring real, ground-level knowledge to refining the sequence and durations of the work. Their direct involvement is what distinguishes genuine collaborative planning from a schedule simply handed down without real input.

Why does percent plan complete have different targets depending on the scheduling system used?

A Last Planner System built on top of a traditional CPM schedule realistically targets eighty to eighty-five percent commitment reliability, while one built on a genuine Takt plan can realistically target a full one hundred percent. This difference reflects the greater underlying structure and discipline built into Takt planning itself.

Where should foremen and lead persons spend most of their planning time?

The six-week make-ready look-ahead window is where foremen and lead persons should focus the majority of their real planning effort, proactively identifying and removing roadblocks well before they affect the actual work. This shifts leadership from reactive daily problem-solving toward genuine, forward-looking preparation.

Is the Last Planner System just a set of scheduling tools, or something more?

It is both a mechanical cascade of planning deliverables and a genuine cultural shift, requiring leaders to abandon command-and-control thinking and siloed leadership in favor of real collaboration. Without that cultural shift, even a technically complete cascade of schedules rarely produces the trust and engagement the system depends on.

If you want to learn more we have:

Discover Jason’s Expertise:

Lean Onboarding Series – Holding Start Dates

Posted on September 29, 2026September 29, 2026 by va.jason.almas@gmail.com

Read 15 min

The Professor Who Moved Up Your Due Date

Imagine finishing a genuinely difficult school assignment early, due Sunday, but done and submitted by Thursday. Proud of the work, the assignment gets emailed in ahead of schedule. The professor’s response: great, your next assignment now starts Friday and is due next Thursday, since you clearly had time to spare. No time to review notes, no time to rest, no time to actually enjoy having finished early. Just an accelerated deadline as the reward for good work.

Nobody would tolerate a class run that way, and nobody would learn well under those conditions. Yet this exact pattern shows up constantly in construction, when a crew that finishes their zone ahead of schedule gets immediately pushed into the next area with no real time to prepare, regroup, or improve.

The Real Pain: Finishing Early Becomes a Punishment

The real pain is what happens when finishing ahead of schedule stops being something worth celebrating and instead becomes the trigger for more, earlier work with no time to prepare. That pattern teaches a team, quietly but unmistakably, that finishing early is actually a bad thing to let show. It discourages exactly the efficiency and hard work that should be genuinely rewarded.

The Failure Pattern: Running Around Installing Work That’s 90% Finished

The failure pattern is rushing prematurely into the next zone before genuinely finishing, training, and preparing in the current one. This does not actually gain real ground. It simply spreads incomplete, not-quite-finished work across a larger area of the building, creating the appearance of progress without the substance of it.

A few things belong squarely inside that extra buffer time when a crew finishes ahead of schedule, and they are worth naming directly:

Genuinely finishing the current zone completely, rather than leaving it at ninety percent done while moving on.
Organizing gang boxes, tools, and materials, and cleaning up the space thoroughly before moving forward.
Pre-staging materials and refreshing the layout for the next zone, so the actual transition happens smoothly when the time comes.

This Isn’t About Being Slow, It’s About What the Extra Time Is Actually For

None of this discourages hard work or genuine efficiency. A crew that finishes ahead of schedule has earned that extra time fairly. The point is what that time should actually be used for: real preparation, genuine improvement, and thorough completion, not premature advancement that quietly undermines quality and safety in the process.

A Pre-Game Huddle and a Post-Game Reflection

A useful way to think about this extra time comes from football. A team does not simply finish one game and sprint directly into the next one with no pause in between. There is a post-game reflection on what worked and what needs improvement, and a pre-game huddle preparing specifically for what comes next. Buffer time in a construction zone deserves that same treatment, a genuine pause for reflection and preparation, not a signal to immediately barrel forward.

Why It Matters: Buffers Are Everywhere in Nature for a Reason

This matters because buffers show up throughout nature and everyday life for good reason. Trees maintain space between each other. Weeks include a weekend buffer before starting again. Even a heartbeat includes a brief pause between each beat. Nothing functions well without some built-in space to reset, and construction scheduling is no different.

Teach the Framework: What Actually Belongs in the Buffer

The specific, legitimate uses for buffer time are worth naming clearly and completely. Finish the current zone thoroughly, leaving nothing at a partial state. Organize gang boxes and tools, applying real 5S discipline to the space. Reflect genuinely on how the work could be done better next time, and update quality visuals to reflect that learning. Refresh the layout in the next zone, pre-stage materials so they are ready when needed, complete inspections, walk the space as a full team, and train workers on anything that needs reinforcing. All of this is real, valuable work, even though none of it is technically “moving into the next zone.”

A few signs help distinguish a team using buffer time correctly from one rushing ahead prematurely, and they are worth checking honestly:

The current zone is genuinely complete, inspected, and clean, not left at a rough ninety percent while attention shifts elsewhere.
Materials and layout for the next zone are prepared and staged in advance, rather than being figured out on arrival.
The crew has had real time to reflect, train, and improve, rather than moving directly from one task into the next with no pause.

Turning This Into Daily Practice

Default to holding the start date and using any extra time exactly as intended, for genuine finishing, preparation, and improvement. There is one legitimate exception worth naming directly: if a crew and the coordinating trade partners have genuinely completed their real preparation, quality checks, and training, and mutually, willingly agree to move ahead together, that is a reasonable, coordinated choice. It should never become the default, and it should never be something a superintendent pressures or guilts a crew into doing simply because they finished early.

Connecting It Back to Building People, Not Just Projects

None of this happens without leaders willing to protect buffer time as a genuine tool for improvement, rather than treating early completion as an invitation to immediately demand more. Building that discipline into how a project actually runs is exactly what allows crews to keep improving over time, rather than quietly learning to hide how efficient they really are.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams build the kind of scheduling discipline that rewards genuine efficiency instead of accidentally punishing it.

The Challenge

So here is the challenge worth carrying onto your next project: the next time a crew finishes ahead of schedule, resist the urge to immediately push them into the next zone, and let that earned time actually be used for finishing, training, and preparation instead. As Jason put it plainly, “We do not gain anything by running all around the building and installing work that’s 90% finished.” On we go.

FAQ

Why shouldn’t a crew move directly into the next zone as soon as they finish early?

Rushing ahead prematurely tends to leave the current zone incomplete while spreading effort into new areas, creating the appearance of progress without genuinely finishing anything. Using that extra time to fully complete the current zone and prepare for the next one produces far better long-term results.

What should buffer time actually be used for when a crew finishes ahead of schedule?

Genuinely finishing the current zone, organizing tools and materials, reflecting on how the work could improve, updating quality visuals, refreshing the next zone’s layout, pre-staging materials, and training workers all belong in that time. None of this is wasted time, even though it does not look like forward progress in the moment.

Is it ever acceptable for a crew to move ahead of schedule into the next zone?

Yes, but only when the crew and coordinating trade partners have genuinely completed their preparation, quality checks, and training, and mutually agree to move forward together. This should remain a deliberate, coordinated exception, never a default expectation or something a crew feels pressured into.

Why does pushing a crew into more work immediately after they finish early discourage efficiency?

When finishing ahead of schedule simply triggers more, earlier work with no time to prepare or rest, teams quickly learn that efficiency gets punished rather than rewarded. This creates a strong incentive to hide genuine progress rather than share it openly.

How does the football team analogy apply to construction scheduling?

Just as a football team uses time between games for reflection and preparation rather than moving directly from one game into the next, a construction crew benefits from using buffer time to reflect, train, and prepare rather than immediately advancing into new work. This pause is what allows genuine, sustained improvement over time.

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