Non-Direct Authority Positions

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

Read 18 min

Why Non-Direct Authority Positions Should Never Run Operations

Here’s the deal. This one might sound petty at first, but it has cost real companies real money, and I have watched it play out over and over across our industry. Support positions, people development, legal, training, scheduling, BIM, technology, exist to serve operations. They do not get to tell operations what to do, no matter how good their intentions are, because they are not accountable for the outcome.

That distinction sounds simple. In practice, it gets violated constantly, and every single time it happens, the results are predictable and bad.

A Story Worth Telling, Because It Ended Well

We have a philosophy at Elevate that we want to hire people for life, meaning we want a genuine cultural fit, someone who drives results and lives our core values, and we want to be part of that person’s life for as long as they want to stay. That is different from hiring anyone at all just to fill a seat. If someone is not culturally aligned or not performing, we cannot keep employing people that way and still stay in business.

One of the tools we use is what we call the Keeper Test. Ask a direct supervisor a simple question. If this person told you today they had a better offer somewhere else, would you fight to keep them? The honest answer tells you a lot.

There was a person on our operations team who was genuinely a good person, but who consistently struggled to get work done, tended to place responsibility on the team rather than take it on themselves, and did not improve despite real coaching. We coached, trained, and invested in this person seriously. Eventually, the direct line supervisor gave an honest answer: I care about this person, I hope they land somewhere great, but I would not fight for them, because nothing we do from a coaching standpoint moves the needle.

Then someone from our people development team, who was not in the direct line of operational authority, said they would fight for this person. I pushed back hard in that moment, and it got a little tense. I am glad it did, because pushback means people are engaged and alive in the conversation, not just going along.

The Fix That Made the Principle Click

Here is how we resolved it, and I think this is the part worth remembering. I said, if you genuinely want to fight for this person, then they move to your team. You own the relationship, you own the coaching, and you own the outcome. You do not get to tell operations to keep someone operations has already determined is not working out, while you carry none of the accountability for that decision.

The room paused, and then people development got it immediately. You cannot fight for somebody and then hand them back to the people who already said the fit was not working, effectively passing a defect down the line to someone else to deal with. I genuinely respect that team for pushing back on me in the first place and then hearing the principle once it was laid out clearly. That is exactly the kind of healthy conflict a real team needs to have.

Why This Keeps Happening Everywhere

I have watched this exact pattern repeat across construction companies more times than I can count. A support department, legal, technology, training, scheduling, tells operations what to do, and it never works out well. Not occasionally. Every single time.

The reason traces back to incentives, not intentions. A support position that is not accountable for the operational result is incentivized to feel important, to feel needed, to look good enough to keep their own job secure. In theory they might also be incentivized to create flow, benefit the people actually doing the work, and genuinely listen. In practice, that second set of incentives rarely wins out, because it is not what determines whether their own position feels secure. Because they are not accountable, it is not their decision, and pretending otherwise sets up a structure that runs on the wrong incentives from the start.

Watch for these signs a non-authority position has started making decisions that belong to operations:

A department outside the direct chain of command issuing direction rather than support or recommendations
Decisions being made by someone with no experience actually doing the operational work being directed
Operational leaders quietly following direction they privately disagree with because it came from a department rather than their own chain

What a Real Line of Authority Looks Like

I grew up at Hensel Phelps, a company that was genuinely strict about this. The path ran field engineer, project engineer, assistant superintendent, then either project manager or superintendent, and up through the chain of command from there. Every single person in that chain, all the way to the executive vice president, the president, and the CEO, was accountable for the results their decisions produced. Departments like technology, pre-construction, and training existed in a support role, subservient to operations, precisely because they were not in that direct, accountable chain.

That structure is not about ego or hierarchy for its own sake. It is about matching decision making authority to actual accountability. When operations is staffed with people who know the work, are being properly trained, and are held accountable for results, and you place a trainer, a scheduler, a BIM specialist, or any support role in charge of directing a superintendent or field director, you are asking for trouble. The decisions that follow will not be grounded in field experience, will not carry real accountability, and will not consistently reflect what operations actually needs. They will instead be shaped by a very human, very understandable drive to feel significant and in control, even when that is not the intention going in.

Respecting People Means Respecting the System They Work Inside

This connects to something I believe deeply about human nature. The human brain did not evolve to handle influence and incentive structures cleanly. Put people into a system where they can direct outcomes they are not accountable for, and something in most of us will eventually reach for control or significance, even with the best of intentions. That is not a character flaw specific to any one department or person. It is a predictable feature of how incentive structures shape behavior, and the fix is structural, not moral.

Respect for people, something the Japanese Lean tradition gets right, means designing systems that do not put good people in a position where their incentives quietly work against the outcome everyone actually wants. A support role given authority it is not accountable for is not a favor to that person. It is a setup that eventually damages both the support function’s credibility and operations’ ability to actually run the project.

Building This Boundary Into Your Own Organization

None of this is about diminishing support functions. Legal, training, scheduling, and people development are genuinely necessary and valuable. The principle is narrower than it sounds: authority to direct operational decisions has to sit with people who are accountable for the operational results, full stop.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your organization build a clean line of authority where support functions genuinely support operations instead of quietly directing it. Getting this boundary right protects both the credibility of your support teams and the ability of your field leaders to actually run their projects.

So here is the challenge. Look at your own organization and ask where a support function might currently be directing operational decisions rather than advising on them. If you find one, do not just correct the direction. Ask the support team the same question I asked people development. If you believe this strongly enough to override operations, are you willing to own the outcome yourself? That question tends to clarify things fast.

Jason Schroeder said it plainly: “Because they’re not accountable, it’s not their decision.” Keep authority and accountability matched, and this problem mostly takes care of itself.

On we go.

FAQ

How do you tell the difference between a support function advising operations and one that is actually directing it?
Advising looks like a recommendation operations is free to accept, modify, or decline based on field judgment. Directing looks like operations being told what to do with the expectation of compliance, regardless of field experience or accountability for the outcome. The clearest test is whether the operational leader retains the final call and the accountability that comes with it, or whether that authority has quietly shifted to the support function.

What should happen if a support team genuinely believes operations is making the wrong call?
They should raise the concern directly and make their case, the same way anyone should be able to voice disagreement inside a healthy team. What should not happen is the support function overriding the operational decision without taking on the accountability for the outcome. If they feel strongly enough to want control over the decision, the honest resolution is for them to take ownership of that piece of work directly, the way people development took ownership of the employee in this story.

Why does this pattern show up so consistently across different companies and industries?
Because the underlying incentive structure is the same everywhere it happens. A position that is not accountable for operational results but is given influence over them tends to use that influence to feel important or secure in their own role, even without any bad intent. That incentive dynamic is a predictable feature of how humans respond to authority without accountability, not a flaw unique to any particular company or department.

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.

Advanced Work Packaging Done Right

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

Read 17 min

How Advanced Work Packaging Can Actually Hurt Your Project

Here’s the deal. Advanced work packaging is supposed to make large industrial and data center projects easier to plan and execute. Done wrong, it does the opposite. It locks a general contractor and every trade partner into a rigid structure with no room to optimize, and I have watched it cost real projects four to five months of schedule that never had to be lost.

If you work in oil and gas, industrial construction, or data centers and you have heard the term advanced work packaging without fully understanding how it can go sideways, this is exactly the warning you need before your next project locks in its work breakdown structure.

The Four Packages, In the Right Order

Advanced work packaging breaks a project into four connected layers, and understanding how they relate to each other is the whole key to sizing them correctly.

At the far end sits the engineering work package, which handles the design and engineering for a piece of scope. Before that scope can be built, it needs a procurement work package, which handles everything related to sourcing and delivering the materials and equipment involved. Once design and procurement are aligned, you get a construction work package, the actual chunk of physical work being planned and executed. And the construction work package gets sliced further into installation work packages, smaller pieces broken out by discipline, which in Takt planning terms is simply the task or Takt wagon moving through a zone.

The order matters because a mistake made at the construction work package level ripples through the installation work packages beneath it, and there is no fixing that downstream once the structure has been locked in.

Sizing a Construction Work Package the Right Way

Here is the sizing principle that most advanced work packaging literature never states clearly enough. A construction work package should be sized the same way you would size a phase in Takt planning, around a train of trades moving through its own unique set of zones.

Superstructure is a good example. The superstructure phase has its own zones and its own train of trades flowing through them, separate from anything else happening on the project. The interiors of a building are the same. All of the interior work has its own train tracks, its own zones, and its own sequence of trades. Each of those is a distinct phase, and each phase is what should define a construction work package. Once you have that phase correctly bounded, breaking it into installation work packages by discipline, fire sprinkler, priority walls, overhead mechanical, and so on, fits naturally into the progression of work through those zones.

That is the correct method. Size the construction work package around a real phase with real zones, not around whatever chunk of the building happens to be convenient to draw a boundary around.

Where Real Projects Go Wrong

Here is what actually happens on a lot of data center and industrial projects. Instead of sizing construction work packages around phases and zones, the entire building gets batched into one massive chunk. A small admin office area might get treated as its own package, while an enormous open area gets lumped into a single, undifferentiated construction work package with no internal zoning at all.

Once that structure gets built into a CPM schedule, and pairing advanced work packaging with CPM compounds the problem badly, the result is a completely unleveled plan. On one project like this, the time lost to improper breakdown ran into literal months, not weeks, purely because the construction work packages were sized wrong from the start.

Watch for these signs your advanced work packaging structure has already gone wrong:

A construction work package covering an entire building or an entire large open area with no internal zoning
Installation work packages that do not correspond to any recognizable train of trades moving through defined zones
No mechanism to adjust the work breakdown structure once it has been set in the scheduling software

