Don’t Ever Disrespect a Trade Partner or Vendor!

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

Read 16 min

Don’t Get A Big Head Just Because You Have A Little Authority

Don’t get a big head just because you have a little authority. That line deserves to sit at the front of every new leader’s mind, because the moment a title shows up, so does the temptation to treat it like it earned something it did not. A badge, a promotion, or a new seat at the table changes what someone is responsible for. It does not automatically change how much they actually know.

Where A Little Title Creates A Big Problem

New field engineers, project coordinators, and assistant superintendents step into construction with a title before they have the tenure to match it. That gap is normal, and it is not the problem. The problem shows up when someone treats a fresh title as license to speak down to a foreman, a vendor, or a trade partner who has spent decades learning the exact craft that title is supposed to help coordinate. A little authority, handled carelessly, becomes a big head fast, and once it does, it shows up in tone, in emails, and in the small decisions nobody else in the room ever sees.

When Position Gets Confused With Superiority

The failure pattern is simple to spot once it is named. Somebody earns a title, a badge, a seat at the table, and quietly starts treating that title as proof they know more than the people around them, especially the people technically below them on a contract chain. A general contractor’s coordinator talks down to a vendor. A young assistant PM gets short and condescending with a trade partner foreman who has been in the field for thirty years. The title changed overnight. The wisdom did not, and pretending otherwise is where the real trouble starts.

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

The system failed them, they did not fail the system. Nobody hands a new field engineer or project coordinator a lesson on how to carry authority well. Most onboarding covers software, safety, and process, but almost none of it covers humility. Without that lesson, a new title can quietly curdle into condescension, not because someone set out to be disrespectful, but because nobody ever drew the line between having a position and having earned superiority.

A Rude Email And An Honest Confession

A recent example makes the point directly. A project coordinator sent a genuinely rude, condescending email over a difficult project where extra effort and extra help were already being poured in to make things work. The instinct in that moment was to want to walk away entirely rather than keep working with someone treating the relationship that way. What makes the story worth telling is the honest admission that followed it, a recognition that this same condescending behavior showed up decades earlier, aimed at trade partner foremen who were forty, fifty, sixty years old, simply because a young area assistant superintendent had not yet learned to respect a lifetime of field wisdom sitting right in front of him. Looking back on it now, that old version of stiff necked, hard nosed behavior is exactly what needed to change first.

Why This Distinction Matters

This matters because construction runs on relationships that get tested and rebuilt project after project. Trade partners, vendors, and foremen remember who treated them with respect and who treated them like an obstacle. A single condescending email or a dismissive tone in a trailer meeting can quietly cost a company a trade partner relationship that took years to build. Respect is not a soft skill on the side of the job. It is the thing that keeps the same good people willing to work with you again on the next project, and the one after that.

Authority Without Wisdom Is Just Noise

There is an old saying worth carrying into every new title. The smart man glories in all he knows. The wise man is humbled that he knows no more. A title can make someone smart on paper, familiar with software, systems, and processes. Only time, humility, and enough hard lessons turn that smart person into a wise one. Confusing the two is exactly how a little authority turns into a big head.

Position Is Not The Same As Respect Earned

Nobody automatically deserves disrespect because of where they sit on a contract chain. A third tier subcontractor, a small vendor, a foreman without a college degree, none of that changes how much respect that person is owed. Being the general contractor, or the one holding the purchase order, or the one running the meeting does not make anyone better than the people they are coordinating. It only makes them responsible for coordinating well, and coordinating well starts with respect, not with rank.

What This Looks Like When It Goes Right

The correction is not complicated. Treat every trade partner, vendor, and foreman the way their experience actually deserves, regardless of title, position, tenure gap, or how junior the person delivering the message happens to be. Ask questions instead of issuing commands to people who have forgotten more about their craft than a new hire has learned. Say thank you. Assume competence before assuming ignorance. None of this costs anything, and all of it protects relationships that a company depends on far longer than any single project, especially in an industry where the same trade partners and vendors show up on job after job for years.

Signs Authority Is Going To Your Head

Watch for these patterns in yourself before someone else has to point them out.

Speaking to vendors or trade partners in a tone you would not accept from someone else
Assuming your title means you know more than someone with decades of field experience
Feeling irritated when a foreman or vendor pushes back on a decision
Forgetting to say thank you to the people actually doing the work

Connect To Mission

None of this means avoiding hard conversations or lowering your standards. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. It means holding those standards while still treating every person on the project, regardless of position, with the respect their experience has actually earned. A leader can be direct, demanding, and still deeply respectful, all at the same time.

Ways To Keep Authority In Check

Use these the next time a title tempts you to talk down to someone.

Ask yourself how many years of experience the other person has before you speak
Say thank you to trade partners and vendors as often as you correct them
Replace commands with questions when you are unsure of the full picture
Apologize quickly and directly when a tone comes out wrong

A Challenge For Every New Leader

Here is the challenge this week. Notice the next time a title, a badge, or a little bit of authority tempts you to speak down to someone with more field experience than you have. Pause, and choose respect instead, even if the moment feels small at the time. As Jason has said, we have got to figure out how to not throw people away going forward, and that starts with never treating a person as less than simply because of where they sit on a contract chain.

On we go.

Frequently Asked Questions

Why do new leaders sometimes become disrespectful toward experienced trade partners? A new title can create a false sense of superiority before real field wisdom has been earned, and without training on how to carry authority well, that gap can quietly turn into condescension over time.

Does a person’s position on a contract chain determine how much respect they deserve? No. A vendor, a third tier subcontractor, or a foreman without a formal title still deserves the same baseline respect as anyone else on the project, regardless of contractual hierarchy.

How can a leader tell if authority is starting to go to their head? Common signs include speaking to trade partners in a tone they would not accept themselves, feeling irritated by pushback from experienced people, and forgetting to say thank you to the people actually doing the work.

Why does respecting tenure and experience matter for a company long term? Trade partners and vendors remember how they were treated, and disrespect can quietly end relationships that took years to build, while respect keeps good people willing to work together again on future projects.

What is the difference between having authority and having earned respect? Authority comes from a title or position, while respect is earned through wisdom, humility, and how consistently someone treats people well, which is why a title alone should never be mistaken for superiority.

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.

Treat Your Subordinates Right!

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

Read 17 min

The Difference Between Consequences And Punishment On Your Jobsite

You cannot expect a soldier to be a proud soldier if you humiliate him. That line comes from a poster written by General Arthur Hyman, and once you read the whole thing, it says something about leadership that construction desperately needs to hear. Jason has said it plainly before. Construction is full of hard conversations, but you do not have to say them hard. Being firm and being harsh get treated like the same thing on far too many jobsites, and that confusion costs teams more than most leaders realize.

Where Leadership Goes Wrong On The Jobsite

Walk enough projects and you will meet both kinds of leaders. One holds a high standard and treats people with respect while doing it. The other holds the same standard, but gets there by embarrassing people in front of their crew, raising their voice until a trailer meeting feels like a courtroom, or making an example out of someone so everybody else falls in line out of fear. Neither leader is short on standards. What separates them is how the standard gets enforced. Both might get short term results. Only one of them builds a team that actually wants to be there tomorrow.

Confusing Firmness With Harshness

The failure pattern almost always starts the same way. A leader equates zero tolerance for bad behavior with permission to be harsh about it. They think that because a mistake was serious, the response has to be personal, loud, or humiliating to land. So a repeated safety violation turns into a public dressing down instead of a real conversation. A cultural mismatch turns into cold treatment instead of a respectful exit. Somewhere in there, a little authority starts to feel like a license to posture, what Arthur Hyman’s writing calls the little man with a little job and a big head. The line between discipline and bullying gets blurry, and once it blurs, people stop trusting leadership even when leadership is technically right.

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

The system failed them, they did not fail the system. Most leaders who default to harshness were never shown another way. They came up in an environment where the loudest voice in the trailer was considered the strongest leader, and nobody modeled the difference between firmness and cruelty for them. Blaming an individual leader for repeating what they were taught misses the deeper issue. Jason has been honest about this himself, admitting he has acted this way at times and worked to repent from it. What is missing for most leaders is not character. What is missing is training on where that line actually sits.

Why Respect For People Has To Come First

Jason ran into this exact question while building a construction excellence course with his wife, Katie. She kept asking why respect for people had to be the very first principle in the entire program, and he finally landed on the honest answer. If respect for people is not the first principle, then everything else the team does in construction will end up hurting people somewhere along the way. Scheduling, quality, and safety do not hold up if the foundation underneath them disrespects the humans doing the work. Once Katie heard that answer, the title of the course was never really in question again.

Why This Distinction Matters

This matters because people can tell the difference between being corrected and being punished, even when the outcome looks similar from the outside. A worker who gets sent home to retrain after a safety violation, but is treated with dignity through the process, comes back engaged and careful. A worker who gets humiliated in front of the crew for the same violation comes back guarded, resentful, or gone entirely. Safety reporting drops in a culture built on humiliation, because nobody wants to admit a mistake to a leader who might make an example out of them next. Fear can move a crew for a little while. Respect is what keeps them there for years.

