We Have Just Begun, Feat. Hal Macomber

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

Read 18 min

Don’t Hit the Car in Front of You

Teaching a teenager to drive comes down to two things at first, and only two things: do not hit the car in front of you, and stay between the lanes. Turn signals, mirrors, all of that comes later, once those two fundamentals are actually solid. A new driver obsessing over the rearview mirror while drifting toward the car ahead is a driver about to cause an accident.

Running a project works the same way. Too much attention on what already happened, and not enough on what is directly ahead, is exactly how a team ends up hitting something that could have been avoided entirely.

The Real Pain: Project Controls That Only Look Backward

The real pain is that most of what gets called “project controls” today is really just a rearview mirror exercise. A monthly or biweekly schedule update reports on what already happened, weeks after the fact, long after any real chance to prevent the problem has already passed.

By the time that update reaches anyone who could act on it, the information is already old news. A schedule performance index or a cost performance index can tell you clearly that something went wrong last month. Neither one helps you steer around the thing that is about to go wrong tomorrow.

The Failure Pattern: Reporting the Past Instead of Steering the Future

The failure pattern is treating a periodic schedule update as the entirety of project control, rather than as one piece of a much more active, forward-looking system. There is a real, costly lag between collecting data and actually using it, and that lag does not have to be thirty or forty days long. It can be measured in hours instead.

Teams stuck in this pattern spend enormous energy explaining what already went wrong, and comparatively little energy actually steering toward what is coming next.

A few signs tend to show up when a project’s control system is backward-looking instead of forward-steering, and they are worth checking honestly:

Schedule updates happen on a monthly or biweekly cycle, with no meaningful check-in tied to the pace of the actual work itself.
Conversations focus heavily on explaining variances that already happened rather than adjusting course for what is coming next.
The gap between collecting data and acting on it is measured in weeks, when it could realistically be measured in hours.

This Isn’t About Ignoring the Past, It’s About Where You Put Your Attention

None of this means history does not matter. It means constant rearview attention, at the expense of what is directly ahead, is dangerous whether you are driving a car or running a project. The dashboard in front of you, speed, temperature, fuel, matters far more moment to moment than what is already behind you.

Real project control means keeping your primary attention on the next milestone, checking whether you are still effectively steering toward it, rather than spending most of your energy analyzing what already happened further back down the road.

Checking In Before Noon, Not 30 Days Later

Here is what that looks like applied directly to Takt-based production. For a one-day Takt time, the real check-in should happen no later than noon, are we effectively steering toward finishing this wagon by the end of the day. For a two-day Takt time, that check happens by the start of the second day. For a five-day Takt time, by the start of the third day.

None of these checks require waiting for a formal schedule update cycle. They are built directly into the rhythm of the work itself, catching a steering problem while there is still time to correct it, rather than discovering it long after the moment to fix it has already passed.

Why It Matters: You Can’t Correct a Course You Already Missed

This matters because real steering only works with fast, frequent, small corrections. A course correction made hours after drifting off track is manageable. The same drift, left unnoticed for weeks, becomes a genuine crisis by the time anyone finally looks at the data.

As one longtime Lean construction consultant puts it plainly, project controls are really about steering, not about looking over your shoulder. A team that treats control as steering toward the next milestone, checked frequently and early, stays in a fundamentally different position than a team that treats control as a monthly report card on what already happened.

Teach the Framework: Measurement, Assessment, and Control Working Together

Three things work together here. Measurement means tracking whether your production trains are actually hitting their Takt time reliably, not just whether tasks eventually got done, since a plan that finishes wildly early or late just as often as on time is not really flowing at all, even if the average looks fine on paper. Assessment means asking, in order, whether the team is learning, whether the team is improving, and whether the project overall is better off than it was, rather than jumping straight to a verdict without asking whether real learning happened first.

Control means taking that fresh, current information and steering toward the next milestone right now, today or tomorrow, rather than weeks from now when a formal update finally circulates. All three pieces depend on each other. Measurement without frequent assessment just produces numbers nobody uses in time. Assessment without fast control just produces insight that arrives too late to matter.

A few practical markers show whether a team is actually steering, rather than just reporting after the fact:

A check-in tied to the actual Takt time happens well before the period ends, not just at the next scheduled meeting.
The team can say clearly whether they are learning and improving, not just whether tasks got marked complete.
Course corrections happen the same day or the next day a drift is noticed, rather than waiting for a formal update cycle.

Turning This Into Daily Practice

Building this starts with tying your check-ins directly to your actual production rhythm rather than an arbitrary calendar cycle. If your Takt time is one day, check by midday. If it is two days, check by the start of day two. Ask specifically whether you are still on course for the next milestone, not just what already happened during the last reporting period.

Why Trust Comes First

None of this steering works without something less technical but just as essential: real trust and connection between the trades actually doing the work. A striking point made at a recent industry gathering was that construction will not solve its deepest problems until it deals honestly with distrust, and that distrust cannot be resolved without genuine goodwill between people first.

On a single Takt train with dozens of trades depending on each other’s timing and quality, that trust is not optional, it is the thing that makes real-time steering possible at all. The practical challenge is refreshingly simple: learn the name of someone on another trade, introduce yourself, build a real connection before you actually need it. Worker huddles that include real stories and honest vulnerability, not just logistics, build exactly this kind of trust over time, and it shows.

Connecting It Back to Building People, Not Just Projects

None of this happens without leaders willing to build both the measurement systems that catch drift early and the genuine human trust that makes steering together actually possible. Both pieces matter, and neither one works well without the other.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow, including building real-time steering systems instead of rearview-mirror reporting.

The Challenge

So here is the challenge worth carrying onto your next project: build a check-in tied to your actual Takt time, not your calendar, and ask whether you are steering toward the next milestone right now. Then go learn the name of someone on a different trade than your own. As Greg Howell put it, “Project controls is really about steering, not looking over your shoulder.” On we go.

FAQ

What does it mean that “project controls is about steering, not looking over your shoulder”?

It means real control focuses on actively steering toward the next milestone in real time, rather than just reporting on what already happened in the past. A monthly schedule update that only explains old variances is not the same thing as actually correcting course while there is still time to do it.

Why isn’t a monthly or biweekly schedule update enough for real project control?

The lag between collecting that data and actually acting on it is often weeks long, by which point the moment to prevent a problem has usually already passed. Real steering requires check-ins tied to the actual pace of the work, sometimes within hours, not a fixed calendar cycle.

How often should a team check whether it’s on course, according to this framework?

The check-in should be tied to the actual Takt time. A one-day Takt time calls for a check by midday, a two-day Takt time by the start of the second day, and a five-day Takt time by the start of the third day, well before the period ends.

What is the right order for assessing a team’s performance?

First ask whether the team is genuinely learning, then whether they are improving, and only then whether the project overall is better off. Skipping straight to a final verdict without first confirming real learning happened tends to miss what is actually driving performance.

Why does trust between trades matter for something as technical as project controls?

Real-time steering depends on people across different trades communicating honestly and quickly when something is off course, which requires genuine trust, not just a shared schedule. Building that trust, through simple steps like learning another trade’s name or sharing real stories in huddles, makes the entire steering system actually work in practice.

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.

Things are Getting Better!

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

Read 17 min

A Buzz of Hopefulness

Traveling to a different jobsite almost every week, sometimes two or three in a single week, gives a pretty direct read on where the industry is actually headed. Lately, that read has been genuinely encouraging: a real, growing sense of hopefulness among leaders who are investing seriously in their people.

In just the past month alone, five separate major contractors independently reached out asking for help building superintendent and project manager training programs. The month before that, several more. This is not one company having a good idea. It is a pattern showing up again and again, in companies that have no connection to each other at all.

The Real Pain: An Industry Used to Going It Alone

The real pain, historically, is that construction leaders have mostly had to figure things out through grit and isolation. Formal training investment has been the exception rather than the norm, and when things went wrong on a jobsite, the default explanation was rarely a hard look at the system, it was blaming whoever happened to be closest to the problem.

That pattern left a lot of genuinely capable people without the structure or support they needed to grow, and it left a lot of hardworking crews carrying the blame for issues that were never really theirs to own in the first place.

The Failure Pattern: Blaming the Worker Instead of Building the System

The failure pattern is defaulting to blaming workers, foremen, or trade partners the moment something goes wrong, rather than asking whether the conditions around them were ever actually set up for success. It is an easy explanation to reach for, and it is very often the wrong one.

A telling moment came during a recent project tour with international visitors. One comment stood out: the workers on this site were genuinely focused, showing up prepared, and doing exactly what they were being paid to do. That observation was not really about any one group of workers being inherently better than another. It was a direct reflection of how well a crew is actually managed and supported.

A few signs tend to show up when a leader has slipped into blaming workers instead of examining the system around them, and they are worth checking honestly:

A recurring jobsite problem gets explained as “that’s just how workers are” rather than examined for gaps in training, planning, or support.
Leadership assumes worker discipline is the core issue without first asking whether the crew was ever given a clean, safe, well-organized environment to work in.
Genuine outliers, someone showing up impaired or making a serious mistake, get treated as proof of a broader pattern rather than a rare exception.

