Don’t Just Do Something, Stand There

Posted on August 24, 2026August 24, 2026 by Team Jason Schroeder

Read 9 min

Don’t Just Do Something, Stand There

Here’s the deal. There is a quote I want credit going to the right place for. Hal Macomber said it, and Adam Hoots is who reminded me of both the line and who said it. Don’t just do something, stand there. I love this quote, and I think it captures one of the most misunderstood ideas in all of construction.

Who gets credit for a good idea matters far less than whether the idea actually gets used. This one deserves to get used constantly, because it corrects a mistake that costs real money on almost every jobsite in America.

Why Keeping Everyone Busy Is a Bad Goal

Go back to Eliyahu Goldratt’s thinking on full kit and flow, and a specific truth becomes clear. People trying to look busy is a bad thing, not a good one.

Here is the example that makes it concrete. Picture a factory that needs a throughput of four parts an hour. The equipment on the line has different production rates: four parts an hour, then four, then two, then four, four, four, four. If you tell every single piece of equipment to run at its own maximum speed regardless of the others, you actually end up with something like one point two to one point eight parts an hour of real throughput. Everyone working flat out produces the worst result on the list.

If you double the capacity of that slow two part per hour machine, your throughput can reach the full four parts an hour the system needs. Alternatively, if you deliberately slow every other machine down to match that same two part per hour pace, running the faster machines only half the time, your throughput becomes two parts an hour. Slower on paper for most of the equipment, but a better real number than the chaos of everyone running full speed independently. Full speed everywhere is the worst option on the table, and matched pace beats maximum busyness every single time.

The Excavator Story That Makes This Real

Here is my favorite illustration of this, because it happens on real jobsites constantly. Picture an excavator operator on a civil crew who comes up to an unknown pipe that might or might not be in the way of the planned trench. The crew needs to figure out how to proceed, and rather than staying with the problem or stepping out of the cab to help solve it, the operator decides to go look busy somewhere else, wanting to impress the boss with visible activity.

Watch what actually happens next. Diesel gets burned for no productive reason. Equipment takes wear and tear it did not need to take. The work done elsewhere is now uncoordinated and has to be reworked, because it was not planned as part of the sequence. A pile that got moved during that detour is now sitting in the wrong spot, blocking something else. The equipment risks breaking down doing unplanned work. And once the original crew is ready to continue, they now have to wait for the operator to come all the way back and get reoriented to the actual problem, on top of whatever finished work got run over or disturbed during the detour.

All of that dollar waste happened because staying busy felt more valuable in the moment than standing still and solving the actual problem. It was not.

Watch for these signs someone is optimizing for looking busy instead of for flow:

A worker or piece of equipment relocating to unrelated work the moment the original task hits an unknown or a problem
A crew treating idle time as inherently bad, even when the alternative is uncoordinated, unplanned activity
Finished work getting disturbed or reworked because someone needed something to do in the meantime

Stop, Call, Wait

There is a phrase worth adopting directly from this. Stop, call, wait. Sometimes having a worker actually wait is the better outcome. Sometimes a foreman not actively working is the better outcome. Sometimes a zone sitting temporarily idle is the better outcome, because the alternative is pushing ahead without full kit or without a clear plan, and pushing a defect or an uncoordinated decision down the line is far more expensive than the appearance of lost time in the moment.

This connects directly to something worth holding as a standing habit on any project. If you see, hear, or sense something is not right, the correct response is to stop, call the right people in, and wait for a real answer before proceeding, not to keep moving in some other direction just to avoid looking idle.

Why “Don’t Just Stand There, Do Something” Gets Us in Trouble

Here is the instinct working against us. Our default in the United States tends to run the opposite direction. Don’t just stand there, do something. That instinct, so deeply ingrained that it feels like common sense, is exactly what produces the excavator story above, over and over, on jobsites everywhere.

The correct instinct runs the other way. Don’t just do something. Stand there until you actually know what you are supposed to do, which comes down to preparation, doing the work correctly the first time, and staying in a genuine flow rather than filling time with activity that has not been thought through. Worrying more about whether the work is actually flowing than whether everyone looks occupied is the entire shift in mindset this quote is pointing toward.

Resource Efficiency vs Flow Efficiency

There is a real framework behind why this works, described by researcher Niklas Modig as the distinction between resource efficiency and flow efficiency. Resource efficiency asks whether every person and every piece of equipment is being used as much as possible. Flow efficiency asks whether the actual work is moving smoothly and completely through the system.

Those two goals are not the same, and optimizing for the first one frequently damages the second. A jobsite obsessed with resource efficiency keeps everyone visibly busy and produces uncoordinated rework, wasted material, and wear on equipment that did not need to happen. A jobsite that genuinely prioritizes flow efficiency accepts that a worker standing still, a foreman not actively swinging a tool, or a zone temporarily unworked can be exactly the correct state, because the actual measure of success is whether work moves cleanly through the system, not whether every second looks productive on the surface.

Building This Into How Your Team Operates

None of this works if it stays a clever quote nobody actually applies under pressure. The instinct to look busy runs deep, and it takes real discipline, and real permission from leadership, to let a crew stop and wait when that is genuinely the correct move.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams build the discipline to prioritize flow over the appearance of busyness, including giving crews explicit permission to stop, call, and wait when a real problem shows up instead of filling the gap with unplanned activity. That permission has to come from leadership directly, because nobody wants to be the person standing still if they think it will be read as laziness.

So here is the challenge. Think about the last time someone on your project filled idle time with unplanned activity rather than stopping to solve the actual problem in front of them. Calculate honestly what that decision actually cost in rework, wasted material, or lost coordination. That number is usually a lot larger than the cost of simply standing there and waiting for the right answer.

Jason Schroeder said it plainly: “Stop, call, wait.” Sometimes the most productive thing a worker can do is exactly nothing, until the real problem gets solved.

On we go.

FAQ

Isn’t it always better to keep workers and equipment busy to maximize productivity?
No, and this is the core misunderstanding the quote addresses. Keeping every resource maximally busy regardless of the actual bottleneck in the system frequently produces worse total throughput than intentionally matching pace to the true constraint. A factory or jobsite optimized purely for resource utilization can end up slower overall than one that accepts some idle time in exchange for coordinated, planned flow.

What should a worker actually do when they hit an unexpected problem instead of finding other work to look busy?
Stop, call the right people in to look at the problem, and wait for a genuine resolution before proceeding, rather than moving to unrelated work in the meantime. Staying present with the problem, or stepping in to help solve it directly, avoids the uncoordinated rework, wasted material, and equipment wear that come from filling the gap with unplanned activity elsewhere.

What is the difference between resource efficiency and flow efficiency?
Resource efficiency measures whether every person and piece of equipment is being used as much as possible at any given moment. Flow efficiency measures whether the actual work is moving smoothly and completely through the system from start to finish. Optimizing heavily for resource efficiency often damages flow efficiency, since keeping everyone busy regardless of coordination tends to produce rework and waste that slows the overall project down.

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.

Trades Following the System

Posted on August 24, 2026August 24, 2026 by Team Jason Schroeder

Read 8 min

Trades Should Follow the System, Not Be Punished for Failing

Here’s the deal. A general contractor has to be genuinely firm about the environment, the cleanliness, the safety, the organization, and the logistics on a jobsite, while also being genuinely warm and caring toward the people working inside that system. People assume those two things contradict each other. They do not, and understanding why is one of the most important distinctions a GC can make.

There is a specific line worth drawing clearly. Care intensely whether trades are following the system. Never punish them for failing or making an honest mistake. Those are two completely different things, and treating them as the same thing is where a lot of leadership goes wrong.

Firmness and Warmth Come From the Same Place

People sometimes accuse me of running hot and cold. Nice with the small stuff, harsh with everything else. That is not accurate, and I want to explain why, because the explanation matters more than the accusation.

I send people home for zero tolerance violations because I respect them. I shut down crews to clean because I respect them. I hold a firm line on deliveries because I respect them. I also do barbecues because I respect them. I run worker huddles because I respect them. I shake hands and pick up trash myself because I respect them. Every single one of those actions, the firm ones and the warm ones, comes from the exact same source. A genuinely clean, safe, organized environment where bad behavior is not tolerated is one of the most respectful things you can give the people working on your site. It is not the opposite of caring about them. It is what caring about them actually looks like in practice.

