How to Respond to a Super when He Says….

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

Read 16 min

What To Say When A Superintendent Asks For The Impossible

Every trade partner eventually hears some version of the same sudden demand, usually at the worst possible moment in a busy week. I need more manpower. I need you to work overtime. I need you to work this weekend. How that moment gets handled says more about a company’s discipline and long term reputation than almost anything else on the project, because the response either protects flow or quietly damages it for the remainder of the job.

Where Sudden Demands Trigger The Wrong Response

The instinct when a superintendent makes an urgent request is to react immediately, either by scrambling to comply no matter the cost, or by getting defensive and pushing back emotionally in a way that damages the relationship. Neither response actually solves anything. Both reactions skip the one step that matters most, actually looking at what the data says before agreeing to anything, and both tend to create more problems than they solve once the dust settles.

Reacting Instead Of Diagnosing

The failure pattern shows up constantly on projects run without real discipline around flow and rhythm. A superintendent feels behind, panics, and reaches for the first lever that feels like action, more people, more hours, more urgency. The trade partner, wanting to look responsive and helpful, says yes immediately without checking whether the request actually addresses the real problem. Everyone feels busy. Almost nothing actually improves, and the same pressure often resurfaces again within a week or two.

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

The system failed them, they did not fail the system. Plenty of superintendents were never trained in Takt planning, trade flow, or how to diagnose a schedule problem before reacting to it. They are, in a very real sense, pretending to be superintendents without ever having received the training the role actually requires, pointing and demanding instead of planning and coordinating. That is not a character flaw. It is a gap that shows up as pointing, demanding, and reacting instead of planning, and it is worth responding to with patience rather than frustration.

Trade Flow Is Like Money In Monopoly

One useful way to picture this comes straight from a board game almost everyone already understands. In Monopoly, as long as you have plenty of money, you can absorb almost anything, a bad roll, an unlucky property, a big rent payment. Trade flow works the same way for a trade partner. As long as a crew keeps moving from area to area at a consistent pace, with real distance and rhythm protected, roughly eighty percent of that flow, a trade partner can absorb plenty of disruption along the way without it becoming a real crisis. Lose that flow entirely, and everything starts to collapse just as fast as running out of cash on a Monopoly board, no matter how hard everyone suddenly starts working.

Why This Distinction Matters

This matters because reactive requests, more people, more hours, more pressure, often make an actual schedule problem worse rather than better, no matter how urgent the moment feels at the time. Adding a large number of new workers into an area rarely delivers proportional speed. New crews create coordination overhead, unfamiliarity with the site, and a real loss in productivity right when a project can least afford it. The same principle behind why adding massive headcount to a struggling initiative usually backfires applies just as directly to a construction crew under pressure, and it is worth remembering the next time a quick fix feels tempting.

The Right First Question Every Time

The response to nearly every sudden demand starts the same way. Let’s look at this together. That single phrase turns a reactive moment into a collaborative one, and it opens the door to the actual diagnostic conversation that needs to happen before anyone commits to anything, whether that means adding people, working extra hours, or moving an entire crew somewhere new.

Manpower, Overtime, And Weekend Work

When a superintendent asks for more manpower, the real question is whether the crew is actually behind schedule or whether the ask is really about accelerating an already reasonable pace. The same logic applies to overtime and weekend work requests. If a trade partner is genuinely behind, some extra hours for a short stretch is often reasonable. If the request is really about compressing the original schedule, that is a different conversation entirely, one that needs to look at cost impacts and whether the new pace is even realistic to sustain over time without burning out the crew.

Missing Answers, Area Holds, And Trade Stacking

When a superintendent says an answer is not available yet, the right move is to check whether that missing information is actually blocking the work, and if so, to find backlog work rather than letting a crew stand idle waiting around for a decision. When asked to hold off on an area, the conversation should center on backlog options and how the pause affects flow later in the schedule. When asked to move to a new area, or to work alongside another trade in a shared space, the right response is always the same, let’s look at this together, what is the plan, and will this protect or damage trade flow for everyone involved.

Signs A Superintendent Is Reacting Instead Of Managing