This Isn’t Naive Optimism, It’s a Pattern Worth Naming

It is fair to be skeptical of any one person’s optimistic read on an entire industry, especially someone who spends most of their time working directly with companies already motivated to improve. That bias is worth acknowledging honestly.

But the pattern here is not just anecdotal color, it is showing up independently, in companies with no coordination or awareness of each other, converging on remarkably similar solutions at the same time. That kind of unplanned convergence is a much stronger signal than any single success story on its own.

Two Companies, the Same Idea, Never Talking to Each Other

Here is a striking example. Two separate contractors, without any contact or coordination with one another, independently built nearly identical visual training boards for onboarding their superintendents and project managers, mapping out a step-by-step development path complete with training milestones, recommended resources, and clear role progression.

Neither company knew the other was doing this. Both arrived at a strikingly similar solution to the same real problem: giving their field leaders an actual, visible path to grow along, rather than leaving them to figure it out alone. That kind of independent convergence, happening in more than one place at once, is exactly the kind of signal worth paying attention to.

Why It Matters: Momentum Compounds

This matters because these shifts tend to build on each other rather than stay isolated. Flow-based scheduling approaches like Takt planning, once a niche topic mentioned briefly at a handful of industry events, are now a majority topic at many Lean construction gatherings, backed by a rapidly growing base of case studies and real project results.

It also matters because the conversation around mental health in construction is finally moving past surface-level awareness toward real, usable training and support. That shift carries real weight: construction already loses far too many people to workplace fatalities, and it loses several times that number to suicide, a sobering reality that makes genuine mental health support far more than a nice-to-have.

Teach the Framework: What’s Actually Driving the Shift

Three things appear to be driving this momentum together. First, leadership is finally investing directly in structured training for superintendents and project managers, rather than assuming natural talent and grit alone will carry people through. Second, more leaders are rejecting the reflexive instinct to blame workers for problems that actually trace back to planning, readiness, and management. Third, flow-based scheduling approaches are scaling rapidly as more companies see direct, measurable results compared to older, less transparent scheduling methods.

None of these three shifts happens in isolation. Better training produces leaders who plan more thoughtfully. Better planning produces conditions where workers can actually succeed, which undercuts the old habit of blaming them by default. And visible results from better scheduling approaches give leadership real evidence to keep investing further.

A few practical signs help identify whether a company is genuinely part of this shift or still stuck in old patterns:

A defined, visible training path exists for superintendents and project managers, rather than an assumption that people will simply figure it out.
The default explanation for jobsite problems looks first at planning, readiness, and management before ever blaming the workers involved.
Scheduling has moved, or is actively moving, toward transparent, flow-based approaches rather than staying locked into older, harder-to-follow formats.

Turning This Into Daily Practice

Start by asking a few honest questions about your own organization. Is there an actual training path for people entering leadership roles, or are they simply handed a project and left to sink or swim? When something goes wrong on a jobsite, is the first instinct to examine the system, or to blame whoever was closest to the problem? And is your scheduling approach actually built for transparency and flow, or still running on old habits that quietly work against your own team?

None of these questions require a perfect answer immediately. They require an honest one, and a willingness to start closing whatever gap the honest answer reveals.

Connecting It Back to Building People, Not Just Projects

None of this happens without leaders willing to invest in training, examine their own systems honestly, and give their people a real, visible path forward instead of leaving growth to chance. That kind of investment is exactly what is quietly reshaping the industry right now, one company at a time.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow, and be part of the same momentum already building across the industry.

The Challenge

So here is the challenge worth carrying forward: the next time something goes wrong on your project, resist the instinct to blame the people closest to it, and look honestly at the system around them instead. As Jason put it plainly, “We’ve got to stop blaming our workers for the problems in our industry.” On we go.

FAQ

Why does Jason believe momentum is genuinely building in the construction industry right now?

In just the past couple of months, multiple major contractors independently reached out asking for help building superintendent and project manager training programs, with no coordination between them. That kind of unplanned convergence across unrelated companies is a stronger signal than any single success story.

Why is blaming workers for jobsite problems usually the wrong explanation?

Workers who are well managed, given clean and organized conditions, and properly supported tend to perform well consistently. When problems repeat, the more useful question is usually whether planning, training, and readiness were actually in place, not whether the workers themselves are simply undisciplined.

What is the significance of two companies independently building similar training programs?

It shows the need for a structured leadership development path is being recognized broadly across the industry, not just by one forward-thinking company. That kind of parallel, uncoordinated progress suggests a genuine shift rather than an isolated trend.

Why is flow-based scheduling like Takt planning scaling so quickly right now?

As more companies adopt it and share real project results, the case studies and success stories compound, giving other leaders concrete evidence rather than just theory. That visible proof accelerates adoption further as more organizations see measurable improvements over older scheduling methods.

Why does Jason connect construction’s mental health conversation to this broader industry shift?

As training and support systems improve, industry conversations are also moving past generic awareness toward real, usable mental health support. Given how significantly construction is affected by suicide, alongside workplace fatalities, this shift toward genuine, practical support matters as much as any technical or training improvement.

If you want to learn more we have:

Discover Jason’s Expertise:

Super Path for Growth

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

Read 17 min

Is There a Path?

A young professional recently shared that showing genuine interest in Lean principles was a real factor in landing a final interview with a new company. That same person admitted something else too: implementing those same principles at their current job had been an uphill battle, with little support or clear direction for how to actually grow into that kind of role.

That combination, real enthusiasm paired with no defined path forward, is far more common than it should be. It raises a question worth asking honestly about any organization: when someone comes on board, is there an actual path mapped out for them, week by week, month by month, or are they simply left to figure it out alone?

The Real Pain: Talented People With No Defined Next Step

The real pain is that so many genuinely talented superintendents and project managers progress almost entirely by accident, through personal grit, a lucky mentor, or sheer persistence, rather than through any deliberate structure their company put in place. Ambition alone is not the problem. The absence of a real path is.

People who want to grow and improve, who read on their own time, who chase down extra training, deserve more than vague encouragement. Without a mapped sequence of skills, habits, and milestones, that motivation has nowhere clear to go.

The Failure Pattern: Sink or Swim, Hope for the Best

The failure pattern is hiring good people and simply trusting them to figure out the rest on their own. Handing someone a project and hoping their natural talent carries them through is not a development strategy, it is an absence of one.

Without structured onboarding, a genuine reading and learning habit, real software fluency, and hands-on mentorship, even talented people plateau far earlier than they should, not because they lack potential, but because nobody ever built them an actual path to grow along.

A few signs tend to show up when a company has no real career progression path for its field leaders, and they are worth checking honestly:

New superintendents or PMs receive a project assignment with little to no structured onboarding beyond basic company policy.
There is no expectation or support around ongoing reading, training, or skill development beyond whatever someone pursues entirely on their own.
Nobody can clearly describe what the next concrete step looks like for a specific person’s growth, this month, this quarter, or this year.

This Isn’t About Perfection, It’s About Having Any Path At All

None of this means a company is failing its people intentionally. Most organizations never sat down and deliberately mapped this out, not because leadership does not care, but because nobody ever framed it as something worth designing on purpose.

Building a real path does not require an elaborate, fully polished system from day one. It requires a deliberate sequence: foundational skills first, then structured training, then real habits practiced consistently, then advanced development as someone grows into greater responsibility.

What a Real Path Can Look Like

Here is one example of what a genuine sequence can look like in practice. It starts with foundational skills: surveying and layout basics, reading lift drawings, frontline quality and safety habits, visualizing work in three dimensions, and building a personal organization system before anyone worries about advanced leadership concepts. From there, company-specific onboarding and real software fluency follow, learning the actual tools of the trade, scheduling software, drawing platforms, whatever the role specifically requires.

Layered alongside that technical foundation is a genuine reading habit, a book every week, every two weeks, or every month, consistently sustained over time. Only once that foundation is solid does more advanced, hands-on training make sense, structured experiences that stretch someone’s expectations of what they are capable of and immerse them in real production planning and problem solving. After that comes an implementation phase, where concepts get tested and proven on an actual project rather than staying theoretical, followed by some form of verification or certification that confirms the learning has genuinely translated into real capability. One contractor built this entire sequence into a simple visual board, mapping out step by step what a new superintendent or project engineer should be working on, complete with the specific books, videos, and resources tied to each stage.

Why It Matters: There’s a Real Correlation Between Learning and Opportunity

This matters because there is a real, observable pattern between people who commit to ongoing learning and the opportunities that come their way afterward. The professional who leaned into Lean concepts on their own initiative ended up in a final interview partly because of that same commitment.

Companies that build a genuine path for their people are not just being generous, they are directly investing in retention and performance. People who can see where they are headed, and what specific steps get them there, are far more likely to stay engaged and keep growing than people left to guess at their own trajectory.

