Elevating Construction Senior Superintendents – Part 4

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

Read 14 min

Are You Multiplying Your Team, Or Diminishing It?

Every team eventually reflects the kind of leader standing over it. A leader can multiply that team’s intelligence and capability, or quietly diminish it, and the choice belongs entirely to the person at the top, whether they realize they are making it or not every single day.

Where Good Intentions Quietly Diminish A Team

A leader steps in to fix a problem, makes every decision personally, and keeps a close eye on everything happening below them, genuinely believing this is what responsible leadership actually looks like. The team starts feeling smaller under that attention instead of bigger and more capable. Energy drains out of the room slowly over time. People start waiting to be told what to do instead of figuring it out themselves, and the leader never quite connects their own behavior to that change happening right in front of them.

Confusing Control With Capability

The failure pattern is assuming a team needs constant oversight to actually get anything right, when the opposite is usually closer to the truth. A leader who believes people cannot figure things out without them will build a team that genuinely cannot, not because the people lack ability, but because they have never been given the room to use it. Treating people as incapable tends to make them incapable over time, regardless of how talented they actually were to begin with.

The System Failed Them, They Didn’t Fail The System

The system failed them, they did not fail the system. Most leaders learned to lead by watching other leaders, and if the only model they ever saw was someone who hoarded decisions and stepped in to save the day, that pattern gets repeated without anyone consciously choosing it. Nobody sits leaders down and explains that there are two fundamentally different styles available, one that diminishes a team and one that multiplies it.

Two Very Different Bosses, Two Very Different Careers

One honest comparison shows exactly what this distinction feels like from the inside, living through both extremes within the same career. Working under a leader who blocked nearly every decision, refused to let anything move forward without personal approval, and blamed others for the resulting delays, produced a genuine breaking point, eventually leading to leaving that role entirely rather than continuing to absorb the frustration. What followed was an unexpected surge of accomplishment once free of that environment, proof that the earlier struggle had far less to do with personal capability than it seemed at the time it was happening. A completely different experience came from a leader who, in the middle of a tense meeting full of pointed criticism from senior peers, simply said that the plan and the person behind it deserved trust rather than second guessing in front of everyone present. That single moment of public confidence produced a level of motivation and effort that no amount of pressure or oversight ever could have matched on its own.

Why This Distinction Matters

This matters because a concept popularized in the leadership book Multipliers by author Liz Wiseman captures something worth taking seriously for anyone leading a team. Diminishing leaders assume intelligence is rare and that people cannot succeed without their constant involvement, which quietly shrinks a team’s actual capability over time without anyone intending it. Multiplying leaders assume intelligence is common and simply needs the right conditions to show up, which tends to draw out far more capability than anyone realized a team actually had all along. The exact same group of people can perform dramatically differently depending entirely on which kind of leader happens to be standing over them at any given moment.

A Team Also Needs A Real Goal Worth Chasing

Even a team led by a genuine multiplier still needs something concrete to actually chase, not just good intentions and careful preparation. One company had done everything right in preparation, building a real production plan, a constructability review, and a fresh eyes meeting before a two hundred and forty million dollar project ever broke ground. Despite all that preparation, the team fell eight weeks behind almost immediately, having grown quietly complacent, assuming good preparation alone guaranteed a good outcome without anything else required. Introducing one clear, urgent milestone around the foundations changed everything about how the team actually operated day to day. The team rallied hard around that single target, recovered the lost time, and ultimately finished on time, under budget, with a genuinely satisfied client at the end of it all. Preparation alone was never going to be enough without something specific and urgent enough to actually pull the team forward together.

Signs You Might Be Diminishing Your Team

Watch for these patterns before assuming your team simply lacks capability.

You make most decisions personally instead of trusting others to
You step in to fix problems before anyone else gets the chance
People wait for direction instead of acting on their own judgment
Mistakes get blamed on individuals instead of examined as a team

Connect To Mission

None of this means lowering standards or stepping back from real accountability. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. It means recognizing that a team’s actual capability often reflects the kind of leadership placed over it, far more than the raw talent sitting inside it.

Ways To Multiply Your Team Instead

Use these to shift from diminishing a team toward genuinely multiplying it.

Assume people are capable before assuming they need rescuing
Publicly back a plan and the person behind it under real pressure
Give the team a specific, urgent goal, not just a general direction
Ask what happened as a team instead of who is to blame

A Challenge For Every Leader Building A Team

Here is the challenge this week. Notice one moment where you stepped in to control or fix something a capable team member could have handled themselves, and resist that urge the next time it happens. As has been said plainly, diminishers say people will never figure it out without them, while multipliers say people are smart and will figure it out through good coaching.

On we go.

Frequently Asked Questions

What is the difference between a multiplier and a diminisher as a leader? A diminisher assumes people cannot succeed without constant personal oversight, which shrinks a team’s actual capability over time, while a multiplier assumes people are capable and simply need the right support, which draws out far more capability than expected.

Why does a good plan alone sometimes fail to keep a team motivated? Thorough preparation can create a false sense of security that leads to complacency, since a team may assume good planning alone guarantees a good outcome without a specific, urgent goal actually pulling their effort forward.

What does a strenuous performance goal actually look like in construction? It looks like a specific, urgent milestone, such as a foundation completion date, that gives a team something concrete and immediate to rally around, rather than a vague, general sense of the overall project timeline.

How can you tell if you are diminishing your own team without realizing it? Watching for patterns like making most decisions personally, stepping in to fix problems before anyone else can, and blaming individuals instead of examining situations as a team are all reliable signs worth paying attention to.

Why do talented teams sometimes still need an external goal to perform their best? Even highly capable, well prepared teams can drift into complacency without a specific target to chase, since preparation alone does not create the urgency and focus that a real, strenuous goal provides.

If you want to learn more we have:

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

Discover Jason’s Expertise:

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

The Costs of Material Handling, Feat. John Coffman

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

Read 14 min

Why Material Handling Is The Cost Nobody Tracks

Material handling will eat up a budget faster than overtime and faster than bad crew sizes, and it does it as an invisible cost nobody is actually tracking on most projects. Most teams plan the work itself in careful detail while leaving how materials actually get there almost entirely to chance and good luck.

Where A Careful Plan Still Leaves Money On The Table

A team breaks an activity down into individual tasks, counts every part and piece involved, and calculates a precise duration for the work itself down to the minute. None of that detailed planning touches the actual cost of getting materials to the right place at the right time before the work can even begin. By the time anyone notices money disappearing, material handling has already quietly consumed a huge share of the budget nobody assigned to it in the first place.

Folding A Real Cost Into Something Invisible

The failure pattern is letting material handling costs get absorbed into general unit pricing instead of tracking them as their own real category. Once a cost disappears into a broader number, nobody can actually see it, nobody improves it, and it just keeps quietly repeating on the next project and the one after that. A cost that cannot be seen cannot be managed, no matter how much attention gets paid to everything else on a job.

The System Failed Them, They Didn’t Fail The System

The system failed them, they did not fail the system. Detailed activity planning methods rarely include material handling as a real category worth measuring on its own, so it feels natural to plan the work thoroughly while leaving delivery and storage logistics as an afterthought. Without a deliberate habit of planning for material handling specifically, even a genuinely careful team ends up losing real money to a cost they never saw coming.

A Truckload Of Plywood That Moved All Day

One honest story shows exactly what this invisible cost actually looks like in action. A mentor once set up a time lapse camera on a project for an entire day, then sat down afterward to review the footage together. A truckload of plywood had been unloaded in one spot, and by the end of the day, that same plywood had been moved repeatedly across the site before finally reaching the place it actually needed to be used. Nobody had planned where that delivery should actually land. The real cost of that oversight was not the plywood itself. It was every single unnecessary move it took before the material finally reached the formwork it was meant for.

Why This Distinction Matters

This matters because material handling costs can range anywhere from twenty five percent to as much as a full doubling of an activity’s anticipated cost, depending entirely on how well or badly that handling gets managed. That range is far too large to leave to chance or fold quietly into a generic unit price. Planning where materials will land, how they will move, and who is responsible for keeping that area organized deserves the same real attention given to the actual construction work itself.

A Laydown Area That Revealed Everything

A second story shows how visible this cost actually is once someone knows where to look for it. Walking a badly organized third floor laydown area one morning revealed storage completely ignored by every trade involved, and the response was immediate and direct, a clear deadline to fix it and a clear consequence if it ever happened again. It never happened again. A very different project told the opposite story. Walking a genuinely complex, oddly angled building with an intern one day revealed a laydown area so well organized, both inside and outside the building footprint, that it became possible to relax about nearly everything else on that project. A superintendent who manages material handling at that level of detail is very likely managing everything else with the same care.

The Real Driver Behind Crew Productivity