Watch for these patterns, which usually mean panic is driving the request rather than an actual plan grounded in the schedule.

Requests for more manpower with no reference to the schedule or plan
Pressure to accelerate without any conversation about cost or feasibility
Crews expected to sit idle waiting on answers with no backlog plan
Sudden area changes with no discussion of how flow will be protected

Connect To Mission

None of this is about being difficult or slowing down a project unnecessarily. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. It means responding to pressure with data and calm collaboration instead of panic, which is exactly what actually protects a schedule under stress, for the trade partner and the general contractor alike.

Questions To Ask Before Saying Yes Or No

Use these the next time a superintendent makes a sudden request.

What does the Takt plan say about where we actually stand right now
Is this request about recovering time or accelerating beyond the original plan
How will this decision affect our trade flow going forward
What does a genuine win win look like for both sides here

A Challenge For Every Trade Partner

Here is the challenge this week. The next time a superintendent makes a sudden demand, resist the urge to react immediately in either direction. Ask to look at the plan together first, and let the data guide the conversation from there. As has been said plainly, the game is all about trade flow, and protecting it is what actually lets a trade partner meet a schedule instead of just reacting to it every time pressure shows up.

On we go.

Frequently Asked Questions

What should a trade partner say when a superintendent suddenly demands more manpower on a project already underway? The right first step is asking to look at the schedule together, checking whether the crew is genuinely behind or whether the request is really about accelerating an already reasonable pace that was agreed to earlier.

Why does adding more people or hours often fail to fix a schedule problem on a construction project? New crews bring coordination overhead and unfamiliarity with the site, which frequently offsets any speed gained by simply adding headcount, especially under time pressure when there is little room left to absorb a genuine mistake or a slow first week.

What does trade flow actually mean and why does it matter so much on a real project? Trade flow means a crew moves from area to area at a consistent pace, speed, and distance, and protecting that rhythm is what allows a trade partner to absorb disruption without losing overall schedule performance across the life of the job.

How should a trade partner respond when asked to move areas or work alongside another trade on the same project? The right response is to look at the plan together, confirm materials and permissions are in place, and discuss directly how the move will affect trade flow going forward for both trades involved.

Why is staying calm and data focused better than reacting emotionally to a sudden demand on a busy project? A calm, data driven response protects the actual schedule and relationship, while an emotional reaction, whether blind compliance or pushback, tends to address the symptom instead of the real root cause sitting underneath it.

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.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo.

To Skin a Cat!

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

Read 16 min

Why We’re Doing That Is Not The Same As It’s Working

There are a thousand different ways to get a job done. But at the end of the day, the job actually has to be finished, completely, not just mostly, not just on the easy side. That distinction sounds obvious until you start actually testing it against how most teams talk about their own processes, day in and day out, on nearly every project they run.

Where Good Intentions Quietly Replace Real Results

Ask almost any team about a process, procurement, onboarding, huddles, cleanliness, and the answer comes back the same way every time, almost like a reflex nobody has ever questioned. Yeah, we do that. It sounds like confidence. Most of the time it is actually a guess, offered by someone who has never stopped to measure whether the process is genuinely working or just technically happening somewhere in the background of a busy project.

Confusing Activity With Effectiveness

The failure pattern is easy to miss because it feels so reasonable in the moment. Somebody asks if a process exists, and the answer is yes, so the conversation moves on. Nobody follows up by asking how well that process actually performs. A procurement system that exists on paper but leaves half the team guessing is still, technically, a procurement system. It just is not a working one, and the difference between those two things is where most real problems quietly hide until they surface as a bigger issue later, usually at the worst possible moment on a schedule.

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

The system failed them, they did not fail the system. Nobody teaches most teams to separate the question of whether something happens from the question of whether it actually works. Saying yes feels good. Admitting a process is only partly effective feels like failure, so most people default to the version of the truth that lets everyone feel fine about where things stand, even when the data would tell a very different story.

Mapping A Process Card By Card