Any one of these is a sign the schedule is about to waste months it did not need to lose.

The Real Problem: No Room to Optimize

Here is what makes this worse than a normal CPM problem. Once a general contractor builds the work breakdown structure in scheduling software like P6, both the GC and every trade partner are locked into following it exactly as drawn. There is no room left to optimize.

That is a genuinely dangerous trap, because with a standard CPM schedule alone, teams are at least often willing to run a pull plan and adjust zone sizes afterward to fix an unleveled sequence. Advanced work packaging, done wrong, removes even that option. The structure has already been decided, and everyone downstream has to live inside it whether it makes sense or not. In other words, advanced work packaging is not neutral. Done poorly, it does not just fail to help. It actively makes an unleveled schedule harder to fix than it would have been without it.

What Fixing This Actually Looks Like

The fix is not complicated in concept, even though it takes real discipline to execute. Optimize each phase using a proper Takt calculator, get the zoning genuinely right, and only then build the construction work packages from that leveled foundation. Done this way, a project can realistically gain back four to five months compared to the unleveled version, without changing a single thing about the actual scope of work.

That gain does not come from working faster or cutting corners. It comes entirely from sizing the work correctly the first time, so trades flow through zones evenly instead of colliding in an oversized package or sitting idle waiting for an undersized one. Queueing principles like Little’s Law and Kingman’s formula explain why this matters mathematically: uneven batch sizes and unleveled work in process reliably produce longer wait times and worse throughput, no matter how skilled the people executing the work happen to be. Ignore that math and you are fighting queueing theory itself, not just a scheduling preference.

Why This Deserves Attention Before You Lock In a Structure

None of this is really about scheduling software or a specific book on advanced work packaging. It is about protecting real project time, real trade partner relationships, and real budget from a structural mistake that becomes almost impossible to reverse once it is set.

A general contractor and trade partner both lose when a construction work package traps them inside an unleveled batch with no room to pull plan their way out of it. The fix has to happen before the work breakdown structure gets built into the scheduling software, because after that point, everyone is simply living inside whatever was decided, whether it reflects real zones and real flow or not.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams size construction work packages around real phases and real zones before they ever get locked into a rigid structure. Getting this right before the schedule freezes is worth months of recovered time later.

So here is the challenge. If you have a project heading toward advanced work packaging, or one already partway through it, check whether your construction work packages were sized around actual zones and a real train of trades, or around a convenient chunk of the building. If it is the latter, raise that now, while there is still room to correct it, rather than after the structure has been built into the schedule and everyone is locked in.

Jason Schroeder said it plainly: “Advanced work packaging isn’t helping. It is actually making this worse.” Get the zoning right before you lock the structure, and the same tool becomes an asset instead of a trap.

On we go.

FAQ

What is the difference between a construction work package and an installation work package?
A construction work package is the larger chunk of physical work tied to a specific phase, such as superstructure or interiors, defined by its own train of trades moving through its own zones. An installation work package is a smaller slice of that construction work package broken out by discipline, like fire sprinkler or overhead mechanical, which corresponds to a task or Takt wagon moving through those same zones.

Why is pairing advanced work packaging with a traditional CPM schedule especially risky?
Because a CPM schedule alone at least leaves room for a team to run a pull plan and adjust zone sizes after the fact if the sequence turns out unleveled. Advanced work packaging locks the general contractor and trade partners into the work breakdown structure once it is built into the scheduling software, removing that flexibility entirely. If the packages were sized wrong from the start, there is no later opportunity to fix it through a pull plan.

How much schedule time can be lost from improperly sized construction work packages?
On real industrial and data center projects, improperly batched construction work packages have caused delays measured in literal months rather than weeks. Correctly sizing those packages around real phases and Takt calculated zones has, in comparable cases, recovered four to five months of schedule without changing the underlying scope of work at all.

If you want to learn more we have:

Discover Jason’s Expertise:

Professional A-Holes in Construction

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

Read 15 min

The Professional Toxicity Problem: Why Polish Is Not the Same as Respect

Here’s the deal. Some of the most damaging leaders in construction never raise their voice, never miss a deadline on paperwork, and never say a word out of place in a meeting. They are polished, buttoned up, and dressed to the nine. And they can still be the most toxic person on the project.

We have trained ourselves to equate professionalism with safety, as if a calm voice and a clean suit automatically mean the person is treating people well. It does not work that way, and field leaders need to know the difference.

The Leader Who Never Curses and Still Scares Everyone

Picture the corporate figure everybody in construction has met at least once. Immaculately dressed, perfectly composed, never a harsh word out of place. This person can walk into a room, say almost nothing, and leave everyone in it a little smaller than they were before. The intimidation is not loud. It is a stare, a tone, a way of looking down at the people who are actually trying to progress, learn, and grow in the company.

That is the pattern worth naming. Not the individual, the pattern. Because this style of leadership shows up on plenty of jobsites, and it is easy to miss if you are only watching for the obvious signs of a bad boss, yelling, cursing, visible anger. The quiet version does just as much damage, sometimes more, because it hides behind a surface that looks like exactly what our industry has been trained to reward.

Classical Business Management in a Nice Suit

Underneath the polish, this leadership style runs on a very specific order of priorities. Money first. Control of people second. Protection of the internal leadership team third. That is classical business management, and it does not need a single cuss word to be genuinely harmful, because the harm is not in the language. It is in the priorities.

A leader operating on that order treats people as instruments for hitting numbers rather than as the actual value creators on the project. Every interaction becomes a subtle test of who holds power. Contracts get used as leverage instead of agreements. Disagreement gets treated as a threat to manage rather than information worth hearing. None of that requires a raised voice. Composure is not the same thing as care, and a person can be completely professional in manner while being completely toxic in effect.

Watch for these signs of professional toxicity, because they rarely announce themselves the way an angry outburst does:

People leaving a conversation with that leader feeling smaller, not clearer
Disagreement quietly disappearing from meetings instead of being worked through
Contracts, policy, or process used as a weapon rather than a shared reference point

Any one of these, present consistently, is worth taking seriously, no matter how composed the person delivering it appears.

Why We Keep Getting Fooled By This

Part of the reason this pattern survives is that we have trained ourselves to look for the wrong signal. We watch for cursing, sloppiness, and visible anger as the warning signs of a bad leader, and we treat their absence as evidence that everything is fine. That is backwards. A calm, well dressed, perfectly professional exterior tells you almost nothing about whether that person actually respects the people in front of them.

Meanwhile, plenty of genuinely good leaders in the field are direct, a little rough around the edges, occasionally colorful in their language, and completely devoted to the people they lead. If we judge leadership on polish alone, we will consistently overrate the wrong people and underrate the right ones. Psychological safety, honest disagreement, and real respect for craft are the actual measures. Everything else is decoration.

What Real Leadership Looks Like Instead

The alternative is not simply the opposite of polish, roughness for its own sake. It is a different order of priorities entirely. People first. Then the process that supports them. Then the business results, which follow naturally when the first two are genuinely in place.

A leader operating from that order treats disagreement as useful information rather than a threat. A leader like that can hold a firm standard, the same firm standard we have talked about elsewhere, on cleanliness, safety, and organization, without needing intimidation to enforce it, because the standard is being held with respect rather than as a display of power. The measure is not how composed someone looks in a meeting. It is whether the people who report to them feel safe enough to tell the truth, disagree honestly, and bring a problem forward the moment they see one.

Why This Matters More in Construction Than Almost Anywhere Else

Construction runs on total participation. We have talked before about how one person, one crew, or one step not participating can bring an entire system to zero. A leader who quietly makes people feel small, intimidated, or unsafe is actively working against that participation every single day, even while appearing completely professional in the process.

Craft workers deserve leaders who make it safer to speak up, not harder. Foremen deserve leaders who treat disagreement as useful rather than dangerous. When a project is being run by someone whose polish is covering for a genuinely toxic set of priorities, the cost shows up exactly where it always does. Problems get hidden instead of surfaced. People stop raising issues early. Rework climbs. Turnover climbs. And none of it gets traced back to the actual cause, because the person responsible never raised their voice once.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams build leadership that holds a real standard without relying on intimidation to do it. The goal is never permissiveness on one end or fear on the other. It is confident, respectful leadership that makes people safer to speak up, not smaller.

So here is the challenge for this week. Think about the leaders on your project, at every level, and set polish aside entirely. Ask instead whether people leave conversations with them feeling more capable or less. Ask whether disagreement actually gets heard or quietly disappears. That is the real test, and it has nothing to do with how sharp anyone’s suit is.

Jason Schroeder said it plainly: “The first thing you’ll notice is that they’re completely put together. The second thing you’ll notice is that they’re completely toxic.” Do not let the first observation stop you from making the second one.

On we go.

FAQ

How is professional toxicity different from someone simply being reserved or formal?

Being reserved or formal is just a communication style, and plenty of reserved leaders are genuinely respectful and safe to work for. Professional toxicity is defined by the effect on the people around the leader, not the style itself. The test is whether people leave interactions feeling smaller, whether disagreement disappears instead of getting addressed, and whether policy or contracts get used as leverage rather than shared reference points.

Why does this pattern survive so easily in construction and other industries?
Because most organizations watch for the visible signs of bad leadership, like yelling, cursing, or visible anger, and treat their absence as proof that a leader is fine. That habit lets a calm, polished, intimidating leadership style go unchecked for years, since it never trips the alarm most people are actually watching for.

Can a leader hold a firm standard without becoming this kind of toxic figure?
Yes, and the difference lies entirely in the posture behind the standard. A leader can insist on cleanliness, safety, and quality with total consistency while genuinely respecting the people they are holding to that standard. The toxic version uses the standard as a tool for intimidation and control. The healthy version uses it as a shared commitment the whole team believes in together.