Consequences Versus Punishment

Here is the actual distinction worth sitting with. Punishment, by definition, means inflicting a penalty on someone as retribution for an offense. Retribution is the key word. It is emotional. It is personal. It exists to make someone pay. Consequences are different. A consequence is simply the natural, matter of fact result of a decision, delivered without needing to humiliate anyone in the process. If someone is not a cultural fit for the team, the most respectful answer is to invite them to find a place where they can be happy, so everyone involved ends up better off. That is a consequence, not a punishment, and it should feel like a non emotional, matter of fact decision rather than a verdict handed down in anger.

What This Looks Like In The Field

Picture a worker with repeated safety violations because their mind clearly is not in the game that day. The victim mentality response is to warn them and walk away, hoping it fixes itself. The punishment response is to embarrass them publicly so everyone gets the message. The respectful, accountable response is to send them home, get them the training or the mindset reset they need, and bring them back ready to work safely. None of those three options ignore the problem. Only one of them actually solves it, and only one of them treats the person like a human being worth investing in rather than an example to make.

Signs You’re Leading With Punishment Instead Of Consequences

Watch for these signals. They tend to show up quietly before a team’s trust in leadership breaks visibly.

Corrections happen in front of the whole crew instead of privately
Consequences feel personal or emotional instead of matter of fact
People hide mistakes instead of reporting them early
The same behavior gets addressed differently depending on the leader’s mood

Building Accountability The Right Way

Real accountability is not about being harder on people. It is about clarity, training, and follow through. Clarity means the standard was actually communicated before someone was expected to meet it. Training means the person had a real chance to learn how to do it right the first time. Follow through means leadership closes the loop instead of letting things slide until frustration finally boils over into a harsh reaction. When those three pieces are in place, consequences stop feeling like punishment because everybody already understood what was coming and why long before it happened.

Connect To Mission

None of this makes a team soft. It makes a team strong enough to hold a high standard without breaking the people trying to meet it. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. Respect for people is not the opposite of accountability, and it was never meant to be soft. It is what makes accountability sustainable, because a crew that trusts its leadership will hold the line even when nobody is watching.

Ways To Respond With Consequences This Week

If you want to start closing the gap between firmness and harshness, here is where to begin.

Move corrections to a private conversation whenever possible
State the standard clearly before you ever have to enforce it
Ask what training or support the person actually needs
Choose the most respectful response, not the loudest one

A Challenge For Every Leader

Here is the challenge this week. The next time someone falls short, pause before you respond and ask yourself one question, is this a consequence or is this punishment. If the answer leans toward punishment, find the more respectful path before you open your mouth. As Jason has said, “People are not the problem, the system is the problem and we have the ability to engineer near perfection for our personal organization systems.” Lead the system, not the retribution.

On we go.

Frequently Asked Questions

What is the difference between a consequence and a punishment at work? A consequence is the natural, matter of fact result of a decision or behavior, delivered without humiliation. Punishment is retribution, meant to make someone pay emotionally for a mistake, and it damages trust even when the underlying standard was fair.

Why does respect for people need to be the first principle in construction leadership? If respect for people is not established first, every other system built on top of it, scheduling, quality, and safety, ends up hurting the humans doing the work. Respect for people is the foundation everything else depends on.

How should a leader respond to repeated safety violations without being harsh? The respectful response addresses the behavior directly and privately, then provides the training or reset the person actually needs. Public humiliation might change behavior temporarily, but it damages trust and discourages people from reporting mistakes honestly.

What does true accountability actually require from a leader? True accountability requires clarity about the standard, real training to meet it, and consistent follow through, not harsher punishment. When those pieces are missing, consequences start to feel personal instead of fair.

Can a leader be firm without becoming harsh? Yes, and the difference comes down to intent and delivery. Firmness holds a clear standard with respect, while harshness uses humiliation or emotion to make a point, and only one of those approaches builds a team that trusts its leader.

If you want to learn more we have:

Discover Jason’s Expertise:

Kanban Mantras

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

Read 21 min

The Five Kanban Mantras That Keep Construction Flowing

Here’s the deal. Most construction teams think their biggest problem is the work itself. It usually isn’t. Give a crew the right materials, the right information, and enough people, and they generally get the job done. The real trouble almost always shows up somewhere else, in the space between one task and the next.

Where Construction Teams Actually Lose Time

Walk almost any jobsite and you will see it. A trade finishes their portion of a zone, but the next trade is not ready to receive it. Materials show up weeks early and pile up in the way, or arrive late and stop the whole sequence cold. Crews start five different tasks in a day and finish none of them, circling back later to clean up work that should have been done right the first time. None of this looks like laziness. It looks like busyness. But busyness and flow are not the same thing, and most teams cannot tell the difference until the schedule tells them the hard way.

Why Handoffs Keep Breaking Down

The failure pattern is almost always the same. Foremen and crews get trained to install work. They rarely get trained to manage the handoff of that work. So when a crew finishes their scope, in their mind, they are done. The transition to the next trade becomes an afterthought instead of the actual finish line. Meanwhile, materials and information get pushed into the pipeline on a schedule that has nothing to do with what the next station can actually absorb. Someone decides more is better, so more shows up, whether or not the site is ready. That is not a discipline problem. That is a design problem in how the flow of work was set up.

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

The system failed them, they did not fail the system. Nobody sat these crews down and taught them that the handoff, the moment one trade finishes and hands the zone to another, is the most important part of the process. Nobody told the person ordering materials that flooding the site early creates a hazard instead of a head start. When a team was never taught to think this way, blaming them for the resulting chaos misses the real issue. The fix is not a lecture. The fix is a better system.

A Simple Picture Worth A Thousand Schedules

One of the simplest ways to see this is a picture, not a spreadsheet. Draw a sideways hourglass on a whiteboard. On one side, draw circles representing work waiting to happen. In the middle, draw the narrow neck, the bottleneck, whatever trade, tool, or area has the least capacity on your project right now. Then ask the obvious question. Should you push harder on the circles piling up, or widen the neck? The answer is obvious once you see it drawn out. Pushing harder on a narrow bottleneck does not create flow. It creates a jam. Widening the bottleneck, or slowing what feeds into it, is what actually gets the work moving again.

Why This Matters On Your Project

This matters because a jammed system slows down everyone behind it, not just one trade. Quality suffers when crews juggle several unfinished tasks instead of finishing one properly before moving to the next. Safety suffers when materials pile up in walkways because they arrived before anyone was ready for them. And your people suffer, because a team that spends its day firefighting instead of flowing goes home exhausted instead of proud. Flow over busyness is not just a phrase. It is the difference between a crew that finishes on time and a crew that never quite catches up.

What Kanban Actually Means For Your Site

Kanban is a simple framework built to make all of this visible. It requires real time communication of capacity and full transparency of the work, usually shown on a visual board so every team member can see the state of every task at any moment. Scrum builds on that same visibility but adds real structure to the team and the schedule, which is why proper Scrum training matters alongside any visual board. At its core, Kanban asks a team to commit to a few disciplines: never pass a defective product down the line, take only what is needed, produce the exact quantity required, level the production, fine tune the process, and work to stabilize and simplify the system. Those disciplines sound simple, but very few teams practice all of them consistently.

Focus On The Baton, Not Just The Runners

The first mantra worth internalizing is this: focus on the baton, not just the runners. When workers have everything they need, materials, information, and manpower, they usually perform well. That is rarely the actual problem. The real problem lives in the handoffs, in accepting the work from the trade before you, keeping the area clean and safe, finishing on schedule, and being ready to transition to the next trade. A foreman should never think of themselves as only being in the game while installing work, and out of the game the moment a roadblock shows up. The best foremen stay present in the transitions, because that is where projects are won or lost.

Stop Starting And Start Finishing

The second mantra is just as direct. Stop starting and start finishing. Think about how often a team begins several activities and finishes almost none of them, only to circle back later and rework what should have been completed the first time. That pattern quietly produces nearly every kind of waste construction teams already recognize. Excess inventory of unfinished work sits around the site. Extra motion and transportation get created moving between half done tasks. Defects creep in. Over processing happens as people redo steps they thought were handled. All of it traces back to one habit shift: finish the work you start before moving to the next thing.

Don’t Jam The Motorway

The third mantra is do not jam the motorway. This is the hourglass picture in words. Do not push so much work into the system that it cannot physically move through. Limit your work in process and level it according to your actual bottleneck, whatever trade, area, or tool has the least capacity right now. The instinct in a schedule crunch is to push more work forward and hope it squeezes through. The better instinct is to protect the pace of your slowest point and build the plan around it. A motorway that is not jammed moves faster than one that is overloaded.

Just Enough, Just In Time