Teach the Framework: Build Habits Before You Build Titles

A title or a promotion handed to someone without the underlying habits and skills to support it just sets that person up to struggle. Real capability gets built through small, consistent habits practiced daily, not a single training event or a new job title alone.

Three specific habits show up again and again in genuinely strong builders: studying the drawings for fifteen to thirty minutes every single day, spending real time in the schedule daily to see what is coming, and taking regular reflection walks around the actual project to notice what the site itself is communicating, cleanliness, morale, pace, quality. None of these habits require a big training budget. They require consistency, and a company willing to expect and support them.

A few practical elements turn a vague sense of “we should develop our people” into an actual, usable path:

A clear, sequenced list of foundational skills and software every new superintendent or PM needs to build before advancing further.
A genuine, supported reading habit, with a specific list of recommended books tied to the role and stage of someone’s career.
A visible way to track progress, whether that is a simple checklist, a shared board, or a formal onboarding program, so people can see their own trajectory rather than guessing at it.

Turning This Into Daily Practice

Building this does not require solving the entire system at once. Start by mapping even a basic version: what should someone be doing in their first month, their first quarter, their first year, and what specific books, skills, or training milestones mark each step along the way.

Pair that structure with daily habits, studying drawings, reviewing the schedule, walking the site, that build real capability over time, rather than relying entirely on occasional formal training events to carry the weight of someone’s entire development.

Connecting It Back to Building People, Not Just Projects

None of this happens without leaders willing to treat career development as something worth designing deliberately, rather than something that simply happens or does not, depending on luck and individual initiative. Building a genuine path is exactly the kind of investment that keeps strong people growing instead of stalling out or leaving.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow, including building the kind of career path that turns potential into real, lasting capability.

The Challenge

So here is the challenge worth carrying back to your own organization: look honestly at what happens when someone new comes on board. Is there something specific they should be working on every week, every month, and is that path actually mapped out anywhere? As Jason put it plainly, “Is there something where every week, every month, they can be working on something? Is that mapped out?” On we go.

FAQ

Why do so many superintendents and PMs end up progressing without any real company support?

Most organizations never deliberately designed a career path, not out of neglect, but because nobody framed it as something worth building on purpose. Without that structure, motivated people often progress through personal initiative and persistence rather than any real system.

What foundational skills should come before advanced leadership training?

Basics like surveying and layout, reading lift drawings, frontline quality and safety habits, three-dimensional visualization, and a personal organization system all belong early in someone’s development. Building this foundation first makes later, more advanced training far more effective.

Why does a consistent reading habit matter so much in this path?

There is a real, observable pattern between people who commit to ongoing learning, through books, podcasts, and outside training, and the career opportunities that follow. A sustained reading habit, even just a book a month, reflects and reinforces the kind of continual growth that tends to open doors.

What are the three daily habits that build real builder capability?

Studying the drawings for fifteen to thirty minutes daily, spending real time in the schedule to see what is coming, and taking regular reflection walks around the project to notice its condition and morale. These small, consistent habits build far more lasting capability than occasional formal training alone.

How can a company start building a career path if it doesn’t have one yet?

Start with a simple, sequenced outline of what someone should be working on in their first month, quarter, and year, paired with specific skills, software, and recommended reading tied to each stage. Making that path visible, even through something as simple as a shared checklist or board, helps people see their own trajectory instead of guessing at it.

If you want to learn more we have:

Discover Jason’s Expertise:

The TRIAD!

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

Read 17 min

“I’m Really Excited About This” (Said Like You’re Not)

At a recent training, someone described what they were passionate about using genuinely excited words, “I’m really fired up about this,” but said them in a flat, low-energy, almost monotone voice. The words said one thing. Everything else about how they were delivered said something completely different.

That mismatch matters more than it seems. When your body and tone contradict your words, the message that actually gets reinforced is the physical one, not the verbal one. Saying you are excited without ever sounding or standing like it does not just fail to convey excitement, it can actively teach your own mind the opposite lesson.

The Real Pain: Showing Up Flat When It Matters Most

The real pain is showing up for something that genuinely matters, a big presentation, a hard conversation, a leadership moment, while your posture, tone, and word choice are all quietly working against the outcome you actually want. Nobody does this on purpose. It usually just happens by default, without anyone noticing the mismatch until performance suffers.

Most people treat mindset as something that happens purely in the head, disconnected from how they are standing, breathing, or phrasing things out loud. That disconnect is exactly where performance quietly leaks away.

The Failure Pattern: Ignoring the Body’s Role in Performance

The failure pattern is assuming that willpower or good intentions alone are enough to get into a strong, capable state, without paying attention to the physical and verbal signals reinforcing, or undermining, that intention. Slouched shoulders, a hesitant tone, and hedged language like “I’ll try” all quietly work against someone’s stated goals, even when their intentions are genuinely good.

A simple demonstration makes this vivid. Ask someone to hold their arm out and resist as you try to move it while they say, out loud and with real conviction, “I will, I will, I will.” Then ask them to repeat the exercise saying “I will try, I will try, I will try” instead. The difference in how firmly that arm holds is worth experiencing firsthand rather than just reading about.

A few signs tend to show up when physiology and language are quietly working against someone’s own intentions, and they are worth checking honestly:

Words describing confidence or excitement get delivered in a flat, low-energy tone that contradicts the message.
Hedged language like “I’ll try” or “hopefully” gets used in place of direct, committed language like “I will.”
Posture, slouched shoulders, closed body language, arms crossed, undercuts a message meant to project confidence or readiness.

This Isn’t Magic, It’s a Demonstration Worth Trying

None of this requires believing in anything mystical. It is worth trying the arm-hold demonstration directly, with a partner, rather than simply taking the concept on faith. The physical difference between committed language and hedged language tends to be immediately noticeable once you actually feel it.

This connects to a well-known personal development idea sometimes called neuro-associative conditioning, the general notion that repeated physical states and language patterns train the mind to associate certain words and postures with certain outcomes over time. Treat it as a practical tool worth testing for yourself, rather than a scientific claim requiring blind acceptance.

Building the Triad on Paper

Here is a specific exercise worth doing directly, borrowed from a business coaching session. Start by recalling a specific moment when you were genuinely at your best, a moment of real confidence, joy, or accomplishment. From that memory, identify at least three distinct emotions you felt in that moment.

One real example: the three emotions identified were a sense of contribution and giving, a feeling of love, and a sense of hope tied to learning and growth. From there, three columns get built on paper: physiology, describing exactly how your body felt and looked in that peak moment, shoulders back, smiling, looking up; focus, describing what your mind was concentrated on, in this case, bringing out the best in others; and language, the specific words and phrases that captured that state, spoken in the present tense as if already true.

Why It Matters: You Become What You Rehearse

This matters because repeating a specific physiology, focus, and set of words is not just positive thinking, it is deliberate rehearsal. The more consistently someone practices standing, focusing, and speaking the way they do in their best moments, the more accessible that state becomes on demand, rather than something that only shows up by accident.

This connects to a related habit worth mentioning honestly: reframing negative self-talk by writing it down, crossing it out, and replacing it with a truer, more constructive statement next to it. This is a personal practice worth trying as one tool among many, not a replacement for professional support if someone is dealing with more serious or persistent mental health struggles, which deserve real professional care.

Teach the Framework: Physiology, Focus, Language

The three components work together as a system. Physiology comes first: standing tall, shoulders back, smiling, looking up, rather than slouched or closed off. This is not just cosmetic, posture genuinely affects energy, alertness, and readiness to perform.

Focus comes second: deliberately choosing what to concentrate on, framed in terms of success rather than failure. Someone learning a name should think “what is this person’s name” rather than repeating “I’m bad with names.” Someone facing a challenge should focus on winning it, not on the possibility of losing. Language comes third, and it may matter the most: the specific words used, especially the difference between committed language, “I will,” and hedged language, “I will try,” which studies in behavioral psychology and common coaching practice both suggest carries real weight in how confidently a person actually shows up.

A few practical steps turn this into something usable rather than just theory:

Recall a specific peak moment and identify at least three genuine emotions felt during it, rather than generic ones.
Write out your own physiology, focus, and language columns based on that memory, being as specific as possible.
Practice running through all three, posture, focused thought, and spoken words, together, especially before moments that genuinely require your best effort.

Turning This Into Daily Practice

This does not need to be complicated. Write your own triad once, on paper, and revisit it two or three times a day, especially before something important: a difficult conversation, a big presentation, a moment that calls for real confidence and energy.

Physically get into the posture, mentally return to the focus, and say the words out loud, ideally with real conviction rather than a flat, disconnected tone. Over time, this rehearsal makes a strong, capable state easier to access consistently, rather than something that only shows up when circumstances happen to be perfect.

Connecting It Back to Building People, Not Just Projects

None of this happens without leaders willing to take their own mindset and physical presence as seriously as they take a project schedule. Building a genuine, rehearsed sense of confidence and focus is exactly the kind of personal discipline that shows up in how someone leads a team, a meeting, or a difficult conversation.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow, including the personal habits that help leaders show up at their best when it matters most.