If you want to learn more we have:

Discover Jason’s Expertise:

Engineering Guide To Temporary Construction Fence Standards

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

Read 24 min

Engineering Guide to Temporary Construction Fence Standards: Why Your Fence Line Is a Leadership Signal

Temporary does not mean negligent.

Here is the deal. The construction fence is the most publicly visible element on any project and the one that gets the least leadership attention. It is the first thing the public sees. It is the first thing an inspector sees. It is the first thing a pedestrian walking past your project at seven in the morning with a stroller sees. And what they see tells them exactly what kind of project this is before they ever meet the superintendent, review the schedule, or hear a single word about the team’s commitment to quality.

A taut screen, level posts, clean sidewalk access, and proper bracing communicates that this project is run by people who care about the details that nobody is watching. A loose screen blowing into pedestrian space, bent post tops leaning over the sidewalk, and scattered base supports communicates that nobody is watching at all.

The Pain That Walks Past Your Site Every Day

Every active construction project in an urban or suburban setting has a public interface. That interface is the fence line, and the condition of that fence line is producing a continuous, uncontrolled message about the project to every person who passes it.

A pedestrian who has to step around a sandbag that has shifted into the sidewalk is receiving a message. A parent who sees damaged panels and loose screen fabric blowing toward the path their child walks to school is receiving a message. A city inspector who drives past on the way to another project and notices bent post tops and missing braces is receiving a message. None of those messages are being sent intentionally, but all of them are being received clearly.

The problem is not that project teams do not understand this. Most superintendents know their fence should look good. The problem is that fence maintenance lives in the category of tasks that are important but never urgent, which means they get deferred in favor of whatever is urgent today. The screen that started pulling loose on Tuesday is still loose on Friday. The panel that got damaged by a delivery truck two weeks ago has not been replaced. The bracing that should have been checked after last week’s windstorm was not checked because last week’s windstorm also created three other problems that demanded immediate attention.

The fence degrades slowly, and slow degradation is the kind of problem construction leadership is worst at catching because it never announces itself as a crisis. It just gets a little worse each week until someone external, an inspector, a neighbor complaint, a project owner doing a drive-by, sees it and names it. By then, the fence has been communicating the wrong message for weeks.

The Failure Pattern

The failure pattern is treating the fence as a one-time installation rather than a maintained system.

The fence goes up during mobilization. The crew that installs it does a good job. Posts are level, screen is taut and secured on the interior face, panels are new, bracing is proper, base supports are uniformly placed. For the first two weeks, the fence looks excellent. Then the project starts. Deliveries come and go. Equipment moves along the perimeter. Weather hits. A panel gets clipped. A brace gets knocked out. The screen starts to pull free at one attachment point, then two, then a full section is loose and catching wind.

Nobody is assigned to the fence. That is the system failure. The fence is not on a maintenance schedule. It is not part of a daily or weekly walk with documented standards. It is not anyone’s specific responsibility after installation. It belongs to everyone in theory, which means it belongs to no one in practice. The degradation is incremental and distributed across dozens of small events, none of which individually feel like a problem worth stopping the day for.

By the time the fence is visibly non-compliant, the gap between the current condition and the standard has grown so large that fixing it feels like a project rather than a maintenance task. And a maintenance task that has grown into a project gets deferred even further because now it requires planning, material, and labor that have to be pulled from the real work.

They Didn’t Fail the System

When a project’s fence line looks bad, the instinct is to find someone to hold accountable. Who was supposed to be watching the fence? Why didn’t the foreman catch this? Why didn’t anyone report it?

The answer is usually that nobody was watching the fence because the system never assigned anyone to watch it. The foreman didn’t catch it because the foreman has eighty things competing for attention and the fence was not on the daily checklist. Nobody reported it because slow degradation does not produce a report-worthy event on any single day. It produces a hundred small events, each one below the threshold of attention, that accumulate into a visible failure over weeks.

The person is not the problem. The absence of a maintenance system is the problem. Build the system and the fence stays compliant. Leave the system absent and blame the person when it fails, and the fence will fail again on the next project exactly the same way.

What Compliant Actually Looks Like

The difference between a compliant fence setup and a non-compliant one is not ambiguous. It is specific, observable, and binary at every checkpoint.

Uniformly level post tops mean that the top line of the fence reads as straight and intentional from any viewing angle. Bent or uneven post tops create a visual signal of neglect and, more practically, reduce the structural integrity of the panel connections. A post that has been bent by contact with equipment is a post that is no longer carrying its share of the wind load, which means the adjacent panels are carrying more, which means they will fail sooner.

Screen secured tautly on the interior face is a safety specification, not an aesthetic preference. Screen mounted on the exterior catches wind and acts as a sail, pulling away from the fence and extending into pedestrian space. Screen mounted on the interior is pressed against the panels by wind rather than pulled away from them. That single installation decision, interior versus exterior, is the difference between a screen that stays put in wind and one that becomes a sidewalk hazard.

New, undamaged panels maintain the structural envelope of the fence and the visual standard of the project. A damaged panel is a weak point in the perimeter and a visual signal that the project tolerates degradation. Proper internal bracing keeps the fence stable under wind load and prevents the slow lean that eventually puts a post over pedestrian space. Clean, unobstructed sidewalk access is both a compliance requirement and a basic obligation to the public using the space adjacent to your project. Uniformly placed base supports distribute the load and prevent the shifting that leads to panels separating and opening gaps in the perimeter.

Each of those elements is a system input. When all six are maintained, the fence performs its function and communicates a standard. When any one of them degrades, the system starts to fail and the public sees it before the project does.

Why the Fence Is a Leadership Signal

The fence matters beyond compliance for a reason that most project leaders understand intuitively but rarely act on deliberately.

Standards are contagious. A project where the perimeter is clean, the fence is taut, the sidewalk is clear, and the base supports are uniform is a project that communicates a standard before anyone walks through the gate. Every trade partner arriving on site that morning receives the signal: this is a project where the details are maintained. That signal influences how they set up their work area, how they leave their zone at the end of the day, how they treat shared spaces, and how seriously they take the standards that the superintendent communicates in the morning meeting.

The reverse is equally true. A fence line with loose screen, bent posts, and obstructed sidewalks communicates that the standard here is flexible. That message does not stay at the perimeter. It migrates inward. The laydown yard gets a little less organized. The gang box gets a little less maintained. The zone handoffs get a little less clean. The tolerance for degradation that started at the fence line eventually touches the work itself, and by then it is a culture problem rather than a maintenance problem.

This is why the fence is a leadership system and not a facilities task. The condition of the perimeter is a statement about the project’s relationship with standards, and that statement is being read every day by every person who enters the site and every member of the public who walks past it.

Building a Fence Maintenance System

A compliant fence line does not maintain itself, and hoping someone will notice problems is not a system. The system needs three components to work.

First, the fence needs to be on a scheduled inspection cadence. Weekly at minimum, more frequently during weather events or periods of heavy delivery and equipment activity along the perimeter. The inspection is a walk of the full perimeter checking each of the six compliance points: post level, screen attachment and tension, panel condition, bracing integrity, sidewalk clearance, and base support placement. That walk takes fifteen to twenty minutes and prevents the slow degradation that turns a compliant fence into a liability.

Second, the inspection needs an owner. One person, with the authority to order replacement panels and the expectation that deficiencies found during the walk will be corrected within twenty-four hours. Shared responsibility for the fence is no responsibility for the fence.

Third, replacement materials need to be on site. A project that has to order a replacement panel and wait three days for delivery is a project that will run non-compliant for three days while the order processes. Having two or three spare panels, a roll of screen material, and replacement hardware staged on site means that any deficiency found during the walk can be corrected the same day.

Signals Your Fence System Needs Attention

Walk your perimeter today and look for these patterns:

Screen fabric that is loose, pulling away from attachment points, or mounted on the exterior face rather than the interior
Post tops that are no longer uniformly level, indicating equipment contact or wind damage that was not corrected
Panels with visible damage, holes, or separation at connection points
Base supports that have shifted, creating gaps between panels or allowing posts to lean
Any sidewalk obstruction, including shifted sandbags, scattered materials, or screen fabric extending into the pedestrian path

Each of those findings is a same-day correction, not a discussion item. The cost of fixing any one of them is measured in minutes. The cost of leaving them is measured in the message they send every hour to every person who passes your project.

The Standard Starts at the Property Line

Your project’s relationship with quality is visible before anyone walks through the gate. The fence line is the first page of the story the project is telling, and it is being read by the public, by inspectors, by trade partners arriving for their first day, and by the project owner driving past on a weekend.

That first page is yours to write. Make it clean, make it level, make it compliant, and make it maintained. The discipline that holds the perimeter standard is the same discipline that holds the schedule, the safety program, and the quality standard on the work itself. 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 teach that standards start at the smallest, most visible detail and scale inward from there, because the detail is the culture.

Here is your challenge. Walk your fence line this afternoon. Not tomorrow. Not after the next meeting. Today. Walk every linear foot of it with the six compliance points in mind. Fix what you find, assign what you cannot fix today, and schedule the walk as a weekly event that does not get skipped.

Edwards Deming said: “Quality is everyone’s responsibility.” Start at the fence line and let the quality work its way in. The public is already watching.

On we go.

FAQ

Why does it matter whether the screen is mounted on the interior or exterior face?
Screen mounted on the exterior catches wind and acts as a sail, pulling away from the fence and extending into pedestrian space. Screen mounted on the interior is pressed against the panels by wind rather than pulled away from them. The interior mounting is structurally more stable under wind load and eliminates the hazard of loose fabric blowing into the sidewalk. It is a safety specification, not a preference.