Your Contractor Not Showing Up Is Your Problem

Here is where I get direct with general contractors specifically, because this is where I see the most excuse making. If a trade partner is not showing up to pull plans, pre-construction meetings, on time arrivals, or huddles, that is not a mystery to shrug at. You picked the wrong contractor, and it is your job to fix it.

There is a moment worth picturing here. Somebody complains that their trade partner will not show up to huddles, as if that is simply a fact of nature they have no control over. The honest response is closer to being reminded of your own job title. You are the general contractor. If a trade partner is not participating in the systems your project runs on, that falls squarely inside your authority to address.

Do not tell me you cannot modify the contract. You can. Do not tell me you cannot change the trade partner you are working with. You can do that too. Getting the right people on the bus, and structuring the contract so it actually works for everyone involved, is not one job among many for a general contractor. It is the job.

Watch for these signs a GC is avoiding a decision that is genuinely within their authority to make:

Blaming a trade partner’s absence from huddles or planning sessions as unfixable rather than addressing it directly
Treating the existing contract as untouchable rather than something that can be modified when it is not working
Continuing to work with a trade partner who consistently will not participate in the collaboratively built system, without ever considering a change

The Distinction That Actually Matters

Here is the principle underneath all of this, and it is the one worth remembering above everything else. I worry whether a trade is following the system. I do not worry whether they are making mistakes or failing.

Leaders who never actually control their site or hold trades to a real system end up with only one tool left when something goes wrong: blaming and punishing people for failing or for honest mistakes. That is what happens when the system itself was never enforced in the first place. There is nothing else left to point to except the person, so the person absorbs consequences that should have belonged to a missing system.

I run this differently. As long as a trade is genuinely following the collectively decided, collaborative system, everything else gets fixed together. If they are failing at a piece of the work, I will help. If they made a mistake, I will help fix it. The one thing that will not be tolerated is refusing to follow the system the whole team agreed to build together. That is the actual line, and it is a very different line than punishing effort, mistakes, or honest struggle.

Why This Distinction Protects Psychological Safety

This connects directly to something worth holding onto from a different angle. A team cannot take real interpersonal risks, admit mistakes, or ask for help if doing so gets punished the same way as refusing to follow the system does. Collapsing those two categories into one destroys the very trust that lets people surface problems early instead of hiding them until they become expensive.

Separating them clearly does the opposite. Trades know they can come forward with a mistake or a struggle and get real support, because that is not the thing being enforced with zero tolerance. What is being enforced with zero tolerance is refusal to participate in the shared system everyone helped build. That distinction is exactly what lets a jobsite be both genuinely disciplined and genuinely safe for the people working on it at the same time.

What Holding This Line Actually Looks Like

None of this works as a slogan. It requires a general contractor to actually know the difference in the moment, and to respond accordingly instead of defaulting to blanket punishment or blanket permissiveness.

When a trade is not participating in huddles, pull plans, or the agreed system, that gets addressed directly, and if it continues, that becomes a contract and staffing decision, not an ongoing complaint. When a trade is participating fully and still runs into a mistake, a failure, or a genuine struggle, that gets met with real help, not punishment. Holding both of these at once, firm on participation and supportive on outcomes, is what actually produces a site that is disciplined, safe, and genuinely respected by the people working there.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams build exactly this distinction into how they lead, holding trades firmly to the system while genuinely supporting them through the mistakes and struggles that come with real work. That combination is what actually earns long term trust from trade partners, not fear of punishment for every misstep.

So here is the challenge. Look at your own project and ask honestly whether you are enforcing participation in the system, or whether you are quietly punishing trades for failures and mistakes instead. If it is the second one, that is exactly where to recalibrate, starting with your very next conversation with a struggling trade partner.

Jason Schroeder said it plainly: “I worry if a trade’s following the system, not if they’re making mistakes or failing.” Hold that line clearly, and you get a site that is both disciplined and genuinely safe for the people on it.

On we go.

FAQ

What should a GC actually do if a trade partner will not participate in huddles or planning sessions?
Address it directly and specifically, rather than treating it as an unavoidable trait of that trade. If direct conversation does not resolve it, recognize that modifying the contract or changing which trade partner is being used is genuinely within a general contractor’s authority. Continuing to tolerate non-participation while complaining about it is a choice, not an unavoidable circumstance.

Why is punishing mistakes the same way as punishing non-participation actually harmful?
Because it removes the distinction between a trade genuinely trying and failing, which deserves support, and a trade refusing to engage with the system at all, which deserves a direct response. Collapsing both into the same punishment discourages people from admitting mistakes or asking for help, since doing so carries the same risk as outright refusing to participate, which ultimately hides problems instead of surfacing them early.

Does being firm about system participation conflict with genuinely caring about the trades on a project?
No, and treating them as opposites is the actual mistake. A clean, safe, organized environment with real participation in shared systems is itself a form of respect for the people working there, since it protects their safety and their time. Genuine warmth toward people and genuine firmness about the system they operate within come from the same underlying respect, rather than existing in tension with each other.

If you want to learn more we have:

Discover Jason’s Expertise:

Why Capital One Saved Our Construction Business?

Posted on August 24, 2026August 24, 2026 by Team Jason Schroeder

Read 8 min

What My Banking Fight Taught Me About Running a Construction Business

Here’s the deal. Nobody teaches contractors that the bank you choose can be the difference between growing your business and watching it stall right when the work is finally there. I learned this the hard way, and I want to walk you through exactly what happened, because if you run a growing construction company, you are probably one large payroll cycle away from hitting the same wall I did.

Where This Actually Started

Years ago, when my wife Kate and I were first married, I was genuinely irresponsible with credit. That part is entirely on me. I let debt climb to around sixty thousand dollars across a handful of cards, starting from an original balance closer to fifteen thousand. One of those cards in particular had a habit of turning a ten dollar late fee into a spiral of interest rate increases and penalties, and I let it compound instead of getting ahead of it.

We eventually learned about debt stacking, the approach popularized by Dave Ramsey, paying off the largest balance first and rolling that payment into the next one. We got out of debt completely and stayed there. The problem was that being debt free is not the same as having good credit. My score sat around six hundred forty even after we had cleaned everything up, simply because we had not built any positive credit history to replace the debt we paid off.

The Bank That Actually Helped Build the Business

One bank was willing to work with us at that stage when nobody else would. A credit building card, used carefully and paid on time, took our credit score from six hundred forty up to eight hundred thirty, and it has hovered around eight hundred five ever since. That single relationship is what eventually let us qualify for enough credit to actually start the business.

Where It Got Genuinely Difficult

Here is where the real lesson for contractors starts. Like most people starting a company, our early banking relationship was with a large, familiar national bank. They were fine for basic credit cards. They were not willing to extend a business line of credit, even a modest fifty thousand dollars, despite our business running four million dollars in revenue with six hundred thousand dollars in accounts receivable and genuinely strong credit backing it up.

That was not a one time no. We were three or four years into the business by the time we applied, with real financials behind us, and the answer stayed the same. Nothing, nothing, nothing.

Solving It the Hard Way

We ended up working with a smaller regional bank, First Fidelity Bank in Phoenix, who was willing to extend a line of credit starting at twenty five thousand dollars, then fifty thousand, then seventy five thousand, based on a proper loan application and the appropriate lien filing. That bank was not strong on credit cards, so we ended up managing two separate banking relationships just to keep both sides of the business functioning, credit cards through the large national bank, and a line of credit through the smaller regional one.

Watch for these signs your current bank does not actually understand construction cash flow:

Your business is denied a line of credit despite strong revenue, real accounts receivable, and a solid credit history
Your bank will not use your accounts receivable as part of your creditworthiness at all
You are managing two or more separate banking relationships just to cover different financial needs

The Point Where the Business Was Actually at Risk

Eventually payroll reached one hundred eighty thousand dollars a month, with revenue climbing toward seven million and beyond. At that scale, a business genuinely needs a real line of credit to bridge the gap between paying crews and collecting on invoices. We were told no again. No line of credit, nothing, despite the numbers behind us being stronger than they had ever been.

That is a genuinely dangerous place for a growing construction company to sit. We were facing an actual choice between turning down new work or risking the business running out of cash at some point during a normal payroll cycle, purely because the banking relationship could not keep pace with legitimate, documented growth.