A related insight explains why this matters even more than it first appears to. Research comparing crew productivity found that top performing crews were roughly four times as productive as the lowest performing ones, but that gap showed up almost entirely during the moments crews were actually working, not during the moments they were searching for materials, waiting on information, or moving something that should never have needed to move at all. Give any crew, even a below average one, real materials, real information, and a real plan, and production becomes possible. Take those things away, and even a talented crew cannot outrun the resulting waste.

Signs Material Handling Is Quietly Costing You

Watch for these signs before material handling silently drains a real budget.

Materials get moved multiple times before actually being installed
Laydown areas look disorganized with no clear ownership assigned
Nobody can say what material handling actually costs on this project
Workers spend real time searching instead of actually building

Connect To Mission

None of this means material handling deserves more attention than the actual construction work itself. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. It means recognizing that an invisible cost is still a real cost, and planning for it deliberately protects a budget that would otherwise quietly disappear.

Ways To Plan For Material Handling Before It Costs You

Use these before the next delivery shows up on your project.

Decide exactly where a delivery will land before it actually arrives
Assign clear ownership for every laydown area and storage location
Track material handling as its own real cost, not a hidden add on
Walk laydown areas regularly with the same scrutiny given to the work

A Challenge For Every Superintendent

Here is the challenge this week. Walk one laydown area on your project and honestly assess whether materials are moving efficiently or being handled again and again unnecessarily. As has been said plainly, if we can get out of the way and provide everything that people need, they will set the world on fire, and that starts with making sure the materials are actually where they need to be.

On we go.

Frequently Asked Questions

Why is material handling considered an invisible cost on most projects? Material handling costs typically get folded into general unit pricing instead of being tracked separately, which means the cost exists and grows quietly without anyone actually seeing it or working to improve it over time.

What can a poorly planned material delivery actually cost a project? Depending on how well or badly it gets managed, material handling can add anywhere from twenty five percent to as much as a full doubling of an activity’s anticipated cost, making it one of the largest hidden expenses on many projects.

Why does a well organized laydown area say so much about a project’s overall health? A superintendent who manages material storage and handling with real precision is very likely applying that same level of care to layout, quality, and every other detail across the entire project, which makes a laydown area a genuine leading indicator worth trusting.

What is the real difference between low and high performing crews? The productivity gap between crews shows up almost entirely in the moments they are actually working, which means giving any crew real materials, real information, and a real plan often matters more than raw individual skill differences.

What is a simple way to start tracking material handling costs? Deciding exactly where deliveries will land before they arrive, assigning clear ownership for laydown areas, and tracking material handling as its own line item instead of folding it into general costs are all simple, practical starting points.

If you want to learn more we have:

Discover Jason’s Expertise:

Elevating Construction Senior Superintendents – Part 6

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

Read 13 min

Why Courage Is What Actually Turns A Plan Into A Result

Knowledge is not power. Action is power. Every senior leader eventually discovers that having the right answer means very little without the courage to actually hold the line on it when real pressure finally arrives and tests it.

Where Good Plans Quietly Get Abandoned Under Pressure

A leader builds a genuinely sound plan, a steady pace, a clean and organized site, a realistic schedule built on real milestones. Outside pressure arrives anyway, an anxious client, a nervous executive, a corporate visitor convinced that adding people or rushing a phase will fix everything that appears to be going wrong. Caving to that pressure feels safer in the moment than holding firm, even when the original plan was actually the better choice all along and would have worked exactly as intended.

Confusing Compliance With Being A Team Player

The failure pattern is treating pushback from authority as something to avoid at nearly any cost, mistaking that avoidance for being cooperative or easy to work with. Abandoning a sound plan because someone senior got nervous rarely produces a better outcome. It usually just replaces a stable, working approach with a reactive one, right at the moment stability actually mattered most.

The System Failed Them, They Didn’t Fail The System

The system failed them, they did not fail the system. Nobody explicitly teaches leaders that courage is a specific, learnable habit that has to be deliberately developed, so it feels natural to equate pushing back on pressure with being difficult, rather than recognizing it as one of the most valuable things a leader can actually do for a project.

Holding The Line Against A Caravan Of Nervous Executives

One real story shows exactly what courage looks like under sustained, repeated pressure over time. Closing out a project where roughly a third of the scope had been altered through change orders, corporate leadership grew increasingly anxious about the finish date, repeatedly pushing to add manpower and increase crew sizes outside of the clean, stable approach that had gotten the project that far already. Nearly every month, a group from corporate arrived to review progress and push for exactly that same reactive fix. Nearly every month, the answer stayed the same, holding steady with consistent crew levels, a clean and organized site, and a smooth, even pace all the way to the finish line. The project finished exactly on schedule, down to the day, without ever sacrificing safety, cleanliness, or the stability that made the whole plan work in the first place.

Why This Distinction Matters

This matters because none of the other habits, planning, clarity, urgency, or productivity, actually matter without the courage to defend them once they get genuinely tested. Zero tolerance safety standards, real cleanliness, and holding a genuine schedule milestone all require someone willing to hold that line even when doing so feels uncomfortable or unpopular in the moment it counts most. A leader who folds under pressure quietly teaches an entire project that the plan was never actually serious to begin with, no matter how well it was written down on paper.

Urgency Requires The Same Kind Of Courage

A related story shows how courage also applies to recognizing urgency early, well before anyone else on the team actually sees it coming. While planning a complex laboratory project, it became clear early on that final commissioning requirements meant key systems needed to be fully operational roughly eight weeks ahead of where a normal schedule would have naturally placed them. That recognition meant driving early procurement and infrastructure work from day one, not rushing later once the deadline loomed, but deliberately front loading effort based on a milestone most people would not have noticed yet at that early stage. A neighboring project of similar size, led without that same early urgency, finished twelve months behind schedule as a direct result. Seeing the real timeline clearly, and having the courage to act on it early, made the entire difference between the two outcomes.

Where Courage Actually Shows Up On A Project

Keep these in mind, since each one requires real courage to actually hold.

Maintaining a steady, stable pace under pressure to rush
Enforcing genuine zero tolerance safety standards consistently
Holding a real schedule milestone instead of quietly letting it slide
Protecting clean, organized site standards when it feels inconvenient

Connect To Mission

None of this means ignoring genuine feedback or refusing to ever adjust a plan that actually needs changing. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. It means having the courage to defend a genuinely sound approach, even when pressure from above suggests abandoning it would be easier in the short term for everyone involved.

Questions To Ask Before You Cave To Outside Pressure

Use these the next time pressure tempts you to abandon a plan that is actually working.

Is this plan actually failing, or is someone simply getting nervous
What would change if I held the line for one more month
Am I protecting the team’s stability, or trading it for temporary comfort
Have I clearly shown the data behind why this approach is working

A Challenge For Every Senior Leader

Here is the challenge this week. Identify one place where outside pressure is currently tempting you to abandon a plan you genuinely believe in, and find the courage to hold your ground on it for one more cycle. As has been said plainly, knowledge is not power, action is power, and courage is what actually turns the right answer into a finished project instead of just a good idea on paper.

On we go.

Frequently Asked Questions

Why is courage considered the capstone habit that makes everything else actually work? Planning, clarity, and urgency only matter if a leader is willing to defend them when they get tested by real pressure, which is why courage functions as the habit that actually converts good intentions into a finished result.

What does holding the line under pressure actually look like in practice? It looks like maintaining a steady, stable approach, consistent crew levels, and genuine safety and cleanliness standards even when nervous stakeholders are pushing to rush the schedule or add unplanned manpower to fix a problem that stability was already solving.

Why does urgency matter even when a project still looks like it has plenty of time left? Real milestones like commissioning requirements often demand action many weeks before a surface level schedule would suggest, so recognizing that true timeline early, and acting on it with courage, prevents a much larger delay from surfacing later.

What is the difference between pushing a team and driving a team? Pushing tends to mean rushing and cutting corners under pressure, while driving means moving with real urgency toward a milestone while still protecting safety, cleanliness, and a steady, sustainable pace for the people doing the work.

Why can adding manpower under pressure sometimes make a project worse, not better? Adding people to a stable, well running process can disrupt the very rhythm and organization that was actually producing results, which is why holding a proven approach steady often outperforms a reactive scramble driven by outside anxiety.

If you want to learn more we have:

Discover Jason’s Expertise:

Elevating Construction Senior Superintendents – Part 3

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

Read 14 min

Why Trust Has To Come Before Everything Else On Your Team

Every team exists somewhere on a spectrum, from a loose group that simply shares information to a genuinely high performing team that holds itself mutually accountable without anyone forcing it. The difference between those two extremes almost always comes down to one word, trust, more than talent, effort, or even good intentions.

Where Leaders Skip Straight To Demanding Accountability