How often should the fence line be inspected?
Weekly at minimum during normal conditions, and additionally after any weather event with significant wind, after heavy delivery or equipment activity along the perimeter, and after any reported damage. The inspection is a full perimeter walk checking post level, screen condition, panel integrity, bracing, sidewalk clearance, and base supports. It takes fifteen to twenty minutes and prevents the slow degradation that makes fence problems invisible until they are severe.

Who should be responsible for fence maintenance?
One specific person with the authority to correct deficiencies and order replacement materials. Shared responsibility produces no responsibility. The assigned person does not need to make every repair personally, but they need to own the inspection cadence, the standard, and the follow-through on corrections.

If you want to learn more we have:

Discover Jason’s Expertise:

The Advanced Japanese Toilet System

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

Read 22 min

The Advanced Japanese Toilet System: What Obsessive Design Teaches Construction About the Friction Nobody Reports

A modern Japanese toilet has more thoughtful design than most construction trailers, most field offices, and most project management systems combined.

Eleven distinct features. Each one solves a small problem most people never thought to articulate. A sensor-activated lid so nobody touches the surface. A heated seat with adjustable temperature. A pre-mist that coats the bowl before use so waste does not adhere. A self-cleaning nozzle that cleans itself before and after every cycle. An adjustable bidet wand for personalized hygiene. A warm air dryer so paper becomes unnecessary. Power-saving modes that optimize water and electricity automatically. An activated-carbon deodorizer. A dual-flush system with smart sensors. And a wireless remote that controls every function from a wall-mounted panel. Here is the deal. Nobody asked for most of those features. Nobody filed a complaint about the problems they solve. The designers found the friction by watching, not by waiting for someone to report it.

The Pain That Stopped Being Pain

Every industry has friction so familiar that people stop experiencing it as friction. They absorb it. They work around it. They develop habits that accommodate it. And eventually they forget there was ever a problem at all, because the workaround became the process and the process became invisible.

In construction, these invisible frictions are everywhere. The tool crib that requires a ten-minute walk and a conversation with someone who may or may not be there. The drawing set that is one revision behind because nobody walked the new set to the field. The material staged two zones away from where the work is happening because the laydown plan was drawn during mobilization and never updated. The daily report that gets filled out from memory at four in the afternoon because there is no system for capturing information at the point of work.

Nobody complains about these things anymore. That is not because they stopped being problems. It is because the people experiencing them got good enough at absorbing the cost that the cost became invisible to everyone upstream. The foreman does not report that the tool crib walk takes ten minutes because the foreman stopped timing it three months ago. The superintendent does not flag the material staging distance because the crew adapted by starting their day with a longer haul and the schedule absorbed it. The cost is real, it runs every day, and it lives in a category that no report captures: friction that was accepted rather than eliminated.

The Failure Pattern

The failure pattern is designing for the major functions and abandoning the small ones to the user.

A construction project gets real design attention on a handful of major systems. The schedule is designed. The budget is designed. The safety program is designed. The procurement process is designed. Those systems get meetings, reviews, software, and accountability structures. They are the heated seat and the automatic flush of the project, the features that are obviously important and obviously worth investing in.

Everything else gets left to the person doing the work. How the crew gets information in the morning. Where their water is. How far the walk is from parking to the work face. Whether the permit they need is findable in under sixty seconds. Whether the tool they need is staged where they need it or two hundred feet away. These are the pre-mist, the deodorizer, the self-cleaning nozzle of the project. Small, specific, high-frequency interactions that nobody designed and that compound into hours of lost capacity every single day.

The Japanese toilet refuses to make that division. It treats every moment of contact between the person and the product as worthy of design. That refusal is what makes it remarkable, and that refusal is what construction leadership needs to learn.

They Didn’t Fail the System

When a crew is slower than expected, when a foreman seems perpetually behind, when the schedule slips by small amounts that nobody can explain with a single cause, the diagnosis usually lands on the people. They need to move faster. They need better time management. They need more urgency.

That diagnosis misses the actual mechanism. A crew absorbing fifteen small frictions a day is a crew that has lost an hour of capacity before the first real problem even surfaces. They are not slow. They are navigating a system that never cleared the path for them. Every unnecessary walk, every search for a document, every wait for an answer, every material haul from the wrong staging area is a withdrawal from that crew’s productive capacity. The person looks slow because the system consumed their speed before they got to the work.

The Japanese toilet understood this at the product level. It did not assume the user would figure out cleanliness, odor management, and hygiene on their own. It watched the complete experience and built a response for every friction point. Construction projects need to make the same decision about the complete crew experience, and most have not made it yet.

What Eleven Features Teach About System Design

The lesson of the Japanese toilet is not about any individual feature. It is about completeness.

A single feature, the heated seat, is a nice addition. Two features together, the heated seat and the bidet, start to feel like a system. By the time you reach eleven features, each one addressing a specific friction in the user experience, you are looking at something qualitatively different from a product with upgrades. You are looking at a product where someone refused to stop watching until every friction was addressed.

That completeness produces an experience where the user never encounters a problem the system has not already handled. They do not need to think about hygiene because the self-cleaning nozzle handles it. They do not need to worry about odor because the activated-carbon deodorizer handles it. They do not need to manage flushing because the smart sensors handle it. The cognitive load of the experience approaches zero because every decision that could be made by the system was moved out of the user’s hands.

Apply that principle to a construction crew’s daily experience and ask yourself how close your project comes. How many decisions is the crew making that the system should have already made for them? How many walks are they taking that a better staging plan would have eliminated? How many searches for information are they running that a better communication system would have prevented? Each gap between the Japanese toilet standard and your project’s current state is a feature your system is missing, and your crew is absorbing the cost of every missing feature, every day.

The Pre-Mist as a Construction Principle

The pre-mist feature deserves specific attention because it captures a design principle that transfers directly.

Before the toilet is used, a fine mist of water coats the bowl surface. This prevents waste from adhering, which means the flush cycle is more effective and the bowl stays cleaner with less water and less effort. The feature is preventive. It addresses the problem before the problem exists. The user does not know it is happening. They just notice that the experience is cleaner than they expected.

In construction, this is make-ready planning. It is constraint removal before the crew arrives. It is kitting materials to the point of use before the trade enters the zone. It is clearing the work face before the Takt clock starts. Every one of those practices changes the conditions ahead of the work so the work flows clean rather than fighting friction that should have been eliminated upstream.

Projects that run make-ready planning well are projects where crews describe the work as smooth. Projects that skip it are projects where every day feels like a fight, where recovery is more common than execution, and where the people doing the work absorb the cost of upstream failures they had no part in creating. The pre-mist takes fifteen seconds and prevents hours of cleaning. Make-ready planning takes hours and prevents weeks of recovery. Same principle at a different scale.

Signals Your Project Has Unaddressed Friction

Go walk one complete crew experience from arrival to the work face and watch for these patterns:

A resource positioned for setup convenience rather than for the person who uses it forty times a day
A workaround so established that new hires learn it during onboarding as though it were the real process
Information that requires a person to go find it rather than having it arrive where and when it is needed
A task that takes more steps than it logically should, where the extra steps have become invisible to the people performing them
A small annoyance that everyone can name but nobody has proposed fixing because it feels too minor to escalate

Each one of those is a missing feature. Each one is running a cost that nobody is tracking.

Why the Small Frictions Cost the Most

The instinct in construction leadership is to focus attention on the large, named problems. The schedule recovery. The budget overrun. The safety incident. Those are real and they deserve real attention. But they are also visible, tracked, and assigned. Someone is working on them.

The small frictions are not assigned to anyone. They persist for the entire duration of the project, quietly consuming capacity from every person who encounters them. A two-minute friction that hits thirty people twice a day is two hours of lost capacity every day for the life of the project. That is worse than most items on the constraint log, and it will never appear on the constraint log because nobody named it.

Lean construction teaches exactly this discipline. Takt planning makes flow visible. Workface planning clears constraints before crews arrive. Kitting, point-of-use storage, and zone control position resources where the work happens rather than where they are convenient to store. 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 bring the discipline of seeing friction that everyone else has accepted and eliminating it systematically, which is the discipline that makes the difference between a project that functions and a project that flows.

Go Count What Nobody Counts

Here is your challenge. This week, walk one crew’s complete experience from their truck to the work face and back again. Do not fix anything. Just count. Count every unnecessary step, every search, every wait, every workaround. Write the number down and multiply it by the number of days remaining on the project.

That number is the cost of friction your project has been absorbing since mobilization. Now that you can see it, you can design for it. That is all the Japanese toilet did. Someone watched, counted, and refused to stop until every friction had a solution.

Epictetus wrote: “First say to yourself what you would be, and then do what you have to do.” The project you would be is one where no crew member fights a friction the system should have already solved. Go build that project, one missing feature at a time.

On we go.

FAQ

How does a Japanese toilet relate to construction management?
The connection is the design philosophy, not the product. The Japanese toilet demonstrates what happens when someone watches the complete user experience and eliminates every small friction systematically rather than designing for the major functions and abandoning the rest. That same discipline applied to a construction crew’s daily experience is what separates projects that flow from projects that grind through every day.

What is the pre-mist principle in practical construction terms?
It is preventive design applied before the work begins. Make-ready planning, constraint removal, kitting, and point-of-use material staging are all pre-mist equivalents. They change the conditions ahead of the crew so the work encounters clean surfaces rather than friction that should have been cleared upstream. The investment is small. The downstream cost it prevents is large.