What Finally Changed Things

A business relationship representative reached out directly, took the time to actually understand the business, and made an offer that initially sounded too good to be true, enough that we spent weeks verifying it was legitimate before moving forward. The bank was willing to use our accounts receivable as real collateral, despite construction sitting in our business name, something other banks had specifically refused to do. The result was a six hundred thousand dollar line of credit at seven and a quarter percent interest, renewing at that same rate, with no penalty for using it only when actually needed.

That relationship did more than solve a cash flow problem. It came with a real customer service team standing behind the account and continued to help build credit over time, on top of the line of credit itself. At the exact moment the business was choosing between turning away work or risking insolvency, that banking relationship is what let us keep going.

Why This Matters Beyond One Company’s Story

None of this is really about praising or criticizing a specific bank for its own sake. It is about a pattern that affects contractors constantly and rarely gets discussed openly. Construction businesses carry a specific cash flow profile, real payroll due on a fixed schedule, real accounts receivable often collected weeks or months later, and plenty of banks are simply not built to underwrite that reality, regardless of how strong the underlying financials actually are.

A contractor turning down profitable work because a bank will not extend reasonable credit is not a business failure. It is a banking relationship failure, and it is worth treating that distinction seriously before assuming the problem sits with your company rather than your bank.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow, and a stable, well capitalized business behind those field teams is just as important to that stability as any schedule or system. A construction company that cannot make payroll because of a banking gap will not have the chance to apply any of the rest of what we teach.

So here is the challenge. If your business has ever been denied a reasonable line of credit despite strong revenue and real accounts receivable, do not assume that answer reflects your company’s actual creditworthiness. Shop that relationship the same way you would shop a major subcontract, and look specifically for a bank willing to underwrite construction cash flow rather than treat it as a red flag.

Jason Schroeder said it plainly, describing the banking relationship that turned things around: “Capital One is like Tony Robbins to me. Literally saved my life, built my business.” Find the banking partner that actually understands your business, and treat that relationship with the same seriousness you give any other system that keeps your company running.

On we go.

FAQ

Why would a bank refuse a line of credit to a business with strong revenue and receivables?
Some banks apply lending criteria that do not account well for construction specific cash flow patterns, particularly the gap between fixed payroll obligations and accounts receivable that may take weeks or months to collect. Even strong revenue and a solid credit score do not guarantee approval if a bank’s underwriting model does not use accounts receivable as collateral or views construction as higher risk regardless of the specific business’s financial strength.

What is debt stacking, and how does it actually work?
Debt stacking, sometimes called the debt snowball method and popularized by Dave Ramsey, involves paying minimum payments on all debts while directing any extra available money toward the single largest balance first. Once that balance is paid off, the payment that was going toward it rolls into the next largest balance, creating a snowball effect that accelerates as each debt gets eliminated.

Why did a low credit score persist even after becoming debt free?
Because a credit score reflects a history of credit use and repayment, not simply the absence of current debt. Paying off debt entirely without maintaining any active, well managed credit accounts can leave a score stagnant or low, since there is no ongoing positive repayment history being reported. A credit building product used carefully and paid on time is often necessary to actively rebuild that history afterward.

If you want to learn more we have:

Discover Jason’s Expertise:

Advanced Work Packaging (AWP)

Posted on August 24, 2026August 24, 2026 by Team Jason Schroeder

Read 12 min

Advanced Work Packaging Done Right: Give the Field the Right Work, Ready, at the Right Time

Advanced Work Packaging should not be complicated. At its best, it is simple. Give the field the right work, in the right sequence, with the right materials, at the right time, with the roadblocks removed before the crew arrives. That is the whole game.

Here is the deal. AWP has a reputation for being a megaproject bureaucracy, buried under acronyms, oversized packages, disconnected planners, and beautiful documentation that still does not help the foreman on Monday morning. That reputation is deserved on a lot of projects, not because the underlying idea is flawed, but because the system got built for the document instead of the crew. AWP was never meant to be paperwork. It was meant to create flow, and the difference between those two outcomes is entirely a matter of execution discipline.

The Pain of a Package That Isn’t Actually Ready

Here is what happens on a project running AWP badly. A crew shows up Monday morning with an Installation Work Package that looks complete on paper. The drawings are attached. The scope is defined. The package has gone through review. And then the crew discovers that half the material listed is not actually on site, or is on site but staged in the wrong location, or the permit required to start work has not been submitted, or a predecessor task that this package depends on is only ninety percent complete rather than fully done.

The package existed. It was documented. It went through the process. And it still failed the crew, because documentation and readiness are not the same thing. A package that lists what materials are needed is not the same as a package that confirms those materials are physically present, staged, and accessible. A package that names a predecessor task is not the same as a package that verifies the predecessor is genuinely complete. The gap between “documented” and “ready” is exactly where AWP breaks down on most projects, and it breaks down invisibly, because the paperwork looks fine right up until the crew is standing there with nothing to do.

The Failure Pattern

The failure pattern is treating package creation as the finish line instead of treating package readiness as the actual deliverable.

Most AWP implementations put enormous energy into the engineering and planning phases. Engineering Work Packages get built with drawings, models, specs, and quantities. Procurement Work Packages get built identifying what needs to be bought and delivered. Construction Work Packages get built dividing the field scope by area and discipline. All of that work is real, necessary, and often done well. Then the system hands off an Installation Work Package to the field and assumes the upstream planning guarantees downstream readiness.

It does not. A package can be planned correctly and still arrive at the crew incomplete, because planning and verification are different activities. Planning determines what should happen. Verification confirms that what should happen actually has happened, in the field, in physical reality, before the crew’s clock starts. Projects that skip the verification step and rely on the planning step alone are the projects where AWP becomes bureaucracy: extensive documentation that never quite translates into a crew starting work without interruption.

They Didn’t Fail the System

When a crew shows up to an incomplete package and loses the morning waiting on missing material or an unresolved predecessor, the instinct is to look at whoever assembled the package. Why didn’t they check? Why wasn’t this caught?

The honest answer is usually that nobody’s job was specifically to verify full kit readiness before the package was released to the field. Engineering did their part. Procurement did their part. Construction planning did their part. Each function completed its own piece and handed it forward, trusting that the next function would catch anything incomplete. Nobody owned the final checkpoint that confirms, physically and specifically, that every element of the package is actually present and ready before a crew is scheduled against it.

That is not a person failing to do their job. That is a system with no assigned owner for the step that matters most. Build that ownership into the process and the failure disappears. Leave it unassigned and the same gap will repeat on every package, regardless of how skilled or careful any individual planner happens to be.

The Path of Construction Drives Everything

Advanced Work Packaging starts with the Path of Construction, the real sequence the work wants to be built in, driven by the physical and logical constraints of the actual build rather than by an arbitrary planning convenience. This is the foundation everything else aligns to. Get the Path of Construction wrong, and every downstream package inherits that error, no matter how well each individual package is documented.

From the Path of Construction, the system aligns through five package types, each answering a specific question. The Engineering Work Package answers what are we building, providing the drawings, model, specifications, and quantities that define the scope. The Procurement Work Package answers what needs to be bought, delivered, and staged, translating design intent into material that physically exists on site. The Construction Work Package answers how the field scope divides by area and discipline, organizing the larger sequence into planning units that make sense for coordination. The Installation Work Package answers what one crew needs to install, safely and completely, sized specifically to a crew’s actual capacity for a defined period of work. And the Commissioning Work Package answers whether the finished system actually works, closing the loop from design intent to verified, functioning system.

Each package type builds on the one before it, and the alignment between them is what makes the whole system coherent. A CWP that does not trace cleanly back to the Path of Construction creates confusion downstream. An IWP that does not trace cleanly back to its CWP creates the same problem at a smaller scale. The alignment is not bureaucratic overhead. It is what keeps every level of the system pointed at the same actual sequence of work.

Full Kit Is the Whole Point

Here is the requirement that separates AWP done right from AWP done as paperwork. The package is only valuable if it is ready. Not mostly ready. Not “we will figure it out in the field” ready. Not “the material is somewhere onsite” ready. Ready means full kit.