The fourth mantra applies directly to how material gets staged. Just enough, just in time. This does not mean waiting until the day of installation to bring materials to the site, because every plan needs a real time buffer and a material buffer to absorb normal variation. What it does mean is that the buffer belongs in your supermarket or lay down area, not scattered across the actual work zone where people are tripping over it. Bringing materials out only when it is truly time to install keeps the work area clear, keeps the crew focused, and keeps the site safer for everyone.

Flow, Then Pull, Never Push

The fifth mantra ties everything together. Flow, then pull, and never push. Do not ram paper into a printer that is already jammed, and do not ram work into a bottleneck that cannot absorb it. The goal is never to force more through a constrained system. The goal is to increase the actual capacity of that constraint, so the system can move faster without anyone getting overloaded. This is what make ready, then flow really means in practice. Prepare the work so it is ready to be pulled forward by the next trade, rather than pushed forward before anyone downstream can receive it.

Signs Your Site Is Jamming The Motorway

Watch for these signals. They usually show up before a schedule visibly falls apart, and they are worth catching early.

Multiple zones started but none finished cleanly
Materials stacked in walkways well before installation
Crews reworking the same task more than once
Foremen absent from the moment a roadblock appears

Turning Mantras Into Daily Habits

None of these mantras require new software. They require a shift in how a team looks at its own flow. A foreman who asks whether the next trade is truly ready before pushing a zone forward is practicing pull instead of push. A superintendent who protects a lay down area instead of letting materials flood the work zone is protecting just enough, just in time. A project engineer who insists a task gets finished before starting the next is living out stop starting and start finishing without ever saying the word Kanban.

Connect To Mission

All of this comes back to something bigger than a whiteboard drawing or a LinkedIn post about mantras. It comes back to protecting the people doing the work. A team that is not jammed or constantly firefighting is a team that goes home on time and in a good frame of mind. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. Respect for people is not soft. It is a production strategy that starts with honoring handoffs and limiting work in process instead of pushing harder just to survive the day.

Quick Wins To Build A Pull Mindset This Week

If you want to start applying this on your project this week, here is where to begin.

Ask your next trade if they are truly ready before you push work to them
Move excess material back to the lay down area
Finish one task completely before starting the next
Coach foremen to stay present through every handoff, not just the install

A Challenge For Your Crew

Here is the challenge this week. Walk your project and find the one place where work is being pushed instead of pulled. Find the one bottleneck getting jammed instead of protected. Then make ready, then flow. As Jason has said, “Production does not mean adding labor, rushing materials, throwing money at the problem, pushing people, or increasing work in progress. Rather, it means we know how to produce according to production principles.” Choose the principles over the push.

On we go.

Frequently Asked Questions

What is the difference between Kanban and Scrum on a construction project? Kanban is a visual framework that makes the state of every piece of work transparent in real time. Scrum builds on that same visibility but adds real structure to how the team operates, which is why strong teaming training matters alongside any visual board.

Why does limiting work in process matter more than working faster? Pushing more tasks into motion at once feels productive, but it usually creates unfinished work, rework, and waiting. Limiting work in process protects quality and moves the system faster.

What does “don’t jam the motorway” mean for a job site? It means protecting the pace of your actual bottleneck instead of forcing more work through it than it can handle. A system that respects its own capacity moves faster than one that is constantly overloaded.

How does “just enough, just in time” apply to material deliveries? Materials should arrive with a real buffer at your supermarket or lay down area, not scattered across the active work zone. Bringing materials in only when it is truly time keeps the site clear and safe.

Why should foremen focus on handoffs, not just installation? Workers with the right materials and information usually perform well on the task itself. The real risk lives in the transition between trades, which is why a foreman needs to stay present through every handoff.

If you want to learn more we have:

Discover Jason’s Expertise:

Re·source·ful·ness

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

Read 16 min

Why Resourcefulness Beats Resources On Every Project

You don’t have a resource problem. You have a resourcefulness problem. That line came from a slide inside Tony Robbins’ Unleash the Power Within program, and it landed hard enough to build an entire episode around it. It applies just as much to a jobsite as it does to a boardroom.

Where Teams Default To Buying Their Way Out

Ask most struggling teams why a project is behind, and the answers sound familiar. Not enough time. Not enough people. Not enough budget. Not enough technology. Not enough education. Not enough research. Terrible management. Terrible people. That last one deserves a second look, because it usually is not even true, and leaning on it lets everyone off the hook before anyone has actually gotten resourceful. And the solution that usually follows sounds just as familiar, buy new software, rent new equipment, hire another layer of management, or add another gadget to the pile. None of it addresses the actual gap, and the bill keeps arriving anyway.

Fixing Resourcefulness Problems With Resources

The failure pattern is consistent. A team hits friction, and instead of asking what they could do differently with what they already have, they ask what they could buy to make the friction disappear. That instinct feels productive in the moment. It rarely fixes anything, because the underlying problem was never about having too little. It was about using what already existed poorly, and no purchase order changes that on its own.

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

The system failed them, they did not fail the system. Very few people are ever taught to separate resourcefulness from resources. Most training in construction and business focuses on acquiring more, more staff, more software, more equipment, without ever building the muscle of asking how to be clever with what is already on hand. Nobody sat these teams down and defined resourcefulness as the ability to find quick and clever ways to overcome difficulties. So they default to what they were taught, which is to buy, and then they wonder why the underlying friction never actually goes away even after the purchase clears.

A Shed, Some AstroTurf, And A Business Built On Resourcefulness

Building a company from scratch offers a pretty direct test of this idea. Elevate Construction did not start in a nice office. It started in a ten by twelve shed in the backyard, fitted out with sound tiles, a computer, and even some AstroTurf on the floor, without upgrading the house or swapping out the same vehicles already sitting in the driveway. That approach was not a hardship. It was resourcefulness in action, and it is a big part of why the business became successful without ever needing to lean on unnecessary resources to get there.

Why This Distinction Actually Matters

This matters because chasing resources instead of resourcefulness quietly drains a business or a project. Every dollar spent masking a resourcefulness gap is a dollar that could have gone toward training, toward paying people well, or toward simply staying in business through a slow season. Waste like that does not always look like waste. Sometimes it looks like a brand new truck parked in the lot.

The Real Cost Of Choosing Lavish Over Resourceful

Picture two smaller businesses stepping into partnership with a larger, successful one. Instead of using existing equipment and finding clever ways to get started lean, both new partners bought brand new heavy duty trucks and the best gear available, because that was the world they were used to operating in. The main business ended up feeding those two smaller ones for years, hundreds of thousands of dollars in the negative, money that resourcefulness could have kept in the business entirely. Nobody set out to waste money. They simply reached for resources before ever reaching for resourcefulness.

What Resourcefulness Actually Means

Resourcefulness is the ability to find quick and clever ways to overcome difficulties. It means being mindful with what you have, being creative, and refusing to be extravagant simply because extravagance feels easier than problem solving. A resourceful leader can meet a difficult situation and devise a way through it using existing people, existing tools, and existing time, rather than reaching for a checkbook the moment friction shows up. That leader can define the situation clearly, get a clear vision of the outcome, list out the resources actually available, and then work through a real plan A, B, C, and beyond before ever assuming more spending is the answer. Do or do without captures the whole idea in four words, and it is a far more useful question to carry into a tough week than any list of what is missing.

When After Hours Work Becomes A Warning Sign

One place this shows up constantly in construction is overtime. Somebody should be able to do their job in a normal work week and go home to run a genuinely decent project. When a person or a team consistently relies on after hours work just to keep up, that extra time is not dedication. It is waste, and it is usually masking an ineffectiveness that resourcefulness would have solved without ever needing the extra hours in the first place.

Signs A Team Is Masking Waste With Resources

Watch for these patterns before they get expensive.

Every new problem gets answered with a new purchase
After hours work becomes the normal way to stay on schedule
New offices, trucks, or equipment appear before the team is proven
Nobody asks what could be done differently with what already exists

Coaching A Team Toward Resourcefulness

The next time somebody proposes buying their way out of a problem, the more useful question is simple. Have you actually gotten resourceful first? That single question, asked consistently, starts to shift a team’s instinct from reaching for a purchase order to reaching for creativity, commitment, and a genuine plan A, B, and C before anyone spends a dollar on plan D. Over time, that shift becomes a habit the whole team carries, not just something a leader has to keep repeating. Getting resourceful often just means reducing duplicated work, creating synergy between people who were already operating side by side, and choosing to operate lean instead of extravagant. There are entire courses built around exactly this, lean leadership, lean communications, lean meetings, and lean foundations, for teams that want a structured way to build the habit rather than guessing at it alone.

Connect To Mission

Being resourceful protects more than a budget. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. A team that learns to be resourceful together builds real capability, and that capability outlasts whatever equipment or software eventually gets replaced.

Questions To Ask Before You Buy Your Way Out

Before approving the next purchase meant to fix a problem, ask these first.

What could we do differently with our current people and tools
Is this truly a resource gap or a resourcefulness gap
What would plan B look like if we could not spend anything
Are we solving the problem or just masking it