One approach worth borrowing came from a company that had gotten genuinely good at mapping out its own processes in detail. Take onboarding as an example. Every single step, placing the job ad, screening applicants, the first interview, the background check, the team interview, the personality profile, a final round, the offer letter, gets its own card on a board. Once every step is visible, the real conversation can finally start, because now there is something specific to evaluate instead of a vague feeling about how onboarding generally goes as a whole.

Color Coding The Truth

The real value shows up once every card gets scored honestly, not on whether it happens, but on how well it actually works. A simple one to ten scale does the job. A card scoring zero through six gets marked as struggling. Seven or eight counts as solid. Nine or ten means it is genuinely humming along without friction. Suddenly a process that looked fine as a single vague impression turns into a specific, visual map of exactly which parts are working and which parts only look like they are working from a distance.

Why This Distinction Matters

This matters because a process running at fifteen or twenty percent effectiveness can still technically be called a process, and that gap between existing and working is exactly where budgets, schedules, and trust quietly erode over time. Nobody would accept a heart pumping blood at thirty five percent effectiveness, or a kidney filtering at fifteen percent, simply because it was still technically doing its job, and that comparison is worth sitting with for a moment. Yet plenty of teams accept exactly that level of performance from their procurement system, their huddles, their cleanliness standards, simply because something resembling the process is happening somewhere on the project, and nobody has stopped long enough to actually check.

What Conditions Of Satisfaction Actually Mean

A condition of satisfaction is the specific, complete outcome a process is actually supposed to produce, regardless of which method gets used to get there, and regardless of who ends up doing the work. A procurement system either gives full visibility into what is coming and when, or it does not. A huddle either puts real information and real conversation in front of a crew using visuals and metrics, or it is just someone walking around having quick one on one chats that feel productive but rarely are, no matter how well intentioned the effort behind them happens to be. The method can vary. The condition of satisfaction cannot be watered down and still count as met.

Stop Grading On Effort Alone

This same standard applies everywhere a team says the familiar phrase, we do that, whether the conversation is happening in a trailer, an office, or a boardroom far from the actual work. Takt planning implemented halfway is not Takt planning working. A procurement tracker that only lives inside a general project management tool without a dedicated log is not a procurement system doing its job. A clean site that still has debris, cords, and clutter scattered through half the work areas is not actually a clean site, no matter how confidently someone describes it that way in a meeting full of people nodding along in agreement. The question was never whether something is happening. The question is always how well it is working, and that question deserves an honest answer every time it gets asked.

Signs You’re Settling For We Do That

Watch for these signals the next time a process gets a passing grade nobody actually verified against real evidence.

Nobody can describe the specific outcome the process is supposed to produce
A yes or no answer replaces an actual effectiveness score
The same process gets described as working fine year after year with no measurement
Problems tied to that process keep resurfacing despite reassurance it exists and functions

Connect To Mission

None of this is about creating more paperwork for its own sake or slowing a project down with extra reporting. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. It means making sure the systems a team already believes in are actually delivering the results they were built to deliver in the first place.

How To Actually Measure If A Process Is Working

Use these steps the next time a process gets an automatic yes without anyone actually checking the details behind it.

Break the process into its individual component steps
Score each step honestly on how well it performs, not whether it exists
Ask what the real condition of satisfaction is before accepting an answer
Revisit the score regularly instead of assuming it stays true forever once it is set

A Challenge For Every Team

Here is the challenge this week. Pick one process your team already believes is working, and actually map it out, step by step, scoring each piece honestly instead of relying on a single overall impression. As Jason has said, I don’t care that you’re doing it, I want to know that it’s working. That single distinction changes how a team evaluates everything it already believes is fine.

On we go.

Frequently Asked Questions

What does conditions of satisfaction mean for a business process? It means the specific, complete outcome a process is actually supposed to produce, regardless of which method is used to get there, so a process only counts as successful when that full outcome is genuinely met, not just approximately met.

Why isn’t we already do that a useful answer when evaluating a process? That answer confirms something exists without measuring how well it actually performs, which allows weak or partially effective processes to keep being treated as successful indefinitely, sometimes for years at a stretch.