Materials physically present and staged at the point of use, not merely ordered or somewhere in a laydown yard. Tools available and positioned for the specific installation task. Information current and accurate, matching field conditions rather than an earlier revision. Access confirmed, meaning the crew can physically get to the work location without obstruction. Permits secured and in hand before the crew arrives, not in process. Predecessors genuinely complete, verified rather than assumed. Roadblocks removed, meaning every known obstacle between the crew and productive work has been cleared in advance.

Every one of those six elements has to be true simultaneously for a package to be genuinely ready. Five out of six is not full kit. It is a package with a gap, and that gap is exactly where the crew loses time, exactly the kind of loss this factory has covered before in staging materials and workface planning. The difference with AWP is scale: a staging gap on a single task costs a crew minutes. A full kit failure on an Installation Work Package can cost a crew an entire morning, because the package was supposed to be the crew’s complete instruction set for the day, and an incomplete instruction set means the crew has nothing productive to fall back on.

Why Pairing AWP With Takt Planning Completes the System

AWP defines what work is packaged and confirms that it is ready. Takt planning defines the rhythm and location that work moves through. Paired together, the system gains something neither one produces alone: work that is not just packaged, but packaged to the beat of production, by location, in the order the field actually needs it.

Without Takt, a well-built AWP system can still produce packages that are individually ready but poorly sequenced against the actual rhythm of the project, arriving too early, too late, or out of step with the crews working adjacent zones. Takt planning gives AWP its cadence, ensuring that full kit packages arrive exactly when the production rhythm calls for them, no earlier and no later. That pairing is what turns AWP from a documentation exercise into a genuine production system, because the packages are not just complete, they are timed.

Signals Your AWP System Has Become Paperwork

Look for these patterns on your current project:

Installation Work Packages are released to the field with material listed as needed but not confirmed as staged and present
Crews regularly discover incomplete predecessors or missing permits after their package has already started
The path from Engineering Work Package through Installation Work Package involves multiple disconnected planners with no single owner verifying alignment
Packages are sized larger than what a single crew can complete in the planned duration, creating ambiguity about what “done” means
Nobody has a specific responsibility for confirming full kit readiness before a package is scheduled to the field

Each of these signals the same underlying gap: documentation exists, but verification does not, and that gap is exactly where AWP degrades into bureaucracy.

Building the Verification Step Into the System

The fix is not more documentation. It is assigning a specific ownership role for full kit verification, someone whose job is to walk through every element, materials, tools, information, access, permits, and predecessors, and confirm each one is physically true before the package is released. That verification should happen close enough to the scheduled work date that conditions have not changed since the check, but early enough that any gap found can still be closed before the crew is scheduled against the package.

This is the same discipline behind make-ready planning and workface planning that this factory has covered before, applied specifically at the packaging level. The principle does not change. The work should meet a clean, prepared, fully ready environment every time it begins, because a crew that starts with a complete package stays in flow, and a crew that starts with a gap spends the day recovering from a failure that upstream planning should have caught. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. Jason Schroeder and the LeanTakt team pair Advanced Work Packaging with Takt planning specifically because packaging without rhythm is paperwork, and rhythm without full kit readiness is a schedule that looks good on paper and fails in the field.

Build One Prepared Package Before You Build a Hundred

Here is your challenge. Take one upcoming Installation Work Package and walk it against all six full kit elements yourself, physically, before it goes to the field. Materials staged. Tools available. Information current. Access confirmed. Permits in hand. Predecessors truly complete. Fix whatever gap you find before the crew is scheduled against it.

Design, make, transport, build. One source of truth. One clear path. One prepared package at a time. That is what separates AWP as a practical field system from AWP as documentation nobody trusts. Start with one package done right, and let the discipline scale from there.

On we go.

FAQ

What is the single biggest reason AWP implementations fail on real projects?
The most common failure is treating package documentation as the deliverable instead of package readiness. A package can be planned, drawn, and specified correctly and still fail the crew if materials, permits, access, or predecessor completion were not physically verified before release. Documentation and readiness are different things, and most failed AWP systems only ever achieved the first one.

How is full kit different from a standard material list on a work package?
A material list identifies what is needed. Full kit confirms that materials are physically present, staged at the point of use, along with tools, current information, confirmed access, secured permits, and verified predecessor completion. Full kit is a verification standard, not a planning document, and it requires someone to physically check field conditions rather than trust that the plan was executed as written.

Who should be responsible for verifying full kit readiness before a package is released?
A specific, assigned owner, distinct from the engineering, procurement, and construction planning functions that build the package. This role’s job is to confirm, close to the scheduled work date, that every full kit element is genuinely true in the field. Without a single owner for this checkpoint, verification tends to fall through the gaps between functions that each assume someone else already checked.

If you want to learn more we have:

Discover Jason’s Expertise:

Paul Akers’ Lean Standup Desk

Posted on August 24, 2026August 24, 2026 by Team Jason Schroeder

Read 11 min

Paul Akers’ Lean Standup Desk: A Quiet Masterclass in Removing the Friction You Stopped Noticing

Most desks are built to keep you in one place. This one is built to move.

Here is the deal. Paul Akers built a mobile standup desk out of black pipe fittings, casters, and a few carefully chosen accessories, and the desk itself is not really the point. The point is what the desk demonstrates. Every design decision on it exists to remove a specific, small friction that most people have simply learned to live with. Wasted motion. Scattered tools. The wrong working height. A missing plug when you need one. None of those problems are dramatic. All of them quietly drain a day, and almost nobody bothers to fix them because each one feels too minor to justify the effort.

The Pain That Feels Too Small to Fix

Think about a typical workday at a standard fixed desk. You need a tool, and it is in a drawer three feet away, so you reach, shift your chair, retrieve it, and settle back in. You need to plug in a laptop, and the outlet is behind the desk, so you crouch, feel around, and eventually find it. You need to move your work to a different part of the room for a conversation or a different task, and the desk stays exactly where it is, because it was never built to go anywhere. Each of these moments costs seconds, not minutes. None of them feels worth solving.

That is exactly why they persist. A friction that costs thirty seconds does not trigger the kind of attention that a friction costing thirty minutes would. But the thirty second friction repeats dozens of times a day, every day, for as long as the workspace stays the same. Multiply a small cost by a high frequency and the total is significant, even though no single instance ever feels significant enough to address.

Most people do not calculate that math. They just adapt. They learn where the outlet is. They develop a habit of reaching for the drawer without thinking about it. The friction becomes invisible not because it stopped costing anything, but because the person absorbing it got good enough at absorbing it that it no longer registers as a problem.

The Failure Pattern

The failure pattern is treating small, personal frictions as unworthy of design attention, while reserving design thinking for larger, more visible systems.

This happens at every scale. A company will invest heavily in software, workflow systems, and process documentation, while an individual’s actual physical workspace, the desk, the tool layout, the power access, gets almost no design attention at all. The assumption is that big systems deserve engineering and small personal spaces do not, as though the friction in a two-foot radius around a person does not add up the same way friction in a larger system does.

Paul Akers’ desk rejects that assumption entirely. It applies the same rigor to a personal workstation that a Lean practitioner would apply to a production line. Every component exists because it removes a specific friction that was identified through actual observation of how the desk gets used, not through guessing at what might be convenient.

They Didn’t Fail the System

When someone’s workspace is inefficient, cluttered, or awkward, the instinct is to think they should be more organized or more deliberate about their setup. That instinct misplaces the responsibility.

Most people were never taught to look at their own workspace the way a Lean practitioner looks at a production line. Nobody walked them through the exercise of counting how many times they reach for something, how far they walk to plug something in, or how often they change the height or position of their work throughout the day. Without that observation, the workspace simply accumulates whatever configuration happened to exist when it was first set up, and it stays that way indefinitely because nobody applied the same design thinking to it that they would apply to any other system they were responsible for improving.

The friction in a personal workspace is not a personal failing. It is a design gap, exactly the same kind of design gap that shows up in an unmanaged connex box or an unlabeled storage bin. The difference is scale, not category.

What the Desk Actually Solves

Every component on this desk maps directly to a friction that most people never bother to name.

The black pipe and fitting frame solves the cost and rigidity problem of conventional furniture. Pipe and fitting construction is cheap, durable, and easy to modify. If the working height needs to change, or a new accessory needs to be added, the frame accommodates it without requiring a whole new piece of furniture. That adaptability matters because a fixed-purpose desk locks you into whatever configuration it was built for, and needs change faster than furniture typically does.