How do you find friction that people have stopped seeing?
Walk the experience yourself with fresh eyes and count everything that requires extra effort, extra steps, or extra time. The other reliable method is to ask a new hire what surprised them in their first week. People who have not yet adapted to the friction can still see it clearly. Once someone has been on the project for three months, the adaptation has set in and the friction becomes invisible to them.

If you want to learn more we have:

Discover Jason’s Expertise:

Why Do Trade Partners Stop Trusting General Contractors?

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

Read 16 min

Why Trade Partners Stop Trusting General Contractors

Here’s the deal. I love general contractors. I work for general contractors, I support general contractors, and I want them to win. And I am going to say something that will land hard anyway, because it needs to be said. Most GCs, even the big, well known ones, no longer know how to do the actual job that trust with trade partners depends on.

That job is simple to describe and hard to execute. Keep a remarkable environment. Keep every trade on a shared rhythm. Make sure information, materials, and payment actually reach the people who need them, on time, every time. Most GCs have quietly stopped doing that, and then act surprised when trust with their trade partners has eroded.

What the Job Actually Requires

A general contractor exists to create the conditions trades need to succeed. That means a jobsite that is organized and safe. It means a schedule with real rhythm, not chaos dressed up as urgency. It means the three resources every trade genuinely depends on arriving reliably: accurate information, available materials, and payment on time.

None of that is complicated to describe. It is a fundamentally supportive role, and when it is done well, trades show up, do excellent work, and want to come back for the next project. When it is not done well, the entire relationship starts from a place of suspicion instead of partnership, no matter how good the individual people involved might be.

What Has Actually Been Happening Instead

Here is the pattern I see repeating across projects, and it is not subtle once you name it. Trades get badmouthed behind closed doors. They get criticized publicly and run down in meetings where they are not present to respond. Payment gets delayed past when it was earned. Cure notices get issued as a default management tool instead of a genuine last resort. Credit for a well finished job goes to the GC’s own marketing, with no mention of the trade partners who actually built it.

Then, when the schedule slips, the question that gets asked is why the trade is not done yet. Nobody stops to ask whether the trade was actually given a system capable of letting them finish on time in the first place.

Watch for these as signs a GC has slipped into this pattern, whether intentionally or not:

Trade partners criticized in meetings they are not present to respond to
Payment consistently late relative to what the contract and completed work actually earned
Credit for finished work going entirely to the GC with no acknowledgment of the trades who built it

Any one of these erodes trust. All three together destroy it.

Nearly Everything That Goes Wrong Is the GC’s Responsibility

I want to be precise about this, because it is a strong claim and I mean it precisely. Assuming a supportive owner and a reasonably fair contract, nearly everything that goes wrong on a construction project traces back to the general contractor. Not most things. Nearly everything.

There are really only two things I would ever put on a trade partner. Either they do not participate, meaning they do not show up, engage, or follow through on what they committed to. Or they ask for more space than the project can reasonably give them. That is the complete list. Everything else, delays, quality problems, coordination failures, is the trade doing their honest best inside a system the GC built, and if that system did not set them up to succeed, the failure belongs to whoever built the system, not to the people trying to work inside it.

Failing Despite Their Best Efforts

Edwards Deming put it plainly: “A bad system will beat a good person every time.” That is exactly what is happening on a huge number of jobsites right now. Trade partners are genuinely trying, genuinely skilled, and genuinely failing, not because they lack competence or effort, but because the system around them, the schedule, the information flow, the payment cadence, the basic respect, was never built to let them succeed.

That distinction matters enormously, because it changes where the fix belongs. If you believe trades are failing because they are lazy or careless, you respond with more pressure, more cure notices, more criticism. If you recognize trades are failing despite real effort inside a broken system, you respond by fixing the system, which is the only response that actually works.

Why Trust Has Declined So Broadly

The honest reason a lot of trade partners no longer trust general contractors is not personal animosity. Most GCs are genuinely good people, and I say that without reservation. The problem is that the majority of general contractors, as an industry pattern, have become incompetent at the specific job that earns trust: creating an environment where trades can actually do their best work and be treated with basic respect while doing it.

That gap between good intentions and actual system competence is where trust dies. A trade partner does not need a GC to be perfect. They need a GC who pays on time, communicates clearly, protects their working conditions, and gives credit where it belongs. When those basics slip industry wide, trust erodes industry wide, and every individual GC, even the genuinely good ones, inherits the suspicion built up by the pattern as a whole.

What Rebuilding This Actually Requires

None of this is really about defending trades or attacking GCs. It is about naming a system failure clearly enough that it can actually be fixed, because vague guilt never changes behavior and specific accountability does.

A GC that wants to rebuild trust starts by treating the three resources, information, materials, and payment, as non negotiable commitments rather than variables that flex under pressure. It means removing the habit of criticizing trades in rooms they cannot respond in, and replacing cure notices as a default tool with genuine problem solving conversations first. It means giving credit publicly to the trades who actually built the work, consistently, not occasionally. And it means asking, before ever asking why a trade is not done, whether that trade was actually given a real system to succeed inside.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help general contractors build the kind of environment, rhythm, and resource flow that earns trust back, because that trust is not restored through better marketing. It is restored through a system that actually works the way it is supposed to for the people doing the physical work.

So here is the challenge. Look at your last project and ask honestly whether information, materials, and payment reached your trade partners reliably and on time. Ask whether any trade got criticized in a room they were not part of. Ask whether the credit for a job well done included the people who actually built it. Wherever the honest answer is uncomfortable, that is exactly where the system needs to be rebuilt.

Jason Schroeder said it plainly, echoing Deming: “A bad system will beat a good person every time.” Trade partners are not failing you. The system around them is failing them, and that system is yours to fix.

On we go.

FAQ

If a trade partner misses a deadline, how do you know whether it is their fault or the GC’s system?
Start by checking whether the trade actually received what they needed to succeed: accurate information on time, materials available when scheduled, and space in the zone that matched what was reasonably promised. If those were all genuinely in place and the trade still did not participate or engage, that is a legitimate trade issue. If any of those three were missing or unreliable, the responsibility sits with the system the GC built, not with the trade trying to work inside it.

Why does the article say only two things can be blamed on trade partners?
Because outside of a trade failing to participate or asking for more space than a project can reasonably provide, nearly every other failure traces back to conditions the general contractor controls, such as information flow, material availability, payment timing, and schedule design. Narrowing the list this tightly forces honest accountability rather than letting vague blame spread onto people who were genuinely doing their best inside a flawed system.

How does late payment specifically damage trust with trade partners?
Payment is one of the three core resources a trade depends on to keep their own crews paid, their materials ordered, and their business running. When payment consistently lags behind completed work, it signals that the GC’s commitments cannot be relied upon, which erodes the foundation trust is built on far faster than almost any other single factor, even when the actual construction relationship otherwise looks fine on paper.

If you want to learn more we have:

Discover Jason’s Expertise:

Is Lean Construction Worth It or Is It Just Another Buzzword?

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

Read 17 min

Is Lean Construction Worth It, or Just a Buzzword?

Here’s the deal. Lean construction is both a buzzword and the real deal, and which one you get depends entirely on who is implementing it and why. For people willing to actually do the work, it is genuinely worth it. For people using the word to sound current, it is exactly the empty buzzword everybody suspects it is.

I have watched this pattern play out with client after client, and it is remarkably consistent. A company never does well with Lean if it does not care about people and hold high, innovative expectations at the same time. Miss either one and the whole thing collapses into talk.

The Two Ways Lean Fails Before It Starts

There are two specific failure modes worth naming, because they show up constantly and they are entirely predictable.

The first is treating Lean as a profit strategy first. Any company that adopts Lean primarily because they want to make more money will fail with it, every time. Lean built on that foundation optimizes for the wrong thing from day one, and the moment the cost savings slow down or a shortcut looks tempting, the whole system gets abandoned, because it was never really about the people or the process. It was about the number.

The second is weak leadership. If the leader will not lead the implementation themselves, personally, visibly, and consistently, Lean fails and becomes exactly the buzzword people accuse it of being. There are people in this industry who talk constantly about Lean theory, the frameworks, the terminology, and if you look at their own companies or their own lives, you find mess, waste, and disrespect. They are using the language of Lean to build a personal brand or make money off the idea, without ever actually living it. That is the gross version of this, and it is unfortunately common.

What Real Implementation Actually Looks Like

Contrast that with someone like Paul Akers, author of 2 Second Lean and one of the clearest examples of Lean actually being lived rather than just discussed. He genuinely respects people. He builds stable environments. He runs on real one piece flow, understands Takt time and bottlenecks in his own operation, and uses visual information the way it is meant to be used, not as decoration but as an actual management tool. His business is built around quality, not around talking about quality.

That kind of practitioner has what I would call a perfect, functioning home and a genuinely well run company, and has personally led thousands of people through tours in Japan to see Lean thinking up close. When someone operates at that level, something interesting happens. They reach what looks like one hundred percent of what Lean can offer, and then a whole additional two hundred percent of possibility opens up beyond that. Reach that two hundred percent, and another three hundred percent opens up past it. People who genuinely live this end up doing things that most companies cannot even imagine, because they have kept climbing past the point where everyone else stopped.

For most people talking about Lean, none of that ever happens, because it stays talk. No action behind the language.

Proof Has to Be Visible, Not Just Claimed

I am not perfect at this either, and I do not pretend to be. But at home, we are constantly working on improving how things run. In the company, we have published 360 Lean videos at last count, out of 86 produced every single week, most of which never even make it to a public platform. There is a morning huddle every day. Every process gets improved on a regular basis. There is a formal kaizen process and a formal training process, not an informal one that only happens when someone remembers to run it. At home, I am doing the same thing with my own kids, treating improvement as a genuine way of life rather than a professional performance.