The Challenge

So here is the challenge worth carrying into this week: build your own triad on paper, physiology, focus, and language, based on a real peak moment, and practice running through it before your next high-stakes conversation or challenge. As Jason put it plainly, “Whatever we say we are is what we are.” On we go.

FAQ

What is “the triad” in this context?

It refers to three components, physiology, focus, and language, that work together to help someone access a confident, high-performing mental and physical state on demand. Writing out your own specific version of each, based on a real peak moment, turns the concept into a practical daily tool.

Why does the difference between “I will” and “I will try” matter so much?

In a simple demonstration, people holding a strong physical stance while saying “I will” tend to feel noticeably more resistant to being moved than when saying “I will try.” The specific words used appear to carry real weight in how committed and capable a person actually feels in the moment.

Is the science behind neuro-associative conditioning fully established?

It is a widely used concept in personal development and coaching circles, built on the general idea that repeated physical states and language patterns can train mental associations over time. It is worth treating as a practical tool to test for yourself rather than a rigorously proven scientific claim.

How does posture affect performance, beyond just looking confident?

Standing tall with shoulders back and looking up tends to increase alertness and readiness compared to a slouched, closed posture. This physical state feeds back into focus and language, making all three components work together rather than separately.

Is writing down and reframing negative self-talk a substitute for professional mental health support?

No. It can be a useful personal practice for building healthier daily self-talk, but it is not a replacement for professional care when someone is dealing with more serious or persistent mental health struggles, which deserve real, qualified support.

If you want to learn more we have:

Discover Jason’s Expertise:

Get them to their Best Self

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

Read 17 min

“You’re Doing Great” Isn’t Feedback

As a project director walking a jobsite, the habit was simple and, in hindsight, hollow: great, great, great, looking good, looking good. Everything technically met minimum clean standards, minimum safety standards, minimum everything, so there was rarely any real feedback offered, just a quick round of compliments and a pat on the back.

Looking back, that habit was genuinely disappointing to the people receiving it, even if it felt generous in the moment. Meeting a minimum standard is not the same as knowing where someone actually wants to go in their career, and confusing the two meant an entire team was quietly being shortchanged on something they actually needed.

The Real Pain: Confusing Praise, Criticism, and Real Feedback

The real pain is that praise, criticism, and genuine feedback for improvement constantly get mixed up, even though they are three completely different things. Praise celebrates a step someone already took. Criticism tells someone they are near the bottom and likely to stay there. Feedback for improvement helps someone take their next step forward, regardless of where they currently stand on that spectrum.

Someone performing excellently does not need less feedback than someone struggling, they need a different kind: guidance toward the specific next step that gets them closer to where they are actually trying to go.

The Failure Pattern: Feedback That Ignores the Destination

The failure pattern is giving feedback, or withholding it entirely, based only on whether someone currently meets a minimum bar, without ever knowing or referencing what that person actually wants to become. A superintendent who has met every standard on the checklist can still be given nothing but generic praise, purely because there was no known target to coach them toward.

This quietly punishes strong performers the most. The person doing everything right gets the least useful feedback, simply because their work looks fine on the surface, even though they may be one specific insight away from their next real breakthrough.

A few signs tend to show up when feedback in an organization has collapsed into just praise or just criticism, and they are worth checking honestly:

Strong performers consistently receive generic compliments rather than specific, forward-looking guidance tied to their own goals.
Leaders assume someone doing well “doesn’t need” feedback, rather than asking what their next step actually is.
Nobody on the team can clearly state what career or personal trajectory their manager is actually helping them work toward.

This Isn’t Nitpicking, It’s a Gift

None of this means constantly pointing out flaws or nitpicking every small imperfection. A powerful training experience makes the real distinction clear: performing at ninety-nine percent and still being told, clearly and kindly, exactly what that remaining one percent looked like was not criticism, it was a genuine gift.

The difference is not whether a correction gets offered. It is whether that correction is tied to where the person is actually trying to go. Feedback rooted in someone’s own stated goals lands as coaching. The identical observation, offered without any connection to their goals, can land as mere nitpicking instead.

The Hoist Operator Who Became a Field Engineer

Here is what noticing someone’s real trajectory can unlock. A hoist operator on one project was simply doing his job, operating equipment, showing up, working hard. A couple of people noticed something more in him and made him an offer: learn English, and we will personally teach you to become a field engineer.

That one conversation changed the entire direction of his career. He is, by every account, wildly successful today. He likely would have kept working hard and doing fine regardless. But it is worth asking honestly: would he have had the same opportunities without that specific, trajectory-aware conversation, offered by people willing to notice him and say something?

Why It Matters: People Are One Conversation Away

This matters because so many people are genuinely one honest conversation away from their next real step, a promotion, a stronger marriage, better mental health, a completely different career trajectory, and that conversation only happens if someone else is willing to notice them and actually say something.

Leaders sometimes talk themselves out of offering feedback, assuming nobody wants their opinion, or worrying about talking too much. In practice, the opposite tends to be true. Naming what someone needs to hear, connected clearly to where they want to go, is rarely unwelcome when it is offered with genuine care.

Teach the Framework: Know the Goal, Notice the Person, Name the Step

Real trajectory-based feedback rests on three things working together. First, know what the other person’s actual goal is, not what you assume they should want, but what they have genuinely told you they are working toward. Second, actually notice people, which requires stepping outside your own performance and self-focus long enough to pay real attention to someone else’s. Third, name a specific, concrete next step tied directly to their stated goal, rather than offering vague praise or blanket criticism untethered to anything they actually care about.

Skipping any of these three steps breaks the whole process. Feedback without a known goal becomes generic. Noticing without naming a next step stays a nice observation that never becomes useful coaching. And none of it works if the person giving feedback never stops long enough to actually see what is happening with someone else.

A few practical habits keep feedback anchored to someone’s real trajectory instead of generic praise or criticism:

Ask people directly what they are working toward, in their career or personally, rather than assuming you already know.
Frame feedback as “I noticed this, and if you did this, it would help you get closer to that,” connecting the observation directly to their stated goal.
Offer this kind of feedback to strong performers just as often as to those who are struggling, since meeting a minimum standard is not the same as having no room left to grow.

Turning This Into Daily Practice

This starts with a simple habit: ask people what they actually want, out loud, and remember the answer. That single piece of information turns every future observation into potential coaching instead of generic praise or unconnected criticism.

Being willing to go first with vulnerability also matters here. Leaders who openly discuss their own goals, struggles, and growth areas tend to create space for others to do the same, whether that means a career goal, a personal struggle, or something as significant as mental health. Normalizing those conversations starts with someone willing to speak first.

Connecting It Back to Building People, Not Just Projects

None of this happens without leaders willing to actually learn what their people want, rather than assuming a compliment or a correction is enough on its own. Building that habit turns ordinary feedback into something genuinely useful for the specific person receiving it.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow, including how leaders coach people toward their own real goals instead of a generic standard.

The Challenge

So here is the challenge worth carrying into your next conversation with a direct report, a trade partner, or a colleague: find out where they actually want to go, and offer them one specific, concrete step to help get them there. As Jason put it plainly, “We should be providing feedback for improvement based on where people want to go, not on just what they need to improve in the current moment.” On we go.

FAQ

What is the real difference between praise, criticism, and feedback for improvement?

Praise celebrates a step someone already took, and criticism tells someone they are near the bottom and likely to stay there. Feedback for improvement helps someone take their next step forward regardless of where they currently stand, which makes it useful for both struggling and excelling performers alike.

Why do strong performers often receive the least useful feedback?

Leaders often assume someone meeting every standard does not need anything beyond praise, since there is no obvious problem to correct. Without knowing that person’s actual next goal, feedback defaults to generic compliments instead of a specific, meaningful next step.

How is pointing out a missing one percent different from nitpicking?

The difference lies in whether the observation is connected to the person’s own stated goals. Feedback tied to where someone genuinely wants to go lands as coaching, while the same observation offered without that connection can feel like nitpicking instead.

Why does noticing someone’s potential matter so much, using the hoist operator example?

A specific, trajectory-aware conversation, offering to teach him to become a field engineer if he learned English, changed the direction of his entire career. Without someone taking the time to notice him and say something directly, that opportunity may never have come up at all.

What are the three things needed to give real, trajectory-based feedback?

Know what the person’s actual goal is, notice them enough to see how they are progressing toward it, and name one specific step that would move them closer. Skipping any of these three turns the feedback into either generic praise, an unconnected observation, or criticism with no real direction attached.

If you want to learn more we have:

Discover Jason’s Expertise:

Modeling What You Want, Feat. Ava Schroeder

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

Read 16 min

Cheering From the Sideline

At a recent training event, one participant was struggling to complete a physical exercise, unable to muster the energy or enthusiasm needed to push through it. Their peers gathered around, clapping and shouting encouragement, urging them to give more energy, more effort, more enthusiasm.