The angled laptop shelf solves the eye-level problem. A laptop sitting flat on a standard desk surface forces the user into a downward head position for hours at a time, a posture that compounds into fatigue and discomfort over a full day. Raising and angling the screen keeps it at eye level and supports active, engaged standup work rather than the slumped posture that a flat surface encourages.

The point-of-use tool tote solves the scattered tools problem. Instead of tools distributed across drawers, shelves, and surfaces where retrieval requires searching, everything lives in one portable caddy that stays visible and within reach. This is the same principle behind the Lean Connex Box applied at individual scale: everything needed has a home, and that home is close enough that retrieval does not interrupt the flow of work.

Onboard power solves the missing plug problem. A power strip and retractable cord reel mean the desk can plug in wherever the work happens, without requiring a search for the nearest outlet or a long extension cord snaking across the floor. This single addition removes one of the most common small frictions in any workspace: the moment of realizing your equipment cannot function where you currently are because power is not available there.

Mobile casters solve the fixed location problem. A desk on wheels goes to wherever the work needs to happen, rather than requiring the work to come to the desk. That flexibility means the workstation adapts to the task instead of forcing the task to adapt to the workstation’s location.

And the lean footprint solves the wasted space problem. A compact size supports focused work without occupying more floor space than the task requires, keeping the surrounding area open and minimizing unnecessary movement around the workstation itself.

The Mindset Behind the Desk

The real lesson is not the desk. It is the discipline of looking at a small, personal space with the same seriousness that Lean thinking applies to a factory floor or a jobsite.

Lean is often associated with large, visible systems: production lines, material flow, project schedules. But the discipline underneath Lean is not about scale. It is about seeing waste wherever it exists and refusing to accept it just because it is small or personal. Wasted motion is wasted motion whether it happens on an assembly line or in the two feet of space around your own workstation. Scattered tools cost time whether they are scattered across a jobsite connex box or across your own desk drawers. The principle transfers completely. Only the scale changes.

This connects directly to everything this factory has covered about staging materials, organizing connex boxes, and eliminating friction on jobsites. All of those practices are about applying design attention to spaces that were previously left to accumulate friction unnoticed. Paul Akers’ desk simply applies the identical discipline at the smallest possible scale: one person, one workstation, one day at a time.

Signals Your Own Workspace Has Unaddressed Friction

Look honestly at your own daily setup and watch for these patterns:

You regularly search for a tool or item that should have an obvious, fixed location
You have developed a habit of working around a missing plug, an awkward height, or an inconvenient layout rather than fixing it
Your workspace stays in one location even when the task would be better served somewhere else
You have accepted a posture or setup that causes discomfort because changing it feels like more effort than it is worth
You could not describe, right now, why your workspace is arranged the way it is, other than that it has always been that way

Each of these is a small, fixable friction that most people carry for years simply because nobody applied design thinking to their own immediate space.

Why the Small Scale Matters Most

There is a reason this lesson deserves attention even though it is about a desk rather than a jobsite. If someone cannot apply Lean thinking to their own immediate workspace, the two feet of space they occupy every single day, it is unlikely they will apply it consistently to a much larger and more complex system like a construction project.

The discipline of noticing friction, naming it specifically, and designing a fix is a skill that develops through practice, and the smallest, most personal scale is the easiest place to practice it. A superintendent who has trained themselves to notice and fix friction in their own workspace carries that same noticing habit onto the jobsite, into the connex box, into the material staging plan, into the daily rhythm of the whole project. The habit is the same habit. It just gets applied at a bigger scale once it has been built at a small one.

Lean is not a program you install on a project. It is a way of seeing waste everywhere, including the small radius immediately around you, and refusing to accept that waste just because it is familiar or small. That way of seeing is what Elevate Construction helps field teams build, one habit at a time, starting wherever the friction is easiest to notice and fix. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow, starting with the discipline of seeing waste at every scale, from the jobsite down to the desk.

Fix the Two Feet Around You

Here is your challenge. Look at your own workspace today, whatever it is, a desk, a truck cab, a laptop bag. Identify one small friction you have been quietly absorbing for months. A tool that is never where you need it. A cord you are always hunting for. A height that is never quite right. Fix that one thing this week.

Taiichi Ohno taught that waste hides in the places people have stopped looking, because familiarity makes it invisible. Your own workspace is one of those places. Go look at it the way Paul Akers looked at his desk, and fix what you find.

On we go.

FAQ

Why build a custom desk instead of buying a standard standup desk?
A custom build using pipe and fittings costs less than most commercial standup desks and can be modified freely as needs change, adding a new accessory, adjusting height, or reconfiguring the tool storage without needing to replace the entire piece of furniture. That adaptability is difficult to match with a fixed commercial product designed for a general use case rather than your specific daily friction points.

What is the value of casters on a workstation like this?
Casters let the workstation go to wherever the work needs to happen rather than requiring the work to come to a fixed location. This is the same logic behind portable material staging and mobile connex units: bringing the resource to the point of use eliminates the friction of relocating yourself or your materials to match a fixed setup.

How does this connect to Lean principles used on construction jobsites?
The desk applies the identical discipline used in the Lean Connex Box and material staging practices: give everything a fixed, visible location, eliminate wasted motion, and design the physical environment around actual use patterns rather than accepting whatever arrangement happened to exist by default. The scale is different. The underlying principle of eliminating friction through deliberate design is exactly the same.

Is a standup desk actually better than a seated desk for daily work?
The ergonomic case for alternating between sitting and standing throughout the day is well established for reducing the health costs of prolonged sitting. The desk in this design supports standup work at eye level specifically, which is one piece of the overall friction-elimination approach rather than the entire point. The larger lesson applies regardless of whether someone chooses a standup or seated configuration for their own workspace.

If you want to learn more we have:

Discover Jason’s Expertise:

Do Pull Planning Sessions Actually Work?

Posted on August 24, 2026August 24, 2026 by Team Jason Schroeder

Read 8 min

Do Pull Planning Sessions Actually Work?

Here’s the deal. Pull planning sessions absolutely work, one hundred percent, but only if you do them the right way. Most of the industry does not, and that gap is exactly why so many people conclude pull planning is just a feel good exercise with stickies on a wall instead of one of the most important tools in all of construction.

I want to be precise about the difference between the version that works and the version that fails, because the two look similar on the surface and produce completely different results underneath.

The Version the Industry Teaches, and Why It Is Wrong

The typical approach taught across our industry is one big batched pull plan, covering a huge area all at once, or a rolling three week or six week pull. I have never heard anything dumber than treating a three or six week window as an actual pull plan. That is a look ahead cadence, not a pull plan, and confusing the two is exactly where most implementations go wrong from the very first step.

Alongside that, a set of unwritten rules has calcified into industry gospel that actively makes pull planning worse. You have to use sticky notes. Each trade has to write their own sticky by hand. You cannot use digital software. You should batch large areas together to save time. Every one of those rules is wrong, and the last one, batching large areas, is genuinely the worst thing you can do, because it destroys the entire purpose of the exercise before it even starts.

What a Real Pull Plan Actually Is

A pull plan belongs to a phase, and that phase has its own unique zones. The plan gets built by starting with one zone and letting every other zone cascade from it on Takt time, not by trying to plan an entire large area all at once as one undifferentiated block.

Done this way, a pull plan does several specific things at once. You identify your zones correctly, based on actual work density rather than a rough guess. You gain real buffers, placed deliberately where the plan needs them. You surface and optimize the actual constraints in the system, meaning the design level problems like zone sizing, sequence, and Takt time that no amount of individual effort can fix on its own. In effect, you are not just scheduling a phase. You are designing an entire production system for it, one zone at a time, with every other zone building off the first.

Watch for these signs your pull planning process has slipped into the version that does not work:

Sessions labeled a pull plan that are actually just a three or six week look ahead
Large areas planned together as a single block instead of broken into zones with a defined cascade
Rules requiring sticky notes, trade-written notes by hand, or a ban on digital tools, treated as non negotiable tradition

Why Real Pull Planning Is Genuinely Hard

I want to be honest about something. Real pull planning is one of the hardest, most gut-wrenching things you can do in this work. I have never once walked into a pull plan expecting it to be easy, and anyone telling you otherwise has probably never run one the correct way.