A team struggles to hit its goals, and the natural response is to demand more accountability from everyone involved right away, sometimes in the very next meeting. That demand rarely produces the result anyone actually wants when it arrives too early in the process. Real accountability sits near the end of a much longer sequence, and trying to force it before the earlier steps are in place tends to produce resentment instead of results worth celebrating.

Confusing The Goal With The Starting Point

The failure pattern is treating accountability as something a leader can simply request on its own, disconnected from everything that has to happen first. A team cannot hold itself accountable to goals it never actually agreed on together. It cannot set real goals together without first working through honest conflict about what those goals should be. And it cannot engage in honest conflict without a real foundation of trust underneath the entire team.

The System Failed Them, They Didn’t Fail The System

The system failed them, they did not fail the system. Nobody explicitly teaches leaders that team behaviors follow a specific, non negotiable order, so it feels natural to demand the visible result, accountability and performance, without first doing the harder, less visible work of building genuine trust among the people expected to deliver it.

Sharing Calendars Instead Of Hoarding Control

One honest story shows what building real trust actually looks like in practice, even when it feels uncomfortable at first. Early in one leader’s career, keeping a personal calendar private felt like a way to preserve control, quietly avoiding accountability for how time was actually being spent day to day. Choosing instead to share calendars openly with the team produced better decisions, more genuine support, and stronger overall performance almost immediately after the change was made. A related practice involves posting a short, personal summary of each team member’s goals somewhere visible, turning private ambitions into something the whole team could actually help each other achieve together over time.

Why This Distinction Matters

This matters because a team that has never built real trust will not risk honest conflict, and a team that avoids honest conflict will never actually commit to shared goals, no matter how clearly those goals get written down on paper. A commonly cited comparison makes the point well. Elite teams tasked with extremely high stakes work often prefer a moderately skilled member they can trust completely over a highly skilled member they cannot, because low trust quietly poisons everything a team is trying to accomplish together, no matter how talented any single person happens to be.

The Five Behaviors In Order

Trust comes first, built through real transparency, shared information, and a genuine willingness to be open about strengths, weaknesses, and mistakes that a team member might otherwise hide. Healthy conflict comes second, since a team that trusts each other can finally have honest, sometimes uncomfortable conversations about what actually needs to change without anyone taking it personally. Shared goals come third, built through the kind of real conflict that surfaces genuine agreement instead of quiet, unspoken disagreement everyone privately holds onto. Mutual accountability comes fourth, only possible once a team has actually committed to goals they built together rather than goals handed down from above. And real performance comes fifth, arriving as the natural result of everything that came before it, not as something a leader can simply demand on its own without doing the earlier work first.

Accountability Changes Everything Once It Finally Arrives

One real example shows exactly what happens once a team crosses into genuine accountability for the first time. In an intensive, multi day training camp where participants build a real structure together under serious time pressure, teams typically struggle at first, working in silos, getting distracted, and slowly becoming demoralized as the deadline approaches. Every single time, the teams that eventually succeed are the ones that start holding each other accountable, calling out a bad attitude, stepping in to help with a struggling task, checking each other’s work without being asked to. The teams that never reach that point consistently miss their deadline, while the teams that do reach it are transformed almost overnight into something genuinely different.

Ways To Build Real Trust On Your Team

Keep these close, since trust is the foundation everything else depends on.

Share calendars and information openly instead of guarding them
Post personal goals somewhere visible so the team can help achieve them
Choose open, shared spaces over closed doors whenever possible
Avoid language that emphasizes hierarchy over genuine partnership

Connect To Mission

None of this means accountability does not matter, because it absolutely does. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. It means building the trust, conflict, and shared goals that actually make real accountability possible, instead of demanding it before a team is genuinely ready to deliver it.

Questions To Ask About Your Own Team’s Trust

Use these to check where your team actually sits in the sequence.

Do team members share real information openly, or keep things guarded
Does honest conflict happen in meetings, or only in private afterward
Were current goals actually built together, or simply handed down
Would team members call each other out before a leader has to step in

A Challenge For Every Leader Building A Team

Here is the challenge this week. Pick one way to build more genuine trust on your team, sharing a calendar, posting a real goal, opening up a closed door, and follow through on it deliberately. As has been said plainly, the problem is not that there are problems, the problem is expecting otherwise, and trust is what finally lets a team bring its real problems to the surface together.

On we go.

Frequently Asked Questions

What are the five behaviors of a real team, in the correct order? The five behaviors are trust, healthy conflict, shared goals, mutual accountability, and performance, and each one depends directly on the behavior that comes before it in that same fixed sequence, without exception.

Why does trust have to come before accountability on any real team? A team cannot hold itself accountable to goals it never genuinely agreed on together, and it cannot agree on real goals without honest conflict, which only happens once real trust has already been established among the people actually involved.

What is a simple way to build real trust on a construction team? Sharing calendars, posting personal goals somewhere visible, and choosing open communication over closed doors and guarded information are all simple, practical ways to build genuine trust over time.

Why might a moderately skilled team member with high trust be more valuable than a highly skilled member with low trust? Low trust quietly undermines everything a team tries to accomplish together, since it prevents open communication and honest conflict, while a trusted team member, even a moderately skilled one, strengthens the entire team’s ability to function well.

What does real accountability actually look like once a team finally has it? It looks like team members calling out a bad attitude, stepping in to help someone struggling, and checking each other’s work without being asked, all happening naturally instead of only when a leader intervenes directly.

If you want to learn more we have:

Discover Jason’s Expertise:

Elevating Construction Senior Superintendents – Part 2

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

Read 13 min

Why Every Project Needs A Captain, Not A Delegator

The project is a reflection of everything the builder has in his or her mind. Picture your project as a ship, with yourself standing at the helm as its captain, and the entire role of a senior leader suddenly becomes much easier to understand and actually apply.

Where Busy Gets Confused With In Command

A leader delegates one responsibility after another, staying constantly busy with paperwork, meetings, and lower level tasks that feel productive in the moment they are completed. The ship still needs someone actually steering it, watching the horizon, and anticipating what comes next before it becomes a real problem. Staying busy and actually captaining a project turn out to be two very different things, and only one of them keeps the whole operation moving in the right direction.

Confusing Delegation With Abdication

The failure pattern is delegating away responsibilities that were never actually meant to be delegated in the first place. Training the crew, stocking the project, and staying vigilant about what could go wrong all belong to the person at the helm. Handing those specific responsibilities to someone else, or simply assuming they will handle themselves, is not delegation. It is quietly abandoning the one post that cannot be left unattended.

The System Failed Them, They Didn’t Fail The System

The system failed them, they did not fail the system. Nobody explicitly teaches leaders the difference between staying busy and actually captaining a project, so it feels natural to equate a full calendar with genuine control over what is actually happening. Without that distinction, real vigilance quietly gets replaced by motion that looks productive but never actually steers anything.

A Concrete Crew That Needed Training, Not Blame

One real story shows what captaining actually looks like in practice, especially under real pressure. A concrete crew, along with the foremen overseeing columns, walls, and decks, was simply not performing well, and the company had never properly trained them for their specific roles on this project. Rather than complaining, sending notices, or waiting for someone else to fix it, the leader in charge scheduled a daily hour long training session before the normal huddle so the foremen could actually build the skills their roles required to succeed. The concrete work finished within hours of its original target date, on a site with genuinely difficult conditions, because the team was finally equipped to succeed instead of simply blamed for falling short of expectations nobody had actually prepared them to meet.

Why This Distinction Matters

This matters because a captain who assumes a crew will simply arrive fully trained is setting an entire project up for exactly the kind of failure that gets blamed on everyone except the person actually responsible for it in the first place. Training, logistics, and vigilance cannot be outsourced to hope or good intentions alone. They belong to whoever is actually standing at the helm of the project, and treating them as someone else’s job is how a functioning ship quietly drifts into real trouble without anyone noticing until it is too late to easily fix.

Knowing Where You Are Actually Going

A captain also has to know the mission itself, not just how to keep the crew busy along the way. One project involved a below grade space covered by waterproofing, protection board, and several feet of dirt, sitting in a genuinely high risk area for water intrusion, with the owner treating flawless waterproofing as one of their top priorities for the entire job. The team built a real plan around a single, well trained crew working at a careful, even pace, double inspecting the waterproofing before it was ever covered, and made sure everyone on site understood exactly why that detail mattered so much to the owner. Knowing the actual mission, and making sure the entire team understood it too, was what made hitting that milestone possible.

The Seven Keys Of Captaining Your Project

Keep these seven together, since a ship missing even one of them starts to drift.

Build functional, well connected teams throughout the project
Train people rather than assuming they already know their role
Keep the project properly stocked through real ownership of procurement
Maintain the systems that keep information and materials flowing
Know the actual mission and what matters most to the owner
Communicate the plan through real short interval planning
Stay productively paranoid about what could go wrong next