How does color coding help evaluate whether a process is actually working? Scoring each step of a process on a simple scale turns a vague overall impression into a specific, visual map of exactly which parts are effective and which parts only appear to be working.

Why does it matter if a process is only partially effective? A process running at a fraction of its real capacity can still technically exist, but it quietly produces the same ongoing problems a fully working process would have prevented in the first place.

Can this concept apply beyond one department? Yes. The same standard of measuring effectiveness instead of mere existence applies just as well to accounting, pre construction, bidding, scheduling, and project controls as it does to any single process on a jobsite, and the same color coded mapping approach works in every one of those settings too.

If you want to learn more we have:

Discover Jason’s Expertise:

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo.

If It Made You Better…

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

Read 16 min

Why Did You Like It Is The Wrong Question After Every Meeting

I don’t care if you liked it. That line sounds harsh out of context, and it is worth sitting with anyway, because it points at one of the most common mistakes construction teams make after every meeting, training, and coaching session. The question we ask at the end of these gatherings shapes what we actually learn from them, and most teams are asking the wrong one.

Where Feedback Quietly Goes Wrong

Walk out of almost any Last Planner meeting, pre construction session, or training day, and the closing question sounds the same everywhere across the industry. What did you like about this? What did you not like? It feels considerate. It feels like good facilitation. But it quietly trains an entire team to evaluate serious, purposeful work the same way they would rate a restaurant.

Confusing Preference With Purpose

The failure pattern is simple to spot once you see it. A meeting, training, or coaching session exists to accomplish something specific, move a schedule forward, align a team, build a skill, solve a real problem. But the feedback collected at the end rarely asks whether that purpose was met. It asks whether people enjoyed the experience, which produces whimsical, emotional opinions rather than logical assessments of whether the work got done. That is not a character flaw in the people answering. It is simply what happens when the question invites comfort instead of results.

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

The system failed them, they did not fail the system. Nobody sits facilitators down and draws a clear line between preference feedback and purpose feedback. Asking what someone liked is the natural question, the same one we ask about a movie or a meal, so it gets carried into boardrooms and trailer meetings without anyone questioning whether it actually helps. The habit is understandable and easy to fall into. It is simply aimed at the wrong target.

A Boot Camp Story About Two Different Kinds Of Feedback

One company sent three superintendents through a boot camp together. One of them came in fully invested, applied what he learned, earned a promotion, and came back a genuine advocate for the program. The other two came in without much buy in, were not performing well before they even arrived, and left focused entirely on what they personally found uncomfortable rather than what the program actually accomplished. Their feedback centered on preference, not purpose, and it was loud enough that the company never sent another employee to the training again. Dozens of people at that company lost access to real development because two voices talked about comfort instead of outcome, while dozens of other participants from other companies came through the exact same program and left as genuine advocates for it.

Why This Distinction Matters

This matters because preference based feedback does not just waste a survey question. It quietly shapes whether valuable training, coaching, and meetings continue to happen at all. When leadership hears complaints about how something felt instead of whether it worked, the easy decision is to cancel the program rather than question the feedback itself. Multiply that pattern across every Last Planner meeting, safety training, and pre construction session, and preference driven feedback becomes a slow leak on a team’s actual growth. Real improvement requires real signal, and comfort is rarely the same thing as signal.

What A Coach Is Actually For

The word coach comes from the same root as a horse drawn carriage, something built to move people forward from one place to another. A personal trainer who pushes you through a hard workout is not there to be liked in the moment. They are there to move you forward. The same is true for a sports coach, a business coach, or a facilitator running a collaborative planning session. Whether the experience felt comfortable was never the actual point, and judging a coach by comfort instead of progress misunderstands the entire job description.

The Heart Surgeon Test

Picture someone who just went through a difficult heart surgery followed by months of painful rehabilitation. Nobody asks that person whether they liked the surgery. The only question that matters is whether it worked. Did the heart get fixed? Can they live another twenty or thirty years because of it? That same standard belongs in every meeting, training, and coaching session that construction teams run. The right question was never about comfort. It was always about whether the purpose got accomplished.

Ask Purpose, Not Preference