Here is how seriously we take the preparation for it now. We ask for production data four weeks before the pull plan even happens, specifically so we are not caught off guard by a surprise in the middle of the session. That is not excessive caution. It reflects how much weight the pull plan actually carries for the rest of the project. Walking into it unprepared, without real production data in hand, means discovering constraints in the room instead of anticipating them, which makes an already difficult session harder than it needs to be.

Why This Single Session Matters So Much

Here is the claim that should genuinely change how seriously your organization treats this. In my experience, somewhere between ninety and ninety eight percent of all known roadblocks or constraints on a project trace their root cause back to an improperly done pull plan.

Think about what that actually means. Nearly every downstream problem you fight for the rest of the project, the trade stacking, the zone bottlenecks, the schedule slips that seem to come out of nowhere, very often has its origin in decisions made or skipped during pull planning. Get the zoning wrong, skip the constraint identification, batch a large area instead of cascading zone by zone, and you have effectively pre-loaded the rest of the project with problems that will surface later as roadblocks, disguised as unrelated field issues.

That is exactly why you will never improve past a constraint you failed to see and optimize during the pull plan. Constraints are system level problems, built into the design of the plan itself, and the pull plan is specifically where that design gets set. Miss it there, and no amount of hustle in the field will fully undo it later.

What Doing It Right Actually Looks Like

The correct method starts with the phase and its unique zones, not with the whole area treated as one undifferentiated block. You identify the right zoning based on actual work density. You build the sequence by starting with one zone and cascading the rest on Takt time. You gain buffers deliberately as part of that process, rather than hoping slack appears somewhere by accident. And you treat the entire exercise as designing a production system, with genuine attention to optimizing the constraints you find, rather than a scheduling formality to check off before construction starts.

None of the surface level rules the industry insists on, stickies, hand-written notes, no digital tools, actually matter to this outcome. What matters is the zoning logic, the cascade, the buffer placement, and the constraint optimization. Get those right and the format you use to capture it becomes a secondary detail.

Why This Deserves Real Investment

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams run pull planning the way it is actually meant to work, by zone, with real buffer calculation and constraint optimization, instead of the batched, sticky-note version that leaves most of the value on the table. Given how much of a project’s downstream roadblocks trace back to this single session, the investment in doing it correctly pays for itself many times over before construction even begins.

So here is the challenge. Look at your last pull plan and ask honestly whether it was actually built zone by zone with a real cascade, or whether it was a large area batched together and called a pull plan out of habit. If it was the latter, that gap is very likely where a meaningful share of your current roadblocks originated, whether anyone on the team has connected the two yet or not.

Jason Schroeder said it plainly: “Pull planning is one of the most important things in all of construction.” Do it the right way, and it will show up in exactly how few roadblocks you spend the rest of the project fighting.

On we go.

FAQ

What is the difference between a pull plan and a three or six week look ahead?
A pull plan is the process of designing a phase’s production system, identifying zones, sequencing them, and optimizing constraints before that phase of work begins. A three or six week look ahead is a rolling planning cadence used during execution to manage the near term work. Treating a rolling look ahead as a substitute for a real pull plan skips the zone identification and constraint optimization that actually prevents downstream roadblocks.

Why is batching a large area together considered the worst approach to pull planning?
Because batching removes the zone level detail that makes a pull plan useful in the first place. A properly run pull plan identifies unique zones within a phase and cascades the sequence from one zone outward on Takt time, which is exactly what surfaces trade bottlenecks, zone bottlenecks, and sizing issues. Planning a large area as one undifferentiated block hides those same problems instead of revealing them, which is precisely when they resurface later as unexplained roadblocks in the field.

Does a pull plan really have to use sticky notes and be free of digital tools?
No. Those rules are common industry tradition, not requirements that actually affect whether a pull plan works. What matters is whether the plan identifies zones correctly, cascades the sequence properly, calculates real buffers, and optimizes the constraints in the system. Digital tools can support that process just as effectively as physical stickies, provided the underlying zoning and sequencing work is done correctly.

If you want to learn more we have:

Discover Jason’s Expertise:

What’s The Biggest Lie We’ve Been Told About Project Management?

Posted on August 24, 2026August 24, 2026 by Team Jason Schroeder

Read 8 min

The Biggest Lie in Project Management

Here’s the deal. The biggest lie in project management is that the problem is the people. That workers, foremen, and trades are somehow a bunch of lazy, ignorant, difficult humans, and that we need layers of managers and paper pushers just to drag the project through in spite of them. That story is false, and believing it is exactly what keeps our industry stuck.

The truth is the opposite. The people who actually build our projects are sharp, skilled, and genuinely valuable human beings doing hard, complex work every day. They are, more often than not, tripping over themselves trying to help the general contractor and the project delivery team succeed. The real problem sitting underneath every failed schedule is our systems, and we have built a whole industry culture around refusing to admit that.

Watch What Happens When You Question the System

Here is a pattern I run into constantly. Every time I post something critical of CPM as a scheduling philosophy, someone responds with a version of the same defense. The system is fine, they say. People are just using it wrong.

That response is the lie in action, live and in real time. It takes a genuine system failure, a method that mathematically produces impossible durations and forces trade stacking, and redirects the blame onto the people trying to execute inside it. General contractors will defend their own systems and refuse to examine their own beliefs before they will consider that the actual method might be broken. It is far more comfortable to say the trades are not trying hard enough than to admit the plan they were handed was never achievable in the first place.

A Different Way to Think About People

There is a cultural contrast worth sitting with here. In the West, we have a deeply ingrained habit of throwing people away when something goes wrong. Find who is responsible, blame them, remove them, move on. It feels satisfying in the moment and it rarely fixes anything.

Compare that to a perspective shaped by Shinto and Buddhist tradition in Japan, where the belief is that every person carries inherent worth, and you do not simply exile or discard a human being because something went wrong around them. That is not a religious argument. It is a genuinely useful operating principle for how to run a jobsite. If every person on your project has real, inherent value, then a failure has to be explained by something other than that person being fundamentally bad or lazy, because that explanation runs directly against the premise. The explanation that remains is the system they were working inside.

We need that principle back in Western business culture generally, and in construction specifically. Stop blaming people. Start blaming the system. Start blaming the process. That shift is not softness. It is accuracy.

Why This Lie Is So Convenient

Here is the uncomfortable part. The lie that people are the problem survives because it protects something. If workers, foremen, and trades are the problem, then the Project Management Institute’s entire model of monitoring, controlling, and managing people makes sense. If people need to be pushed and timed, then Frederick Taylor’s original approach to scientific management, treating human beings as inputs to optimize rather than experts to support, makes sense too.

But we never actually needed either of those things in the form they took. We never needed an institute built primarily to monitor people rather than build better systems for them to work inside. We never needed a management theory built on timing and pushing human beings like machinery. What we actually needed, and still need now, is a focus on genuinely supporting and respecting the people doing the work, paired with real discipline on the process itself.

Watch for these signs your organization has quietly bought into the lie:

Schedule failures consistently explained as a trade or worker problem rather than examined as a system design issue
Defense of an existing method, like CPM, whenever someone questions whether it is actually achievable
Little appetite for examining whether the process itself, rather than the people executing it, needs to change

Being Hard on the Process, Not the People

Here is the actual formula that works, and it is simpler than either extreme our industry tends to swing toward. Be hard on the process. Be supportive and respectful of the people. Do both at the same time, consistently, and you get a quality product along with everything else you actually wanted from the project in the first place.

Being hard on the process means genuinely scrutinizing whether your schedule is achievable, whether your zones are sized correctly, whether your buffers exist, and whether your sequence respects how trades actually move through space. It means treating a schedule failure as a signal to investigate the system, not a signal to find someone to blame. Being supportive of people means trusting that the workers, foremen, and trades on your project are genuinely trying, genuinely skilled, and genuinely deserving of a system that lets them succeed instead of one that sets them up to fail and then gets angry when they do.

Why Fixing the System Requires Real Human Effort

Here is something worth understanding clearly. Recognizing that the system is the problem does not mean the fix happens automatically. It takes real, deliberate, intelligent human effort to actually rebuild a broken process, and that effort has to come from people willing to challenge their own beliefs about the systems they have relied on for years.

That is genuinely harder than blaming a trade for being slow. It requires a general contractor to sit with the uncomfortable possibility that the CPM schedule they trusted for a decade was mathematically flawed from the start. It requires a leadership team to admit that a management philosophy built on monitoring and control was never actually respecting the people executing the work. That kind of honest self examination is the actual work of fixing a broken system, and it is exactly the work that blaming people lets everyone avoid.