Connect To Mission

None of this means a captain has to perform every single task personally with their own two hands. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. It means recognizing that certain responsibilities, training, logistics, and ongoing vigilance, can never actually be handed off, no matter how busy the rest of the job gets or how tempting delegation feels in the moment.

Questions To Ask Before You Delegate Away The Helm

Use these to check whether you are actually captaining your project or simply staying busy without steering it.

Have I assumed my crew is trained instead of confirming it directly myself
Do I know exactly what matters most to my owner right now, today
Am I treating procurement as someone else’s responsibility to manage
What could be going wrong right now that I have not looked for yet

A Challenge For Every Senior Superintendent

Here is the challenge this week. Pick one of these seven keys you have quietly been delegating away, and take direct ownership of it again starting today, not next week. As has been said plainly, it’s your job and it’s your ship, and the crew depends on you actually standing at the helm rather than somewhere else entirely.

On we go.

Frequently Asked Questions

What does it mean to captain a project instead of just running it day to day? Captaining a project means taking direct, personal ownership of training, logistics, strategic direction, and ongoing vigilance, rather than assuming those responsibilities will simply take care of themselves or belong to someone else on the team.

Why can’t training your crew be left to someone else or simply assumed to already be handled? Trade partners and workers do not automatically arrive fully trained for a specific project’s exact needs, and treating training as someone else’s job leaves a leader blaming a crew for failures that proper training could have prevented from the very start of the work.

What are the seven keys behind captaining a project like a ship? The seven keys are building functional teams, training people, keeping the project properly stocked, maintaining key systems, knowing the actual mission, communicating the plan through short interval planning, and staying vigilant through productive paranoia about what could go wrong.

Why does staying vigilant matter more than simply staying busy? A full schedule can create the feeling of being in control without actually producing real oversight, while genuine vigilance means actively anticipating problems before they surface, which is what actually keeps a project on course.

What happens when a leader stops actively captaining the ship? Responsibilities that were never meant to be delegated, like training, procurement, and ongoing vigilance, quietly go unmanaged, and a project drifts into problems that eventually surface as the leader’s failure regardless of who was technically supposed to handle them.

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:

Elevating Construction Senior Superintendents – Part 1

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

Read 14 min

Your Project Reflects What You Tolerate

Your job reflects what you tolerate. That single line reframes an entire career, moving the responsibility for a project’s condition away from circumstances and squarely onto the leader actually running it day after day.

Where Leaders Quietly Blame Circumstances Instead Of Themselves

A project runs messy, unsafe, or behind schedule, and it feels natural to point at the client, the trade partners, or plain bad luck as the reason why things turned out this way. Those factors are real. They rarely explain the whole picture on their own. The condition of a project usually traces back to something much closer to home, the actual standard its leader has quietly decided is acceptable to allow.

Confusing Circumstances With What You Actually Tolerate

The failure pattern is treating a project’s condition as something that simply happens to a leader rather than something a leader actively shapes through what gets allowed to continue. A messy site, a late milestone, an unsafe habit, none of these exist in isolation from the standard set by the person in charge. Whatever gets tolerated repeatedly becomes the actual, unspoken standard for everyone else on the team.

The System Failed Them, They Didn’t Fail The System

The system failed them, they did not fail the system. Nobody explicitly teaches leaders that their own internal expectations function like a thermostat, quietly pulling a project back toward a specific range no matter how ambitious the stated goals happen to be. Without that understanding, it feels natural to search outward for the cause of a problem instead of examining the standard being modeled and tolerated from the top.

A Foreman Finally Understands The Real Ask

One real story captures this idea perfectly. A plumbing foreman once approached a superintendent and said something that stuck with him for the rest of his career, long after that specific project had ended. He said he finally understood what was actually being asked of him, that the goal was never a list of rigid rules to memorize, but simply to see the project the way the superintendent saw it, and to rise to the level of expectations being modeled every single day on site. That single insight, offered by someone on the crew rather than a book or a training course, captured the entire secret behind why some leaders consistently run better projects than others year after year.

Why This Distinction Matters

This matters because a leader cannot demand a standard from a team that they do not genuinely hold for themselves first, no matter how clearly that standard gets stated out loud. A superintendent who runs a personally messy, disorganized life tends to run a messy, disorganized project without ever fully realizing the connection between the two. Raising the actual condition of a project starts with raising the internal standard, the real mental set point, of the person leading it, not simply announcing a new goal and hoping everyone else complies on their own.

Practical Ways To Actually Raise Your Own Set Point

Real, lasting change to a personal standard rarely happens by accident or wishful thinking alone. Attending genuine leadership training and real conferences provides an energy and perspective boost that is difficult to generate alone, sitting at a desk. Reading constantly, ideally a book a week, builds knowledge and expands thinking faster than almost any other single habit available to a busy professional. Studying real role models and mentors, people who have already achieved the standard being pursued, gives a concrete example to actually pattern behavior after instead of guessing. And deliberately avoiding normalized failure, refusing to let a struggling project become a comfortable routine, protects a leader’s expectations from quietly eroding over time without them ever noticing it happening until much later.

The Five Keys Of Leading, Not Doing

Once a leader’s own standard genuinely rises, the actual job changes along with it in a very real, practical sense. Building the team by caring for and respecting individuals becomes a real, daily priority instead of an afterthought squeezed in when time allows. Having difficult conversations, the ones most people quietly avoid for as long as possible, becomes part of the job rather than something delegated away to someone else. Managing, coaching, and mentoring direct reports takes real, dedicated time instead of happening only when a problem forces the issue. Ensuring the team holds genuinely effective meetings becomes a deliberate responsibility instead of a box to check off a list. And scaling clarity and communication across an entire project becomes something actively managed, not something left to chance or good luck.

Ways To Raise Your Own Set Point

Keep these close, since raising a personal standard is what actually raises a project’s condition.

Attend real leadership training or conferences on a regular basis
Read consistently, aiming for a book a week
Study a real mentor or role model worth patterning behavior after
Refuse to let a struggling project quietly become a normal routine

Connect To Mission

None of this means every circumstance on a project is fully within anyone’s control. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. It means recognizing that a leader’s own standard shapes far more of a project’s outcome than circumstances alone ever could.

Signs Of A Leader Ready To Raise The Bar

Keep these five in mind once your own standard genuinely starts to rise.

Build the team by caring for and respecting individuals
Have the difficult conversations most people quietly avoid
Manage, coach, and mentor direct reports with real intention
Ensure the team holds genuinely effective, remarkable meetings
Scale clarity and communication across the entire project

A Challenge For Every Leader Ready To Raise The Bar

Here is the challenge this week. Look honestly at one condition on your project you have been quietly tolerating, and ask whether it reflects the actual standard you want to be known for. As has been said plainly, your job reflects what you tolerate, and raising that tolerance is the fastest way to raise everything else that follows from it.

On we go.

Frequently Asked Questions

What does it mean that a project reflects what you tolerate? It means the actual condition of a project, whether messy or organized, late or on time, safe or unsafe, tends to match whatever standard its leader has quietly allowed to continue, rather than being determined primarily by outside circumstances.

What is a mental set point, and why does it matter for a superintendent? A mental set point is the internal standard a leader genuinely holds, and it functions like a thermostat, pulling a project back toward that specific range regardless of stated goals, which is why raising the standard itself matters more than simply announcing a new target.

What are some practical ways to actually raise your own set point? Attending real leadership training, reading consistently, studying a genuine mentor or role model, and refusing to let a struggling project become a normalized routine are all practical ways to raise a personal standard over time.

What is the difference between leading and doing on a project? Doing refers to hands on tasks like paperwork, layout, and quality checks, while leading refers to building the team, having difficult conversations, coaching direct reports, running effective meetings, and scaling communication, all of which require stepping away from easier, more familiar tasks.

What are the five keys of real leadership described here? The five keys are building the team through genuine care and respect, having difficult conversations, managing and coaching direct reports, ensuring effective meetings, and scaling clarity and communication across an entire project.

If you want to learn more we have:

Discover Jason’s Expertise:

Construction Has No Choreography

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

Read 16 min

Here’s the deal. After doing a lot of field walks recently, I keep noticing the same thing over and over, on project after project. Almost everything in construction carries a two-to-four-hour delay built into it, and most of the industry has simply stopped noticing.

A trade has a question, two to four hour delay. Somebody needs a forklift, two-to-four-hour delay. Somebody needs a crane, two-to-four-hour delay. Somebody wants to meet with a foreman on site, two-to-four-hour delay. Somebody makes a phone call, two-to-four-hour delay. A trade hits a problem that could stop the whole train and needs to talk to the crews around them, two-to-four-hour delay. Somebody needs a logistics item just to mobilize into the building, two-to-four-hour delay. A field engineer is asked for layout, two-to-four-hour delay. I could genuinely keep going. I want that repetition to feel annoying, because it should. It should feel unbearable, because that reaction is exactly the point.