The fix is straightforward. Before ending any meeting, training, or coaching session, state the purpose out loud first. This meeting was for us to accomplish a specific outcome. Then ask what actually helped accomplish that outcome, and what could accomplish it even better next time. That single shift moves the conversation away from whimsical opinions and toward real, usable feedback the team can act on immediately.

Try A Plus Delta Instead Of Like Dislike

A plus delta captures this shift in one simple tool. Instead of asking what people liked or disliked, ask two purpose anchored questions. What accomplished the purpose of this session. What could better accomplish the purpose of this session. Both questions stay tied to the actual goal instead of drifting into personal comfort, and both produce feedback a team can genuinely use to improve the next meeting.

Purpose Belongs At The Start, Not Just The End

This same fix works even better when it happens before a meeting ever starts. Open every gathering by stating the purpose out loud. This is why we are here. This is what we are trying to accomplish. Say it plainly, even when the topic is difficult. A team that walks into a meeting already knowing its purpose is far less likely to drift into personal opinions by the time that meeting ends, because the standard for success was set before anyone had a chance to make it about comfort.

Where This Applies Beyond The Boardroom

This shift matters everywhere a team gathers with a purpose, and construction runs on exactly this kind of gathering almost every single day.

Last Planner and collaborative planning meetings
Pre construction and IPD sessions
Safety trainings and organizational transformation sessions
Leadership meetings and budget reviews

Connect To Mission

None of this means ignoring how people feel, and it does not mean feedback has to be cold or dismissive of real concerns. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. It means making sure the purpose of the gathering, not personal comfort, drives whether the team calls it a success.

Questions To Ask Instead Of Did You Like It

Use these the next time a meeting, training, or coaching session wraps up and it is time to gather real, useful feedback.

What was the actual purpose of this session
What accomplished that purpose well
What could accomplish that purpose even better
Are we reacting to comfort or to results

A Challenge For Every Leader

Here is the challenge this week. In your very next meeting, training, or coaching session, skip the question of what people liked. State the purpose clearly, then ask what accomplished it and what could accomplish it better. As Jason has said, if we are always just worried about what we like, then we will never engage in real conversations, real feedback, or real solutions. Purpose first, comfort second, every single time.

On we go.

Frequently Asked Questions

Why is asking what did you like the wrong question after a meeting or training? That question collects emotional, comfort based opinions instead of information about whether the actual purpose of the meeting was accomplished, which limits how useful the feedback really is.

What is a plus delta, and how is it different from asking about likes and dislikes? A plus delta asks what accomplished the stated purpose of a session and what could accomplish it even better, keeping feedback tied to outcomes instead of personal comfort.

Why does the heart surgeon analogy matter for how teams think about training? Nobody asks whether a heart surgery patient enjoyed the procedure, only whether it worked, and that same standard of effectiveness over comfort belongs in how teams evaluate meetings and training.

What does the word coach actually mean, and why does that matter? Coach shares its root with a horse drawn carriage, something built to move people forward, which is a reminder that a coach’s job is progress, not popularity.

How can a small amount of negative preference based feedback affect a whole team? When leadership hears complaints about comfort instead of outcomes, the easy response is often to cancel a valuable program entirely, which can cut off many other people from real development over the input of just a few voices.

If you want to learn more we have:

Discover Jason’s Expertise:

Stay Loose, Feat. Bert Sarkkinen

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

Read 16 min

Why Staying Loose Beats Gripping Tighter Under Pressure

The best way to go through hard times is to stay loose. That line opened a recent conversation with Burt Sarkinen, a timber framer with nearly fifty years in construction and author of The Art of Hybrid Timber Framing, and it is worth sitting with because most people do the exact opposite the moment things get hard.

Where Pressure Quietly Makes Everything Worse

The instinct under real pressure is almost always to grip tighter. Work longer hours. Force a decision before it is ready. Refuse to make a mistake in front of anyone. It feels like control. Most of the time, it produces the opposite, rushed judgment, strained relationships, and a body and mind running on fumes instead of clarity. The irony is that gripping tighter rarely solves the actual problem sitting underneath the pressure in the first place.