A Challenge For Your Team

Here is the challenge this week. The next time a problem shows up on your project, resist the urge to reach for a purchase order first. Ask what a resourceful team would do with exactly what it already has. Success comes from what you do with things, not how much of the things you have. That is the whole lesson, said as simply as possible.

On we go.

Frequently Asked Questions

What is the difference between resources and resourcefulness? Resources are the people, money, tools, and equipment available to a team. Resourcefulness is the ability to find quick and clever ways to overcome difficulties using what is already on hand, rather than automatically acquiring more.

Why do teams default to buying solutions instead of getting resourceful? Most training in construction and business emphasizes acquiring more rather than being creative with existing resources, so teams default to purchasing because nobody taught them a resourceful alternative.

How does overtime relate to resourcefulness? Consistent after hours work is often a sign of masked ineffectiveness rather than dedication. A resourceful team typically finds ways to complete strong work within a normal schedule instead of relying on extra hours.

What is a practical way to build a more resourceful team? Before approving a new purchase meant to solve a problem, ask what could be done differently with the people, tools, and time already available, and treat that question as the first step rather than a last resort.

Can a business grow successfully while staying resourceful instead of resource heavy? Yes. Building a business with modest tools and space instead of expensive offices and equipment is a direct example of resourcefulness driving real, lasting growth without unnecessary spending.

If you want to learn more we have:

Discover Jason’s Expertise:

The Ladder of Accountability

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

Read 16 min

The Ladder Of Accountability Every Leader Should Climb

Being accountable means you make things happen. A poster spotted on a jobsite wall put that idea next to its opposite so clearly that it is worth building a whole conversation around, especially since most of us have lived on both sides of that ladder at different points in our careers.

Where Teams Quietly Slide Into Victim Mode

Every project runs into real obstacles, bad weather, late procurement, a crew that comes up short. The problem is not that obstacles happen. The problem is how a team responds once they do. Some teams acknowledge what is actually happening and go find a way through it. Others explain, quietly or loudly, why none of it was really their responsibility to solve. A poster on a jobsite wall captured this split better than most training ever does, with victim behaviors listed at the bottom and accountable behaviors listed at the top, like a literal ladder to climb.

Four Behaviors That Keep People Stuck

The failure pattern usually shows up in a predictable order. First comes being unaware, floating through the day without really knowing the standards or expectations. Then comes blaming others, when something goes wrong and the instinct is to point somewhere else. Then comes the excuse of I can’t, which sounds humble but actually forfeits the ability to try before anything has even been attempted. Whether you believe you can or you believe you can’t, you tend to be right, simply because belief shapes whether you keep trying past the first obstacle. And the most damaging one of all is waiting and hoping, waiting for better weather, hoping the crew shows up, hoping the material arrives on time. Construction leans on this one constantly. Waiting and hoping that a crew will have enough people is not a strategy. Waiting and hoping that a key piece of procurement shows up on time is not a strategy. Waiting and hoping that the weather cooperates during a critical phase is not a strategy either. None of those four behaviors are strategies. They are ways of staying comfortable while losing control.

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

The system failed them, they did not fail the system. Nobody sits crews or leaders down early in their careers and draws a clear line between a victim mentality and an accountable one. Without that line drawn plainly, people default to whichever behavior feels safest in the moment, and blaming circumstances almost always feels safer than owning them, at least until the pattern starts costing schedule, trust, and results. Most people are not choosing to be victims on purpose. They simply never learned there was a ladder to climb in the first place.

Even The King Of Victim Mode Can Change The Habit

Being honest about this pattern matters more than pretending to be above it. Even someone who teaches accountability for a living can slip straight into victim mode at home, turning a mistake around so that somehow someone else becomes the one at fault and the one doing the hurting. Naming that habit out loud is the first step toward catching it before it becomes automatic, whether it shows up in a marriage or in a trailer meeting on a Monday morning.

Why Being Told It Is Your Fault Is Not An Insult

Several well known voices in leadership circles like to say some version of the same blunt line, it’s your fault. Said one way, that sounds harsh. Said the way it is actually meant, it is one of the most empowering things a leader can hear. Nobody says it’s your fault to hurt you. They say it because believing something is your fault means you will take action to fix it, instead of waiting on someone else to fix it for you. Believing everything that touches your world is somehow your responsibility to influence is not about guilt. It is about staying in the driver’s seat of your own outcomes, on a project, in a business, or at home.

Why Climbing The Ladder Actually Matters

This matters because a victim mentality is fundamentally a loss of power. A person who blames the weather, the crew, or the supply chain for every setback has handed control of their outcomes to something outside themselves. An accountable person keeps that control, because their state is not determined by what somebody else did or did not do. That difference shows up directly in schedule performance, safety culture, and whether a team actually solves problems or just spends its energy explaining them away.

Acknowledge Reality, Then Own It

The climb toward accountability starts with acknowledging reality, actually coming to terms with what is happening instead of minimizing or explaining it away. From there comes owning it, treating the situation like it belongs to you even if you did not directly cause it. That ownership is what creates the empowered state where solutions actually start to appear, because a person who owns a problem stops waiting for someone else to solve it.

Find Solutions, Then Make It Happen

Once reality is acknowledged and owned, finding solutions becomes possible, because a person in that state is resourceful instead of defeated. The final rung is simply making it happen, and it is worth remembering that there are always more ways to solve a problem than there are excuses to avoid it. Truly accountable people tend to find one of those ways, again and again, until it becomes their default response to friction. That default response is what eventually separates the people who get promoted from the people who stay stuck explaining why they could not.

Figuring It Out Does Not Mean Figuring It Out Alone

One important clarification belongs here. Being told to figure it out and find a way was never meant to mean doing it alone in a silo. It means finding a way with the team, with the resources already available, by asking for help, reaching out, doing the research, and expanding the network around you. Accountability is not isolation. It is ownership paired with resourcefulness, and the two work best together. A leader who demands accountability but offers no support is not building an accountable team. They are just building a lonelier version of the same victim mentality they were trying to fix.

Signals You Are Sliding Toward Victim Mode

Watch for these before they become a habit.

Explaining why a setback was not your responsibility
Saying I can’t before actually attempting a solution
Waiting for conditions to improve instead of acting now
Feeling like your day is controlled by everyone else’s decisions

Connect To Mission

Climbing this ladder is not about ignoring real obstacles, and it is not about pretending every setback was self inflicted. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. A team full of people who acknowledge reality and own their part of it will always outperform a team full of people waiting for something to change.

Questions To Climb Toward Accountability

Ask these the next time an obstacle shows up.

What is actually happening here, without softening it
What part of this can I genuinely own
Who can I bring in to help find a solution
What is the next action that actually makes something happen

A Challenge For Every Team

Here is the challenge this week. Notice the next time you catch yourself waiting and hoping instead of acting, and climb one rung higher. Acknowledge reality, own it, find a solution, and make it happen. There are more solutions and ways to make it happen than there are ways to blame others and find excuses.

On we go.

Frequently Asked Questions

What are the four behaviors in the victim category of the ladder of accountability? They are being unaware or unconscious of expectations, blaming others, using the excuse of I can’t, and waiting and hoping instead of acting.

What are the four behaviors in the accountable category? They are acknowledging reality, owning the situation, finding solutions, and making it happen, each one building on the step before it.

Why is waiting and hoping considered the most damaging victim behavior? Waiting and hoping is not a strategy in any part of construction, from estimating to project operations, and it leaves outcomes entirely dependent on circumstances instead of on action.

Does figuring it out mean solving a problem completely alone? No. Figuring it out means finding a way using the team, existing resources, and outside help when needed, not isolating yourself to solve everything without support.

How does accountability create a sense of empowerment? When someone owns a situation instead of blaming it on circumstances, they keep control over their own outcomes, which creates the empowered state needed to actually find and implement solutions.

If you want to learn more we have:

Discover Jason’s Expertise:

Things You Cannot Delegate as a CEO

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

Read 16 min

The Things A CEO Can Never Fully Delegate

There are certain things that as a CEO you must do, and no amount of trust in your team changes that fact. Delegation is not the same as disappearing from the details that actually run your business.

Where Delegation Quietly Turns Into Absence

Plenty of leaders start a business wanting to be the kind of owner who delegates completely, trusts the team, and steps back into a hands off role. It sounds healthy. It sounds like good culture. But when the outcome of the business and the obstacles standing in its way get fully handed off to somebody else, the leader stops seeing the very things that would have let them catch a problem early. Somewhere in that process, a CEO quietly slides from owning and leading the business into merely operating inside it, which is a much smaller and much riskier job than the title suggests.

Mistakes Happen Because Of What You Cannot See

The failure pattern is almost always the same, and it comes down to one honest sentence. Mistakes happen because of what we cannot see. A leader hands off finances entirely to a CFO, hands off hiring entirely to a chief people officer, hands off sales entirely to a sales lead, and then takes a step back, believing that full autonomy in each of those areas is the same as good leadership. It is not. It is a blind spot with a job title attached to it.

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