Why This Happens Everywhere, All the Time

The reason this delay shows up constantly comes down to something real about how the human brain works. To actually do pre-planning effectively, ahead of time, the brain has to be able to envision why something matters, or envision the real risk of not planning for it. And whatever that planning task is has to feel important enough, in the moment, to actually get chosen over something else competing for attention.

Most of the time, in the moment, we choose to go figure things out in the field instead of preventing the problem from happening in the first place. And people genuinely take pride in that reactive skill, treating the ability to improvise a fix on the spot as a mark of competence rather than a symptom of a plan that never should have needed rescuing.

Figuring It Out Has a Place, and It Is Not in the Field

I want to be precise about something, because I do genuinely believe in figuring things out. I am naturally a figure it out kind of person, and if someone consistently needs everything spoon fed to them with no ability to problem solve, I have very little patience for that.

But I am never talking about figuring it out in the field. I am never talking about figuring it out after the fact, in the moment, once the crew is already standing there waiting. I am talking about figuring it out in the pre-planning. Say it again. Figure it out in the pre-planning. I do not want anyone treating reactive, in-the-moment improvisation as the skill worth mastering. I want genuine research and real diligence applied ahead of time, specifically so problems get prevented instead of heroically solved after they have already cost real time.

A Story That Still Bothers Me

I want to be honest about how much this actually gets under my skin. I once flew somewhere for an important meeting, and the project manager responsible for having materials ready simply had not prepared anything. The response, in essence, was to shrug it off and go firefight in the moment, treating that improvisation as a chance to feel useful and significant. That single instance still frustrates me, and I am completely fine being told that reaction is a little emotionally immature. It genuinely bothered me, because there was no real acknowledgment of what that lack of preparation actually cost everyone in that room.

Watch for these signs your project is running on reactive improvisation instead of real pre-planning:

Equipment like forklifts, cranes, and hoists consistently requiring a wait rather than being scheduled in advance.
Foreman meetings capped at an arbitrary length rather than lasting as long as genuinely needed to lock in tomorrow.
A pattern of praising quick in-the-moment fixes rather than asking why the fix was needed at all.

Why Locking in the Day Before Actually Matters

People push back on this constantly, often mocking the idea of an afternoon foreman huddle and insisting planning should just happen in the morning instead. I understand the instinct, and it misses the actual point. If you want to eliminate the four hour delay pattern running through an average day, you have to plan at least a full day ahead.

That means deliveries scheduled for tomorrow, not figured out tomorrow morning. It means every piece of work mapped out so everyone knows exactly where it goes the next day. It means knowing when the forklift is actually available tomorrow, locked in ahead of time, not discovered through a two hour wait once someone needs it. Everything genuinely locked in and ready before the day even starts.

I genuinely dislike the rule that meetings have to fit inside some arbitrary time limit. A foreman meeting needs to run exactly as long as it takes to make the next day as predictable as humanly possible. Skip that discipline, and you are signing up for repeated four hour delays stacked on top of the physically demanding work everyone already has to do that day. That is not a minor inconvenience. It is genuinely unfair to the people living inside it.

Why This Should Bother You More Than It Bothers Me

If one instance of poor preparation frustrated me enough to still be thinking about it, consider what it actually feels like to be a trade partner living inside this pattern every single day. Waiting for a forklift. Waiting for a crane. Waiting for a hoist. Waiting for someone to move a pile of dirt or a parked truck out of the way before you can even start your own work.

That daily grind of waiting is genuinely exhausting, and it is completely preventable. We have to stop treating it as an unavoidable feature of construction and start treating it as exactly what it is, a direct result of planning reactively instead of proactively.

Building Real Choreography into Your Own Project

None of this requires new technology or a bigger budget. It requires a genuine commitment to pre-planning a full day ahead, every single day, without exception, and a willingness to let a foreman meeting run as long as it actually needs to in order to lock that plan in.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build the kind of daily pre-planning rhythm that eliminates these constant two-to-four-hour delays, tied directly into the Takt planning and huddle structure that makes tomorrow genuinely predictable instead of a series of reactive scrambles.

So here is the challenge. Track how many two-to-four-hour delays actually happen on your project over the course of one normal week, waiting on equipment, waiting on answers, waiting on materials, waiting on a foreman. Then ask honestly whether any of those delays could have been eliminated by locking the plan in a full day ahead of time. Most of them can be.

Jason Schroeder said it plainly: “Figure it out in the pre-planning.” Do that consistently, and the choreography construction has been missing finally starts to show up.

On we go.

FAQ

Why does a two-to-four-hour delay show up so consistently across so many different situations on a jobsite?

Because most planning happens reactively, in the moment a need arises, rather than proactively, a day or more in advance. Equipment, materials, and answers to questions all require some lead time to coordinate, and without that lead time built into a daily plan, waiting becomes the default outcome almost every time something is needed.

Why does the article argue against capping foreman meetings at a fixed length?

Because the actual purpose of that meeting is to lock in a genuinely predictable next day, and an arbitrary time limit can cut that planning short before it accomplishes its real goal. A meeting that runs as long as it takes to schedule deliveries, confirm equipment availability, and map out the next day’s work tends to prevent far more delay than it costs in extra meeting time.

Isn’t being good at figuring things out in the field a valuable skill for a superintendent or foreman to have?

Improvisation and problem solving are valuable skills in general, but the article draws a distinction between using that skill during pre-planning, where research and diligence can genuinely prevent a problem, versus relying on it reactively in the field after a preventable delay has already occurred. The goal is applying that same figure it out mindset earlier, before the problem happens, rather than treating in-the-moment firefighting as the mark of a strong performer.

How far ahead should a project team actually plan to eliminate these recurring delays?

At minimum, a full day ahead, with deliveries scheduled, equipment availability confirmed, and the next day’s work mapped out before that day even begins. Planning further ahead through look ahead planning and Takt sequencing extends that predictability even further, but locking in at least the next day consistently is the baseline needed to break the pattern of constant reactive waiting.

If you want to learn more we have:

Discover Jason’s Expertise:

The Field Book

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

Read 20 min

The Field Book: Don’t Build Without One

The best field people write things down.

Here is the deal. Not in their phone. Not in an app they will open once and forget about. In a field book that lives in their back pocket, gets pulled out a dozen times a day, and holds the specific, hard won details that make the difference between a project run on memory and a project run on record. I came up through the trades, and one of the first things I learned from the builders I respected most was exactly this. Nobody who was actually good at the job trusted their memory alone.

The Pain of a Project That Only Lives in Someone’s Head

Picture the alternative. A field engineer sets a control point on a Tuesday, checks it visually, and moves on to the next task without recording it anywhere except their own recollection. Three weeks later, someone asks what the weather was the day a specific pour happened, or who was on site, or exactly where a benchmark was established relative to a property line. Without a written record, the answer depends entirely on someone’s memory of a specific day weeks in the past, and memory degrades in exactly the ways that matter most on a construction project. Details blur together. One Tuesday starts to sound like every other Tuesday. The exact measurement that mattered gets remembered approximately instead of precisely, and approximately is not good enough when a control point, a property line, or a daily report becomes the reference everyone downstream depends on.

This is not a hypothetical problem. It is the default condition of any project where critical field information exists only in someone’s head. And the person holding that information does not fail anyone by forgetting. They fail because memory was never designed to be a permanent record, and asking it to serve as one guarantees that details will eventually be lost, right at the moment someone genuinely needs them.

The Failure Pattern

The failure pattern is trusting memory, or worse, an app nobody actually opens consistently, to do the job that a physical, always available record is built to do.

Digital tools have real value, and this is not an argument against them. But a phone requires charge, requires unlocking, requires navigating to the right app, and requires the discipline to actually open it in the moment a field observation needs to be captured, standing in the mud, hands occupied, weather uncooperative. A field book requires none of that. It lives in a back pocket, opens instantly, and captures information the moment it happens, without any dependency on battery life or app navigation or the friction of digital entry under field conditions. Projects that rely entirely on digital capture, without the physical backup of a field book, frequently discover that the information exists in theory but was never actually entered in the moment it mattered, because the friction of digital capture in real field conditions is higher than most people account for.

They Didn’t Fail the System

When a detail gets lost, a control point’s exact location, a specific conversation about a field condition, the reason behind a decision made weeks earlier, the instinct is to ask why nobody wrote it down. That question is fair, but it is worth asking a prior question first. Did that person actually carry a tool designed for capturing information the moment it happened, or were they relying on memory and an app that friction made impractical to use consistently in the field?