When I ran a project as a superintendent, I videoed and podcasted about it the entire time, showing the bathrooms, the huddles, the cleanliness, everything, specifically because I knew someone would eventually claim I was making it up otherwise. If you have not actually implemented these things yourself, in a way other people can see and verify, you do not really know whether they work. Talk without visible proof is exactly the buzzword version of Lean people are rightly skeptical of.

Watch for these signs you are looking at the buzzword version rather than the real thing:

Heavy on Lean terminology, light on any visible proof of daily practice
A personal life or company that is messy, wasteful, or disrespectful behind the public message
Adoption driven primarily by cost savings rather than genuine respect for people

Lean Requires Strong Leadership to Start, Not Permission

Here is the part that surprises people. Lean was never butterflies and kittens. At the start, it requires decisive, non negotiable direction from leadership. Not permissiveness, not asking everyone whether they are comfortable with the change, not a slow consensus building process before anything actually moves. Real implementation starts with a leader who decides it is happening and leads it themselves, followed by genuine training, real buy in, and eventually a culture that carries itself forward without needing to be pushed.

Look at any authentic Lean culture you have ever encountered, whether it is the Japanese companies where a lot of this thinking originated, Paul Akers’s own operation, or Bob Chapman’s Barry-Wehmiller, the company behind his book Everybody Matters. None of them asked permission before they started. The leaders in every one of those cases were not weak, and they led from the top, decisively, at the outset.

That does not mean Lean stays top down forever. It means the launch requires firm direction, because a system built on permissiveness at the start never survives its first real test. Once the training happens and buy in is genuine, the team carries the culture forward on its own, which is the whole point. But that self sustaining phase only exists because someone was willing to lead firmly enough to get it started in the first place.

Why This Distinction Actually Matters for You

None of this is really about defending a buzzword. It is about protecting the real thing from getting drowned out by people using the language without doing the work.

If your team is skeptical of Lean or Takt because they have seen it done badly elsewhere, talked about constantly and never actually lived, that skepticism is earned, and it deserves a real answer rather than more theory. The answer is proof. Visible huddles. Documented improvement. Leadership that shows up and leads the change itself instead of delegating the hard parts and taking credit for the results.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams build a genuine Lean culture rather than a borrowed vocabulary, starting with leadership that is actually willing to lead the change itself. That distinction between talk and proof is the entire difference between a buzzword and a system that actually works.

So here is the challenge. Look honestly at your own implementation, whatever stage it is at. Is leadership genuinely leading this personally and visibly, or has it been handed off to a program or a consultant to run without them? Is there documented, visible proof of daily practice, huddles, kaizen, improvement, or is it mostly discussed in meetings and rarely seen in the field? Wherever the honest answer is uncertain, that is exactly where the buzzword risk is highest.

Jason Schroeder said it plainly: “Lean was never butterflies and kittens.” It takes real leadership to start, and real proof to keep it honest.

On we go.

FAQ

Why does implementing Lean primarily to cut costs tend to fail?
Because cost reduction as the primary goal optimizes the system for the wrong outcome from the very beginning. The moment savings slow down or a shortcut becomes tempting, a Lean effort built on that foundation gets abandoned, since it was never actually rooted in respect for people or genuine process improvement in the first place.

What does it mean that Lean requires strong leadership at the start rather than permission?
It means the initial rollout works best when a leader decides firmly that the change is happening and leads it personally and visibly, rather than building slow consensus or waiting for everyone to feel fully comfortable first. That firm start is followed by real training and genuine buy in, after which the team can carry the culture forward on its own. Without that decisive beginning, most Lean efforts stall before training or buy in ever really happen.

How can a team tell the difference between genuine Lean practice and buzzword usage?
Look for visible, ongoing proof rather than terminology alone. Daily huddles that actually happen, a real kaizen and training process, and leadership that documents and shows their own practice rather than only discussing theory are all signs of the genuine version. Heavy use of Lean language paired with a messy, disrespectful, or wasteful reality behind the scenes is the clearest sign of the buzzword version.

If you want to learn more we have:

Discover Jason’s Expertise:

Takt Steering & Control: Keeping Your Construction Project on Track

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

Read 18 min

Takt Steering and Control: The Difference Between a Constraint and a Roadblock

Here’s the deal. Most of our industry uses one word, constraint, for two completely different problems, and that habit is quietly costing every trade partner on the jobsite. If you cannot tell a constraint apart from a roadblock, you cannot fix either one correctly, and you end up applying the wrong solution to both.

Takt steering and control exists to fix that confusion, and once you see the distinction clearly, the whole system of meetings, logs, and recovery strategies built around it starts to make sense.

Two Analogies Worth Remembering

Think about a vehicle with a governor, a physical device that limits how fast it can go no matter how hard you press the pedal. That is a constraint. It is built into the design of the system, and it stays there until somebody deliberately changes the design itself. Now picture a boulder sitting in the road in front of that same vehicle. That is a roadblock. It has nothing to do with how the vehicle was designed. It is a temporary obstacle sitting in the path, and it needs to be removed so the vehicle can keep moving.

Same distinction with a runner. A bad knee that limits top speed is a constraint, something built into the system that can be optimized through surgery, therapy, training, or a brace, but never fully eliminated. A cow standing in the trail is a roadblock. It is removable, it is temporary, and once it moves, the runner is back to whatever pace the constraint allows.

Constraints are system problems. Roadblocks are removable obstacles. Confusing the two means you either waste energy trying to permanently redesign something that was only ever a temporary blockage, or you accept as permanent something that should have been cleared out of the way in an afternoon.

The Train, the Tracks, and Where Constraints Actually Live

In a Takt system, think of the sequence of trades moving through a building as a train, and the zones that train moves through as the train tracks. Together, the train and the tracks are your system.

Anything involving how that train and those tracks were designed is a constraint. Zone sizing. Crew composition. Sequence of trades. Duration per zone. These get adjusted and optimized through the pull plan process, and by the time the pull plan is finished, most of the constraints in the system have already been worked through as thoroughly as they can be. That does not mean constraints disappear. It means they have been optimized as far as the design allows, the same way a runner’s knee can be treated but never turned into a knee that never had a problem.

Roadblocks live somewhere else entirely. As the train of trades weaves through the building, floor by floor, anything sitting in the way that is removable and temporary is a roadblock, not a constraint. Confusing a removable roadblock with a permanent constraint is exactly why our industry struggles here. We call everything a constraint, which means we have no name for the actual system problems buried underneath the roadblocks we could have simply cleared.

Finding and Removing Roadblocks Before They Ever Touch the Work

Once that distinction is clear, the primary daily focus becomes obvious. Find roadblocks and remove them before they ever impact the actual work.

That is what the meeting system is built to do. The first two meetings in the pull planning process exist mainly to adjust constraints, because that is where system level design decisions get made. Every meeting after that shifts almost entirely to finding and removing roadblocks, using a simple rhythm: identify, discuss, solve. In the trade partner weekly tactical, look ahead planning and weekly work planning both hunt for roadblocks. In the foreman’s daily planning session in the afternoon, the focus is on roadblocks specifically for the next day. In the morning conversation with the actual workers, the question is direct: do you have any roadblocks? During zone control walks, the trade partner working that zone gets asked the same question. Roadblocks get surfaced constantly, from every angle, so they can be removed well before they reach the project team, or ideally before they reach anyone at all.

Once a roadblock is identified, it goes on a log, broken out by phase and zone if needed, with a clear description and a person assigned to remove it. The log tracks how many are past due, how many are critical because they fall inside the next seven days, and how many total are still removable before the weekly work plan locks in. Here is the counterintuitive part. More entries on that log is actually the goal, not fewer, because more entries mean roadblocks are being caught early and far out from impact. What you actually want to avoid is only one or two entries showing up right before impact, which means roadblocks are being found too late to matter.

Watch for these signs your roadblock system is working the way it should:

Roadblocks logged well ahead of the zone rather than discovered the day work is due
A short list of past due items, since a growing backlog signals roadblocks are outrunning your removal capacity
Standard work posted visually in each zone, so successor crews inherit clean conditions instead of new problems

Building Cleanly So the Next Crew Inherits Nothing but Progress

Removing roadblocks is half the job. The other half is following standard work well enough that you never create a roadblock for the crew coming in behind you. That means having a clear visual reference in every zone showing exactly what the work should look like, the goals, the scope, and the specific dos and don’ts for that area.

Put those two things together, active roadblock removal and disciplined standard work, and the result is a crew that arrives to a zone, checks in with a simple question of whether they are on track to finish within their Takt time, and finds the work already prepared out ahead of them. That is what a clean handoff actually looks like in practice, not as a nice idea but as the direct result of two specific habits working together.

Recovering From an Impact Without Crashing the Schedule

Sometimes a roadblock does slip through and actually hits the work. CPM has exactly one answer for that situation, and it does not work. Crashing the activity, adding labor, adding crews, working overtime, rushing, pushing, panicking, and throwing in too much material all at once. That approach is not clever. It is a scramble that hurts people and rarely fixes the underlying issue.

Takt planning gives you twelve genuinely different ways to recover from an impact, none of which require shortening the duration or hurting anyone on the crew. You can adjust the sequence. You can draw on a buffer that was built into the plan specifically for this purpose. You can pull from workable backlog, meaning swing capacity that exists precisely so a delay does not become a crisis. You can rezone the affected work. There is a tool built specifically for constraints and roadblocks that, once you hit an actual impact, walks you through what would have prevented it and what your realistic options are for recovering from it, all tied to the specific type of delay you are facing.

Steering the Site Instead of Just Reacting to It