What This Means for Your Own Project

None of this is really about winning an argument over CPM or defending a particular management philosophy. It is about where you actually look when something on your project goes wrong.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build the habit of examining the system first, genuinely, before looking anywhere else. That single habit, practiced consistently, is what separates organizations that keep repeating the same failures from organizations that actually get better project after project.

So here is the challenge. The next time something on your project falls behind, resist the instinct to ask which trade or which person is responsible. Ask instead whether the schedule was ever achievable, whether the zones were sized correctly, and whether the system gave the people executing the work a real chance to succeed. That question will usually take you somewhere far more useful than blame ever does.

Jason Schroeder said it plainly: “The biggest lie in project management is that people are to blame.” Stop believing it, and start fixing what is actually broken.

On we go.

FAQ

If the system is usually the problem, does that mean individual performance issues never exist?
Individual performance issues do exist, but they are far less common than our industry’s habit of blame suggests, and they should be evaluated only after the system itself has genuinely been ruled out as the cause. A worker or trade repeatedly struggling inside a well designed, achievable system with proper training and support is a different situation than one struggling inside an impossible schedule with no real chance to succeed. Confusing the two leads to blaming good people for a bad system.

Why do general contractors resist admitting their own systems are the problem?
Because admitting a system is broken usually means admitting a method the organization has trusted and defended for years was flawed from the start, which is uncomfortable and requires real self examination. It is far easier, in the moment, to attribute a schedule failure to a trade or worker than to question the underlying philosophy the entire organization has built its planning around.

What does being hard on the process actually look like in daily practice?
It means genuinely scrutinizing whether a schedule is achievable, whether zones and sequences were properly calculated, and whether buffers exist to absorb real world variation, rather than assuming the plan is fine and any failure to hit it reflects poorly on the people executing it. It also means treating a recurring schedule problem as a signal to investigate the system’s design, not as evidence that people need to be pushed harder.

If you want to learn more we have:

Discover Jason’s Expertise:

The Definition of Done

Posted on August 24, 2026August 24, 2026 by Team Jason Schroeder

Read 9 min

Bake Me a Cake

Tell someone to bake a cake, and you will get a cake. It might not be the one you actually wanted. Tell them to bake a cake that a specific person really likes, made out of ice cream, in their favorite flavor, sturdy enough to hold lit candles through a full round of happy birthday, and ready by tomorrow noon, and something different happens entirely.

With that level of clarity, the outcome lands right nine times out of ten, often with almost no back-and-forth at all. The difference was never the skill of the person baking the cake. It was whether “done” was ever actually defined before the work began.

The Real Pain: Rework from an Unclear Finish Line

This same gap shows up constantly in delegation, especially as a team grows. A task gets written on a board or sent in a message, something like “create this crew matrix for this contractor.” Whoever picks it up has to guess at what that actually means, dig for context, make assumptions, and deliver something that may or may not match what was actually needed.

That guessing game is not a minor inconvenience. It produces real rework, real frustration, and real wasted hours, all because the finish line was never clearly described in the first place.

The Failure Pattern: Expecting People to Read Your Mind

The failure pattern is subtle because it feels like normal delegation. A task gets assigned with a title and maybe a sentence of context, and the person assigning it assumes their own mental picture of the finished product is obvious to everyone else. It rarely is.

When the delivered work does not match that unstated mental picture, frustration follows, often directed at the person who did the work, when the real gap was upstream the entire time: nobody ever described what “done” actually looked like.

A few signs tend to show up when a team is struggling with an unclear definition of done, and they are worth checking honestly:

Tasks come back requiring significant rework, not because the effort was poor, but because the wrong thing was built entirely.
People spend real time digging for context or guessing at intent before they can even start a task.
Frustration with a delivered task centers on “that’s not what I meant” rather than any actual quality issue with the work itself.

This Isn’t Laziness on Their Part, It’s Missing Information Upfront

Here is an honest admission worth making directly: this pattern is not usually the fault of the person doing the work. Expecting someone to read your mind, assuming they will simply arrive at the exact same mental picture you have without being told, is the actual root cause, and it took real self-reflection to see that clearly.

The fix was never to manage people more closely or to get frustrated when a guess landed wrong. It was to invest a few extra sentences upfront describing exactly what finished actually looks like, before the work ever begins.

The Process Improvement Board: One Sentence That Changed Everything

Here is what that shift looked like in practice. A recurring task, building a crew matrix schedule for a specific contractor, used to go out with just a title and a short description, and it regularly came back needing significant rework because nobody actually knew what the finished product was supposed to accomplish.

The fix was adding one clear sentence directly to the assignment: this task is done when you can visibly see all crews working for this company in separate colors, in a sustainable format that allows the team to allocate resources and predict crew availability for future projects. That single sentence, defining the finish line in concrete terms rather than a vague title, eliminated the rework almost entirely. Nothing else about the process changed, only the clarity of what “done” actually meant.

Why It Matters: Alignment Is the Ninth Waste

This matters because an unclear definition of done is not just an everyday annoyance, it is a recognized form of waste. Lean thinking names eight classic wastes, and a ninth sits right alongside them: misalignment, when people are not actually working from the same understanding of the goal.

An assignment without a clear finish line guarantees misalignment before the work even starts. The person assigning it has one picture in their head, the person doing it builds toward a different one, and the gap between those two pictures is pure waste, no matter how skilled or hardworking everyone involved actually is.

Teach the Framework: Conditions of Satisfaction

This concept has a name in Lean and Last Planner circles: conditions of satisfaction. Before any task, project, or handoff begins, the question worth asking is simple, what specific conditions need to be true for this to be considered genuinely done. Order a specific ice cream flavor and get handed a different one, or ask for a specific vehicle and get talked into a different package “because it’s what you really need,” and the frustration is immediate and obvious. The requester’s actual conditions of satisfaction were never met, regardless of what the other party assumed was good enough.

A useful discipline here borrows from the SMART framework: make the definition of done specific, measurable, actionable, relevant, and time-based, rather than vague language like “make it better” or “get this handled.” Pairing that clear finish line with an honest estimate of effort, the way Scrum teams size tasks before committing to them, ensures a team is not just clear on what done looks like, but realistic about how long it will actually take to get there.

A few practical elements turn any assignment into a real definition of done:

State plainly what the finished result needs to visibly show, do, or enable, not just the task’s general title or subject.
Include any hard constraints, a deadline, a required format, a specific audience that would make an otherwise “acceptable” result actually wrong.
Confirm understanding before work begins, rather than discovering a mismatch only after the task comes back finished.

Turning This into Daily Practice

This does not require lengthy documentation or a formal process overhaul. It requires one habit: before sending any assignment, whether it is a text message, a sticky note, or a verbal request, pause and ask what finished actually looks like, then say that out loud or write it down alongside the task itself.

Starting with the end in mind takes a few extra seconds upfront and consistently saves far more time on the back end, in avoided rework, avoided frustration, and avoided guessing.

Connecting It Back to Building People, Not Just Projects

None of this happens automatically, especially for leaders used to holding the full picture in their own head and assuming everyone else can see it too. Building the habit of stating a clear definition of done is a small shift that pays off every single time a task gets delegated.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow, including how assignments get handed off clearly enough to avoid costly rework.

The Challenge

So here is the challenge worth carrying into your next assignment, whether it is for a crew, a coworker, or your own to-do list: before handing it off, ask what the definition of done actually is, and make sure you have actually communicated it. As Jason put it plainly, “When you give an assignment, when you schedule an assignment, ask yourself, what is the definition of done? What would finish look like? And have I communicated that?” On we go.

FAQ

What does “definition of done” mean when delegating a task?

It means clearly describing what the finished result needs to look like, do, or enable before the work begins, rather than relying on a general task title alone. It is the same idea as conditions of satisfaction, a concept borrowed from Lean and Last Planner thinking.

Why does an unclear definition of done cause so much rework?

Without a clear finish line, the person doing the work has to guess at what “done” actually means, and their guess often does not match what the requester actually pictured. That mismatch is usually only discovered after the work is finished, requiring it to be redone.

How is this connected to the “ninth waste” in Lean thinking?