A field engineer without a physical field book is not failing to be diligent. They are working without the tool that diligence actually requires. Give that same person a book that lives in their pocket, opens instantly, and takes seconds to jot a note in, and the diligence that was always there becomes visible in a permanent record instead of disappearing into memory that nobody can verify later.

What Goes in the Book

Notes capture field observations, measurements, and reminders, the small, specific details that seem minor in the moment and become essential later. A brass cap set at a specific quadrant. A dog tied out at a specific fence line, which sounds trivial until the next person walking that path gets chased and wishes someone had warned them. These notes are not formal documentation. They are the raw, immediate record of what a field person actually observed, in their own words, at the moment they observed it.

Daily reports track weather, crew, and work performed, creating a specific, dated record of exactly what happened on a specific day. When someone asks what happened on site three weeks ago, the answer should not depend on reconstructing a hazy memory. It should come from a daily entry that states, plainly, the date, the day of the week, the weather, the crew present, and the specific work performed that day. That level of specificity, control points established, specific stakes set, benchmarks checked, turns a vague recollection into an exact, defensible record.

To do lists organize next steps, punch items, and follow up tasks in a form that actually gets acted on. The work does not get done because someone remembered it in the moment. It gets done because it was written down, checked against later, and marked complete once it actually happened. A checklist with items checked off is proof of execution in a way that a mental note never is.

Layout and control information, benchmarks, dimensions, control points, and reference locations, is described directly as sacred information, and that word choice is deliberate. This category of information is the foundation that an enormous amount of subsequent work depends on. A control point recorded incorrectly, or not recorded at all beyond someone’s memory of where it was, creates risk that compounds through every subsequent measurement and layout decision that references it. This is exactly the kind of information that must exist in a permanent, physical record, not in anyone’s recollection.

Installation sketches capture quick diagrams that clarify field conditions and installation intent, translating a physical layout, dimensions, orientations, and relative positions, into a visual record that a paragraph of text could never communicate as clearly. A sketch with dimensions beats a paragraph every time, because spatial information is fundamentally visual, and forcing it into pure text loses precision that a quick diagram preserves naturally.

How You Keep Your Tools Says Everything

My father taught me that how you keep your tools says everything about how you do your work. Your field book is a tool. Maybe the most important one you carry, because unlike a physical tool that performs a single task, the field book is the record of every task, every observation, every measurement that everything else on the project depends on being accurate and preserved.

A field book kept sloppily, entries skipped, details recorded vaguely, pages torn out or lost, reflects and often predicts a broader carelessness in how the actual work gets executed. A field book kept with real discipline, consistent daily entries, precise measurements, careful sketches, reflects the same discipline that shows up in how that person actually performs the work itself. The book is not separate from the craftsmanship. It is an expression of it.

Communicate, Verify, Improve

A field book preserves critical jobsite knowledge so the work can be communicated, verified, and improved, and each of those three functions depends directly on the record actually existing.

Communication depends on having something specific to communicate. A daily report that states exactly what happened, who was there, and what conditions existed lets that information travel accurately to anyone who needs it later, whether that is a superintendent reviewing progress, an engineer investigating a question, or a new team member trying to understand what has already happened on the project.

Verification depends on having a record to check claims against. When a question arises about what happened on a specific day, or where a specific control point was actually established, a field book provides the answer that memory alone cannot reliably provide. This is not about distrust between team members. It is about recognizing that memory degrades and written records do not, and a project that depends on accuracy needs the record, not just the recollection.

Improvement depends on being able to look back at what actually happened and learn from it. A field book that spans an entire project becomes a genuine history, a record of decisions made, conditions encountered, and problems solved, that can be reviewed and learned from in a way that scattered memories across a team never quite allow.

Signals Your Team Needs This Discipline

Look for these patterns on your own project:

Questions about what happened on a specific past date that nobody can answer with precision
Control points or benchmarks that exist only in someone’s memory of where they were established
To do items that were discussed verbally and never followed up on because nothing was written down to check against
Field observations, a hazard, a condition, a detail, that got mentioned once and then forgotten because nobody recorded it
A reliance on a digital app for field notes that, in practice, rarely gets opened consistently under actual field conditions

Each of these signals a gap between what actually happened on the project and what anyone can actually prove happened, and a field book is the simplest, most reliable tool for closing that gap.

Carry the Book Every Day

Here is your challenge. If you do not already carry a field book, start tomorrow. Notes, daily reports, to do lists, layout and control information, installation sketches. Write in it every single day, not just when something feels important enough to record, because the details that seem minor in the moment are frequently the exact details someone needs weeks later.

Taiichi Ohno insisted that decisions should be based on what you can actually see and verify, not on assumption or memory. A field book is exactly that principle made physical, a record you can point to, verify, and trust, rather than a recollection that fades the moment you need it most. Communicate. Verify. Improve. That is not just note taking. That is building like a professional.

On we go.

FAQ

Why use a physical field book instead of a phone or digital app?
A physical field book has no battery to manage, no app to navigate, and no friction between the moment an observation happens and the moment it gets recorded. Digital tools have real value for organizing and sharing information after the fact, but in the actual field conditions where a note needs to be captured immediately, hands occupied, weather uncooperative, a physical book that opens instantly and requires no charge is far more reliable in practice.

What is the most important category of information to record in a field book?
Layout and control information deserves the most careful attention, since benchmarks, dimensions, and control points are the foundation that an enormous amount of subsequent work depends on. An error or gap in this category compounds through every measurement and layout decision that references it later, making it genuinely sacred information that must exist in a permanent, verifiable record.

How detailed should a daily report entry actually be?
Detailed enough to answer, with precision, a question asked weeks later about what happened that specific day. Date, day of the week, weather, crew present, and the specific work performed, including any issues encountered, gives a level of specificity that a vague recollection can never match.

If you want to learn more we have:

Discover Jason’s Expertise:

Pull Planning Homework

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

Read 20 min

Pull Planning Homework: The Best Sessions Are Won Before Anyone Walks in the Room

The best pull plan sessions are won before anyone walks in the room.

Here is the deal. I have watched too many pull plans turn into guessing sessions. Trade partners standing at the board, making up durations on the spot, committing to handoffs they have not actually thought through. That is not planning. That is improvising with sticky notes, and the sequence built from that improvisation rarely survives contact with the actual work.

The Pain of a Room Full of Guesses

Picture a typical pull plan session run without preparation. A facilitator asks the mechanical trade how long their rough in will take in a given zone. Someone glances at the milestone, does quick mental math, and offers a number that sounds reasonable but was never actually derived from a real breakdown of the activities involved. The structural trade is asked what they need before they can issue a foundation plan, and the honest answer requires knowing exactly which upstream deliverable they depend on and who owns it, information that nobody in the room has actually confirmed before the meeting started.

Every one of those on the spot answers becomes a sticky note on the board, and the board looks complete once the session ends. But a schedule built from guesses is not a schedule. It is a collection of plausible sounding commitments that nobody actually verified before agreeing to them. When the plan starts to slip, and it does, the root cause traces back to a duration that was never real or a dependency that was never actually confirmed, both of which could have been caught before the session ever started if anyone had done the work of preparing first.

The Failure Pattern

The failure pattern is treating the pull plan session itself as the place where planning happens, rather than as the place where already completed planning gets connected across disciplines.

A pull plan session has a specific, narrow purpose. It exists to take each discipline’s own understanding of their work and link it to every other discipline’s understanding, creating a sequence that reflects real dependencies rather than an assumed order. That purpose only works if every discipline arrives already knowing their own deliverables, their own workflow, and their own needs. When trades instead use the session itself as the place to first figure out their own scope and durations, the session collapses into two jobs happening simultaneously, individual planning and cross discipline coordination, and doing both at once produces worse results at both than doing either one properly.

They Didn’t Fail the System

When a pull plan session produces a schedule that falls apart within the first few weeks, the instinct is to blame the trades for bad estimates or poor commitment. They should have known their durations better. They should have thought this through.

Before reaching that conclusion, ask what those trades were actually given before walking into the room. If nobody structured an expectation that each discipline arrive with their deliverables, workflow, and needs already worked out, then asking for accurate durations and honest dependencies on the spot is asking people to do serious analytical work under social pressure, in front of every other trade, in real time. That is not a fair test of anyone’s planning ability. It is a structural setup that all but guarantees the numbers that come out will be optimistic, vague, or simply invented to keep the session moving.

What Pull Planning Homework Actually Requires

Before the session, every discipline prepares three specific things, and each one answers a different question that the pull plan session depends on already being answered.

Deliverables define the condition of satisfaction for each handoff, the specific, concrete output that discipline is responsible for producing and passing to the next trade. This is not a vague description of scope. It is a precise statement of what “done” actually means for that handoff, because a pull plan sequence only holds together if every trade agrees on what completion actually looks like at each interface point.