The problem was easy to spot from just a few feet away: the peers doing the encouraging were not bringing much more energy themselves. Watching the moment unfold, one observer pointed out exactly what was missing, if they wanted this person to bring more energy, they needed to bring more energy themselves, right alongside them, not just shout instructions from the sideline.

The Real Pain: Telling People What to Do and Expecting Them to Just Get It

The real pain shows up constantly in leadership, coaching, and even parenting: explaining something once, verbally, and then feeling frustrated when it does not land the way it was intended. It is an easy trap to fall into, and an easy one to admit honestly.

Telling someone what to do and simply expecting them to understand exactly what was meant, without ever demonstrating it, sets both people up for frustration. The instructor feels unheard, and the learner feels lost, even when both are genuinely trying.

The Failure Pattern: Coaching From Outside the Boat

The failure pattern is coaching from a distance instead of getting directly involved. A personal example makes this painfully clear: teaching a daughter to drive a boat by staying outside of it, pointing, gesturing, and shouting directions from the water or the dock, rather than sitting beside her in the driver’s seat.

That approach produced exactly what you would expect: frustration, confusion, and a genuinely bad experience for both people involved. The instructions were not wrong. The delivery method was.

A few signs tend to show up when coaching has gotten stuck at telling instead of modeling, and they are worth checking honestly:

Instructions get repeated louder or more forcefully when they are not landing, rather than being demonstrated hands-on instead.
The person giving feedback stays physically or emotionally at a distance rather than working directly alongside the person being coached.
Frustration builds on both sides even though the actual instructions being given are technically correct.

This Isn’t About Being a Bad Leader, It’s About How People Actually Learn

None of this means someone is a poor leader or a poor parent. It usually just means the coaching style being used does not match how the other person actually learns best.

Some people absorb instructions well through explanation alone. Others need to see it demonstrated. Still others, often described as kinesthetic learners, need to physically experience something alongside someone else before it truly clicks. Recognizing which one applies to the person in front of you is not a minor detail, it is the whole difference between a smooth learning experience and a frustrating one.

Sitting in the Driver’s Seat Together

Here is what changed everything in that same boat-driving story. On a different day, instead of coaching from outside the boat, the approach shifted entirely: sitting directly in the driver’s seat together, hands near the controls, actually driving alongside her rather than narrating from a distance.

The difference was immediate and lasting. What had been a frustrating, tense experience became a genuinely positive one, and that same daughter is now considered one of the best boat drivers around. Nothing about the actual instructions changed. What changed was showing up right there in the seat with her instead of coaching from somewhere else entirely.

Why It Matters: Confidence Comes From the Right Starting Point

This matters because how someone starts learning something shapes their confidence far more than most people realize. Starting with encouragement and a modeled example, someone right there doing it alongside you, builds a positive first experience. Starting with repeated failure and correction from a distance builds stress and self-doubt instead, even if the person eventually gets there anyway.

The boot camp moment made this visible in real time. The individual struggling with the exercise did eventually get the support they needed, once their peers actually joined in physically rather than just cheering from the side. But starting that way from the very beginning would have meant more confidence sooner, and a far less stressful path to the same result.

Teach the Framework: Explain, Demonstrate, Guide, Enable

This connects directly to a training model adapted from Boy Scouts leadership development: explain the concept clearly, demonstrate the skill yourself, guide the learner through practice with real, hands-on feedback, and only then enable them to perform independently. Skipping straight from explaining to expecting independent execution leaves out the two steps that actually build real capability and confidence.

Applied to a jobsite, this might mean physically walking a new team member through a task rather than just describing it, or working directly alongside a struggling crew member instead of correcting their work from across the room. Applied at home, it looks exactly like sitting in the driver’s seat instead of shouting instructions from the dock.

A few practical questions help identify when this method is needed instead of a purely verbal explanation:

Has this person already been told what to do multiple times without real improvement, suggesting the delivery method itself needs to change?
Would physically demonstrating this task, or doing it alongside them, likely help more than a further verbal explanation?
Is the feedback being given from a comfortable distance, or is it happening directly alongside the person doing the work?

Turning This Into Daily Practice

Before repeating an instruction louder or more forcefully, pause and ask whether the person in front of you might actually need to see it modeled, or need you working directly beside them, rather than simply hearing it again. That small shift in approach often solves what more explanation never could.

This applies to trade partners learning a new process, new hires figuring out a task for the first time, and family members picking up a new skill, all in exactly the same way. The method rarely needs to change. Often, showing up right next to the person is the actual missing piece.

Connecting It Back to Building People, Not Just Projects

None of this happens automatically, and it takes real humility to recognize when telling someone what to do has not worked and a different approach is needed instead. Building that instinct, to explain, demonstrate, guide, and then enable, is exactly the kind of coaching skill that turns frustration into genuine confidence.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow, including how leaders coach and train the people closest to the work.

The Challenge

So here is the challenge worth carrying into your next coaching moment: instead of just telling someone what to do from a distance, get in the boat with them and do it together. As Jason put it plainly, “Sometimes when we are aiming to help somebody instead of just telling them what to do, we need to get out there and do it with them.” On we go.

FAQ

What is the “Explain, Demonstrate, Guide, Enable” method?

It is a training model, adapted from Boy Scouts leadership development, where a skill is first explained, then physically demonstrated, then practiced together with real-time guidance, and only then handed off for independent performance. Skipping the demonstration and guidance steps often leaves learners stuck, even after a clear explanation.

Why didn’t simply explaining how to drive a boat work well?

Coaching from a distance, pointing and shouting instructions rather than sitting alongside the learner, created frustration for both people even though the instructions themselves were accurate. The delivery method, not the content, was the actual problem.

How can a leader tell if someone needs a demonstration instead of another verbal explanation?

If an instruction has already been repeated multiple times without real improvement, that is a strong signal the delivery method needs to change rather than the message itself. Kinesthetic learners in particular often need to physically experience a task alongside someone else before it truly clicks.

Does this mean verbal instructions are never effective?

No, some people learn well through explanation alone. The key is recognizing that not everyone learns the same way, and being willing to shift to demonstration or hands-on guidance when verbal instruction alone is not landing.

How does starting with encouragement and modeling affect someone’s confidence?

Starting with a modeled example and genuine support builds a positive first experience and faster confidence. Starting with repeated failure and correction from a distance can still get someone to the same skill level eventually, but usually with far more unnecessary stress along the way.

If you want to learn more we have:

Discover Jason’s Expertise:

Do This Before Building Your Project! Feat. Brandon Montero

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

Read 17 min

A Big-Time GS With Paint on His Shoes

On a $360 million project, a general superintendent could have been anywhere else that morning. Instead, he was out with the survey crew, string and spray paint in hand, laying out the entire foundation himself: every pier, the full building perimeter, major mat footings, elevator pits, all of it, with paint on his boots to prove it.

Asked why a leader at that level was doing layout work personally, his answer was simple: he wanted to know how the building actually related to everything around it, and whether anything was in the way. That instinct paid off directly. Comparing his caisson locations against the blue stake marks on the ground, he spotted a duct bank running straight through one of them, something the drawings never showed.

The Real Pain: Assuming the Pad Is Ready

The real pain shows up when a team simply trusts that a site is clear and ready because the drawings say so. Existing conditions, utilities, easements, even roads that look permanent, do not always make it fully onto the design documents, and that gap can sit invisible until construction is already underway.

On one project involving a road widening, the existing road in front of the site looked so finished and permanent that nobody questioned whether it was staying put. It turned out that road itself was part of what needed to change, and nobody had accurately confirmed the property line or how the future building would actually relate to the street until the team physically laid the project out on the ground.

The Failure Pattern: Trusting the Drawings Over the Ground

The failure pattern is treating the design set as a complete, guaranteed picture of reality rather than a starting point that still needs field verification. Drawings reflect what was known and captured at the time they were made, not necessarily everything that actually exists on site.

This becomes especially risky with utilities. A gas line, a water line, an electrical duct bank, a telecommunications cable, any of these can sit exactly where new construction needs to go, and if nobody physically checks for that conflict before excavation begins, the discovery happens at the worst possible time.

A few signs tend to show up when a project is trusting paper over verified ground conditions, and they are worth checking honestly:

Existing utilities and site conditions are assumed to be fully captured by the design drawings without any independent field verification.
Survey marks and layout points are used directly for excavation planning without ever being physically cross-checked.
A site feature, like a road, fence line, or utility pole, is assumed to be permanent and unrelated to the project simply because it looks established.

This Isn’t Paranoia, It’s the Standard Surveyor Practice

None of this is about distrust of designers, other surveyors, or utility companies. Double-checking a civil engineer’s elevations, an architect’s grid dimensions, or another surveyor’s layout marks is not an insult to their work, it is simply standard, professional practice.

Data received from someone else cannot be treated as verified until it has actually been checked. That applies to survey marks just as much as it applies to drawings, specifications, or as-built information from an owner.

The Duct Bank, the Water Line, and the 100-Pair Cable