None of this works as a one time setup. It is a continuous discipline, identify, discuss, solve, log, remove, build clean, and recover intelligently when something still gets through.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow, including installing this exact IDS rhythm so roadblocks get caught early instead of discovered on the day they cost you. And if a GC ever pushes a trade partner toward a crashing style recovery, adding overtime, adding crews, rushing the work, that is exactly the moment to point back to the twelve Takt based recovery strategies and steer the conversation toward a production minded solution instead.

So here is the challenge. Pull your current roadblock log and check two things. How many entries sit past due, and how many are logged well out ahead of impact. If the far out column looks thin and the past due column looks thick, your team is finding roadblocks too late to matter, and that gap is exactly where to focus this week.

Jason Schroeder said it plainly: “We steer people through constraints and we control the environment out ahead so that nothing impacts the train of trades.” That is Takt steering and control in a single sentence.

On we go.

FAQ

How can you tell whether something is a constraint or a roadblock in the moment?
Ask whether it is built into how the system was designed or whether it is a temporary obstacle sitting in the path of otherwise normal work. A constraint, like crew size or zone duration, gets optimized through the pull plan and stays part of the system after that. A roadblock is removable and temporary by nature, and if it can be cleared without redesigning the sequence itself, it is a roadblock, not a constraint.

Why is it actually a good sign to have more entries on the roadblock log?
Because more entries logged well out ahead of the zone means roadblocks are being caught early, which is exactly when they are cheapest and easiest to remove. A short log with only one or two entries close to the work usually means roadblocks are being discovered too late to prevent impact, not that the team has fewer problems.

What makes the twelve Takt recovery strategies different from crashing a CPM schedule?
Crashing relies on adding resources, working overtime, and rushing the work, none of which fix the underlying cause and all of which put pressure directly on the crew. The Takt based recovery strategies, like adjusting sequence, drawing on a planned buffer, using workable backlog, or rezoning work, are built into the plan in advance specifically so a delay can be absorbed without shortening anyone’s duration or increasing pressure on the people doing the work.

If you want to learn more we have:

Discover Jason’s Expertise:

Takt Planning for Trade Partners: How Lean Construction Works in the Field

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

Read 18 min

Takt Planning for Trade Partners: Why Zones, Flow, and Buffers Work in Your Favor

Here’s the deal. Construction is hard. Not because anybody is doing it wrong, but because visualizing how trades actually move through space, and scheduling that movement by time and location, is genuinely difficult work. We do that hard work up front so that the people who matter most in the field, the workers and the foreman, get to work in flow instead of chaos.

That is the whole point of Takt planning, and if you are a trade partner wondering why we ask you to plan this way instead of the old batch and pull method, this is for you.

Workers and Foremen Are the Value, Everyone Else Is Support

Here is something worth saying plainly, because it reframes everything else. The GC, the trade partner management, all of us in a coordinating role, are necessary but non value adding. The workers and foremen are the ones creating real value on the jobsite. They are the kings and queens of the job, and everybody else exists to support them.

That is not a slogan. It changes what the planning work is actually for. We take on the hard job of designing zones and sequences ahead of time specifically so the people doing the physical work can move through the building smoothly, get paid fairly for their production, and go home on time. The complexity belongs to the planners. The comfort belongs to the crews.

How Most Construction Batches Work, and Why That Wastes Time

Picture a typical schedule. Most projects batch an entire area together, pull plan the whole thing at once, and lay out activities left to right without ever asking whether the work is evenly distributed across the space. It looks organized on paper. It is quietly wasting time.

The fix starts with breaking the building into zones, and the zones should be organized by work density, not by equal square footage. Two areas of the same size can carry wildly different amounts of actual work, so sizing zones by square footage alone guarantees some zones will be overloaded and others underused. When you first break a project into just a couple of zones based on a rough guess at density, you will usually find one zone that runs at an even pace and another that becomes a trade or activity bottleneck. That is not a disaster. It is an inefficiency gap, and even with that gap present, you have already gained time compared to the old batch approach, without cutting any time from the trade doing the work.

Finding the Right Number of Zones

The real gain comes from calculating the zone sizes properly instead of guessing, which is exactly what the Takt calculator and the pull plan process are built to do together with you.

Once zones are leveled by density using that calculation, you often end up with more zones, say four instead of two, and here is the part that benefits trade partners directly. If a bottleneck trade was identified, an additional crew gets paid for and trained ahead of time specifically to remove that bottleneck. The sequence then flows cleanly, one, two, three, four, with the same total duration on each activity, but without the inefficiency gap, because there is now enough resource in the system to keep pace. Nobody gets worked out of their time on this. Nobody gets trade stacked. Nobody gets trade burdened. The only reason this works is that an additional crew was paid for in advance, and often that additional crew is not even needed once zones are sized correctly from the start.

Watch for these signs your zoning is not yet dialed in:

Zones sized by equal square footage rather than actual work density
One trade consistently running the bottleneck with no additional resource planned around it
A pull plan that skipped the zone size calculation and went straight to a guess

Getting this right is not a one time exercise. It is a constant process of leveling and repackaging zones until you land on the best overall production duration, and that benefits you directly. Less general conditions cost, less general requirements cost, an earlier exit from the site, and the ability to move on to your next job sooner, all because the work is flowing instead of stacking.

How This Connects to the Weekly and Daily Rhythm

This zoning work is the foundation for the integrated production control system, and it is why we teach the whole thing as one connected rhythm rather than a series of disconnected meetings. Because the zones and the crew flow get worked out early, by the time look ahead planning, weekly work planning, and day planning happen with you, there is already a good sequence in place. Nobody is planning willy nilly. Everything downstream ties back to a Takt plan that already accounts for flow.

Every part of this points toward the same target: adding value to the foreman standing in the zone. That is not an afterthought at the end of the process. It is the reason the process exists at all.

What You Will Actually Experience as a Trade Partner

Here is the most important thing to understand going into pre-construction. You are not being handed a plan. You are helping build one. As we go through Lean, Takt, Last Planner, and Kanban training together, we optimize the work in these phases collaboratively, identifying the right number of zones with you, not deciding it for you and handing it down.

Then, during the pull plan, we gain real buffers and build a sequence with every trade genuinely bought in. This part is hard. It takes real time and real conversation. But it is the gem of the whole system, because it is what lets a project start strong, with a train of trades entering ready zones in flow from day one instead of scrambling to figure it out as they go.

From there, the daily rhythm takes over. We plan the day in the foreman huddle, communicate it in the worker huddle, and then monitor progress through the zones and handoffs in real time. If a delay shows up, there are multiple ways to recover it that do not fall on your shoulders, because the system was built with backup strategies from the start. Visual standards let everyone see how the system is actually performing, which is what makes continuous improvement possible instead of theoretical.

Takt Plans Are Promises, Not Decorations

I want to close on something that matters more than it sounds like it should. A Takt plan should never look like a random pretty diagram somebody put together to look organized. It is a timeline that represents a promise to the owner. It carries the ability to go faster during the pull plan if the team earns it. And it includes a backup zoning strategy with real buffers, in case conditions change.

Takt plans track key milestones and the supply chain visually, through properly leveled zones and properly leveled activities, sized to move fast without collapsing the moment something goes wrong. The result is a path that has real trade flow and real buffers, with a reasonable end date, instead of a critical path with zero room to breathe.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow, and that flow is built specifically to benefit the trade partners doing the work, not just the GC managing the paperwork. Buffers mean you are not the one asked to add labor, work overtime, and absorb the cost when a schedule falls behind, because the system was built with that protection already in it.

Here is the paradox worth sitting with. In a compressed CPM schedule, teams aim for something fast and impossible and consistently overshoot the end date. In a Takt system, teams aim for the right milestone, one built with real buffers and real flow, and consistently undercut it, finishing faster than the target. When you stop rushing, pushing, and panicking, and you actually build buffers back into the plan, projects get done faster, not slower. That is not intuitive, and it is true.

So here is the challenge. In your next pre-construction meeting, ask whether the zones on your project were sized by work density or by equal square footage, and ask where the buffers sit in the plan. If those answers are not clear yet, that conversation is exactly where the collaborative pull plan process is supposed to start.

Jason Schroeder said it plainly: “When you take care of people and when you flow, projects actually get done faster.” That is the whole system, distilled into one sentence.

On we go.

FAQ

Why should zones be sized by work density instead of equal square footage?
Because two areas of identical size can require very different amounts of work depending on what is happening inside them. Sizing zones by square footage alone tends to overload some zones and underuse others, which creates exactly the kind of bottleneck and inefficiency gap that a properly calculated, density based zone avoids.

Does adding an extra crew to remove a bottleneck cost the trade partner money?
The additional crew is paid for and trained ahead of time as part of the planning process, specifically to remove an identified bottleneck without asking the original trade to speed up or absorb extra burden. In many cases, once zones are sized correctly from the start using the proper calculation, that additional crew is not even needed, because the bottleneck never forms in the first place.

How are buffers different from the kind of slack that gets cut from a compressed schedule?
Buffers in a Takt plan are placed on purpose as a backup strategy, built into the zoning and sequence from the start, and protected rather than treated as waste. A compressed CPM schedule typically eliminates that kind of protection entirely to hit an aggressive target, which is exactly why it has no way to absorb a delay once one occurs.

If you want to learn more we have:

Discover Jason’s Expertise:

The Advanced Japanese Toilet System

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

Read 22 min

What a Japanese Toilet Teaches Construction Leaders About Eliminating Friction Nobody Named

A modern Japanese toilet has more thoughtful design than most construction trailers, most project management systems, and most field offices combined.