Workflow lists the actual activities that discipline will perform to produce each deliverable, along with realistic durations for each one. This is where the guessing problem gets solved directly. A duration produced by actually breaking work into its component activities and thinking through how long each one genuinely takes is a fundamentally different number than a duration offered on the spot in front of a room full of people waiting for an answer. The first number is honest. The second number is a social compromise between accuracy and the pressure to keep the meeting moving.

Needs identify exactly what that discipline requires from others, and precisely who must provide it. This is the piece most frequently skipped in unprepared pull plans, because it requires each trade to think backward from their own work to the specific upstream deliverables they depend on, and to know exactly which other discipline owns each of those deliverables. A structural engineer who has done this homework walks in already knowing they need the preliminary wall and foundation analysis before they can issue the foundation plan, and they know exactly who owes them that analysis. That specificity changes the entire conversation.

Why Preparation Changes the Conversation Itself

When a trade shows up to the board having already done this homework, the pull plan session stops being a place to figure things out and becomes a place to connect things that are already figured out. The structural engineer who already knows their dependency and who owns it is not guessing when that conversation comes up. They are confirming, negotiating a specific date, and locking in a commitment that both sides can actually stand behind.

This shift matters because it changes what “commitment” actually means in the room. A commitment made after genuine preparation is a real promise, backed by an actual understanding of the work involved. A commitment made on the spot, without preparation, is closer to a hope, offered because the format of the meeting requires an answer and nobody wants to be the person holding up the session. Both look identical on the board as a sticky note with a duration written on it. Only one of them is likely to actually hold once the work begins.

The Sequence Only Holds When the Inputs Are Real

Pull planning works by starting from the milestone and working backward, each discipline defining what they need from the trade before them in the sequence. That backward logic is powerful, but it only produces a reliable schedule if every discipline’s inputs into that logic are real. A sequence built from honest durations and confirmed dependencies holds because it reflects how the work actually happens. A sequence built from optimistic guesses and unconfirmed assumptions about who owes what to whom looks identical on the board but will not survive the first week of real execution, because the underlying logic it was built from was never true in the first place.

This is exactly why the homework matters more than the session itself, even though the session is what everyone remembers and what looks impressive on a wall covered in color coded sticky notes. The sticky notes were never the magic. The magic is the preparation that made those notes trustworthy, the conversation that happens once trades arrive already knowing their own work, and the promises made between people who have done the thinking necessary to make those promises honest.

How to Actually Complete the Homework

Review the phase being pulled and understand the overall scope of work involved before attempting to break down individual activities. Think through all table work, major activities, and approximate durations for the discipline’s own scope, building a genuine understanding before translating it into specific line items. For each activity, identify exactly what is needed and from whom, rather than leaving dependencies vague or assumed. List activities working backward from the final milestone, since pull planning logic flows in reverse from the goal rather than forward from the start.

Be brief. Each activity and each need should fit on a three by three inch sticky note, forcing genuine clarity rather than vague, paragraph length descriptions that sound thorough but communicate nothing precise. Focus on the work and handoffs relevant to other disciplines, not an exhaustive internal breakdown that nobody else in the room actually needs to see. During the meeting, place notes in the planning line linking each activity to the milestone, keeping the visual logic of the sequence intact as it gets built collaboratively. And as a team, work backward through the board, negotiating and committing to additional needs as they surface in real time, because even the best preparation will not eliminate every cross discipline conversation, it simply ensures those conversations start from real information instead of guesses.

Signals Your Team Is Improvising Instead of Planning

Look for these patterns in your own pull plan sessions:

Trades offering durations on the spot without any visible reference to a prior breakdown of their own activities
Dependencies discovered for the first time during the session rather than identified in advance
Commitments made under visible social pressure to keep the meeting moving rather than genuine confidence in the number
A schedule that looks complete on the board but starts slipping within the first few weeks of execution
No expectation set in advance that trades should arrive having already thought through their own deliverables and needs

Each of these signals a pull plan built on improvisation rather than preparation, and that gap is exactly what Pull Planning Homework is designed to close.

Prepare Before the Next Session

Here is your challenge. Before your next pull plan session, send every discipline the homework requirement explicitly. Deliverables. Workflow. Needs, with names attached. Do not let the session be the first time anyone thinks through their own scope. Let it be the place where already prepared work gets connected into a sequence everyone can actually trust.

Jason Schroeder puts the whole philosophy in four lines: plan the work, work the plan, respect the people, improve every day. The sticky notes were never the magic. The preparation is. Do the homework, and watch the sequence actually hold.

On we go.

FAQ

How much time should a trade partner spend on this homework before a pull plan session?
The time investment scales with the complexity of the phase being pulled, but even a modest amount of deliberate preparation, reviewing the scope, listing major activities with honest durations, and identifying key dependencies, produces dramatically more reliable commitments than arriving with no preparation at all. The goal is genuine thought, not exhaustive documentation.

What happens if a trade partner shows up without having done the homework?
Their commitments in that session are far more likely to be guesses rather than honest estimates, and the resulting schedule inherits that unreliability at exactly the points where that trade’s work connects to everyone else’s. Facilitators should treat homework completion as a genuine prerequisite for a session producing a trustworthy schedule, not an optional nicety.

How specific should the “needs” section actually be?
Specific enough to name both what is needed and exactly who owns providing it, not a general acknowledgment that dependencies exist. The structural engineer example in this practice, knowing precisely that they need the preliminary wall and foundation analysis and knowing exactly which trade owes it to them, is the level of specificity that actually changes the quality of the conversation during the session.

If you want to learn more we have:

Discover Jason’s Expertise:

Leader Standard Work

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

Read 21 min

Leader Standard Work: Your Calendar Is Your Leadership System

Most superintendents do not have a time problem. They have a standard work problem.

Here is the deal. When a leader does not have a weekly rhythm, the job runs them instead of the other way around. Every fire gets fought in real time because nothing was planned in advance to prevent it. Every meeting arrives as a surprise because nothing on the calendar anticipated it. And the routines that actually keep a project flowing, the walks, the planning sessions, the time spent developing people, get squeezed out by whatever screamed loudest that particular day. Leader Standard Work fixes that, not by adding more hours to the week, but by giving every routine that matters a protected, recurring home.

The Pain of a Week That Runs You

Picture a typical week for a superintendent without a standard cadence. Monday starts reactively, responding to whatever accumulated over the weekend rather than opening with a deliberate plan. A job walk happens when there is time, which some days means it does not happen at all. Procurement follow up gets squeezed into whatever gap appears between more urgent demands, which means it frequently does not happen until material is already at risk of becoming a schedule problem. One on one time with team members gets pushed to whenever a crisis is not actively unfolding, which in practice means it rarely happens with any real consistency.

By Friday, that superintendent has spent the entire week reacting. They walked the job on the days nothing more urgent interrupted them. They talked to their people when a problem forced the conversation, not when the person actually needed support or clarity. They feel exhausted, and they are right to feel that way, because a week spent entirely in reactive mode is genuinely more draining than a week spent executing a plan, even when the total hours worked are identical. The exhaustion is not from the volume of work. It is from the absence of any structure that would have let some of that work happen calmly, in advance, instead of urgently, under pressure.

The Failure Pattern

The failure pattern is treating a leader’s calendar as something that fills up passively, in whatever order requests arrive, rather than something that gets designed deliberately in advance.

Most superintendents would never let a project’s construction schedule get built this way. Nobody would accept a schedule that simply records whatever happened each day, in whatever order it happened, without any prior plan to compare it against. Yet that is exactly how most leaders manage their own week. The calendar records events after the fact rather than directing them in advance. Meetings get accepted as they arrive rather than scheduled into a deliberate weekly structure. The result is a leader whose week has no plan to fall back on when things get busy, which means busy weeks default entirely to whoever is loudest in the moment.

They Didn’t Fail the System

When a superintendent seems constantly overwhelmed, missing job walks, skipping one on ones, always racing from one fire to the next, the instinct is to conclude they need better time management or more discipline.

Look past that conclusion and the real issue is usually structural. A leader without a standard weekly cadence is not failing to manage their time poorly. They are managing time inside a system that never gave the important routines a protected place to happen. Without a fixed slot for a daily job walk, the walk competes every single day against whatever urgent request shows up first, and urgent requests win that competition every time, because urgency always outranks importance in a calendar with no prior commitments protecting the important things. The superintendent did not fail to prioritize correctly. They were never given a structure that made prioritizing possible in the first place.

What Leader Standard Work Actually Builds

A Leader Standard Work board maps the entire week, day by day, hour by hour, assigning a protected home to every routine that actually keeps a project flowing.

Morning huddles and setup time open each day on purpose, rather than starting reactively with whatever accumulated overnight. A leader who begins the day with a deliberate huddle and a clear plan for that specific day is operating from intention rather than catching up to events that already happened.