The system failed them, they did not fail the system. Most leaders were never taught the difference between delegating a task and delegating awareness. They wanted to build a healthy, trusting culture, and trust got confused with total hands off ownership. Nobody warned them that being overly optimistic about somebody else’s capability means substituting assumptions for facts, and that gap is where risk quietly builds until it becomes a crisis.

A Cashflow Scare That Changed The Approach

Early in building Elevate Construction, certain responsibilities got handed off completely, with the hope of becoming the kind of leader who trusts people and lets them run. It felt like good culture in the moment, the wonderful, hands off leader who reads books and lets the business hum along on its own. But those areas of the business started to fail quietly, and at one point, cash flow dipped so dramatically that it forced a hard realization. A business leader still has to lead every key aspect of the business, even the parts assigned to someone else, because trust without oversight is not leadership, it is absence with a nicer name. Patrick Lencioni’s wisdom on mentoring, managing, and coaching direct reports turned out to be the missing piece all along.

Why This Distinction Matters So Much

This matters because the consequences of full detachment rarely show up immediately. They show up months later, as a surprise loan the business suddenly needs, or a wave of turnover nobody saw building, or a client relationship that quietly soured because nobody was actually watching it. By the time the problem is visible, the cost of fixing it is far higher than the cost of staying close to it would have been. Optimism is not a strategy, and hoping a delegated area is fine is not the same as knowing it is fine.

Know Where Your Money Actually Is

A CEO has to know the financials at a real level, not a summary glance. That means understanding the balance sheet, the cash flow report, and the profit and loss well enough to know if the business is genuinely healthy or just paying its bills this week. Profit is theory. Cash is fact. A leader who cannot speak to operating cash flow without checking with someone else has delegated something that should never be fully out of their hands. It is remarkable, and it should not be, how many leaders of large companies genuinely do not know where their own money is.

Fill Your Key Seats With The Right People

Having enough great help is not a people problem to hand off. It is a cultural fit and key seat problem, and a CEO needs the vast majority of key seats filled with the right people at all times. This cannot be left entirely to HR, a chief people officer, or a COO, because the health of those seats determines whether every other system in the business actually functions. Above ninety percent of key seats filled with the right people is the number worth holding onto as a standard.

Own The Outcome, Not Just The Oversight

Creating raving fans and building a real marketing and sales strategy also belong to the CEO, even if the day to day execution gets delegated. A raving fan is not just a satisfied client. It is a client who recommends the company to anyone who will listen, and making that happen consistently is a leadership responsibility, not a marketing department task alone. Paperwork, legal work, and routine accounting can move to someone else without much risk. But the outcomes of the business, the obstacles in its way, and whether clients love working with the company are things a business owner has to actively lead, not just supervise from a distance.

Signs You Have Delegated Awareness, Not Just Tasks

Watch for these signals before a small blind spot turns into a real crisis.

You could not explain your cash flow without checking with someone else
Key seat vacancies have gone unresolved for months
You have not spoken directly with a major client in a long time
A single person owns an entire function with no one checking in

Mentor, Manage, And Coach Instead Of Disappearing

The better approach is not withholding trust. It is mentoring, managing, and coaching the people running each part of the business, staying close enough to catch a problem while it is still small. That difference is what separates a business owner who leads from an operator who simply hopes things are fine. Living the lie of an effortless, four hour work week while a business runs itself is not leadership. It is a setup for the exact blind spots that eventually cause a crisis, whether that shows up as a lost client, a key hire who was never really the right fit, or a cash position nobody flagged until it was already a problem.

Connect To Mission

None of this is about micromanaging every decision. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. Staying close to the details you cannot delegate protects the people counting on the business to still be standing next year.

Questions Worth Asking Yourself This Week

Use these to check whether you have delegated the task or the awareness.

Do I know my current operating cash position right now
Are more than ninety percent of my key seats filled with the right people
When did I last hear directly from a major client
What obstacle is currently standing between my team and its outcome

A Challenge For Every Business Leader

Here is the challenge this week. Pick one area you have fully handed off, and get back close enough to see it clearly again, not to take it back, but to lead it. Check the financials yourself this week instead of taking the summary secondhand. If you’re the leader, you’re responsible.

On we go.

Frequently Asked Questions

What can a CEO delegate safely, and what should they never fully hand off? Paperwork, legal work, and routine accounting can be delegated with little risk. The outcomes of the business, its obstacles, its finances, its key hiring decisions, and its client relationships need the CEO to stay directly involved.

Why is knowing the cash flow so important for a CEO? Profit is theory, but cash is fact. A CEO who cannot speak to the actual operating cash position is missing the one number that determines whether the business can genuinely keep running.

What does it mean to delegate awareness instead of just a task? Delegating a task means someone else executes the work. Delegating awareness means the CEO no longer sees what is actually happening in that area, which is where blind spots and eventual crises tend to form.

How can a CEO stay involved without micromanaging? Mentoring, managing, and coaching the people running each function allows a CEO to stay close enough to catch problems early, without taking over the day to day execution themselves.

Why do businesses often discover problems only after they become serious? When oversight is fully removed from a function, small issues go unnoticed until they grow large enough to force a reaction, like a sudden cash shortage or a wave of employee turnover.

If you want to learn more we have:

Discover Jason’s Expertise:

Takt Planning Q&A

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

Read 16 min

Why There Is No Excuse Left For Skipping Takt Planning

Every so often a question shows up that assumes Takt planning only works on one narrow kind of project, a typical vertical building maybe, with predictable procurement and inspections that never interrupt the flow. That assumption is wrong, and after two hours of live questions on exactly this topic, it is worth clearing up in detail.

Where Schedules Actually Fall Apart

Most schedule disputes do not start with bad intentions. They start with a complex P6 schedule that almost nobody on the team can actually use, paired with a procurement process nobody is tracking in one place. A shocking share of jobs run without a real procurement log at all. Teams say the information lives inside their project management software, tracking submittals, and assume that counts, without realizing nobody can actually see the whole supply chain from that view. Materials show up late. Nobody can prove what should have happened versus what actually happened. And when the disagreement finally reaches the owner, the team has no visual record to stand on, just a tangled logic schedule that even the scheduler struggles to explain.

The Myth That Takt Only Works On Typical Buildings

The failure pattern shows up as a series of assumptions. Takt only works on vertical construction, not horizontal or civil work. Takt cannot handle unpredictable procurement. Small Takt zones will conflict with inspections. Trades with different durations cannot share the same zone. Every one of these assumptions sounds reasonable until you actually test it against how the system is built to work, and none of them hold up.

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

The system failed them, they did not fail the system. Most teams were introduced to Takt through a single example, usually a typical vertical building, and nobody walked them through how the same principles apply to civil work, procurement uncertainty, or inspection driven schedules. Once a myth like that takes hold, it becomes the reason a team avoids a system that would have solved their actual problem.

More Fun On Civil Work Than Almost Anything Else

Ask about the exception, and the honest answer might surprise you. Implementing Takt planning on civil work is more enjoyable than almost any other kind of project, specifically because so few teams have tried it there. The zones look different. The processes look different. But the underlying discipline, mapping flow through rhythm, continuity, and consistency, works exactly the same whether the crew is framing walls or grading a roadway.

Why This Actually Matters

This matters because every one of these myths, left unchallenged, keeps teams locked into CPM schedules that protect nobody. Without a procurement log tied to a Takt plan, a team has no way to show an owner what normal standards of care actually looked like when a real delay hits. Without small batch thinking, inspections turn into full stoppages instead of brief interruptions. Every myth that goes unchallenged becomes another way the schedule, and the people executing it, get exposed.

Takt Works On Horizontal And Civil Work

Takt planning is not limited to vertical buildings. You break the project into Takt zones, pull plan each zone, package that into a sequence, and let that sequence become your Takt plan, regardless of whether the work is vertical, horizontal, or civil. The zones simply look different. A civil project might zone by roadway segment or utility run instead of by floor or room, but the same rhythm, continuity, and consistency apply.

Procurement Logs Protect Your Schedule And Your Position

A Takt plan paired with a real procurement log, one that tracks required on job dates calculated back from your point of release dates, does two things at once. It prevents most procurement problems before they start, because the whole team can see what is coming. And if a genuine disruption still happens, a documented Takt plan and procurement log give you a clear, visual comparison between what was planned according to normal standards of care and what actually occurred, which puts you in a far stronger position with an owner than an unreadable schedule ever could. This same Takt plan also feeds directly into your six week make ready look ahead, your weekly work plan, and your day plan, which is why Takt planning and the Last Planner System work together so naturally, almost like peanut butter and jelly.

Small Batches Absorb Inspections Instead Of Breaking Flow

Small Takt zones also solve the inspection problem. If an inspector wants to batch several zones together instead of inspecting each one individually, you simply pause the trains moving through those specific zones and restart them once the inspection clears. Because the zones are small, that pause only consumes a small percentage of the buffer you have already built into the schedule, and the project still finishes on pace.