Confusing Effort With Control

The failure pattern is simple. Somewhere along the way, working harder becomes the only tool anyone reaches for when a project gets difficult. It worked often enough in the past to feel reliable, so it becomes the default, even when the actual problem has nothing to do with effort and everything to do with fear driven decision making. Gripping tighter feels like doing something. It rarely fixes what is actually wrong, and often it just delays the moment when the real issue finally has to be addressed.

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

The system failed them, they did not fail the system. Nobody teaches most construction professionals the difference between staying engaged and staying tense. The industry often glorifies grinding through exhaustion as proof of dedication, so it is no surprise that plenty of good people default to squeezing harder the moment a project gets scary, simply because nobody ever modeled a calmer way through.

A Fifty Year Career Built On Not Rushing

Burt’s own story makes the point well. He started framing homes with his father after high school, and at one point turned down a real wage increase specifically to keep learning the craft longer instead of rushing ahead. That decision built a foundation nothing else could have replaced. Years later, during the Great Recession, an old habit of simply working harder finally stopped being enough. The pressure forced a real shift, from gripping every outcome tightly to genuinely trusting the process and showing up each day with a steady, working heart instead of a clenched fist. It was not an overnight change. It took an economic downturn severe enough to make the old approach impossible to sustain before the new one finally stuck.

Why This Distinction Actually Matters

This matters because construction runs on relationships that get tested and rebuilt project after project, year after year, decade after decade in a career. Fear driven decisions tend to cost more than they save. Fear rushes negotiations, damages relationships with clients and employees, and pushes people into survival mode exactly when clear thinking matters most. Staying loose is not the same as staying careless. It is the difference between showing up steady and showing up scared, and only one of those postures makes room for good judgment when a project actually needs it most.

What Staying Loose Actually Means

Staying loose does not mean disengaging or lowering your standards. It means separating your effort from your grip on the outcome. Wake up, do the work in front of you with a steady heart, and let go of the need to control every result through sheer force. That shift takes the edge off mistakes that would otherwise trigger panic, and it changes how a person shows up in conversations with clients, trade partners, and employees when things get tense. A steady person negotiates better, listens better, and recovers from setbacks faster than someone operating from fear.

Don’t Shortchange Your Early Years In The Craft

This same steadiness starts by respecting the years it takes to actually learn a trade. Too many people entering construction want to skip straight to a title, superintendent, project manager, without putting in real time on the tools or in the field first. That early time is not wasted. It builds a kind of knowledge that cannot be taught any other way, and it becomes the foundation every later decision gets built on, whether that decision is about scheduling, quality, or how to lead the very people once standing beside you on a crew.

Find Your Voice Before You Try To Lead Others

The second half of staying loose is knowing who you actually are. Burt described this as finding your voice, understanding what you are about, what genuinely excites you, and what fair compensation looks like for the value you bring. For anyone who feels like a wallflower or unsure of their own direction, something as simple as practicing public speaking in a structured group setting can force real clarity, because crafting a message and delivering it to other people quickly reveals what you actually believe. That same practice also sharpens listening skills and awareness, both of which matter just as much in a trailer meeting as they do on a stage.

A Simple Tool For Staying On Course

One practical habit worth borrowing is building a short decision compass, boiling down what you are actually trying to accomplish into just a handful of words. When a distracting option shows up, a flashy upgrade, an unnecessary feature, a shiny new direction, that short phrase becomes an easy test. Does this still point toward what we actually said we wanted? If not, it gets set aside without much drama. The same tool works just as well for a company setting priorities as it does for a homeowner picking finishes.

Signs You’re Gripping Too Tight

Watch for these before exhaustion or a bad decision forces the issue into the open.

Reaching for longer hours as the only response to a hard project deadline
Treating every mistake as a crisis instead of information
Feeling unable to relax even when nothing urgent is actually happening
Making rushed calls just to feel like something has moved forward today

Connect To Mission

None of this means lowering the bar on quality, schedule, or safety on your project. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. It means carrying those standards with a steady hand instead of a clenched one, because steady hands make better decisions than fearful ones ever will.