Lean identifies eight classic wastes, plus a ninth: misalignment between people working toward the same goal. An assignment without a clear definition of done guarantees misalignment from the start, since the requester and the person doing the work are working from two different mental pictures.

What makes a good definition of done, in practical terms?

It should be specific, measurable, and time-based rather than vague, describing exactly what the finished result needs to show or accomplish. Including any hard constraints, like a deadline or required format, prevents an otherwise reasonable result from still being the wrong one.

Does adding a definition of done to every task slow delegation down?

In practice, it usually speeds things up significantly. A few extra sentences upfront, describing what finished actually looks like, consistently saves far more time than the rework, confusion, and frustration caused by leaving that finish line undefined.

If you want to learn more we have:

Discover Jason’s Expertise:

Task Force

Posted on August 24, 2026August 24, 2026 by Team Jason Schroeder

Read 8 min

Not Punishment, Not Jail — Task Force

When a trade partner starts failing to meet real, realistic commitments, the instinct in construction is often to document the failures, build a case, and eventually replace them. There is a better way, and it has a name: task force.

A task force means gathering the trade partner’s project manager, their superintendent, the company’s ownership if the situation calls for it, and the general contractor’s own onsite team, and working the problem together every single day until it is genuinely fixed. It is not punishment, and it is not a prelude to termination. It is a direct, daily commitment to help a struggling partner recover.

The Real Pain: Watching a Trade Partner Fail in Silence

The real pain shows up in a familiar pattern. A trade partner starts falling behind, rework climbs, and manpower struggles to keep pace with a realistic schedule. Rather than stepping in to help, the common response is to quietly track the problem, build documentation, and prepare to justify removing them from the project.

Meanwhile, the project itself absorbs the damage. Schedule slips, other trades get disrupted, and the underlying issue never actually gets solved, it just gets replaced with a new trade partner who inherits the same broken conditions.

The Failure Pattern: Punish, Document, Replace

The failure pattern is baked into how many construction contracts are structured in the first place. Too often, contracts are written almost like two rival parties placed against each other, where one side benefits financially the worse the other side performs. That adversarial structure makes documenting failure feel like the natural response, rather than an unusual one.

The problem is that punishing or replacing a struggling trade partner rarely fixes the actual root cause. It just moves the damage downstream, to a new company, a new set of workers, and often the exact same underlying conditions that caused the original failure.

A few signs tend to show up when a project has slipped into a punish-and-replace mindset instead of a genuine help mindset, and they are worth checking honestly:

Documentation of a trade partner’s struggles is being built primarily to justify removing them, rather than to diagnose and fix the actual problem.
Meetings with a struggling trade partner happen occasionally or defensively, rather than daily and collaboratively.
The response to underperformance defaults to contract language and leverage rather than genuine partnership and support.

A Change of Heart

Here is a personal story worth telling honestly, because it is where this whole philosophy actually comes from. Early in one career, a role involved tracking a Division 17 electrical contractor’s rework and manpower on a project specifically to document their struggles and justify bringing in additional support, or removing them entirely. That documentation worked exactly as intended, and the contractor was eventually run off the job and out of business.

Later in life, that same person married the daughter of the man who had run that electrical company, joined the same church congregation, and ended up serving directly alongside him in community roles for years afterward. That experience became an unforgettable, humbling lesson in what respect actually means, and a permanent shift away from treating struggling trade partners as problems to be documented and removed, toward treating them as partners worth helping.

Why It Matters: One Failing Trade Partner Can Sink Everyone

This matters because a struggling trade partner rarely fails in isolation. Their problems ripple into other trades, into the schedule, and into the trust of the entire project team. Replacing them does not undo that ripple effect, it usually just resets the clock while the underlying conditions remain unaddressed.

There is a useful rule of thumb here: one major trade partner struggling on a project is a task force situation. Two or more major trade partners struggling at the same time is a much bigger warning sign, one that calls for escalating to company leadership immediately rather than handling it quietly at the project level.

Teach the Framework: How a Task Force Actually Works

A real task force gathers the right people daily: the trade partner’s project manager, their superintendent, company ownership when the situation is serious enough to warrant it, and the general contractor’s onsite team. Together, this group reviews the previous day’s data, solves problems in real time, and adjusts course together, every single day, until the trajectory of the work is genuinely and sustainably back on track.

This works for a few clear reasons. It puts the best minds in the room instead of leaving the problem to whoever happens to be available. It puts people who can actually make decisions at the literal place of work, rather than routing everything through slow, distant approval chains. And it creates real accountability without punishment, the message becomes “you are accountable for this, and we are going to hold this together,” not “you are in trouble.”

A few practical markers separate a genuine task force from a punitive one in disguise, and they are worth checking directly:

The trade partner’s own leadership, not just field staff, is actively present and engaged in the daily problem-solving.
Conversations focus on fixing the process and the conditions causing the failure, not attacking the people involved.
The task force has a clear, mutually understood end point: when the fix is sustainable, the daily meetings stop and normal operations resume.

Turning This Into Daily Practice

Persistence matters more than most leaders expect. When a struggling trade partner knows their situation is front and center every single day, with real stakes and real attention on it, that consistent visibility motivates a faster, more genuine fix than an occasional warning ever could. The old idea that the squeaky wheel gets the grease applies here, just aimed at helping rather than pressuring for its own sake.

This approach matters even more when the struggling trade partner is a small business, a women-owned enterprise, or a minority-owned business that may simply have less cash flow cushion than a larger competitor, not less competence or effort. Leaning toward help and collaboration in ambiguous contract situations, rather than maximum leverage, reflects a genuine obligation that comes with being the larger, more established party in the relationship.

Connecting It Back to Building People, Not Just Projects

None of this happens without leaders willing to show up daily for a struggling partner instead of quietly building a case against them. That kind of consistent, hands-on support is exactly the leadership skill that turns a failing trade relationship into a sustainable one.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow, including how to genuinely support a trade partner through a difficult stretch rather than simply documenting their way out the door.

The Challenge

So here is the challenge worth carrying onto your next project: the next time a trade partner starts to struggle, resist the instinct to quietly document and prepare to replace them. Gather the right people, show up daily, and work the problem together until it is genuinely fixed. As Jason put it plainly, “It is our obligation to help them and to elevate them.” On we go.

FAQ

What is a construction task force, and how is it different from disciplinary action?

A task force means gathering a struggling trade partner’s leadership and the general contractor’s onsite team to meet daily and solve problems together until performance is sustainably fixed. It is not punishment or a step toward termination, it is a direct, collaborative commitment to help the trade partner succeed.

When should a project use a task force instead of simply replacing a struggling trade partner?

Whenever one major trade partner is failing to meet realistic, well-planned commitments, a task force is the right first response rather than documentation aimed at removal. If two or more major trade partners are struggling at the same time, that is a bigger warning sign requiring immediate escalation to company leadership.

Why does daily attention help a struggling trade partner improve faster?

Consistent, visible attention keeps the problem front and center with real stakes attached, which tends to motivate a genuine fix faster than occasional warnings or threats. It also ensures the right decision-makers are actually in the room every day instead of routing issues through slow approval chains.

Does helping a struggling trade partner mean ignoring contract obligations?

No. A trade partner is still accountable for delivering on their commitments and their contract. The difference is in the approach, leaning toward collaboration and support to help them meet those obligations, rather than defaulting to punitive leverage or documentation aimed at replacing them.

Why does this approach matter especially for small or minority-owned businesses?

Smaller businesses, including women-owned and minority-owned enterprises, often have less cash flow cushion than larger competitors, not less skill or effort. Leaning toward genuine help and partnership in these situations reflects an obligation that comes with being the larger, more established party in the relationship.

If you want to learn more we have:

Discover Jason’s Expertise:

General Offerings

Company Offerings

Systems

Month: August 2026

Don’t Just Do Something, Stand There

Trades Following the System

Why Capital One Saved Our Construction Business?

Advanced Work Packaging (AWP)

Paul Akers’ Lean Standup Desk

Do Pull Planning Sessions Actually Work?

What’s The Biggest Lie We’ve Been Told About Project Management?

The Definition of Done

Task Force

Subscribe Now

Our Office

Get In Touch

Company

Follow Us

General Offerings

Company Offerings

Systems

SUBSCRIBE NOW !

Subscribe to our newsletters and stay updated!