Here is the deal. Eleven distinct features, each one solving a small problem most people never thought to articulate. A sensor-activated lid so you never touch the surface. A pre-mist that coats the bowl before use so waste does not stick. A self-cleaning nozzle that cleans itself before and after every cycle. An activated-carbon deodorizer. A dual-flush system with smart sensors. A heated seat with adjustable temperature. Power-saving modes that optimize water and electricity without requiring the user to think about it. Eleven solutions to eleven frictions, and the person using it never has to name a single one of them because the system already did.

That is not overengineering. That is what happens when someone watches the actual experience closely enough to see the friction that everyone else learned to ignore.

The Pain That Becomes Invisible

Every industry has friction that has become so familiar it stops registering as friction. People adapt to it, work around it, absorb the cost of it daily, and eventually forget it was ever a problem at all. That adaptation is the most dangerous thing that can happen to a process, because once a problem becomes invisible, it becomes permanent.

In construction, the list is long. The foreman who walks two hundred feet to a water cooler because the water station was positioned for setup convenience rather than crew access. The superintendent who opens the same document three times a day because the filing system has no logic. The crew that stages material in a congested corridor because nobody designed a laydown plan for that phase. The trade partner who waits forty minutes for an answer because the person who can give it is physically unreachable somewhere on the site.

None of those people file a complaint. None of them log the waste. They just absorb it. They get good at absorbing it, and getting good at absorbing waste is the thing that keeps it alive. The friction stays because the adaptation is quiet, and because nobody with the authority to redesign the system is watching closely enough to see what the adaptation is costing.

The Failure Pattern

The failure pattern is building systems for the average case and then asking people to tolerate the gaps.

The Japanese toilet does not do this. It does not assume the user will figure out hygiene on their own and only step in for the major functions. It observes the complete experience, every moment of contact between person and product, and designs a response for each one. Pre-mist before use. Self-cleaning before and after. Deodorizer during. Warm air drying after. Each feature addresses a specific, small, real friction that the user has learned to live with, and the sum of all eleven is an experience where the user never encounters a problem the system has not already solved.

Construction systems are built the opposite way. We design for the major functions, the schedule, the budget, the safety program, and leave the small frictions to the user. The result is a system full of gaps that people fill with improvisation, workaround, and tolerance. Those gaps are not visible in any report. They are visible only to the person standing in them, and that person has usually stopped seeing them because they adapted years ago.

The failure is not that we do not care about the small things. The failure is that we do not watch closely enough to see them.

They Didn’t Fail the System

When a crew is slow, when a foreman seems disorganized, when a superintendent is perpetually reactive, the diagnosis in this industry almost always lands on the person. They are not efficient. They need better habits. They need to manage their time.

Here is what I would ask instead. How many invisible frictions did that person absorb today before anyone noticed? How many times did they walk farther than they needed to because the resource was in the wrong place? How many times did they wait for information that should have been at their fingertips? How many small problems did they solve manually that a well-designed system would have prevented entirely?

The person did not fail. The system never eliminated the friction that was consuming their capacity. And because the friction was small enough to absorb individually, it never got named, never got logged, and never got fixed. The person just got a little slower, a little more tired, a little more reactive, and the project called that a performance issue.

What Eleven Features Actually Teach

The Japanese toilet is not remarkable because of any single feature. A heated seat is nice. A self-cleaning nozzle is convenient. Any one of those features alone is a minor improvement. What makes the system remarkable is the completeness of the design, the fact that someone watched the entire experience from beginning to end and refused to leave any friction unaddressed.

That completeness is the lesson. World-class experiences are not built by adding one impressive feature. They are built by obsessing over every small friction the user has learned to ignore and eliminating all of them systematically.

Apply that thinking to a construction project and the implications are significant. Walk the experience of a crew from arrival to departure. Where do they park? How far is the walk to the work face? Where is their gear staged? How do they get information about the day’s plan? Where is the water? Where is the shade? How do they report a problem? How long does it take to get an answer? Each of those touchpoints is a moment where the system is either serving the person or asking the person to serve the system. The sum of all those moments is the crew’s actual experience of the project, and it determines their energy, their engagement, their ownership, and ultimately their output.

The Pre-Mist Principle

There is one feature on the Japanese toilet that deserves particular attention because it illustrates a design philosophy that transfers directly to construction operations.

The pre-mist sprays a fine layer of water on the bowl surface before use. The purpose is simple: a wet surface prevents waste from adhering, which means the flush cycle is more effective and the bowl stays cleaner with less water. The feature is invisible to most users. They do not know it is happening. They just notice that the toilet stays clean.

That is preventive design. It addresses the problem before the problem occurs, rather than cleaning up after it. The pre-mist does not wait for the mess and then work harder to remove it. It changes the surface condition so the mess never forms in the first place.

In construction, the equivalent is make-ready planning, constraint removal before the work begins, kitting materials before the crew arrives, clearing the zone before the trade enters it. Every one of those practices is a pre-mist. They change the conditions ahead of the work so the work flows cleanly rather than fighting friction that should have been eliminated upstream.

The projects that practice this consistently are the projects where crews describe the work as smooth, where the schedule holds, where the Takt rhythm actually produces what it was designed to produce. The projects that skip it are the projects where every day feels like a fight, where recovery plans are more common than execution plans, and where the people doing the work absorb the cost of upstream failures they had no part in creating.

Signals Your System Has Unaddressed Friction

Before you design anything new, go watch the current experience and look for these patterns:

A task that requires more steps than it logically should, where people have stopped noticing the extra steps because they have been doing them for months
A resource that is positioned for the convenience of setup rather than the convenience of the person using it daily
A workaround that has become so standard it feels like the process, even though someone invented it to get around a gap
Information that requires a person to go find it rather than having it arrive where and when they need it
A small annoyance that every person on the site can name but nobody has proposed fixing because it feels too minor to bring up

Each of those is a feature that the system should have but does not. Each one is a pre-mist that was never installed.

Why the Small Frictions Are the Expensive Ones

The instinct in construction is to focus leadership attention on the large problems, the schedule recovery, the budget overrun, the safety incident, the trade conflict. Those are real and they deserve real attention. But they are also visible, named, and already in the system. Someone is working on them.

The small frictions are not in the system. Nobody is working on them. They persist for months, sometimes for the entire duration of a project, quietly consuming capacity from every person who encounters them every day. A two-minute friction that hits thirty people twice a day is two hours of lost capacity, every day, for the life of the project. That math is worse than most named problems on the constraint log, and it never appears on the constraint log because nobody named it.

This is why the Japanese toilet is a better teacher than most management books. It does not lecture about eliminating waste. It demonstrates what it looks like when someone actually watches the complete experience and refuses to leave friction in place just because it is small. That refusal is the discipline. And that discipline, applied to a construction project, is what separates a project that feels good to work on from a project that wears people down.

Lean construction teaches exactly this. Takt planning is the framework for making flow visible. Workface planning is the method for clearing constraints before crews arrive. Kitting, point-of-use storage, and zone control are the tools for positioning resources where the work actually happens. 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 bring the discipline of seeing small friction and eliminating it systematically, which is the discipline that transforms a project from one that functions into one that flows.

Go Find the Friction Nobody Named

Here is your challenge. This week, walk one complete crew experience from arrival to the work face and back. Do not fix anything. Just count the frictions. Count the extra steps, the unnecessary walks, the waits, the workarounds, the searches for information that should have been at hand. Write the number down.

That number is your project’s invisible cost, and it has been running every day since the crew mobilized. Now that you can see it, you can design for it. That is all the Japanese toilet did. Someone counted the frictions, then eliminated them, one feature at a time, until the experience was seamless.

Taiichi Ohno said it directly: “Having no problems is the biggest problem of all.” The frictions your crew stopped reporting are the problems your project stopped seeing. Go see them.

On we go.

FAQ

How does a Japanese toilet relate to construction management?
The connection is the design philosophy, not the product. The Japanese toilet demonstrates what happens when someone watches the complete user experience and eliminates every small friction systematically. That same discipline applied to a construction crew’s daily experience, from arrival to the work face and through every resource interaction, is what separates projects that flow from projects that grind. The product is different. The observation practice is identical.

What is the “pre-mist principle” in construction terms?
It is preventive design: changing the conditions before the work begins so the work encounters less friction. Make-ready planning, constraint removal, kitting, and point-of-use staging are all pre-mist equivalents. They address the problem before the crew arrives rather than asking the crew to fight through conditions that should have been cleared upstream.

How do you find friction that people have stopped seeing?
Walk the experience yourself and count everything that requires extra effort, extra steps, or extra time. People who have adapted to friction cannot see it, but someone who walks the experience with fresh eyes and a counting habit will find it immediately. The other method is to ask a new hire what surprised them in their first week. New people have not yet adapted, so the friction is still visible to them.

If you want to learn more we have:

Discover Jason’s Expertise:

General Offerings

Company Offerings

Systems

SUBSCRIBE NOW !

Subscribe to our newsletters and stay updated!

Related Books

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

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

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

Related Books

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

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

Related Books

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

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

Calumet "K"

faq

General Training Overview

Superintendent / PM Boot Camp

Takt Production System® Virtual Training

Onsite Takt Simulation

Foreman & Field Engineer Training

Testimonials

Testimonials

agenda

Day 1

Foundations & Macro Planning

day2

Norm Planning & Flow Optimization

day3

Advanced Tools & Comparisons

day4

Buffers, Controls & Finalization

day5

Control Systems & Presentations

faq

UNDERSTANDING THE TRAINING

VALUE AND RESULTS

PLANNING AND SCHEDULING TOPICS

APPLICATION & TEAM ADOPTION

VIRTUAL FORMAT & ACCESSIBILITY

faq

GENERAL FAQS

CURRICULUM & OUTCOMES

LOGISTICS & FORMAT

PRICING & VALUE

SEO-BASED / HIGH-INTENT SEARCH QUESTIONS