Here is what catching these conflicts early actually looks like. On one healthcare project, a hundred-pair telecommunications cable providing internet service to an adjacent lot sat directly in the path of planned construction, completely absent from any drawing. Locating that cable meant contacting the utility provider directly and racing to get it relocated just before construction was set to begin.

On another project, a water line near a planned stairwell turned out to be both closer and deeper than the plans indicated, putting it directly in the path of the excavation. Because the team had physically laid out the building and compared it against real utility locations ahead of time, there was enough lead time to bring in shoring and protect the line without ever delaying the schedule. Neither outcome was luck. Both came from refusing to assume the pad was simply ready.

Why It Matters: Utility Conflicts Are Some of the Biggest Roadblocks

This matters because relocating a major utility is not a quick fix. Rerouting something like a major electrical duct bank can take five to six months once a utility company gets involved, timeline that has nothing to do with how fast a construction crew can move and everything to do with a utility provider’s own process.

Catching a conflict during layout, before a single shovel hits the ground, turns a potential months-long delay into a manageable adjustment. Catching it after excavation has already begun turns it into a real crisis.

Teach the Framework: Layout as a Verification System

The right process starts well before boots hit the site. Gather every available as-built and existing conditions record from the civil engineer, the owner, and the city. Get BlueStake completed for public utilities, and bring in a private utility locator or potholing company specifically for anything inside the private property line, since BlueStake typically only covers up to the building connection point.

From there, physically lay the building out on the ground, string, spray paint, or lath at property corners and along property lines, so the actual footprint and its relationship to everything nearby becomes visible rather than theoretical. Then double-check that layout independently: pull a tape from the property line to the street centerline, and from the property line to the building’s grid lines, as a genuine secondary confirmation rather than assuming the initial survey marks are automatically correct.

A few practical steps make this verification process real rather than symbolic:

Request existing conditions and utility as-built data directly from the civil engineer and owner before any layout begins.
Bring in a private utility locator or potholing company for anything inside the property line that public utility locating services do not typically cover.
Independently verify layout with an actual tape measurement, rather than trusting survey stakes or another party’s marks without confirmation.

Turning This Into Daily Practice

None of this has lasting value if it only exists as string, paint, and memory. BlueStake marks fade, potholes get filled back in, and layout strings eventually come down, so capturing everything found in the field, in CAD or AutoCAD, turns a temporary discovery into a permanent, reusable record.

That documented overlay means the same visualization can be recreated anytime it is needed later in the project, rather than depending on a handful of people remembering exactly where a conflict was found months earlier.

Connecting It Back to Building People, Not Just Projects

None of this happens without leaders willing to physically verify conditions themselves rather than assuming the paperwork already covers it. That habit, built early and consistently, is exactly what prevents a hidden utility conflict from turning into a project-defining crisis.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow, including the pre-construction verification habits that catch conflicts before they become roadblocks.

The Challenge

So here is the challenge worth carrying onto your next project: before you trust that the pad is ready, physically lay out your building and compare it against verified existing conditions, not just the drawings. As one general superintendent put it plainly, “I always lay out my own buildings. I want to know how it relates to the rest of the structures.” On we go.

FAQ

Why would an experienced general superintendent personally do building layout instead of leaving it entirely to surveyors?

Physically laying out the building reveals exactly how it relates to everything around it, including conflicts that may not appear on the drawings at all. It is a direct way to verify reality rather than relying entirely on documents and secondhand information.

What is the difference between BlueStake and a private utility locator?

BlueStake typically covers public utilities up to the building connection point, but it often does not address utilities or conditions located on the private portion of a property. A private utility locator or potholing company fills that gap by identifying what actually exists inside the property line itself.

Why does catching a utility conflict during layout matter so much?

Relocating a major utility, like an electrical duct bank, can take five to six months once a utility company is involved, regardless of construction schedule pressure. Finding that conflict during layout, before excavation starts, turns a potential months-long delay into a manageable adjustment instead of a project crisis.

Why shouldn’t survey marks from another professional be trusted without double-checking?

Data from any source, whether a drawing, an as-built, or another surveyor’s layout marks, cannot be considered verified until it has actually been independently checked. This is standard professional practice, not a sign of distrust toward the person who provided it.

What should happen to temporary field discoveries like BlueStake marks or potholing results?

They should be captured and merged into CAD or AutoCAD as a permanent record, since paint fades, potholes get filled, and physical layout strings eventually come down. Documenting these findings ensures the information can be recreated and referenced again later in the project, rather than depending on memory.

If you want to learn more we have:

Discover Jason’s Expertise:

“The Piece,” in One Piece Flow

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

Read 17 min

The Envelope Game

A simple exercise makes this concept click for almost anyone. Take twenty pieces of paper, twenty envelopes, and twenty stamps. Fold all twenty papers first, then stuff all twenty envelopes, then seal all twenty, then stamp all twenty. That is batching, and it takes noticeably longer than the alternative: fold one paper, stuff it, seal it, stamp it, and move to the next, one complete envelope at a time.

This is where people usually get confused. Folding twenty papers in a row feels like focusing on one thing, doesn’t it? That confusion is exactly the point worth untangling, because it reveals the real question underneath one-piece flow: what actually counts as “the piece”?

The Real Pain: Thinking You’re Doing One Piece Flow When You’re Not

The real pain is believing you are already practicing one-piece flow simply because you are repeating the same action over and over, when you are actually still batching at a higher level. Folding twenty papers in sequence is focus on a task, but it is not focus on the actual deliverable.

That false confidence is dangerous precisely because it feels like discipline. Teams and individuals convince themselves they are already doing the efficient thing, which removes any motivation to look closer at what is actually slowing them down.

The Failure Pattern: Confusing a Step With the Piece

The failure pattern is mistaking any single repeated action for “the piece” itself, when the real piece is the complete, finished unit of value someone else is actually waiting on. In the envelope game, the piece was never a folded paper. It was a finished, sealed, stamped envelope ready to mail.

This same confusion shows up constantly in real work. Researching a set of drawings feels like meaningful, focused progress, but if the actual deliverable is a fully reviewed, double-checked, and transmitted submittal, research alone is just one step of a much larger piece still waiting to be completed.

A few signs tend to show up when a team has confused a single step with the actual piece, and they are worth checking honestly:

Work in progress is measured by activity completed, like drawings reviewed or inspections done, rather than by fully finished deliverables ready to hand off.
Similar sub-steps across multiple tasks get grouped together and done all at once, even when each task’s true completion is what actually matters.
Nobody has clearly defined what “finished” specifically means for the task at hand before starting on it.

This Isn’t Intuitive, and That’s Okay

None of this is obvious, and it is worth being honest about that. Nearly every stage of life quietly teaches the opposite lesson: batching similar steps together feels efficient, and it gets reinforced in school, in early jobs, and in how most processes get taught by default.

Doing one thing at a time, all the way to completion, before moving to the next, runs against that lifetime of conditioning. Struggling to see it clearly at first is not a personal failing, it is just genuinely counterintuitive.

Gang Forms and the Missing Envelope

Here is the same question applied directly to construction. Building gang forms involves several steps: shaking out materials, assembling components on strongbacks, sheathing the forms, cleaning and oiling the face, and getting everything ready for rigging. Batching means doing step one across all four forms, then step two across all four, and so on, which means no single form is actually ready to use until every form has passed through every step.

Doing one form completely, all five steps, start to finish, before moving to the next, means that first form is ready for quality control and use far sooner. The same logic applies to submittals: researching drawings, reviewing the submittal, getting a second set of eyes, and transmitting it. Batching means researching all four submittals first, then reviewing all four, then double-checking all four, which delays every single one of them reaching a truly finished state. Processing one submittal completely before starting the next gets that first one out the door, reviewed and ready, far faster.

Why It Matters: The Customer Waits Four Times Longer

This matters because whoever is downstream, a client, an inspector, the next trade, another department, is waiting specifically for a finished piece, not partial progress on several pieces at once. In the envelope game, the first finished, mailable envelope arrives roughly four times faster under one-piece flow than it does under batching.

An exterior inspection and consulting company learned this directly. Their team was running two hours behind daily and twenty to forty reports backlogged, because they treated the inspection and the follow-up report as two separate batched tasks, doing several inspections first and pushing every report to later in the day. The fix was recognizing that the real piece was never just “an inspection,” it was a completed inspection and report together. Once they finished each inspection and its report before moving to the next site, they went from three or four inspections a day to five, and their entire backlog disappeared.

Teach the Framework: Ask What Needs to Be Finished

The core diagnostic question is simple: what actually needs to be complete before this is genuinely ready for whoever is next in line? A hospital’s piece is not a patient who has been seen, it is a patient who has been seen, diagnosed, and treated. A car manufacturer’s piece is not a partially assembled vehicle, it is a finished car. A construction company’s piece, at the largest scale, is a finished building, but at a smaller scale, it might be one completed submittal, one completed inspection report, or one completed form ready for concrete.