Scopes, Not Quantities, Keep Different Trades In Rhythm

One of the more common questions is how Takt accounts for trades with very different durations, like extensive overhead duct in one area and only a small amount of work in another. The answer is that Takt zones are built around scope and level of effort, not raw quantity. Every zone shares the same processes, framing, fire sprinkler, flooring, ceilings, even though the actual quantity of material in each zone varies. Tacking out processes instead of material types is what keeps every trade moving at the same rhythm regardless of zone size. Buffers get sized the same disciplined way. Within a Takt wagon, buffers typically run five to twenty percent, calculated through a stability parametric rather than guessed at, which is exactly why the small pause caused by an inspection rarely threatens the overall finish date.

Three KPIs Worth Tracking In Takt Planning

If you want a simple way to measure whether your Takt implementation is actually working, track these three numbers.

Revisions made to the Takt plan over the life of the project
Remaining buffer rate percentage across your zones and phases
Roadblock removal average, the time between identification and resolution

What Just In Time Actually Requires

Just in time delivery, even in an unpredictable supply climate, still comes down to buffers. You set required on job dates, choose a buffer length that matches current conditions, whether that is two weeks or eighteen, and bring materials into a staging area or supermarket ahead of that date. From there, the project pulls what it needs just in time for installation. No other scheduling system makes that pull as visible or as manageable as a Takt plan does.

Connect To Mission

None of this is about chasing complexity for its own sake. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. A team that trusts its schedule, on any type of project, spends less time firefighting and more time going home on time.

Myths That No Longer Hold Up

Here are the excuses worth retiring for good.

Takt only works on vertical buildings
Unpredictable procurement makes Takt impossible
Small batches require more manpower than large ones
Different trade durations cannot share a Takt zone

A Challenge For Every Scheduler

Here is the challenge this week. Pick one assumption you have been holding about where Takt planning does or does not apply, and test it against an actual project in front of you. As Jason has said, you can use Takt planning for anything, it is just about becoming expert enough with the system to go do it. There are courses, books, and communities built specifically to close that gap, so the only real barrier left is the choice to start.

On we go.

Frequently Asked Questions

Does Takt planning actually work on horizontal or civil construction projects? Yes. Takt zones simply get defined differently, often by roadway segment or utility run instead of floor or room, but the same rhythm, continuity, and consistency principles apply regardless of project type.

How does a procurement log protect a project during a real supply chain disruption? A procurement log tied to required on job dates gives the team a visual, documented comparison between the original plan and what actually happened, which strengthens the team’s position with an owner if a genuine delay occurs.

How does Takt planning handle inspections without stopping the whole project? Small Takt zones let you pause only the specific trains affected by an inspection instead of the entire schedule, and because the pause is brief, it only consumes a small percentage of the project’s existing buffer.

Why can trades with very different work quantities still share the same Takt zone? Takt zones are built around scope and level of effort rather than raw quantity, so every zone shares the same processes even though the actual amount of material in each zone can vary significantly.

What does just in time delivery look like inside a Takt plan? Materials are staged in a supermarket or laydown area ahead of a required on job date, with a buffer length adjusted to current supply conditions, so the project pulls exactly what it needs at the moment of installation.

If you want to learn more we have:

Discover Jason’s Expertise:

To be an Expert!!!

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

Read 17 min

What It Actually Takes To Become An Expert Builder

Here’s the deal. Everybody wants to be the expert in the room. Everybody wants their name attached to results. But very few people are willing to pay the actual price it takes to get there. And in an industry that keeps shrinking the runway to leadership, that gap is starting to show up on jobsites everywhere.

Let’s name the pain first. A field engineer or PM gets handed a schedule that’s already in trouble. Maybe it’s not even their fault. Maybe five other people touched the plan before it landed on their desk, and now they’re the one expected to save it. They’re managing multiple buildings, running with almost no support, and quietly absorbing the consequences of decisions they never made. They start cutting corners on craftsmanship just to keep the schedule alive. And underneath all of it is a question nobody wants to say out loud: how did I end up being the one who fixes everyone else’s mess?

Here’s the failure pattern underneath that pain. Somewhere along the way, a team learned that if things go bad enough, somebody else will show up and clean it up for them. A closer. A field director. A general superintendent parachuting in to save the job. And once that pattern gets established, the original team never has to build the muscle of fixing their own work. They just wait. They pawn it off. And the cycle repeats itself project after project.

The system failed them; they didn’t fail the system. The people creating the mess usually aren’t malicious. They’re operating inside a structure that never taught them accountability meant fixing your own work, not handing it to whoever’s willing to carry it. Real accountability looks like the crew that installed a wall a foot too high being the crew that chips it down, no matter how busy they are. It looks like the superintendent and the PM sitting in the same root cause meeting as everyone else when a safety incident happens, not delegating the paperwork downstream. It looks like business development and pre-construction leaders getting compensated on the profitability of the work they bring in, not just the volume. Every one of these examples ties outcome to ownership.

There’s a field story here worth telling straight. A project was heading into what amounted to a crash landing, and the ask came in loud and clear: come fix it. The instinct in that moment is to swoop in, make the hard calls solo, and hand the team a rescued schedule with a bow on it. That instinct was rejected on purpose. Instead, the team got rallied together. Hard decisions got made about moving people around, but the team made them together and executed them together. By the time the job stabilized, that crew was proud. They were on fire, healthy, and glad because they had done it themselves. Nobody got saved by a hero. The system got repaired by the people standing in it.

Why does this matter beyond one project? Because every time a struggling team gets bailed out instead of coached through the fix, they learn nothing, and the exact same failure shows up on the next job with the exact same crew. That costs schedule. It costs quality, because the person doing the rescuing is usually stretched across too many buildings to catch every craftsmanship detail. And it costs the people underneath the chaos, because burnout doesn’t stay on the jobsite. It follows people home to their families.

So what actually builds someone into the kind of leader who doesn’t need rescuing, and doesn’t create situations that require it? There’s a real answer, and it isn’t shortcuts.

Read The Field, Not Just The Feed

The first fundamental is reading deeply in your field, not skimming social posts about it. Distilling the best thinking from history and applying it to your own work is one of the most underrated habits in construction leadership. Field engineering manuals, leadership books, and the hard lessons already documented by people who went through the fire before you exist for a reason. If someone isn’t willing to read the foundational material in their field, they aren’t ready to claim expert status in it, no matter how confident they sound in a meeting.

This connects directly to knowing your history. Understanding how the last twenty, fifty, even a hundred years of your industry developed gives context for why systems exist the way they do. It’s the difference between blindly following a process and actually understanding why that process protects flow, safety, and people. Biographies, history lessons, and the books themselves carry this context, and skipping it means operating without a foundation.

Ten Years Of Actually Doing It

The second fundamental is time in the field applying what you’ve learned. Not everything that works on paper works in the real world, and it only becomes real once you’ve applied it yourself, made mistakes with it, and adjusted. There’s a meaningful difference between someone who has read about Takt planning and someone who has implemented Takt planning, run into resistance, redesigned the zones, and made it work on an actual crew. You can hear that difference the moment someone starts talking. People who have lived it speak with depth. People who haven’t tend to circle the same surface-level talking points because that’s as far as their experience goes.

This is exactly why credentialing shortcuts should worry every leader in this industry. Compressing a fifteen year track record into five years might solve a staffing gap, but it doesn’t solve the readiness gap. A superintendent running a project over two million dollars who doesn’t know how to build a schedule, doesn’t understand zone control, and can’t run a proper Last Planner meeting isn’t positioned to lead that job. That isn’t an insult. It’s a warning that skipping the runway hurts more people than it helps.

Find People Who Will Tell You The Truth

The third fundamental is surrounding yourself with a community of people who are actually doing the work and are willing to talk honestly about where it went wrong. Sharing mistakes openly with peers who are further ahead, or walking the same road, sharpens everyone in the group. If someone wants to grow into an expert, they need people around them who will challenge their thinking instead of just applauding it. Isolation breeds blind spots. Community closes them.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Connecting It Back To The Mission

None of this is about chasing a title faster or padding a resume. It’s about protecting the people who will one day be led by whoever earns that expertise, or suffer under whoever fakes it. Real leadership development respects the crews standing underneath every decision a superintendent makes. It respects the families waiting at home for someone who didn’t have to burn themselves out covering for a team that was never taught to own its own work. Dignity on a jobsite starts with leaders who actually know what they’re doing, because that knowledge is what keeps zones flowing, mistakes owned, and people protected.

Building real expertise takes patience most people don’t want to have anymore. It takes reading the hard books, learning the history nobody’s teaching in a two week onboarding, spending a decade actually testing ideas against real conditions, and staying close to people who will tell the truth about your blind spots. There isn’t a version of this that gets shortcut without cost, and the cost usually lands on the crew, not the person who cut the corner.