Ways To Practice Staying Loose

Use these the next time pressure tempts you to grip tighter instead of steadier on a project that matters.

Separate the effort you control from the outcome you do not
Write down a short decision compass before a big choice
Journal a few grateful moments at the end of a hard day
Ask what is actually true right now instead of what you fear might be true

A Challenge For Every Builder

Here is the challenge this week. The next time a project gets hard, notice whether you are gripping tighter out of fear or staying steady out of trust in the process you have built. As it has been said, even if a person thought they were going to face the worst tomorrow, the right move is still to plant an apple tree today. Show up, do the work in front of you, and let go of the parts that were never yours to control in the first place.

On we go.

Frequently Asked Questions

What does staying loose actually mean if it is not just relaxing? Staying loose means separating your effort from your grip on the outcome, showing up steady and engaged without letting fear drive rushed decisions or constant tension.

Why shouldn’t new construction professionals rush past hands on trade experience? Early time spent actually learning a craft builds a foundation of knowledge that cannot be taught through titles or shortcuts, and that foundation supports every leadership decision made later in a career.

What is a decision compass and how does it help avoid distraction? A decision compass is a short phrase, often just a handful of words, that captures what you are actually trying to accomplish, giving you a quick test to filter out distracting options that do not match your real goal.

How can someone start finding their voice if they feel unsure of themselves? Practicing structured public speaking in a group setting is one direct way to build clarity, since crafting a message and delivering it to others quickly reveals what you actually think and believe.

Why does gripping tighter under pressure often make outcomes worse for a project? Fear driven decisions tend to rush judgment and strain relationships, while a steadier, trust based approach protects the clear thinking that difficult projects actually require to finish well.

If you want to learn more we have:

Discover Jason’s Expertise:

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:

Discover Jason’s Expertise:

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:

General Offerings

Company Offerings

Systems

What To Say When A Superintendent Asks For The Impossible

Where Sudden Demands Trigger The Wrong Response

Reacting Instead Of Diagnosing

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

Trade Flow Is Like Money In Monopoly

Why This Distinction Matters

The Right First Question Every Time

Manpower, Overtime, And Weekend Work

Missing Answers, Area Holds, And Trade Stacking

Signs A Superintendent Is Reacting Instead Of Managing

Connect To Mission

Questions To Ask Before Saying Yes Or No

A Challenge For Every Trade Partner

Frequently Asked Questions

Why We’re Doing That Is Not The Same As It’s Working

Where Good Intentions Quietly Replace Real Results

Confusing Activity With Effectiveness

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

Mapping A Process Card By Card

Color Coding The Truth

Why This Distinction Matters

What Conditions Of Satisfaction Actually Mean

Stop Grading On Effort Alone

Signs You’re Settling For We Do That

Connect To Mission

How To Actually Measure If A Process Is Working

A Challenge For Every Team

Frequently Asked Questions

Why Did You Like It Is The Wrong Question After Every Meeting

Where Feedback Quietly Goes Wrong

Confusing Preference With Purpose

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

A Boot Camp Story About Two Different Kinds Of Feedback

Why This Distinction Matters

What A Coach Is Actually For

The Heart Surgeon Test

Ask Purpose, Not Preference

Try A Plus Delta Instead Of Like Dislike

Purpose Belongs At The Start, Not Just The End

Where This Applies Beyond The Boardroom

Connect To Mission

Questions To Ask Instead Of Did You Like It

A Challenge For Every Leader

Frequently Asked Questions

Why Staying Loose Beats Gripping Tighter Under Pressure

Where Pressure Quietly Makes Everything Worse

Confusing Effort With Control

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

A Fifty Year Career Built On Not Rushing

Why This Distinction Actually Matters

What Staying Loose Actually Means

Don’t Shortchange Your Early Years In The Craft

Find Your Voice Before You Try To Lead Others

A Simple Tool For Staying On Course

Signs You’re Gripping Too Tight

Connect To Mission

Ways To Practice Staying Loose

A Challenge For Every Builder

Frequently Asked Questions

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