Job walks appear every single day, not as an aspiration squeezed in when time allows, but as a fixed, non negotiable block. Being in the field, seeing the actual work, and supporting the people doing it is not a task that competes with the rest of the job. It is the foundation the rest of the job depends on, and it only survives contact with a busy week if it has a protected place on the calendar that nothing else is allowed to bump.

Procurement time recurs multiple times through the week specifically so material never becomes the roadblock that stops production. Chasing a missing delivery in a panic, after it has already become urgent, costs far more time and creates far more schedule risk than a recurring, calm check in that catches a gap while it is still easy to correct.

Weekly schedule updates and Last Planner sessions keep the plan itself alive, rather than allowing the schedule to quietly drift out of sync with what is actually happening in the field. A schedule that never gets deliberately reviewed and updated stops being a real plan and becomes a historical document nobody trusts.

One on one time with people is protected specifically because leaders build leaders, and that development does not happen accidentally in the gaps of a busy week. It happens because someone decided in advance that a specific person’s growth deserved a specific block of time, every week, regardless of what else was competing for attention that day.

Training blocks develop capability across the whole team on a recurring basis, treating skill development as an ongoing investment rather than something that only happens during a formal onboarding period or an occasional off site session.

And “try to leave” appears on the schedule deliberately, which matters more than it might first appear. A leader who never protects time to actually go home is not being more dedicated. They are running a system with no margin, and a system with no margin cannot absorb anything unexpected without something else breaking.

The Fourteen Hours That Change Everything

Here is the part most people miss when they first look at a board like this. Map the week this deliberately, protecting every routine that actually matters, and the result is not a calendar packed edge to edge with no room to breathe. It is a calendar with fourteen hours left over.

That fourteen hours of buffer is not wasted time or evidence of an underfilled schedule. It is the project’s capacity to absorb the unexpected without the whole week collapsing. It is the room to walk with someone who unexpectedly needs clarity that day. It is the space to remove a roadblock that nobody could have predicted on Monday. It is, sometimes, simply the room to think, which is a resource every leader needs and almost none of them protect deliberately.

This is the counterintuitive insight underneath the entire practice. A week with no standard cadence feels perpetually full, because every hour is consumed reactively by whatever surfaces, with nothing held in reserve. A week built around a deliberate standard, protecting the routines that matter most, actually produces margin, because the important things are no longer competing chaotically with the urgent things for the same unprotected hours. Structure does not consume time. It creates it.

Why This Is a System, Not a Willpower Problem

The leaders who feel like they have no time are usually the ones with no standard. The leaders who plan, walk, coordinate, train, and reflect on a genuine cadence have margin. They have presence. And their jobs flow, not because they are more talented or more disciplined as individuals, but because they built a system that protects the routines their leadership actually depends on, rather than leaving those routines to compete unprotected against whatever happens to be loudest that day.

This is exactly the same principle behind every visual management practice this factory has covered, the Circle of Trust, the project KPI tracker, quality at the source floor markings. A standard that only exists as a good intention gets crowded out by whatever is urgent in the moment. A standard that has a visible, protected, recurring home on a board or a calendar survives contact with a busy week, because the structure itself is doing the work that willpower alone never reliably does.

Five Functions Every Leader’s Week Needs

The board organizes around five functions, and a week missing any one of them is a week with a real gap. Plan starts the week with clear direction, schedules, and preparation rather than reactive scrambling. Walk puts the leader in the field, seeing the actual work and supporting the people doing it. Coordinate aligns trade partners, removes constraints, and keeps work flowing between teams. Train develops people and builds capability across the team on an ongoing basis. Reflect pauses deliberately to learn and continuously improve leadership itself, a function almost every leader skips first when the week gets busy, and the one that arguably matters most for sustained improvement over time.

Build Your Own Board This Week

Here is your challenge. Take your actual calendar for next week and map it the way this board maps a superintendent’s week. Give the job walk a protected daily slot. Give procurement follow up a recurring home. Give at least one person on your team a protected one on one. Give yourself a protected time to leave. Then see what is actually left over.

Edwards Deming said it plainly: “Every system is perfectly designed to get the results it gets.” A week with no standard is a system perfectly designed to produce chaos, reaction, and exhaustion. A week built around Leader Standard Work is a system designed, on purpose, to produce flow, presence, and margin. Your calendar is your leadership system. Build it like one.

On we go.

FAQ

Isn’t a fully scheduled week actually less flexible when something urgent comes up?
The opposite is usually true. A week with protected routines and a deliberate fourteen hour buffer has genuine capacity to absorb the unexpected without collapsing, because the important routines already have a home and do not need to be sacrificed the moment something urgent appears. A week with no standard has no buffer at all, so every urgent event forces something important to be dropped entirely rather than simply rescheduled within existing margin.

How do you build in the daily job walk if the project is genuinely too busy some days?
Protect it as a fixed, non negotiable block rather than something scheduled around everything else. The walk is not competing with the rest of the job. It is the mechanism that prevents many of the fires that would otherwise consume the rest of the week, so treating it as optional under pressure removes exactly the practice that would have reduced that pressure in the first place.

What is the risk of not including reflection time on a leader’s weekly cadence?
Reflection is usually the first function to disappear when a week gets busy, and it is also the function most directly tied to a leader actually improving over time rather than simply repeating the same patterns indefinitely. Without a protected time to pause and learn from the week, a leader tends to keep running the same reactive cycle without ever stepping back to see what a genuine standard cadence could change.

If you want to learn more we have:

Discover Jason’s Expertise:

General Offerings

Company Offerings

Systems

Are You Multiplying Your Team, Or Diminishing It?

Where Good Intentions Quietly Diminish A Team

Confusing Control With Capability

The System Failed Them, They Didn’t Fail The System

Two Very Different Bosses, Two Very Different Careers

Why This Distinction Matters

A Team Also Needs A Real Goal Worth Chasing

Signs You Might Be Diminishing Your Team

Connect To Mission

Ways To Multiply Your Team Instead

A Challenge For Every Leader Building A Team

Frequently Asked Questions

Why Material Handling Is The Cost Nobody Tracks

Where A Careful Plan Still Leaves Money On The Table

Folding A Real Cost Into Something Invisible

The System Failed Them, They Didn’t Fail The System

A Truckload Of Plywood That Moved All Day

Why This Distinction Matters

A Laydown Area That Revealed Everything

The Real Driver Behind Crew Productivity

Signs Material Handling Is Quietly Costing You

Connect To Mission

Ways To Plan For Material Handling Before It Costs You

A Challenge For Every Superintendent

Frequently Asked Questions

Why Courage Is What Actually Turns A Plan Into A Result

Where Good Plans Quietly Get Abandoned Under Pressure

Confusing Compliance With Being A Team Player

The System Failed Them, They Didn’t Fail The System

Holding The Line Against A Caravan Of Nervous Executives

Why This Distinction Matters

Urgency Requires The Same Kind Of Courage

Where Courage Actually Shows Up On A Project

Connect To Mission

Questions To Ask Before You Cave To Outside Pressure

A Challenge For Every Senior Leader

Frequently Asked Questions

Why Trust Has To Come Before Everything Else On Your Team

Where Leaders Skip Straight To Demanding Accountability

Confusing The Goal With The Starting Point

The System Failed Them, They Didn’t Fail The System

Sharing Calendars Instead Of Hoarding Control

Why This Distinction Matters

The Five Behaviors In Order

Accountability Changes Everything Once It Finally Arrives

Ways To Build Real Trust On Your Team

Connect To Mission

Questions To Ask About Your Own Team’s Trust

A Challenge For Every Leader Building A Team

Frequently Asked Questions

Why Every Project Needs A Captain, Not A Delegator

Where Busy Gets Confused With In Command

Confusing Delegation With Abdication

The System Failed Them, They Didn’t Fail The System

A Concrete Crew That Needed Training, Not Blame

Why This Distinction Matters

Knowing Where You Are Actually Going

The Seven Keys Of Captaining Your Project

Connect To Mission

Questions To Ask Before You Delegate Away The Helm

A Challenge For Every Senior Superintendent

Frequently Asked Questions

Your Project Reflects What You Tolerate

Where Leaders Quietly Blame Circumstances Instead Of Themselves

Confusing Circumstances With What You Actually Tolerate

The System Failed Them, They Didn’t Fail The System

A Foreman Finally Understands The Real Ask

Why This Distinction Matters

Practical Ways To Actually Raise Your Own Set Point

The Five Keys Of Leading, Not Doing

Ways To Raise Your Own Set Point

Connect To Mission

Signs Of A Leader Ready To Raise The Bar

A Challenge For Every Leader Ready To Raise The Bar

Frequently Asked Questions

SUBSCRIBE NOW !

Subscribe to our newsletters and stay updated!