Here’s the challenge this week. Take an honest look at where you are on those four fundamentals. Are you reading the books that built the people you respect most? Do you understand the history behind the systems you’re using every day? Are you actually applying what you learn, or just talking about it? And do you have people around you willing to call out your mistakes before the field does it for you. As it’s been said, there’s a difference between people who just say something and people who actually know something. Choose to be someone who knows.

On we go.

Frequently Asked Questions

Why does experience matter more than credentials in construction leadership? Credentials show completed steps, but experience shows whether someone can actually apply concepts like Takt planning or Last Planner under real field conditions. Without that applied experience, leaders make decisions they don’t fully understand the consequences of.

What does true accountability look like on a jobsite? True accountability means the people responsible for a mistake are also responsible for fixing it, whether that’s a crew correcting bad work or a superintendent sitting through a root cause analysis instead of delegating it away.

Why shouldn’t a struggling project just get “rescued” by a senior leader? Rescuing a project without involving the original team means the same team will likely repeat the same mistakes on the next job. Coaching the team through the fix builds capability instead of dependency.

How long does it really take to become an expert in construction leadership? Based on real field experience, meaningful expertise typically develops over roughly ten years of consistent application, paired with continuous reading, historical context, and honest feedback from a trusted community.

What’s the risk of promoting superintendents too quickly? Promoting someone before they understand scheduling, zone control, and fundamental Lean and Takt principles puts the whole project at risk, and ultimately hurts the crews depending on that leader’s decisions.

If you want to learn more we have:

Discover Jason’s Expertise:

Why Are Construction Labor Shortages Getting Worse?

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

Read 16 min

There Is No Labor Shortage. There Is a Willingness to Train Shortage.

Here’s the deal. Everyone keeps posting that construction has a labor shortage. It does not. There are plenty of capable people who want to work in this industry. What we actually have is a willingness to train shortage, and a serious problem misusing the workforce we already have.

That distinction matters enormously, because the fix for a labor shortage and the fix for a training shortage are completely different things, and we have been solving for the wrong problem for years.

Qualified People Cannot Even Get an Interview

I get reached out to on my phone probably fifteen times a day by people who are genuinely qualified. Ex-military. Ex-law enforcement. Top performers in other fields, hungry to move into construction. And they cannot get an interview. They cannot even get recognized by a recruiter.

Here is why. An owner tells a recruiter to go find people. The recruiter, with no other direction, screens for the same narrow bar every time: five, ten, or fifteen years of construction experience, plus a college degree in construction management. That filter eliminates almost every genuinely capable candidate who does not already come from inside the industry, including people with exceptional leadership, discipline, and transferable skill from other demanding fields.

And here is the part that exposes the real problem underneath the excuse. Anyone who already has that experience and works at another company is usually staying there, because loyalty and decent pay tend to keep good people in place. So the pool being screened for is largely a pool that is not actually available to move. We keep looking for people who already know everything and already have somewhere else they would rather stay.

Think about what that actually means for the industry as a whole. If every company is competing exclusively for the same narrow pool of already experienced people, the total number of people doing the work never grows. Companies just trade the same limited group back and forth, bidding wages up in the process, while a much larger pool of willing, capable people sits entirely outside the search because nobody built a pathway for them to get in. That is not a shortage of people. That is a self-inflicted bottleneck at the hiring filter.

We Do Not Train People, and Then We Call It a Shortage

Even when a genuinely capable person does get hired without the traditional background, most companies do not actually train them once they arrive. There is a real, ongoing shortage of formal training, mentorship, and development inside this industry, and it has been quietly getting worse as companies get larger without growing their appetite to develop the people inside them.

Watch for these signs your organization has a training problem disguised as a hiring problem:

Job postings requiring years of construction specific experience for roles that could realistically be trained
Recruiters filtering out candidates with strong transferable skills purely because their background is not construction
New hires receiving little to no structured onboarding or mentorship after they start

This is not a lie told with malice. It is an excuse that has become comfortable, a way of pawning the shortage problem off onto the labor market instead of looking honestly at hiring criteria and training investment. Saying there are no available workers requires nothing of a company. Admitting that the company has not built the training capacity to bring new people up to speed requires an actual investment, and that difference is exactly why the easier story keeps getting repeated.

We Are Also Misusing the People We Already Have

Here is a number worth sitting with. It sometimes takes eighty electricians on a project to do work that should realistically take fifteen, because of how poorly that work is coordinated and sequenced. That is not a labor shortage. That is a Lean and production planning failure, dressed up as a workforce problem.

When trades are stacked, burdened, and poorly sequenced, projects respond the only way they know how: throwing more bodies at the problem. More electricians, more crews, more overtime, none of which fixes the underlying coordination failure that made the extra headcount necessary in the first place. A project running genuine Takt planning, with real zones, real flow, and real buffers, needs a fraction of the labor that a poorly coordinated project burns through trying to compensate for chaos. We do not have too few electricians. We have too little discipline in how we deploy the ones we already have.

This is the part that should really change how companies think about hiring pressure. Every unnecessary body added to compensate for a broken schedule is a person who could have been deployed on a different project, or trained into a role the industry claims it cannot fill. The perceived shortage and the actual coordination failure are the same problem wearing two different names.

Why This Connects to Deming’s Warning About Quality

Edwards Deming argued that if a country loses its focus on quality, economic decline follows, because a country is genuinely defined by what it produces. That warning applies just as directly to how we treat our own workforce as it does to the products coming off a line.

An industry that will not train its people and will not deploy them efficiently is not optimizing for quality. It is optimizing for the appearance of caution, hiring only people who already look safe on paper, while ignoring the actual production science that would let existing people do far more with far less waste. That is a quality problem wearing a labor shortage costume.

What Fixing This Actually Requires

The fix here is not complicated to describe, even though it takes real commitment to execute. Recruiters need direction that goes beyond years of experience and a specific degree, so genuinely capable candidates from military, law enforcement, and other demanding backgrounds can actually reach an interview. Companies need to build real onboarding and mentorship programs for the people they do hire, rather than assuming experience will simply transfer on its own. And projects need to apply real Takt planning and Lean coordination so that the people already on the payroll are being used efficiently instead of being stacked on top of each other to compensate for poor sequencing.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your organization build the training systems and Takt based coordination that actually solve this problem, instead of continuing to blame a labor market that has plenty of willing, capable people in it. The shortage is not out there. It is inside our own hiring filters and our own unwillingness to train.

So here is the challenge. Look at your last five job postings and ask honestly whether the experience requirements would have screened out someone genuinely capable but new to construction. Then look at your current project and ask whether the headcount on any given trade reflects real production planning or simply reflects chaos being solved with more bodies. Both answers point to the same underlying fix.

Jason Schroeder said it plainly: “We don’t have a labor shortage. We have a willingness to train shortage.” Solve that, and the shortage disappears.

On we go.

FAQ

If there are plenty of capable people, why do so many construction companies still say they cannot find workers?
Because most hiring filters are built around narrow criteria, typically years of construction specific experience plus a relevant degree, which screens out genuinely capable candidates with transferable skills from other fields. Recruiters given no other direction default to that filter, and the pool of people who already meet it is largely people who are already employed and reasonably content where they are, which creates the appearance of scarcity even when capable candidates are actively trying to get in.

How does poor project coordination turn into what looks like a labor shortage?
When trades are stacked, burdened, or poorly sequenced, a project compensates by adding more crews and more hours rather than fixing the underlying planning problem. That drives headcount far higher than the actual scope of work requires, creating a demand for labor that is really a demand for better coordination. Projects run on real Takt planning and Lean sequencing typically need meaningfully fewer people to accomplish the same scope.

What should a company change first if it wants to actually solve this instead of blaming the labor market?
Start with hiring criteria, since that is the first filter blocking capable candidates from ever reaching an interview. Build genuine onboarding and mentorship for anyone hired without a traditional construction background, since a lack of structured training is what turns a promising hire into a frustrated one. From there, apply real production planning to reduce the artificial headcount inflation caused by poor coordination.

If you want to learn more we have:

Discover Jason’s Expertise:

Should Every Construction Company Use Takt Planning?

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

Read 16 min

Should Every Construction Company Use Takt Planning?

Here’s the deal. Every company should use Takt planning. Not most companies. Not companies of a certain size or project type. Every single one, and I have yet to find a genuine exception after years of applying it across every kind of project our industry produces.

Civil work. Industrial. Oil and gas. Renovations. Small projects and massive ones. Rhythmic projects and projects that do not repeat in any obvious way. Takt planning works across all of it, because it is built on a time by location format, and that format is what actually captures how construction happens, regardless of the sector or scope.

Why the Format Itself Does the Heavy Lifting

A Takt plan is color coded and organized by time and location together, which means you can see flow directly on the page instead of inferring it from a list of disconnected activities. You can calculate the buffers your plan actually needs. You can spot where trade stacking or trade burdening is about to happen before it costs anyone real time. Every piece of production and operation science that actually governs how work moves through a system sits underneath this format, visible on a single page.