Getting this definition right matters more than the general instinct to “focus.” Focusing intensely on the wrong-sized piece, a single sub-step instead of the true deliverable, still produces the slower, batched outcome, just disguised as diligence.

A few practical questions help correctly identify the real piece before organizing any workflow:

What does the person or team downstream actually need in hand before they can do anything useful with it?
Is progress being measured by individual steps completed, or by fully finished deliverables ready to hand off?
Would grouping similar sub-steps together across multiple tasks actually delay every single one of them reaching a truly finished state?

Turning This Into Daily Practice

Before starting any batch of similar work, whether it is submittals, inspections, forms, or reports, take a moment to explicitly define what “finished” means for one single unit. That definition becomes the actual piece that should flow through the process one at a time.

Watch specifically for the tempting shortcut of grouping similar sub-steps together, research all the drawings, make all the calls, draft all the reports, since that instinct is exactly what quietly turns a genuine one-piece flow effort back into disguised batching.

Connecting It Back to Building People, Not Just Projects

None of this happens automatically, since batching feels efficient and gets reinforced everywhere outside of deliberate Lean training. Teaching teams to correctly identify the real, finished piece in their own work is exactly the kind of practical skill that shortens durations and reduces backlogs without requiring anyone to work harder.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow, including how to correctly apply one-piece flow instead of just relabeling batching as focus.

The Challenge

So here is the challenge worth carrying into your next task list: before organizing your day around a batch of similar work, stop and ask exactly what needs to be finished for one single piece to be genuinely done. As Jason put it plainly, “What is the piece that we want to flow?” On we go.

FAQ

What’s the difference between batching and one-piece flow?

Batching means completing the same step across multiple items before moving to the next step, like folding twenty papers before stuffing any envelopes. One-piece flow means fully completing one item, through every step, before starting the next, which consistently finishes faster overall.

Why does folding twenty papers in a row feel like focus if it’s actually batching?

Repeating the same physical action does feel like concentrated effort, but the real question is what the finished, useful deliverable actually is. In the envelope example, a folded paper is not the deliverable, a sealed, stamped, mailable envelope is, and batching delays that true deliverable significantly.

How does this apply to something like construction submittals?

If the true piece is a fully researched, reviewed, double-checked, and transmitted submittal, batching the research step across several submittals before reviewing any of them delays every single one from reaching that finished state. Processing one submittal completely before starting the next gets that first one out the door far sooner.

Why did the inspection company’s fix work so well?

They had been treating an inspection and its written report as two separate, batchable tasks, doing several inspections and pushing all the reports to later in the day. Once they recognized the real piece was the completed inspection and report together, finishing each one before moving to the next site, their backlog disappeared entirely.

How can someone correctly identify “the piece” in their own work?

Ask specifically what the next person in line, a customer, an inspector, another department, actually needs in hand before they can use it. That fully finished, ready-to-hand-off unit, not any single sub-step along the way, is the real piece that should move through the process one at a time.

If you want to learn more we have:

Discover Jason’s Expertise:

Receiving may be the best Gift

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

Read 17 min

“God Will Pay You Back”

A friend from church survived one of the hardest childhoods imaginable, fleeing conflict in Sudan as one of the “Lost Boys,” crossing dangerous territory with no adults to protect him, and somehow growing into one of the most honest, loyal, and generous men anyone could meet. Years later, after a difficult legal fight, he finally won back custody of his own children, who were still overseas.

When the opportunity came up to help fly his kids to Phoenix using some airline points, it was an easy yes. Later, standing up in front of his church community, he thanked the people who had helped him, then said something worth sitting with: “I will not pay you back, but God will pay you back.” He had nothing to repay the gift with, and he said so plainly, with total humility, trusting that the good would still find its way back around somehow.

The Real Pain: Refusing the Help You Actually Need

The real pain shows up constantly, in much smaller moments than a custody battle or a refugee crossing. Someone offers to cover a small expense, a tank of gas, an admission fee, a simple kindness, and the person on the receiving end insists on paying their own way, even when the offer was genuine and easy to give.

It rarely comes from ingratitude. It usually comes from a deep discomfort with being on the receiving end of generosity, as if accepting help somehow costs something more than money.

The Failure Pattern: Mistaking Independence for Strength

The failure pattern is treating self-sufficiency as a virtue in every situation, even the ones where genuinely accepting help would clearly be the better choice. Refusing a real offer of kindness can look like strength or humility from the outside, but it often just gets in the way of something good actually happening.

This shows up well beyond personal finances. It shows up anywhere someone insists on doing everything alone rather than letting someone else contribute, help, or serve, even when that help is freely and genuinely offered.

A few signs tend to show up when refusing help has become a reflex rather than a genuine choice, and they are worth checking honestly:

A small, easy offer of help gets declined automatically, before there is even time to consider whether accepting it would actually be fine.
Accepting help feels like an admission of failure rather than simply part of how people take care of each other.
The instinct to repay a favor immediately outweighs the instinct to simply say a genuine thank you and let the moment be what it is.

This Isn’t About Weakness, It’s About Completing the Circle

None of this means refusing help is a character flaw. It usually comes from good intentions, not wanting to be a burden, wanting to earn everything independently, wanting to stay humble. But there is a piece missing from that logic worth naming directly.

Refusing a genuine offer of help does not just affect the person declining it. It also quietly denies the giver their own chance to contribute, to feel useful, and to experience the kind of meaning that comes specifically from being able to give. Letting someone help you, when the offer is real, is not weakness. It completes something for both people involved.

A Lifetime of Being Helped

Here is what that looks like across an actual life. Months spent living with in-laws while getting back on financial feet. A parent quietly pulling seven thousand dollars from retirement savings just to help furnish a first home. Fifteen thousand dollars borrowed from an aunt during a tough financial stretch, repaid later with interest. Even a period genuinely destitute enough to need direct assistance from a church community just to get by.

None of that help could ever be fully repaid to the exact people who gave it. But every bit of it built the capacity, later on, to be the one doing the helping, taking kids to the lake, covering small costs for others, giving time and resources freely, because so much had already been freely given first.

Why It Matters: Giving Only Works If Someone Lets You

This matters because giving depends entirely on someone else’s willingness to receive. Imagine a world where countries refused international aid, where cities turned away help after a disaster, where nobody would ever accept a donation or a kind gesture from anyone else. Life would lose an enormous amount of its meaning, because the ability to contribute, to love, and to be of real use to another person is close to the center of what makes life feel worthwhile in the first place.

Every act of generosity needs a willing recipient on the other end to actually exist. Refusing to be that recipient, even out of good intentions, closes off half of that exchange entirely.

Teach the Framework: Reject the Lone Wolf Myth

This connects directly to a principle worth carrying into any leadership role: reject the lone wolf myth. Leaders who insist on solving everything alone, who see asking for help as a weakness, consistently perform worse than leaders willing to ask for support, welcome outside perspective, and let other people contribute.

The same logic that makes a superintendent stronger for asking a peer for advice, touring another project for fresh ideas, or welcoming honest feedback applies just as much personally. Letting someone else help you, whether it is covering a small cost, offering guidance, or simply showing up when you need it, is not the opposite of strength. It is often exactly what strength actually looks like in practice.

A few practical habits build genuine comfort with receiving help instead of reflexively declining it:

Pause before automatically refusing a genuine offer of help, and honestly ask whether accepting it would actually be fine.
Respond to a kindness with a simple, genuine thank you rather than an immediate need to repay or apologize for it.
Look for opportunities to pass a kindness forward to someone else, rather than feeling obligated to repay the exact person who gave it.

Turning This Into Daily Practice

This does not require becoming someone who takes without giving back. It simply means noticing the automatic instinct to decline help and checking whether that instinct is protecting something real, or just protecting pride.

Over time, receiving well and giving well become the same skill, practiced from both directions. The people who are best at generously helping others are very often the same people who learned, at some point, how to gracefully let themselves be helped too.

Connecting It Back to Building People, Not Just Projects

None of this happens without leaders willing to admit they cannot do everything alone, and willing to let their own teams, mentors, and communities actually support them. Building that kind of humility is exactly the kind of leadership quality that makes a person, and a team, genuinely stronger over time.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow, including building a culture where asking for and receiving help is treated as strength, not weakness.

The Challenge

So here is the challenge worth carrying forward this week: the next time someone offers you genuine help, notice the instinct to refuse it, and consider letting it be a gift to both of you instead. As one friend put it after finally being reunited with his own children, “I will not pay you back, but God will pay you back.” On we go.

FAQ

Why is it sometimes harder to receive help than to give it?

Accepting help can feel like an admission that you could not handle something entirely on your own, which many people experience as uncomfortable or even shameful. Reframing it as part of a natural, ongoing cycle of giving and receiving makes it easier to accept graciously rather than reflexively refusing it.

Does refusing help actually affect the person offering it?

Yes. Generosity depends on having someone willing to receive it, and declining a genuine offer denies the giver their own chance to contribute and feel useful. In that sense, letting someone help you is itself a kind of gift back to them.