That single page visibility is not a minor convenience. It means every core Lean principle shows up in one place at the same time. Respect for people, because the plan does not force anyone into rushed, uncoordinated work. Stable environments, because zones and sequences are defined rather than improvised daily. One piece flow, because the plan focuses on completing one thing at a time instead of batching everything at once. Takt time applied wherever it genuinely fits. Visual management, because the whole plan is meant to be looked at and understood quickly, not decoded. And a focus on one quality product moving through at a time, repeated consistently enough that the team can actually improve it project over project.

Compare that to a typical activity list schedule, where a superintendent has to mentally reconstruct flow, buffers, and trade conflicts from hundreds of disconnected bars. A Takt plan puts all of that reasoning directly into the visual itself, so anyone looking at the page, not just the person who built it, can see whether the project is actually set up to succeed.

Even Non-Rhythmic Projects Benefit

People sometimes assume Takt only works on rhythmic projects, meaning ones with obvious repetition floor to floor or unit to unit. That assumption is wrong, and the actual numbers back that up.

A genuinely rhythmic project experiences roughly eleven distinct benefits from Takt planning. A non-rhythmic project, one without that obvious repeated structure, still experiences somewhere between seven and nine of those same benefits. That is not a marginal win. Losing two to four benefits out of eleven still leaves the large majority of the value intact, which is exactly why there is no real category of project where Takt planning fails to be worth using.

Watch for these signs your project would benefit from Takt planning regardless of how rhythmic it looks:

A schedule where trade stacking or trade burdening is hard to spot until it has already caused a delay
No single page view where flow, buffers, and sequence are all visible together
A team that is currently managing chaos day to day rather than following a defined, stable rhythm

The Real Barrier Is a Mindset Shift, Not the Method

If Takt planning works everywhere, why does not every company already use it? The honest answer has nothing to do with the method itself. It is a mindset shift, and mindset shifts are genuinely hard.

Rushing, pushing, and panicking feels like productivity in the moment, even though it consistently produces worse outcomes than a properly planned, steady rhythm. Takt planning requires the opposite instinct. You actually have to know what you are doing before you start, plan the work deliberately, respect the people executing it, and keep environments stable instead of constantly improvised. That sounds like basic construction fundamentals, and it is, but basic fundamentals are exactly what gets abandoned first under schedule pressure. The mindset shift is choosing discipline over the adrenaline of constant firefighting, even when firefighting feels more urgent in the moment.

This is exactly why adoption lags behind proof. Nobody genuinely disputes that a steady, planned rhythm outperforms constant improvisation. The resistance comes from how uncomfortable it feels to slow down long enough to plan properly when a schedule already feels behind, even though that discomfort is precisely what a leveled, buffered Takt plan is designed to remove over time.

Takt Belongs in Design, Not Just Construction

Here is a piece of this that surprises people. Takt thinking does not have to wait for construction to start. It belongs in design too, just applied through a different set of tools depending on the phase.

Early on, in concept design and schematic design, methods like Scrum or Kanban fit that stage of work well, because design at that point is exploratory and iterative in a way that suits those tools. Once a project moves into design development, though, you can absolutely run a pull plan and map the design process onto an actual Takt plan. We do this regularly, and there is no reason design should be treated as fundamentally different from construction once it reaches that phase. There genuinely is not a category of project work, design included, that should not be based on Takt planning once it reaches the point where a defined sequence and rhythm make sense.

Why Toyota Would Say the Same Thing

If you asked the Japanese, or asked Toyota specifically, whether Takt matters, the answer would not be a qualified yes. Takt is the base of everything they do. Not one tool among many. The foundational unit that everything else in their production system is built on top of.

That is worth sitting with, because it means Takt is not a construction industry trend or a scheduling preference. It is a foundational production concept that happens to translate remarkably well into construction, civil work, industrial projects, and design, precisely because it describes something true about how work actually flows through any system with defined space and defined time, regardless of the industry applying it.

What Adopting This Actually Requires

None of this is really about convincing anyone that Takt planning works. The evidence for that is already overwhelming across every project type it has touched. The real work is the mindset shift, choosing to plan deliberately instead of reacting constantly, and choosing stability over the false comfort of constant urgency.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams make that shift, whether your next project is highly rhythmic, completely custom, still in design, or somewhere in an industry that has never used Takt planning before. The format adapts to the project. The mindset shift is what actually determines whether it succeeds.

So here is the challenge. If your company has been treating Takt planning as something reserved for repetitive, rhythmic projects, pick one non-rhythmic project currently in your pipeline and map it onto a real Takt plan anyway. Track how many of those seven to nine available benefits actually show up. The evidence tends to answer this question faster than the argument does.

Jason Schroeder said it plainly: “Takt planning is the best thing that ever happened to construction.” It works everywhere. The only real question is whether your team is ready for the mindset shift it requires.

On we go.

FAQ

Does Takt planning really work on projects with no obvious repetition, like a single custom renovation?
Yes, though the benefit profile shifts slightly compared to a highly rhythmic project. A genuinely rhythmic project experiences roughly eleven distinct benefits from Takt planning, while a non-rhythmic project still experiences seven to nine of those same benefits. The time by location format, the visibility into flow and buffers, and the focus on one piece flow all still apply, even without repeated floors or units to build the rhythm around.

Why does Takt planning require a mindset shift instead of just a new software tool?
Because the format only produces its benefits if the underlying behavior changes along with it. Teams accustomed to rushing, pushing, and panicking through a schedule have to actually plan deliberately, respect the people executing the work, and maintain stable environments instead of reacting to chaos as it happens. Adopting the visual format without adopting that underlying discipline tends to produce a nice looking plan that nobody actually follows.

How does Takt planning apply during the design phase of a project?
Early design work, like concept and schematic design, tends to fit better with iterative methods like Scrum or Kanban, since that stage of design is genuinely exploratory. Once a project reaches design development, a pull plan can map that design work onto an actual Takt plan the same way construction work gets mapped, treating design as a phase with its own zones, sequence, and rhythm rather than as an exception to production planning.

If you want to learn more we have:

Discover Jason’s Expertise:

General Offerings

Company Offerings

Systems

Don’t Get A Big Head Just Because You Have A Little Authority

Where A Little Title Creates A Big Problem

When Position Gets Confused With Superiority

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

A Rude Email And An Honest Confession

Why This Distinction Matters

Authority Without Wisdom Is Just Noise

Position Is Not The Same As Respect Earned

What This Looks Like When It Goes Right

Signs Authority Is Going To Your Head

Connect To Mission

Ways To Keep Authority In Check

A Challenge For Every New Leader

Frequently Asked Questions

The Difference Between Consequences And Punishment On Your Jobsite

Where Leadership Goes Wrong On The Jobsite

Confusing Firmness With Harshness

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

Why Respect For People Has To Come First

Why This Distinction Matters

Consequences Versus Punishment

What This Looks Like In The Field

Signs You’re Leading With Punishment Instead Of Consequences

Building Accountability The Right Way

Connect To Mission

Ways To Respond With Consequences This Week

A Challenge For Every Leader

Frequently Asked Questions

The Five Kanban Mantras That Keep Construction Flowing

Where Construction Teams Actually Lose Time

Why Handoffs Keep Breaking Down

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

A Simple Picture Worth A Thousand Schedules

Why This Matters On Your Project

What Kanban Actually Means For Your Site

Focus On The Baton, Not Just The Runners

Stop Starting And Start Finishing

Don’t Jam The Motorway

Just Enough, Just In Time

Flow, Then Pull, Never Push

Signs Your Site Is Jamming The Motorway

Turning Mantras Into Daily Habits

Connect To Mission

Quick Wins To Build A Pull Mindset This Week

A Challenge For Your Crew

Frequently Asked Questions

Why Resourcefulness Beats Resources On Every Project

Where Teams Default To Buying Their Way Out

Fixing Resourcefulness Problems With Resources

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

A Shed, Some AstroTurf, And A Business Built On Resourcefulness

Why This Distinction Actually Matters

The Real Cost Of Choosing Lavish Over Resourceful

What Resourcefulness Actually Means

When After Hours Work Becomes A Warning Sign

Signs A Team Is Masking Waste With Resources

Coaching A Team Toward Resourcefulness

Connect To Mission

Questions To Ask Before You Buy Your Way Out

A Challenge For Your Team

Frequently Asked Questions

The Ladder Of Accountability Every Leader Should Climb

Where Teams Quietly Slide Into Victim Mode

Four Behaviors That Keep People Stuck

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

Even The King Of Victim Mode Can Change The Habit

Why Climbing The Ladder Actually Matters

Acknowledge Reality, Then Own It

Find Solutions, Then Make It Happen

Figuring It Out Does Not Mean Figuring It Out Alone

Signals You Are Sliding Toward Victim Mode

Connect To Mission

Questions To Climb Toward Accountability

A Challenge For Every Team

Frequently Asked Questions

The Things A CEO Can Never Fully Delegate

Where Delegation Quietly Turns Into Absence