What does “reject the lone wolf myth” mean in a leadership context?

It means recognizing that leaders who insist on solving everything alone, without asking for help or welcoming outside input, consistently underperform compared to those willing to seek support and feedback. Asking for help is treated as a strength that improves outcomes, not a weakness that undermines authority.

How can someone get more comfortable accepting help without feeling guilty?

Start by pausing before automatically declining a genuine offer, and honestly consider whether accepting it would actually be fine. Responding with a simple thank you, rather than an immediate need to repay or apologize, helps make receiving feel natural rather than uncomfortable.

Is receiving help the same as being dependent on others?

No. Receiving help when it is genuinely offered, and later passing that same kindness on to others, is part of a healthy, ongoing cycle rather than a sign of dependency. The people most able to help others generously are often the same people who learned how to accept help gracefully themselves.

If you want to learn more we have:

Discover Jason’s Expertise:

Sneaker Time

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

Read 17 min

What Is Sneaker Time?

Sneaker time is any time spent physically running around a jobsite, chasing down a person, a material, a tool, or a piece of information one interaction at a time. It looks like motion. It looks like hustle. Most of the time, it is neither.

Whether it is tracking down a foreman to relay an update, walking to check on a delivery, or hunting for information that should have already been shared, sneaker time is a real cost hiding in plain sight on almost every project.

The Real Pain: Hours Lost to Just Walking Around

The real pain is how much of a workday this quietly consumes. A superintendent running around solving communication gaps one conversation at a time can lose thirty minutes, two hours, or on a bad day, four to six hours, just moving from person to person instead of doing focused, valuable work.

None of that time shows up as a line item anywhere. It just disappears into the day, one hallway conversation and one walk across the site at a time, while the actual work that needed real attention sits waiting.

The Failure Pattern: Mistaking Motion for Productivity

The failure pattern is keeping the plan entirely in one person’s head and communicating it individually, relationship by relationship, instead of through a shared system everyone can see. It feels responsive and hands-on in the moment. It is actually a bottleneck disguised as diligence.

When one superintendent is the only source of truth for what is happening on a project, every piece of coordination has to physically route through them, one conversation at a time. That is not leadership, it is a single point of failure wearing steel-toed boots.

A few signs tend to show up when sneaker time is quietly draining a project, and they are worth checking honestly:

A superintendent spends large parts of the day physically walking to relay information that could have been shared once, to everyone, in a single meeting.
Materials, deliveries, or inspections get tracked down individually after the fact, rather than confirmed together during a regular planning meeting.
The plan for the day or the week exists mainly in one person’s head rather than somewhere visible the whole team can reference.

This Isn’t Laziness to Want Fewer Meetings, It’s a Trade You’re Not Seeing

It is completely understandable to dislike meetings. Plenty of them genuinely are a waste of time. But the real question worth asking is what actually replaces that meeting once it is gone.

Skipping a well-run meeting does not free up time, it just trades one hour of focused, structured coordination for several scattered hours of individual hallway conversations trying to accomplish the exact same thing, one person at a time. That is a worse trade, not a better one.

Trading a Meeting for a Dozen Hallway Conversations

Here is the exact trade being made, made explicit. Someone who says they would rather skip a meeting and just go talk to people individually is really saying they would rather spend more time doing sneaker time instead of less. Framed that way, the choice looks very different than it does in the moment of frustration with a meeting on the calendar.

A well-run huddle system flips this completely. A daily huddle and a weekly work planning meeting, run consistently and well, coordinate materials, deliveries, inspections, and next steps all at once, with everyone who needs the information present at the same time. Nobody has to be chased down afterward because the coordination already happened, together, in one place.

Why It Matters: Motion, Transportation, and Waiting Are All Waste

This matters because sneaker time is not just an inconvenience, it maps directly onto some of Lean construction’s most basic forms of waste: motion, transportation, and waiting. Every one of those wastes shows up the moment coordination depends on physically finding people instead of gathering them, or waiting on someone else to physically show up with an answer.

A superintendent who becomes the sole keeper of the plan also becomes a permanent bottleneck for the whole team’s information flow. Every question has to route through them individually, every update has to be delivered separately, and the entire project’s throughput slows down to the pace of one person’s feet.

Teach the Framework: Meetings Exist for Communication Throughput

The right way to think about meetings is not as a necessary evil, but as the actual production tool for moving information efficiently, from concept, to design, to the field. A well-structured meeting exists specifically to prevent the kind of one-on-one bottleneck sneaker time creates.

This is exactly why huddle structure matters so much. A daily huddle handles the day’s coordination in one focused conversation. A weekly work planning meeting handles materials, deliveries, and inspections for the week ahead, together, with the right people in the room at the same time. Done well, these meetings replace hours of scattered individual conversations with a fraction of that time spent once, collectively, and done right.

A few practical markers show whether a project has actually eliminated sneaker time or just moved it around:

The plan for the week is visible somewhere the whole team can reference, not stored only in one person’s memory.
Materials, deliveries, and inspections get confirmed together during a regular meeting, not chased down individually afterward.
A superintendent’s day includes real blocks of focused, uninterrupted work, rather than being spent almost entirely in motion between conversations.

Turning This Into Daily Practice

Building this starts with treating the daily huddle and the weekly work planning meeting as genuinely non-negotiable, run consistently and well, rather than something to skip when the day gets busy. The busier the day feels, the more that structured coordination actually matters, not less.

It also means getting the plan out of one person’s head and onto something visual the whole team can see and reference, so questions get answered by looking at a shared plan instead of tracking down whoever happens to be holding it that day. A logistics map showing where materials stage and how deliveries route, a zone map showing where each crew should be, and a weekly work plan posted where everyone can see it all do the same job: they answer questions before anyone has to go looking for a person to ask.

This does not mean every conversation on a jobsite is wasteful. Field presence, checking in with crews, building relationships, and walking the work still matter enormously. The distinction is between purposeful presence and reactive running around, between checking on work that is already coordinated and scrambling to coordinate work that never got organized in the first place.

Connecting It Back to Building People, Not Just Projects

None of this happens without leaders willing to invest real discipline into running huddles and meetings well, rather than treating them as a box to check. That investment is what actually buys back the hours currently lost to running around the site chasing information one conversation at a time.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow, including the meeting structures that eliminate wasted motion instead of creating more of it.

The Challenge

So here is the challenge worth carrying onto your next project: track honestly how much of your day gets spent in sneaker time this week, then ask what a better-run huddle or weekly meeting could have replaced it with. As Jason put it plainly, “We always want to reduce our sneaker time.” On we go.

FAQ

What exactly counts as “sneaker time” on a jobsite?

It refers to any time spent physically walking or running around to communicate information, track down materials, or coordinate with people individually, rather than through a structured meeting or visual system. It includes chasing deliveries, relaying updates person by person, and hunting down answers that should already be shared.

Why is sneaker time considered a waste rather than just normal jobsite hustle?

It directly overlaps with some of Lean construction’s core wastes, motion, transportation, and waiting, since it involves people and information moving inefficiently instead of flowing through a coordinated system. It can consume anywhere from thirty minutes to several hours a day without producing any actual progress on the work itself.

Isn’t skipping a meeting a good way to save time on a busy day?

Not usually. Skipping a well-run meeting typically means the same coordination still has to happen, just spread across several scattered one-on-one conversations instead of one focused session. That trade usually costs more time overall, not less.

How does keeping the plan in one person’s head create a bottleneck?

When only one person holds the full plan, every question or update has to route through that individual personally, which limits the whole team’s pace to how quickly one person can physically respond. A visible, shared plan lets people find answers without needing to track down a specific individual first.

What does a well-run huddle system actually replace?

A daily huddle and a weekly work planning meeting, run consistently and well, coordinate materials, deliveries, inspections, and next steps together in one sitting. Done properly, they replace hours of scattered individual conversations with a fraction of that time spent once, with the right people in the room together.

If you want to learn more we have:

Discover Jason’s Expertise:

General Offerings

Company Offerings

Systems

SUBSCRIBE NOW !

Subscribe to our newsletters and stay updated!

Related Books

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

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

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

Related Books

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

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

Related Books

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

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

Calumet "K"

faq

General Training Overview

Superintendent / PM Boot Camp

Takt Production System® Virtual Training

Onsite Takt Simulation

Foreman & Field Engineer Training

Testimonials

Testimonials

agenda

Day 1

Foundations & Macro Planning

day2

Norm Planning & Flow Optimization

day3

Advanced Tools & Comparisons

day4

Buffers, Controls & Finalization

day5

Control Systems & Presentations

faq

UNDERSTANDING THE TRAINING

VALUE AND RESULTS

PLANNING AND SCHEDULING TOPICS

APPLICATION & TEAM ADOPTION

VIRTUAL FORMAT & ACCESSIBILITY

faq

GENERAL FAQS

CURRICULUM & OUTCOMES

LOGISTICS & FORMAT

PRICING & VALUE

SEO-BASED / HIGH-INTENT SEARCH QUESTIONS