Month: April 2026

The Production Laws, Feat. Hoots & Montero

Posted on by Danny Jiménez⁩
Read 23 min

Can You Stop Fighting Production Laws You Can’t Win Against?

Your project is behind schedule. So you throw more manpower at it. Double the crews. Add overtime. Push workers harder. Work in more areas simultaneously. And the project gets worse. Duration extends. Productivity crashes. Coordination chaos multiplies. Costs explode. And you wonder why more effort created worse results when the answer is you’re fighting production laws you can’t win against. Like gravity, production laws are physics governing how work flows through systems. When you work with them—optimizing bottlenecks, reducing variation, limiting work in progress—projects accelerate. When you fight them—adding manpower, increasing batch sizes, ignoring variation—duration extends despite increased effort. Yet teams keep fighting these laws wondering why more always creates worse when the problem is they’re battling physics instead of leveraging it.

Here’s what most teams miss. There are four production laws governing construction projects: Little’s Law, Bottlenecks, Variation, and Kingman’s Formula. You can’t beat them. You can’t fight them. When you jump, gravity pulls you down. When you increase work in progress, Little’s Law extends your cycle time. When you ignore your bottleneck, Theory of Constraints proves your system moves at bottleneck speed regardless of other resources. When you ignore variation, chaos compounds. When you don’t buffer for variation, Kingman’s Formula shows your system breaks. These aren’t suggestions. They’re physics. And companies in Illinois are cutting twenty percent off project schedules simply by working with these laws through Takt planning instead of fighting them through traditional push-based approaches.

The challenge is teams don’t know these laws exist. They’ve been saying “production” for decades without understanding what it means. When projects fall behind, everyone defaults to the same solution: throw more manpower and materials at it. This is literally the worst thing you can do. It’s what demons would recommend if they wanted to extend project durations. Because adding manpower increases coordination complexity. Adding materials increases work in progress. Both extend cycle times instead of reducing them. But nobody teaches this. So teams keep fighting production laws, wondering why harder work creates worse results when the answer is they’re violating physics governing how work flows.

The Four Production Laws You Can’t Fight

These laws govern construction production. Fight them and you lose. Work with them and projects accelerate:

  • Little’s Law: Work in Progress × Cycle Time = Throughput Time.

  • Limiting work in progress speeds throughput by reducing cycle time.

  • Don’t work in all four levels simultaneously—complete one, then move to the next.

  • Smaller batches move faster than large batches.

  • Five people at two minutes each = ten-minute throughput; eight people at one minute each = eight-minute throughput.

  • Bottlenecks: Your system moves at the speed of your slowest process.

  • Theory of Constraints proves system capacity equals bottleneck capacity.

  • Optimizing non-bottleneck resources doesn’t improve system performance.

  • Only optimizing the bottleneck increases throughput.

  • Adding resources elsewhere creates inventory piling up at the bottleneck.

  • Variation: The enemy creating chaos and unpredictability.

  • Variation compounds—small variations multiply into large disruptions.

  • Reducing variation stabilizes systems enabling flow.

  • Ignoring variation guarantees chaos regardless of other optimizations.

  • Kingman’s Formula: Buffer time needed for variation in production systems.

  • You can’t package work assuming perfect conditions.

  • Crews need buffers for variation and productivity dips during onboarding.

  • Realistic packaging prevents system breakdowns from unrealistic expectations.

Why Throwing Manpower Makes It Worse

Picture the pattern everyone defaults to. Project falls behind. Leadership demands acceleration. Solution: add more workers, add more materials, work in more areas simultaneously. This feels productive. More people equals more work equals faster completion, right? Wrong. This violates every production law simultaneously creating worse results despite increased effort.

Adding manpower increases work in progress. Little’s Law proves this extends cycle time. Now you have crews in four levels instead of one. Coordination complexity multiplies. Rework increases because trades stack on each other. Productivity per worker drops because congestion prevents efficient work. The throughput time extends despite more workers because you increased work in progress fighting Little’s Law.

Adding manpower also doesn’t address the bottleneck. If your bottleneck is design information arriving late, adding field workers doesn’t help. Theory of Constraints proves your system moves at bottleneck speed. Non-bottleneck resources working faster just creates inventory piling up at the bottleneck. You’ve increased costs adding workers who can’t work because the bottleneck hasn’t cleared. The system still moves at bottleneck speed. You just paid more for the same duration.

Adding manpower increases variation. More workers mean more communication paths. More coordination requirements. More potential for errors. More handoffs creating mistakes. Variation compounds. Small variations from individual workers multiply into large disruptions. Your system becomes less stable despite more resources because you increased variation sources fighting the law that variation is the enemy.

This is what Adam Hoots means when he says if demons wanted to extend project durations, they’d tell humans to throw manpower and materials at problems. It’s literally the worst response. But it’s what everyone does because nobody taught production laws. So teams keep fighting physics wondering why harder work creates worse results when the answer is they’re violating fundamental laws governing how work flows.

What Actually Works: Optimize Bottlenecks, Reduce Variation, Limit WIP

Instead of throwing manpower at problems, work with production laws. Companies in Illinois are cutting twenty percent off schedules by doing this through Takt planning. Not just twenty percent faster—twenty percent less frustrating. Better atmosphere. Happier teams. Lower stress. Better results from working with physics instead of fighting it.

Optimize your bottleneck. Theory of Constraints proves this is the only way to increase system throughput. Identify what’s slowing the entire system. Usually it’s information flow, design completion, or material procurement—not field labor capacity. Fix the bottleneck. Now the system moves faster. Adding field workers before fixing bottlenecks just creates expensive idle time.

Reduce variation. Stabilize workflows. Create predictable rhythms. Use Takt planning establishing consistent cycle times. Reduce variation in crew sizes, material deliveries, and information flow. The less variation exists, the more stable systems become. Stable systems flow. Chaotic systems with high variation stall regardless of resources added.

Limit work in progress. Little’s Law proves smaller batches move faster. Complete one level before starting the next. Finish one zone before moving to another. This feels slower because less apparent activity exists. But throughput time actually decreases because cycle time drops when you’re not managing coordination chaos from working everywhere simultaneously.

Buffer for variation realistically. Kingman’s Formula shows you can’t package work assuming perfect conditions. Crews need buffer time for variation and productivity dips. If you package four days of perfect-condition work into four-day Takt time, the system breaks when reality introduces variation. Package realistically with buffers. The system stays stable instead of constantly breaking.

Life Lessons from Bootcamp Participants

The bootcamp participants at Langston Construction revealed powerful insights. Older superintendents close to retirement said “I wish I had this twenty years ago because it would have impacted my career so much.” Another said “Even though I’m retiring in a couple months, I’m going to use this in my personal life and family.” These aren’t young workers seeking advancement. These are experienced professionals recognizing fundamental principles they missed despite decades in the industry.

This reveals how deeply the industry failed teaching production principles. Superintendents worked thirty to forty years never learning that throwing manpower at problems makes them worse. Never understanding bottlenecks determine system capacity. Never recognizing that variation is the enemy requiring reduction not tolerance. Never learning Little’s Law proving smaller batches move faster. They succeeded despite not knowing production laws. Imagine how much better they could have been knowing them.

The insight about using it in personal life and family matters too. Production laws aren’t just construction principles. They’re life principles. Limiting work in progress in your personal life—finishing one project before starting five more—creates better results than spreading yourself thin across many simultaneous commitments. Optimizing your personal bottleneck—the constraint limiting your capacity—improves your life more than adding activities elsewhere. Reducing variation in your routines creates stability enabling you to accomplish more with less stress. These laws govern all systems, not just construction projects.

Adam Hoots challenges everyone to give 100 percent authentically being yourself 100 percent of the time. Not the 100 percent that looks like what others expect. The 100 percent that’s authentically you. Be yourself while switching between learner and teacher. You don’t have all answers. But through your sphere of influence, you know people who do. Don’t fight production laws. Don’t fight being yourself. Work with both instead of against them.

The System Failed You

Let’s be clear. When teams don’t know production laws, it’s not entirely their fault. The system failed by teaching “production” without teaching what production means. Teams used the word for decades without understanding the physics governing how work flows. Nobody taught Little’s Law. Nobody explained Theory of Constraints. Nobody showed that variation is the enemy. Nobody demonstrated Kingman’s Formula. The system assumed people would figure it out. But they didn’t. So teams keep throwing manpower at problems wondering why it makes things worse when the answer is they’re fighting physics nobody taught them existed.

The system also failed by not teaching that adding resources often extends duration instead of reducing it. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. But common wisdom says “add more people to go faster.” This violates Little’s Law, ignores bottlenecks, increases variation, and breaks Kingman’s Formula. Yet everyone does it because nobody taught that production laws prove this approach fails. The system created default responses violating physics then blamed people for following guidance that was wrong from the start.

The system fails by not teaching Takt planning and other approaches working with production laws instead of fighting them. Companies cutting twenty percent off schedules aren’t working harder. They’re working with physics. Limiting work in progress. Optimizing bottlenecks. Reducing variation. Buffering realistically. These approaches leverage production laws instead of violating them. But teams never exposed to this keep fighting physics wondering why harder work creates worse results when the answer is they’re battling laws they can’t win against.

The Challenge

Here’s your assignment. Stop throwing manpower and materials at schedule problems. Start working with production laws instead of fighting them.

Learn the four production laws. Little’s Law shows work in progress times cycle time equals throughput time. Bottlenecks determine system capacity. Variation is the enemy. Kingman’s Formula requires realistic buffers. You can’t fight these. Work with them.

Identify your bottleneck. What’s actually limiting system throughput? Usually it’s information, design, or procurement—not field labor. Optimize that. Everything else is non-bottleneck resources creating expensive inventory piling up waiting for the bottleneck to clear.

Reduce variation. Stabilize workflows. Create predictable rhythms. Use Takt planning establishing consistent cycle times. The less variation exists, the more systems flow.

Limit work in progress. Complete one level before starting the next. Finish one zone before moving to another. Smaller batches move faster than large batches even though less apparent activity exists.

Buffer for variation realistically. Don’t package work assuming perfect conditions. Kingman’s Formula proves you need buffer time. Package realistically. The system stays stable instead of constantly breaking.

Stop fighting production laws. They’re physics. Like gravity, you can’t beat them. Jump and you fall. Increase work in progress and cycle time extends. Ignore bottlenecks and system moves at bottleneck speed. Allow variation and chaos compounds. Work with the laws instead of against them.

Companies cutting twenty percent off schedules aren’t working harder. They’re working with physics. You can too.

On we go.

FAQ

What are the four production laws?

Little’s Law (work in progress × cycle time = throughput time), Bottlenecks (system capacity equals bottleneck capacity per Theory of Constraints), Variation (the enemy creating chaos and unpredictability), and Kingman’s Formula (buffer time needed for variation in production systems). You can’t fight these laws—work with them instead.

Why does adding manpower often make projects worse?

Adding manpower increases work in progress (extending cycle time per Little’s Law), doesn’t address bottlenecks (system still moves at bottleneck speed), and increases variation (more workers = more coordination complexity = more chaos). It violates all production laws simultaneously creating worse results despite increased effort.

How do you work with production laws instead of fighting them?

Optimize your bottleneck (the only way to increase system throughput). Reduce variation (stabilize workflows creating predictable rhythms). Limit work in progress (complete one thing before starting the next). Buffer for variation realistically (package work accounting for reality not perfect conditions). These approaches leverage physics instead of violating it.

What’s the biggest mistake teams make with production?

Throwing manpower and materials at schedule problems. This feels productive but violates every production law. It increases work in progress, ignores bottlenecks, increases variation, and breaks realistic buffering. It’s literally what you’d do to extend duration, yet everyone does it because nobody taught production laws.

How are companies cutting 20% off schedules?

By working with production laws through Takt planning. Limiting work in progress. Optimizing bottlenecks. Reducing variation. Buffering realistically. Not working harder—working with physics. The projects are also twenty percent less frustrating with better atmosphere, happier teams, and lower stress.


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.

On we go

Growing High Speed Superintendents

Posted on by Danny Jiménez⁩
Read 22 min

Are You Growing Your Own Superintendents In-House?

You hire superintendents from the industry expecting them to know what they’re doing. They come with years of experience. But they can’t schedule. They don’t understand Takt. They resist technology. They can’t use Bluebeam. They don’t know IPD or coordination management. And worst, they hold you hostage because “there aren’t many good supers out there” so you tolerate their bad behavior afraid they’ll quit if you demand better. Meanwhile, you wonder why superintendent quality never improves when the problem is you’re hiring from a broken system that never taught them fundamentals. You’re bailing water without plugging the hole. Instead of growing your own superintendents through field engineering programs building fundamental capabilities from the ground up, you’re importing already-formed superintendents hoping they miraculously possess skills the industry never taught them.

Here’s what most companies miss. Being a superintendent is not a builder practicing position. You should be a builder to be a super. But you don’t practice building by being a super pointing and directing. You practice building when you’re doing drawings, layout, quality control, troubleshooting with workers, piecing things together. That’s field engineering. And every successful general superintendent Jason’s tracked had field engineering experience—forms, survey, field engineer, project engineer with field focus. He’s never seen someone go from college straight to assistant super and successfully climb to general superintendent or field director. Ever. The ones who made it had fundamental builder experience first. Because you can’t lead builders without understanding building fundamentals yourself.

The challenge is most companies don’t invest in field engineering programs. They take college graduates and make them assistant superintendents immediately. Or they hire experienced superintendents from the industry who never learned fundamentals either. Then they wonder why superintendent quality stays mediocre. The marshmallow study reveals the pattern. Kids who waited fifteen minutes for two marshmallows instead of eating one immediately did better in life—better relationships, more money, more social stability, less crime. Patience indicates character and predicts success. Taking time to learn fundamentals through field engineering builds Superintendent 2.0 with technological capabilities of project managers, strategic minds of military generals, and people skills from Dale Carnegie. Skipping fundamentals for immediate gratification creates superintendents who hold companies hostage through incompetence companies tolerate because alternatives seem scarce.

Why Field Engineering Builds Real Superintendents

Field engineering is where you practice being a builder. Not pointing and directing. Actually building. Here’s what field engineer boot camp requires showing why it creates superior superintendents:

  • Give participants two points and a set of drawings.
  • By day three, they must have footings placed in the ground.
  • Laser scan results to measure accuracy.
  • They must interpret bad plans, create drawings, determine layout, do mathematical calculations.
  • Actually lay out the work, build it, design formwork systems, get concrete in, schedule everything.
  • This is intense—80% of people in construction couldn’t do it without training.
  • But if you’re going to be a superintendent, you must know how to do this.
  • You can’t tell surveyors to lay out your building without knowing correct survey principles.
  • You can’t tell exterior crews to install without knowing how to piece things together, lay out embeds, calculate angles.
  • These are complex things builders with proper training can do and should do.

What Superintendent 2.0 Looks Like

The superintendent of the future isn’t the superintendent of the past. Superintendent 2.0 has capabilities traditional supers never developed:

  • Technological capabilities of a project manager—computers, Bluebeam, software, digital tools.
  • Strategic mind and logistics sense of a military general—thinking ahead, positioning resources, anticipating problems.
  • Ability to talk to anybody and influence people—Dale Carnegie people skills enabling mentorship and leadership.
  • Deep scheduling knowledge—Takt planning, visual flow schedules, production control systems.
  • Technology fluency—comfortable with digital coordination, BIM, collaboration platforms.
  • IPD understanding—integrated project delivery, collaborative decision-making, shared risk/reward.
  • Coordination management—resolving conflicts before they reach the field, enabling flow.
  • Operational stability—running clean, safe, organized jobs with just-in-time deliveries and visible scheduling.
  • Mentorship capability—building people while building projects, developing next generation.

The Problem: Grumpy Supers Holding Companies Hostage

Walk construction companies and you’ll see the pattern. Three superintendents. All grumpy. All resistant to change. All lacking fundamental skills like scheduling, technology, coordination. But companies tolerate their bad behavior because “there aren’t many good supers out there.” These superintendents know companies need them more than they need companies. So they resist training. They refuse new methods. They complain about technology. And companies accept this because alternatives seem scarce.

This is hostage-taking disguised as employment. Companies can’t demand better because these superintendents might quit. And replacing them with equally mediocre superintendents from the same broken system doesn’t improve anything. So companies stay stuck tolerating incompetence, resisting improvement, and wondering why projects struggle when the answer is they’re employing superintendents who never learned fundamentals and now resist learning them.

The solution isn’t hiring more from the broken system. It’s growing your own through field engineering programs building fundamental capabilities from the beginning. Stop importing already-formed superintendents hoping they miraculously possess skills nobody taught them. Start developing builders who become Superintendent 2.0 through intentional progression from fundamental field engineering to advanced superintendent capabilities.

Jason’s Never Seen This Path Succeed

Jason challenges anyone to prove him wrong. If you’re a general superintendent or field director for a large construction company and you achieved that by coming out of college and going straight into assistant superintendent without field engineering experience, contact him. Because he’s never seen it. Ever. Not once. Every successful general superintendent or field director he’s tracked had field engineering experience—some version of fundamental builder practice before becoming superintendent.

This isn’t coincidence. It’s cause and effect. You can’t lead builders without understanding building fundamentals. You can’t troubleshoot problems without having solved them yourself. You can’t mentor young builders without having walked their path. You can’t command respect from foremen and trades without having done the work they do. Field engineering builds these capabilities. Skipping it creates superintendents who point and direct without understanding what they’re directing or why it matters.

The companies that figure this out will dominate the next decade. They’ll have superintendents who actually know how to schedule, use technology, manage coordination, run operationally stable jobs, mentor people, and execute at levels traditional supers can’t match. And they won’t be held hostage by grumpy incompetent superintendents because they’ll have pipeline of well-trained builders ready to step into superintendent roles with fundamental capabilities already built.

How to Build Strong Field Engineering Programs

Stop shortcutting your future. Invest in field engineering programs developing fundamental builders who become Superintendent 2.0:

  • Start a field engineering program as first priority for field builders.
  • Get field engineer boot camps going—intensive training building real capabilities.
  • Integrate field engineering methods manual (Wes Crawford) into standard training.
  • Create monthly field engineer trainings maintaining skill development.
  • Build field engineering mentoring groups with lead field engineers guiding development.
  • Align career structure 100%—clear progression from field engineer to superintendent.
  • Get projects to pay for field engineers—not overhead, billable production support.
  • Create culture around field engineering immediately under dedicated field engineering group.
  • Align incentives rewarding field engineering excellence and progression.
  • Set higher expectations with training enabling people to meet them.
  • Provide builders good foundations before they become superintendents.

The Marshmallow Study and Patience

The marshmallow study reveals why patience matters. Researchers gave kids choice: eat one marshmallow now or wait fifteen minutes for two. They tracked those kids for 25 years. The ones who waited did better in life—better relationships, more money, more social stability, less crime. The act of patience indicated character and predicted future success.

This applies to superintendent development. You can get immediate self-gratification becoming assistant superintendent right out of school. Or you can wait, spend time as field engineer learning fundamentals, and become far more capable superintendent later. Immediate gratification feels good now but hurts long-term. Patience building foundations creates sustained success.

Companies face the same choice. Hire superintendents now from broken system hoping they’re competent. Or invest in field engineering programs growing your own Superintendent 2.0 over time. Quick hiring feels efficient. But it imports mediocrity. Patient development builds excellence. The marshmallow study proves patience wins. Companies patient enough to grow superintendents instead of hiring them will dominate companies taking shortcuts.

The System Failed You

Let’s be clear. When companies struggle finding good superintendents, it’s not entirely their fault. The system failed by not teaching that field engineering builds fundamental capabilities superintendents need. Nobody showed that you can’t skip fundamentals expecting people to learn them through superintendent experience. Nobody explained that every successful general superintendent had field engineering background. Nobody demonstrated that being superintendent is not builder practicing position—you practice building as field engineer before becoming superintendent. The system assumed people could jump from college to superintendent succeeding when evidence proves they can’t.

The system also failed by not teaching companies to grow their own instead of hiring from broken system. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. But hiring superintendents from industry that never taught them fundamentals just imports mediocrity. Companies must grow their own through field engineering programs building Superintendent 2.0 from ground up instead of hoping industry produces what it’s never produced before.

The system fails by tolerating grumpy superintendents holding companies hostage. When companies accept bad behavior because “there aren’t many good supers,” they enable the very problem preventing improvement. Stop tolerating incompetence. Start growing excellence through field engineering programs creating pipeline of well-trained builders ready to become Superintendent 2.0 with technological capabilities, strategic thinking, and people skills traditional supers never developed.

The Challenge

Here’s your assignment. Stop hiring superintendents from broken system hoping they know what they’re doing. Start growing your own through field engineering programs building fundamental capabilities from the beginning.

If you’re a company, build field engineering program as first priority. Get field engineer boot camps going. Create monthly trainings. Build mentoring groups. Align career paths. Get projects to pay for them. Create culture around excellence. Invest in fundamentals instead of bailing water without plugging the hole.

If you’re starting your career, take field engineering position if offered. Stay there long enough to learn fundamentals. Don’t jump to assistant superintendent immediately. Practice the marshmallow study—wait for two marshmallows instead of eating one now. The patience building foundations creates far greater success than immediate gratification becoming superintendent without fundamentals.

If you’re choosing between companies, pick the one with strong field engineering program. You’re not getting respect you deserve if you haven’t been given time to be field engineer learning how to interpret plans, create drawings, calculate layouts, build formwork, troubleshoot with workers. Companies without field engineering programs shortcut your development hurting your long-term success.

Stop tolerating grumpy superintendents holding you hostage. Build Superintendent 2.0 with technological capabilities of project managers, strategic minds of military generals, and Dale Carnegie people skills. Grow them through field engineering programs building fundamental capabilities traditional supers never developed.

Plug the hole by training fundamental builders at fundamental level. Then bail the water fixing current problems. Or do both simultaneously. But stop just bailing water without plugging hole creating endless cycle of mediocre superintendents you tolerate because alternatives seem scarce.

The superintendent of the future knows how to schedule, understands Takt, uses technology fluently, manages coordination, runs operationally stable jobs, and mentors people excellently. Grow them through field engineering. Build them from fundamentals. Create Superintendent 2.0.

On we go.

FAQ

Why is field engineering essential before becoming superintendent?

Being superintendent is not builder practicing position. You practice building through field engineering—doing drawings, layout, QC, troubleshooting, piecing things together. Every successful general superintendent Jason’s tracked had field engineering experience. He’s never seen someone go college to assistant super to general superintendent successfully without it.

What does Superintendent 2.0 look like?

Technological capabilities of project manager (computers, Bluebeam, software). Strategic mind and logistics sense of military general (thinking ahead, positioning resources). Dale Carnegie people skills (mentoring, influencing, leading). Deep scheduling knowledge (Takt, visual flow). Technology fluency. IPD understanding. Coordination management. Operational stability capabilities.

Why does the marshmallow study matter for superintendent development?

Kids who waited fifteen minutes for two marshmallows instead of eating one immediately did better in life—better relationships, more money, social stability. Patience indicates character and predicts success. Taking time learning fundamentals through field engineering builds superior superintendents. Skipping for immediate gratification creates mediocre superintendents.

How do you build strong field engineering programs?

Start field engineering program as first priority. Run field engineer boot camps. Create monthly trainings. Build mentoring groups. Align career paths clearly. Get projects to pay for them. Create culture around field engineering excellence. Align incentives. Set higher expectations with training enabling people to meet them.

Why are companies held hostage by grumpy superintendents?

Companies tolerate bad behavior because “there aren’t many good supers.” Superintendents know this and resist training, refuse new methods, complain about technology. Companies accept this because replacing them with equally mediocre superintendents from same broken system doesn’t improve anything. Solution is growing your own through field engineering programs.

Word Count: 1,996 words

 

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.

On we go

Working for a Failing Superintendent!

Posted on by Danny Jiménez⁩
Read 25 min

Are You Being Held Up by the Superintendent on the Project?

Your superintendent doesn’t know what they’re doing. No schedule exists. Or if one exists, it’s in their head and they haven’t shared it with anyone. They demand you work everywhere simultaneously destroying trade flow. They tell you to bring materials early creating chaos. They give you conflicting direction daily. And you’re waiting for them to map out your destiny, hoping they’ll eventually get organized and provide the plan you need to succeed. Meanwhile, your crew suffers. Your productivity crashes. Your profits evaporate. And you blame the superintendent for holding you back when the real problem is you’re being a victim instead of taking control. You’re waiting for someone else to create the conditions for your success when actually you must create those conditions yourself because incompetent leadership doesn’t disappear through patience—it gets worse through enabling.

Here’s what most foremen and trade partners miss. You’re in trouble either way. If you follow the superintendent’s bad advice working everywhere without flow, you’ll be in trouble because productivity will crash and they’ll blame you for not performing. If you do the right thing protecting trade flow even when it contradicts their demands, you’ll be in trouble because they’ll complain about you not following direction. Either path leads to conflict. So why not be in trouble and make money? Why not do the right thing creating flow, keeping crews consistent, bringing materials just-in-time according to inventory buffers, and executing properly even though the superintendent doesn’t understand? You’re getting blamed regardless. Might as well do it right and actually succeed instead of following bad direction into failure.

The challenge is shifting from victim mindset to ownership mindset. Expect nothing, appreciate everything, do the right thing. This creates non-emotional effective response enabling you to succeed despite incompetent leadership. But most people do the opposite. They expect everything from superintendents. They appreciate nothing because nobody’s meeting expectations. They respond as victims blaming others for their problems. This creates emotional ineffective response guaranteeing failure. You can’t control whether your superintendent is competent. But you can control whether you take ownership creating your own plan, protecting your trade flow, and executing properly regardless of their incompetence.

Two Mindsets: Victim vs. Owner

Your mindset determines whether incompetent superintendents destroy you or whether you succeed despite them:

  • Victim Mindset: Expect everything, appreciate nothing, respond as victim.

  • You expect superintendents to provide perfect schedules, clear direction, organized logistics.

  • When they don’t deliver, you feel robbed of what you deserved

  • You appreciate nothing because nobody’s meeting your expectations.

  • You respond as victim blaming them for your problems.

  • This makes you emotional, ineffective, and stuck.

  • You get in trouble because you followed bad direction into failure.

  • Owner Mindset: Expect nothing, appreciate everything, do the right thing

  • You expect nothing from superintendents, so they can’t take anything from you.

  • You appreciate everything they do provide, even small things.

  • You do the right thing regardless of whether they support you.

  • This keeps you non-emotional, effective, and moving forward.

  • You might get in trouble for not following bad direction, but you make money and succeed.

Why You’re in Trouble Either Way

Picture the reality. Superintendent tells you to work in five areas simultaneously. You know this destroys trade flow creating chaos. But you follow their direction anyway hoping obedience protects you. What happens? Productivity crashes. Crews stack on top of each other. Rework multiplies. Schedule slips. And the superintendent blames you for not performing. You’re in trouble because you followed their bad advice into failure.

Now picture the alternative. Superintendent tells you to work in five areas. You say “I’ll work in one area completing it fully before moving to the next, creating trade flow that actually finishes work.” They complain about you not following direction. They demand you spread out creating apparent busyness. You explain why flow works better and show them your plan. They’re unhappy. You’re in trouble for not following bad direction.

Either way, you’re in trouble. So why not be in trouble and make money? Why not do it right creating flow, finishing work, making profit, and actually succeeding even though the superintendent complains? You’re getting blamed regardless. Following bad advice into failure doesn’t protect you. It just makes you fail while being blamed anyway. But doing it right despite complaints at least creates success. You get blamed either way. Might as well succeed.

This is the secret most trades never learn. They think following superintendent direction protects them from blame. But it doesn’t. When projects fail, superintendents blame trades regardless of whose advice created the failure. So stop following bad advice hoping obedience excuses poor results. It won’t. Do the right thing creating flow and success. Then when superintendents complain, you can show the results proving your approach works better than theirs.

What Most Superintendent Advice Gets Wrong

Here’s the uncomfortable truth: 60-80 percent of superintendents don’t know what they’re doing. And almost 100 percent of things you hear from those 60-80 percent, if you take their advice, you’ll be doing it wrong. They don’t understand flow. They don’t understand production principles. They demand activity over effectiveness. And following their direction guarantees failure.

Jason has never heard an owner’s representative say “let’s work in one-process flow.” Never heard them say “let’s have the right crew sizes.” Never heard them say “bring materials just-in-time.” They just want to look busy. They say “bring the materials, bring the people, go out there, spend your money, I don’t care, I just want it done.” This advice destroys projects. But superintendents repeat it because they don’t know better. And trades following it fail because the advice was wrong from the start.

If you’re taking advice from uneducated superintendents—meaning superintendents who don’t know lean and flow principles—you’re going backwards. You need to protect your trade flow. You need to win-win solutions. When the superintendent or owner makes a request, answer the question they should have asked, not the question they asked. Respond to requests they should have made. Do things that should be done. Don’t stupidly follow directions that reduce your chances of flow.

For example: Owner says “start work next week clearing 320 acres.” You know this means land sits muddy for three months costing everyone money. Instead of blindly following, show them why starting just-in-time when materials arrive works better. Have the conversation. Make it visual. Communicate. Discuss. Fight for win-win. Don’t just blindly do stuff because someone with authority told you to when you know it’s wrong.

How to Take Control: What Foremen and Trades Must Do

Stop waiting for superintendents to map your destiny. Create your own plan. Here’s what that looks like daily:

  • Come with a plan or be part of someone else’s (which probably doesn’t work)

  • Draw pictures showing where you’ll be working and when.

  • Provide a schedule even if superintendent doesn’t have one.

  • If they have a schedule, adjust it with flow to create trade flow that works as win-win.

  • Communicate daily what you need to succeed.

  • Protect your trade flow—work in sequences that complete, not everywhere simultaneously.

  • Keep crews consistent—don’t crash-load then starve resources.

  • Bring materials just-in-time according to inventory buffers, not too early or too late.

  • Plan it first—make sure work is ready before you start.

  • Build it right—QC as you go, don’t pass defects forward.

  • Finish as you go—complete work fully before moving on, don’t come back later.

  • Have difficult conversations when direction contradicts flow principles.

  • Negotiate only win-wins—show how your approach benefits everyone.

  • Be prepared with visual communication and data proving your approach works.

The Story: If There Isn’t a Way, Pave a Way

Jason tells the story from his book Elevating Construction Superintendents. He was in charge of mechanical, site work, and systems. Another superintendent handled interiors but kept needlessly perfecting the schedule instead of sharing it with trades. The super said “you can’t make a schedule and show it to trade partners before it’s perfect.” Jason said “watch me. I’m going to coordinate with trade partners.”

The senior superintendent walked both of them out and said “Jason, you’re now in charge of this work. You’re no longer in charge of this work.” The other superintendent started to protest. The senior super said “you don’t have to worry about that anymore. Jason’s in charge now.”

The lesson stuck. Don’t ever wait for someone if there’s incompetence, waiting, or needless striving for perfect instead of excellent. Just move forward. Step on toes if necessary. Get it done. If there isn’t a way, pave a way. This is the mindset that succeeds despite incompetent leadership instead of being destroyed by it.

At the Constitutional Convention, 80 percent of the Constitution came from one person who came prepared. James Madison showed up with a plan. Everyone else contributed around his framework. If you don’t have a plan, you’ll be part of someone else’s. And if you’re working for a bad superintendent, they don’t have a plan. Or if they have one, it’s in their head and doesn’t work because they haven’t shared it. So you must come with the plan. Show up prepared. Create the framework. Then execute despite their incompetence.

The System Failed You

Let’s be clear. When foremen and trades struggle under incompetent superintendents, it’s not entirely their fault. The system failed by not teaching foremen to take ownership creating their own plans instead of waiting for superintendent direction. Nobody showed that you’re in trouble either way, so you might as well do the right thing and succeed. Nobody explained that following bad advice doesn’t excuse failure—you’re responsible for results regardless of whose direction you followed. Nobody demonstrated that trades must protect their own flow because superintendents often don’t understand flow principles.

The system also failed by not training superintendents properly. Sixty to eighty percent don’t know what they’re doing. They give bad advice destroying projects. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. But until superintendents get trained, foremen and trades must protect themselves by taking ownership instead of being victims. The system created this mess. But victims stay stuck while owners succeed regardless.

The system fails by not teaching the “expect nothing, appreciate everything, do the right thing” mindset. Most people expect everything, appreciate nothing, and respond as victims when expectations aren’t met. This creates emotional ineffective responses guaranteeing failure. But the alternative—expecting nothing so nobody can take anything from you, appreciating everything even small things, doing the right thing regardless of support—creates non-emotional effective responses enabling success despite incompetent leadership.

The Challenge

Here’s your assignment. Stop being a victim waiting for incompetent superintendents to map your destiny. Take control. Create your own plan. Come prepared with schedules, sketches, Gantt charts showing what you’re doing and when.

Shift to owner mindset. Expect nothing from superintendents so they can’t disappoint you. Appreciate everything they provide even if it’s small. Do the right thing protecting trade flow regardless of whether they support you.

Recognize you’re in trouble either way. Following bad direction leads to failure and blame. Doing the right thing leads to complaints and blame. Either path creates conflict. So choose the path that also creates success. Be in trouble and make money instead of being in trouble and failing.

Protect your trade flow. Don’t blindly follow advice from the 60-80 percent of superintendents who don’t understand flow. Answer the question they should have asked. Respond to requests they should have made. Do things that should be done. Fight for win-win solutions showing why your approach benefits everyone.

Communicate daily. Tell them what you need. Show them your plan. Have difficult conversations when direction contradicts flow. Come prepared so you’re not part of someone else’s plan that doesn’t work.

Plan it first. Build it right. Finish as you go. Keep crews consistent. Bring materials just-in-time. Work in sequences that complete. Do the right thing creating trade flow even when superintendents don’t understand.

If there isn’t a way, pave a way. Don’t wait for incompetent leadership to improve. Take ownership. Get it done. You know that workflow, trade flow, logistical flow, consistent manpower and materials, rhythm and continuity create your shortest path to winning.

On we go.

FAQ

What if following superintendent direction leads to failure?

You’re responsible for results regardless of whose advice you followed. Following bad direction doesn’t excuse failure—it just proves you lack courage to do what’s right. You’re in trouble either way. Might as well do the right thing and succeed instead of following bad advice into failure.

How do you “expect nothing, appreciate everything, do the right thing”?

Expect nothing from superintendents so they can’t take anything from you or disappoint you. Appreciate everything they provide even if small. Do the right thing protecting trade flow regardless of whether they support you. This creates non-emotional effective response enabling success despite incompetent leadership.

Why are you “in trouble either way”?

Following bad direction leads to productivity crashes and blame for not performing. Doing the right thing contradicting their demands leads to complaints about not following direction. Either path creates conflict. So choose the path that also creates success—do the right thing and make money.

What should foremen do when superintendents don’t have plans?

Come with your own plan. Draw pictures showing where you’ll work. Provide schedules even if they don’t have one. Communicate daily what you need. Come prepared so you’re not part of someone else’s plan that doesn’t work. Be like James Madison at Constitutional Convention—show up with the framework everyone else builds around.

How do you protect trade flow when superintendents demand chaos?

Create your plan with proper flow. Show them visually why it works better. Negotiate win-wins explaining how your approach benefits everyone. Have difficult conversations. Do the right thing even if they complain. You’re getting blamed either way—might as well succeed while being blamed instead of failing while being blamed.

 

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.

On we go

First Stabilize, then Optimize!

Posted on by Danny Jiménez⁩
Read 24 min

Are You Optimizing Your Project Before You Stabilize It?

Your project is chaos. Materials everywhere creating treasure hunts. Dirt and debris hiding quality problems. Safety hazards invisible under clutter. Deliveries arriving whenever suppliers feel like it creating too much inventory or not enough. Schedules nobody can see requiring twenty clicks to find anything. And you’re trying to implement lean. Run kaizen events. Eliminate waste. Optimize flow. But you can’t optimize chaos. If today performs at level five, tomorrow at level two, the next day at level seven, improving by one point means six, three, eight. You’re not progressing. You’re oscillating. Because without stability and standards creating consistent baseline performance, improvement efforts just move chaos around instead of eliminating it. And teams keep trying to optimize before stabilizing, wondering why continuous improvement never sticks when the problem is they’re building on shifting sand instead of solid foundation.

Here’s what most teams miss. Cleanliness isn’t for cleanliness sake. Organization isn’t for organization sake. Safety, deliveries, scheduling—none of these matter because they’re nice ideas. They matter because they create stability enabling optimization. Clean sites let you see quality problems, safety hazards, and capacity constraints hidden under clutter. Organized sites reduce motion, transportation, and treasure hunts enabling materials and information to flow. Safe sites create stable environments where workers focus on production instead of avoiding injury. Just-in-time deliveries create right inventory buffers—not too early, not too late, exactly what you need when you need it. Visible scheduling systems with workflow, trade flow, and logistical flow create rhythm teams can depend on instead of chaos they must navigate. These aren’t separate initiatives. They’re stability foundations that make optimization possible.

The challenge is understanding the S-curve of performance. At the bottom is bad—you’re out of business. Halfway up is okay, mediocre. Higher is good. At the top is perfect, outstanding. Most teams think climbing from bad to okay to good feels progressively easier. But gravity pulls equally hard whether you’re at okay or good. The only place where resistance decreases is at the top, striving for perfection where systems become stable enough that maintaining them requires less effort than creating them. When you strive for perfection, you get good. When you strive for good, you get okay. When you strive for okay, you get bad. When you strive for bad, you get out of business. And “good” is the most dangerous place because it feels acceptable, so teams stop improving right when stability would enable real optimization.

Why Stability Must Come First

Everything thrives in stability. Everything thrives with standards. You can’t have improvement without stable baseline performance to build on. You can’t have continuous improvement without standards defining what “normal” looks like so you can detect variation. People fight this because they love autonomy. They resist standards thinking freedom means doing things however they want. But that’s chaos disguised as flexibility. Real freedom comes from stable foundations enabling you to optimize upward instead of constantly firefighting downward.

Picture the difference. Unstable environment: today you perform at five, tomorrow at two, next day at seven. You improve by one point thinking you’re progressing. But six, three, eight isn’t progress. It’s oscillation. You’re working hard going nowhere because the baseline keeps shifting. Now picture stable environment performing consistently at six every day. You improve by one point. Now you’re at seven. Tomorrow you maintain seven. Next day you improve to eight. That’s actual progress built on stability enabling each improvement to stick instead of disappearing into chaos.

This is why Japan is lean. Rice culture created connectedness and respect for people. Island culture forced respect for resources because they can’t waste what they can’t replace. In America, we don’t respect resources or people. Walk into gas stations with disgusting bathrooms. Walk onto construction sites with port-a-potties without toilet paper. We blame everything on not having enough—enough workers, enough time, enough resources. But you don’t need more. You need to be more effective with what you have by stabilizing first instead of heading toward optimization before creating stable foundations.

What Stability Actually Means

Stability isn’t one thing. It’s multiple foundations working together creating consistent baseline performance:

  • Cleanliness. Not for its own sake—so you can see quality problems hidden under debris.
  • Organization. Not to look pretty—to reduce motion, transportation, and treasure hunts.
  • Safety. Not to check boxes—to create environments where workers focus on production, not avoiding injury.
  • Just-in-time deliveries. Not convenience—right inventory at right time preventing too much or too little.
  • Visible scheduling. Not documentation—single-page visibility showing workflow, trade flow, logistical flow within 30 seconds.
  • Personal organization. Not tidiness—capacity to manage responsibilities without chaos.
  • Team balance. Not nice-to-have—healthy teams capable of sustained performance.
  • Standards. Not restrictions—consistent baselines enabling you to detect variation and improve.

Why Cleanliness Creates Visibility

People think Jason wants cleanliness for cleanliness sake. Wrong. Cleanliness creates visibility. If it’s clean, you can see quality problems. Defects don’t hide under debris. If it’s clean, you can see safety problems. Hazards don’t disappear into clutter. If it’s clean, you can see capacity problems. Workflow constraints become obvious instead of invisible. Clean sites let you predict the future and anticipate problems like army generals on site. Dirty sites force you to focus on navigating chaos instead of optimizing flow.

This is why striving for perfection matters. Not “good enough” cleanliness. Perfect cleanliness. When you demand perfection, you get good. When you demand good, you get okay. When you accept okay, you get bad. And bad means out of business. Teams joke “we’ll strive for perfection” like it’s unrealistic. But perfection is the only target creating stability. Tell workers “I want it perfect because only perfection has less gravity. When you strive for perfection, you get good. I don’t want to waste your time. All I want is perfect. Just get it perfect and then we can take a break.” They understand. Perfect becomes the standard creating stability enabling optimization.

Organization works the same way. Not for its own sake. To reduce waste. Motion waste when workers walk unnecessarily. Transportation waste when materials move inefficiently. Treasure hunt waste when people can’t find what they need. Organized sites enable materials, information, and workers to flow because everything has a place and every place has everything needed. Disorganized sites force constant searching, moving, relocating—all waste preventing flow. You can’t optimize flow in disorganized chaos. You must organize first creating stability, then optimize flow building on that foundation.

The S-Curve: Why “Good” Is Dangerous

Picture an S-curve. Bottom is bad—you’re out of business. Halfway up is okay, mediocre. Higher is good. Top is perfect, outstanding. Gravity pulls the ball downward at every level. The effort required to stay at “okay” equals the effort required to stay at “good.” Both require constant pushing uphill. The only place where resistance decreases is at the top, striving for perfection where systems become stable enough that gravity stops pulling as hard.

This reveals why “good” is the enemy of great. Good feels acceptable. Projects running “well enough” create complacency. Teams stop improving because good seems sufficient. But good still requires enormous effort maintaining position. And the moment you stop improving at good, gravity pulls you toward okay. Then mediocre. Then bad. Then out of business. You can’t stop on the S-curve. Stop progressing and you’re automatically regressing. Like being on a treadmill. Stop going forward, you’re automatically going backward.

The only sustainable position is striving for perfection at the top where stability reduces gravity’s pull. Perfect cleanliness is easier to maintain than good cleanliness because standards are clear and deviations are obvious. Perfect organization is easier to maintain than good organization because everything has a place making misplacement visible. Perfect safety is easier to maintain than good safety because the culture enforces standards automatically. Perfection creates stability. Stability reduces effort. Less effort enables optimization. That’s the progression most teams reverse by trying to optimize before stabilizing.

What Happens When You Try to Optimize Chaos

Walk projects trying to implement lean without stability and you’ll see the pattern. They run kaizen events eliminating waste. But waste returns immediately because disorganized chaotic environments recreate it. They implement Last Planner System creating collaborative commitments. But commitments fail because unstable deliveries and invisible schedules make planning impossible. They try IPD building trust through collaboration. But trust erodes when chaos prevents anyone from delivering what they promised. They focus on advanced quality control. But quality problems hide under dirty disorganized conditions making control impossible.

All these optimization efforts fail because they’re built on unstable foundations. You can’t improve chaos. You must stabilize first creating consistent baseline performance, then optimize building on that stability. This is the Integrated Production Control System sequence: stabilize the environment (cleanliness, organization, safety, deliveries, scheduling), then optimize the system (lean tools, continuous improvement, waste elimination, flow creation). Teams reversing this sequence wonder why improvement never sticks when they’re building on shifting sand.

Think like Patton in the 1970s movie. He trained soldiers to act like soldiers, salute like soldiers, dress like soldiers, prepare like soldiers. They practiced like they wanted to play. This created discipline and stability enabling them to execute in chaos. Without that discipline, they’d have been overwhelmed. Construction is the same. You must create discipline through standards and stability before you can execute optimization in chaotic environments. Otherwise, chaos overwhelms every improvement attempt.

The System Failed You

Let’s be clear. When teams try optimizing before stabilizing, it’s not entirely their fault. The system failed by teaching lean as tools instead of teaching stability as foundation. Nobody showed that kaizen events fail without stable baselines to build on. Nobody explained that continuous improvement requires standards defining “normal” so variation becomes detectable. Nobody demonstrated that cleanliness, organization, safety, deliveries, and scheduling aren’t separate from optimization—they’re the stability enabling it. The system taught people to implement lean tools when they should have been creating stable foundations first.

The system also failed by not teaching that “good” is dangerous. Good feels acceptable creating complacency. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. But teams celebrating “good enough” stop improving right when stability would enable real optimization. And the moment you stop improving, gravity pulls you backward toward okay, mediocre, bad, out of business. Nobody teaches this. So teams achieve “good,” stop improving, and wonder why they’re sliding backward when the problem is they stopped on the S-curve instead of striving for perfection at the top.

The system fails by not teaching that you can’t blame lack of resources for chaos. Teams say “we don’t have enough workers, enough time, enough materials.” But you don’t need more. You need to be more effective with what you have through stability. Japan didn’t become lean through abundant resources. They became lean through scarcity forcing respect for resources and people. America resists stability through abundance creating waste. We think more resources solve problems when actually stability solves problems by enabling you to optimize what you have instead of constantly adding more to compensate for chaos.

The Challenge

Here’s your assignment. Stop optimizing before stabilizing. If your project isn’t remarkably clean, safe, organized with just-in-time deliveries and visible scheduling, stop the kaizen events and stabilize first.

Demand perfection in cleanliness, organization, and safety. Not “good enough.” Perfect. When you strive for perfection, you get good. When you strive for good, you get okay. When you strive for okay, you get bad.

Create visible scheduling systems showing workflow, trade flow, and logistical flow on single pages visible within 30 seconds. Stop the CPM madness. Get to Takt planning and visual flow schedules creating rhythm teams can depend on.

Build personal organization systems and balanced teams. Superintendents can’t optimize projects while drowning in chaos themselves. Stabilize individually, then stabilize teams, then stabilize projects.

Remember the S-curve. Good is the enemy of great. Stop improving at “good” and gravity pulls you backward. Only perfection at the top creates stability reducing effort and enabling sustainable optimization.

First stabilize, then optimize. Not the reverse. Create standards and stability establishing consistent baseline performance. Then build continuous improvement on that foundation creating projects that actually get better instead of oscillating between chaos and temporary fixes.

On we go.

FAQ

Why must you stabilize before optimizing?

You can’t improve chaos. If baseline performance oscillates between 2 and 7, improving by 1 point means 3 and 8—oscillation, not progress. Stability creates consistent baseline enabling each improvement to stick. Without stability, optimization efforts just move chaos around instead of eliminating it.

What does stability actually require?

Perfect cleanliness creating visibility. Perfect organization reducing waste. Perfect safety creating stable environment. Just-in-time deliveries creating right inventory buffers. Visible scheduling showing all three flow types. Personal organization and team balance. Standards defining “normal” so variation becomes detectable.

Why is “good” dangerous?

Good feels acceptable creating complacency. Teams stop improving at “good” when stability enabling real optimization requires striving for perfection. The S-curve shows gravity pulls equally hard at okay and good. Only perfection at the top creates stability where maintaining performance requires less effort.

Why strive for perfection instead of “good enough”?

When you strive for perfection, you get good. When you strive for good, you get okay. When you strive for okay, you get bad. Perfect standards create stability making deviations obvious and maintenance easier. “Good enough” creates unstable foundations where chaos constantly returns.

How do cleanliness and organization enable optimization?

Clean sites create visibility showing quality problems, safety hazards, capacity constraints hidden under clutter. Organized sites reduce motion, transportation, treasure hunts enabling materials and information to flow. You can’t optimize what you can’t see. Stability through cleanliness and organization makes problems visible enabling solutions.

Word Count: 1,998 words

 

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.

On we go

Lean Lessons Learned: 10 Steps to Success

Posted on by Danny Jiménez⁩
Read 19 min

10 Things Every Lean Thinker Wishes They Had Known from the Start

One of the most valuable things an experienced Lean practitioner can offer someone earlier in their journey is the honest answer to this question: what would you do differently if you had all the knowledge and experience you have today? Not the principles presented in their ideal theoretical form, but the specific shifts in thinking and practice that would have changed the trajectory of everything. Here are ten.

  1. Understand How the Wastes Create Each Other

The eight wastes are often taught through the DOWNTIME acronym and then promptly forgotten as a memorization exercise. The more valuable understanding is not the list; it is how the wastes interact. Inventory hides waste. When you cannot see what you have or how much of it is needed, the other wastes accumulate invisibly. Information is also inventory: too much information produced at once, overproduction of drawings, reports, or communication leads to misunderstanding, which leads to rework. One waste triggers the next. Learning to see those chains is more useful than memorizing the categories.

  1. Break the Batch Habit

The instinct in construction is to batch things: send RFIs in groups, pour all of zone three before moving on, hold design information until the full package is ready. Batch work feels efficient because it reduces the overhead of transitions. What it actually does is create waiting for the crews who need the information, for the trades who need the preceding work, for the decision-maker who receives a package of forty questions when ten of them are blocking work right now. Reducing batch sizes and moving toward uninterrupted flow is one of the most immediately impactful changes a team can make. Aim for one piece at a time. Ask how each element of your process can be released as soon as it is ready rather than held for the next batch point.

  1. Stop and Readjust When Something Unexpected Happens

Variation is not just an inconvenience. It is waste-producing, energy-draining, and productivity-destroying in ways that compound quickly. When something unexpected happens, the Lean response is to stop and readjust not to push through and absorb the variation into the plan as though it did not cost anything. Variation that is absorbed without acknowledgment shows up later as overrun, rework, or exhausted crews. Stopping to understand what caused the variation and how to prevent it from recurring is not a pause in production. It is production improvement in real time.

  1. Standardize Before You Improve

Variation is often a symptom of having no established standard. Where there is no standard, every person does the same task slightly differently, and the differences accumulate into unreliable outcomes. The most lasting improvements come after standardization not before it. The standard is the floor from which improvement is measured. Before asking how to do something faster or better, ask whether there is a consistent way it is done at all. Start there. A company that uses one cleaning product for 98% of its cleaning needs has solved a problem that is invisible until it is solved, and the reduction in waste from managing fewer products, making fewer decisions, and training to fewer procedures compounds over time in ways that are hard to overstate.

  1. Choose Quality Over Lowest First Cost

The contractor who selects the cheapest hinge for a cabinet door because it was a good deal this week is the same contractor who replaces those hinges for the next decade and still gets calls from customers seventeen years after leaving the business. Lowest first cost is almost never lowest total cost. Quality components, quality materials, quality trade partners, quality planning, these investments pay out across the full lifecycle of whatever is being built. The habit of choosing quality over price, consistently and deliberately, is one of the most durable changes a Lean thinker can make.

  1. Use Kanban as a Replenishment Trigger

The natural response to never wanting to run out of something is to order a lot of it and store it. The warehouse grows. The storage area fills. The time spent managing, moving, and locating that excess inventory eats into every productive hour. Kanban replaces that response with a system: a visual signal that triggers replenishment in small batches when the supply reaches a defined minimum level. Think about how a grocery store shelf works, nobody orders everything at once and stores it in the aisles. The shelf empties, the signal fires, the next batch arrives. That same logic applied to tools, consumables, materials, and information on a construction project eliminates the waste of excess inventory management without ever running out.

  1. Put Everything on Wheels

This one sounds almost too simple to be a Lean principle. It is not. Everything on wheels means everything is movable, tools, staging areas, material carts, workstations, desks. When conditions change on a project site, and they always change, the team that has organized its environment on wheels adapts in minutes. The team that has organized everything in fixed locations spends days managing the consequences of conditions that changed faster than the setup could accommodate. Mobility is a form of built-in flexibility that costs almost nothing to implement and pays back in every phase transition, every scope change, and every logistics adjustment the project requires.

  1. Design the Shop for Flexibility, Not for Today

How any workspace is laid out, a prefab shop, a project trailer, an office should be designed for adaptability, not for the current workflow. Standard components, simple connections, everything on wheels. The ability to reconfigure a workspace in an afternoon is worth more than optimizing a layout for the current work package. When the scope shifts, the workspace should shift with it rather than becoming an obstacle that slows the adaptation. Build nothing into the environment that cannot be undone quickly.

  1. Challenge Everything to Be Cut in Half

Toyota applies a powerful discipline: do not approach any process improvement unless you are attempting to cut the time or effort in half. Not improve it by ten percent. Cut it in half. The reason this target matters is that a ten-percent improvement invites incremental thinking small adjustments to the existing method. A fifty-percent reduction demands a different question: how is this actually being done, and what is in the method itself that is waste rather than value? The question exposes the assumptions the current method is built on. During construction of the World Expo Center in Kazakhstan, a team went from installing one window a day to fifteen. A manufacturing team challenged to increase from thirty windows a day to fifty reached one hundred and ten and is targeting two hundred. The reduction challenge forces genuine innovation rather than modest optimization.

  1. Culture Is the Lean Tool That Outlasts Every Other

Every other item on this list is a practice or a method. Culture is the environment in which all the others either flourish or wither. From 2000 to 2005, one perspective on Lean was as a management tool, a set of practices that produced efficiency. By 2005, the understanding had shifted: Lean is fundamentally about people. It is about tapping into the capacity that every person brings to their work, the knowledge, the ideas, the problem-solving instinct and creating an environment where that capacity is developed rather than consumed. Management’s role in a Lean culture is relentless training, teaching, and elevating people to become world-class problem solvers. When that becomes the orientation, everything changes. People do not believe in you until you believe in them. Invest in the team. The returns are not measurable on a quarterly basis, but they are real and they compound.

Here are the patterns that emerge when these ten shifts take hold together:

  • Problems surface earlier because the system is designed to make variation visible instead of absorb it.
  • Work moves without stops and starts because batching has been reduced to near-zero.
  • The environment adapts faster than conditions change because flexibility was designed in.
  • Quality is never traded for cost at the decision point, which removes an entire category of downstream problems.
  • The team gets better on every project because improvement is built into the daily culture rather than treated as a separate initiative.

Connecting to the Mission

Becoming a Lean thinker is not a destination. It is a laboratory, an experimental, curious, PDCA-driven mode of engaging with every process, every problem, and every opportunity to improve. The scientific method applied to construction: why are we doing this, what is actually happening, where does the waste originate, who is affected, how often does it recur? Always looking. Always learning. Always improving. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Start with the wastes. Eliminate the batches. Stop when variation appears. Standardize before you improve. Choose quality. Replenish on signal. Put everything on wheels. Design for flexibility. Challenge the time in half. Build the culture. And keep going because Lean thinking never ends.

On we go.

Frequently Asked Questions

Why is understanding how wastes interact more important than memorizing the eight wastes?

Because waste produces more waste. Inventory hides defects. Overproduction creates waiting. Rework generates motion and transportation. Seeing the chains between wastes is what produces genuine improvement knowing the names alone changes nothing.

What does “cut it in half” accomplish that a modest improvement target does not?

It forces a different kind of thinking. A ten-percent improvement can be achieved by adjusting the current method. A fifty-percent reduction requires questioning the method itself — which is where the real waste lives.

Why does Lean culture matter more than Lean tools?

Because tools without culture produce compliance at best. Culture produces the ownership, curiosity, and continuous improvement that make the tools work as designed. People who believe their improvement matters will keep improving. People executing tools they were told to use will stop when the pressure stops.

How does Kanban differ from conventional inventory management?

Conventional inventory management tries to predict future demand and stock accordingly, which produces excess. Kanban uses actual consumption as the trigger for replenishment producing only what is needed, when it is needed, in response to real demand rather than forecasted demand.

Why is putting everything on wheels a Lean principle rather than just a convenience?

Because flexibility is a production asset. When conditions change and they always do, a mobile environment adapts in minutes. A fixed environment creates days of disruption. Mobility designed in at the outset costs almost nothing and pays back across every phase transition and scope change.

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.

On we go

The A3 – ‘The idea that less is more’

Posted on by Danny Jiménez⁩
Read 17 min

A3 Problem Solving: The One-Page Tool That Changes How Teams Think

Mark Twain is credited with once observing that he did not have time to write a short letter, so he wrote a long one instead. The insight embedded in that observation is one of the most useful principles in Lean communication: brevity requires more thinking, not less. Reducing complex information to its essential elements forces clarity that length never does. A long report can hide a weak argument. A single well-constructed page cannot.

This is the foundation of the A3 method. The 11×17 format, one sheet, all key information, kept as visual as possible is not an arbitrary paper-size preference. It is a discipline that forces the author to do the hard work of understanding before communicating, and to distill that understanding into only what is essential. When John Shook praised the A3’s impact on Toyota’s operations, he was not talking about paper size. He was talking about the thinking process the format enforces, the collaboration it demands, and the mentorship relationship between Lean leader and Lean learner that it enables.

Why the Format Is Not the Point

The most common mistake teams make when they first encounter the A3 is treating it as a reporting template. They fill in the sections, produce a clean document, and consider the process complete. The document is not the point. The collaboration, the learning, and the depth of analysis that produced the document are the point. The A3 is the visible artifact of a thinking process. Its value is in the quality of the process, not the quality of the formatting.

This distinction matters because it changes how the A3 should be used. The sections of the A3 are not a form to complete sequentially and independently. They are a structured progression through a problem-solving conversation, one that requires collaboration with stakeholders, alignment at each step before proceeding, and the intellectual discipline to not jump to a solution before the problem is genuinely understood.

The Six Steps and What Each One Actually Does

The first step is background and current condition. Before any analysis begins, the team must establish clear agreement on what the problem actually is and how it is currently manifesting. This sounds obvious, but it is the step most often rushed or skipped in traditional problem-solving. Teams tend to jump to solutions because solutions feel like progress. Defining the problem feels like delay. But the A3 framework makes explicit what experienced Lean practitioners know: you cannot solve a problem you have not accurately defined. The background gives context. The current condition describes what is actually happening not what should be happening, not the preferred outcome, but the honest current state. Only when everyone involved is aligned on this definition can the A3 progress.

The second step is goals and targets. What does success look like? How will the team know when the problem has been solved? The goals and targets section connects the problem definition to the standard against which the solution will eventually be evaluated. On Target Value Design projects, this step should connect explicitly to the project’s conditions of satisfaction, the specific, agreed definitions of value that the customer and team established at the outset. If the problem is a design question, the goal is the design outcome that satisfies those conditions. If the problem is an operational failure, the goal is the performance standard that the countermeasure must restore.

The third step is analysis. This is where the discipline of the A3 is most visible. The analysis must be done collaboratively and visually not completed in a silo and presented as finished work. As the team explores options, their engagement shapes the analysis. New perspectives emerge. The understanding of the problem sometimes evolves as the analysis deepens. Choosing by Advantages is one framework that works especially well for design option A3s, but the method depends on the nature of the problem. What the A3 requires of any analysis method is that the essential inputs, the process, and the outputs are visible on the page distilled from whatever detailed models, financial analyses, or data sets exist behind the scenes into the key factors that actually drive the recommendation.

The fourth step is the proposal. Once the team is aligned on the analysis, a specific recommendation is made. Not three options for the owner to choose from. One, the option the team, having done the analysis, believes is the best answer given the project values, the customer’s needs, and the understanding developed through the A3 process. This is an important discipline. Presenting multiple options and asking the customer to choose transfers the decision without transferring the analysis. Presenting one recommendation with the analysis that supports it is genuine Lean leadership. There are times when the proposal is not accepted. The A3 methodology treats this as a valuable learning opportunity another cycle of PDCA that generates information the team did not have before.

The fifth step is the implementation plan. Once the proposal is accepted, the A3 documents the specific steps required to implement the countermeasure or design decision, what will happen, by when, and who is responsible. For a design element, this may be planning dates for documentation and estimating. For operational problems, it may be more detailed. The implementation plan closes the loop between the analysis and the action, ensuring that the A3 does not end at the recommendation but extends into actual execution.

The sixth step is follow-up. This is the check and adjust of PDCA, the step that most teams skip because it requires revisiting the A3 after implementation rather than treating the document as complete at the moment the recommendation is made. The follow-up asks: did the countermeasure actually solve the root problem? Did it deliver the expected value? If the results match the expectation, the A3 is validated and becomes a completed piece of organizational knowledge. If they do not match, the gap between the expected and actual outcomes becomes the new current condition, the starting point for the next A3 cycle.

Here are the signals that a team is using A3 correctly rather than as a form-filling exercise:

  • The problem definition section was debated and refined collaboratively before the analysis began.
  • Stakeholders who contributed to the analysis would recognize their perspective in the document.
  • The proposal section contains one recommendation, not a list of options.
  • The analysis section is visual enough that someone unfamiliar with the project can understand the reasoning.
  • A follow-up date is specified in the document and the team actually conducts the check.

Why the A3 Builds What Teams Actually Need

Beyond solving specific problems, consistent A3 practice builds three capabilities that every Lean organization needs and most struggle to develop: disciplined thinking, collaborative alignment, and mentorship.

Disciplined thinking comes from the constraint the format imposes. Every time a team member is forced to distill complex analysis into what fits on one page, they develop a sharper sense of what is essential and what is noise. Over time, this affects how they think about every problem not just the ones where they formally use an A3.

Collaborative alignment comes from the structure of the process. Because the A3 requires stakeholder engagement at the problem definition stage before the analysis even begins, the solutions that emerge carry the understanding and buy-in of the people who helped define the problem. That buy-in is what makes implementation reliable.

Mentorship is embedded in the format itself. When a Lean leader reviews a team member’s A3, they are not checking a report, they are engaging with a thinking process. The conversation that happens at each step of the A3 between the leader and the learner is where Lean thinking actually develops. The A3 makes that conversation structured, focused, and productive rather than open-ended and impressionistic.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. The A3 is not a form. It is a discipline. The document is evidence that the discipline was practiced.

On we go.

Frequently Asked Questions

What is the A3 problem-solving method?

It is a structured, six-step process for defining a problem, analyzing options, proposing a countermeasure, planning implementation, and following up on results, all captured on a single 11×17 sheet of paper that forces visual, essential communication.

Why does the A3 require collaboration rather than individual analysis?

Because alignment on the problem definition and the analysis is what makes the recommendation credible and the implementation reliable. Analysis done in a silo and presented as finished work bypasses the engagement that produces genuine buy-in.

Why should the proposal section contain one recommendation instead of multiple options?

Because presenting one recommendation with supporting analysis is Lean leadership, it transfers the team’s judgment to the decision-maker rather than transferring the decision without the analysis. Multiple options without a recommendation treat the decision as someone else’s problem.

What happens if the proposal is not accepted?

The A3 methodology treats rejection as a productive PDCA cycle. The reasons the proposal was not accepted become new information that improves the team’s understanding of the problem and the conditions of satisfaction.

What is the follow-up step and why do most teams skip it?

Follow-up is the check-and-adjust step of PDCA revisiting the A3 after implementation to verify whether the countermeasure actually solved the root problem. Most teams skip it because it requires returning to a document after the energy of the implementation has dissipated. But it is the step that validates the A3’s value and generates the learning that improves future A3s.

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.

On we go

A3 and the Learning Organization

Posted on by Danny Jiménez⁩
Read 18 min

A3 Knowledge Management: How to Keep Organizational Learning from Disappearing at Project Close

Here is a pattern that every construction organization has experienced. A project team works through a significant problem, a coordination challenge, a sequence failure, a supply chain disruption, a design coordination breakdown. They do the work of root cause analysis, develop a countermeasure, implement it, and confirm it works. The learning is real and valuable. And then the project ends, the team disperses to new assignments, and six months later a different project team encounters the same problem and starts from scratch because nobody connected them to what was already figured out.

This is one of the most expensive forms of waste in a project-based organization not the cost of the problem itself, but the cost of solving it repeatedly because the solution was never captured and made available. The A3 format solves the first part of this problem by creating a structured record of the analysis and the countermeasure. The organizational A3 management system solves the second part by making that record findable, accessible, and continuously improved across projects and teams.

The Problem at the Organizational Level

Most construction organizations are project-oriented rather than persistent. Teams form around projects, develop expertise and solve problems specific to that project’s context, and then dissolve. The knowledge lives in the people. When the people move, the knowledge moves with them or disappears. This is why so many construction organizations find themselves solving the same problems over and over again, and why onboarding new team members to organizational best practices is so difficult. There is no living system for capturing and transferring what has been learned.

A3s developed on projects represent a significant investment of thinking. Each one captures the current condition, the root cause analysis, the target condition, the countermeasure, and when the PDCA cycle is complete, the verification of whether the countermeasure worked. That is precisely the kind of structured, tested knowledge that other teams need. The challenge is getting it out of the project folder and into a system where someone facing a similar problem can actually find it.

Building the A3 Knowledge System

The simplest viable version of an organizational A3 library is a shared online spreadsheet, searchable, sortable, and filterable by keyword or category, with links to the source A3 documents and contact information for the team members who developed them. The contact information is critical. An A3 document captures the analysis, but the person who did the analysis can answer questions that the document does not address. Connecting searchers to authors is what makes the library a living knowledge network rather than a static archive.

The spreadsheet approach can begin immediately and grow in sophistication as the organization’s Lean capability develops. Purpose-built applications can replace the spreadsheet when the volume of A3s justifies the investment. But the principle matters more than the tool: every significant A3 developed on a project should be cataloged, indexed, and made available to the broader organization before the project team disperses.

Communities of Practice

The A3 library on its own is not enough. A searchable database only produces value when people search it and the habit of searching for prior knowledge before starting a new problem-solving effort requires cultivation. The most effective mechanism for building that habit is a community of practice: a group of Lean practitioners across projects and teams who meet regularly to share developments, ask questions, and collectively advance the organization’s Lean capability.

One approach that has worked particularly well is a combination of three elements. A shared digital log, the searchable A3 catalog provides the persistent knowledge base. An asynchronous communication channel, a Teams chat, a Slack workspace, or similar allows questions and observations to flow between the monthly meetings when something urgent or interesting surfaces. And a monthly web conference of sixty to ninety minutes provides the live interaction that builds relationships and creates the accountability to actually share and learn.

The monthly call agenda has a consistent structure: general updates, open questions and discussion, and key presentations on newly developed A3s. The presentations are the most important element. They give the A3 authors a forum to share what they learned and receive feedback from practitioners with different project contexts. They expose the rest of the community to new approaches and new problems. And they model the A3 method for team members who are newer to the practice seeing well-developed A3s and hearing the thinking behind them is one of the fastest ways to develop A3 capability.

Here are the signals that an organizational A3 knowledge system is functioning well:

  • Team members search the A3 library before starting a new problem-solving effort on a familiar type of problem.
  • The community of practice meeting has consistent attendance because participants find it genuinely useful.
  • A3s are revised and updated when newer project teams find that the original countermeasure did not deliver the expected results in a different context.
  • New Lean practitioners can find both A3 examples and A3 authors when they are learning the method.
  • The number of A3s in the library grows consistently across projects and teams rather than accumulating only when someone champions the effort.

Revision Management and PDCA Across Projects

One of the most powerful features of an organizational A3 library and one of the most underused is the ability to apply PDCA not just within a single problem-solving cycle but across the life of an A3 across multiple projects.

A project team encounters a problem that was addressed on a previous project. They find the A3 in the library. They review the analysis and the countermeasure. And they discover that the current state on their project does not quite match the conditions in which the original countermeasure was developed. The solution that worked in a healthcare facility may not translate directly to a data center. The approach that worked in a climate with predictable weather may need adjustment in a region with different seasonal patterns.

Rather than discarding the prior A3, the new team updates it, adding fresh analysis for the current conditions, documenting where the original solution applies and where it does not, and potentially creating an alternate countermeasure for the new context while preserving the original countermeasure for cases where the original conditions recur. The A3 is now richer than it was before. The organizational knowledge base has been improved by the encounter between the prior solution and the new conditions.

This is PDCA applied to knowledge itself, plan the countermeasure, do it on the first project, check whether it worked on subsequent projects, adjust the A3 when the results warrant it. Over time, the A3s in the library become increasingly robust documents that represent the organization’s collective tested wisdom rather than individual project analyses.

What Toyota Understood

This organizational approach to A3 knowledge management is part of what made the A3 system what some have called Toyota’s secret. It was not just that individual engineers could solve problems using the A3 format, it was that Toyota built the organizational infrastructure to capture, share, and continuously improve the knowledge generated by those problem-solving efforts across the entire company. Each A3 represented individual learning. The library of A3s represented organizational intelligence. And the communities of practice that kept the library alive and growing represented the cultural commitment to continuous learning that made Toyota’s production system consistently better than any competitor could replicate by copying the tools alone.

Construction organizations that build their own version of this system, a library, a community, a culture of searching before starting are building the same advantage in their context. The problems construction projects face is not infinitely varied. Many of the same challenges recur across different projects, different geographies, and different client types. Every problem solved once and captured well is a problem that does not have to be solved from scratch the next time.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. The A3 format captures what was learned. The organizational system is what makes that learning compound across time.

On we go.

Frequently Asked Questions

What is an organizational A3 library and why does it matter?

It is a searchable catalog of A3 documents developed across projects, with links to the source documents and contact information for the authors. It matters because project-based learning disappears when projects end unless there is a system to capture and make it accessible to future teams.

What is the minimum viable version of an A3 knowledge system?

A shared online spreadsheet indexed and filterable by keyword or category, linked to the source A3 documents and the contact information for team members who can answer questions about them. It can be built immediately and does not require purpose-built software to start.

What is a community of practice in the context of A3 management?

A regular gathering of Lean practitioners across projects and teams who share new A3 developments, ask questions, and collectively advance the organization’s capability. The most effective format combines a persistent digital catalog, an asynchronous communication channel, and a monthly live meeting.

How does PDCA apply to A3s across multiple projects?

A newer team that uses a prior A3 may find that the original countermeasure does not fully apply in their context. They update the A3 with fresh analysis and an alternate recommendation, improving the document’s value for future teams. The A3 becomes a living record that gets more accurate and more useful with each iteration.

Why does the contact information of A3 authors matter as much as the document itself?

Because the document captures the analysis but the author can answer questions the document does not address. Connecting searchers to the people who did the thinking is what makes the library a knowledge network rather than a static archive.

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.

On we go

A3 – Other Uses

Posted on by Danny Jiménez⁩
Read 18 min

Beyond Problem Solving: Three Ways the A3 Format Is Changing How Construction Teams Communicate

The A3 report is one of the most powerful tools in the Lean construction toolkit, and most teams that have encountered it know it primarily as a problem-solving format. A structured, single-page approach to capturing the current condition, the root cause analysis, the target condition, and the countermeasure, all on one 11×17 sheet of paper. The discipline of fitting the most important information onto a single page is not a constraint. It is the point. It forces clarity, reveals gaps in thinking, and makes the analysis accessible to everyone who needs to understand it rather than buried in a report that only the author can navigate.

But the A3 format has been finding its way into other applications in Lean construction, and each one carries the same essential discipline: present only what is most important, in a format that can be understood quickly, and let that constraint force better thinking about what actually matters.

The Problem This Solves

Before getting into the three applications, it is worth naming what they all share as a common target. Construction projects generate enormous amounts of reporting status updates, proposals, lesson-learned documents, phase retrospectives. Most of that reporting is shaped by tradition rather than by the question of what the reader actually needs. Status reports are structured around what the project team has done rather than what the decision-maker needs to know. Proposals contain pages of boilerplate that exist because they have always been included, not because they serve the selection process. Retrospective outputs get filed in a shared drive and rarely influence the next project.

The A3 format challenges all of that by imposing a constraint that forces the author to make a decision: if I can only put the most important information on one page, what is actually most important? That decision is itself a form of analysis. The act of reducing to what is essential is where the thinking happens.

A3 Project Dashboards

The project dashboard is one of the most natural extensions of the A3 format. Like a dashboard in a car, the project dashboard exists to tell the driver in this case the project team, the leadership, and key stakeholders, the current state of the project at a glance. Not everything that has happened. Not a comprehensive account of all activities. The critical indicators that show whether the project is healthy, what requires attention, and where the warning lights are.

A well-designed A3 project dashboard makes these things visible without requiring anyone to sit through a meeting or read a multi-page report to get oriented. Milestones and their current status. Percent plan complete trend over recent weeks. Buffer consumption for the current phase. Any open red flags that warrant further investigation. Key procurement dates against the production plan. The dashboard is a quick snapshot that confirms what is on track and immediately draws the eye to what is not.

The discipline of fitting all of that onto one 11×17 page forces the team to decide what matters most in terms of project health. It also forces a conversation about what the right leading indicators are not what is easy to report, but what is actually informative about where the project is headed. That conversation is valuable independent of the dashboard that results from it.

What makes the A3 dashboard different from a traditional status report is not just the size, it is the audience orientation. A traditional status report is built around what the project team has produced. An A3 dashboard is built around what the stakeholder needs to know. The shift in perspective changes the content of the communication significantly.

A3 Proposals

The application of the A3 format to proposals is less common but potentially one of the most transformative shifts available to the Lean construction community. Traditional proposals for Lean and IPD projects often contain substantial boilerplate pages of standard organizational history, templated project approach descriptions, credential lists that look more or less the same from firm to firm. The information that actually differentiates one team from another can be buried in forty pages of content that exists because the proposal template requires it.

An A3 proposal or a small set of A3 pages, such as one for the team and one for the project approach forces the proposing team to make a genuine decision: what does this client actually need to know from us, specifically for this project, that would inform their selection? The boilerplate disappears because there is no room for it. What remains is the essentials, chosen deliberately.

From the client’s perspective, receiving an A3 proposal is itself informative. The elements the proposing team decided were essential enough to include on a single page reveal how that team thinks, what they prioritize, how they communicate, whether they have genuinely understood the project’s specific context or are presenting a generic version of themselves. A team that can produce a clear, compelling A3 proposal is demonstrating exactly the discipline that produces clear, well-run projects.

Some progressive owners have extended the same discipline to their RFPs issuing the project request in A3 format to impose essentialism on themselves. What are we actually looking for from a project team? If we can only express it on one page, what belongs there? The constraint surfaces clarity on both sides of the selection process.

A3 Retrospectives

The A3 problem-solving format is naturally suited to specific retrospectives, cases where a particular outcome did not meet expectations and the team is analyzing root cause and developing a countermeasure. The structured A3 format guides that analysis from current condition through root cause through target condition through countermeasure, and produces a document that captures both the analysis and the action.

General retrospectives conducted at phase transitions, at project completion, or after user occupancy have a different character. They are broader surveys of what worked, what did not, and what should change. The outputs can be more diffuse. And that diffuseness is often what causes retrospective learnings to disappear into shared drives and never influence another project.

Capturing the outputs of general retrospectives in an A3 format serves the same function that the format always serves: it imposes a discipline of reduction that forces the team to identify what actually matters most from the retrospective conversation. If the key findings from this phase review had to fit on one page, what would they be? That question produces a more actionable document than the meeting notes alone.

The A3 retrospective output also serves as a natural bridge to more specific A3 development. An open question or a lesson learned identified in the general retrospective might become the starting current condition of a specific problem-solving A3, the input for a more formal analysis that produces a countermeasure the organization can standardize.

Here are the signals that A3 thinking is spreading productively across a project team:

  • Status reporting has shifted from comprehensive activity logs to focused red-flag identification.
  • Proposals are being built around what the client needs to know rather than around what the template requires.
  • Retrospective outputs are captured in a format that can be shared and referenced, not just discussed.
  • Team members can describe the most important information about any topic in one page or less.
  • The constraint of the format is experienced as a thinking tool rather than a presentation limitation.

Why the Format Is the Practice

What all three applications share is the same discipline that makes the original A3 problem-solving format valuable: the constraint of the page forces a decision about what is essential. That decision is where the thinking happens. A status report that fits on one page is not a shorter version of a longer report; it is a different kind of thinking about what project health actually looks like. A proposal that fits on two A3 pages is not a condensed version of a forty-page submission, it is a deliberate articulation of what this team believes this client actually needs to understand.

The A3 format in any of its applications is a visual management tool. It makes thinking visible, accessible, and comparable across time. When a project team develops a series of A3 dashboards over a project’s life, the dashboards become a visual record of how project health evolved, a kind of visible production log that no traditional reporting structure produces. That visibility is what Lean production systems are built on: see as a group, know as a group, act as a group.

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

The A3 format is not a paper size. It is a discipline. And the discipline applies wherever clear thinking needs to be shared efficiently.

On we go.

Frequently Asked Questions

What makes the A3 format valuable beyond problem solving?

The format’s constraint fitting the most important information on one-page forces essential decision-making about what actually matters. That discipline applies to any communication purpose: dashboards, proposals, retrospectives, or any situation where clarity and accessibility matter more than comprehensiveness.

What should a project dashboard in A3 format include?

The key indicators of project health: milestone status, PPC trend, buffer consumption, red flags requiring attention, and critical procurement dates. The test is whether a stakeholder can understand the project’s current state in thirty seconds without asking questions.

Why is the A3 proposal format useful for both proposers and clients?

For proposers, it forces a genuine decision about what this specific client actually needs to know. For clients, the elements the proposer chose to include reveal how that team thinks and whether they have understood the project’s specific context.

How does the A3 format improve retrospective outputs?

By forcing reduction to what is most important. The constraint produces a document that can be shared, referenced, and acted on rather than meeting notes that get filed and forgotten. It also naturally surfaces specific open questions that can seed more formal A3 problem-solving.

Is the A3 format limited to paper or physical documents?

No. The discipline of the format fitting the most essential information into a constrained, visually clear layout applies equally to digital formats, shared screens in planning rooms, or printed documents posted on site walls.

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.

On we go

Why You Should Start with the 5 Where’s Before the 5 Whys

Posted on by Danny Jiménez⁩
Read 19 min

Why Most Problem-Solving in Construction Goes Nowhere and What to Do Instead

When something goes wrong on a construction project, the instinct is to find out who did it and fix the symptom. The schedule slipped who missed the handoff? The quality was rejected whose crew did the work? The materials were wrong, who placed the order? Those questions feel productive because they produce answers. They are almost never solving the actual problem. They are identifying the person who happened to be standing at the place where the symptom appeared, which is usually nowhere near the place where the problem actually started.

Taiichi Ohno, the manufacturing genius behind the Toyota Production System, the person most responsible for developing the Lean thinking that construction is now trying to apply, understood this so deeply that he built his entire teaching practice around a single discipline: stand in the place where the problem is, observe what is actually happening, and ask why. Not who. Why. And before you ask why, ask where. Five times, if necessary, until you are standing at the actual point of cause.

The Ohno Circle

The story of the Ohno circle is worth knowing in full because it captures something that rarely exists in modern construction culture: the willingness to invest deep time in genuine observation. Ohno would stand in a circle drawn on the factory floor, watch what was happening, and keep asking why, sometimes for hours. He would bring a student with him, a group leader, which is the equivalent of a superintendent in construction and leave them in the circle to observe while he stepped away. He would return later and ask what they had seen. He would do this multiple times across an entire day, expecting each return to produce a deeper analysis.

On one occasion, according to Jeff Liker, Ohno forgot about a student at the end of the day. The student stayed in the circle, overnight, into the next day until his wife called the factory and blasted Ohno for the oversight. There is something in that story that is both amusing and instructive. The student stayed because the culture demanded deep observation. The problem with suggesting that approach to most superintendents today is that ten minutes of deliberate observation in one place feels like the most unproductive thing imaginable when there are thirty things demanding attention simultaneously. The irony is that those thirty demands often persist precisely because nobody has stood still long enough to find their actual origin.

What Happens When We Skip the “Where”

Here is the pattern that plays out on nearly every construction project where problems are solved at the symptom level. A quality defect appears in zone three. Someone is identified. A correction is made. The correction is documented. And three weeks later, the same type of defect appears in zone seven, because the condition that produced it somewhere upstream in the process, weeks before the defect became visible was never found and never changed. The symptom was eliminated. The point of cause was never reached.

This is not just inefficient. It is actively harmful. By eliminating the symptom without finding the point of cause, the connection to the source of the problem is severed. The problem will return. And when it returns, it will return in a condition that is harder to trace back to its origin because the previous correction created the impression that the problem was solved. In safety terms, this is how serious incidents develop: through a series of near-misses that were resolved at the symptom level, each one quietly worsening the underlying condition.

The System Failed the Problem-Solver

Most people in construction were never taught disciplined problem-solving. They were taught to identify what went wrong, fix it, and move on. The pace of construction projects, the daily urgency of handoffs, deliveries, inspections, and schedule pressures, makes that approach feel like the only viable one. There is no time to stand in a circle and observ  e for two hours. There is barely time to get through the morning huddle.

But that time pressure is itself a symptom. Projects that are chronically too busy to solve problems at the root level are projects that will keep encountering the same problems, forever, because the system was never changed. The busyness that prevents root cause analysis is often generated by the problems that root cause analysis would have prevented. The system built the cycle. The people inside it are running as fast as the system allows.

5 Wheres Before 5 Whys

Here is the discipline that changes everything about how problem-solving works. Before asking why five times, ask where five times. Where did this problem come from? Where are the instructions that should have prevented it? Where in the process did the actual cause originate? Where is the answer detailed? Where does the system break down that allowed this to reach the point where it became visible?

The 5 Whys is a powerful tool. But it only produces useful results when it is applied at the point of cause, the actual location in the process where the problem originated not at the point of discovery, which is usually much further downstream. Most problem-solving in construction applies the 5 Whys at the point of discovery and calls the answer a root cause. What it actually found is the most recent place the problem became impossible to ignore.

Ohno’s lesson to Hayashi makes this precise. Hayashi identified a serious quality problem in assembly and was ready to start solving it. Ohno stopped him and demanded to know where the problem had actually occurred. Hayashi realized the defective part might have originated in how it was manufactured at an earlier stage. Ohno asked why he was standing in assembly if the problem was in manufacturing. Then, when Hayashi moved to go upstream, Ohno stopped him again because the assembly problem still had to be contained before the root cause upstream could be addressed. Two separate actions: contain the symptom where it is visible, then trace back to the actual origin and change the condition there.

That sequence is the complete problem-solving discipline: identify the symptom, contain it at the point of discovery, then find the point of cause by asking where the problem originated and only then ask why the system allowed that condition to exist.

Here are the signals that a project team is doing symptom-solving rather than root cause problem-solving:

  • The same type of problem reappears in different zones after being corrected once.
  • Problem-solving conversations begin with identifying who is responsible rather than where the problem originated.
  • Corrections are made without any change to the system condition that produced the defect.
  • Lessons learned are documented but the process that generated the lesson remains unchanged.
  • The team is too busy managing recurring problems to have time for structured problem-solving.

Source Management

Ritsuo Shingo, son of Shigeo Shingo, teaches a principle he calls source management. The meaning is the same as what Ohno was teaching through the circle: we must get to the source, and only at the source can real change happen. Dealing with what appears to be the problem at the point of discovery, downstream from where it originated is exhausting, demoralizing, and ultimately futile. It is a waste that Lean practitioners sometimes call a waste of life: wasting time and energy solving problems that will return because the actual source was never found and never changed.

It encompasses all the other wastes and exceeds them. You can eliminate the eight operational wastes on a project and still be destroying value if the team is spending its capacity repeatedly addressing the same symptoms instead of finding their origin. The waste of life is what happens when problem-solving looks productive on the surface and produces nothing durable underneath.

Connecting to the Mission

At Elevate Construction, the system-first diagnostic is foundational. When something goes wrong on a project, the first question is not who failed. It is where in the system the condition that produced the failure was allowed to exist. That framing protects the people and produces better outcomes. It also requires the discipline that Ohno spent his career demanding from his students: the willingness to observe carefully, trace problems to their origin, and change the system at the source rather than the symptom.

That discipline is what separates a Lean organization from an organization that is performing Lean. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Ask the 5 Wheres before the 5 Whys. Stand at the point of cause before asking why. Contain the symptom. Change the source. Then the improvement holds.

On we go.

Frequently Asked Questions

What is the difference between the point of discovery and the point of cause?

The point of discovery is where a problem becomes visible where the defect is found, where the delay is noticed, where the complaint is made. The point of cause is where the problem actually originated, which is almost always upstream in the process from where it was discovered. Solving the problem at the point of discovery without reaching the point of cause only eliminates the symptom.

Why ask the 5 Wheres before the 5 Whys?

Because the 5 Whys only produces useful root cause analysis when it is applied at the point of cause. Asking why at the point of discovery produces an explanation for the symptom, not the source. The 5 Wheres narrows the problem from a vague symptom to a specific location in the process where the investigation can begin.

Why does eliminating a symptom make the underlying problem worse?

Because it severs the visible connection between the symptom and its cause. When the symptom disappears, the problem appears solved. The underlying condition continues unchanged, returning later in a form that is harder to trace and often more serious particularly in safety contexts.

What is “source management” as taught by Ritsuo Shingo?

Source management is the principle that real, lasting change only happens at the source of the problem not at the point where it becomes visible. It requires tracing problems upstream to their origin and changing the system condition that allowed them to develop.

How does this connect to the system-first philosophy in Lean construction?

Lean construction treats almost all failures as system failures rather than people failures. When a problem occurs, the first diagnostic question is what in the system allowed this condition to develop. The 5 Wheres operationalizes that diagnostic by directing the investigation upstream to the system origin before the 5 Whys asks why the system failed.

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.

On we go

Facing Your Fears!, Feat. Brandon Montero

Posted on by Danny Jiménez⁩
Read 26 min

If You Keep Giving Up, Your Why Isn’t Big Enough

You quit when things get hard. The diet lasts two weeks. The business idea fades after the first obstacle. The training feels uncomfortable so you stop attending. The relationship requires difficult conversations so you avoid them. The fitness goal demands consistency so you make excuses. And you wonder why life doesn’t deliver remarkable experiences when the problem is your why isn’t big enough to overcome discomfort. Eric Thomas says it clearly: if you keep giving up, it’s because your why is not big enough. Because if you quit today and nobody gets hurt, nobody misses anything, your why is too weak. When you want to succeed as badly as you want to breathe, that’s when you become successful. But most people’s why is comfortable, not compelling. Safe, not sacred. Convenient, not crucial. And convenience-level why creates convenience-level effort producing convenience-level results that never transform anything.

Here’s what most people miss. Everything is on the line. Not someday. Not eventually. Right now. Whether you believe in afterlife or not, whether God exists or not, plug in the math on any scenario and you’re wasting time if you’re not living fully. If this is all you get and you cease to exist after death, that makes every moment more important. You only have 40 years left. Make them count. Fly to Hawaii. Build that business. Live your purpose. If there’s eternity, why waste these wonderful bodies and this adversity that springboards you to higher existence? Either way, there’s never a scenario where fishing for three years straight makes you happy. People think they want retirement doing nothing. But they die within three months or wither away miserable. The week fishing was great because of the promise of returning to work and grinding. The promise of progress. Without that, humans deteriorate because we’re eternal beings designed for growth, not stagnation.

The challenge is facing fears now instead of running from weakness. Robert Louis Stevenson said you cannot run away from weakness. You must fight it out or perish. And if that be so, why not now and where you stand? Your fears don’t disappear with time. They don’t shrink through avoidance. They grow. They multiply. They control you until you face them directly saying “I see you there, I’m still moving forward, there’s nothing you can say that can stop me because I see my why.” The people who transform are people who stop running, plant their feet, and fight weakness out exactly where they stand. Not someday. Not when conditions improve. Now. Because if not now, when? And if not here, where?

What’s Actually on the Line

When you ask “what’s on the line,” the answer is everything. Literally all of it. People minimize this to avoid discomfort, but reality doesn’t care about your comfort:

  • Your one life and whether you live it remarkably or waste it comfortably.
  • Your purpose and whether you fulfill it or abandon it for easier paths.
  • Your family and whether you protect them through systems or sacrifice them through chaos.
  • Your health and whether you build it through discipline or destroy it through convenience.
  • Your relationships and whether you strengthen them through growth or break them through stagnation.
  • Your career and whether you develop mastery or settle for mediocrity.
  • Your potential and whether you discover what you’re capable of or die wondering.
  • Your legacy and whether people remember you transformed lives or wasted opportunities.
  • Your children’s example and whether they see courage or complacency modeled.
  • Your eternity (if you believe in it) and whether you prepared for it.
  • Your time remaining and whether each year counts or disappears into comfort.
  • Everything that matters to you and whether you fight for it or let it slip away.

Why Your Why Must Be Bigger Than Your Comfort

Picture Eric Thomas’s message. When you want to succeed as badly as you want to breathe, that’s when you become successful. Not when you want it casually. Not when you prefer it generally. When you need it desperately. When quitting means people you love suffer. When giving up betrays everything sacred to you. That’s the level of why that overcomes obstacles instead of retreating from them. Comfort-level why says “I’d like to be healthier.” Compelling why says “my kids need me alive and present for their weddings, not dead from preventable disease at 55.”

Brandon Montiero’s team does Friday morning workouts together. Circuit training. Yoga. Meditation. Construction dudes meditating. Creating peaceful, cohesive, awesome environments where like-minded people draw into circles supporting each other. That doesn’t happen with weak why. That requires why strong enough to prioritize connection over convenience, growth over comfort, and transformation over tolerance of mediocrity. The workout isn’t the point. The bond is. The shared commitment to becoming better together. That’s what compelling why creates.

Boot camp participants who stop smoking. Six people now. Still not smoking. Because their why became bigger than their addiction. The guy who lost six pounds because his why overcame his eating habits. The people who dance with their kids now because their why includes being present, playful fathers instead of distant providers. Nelson’s kid saying “I freaking rock” because dad came home from boot camp different, more engaged, more alive. That’s what happens when why grows bigger than comfort. Transformation cascades through every area because the foundation shifted from convenient to compelling.

What’s your why? If you keep giving up, it’s not big enough. If you quit when things get hard, it’s too weak. If obstacles stop you, it’s insufficient. Find why that makes quitting impossible. Find why that makes your children’s futures depend on your success. Find why that makes other people’s lives improve through your growth. Find why where quitting today means people you love suffer. That’s the size of why that overcomes anything.

You Cannot Run from Weakness—Face It Now

Robert Louis Stevenson’s quote captures the non-negotiable reality: you cannot run away from weakness. You must fight it out or perish. And if that be so, why not now and where you stand? Your fears don’t shrink through avoidance. They don’t disappear with time. They grow. They multiply. They control you increasingly until you face them directly. The person who runs from weakness finds it chasing them everywhere, showing up in different forms, destroying different areas of life until they finally turn and fight.

The person who faces weakness now, where they stand, says “I see you there. I acknowledge you exist. And I’m moving forward anyway because my why is bigger than my fear.” The fear doesn’t vanish. Brandon mentioned this clearly: fears never go away completely. But you get right in front of them and deal with them. And although they’re never fully gone, you say “I see you there, I’m still moving forward, there’s nothing you can say that can stop me because I see my why.”

This is why boot camps work. Not because Jason and Brandon eliminate fear. Because they help people face fear directly, push through it into learning zones, and discover capabilities they didn’t know they had. The superintendents who show up nervous, resistant, uncertain. Then get direct feedback pushing them into fear zones. Then push through fear into learning. Then discover growth on the other side. Then leave different, dancing with their kids, losing weight, stopping smoking, showing up for families, leading projects better. Not because fear disappeared. Because they faced it and moved forward anyway.

The Noticer: Emotional Awareness Before Reaction

Brandon teaches a powerful technique for facing fears and managing emotions. Introduce a “noticer” that observes your emotions before you react to them. When you feel anger rising, can you notice “I’m feeling angry” before exploding? When anxiety builds, can you observe “I’m worried about this deadline” before snapping at your kids? When fear emerges, can you recognize “I’m afraid of failing” before retreating to comfort?

The noticer is you. But it’s the aware part of you that observes emotions instead of being controlled by them. Most people go right from feeling to reaction. They feel angry and immediately yell. They feel afraid and immediately quit. They feel anxious and immediately avoid. No space between stimulus and response. No awareness of why the emotion emerged. Just immediate reaction creating damage they regret later.

But if you can introduce that one-second pause, that noticer saying “I notice I’m feeling this emotion, why is that happening?” you create space for choice. Your kid tells an amazing joke. Normally you’d dismiss it because you’re stressed about work. But the noticer says “I’m really worried about this deadline at work, and that’s why I don’t want to listen right now.” The awareness lets you choose. You can say “Actually, this deadline doesn’t matter more than my kid’s joy. Let me listen fully to this joke and deal with the deadline later.”

Practice this with all emotions, not just big ones. When little feelings creep up throughout the day, introduce the noticer that says “Hey, you just changed course with your emotions. I noticed it. This is why.” The practice builds awareness. And awareness creates choice. And choice creates the ability to act according to your why instead of reacting according to your emotions.

Signs Your Why Isn’t Big Enough

How do you know if your why needs strengthening? Check yourself honestly:

  • You quit when things get uncomfortable or hard.
  • You make excuses protecting you from discomfort.
  • You give up on goals after initial obstacles.
  • Nobody gets hurt if you quit today—your why affects only you.
  • You prefer comfort over growth when choosing between them.
  • You avoid difficult conversations required for transformation.
  • You retreat from fear instead of facing it directly.
  • You waste time on activities that don’t serve your purpose.
  • You tolerate mediocrity instead of demanding excellence from yourself.
  • You haven’t defined what’s actually on the line if you fail.
  • You can’t articulate who suffers if you don’t succeed.
  • Your goals feel like preferences, not sacred responsibilities.

The System Failed You

Let’s be clear. When people’s why is too weak to overcome obstacles, it’s not entirely their fault. The system failed by teaching that comfort is the goal instead of teaching that purpose is the prize. Nobody showed that compelling why comes from understanding what’s actually on the line. Nobody explained that everything matters—your life, your purpose, your family, your legacy, all of it. Nobody demonstrated that weak why creates weak effort creating weak results. The system assumed people would naturally develop strong why when actually most people drift through life with convenience-level motivation producing convenience-level outcomes.

The system also failed by not teaching that you can’t run from weakness. You must fight it out or perish. And if that be so, why not now and where you stand? If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. The system taught people to avoid fear as weakness when actually facing fear creates strength. And teams never taught this keep running from weakness until it catches them, destroys them, and makes them wonder what happened when the answer was they never stood their ground and fought.

The system fails by not teaching emotional awareness before reaction. The noticer technique isn’t common knowledge. Most people go straight from feeling to reaction without awareness of why emotions emerged or choice about how to respond. This creates damage in relationships, careers, and health that awareness would prevent. But nobody teaches this. So people react automatically, create messes, and wonder why life feels chaotic when the answer is they never learned to notice emotions before being controlled by them.

The Challenge

Here’s your assignment. Identify your why. Write it down. Be specific. Who suffers if you quit? Who benefits if you succeed? What’s actually on the line? If your why is weak (nobody gets hurt if you quit today), strengthen it. Find purpose bigger than personal comfort. Find responsibility to people you love. Find sacred obligation you can’t betray.

Face one weakness this week. Don’t run from it. Plant your feet. Fight it out. Say “I see you there, I’m still moving forward, there’s nothing you can say that can stop me because I see my why.”

Practice the noticer. When emotions emerge, introduce that one-second pause. Notice what you’re feeling. Ask why that emotion appeared. Choose how to respond instead of reacting automatically. Build awareness creating choice creating control.

Stop wasting time. Whether there’s eternity or not, whether God exists or not, everything is on the line right now. Your one life. Your purpose. Your family. Your potential. All of it. You don’t have 40 years to fish doing nothing. You have 40 years to build remarkable legacy through growth, contribution, and transformation.

You cannot run away from weakness. You must fight it out or perish. And if that be so, why not now and where you stand?

When you want to succeed as badly as you want to breathe, that’s when you become successful. Find that level of why. Face your fears. Live remarkably.

On we go.

FAQ

How do you know if your why is big enough?

If you keep giving up when things get hard, your why isn’t big enough. If nobody gets hurt when you quit today, your why is too weak. Compelling why makes quitting impossible because people you love depend on your success. Convenience-level why creates convenience-level effort producing convenience-level results.

What does “everything is on the line” actually mean?

Your one life, your purpose, your family, your relationships, your health, your career, your potential, your legacy, your children’s example, your time remaining—literally all of it. Whether there’s eternity or not, this life matters. Wasting it on comfort instead of living it remarkably means losing everything that could have been.

How does the “noticer” technique work?

Introduce one-second pause between feeling and reaction. When emotions emerge, notice “I’m feeling angry/afraid/anxious” before acting. Ask why that emotion appeared. This creates space for choice. You can respond according to your why instead of reacting according to your emotions automatically.

Why can’t you run from weakness?

Weakness doesn’t shrink through avoidance. It grows. It multiplies. It controls you increasingly until you face it. Robert Louis Stevenson said you must fight it out or perish. And if that be so, why not now and where you stand? Facing weakness directly is the only path to freedom from it.

What makes boot camps effective for transformation?

They push people into fear zones, help them push through into learning zones, and prove they’re capable of more than they believed. People leave different—dancing with kids, losing weight, stopping smoking, showing up for families. Not because fear disappeared, but because they faced it and moved forward anyway.

Word Count: 1,997 words

 

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.

On we go

    Related Books

    The First Planner System: The Project Planning System for Executives, Project Managers, and Superintendents in Pre-construction - Book 2
    Get Book
    Pull Planning For Builders: How to Pull Plan Right, Respect People, and Gain Time (The Art of the Builder)
    Get Book
    The Ten Improvements to Production Planning: What Lean Builders Can Do To Improve Short Interval Planning (The Art of the Builder)
    Get Book

    Related Books

    The First Planner System: The Project Planning System for Executives, Project Managers, and Superintendents in Pre-construction - Book 2
    Get Book
    Built to Fail: Why Construction Projects Take So Long, Cost Too Much, And How to Fix It
    Get Book

    Related Books

    The First Planner System: The Project Planning System for Executives, Project Managers, and Superintendents in Pre-construction - Book 2
    Get Book
    The 10 Myths of CPM: How The Critical Path Method Systematizes Disrespect for People
    Get Book
    Calumet "K"
    Get Book

    faq

    General Training Overview

    What construction leadership training programs does LeanTakt offer?
    LeanTakt offers Superintendent/PM Boot Camps, Virtual Takt Production System® Training, Onsite Takt Simulations, and Foreman & Field Engineer Training. Each program is tailored to different leadership levels in construction.
    Who should attend LeanTakt’s training programs?
    Superintendents, Project Managers, Foremen, Field Engineers, and trade partners who want to improve planning, communication, and execution on projects.
    How do these training programs improve project performance?
    They provide proven Lean and Takt systems that reduce chaos, improve reliability, strengthen collaboration, and accelerate project delivery.
    What makes LeanTakt’s training different from other construction courses?
    Our programs are hands-on, field-tested, and focused on practical application—not just classroom theory.
    Do I need prior Lean or takt planning experience to attend?
    No. Our programs cover foundational principles before moving into advanced applications.
    How quickly can I apply what I learn on real projects?
    Most participants begin applying new skills immediately, often the same week they complete the program.
    Are these trainings designed for both office and field leaders?
    Yes. We equip both project managers and superintendents with tools that connect field and office operations.
    What industries benefit most from LeanTakt training?
    Commercial, multifamily, residential, industrial, and infrastructure projects all benefit from flow-based planning.
    Do participants receive certificates after completing training?
    Yes. Every participant receives a LeanTakt Certificate of Completion.
    Is LeanTakt training recognized in the construction industry?
    Yes. Our programs are widely respected among leading GCs, subcontractors, and construction professionals.

    Superintendent / PM Boot Camp

    What is the Superintendent & Project Manager Boot Camp?
    It’s a 5-day immersive training for superintendents and PMs to master Lean leadership, takt planning, and project flow.
    How long does the Superintendent/PM Boot Camp last?
    Five full days of hands-on training.
    What topics are covered in the Boot Camp curriculum?
    Lean leadership, Takt Planning, logistics, daily planning, field-office communication, and team health.
    How does the Boot Camp improve leadership and scheduling skills?
    Yes. You’ll learn how to run day huddles, team meetings, worker huddles, and Lean coordination processes.
    Who is the Boot Camp best suited for?
    Construction leaders responsible for delivering projects, including Superintendents, PMs, and Field Leaders.
    What real-world challenges are simulated during the Boot Camp?
    Schedule breakdowns, trade conflicts, logistics issues, and communication gaps.
    Will I learn Takt Planning at the Boot Camp?
    Yes. Takt Planning is a core focus of the Boot Camp.
    How does this Boot Camp compare to traditional PM certification?
    It’s practical and execution-based rather than exam-based. You learn by doing, not just studying theory.
    Can my entire project team attend the Boot Camp together?
    Yes. Teams attending together often see the greatest results.
    What kind of real-world challenges do we simulate?
    Improved project flow, fewer delays, better team communication, and stronger leadership confidence.

    Takt Production System® Virtual Training

    What is the Virtual Takt Production System® Training?
    It’s an expert-led online program that teaches Lean construction teams how to implement takt planning.
    How does virtual takt training work?
    Delivered online via live sessions, interactive discussions, and digital tools.
    What are the benefits of online takt planning training?
    Convenience, global accessibility, real-time learning, and immediate application.
    Can I access the virtual training from anywhere?
    Yes. It’s fully web-based and accessible worldwide.
    Can I access the virtual training from anywhere?
    Yes. It’s fully web-based and accessible worldwide.
    What skills will I gain from the Virtual TPS® Training?
    Macro and micro Takt planning, weekly updates, flow management, and CPM integration.
    How long does the virtual training program take?
    The program is typically completed in multiple live sessions across several days.
    Can I watch recordings if I miss a session?
    Yes. Recordings are available to all participants.
    Do you offer group access or company licenses for the virtual training?
    Yes. Teams and companies can enroll together at discounted rates.
    How does the Virtual TPS® Training integrate with CPM tools?
    We show how to align Takt with CPM schedules like Primavera P6 or MS Project.

    Onsite Takt Simulation

    What is a Takt Simulation in construction training?
    It’s a live, interactive workshop that demonstrates takt planning on-site.
    How does the Takt Simulation workshop work?
    Teams participate in hands-on exercises to learn the flow and rhythm of a Takt-based project.
    Can I choose between a 1-day or 2-day Takt Simulation?
    Yes. We offer flexible formats to fit your team’s schedule and needs.
    Who should participate in the Takt Simulation workshop?
    Superintendents, PMs, site supervisors, contractors, and engineers.
    How does a Takt Simulation improve project planning?
    It shows teams how to structure zones, manage flow, and coordinate trades in real time.
    What will my team learn from the onsite simulation?
    How to build and maintain takt plans, manage buffers, and align trade partners.
    Is the simulation tailored to my specific project type?
    Yes. Scenarios can be customized to match your project.
    How do Takt Simulations improve trade partner coordination?
    They strengthen collaboration by making handoffs visible and predictable.
    What results can I expect from an onsite Takt Simulation?
    Improved schedule reliability, better trade collaboration, and reduced rework.
    How many people can join a Takt Simulation session?
    Group sizes are flexible, but typically 15–30 participants per session.

    Foreman & Field Engineer Training

    What is Foreman & Field Engineer Training?
    It’s an on-demand, practical program that equips foremen and engineers with leadership and planning skills.
    How does this training prepare emerging leaders?
    By teaching communication, crew management, and execution strategies.
    Is the training on-demand or scheduled?
    On-demand, tailored to your team’s timing and needs.
    What skills do foremen and engineers gain from this training?
    Planning, safety leadership, coordination, and communication.
    How does the training improve communication between field and office?
    It builds shared systems that align superintendents, engineers, and managers.
    Can the training be customized for my team’s needs?
    Yes. Programs are tailored for your project or company.
    What makes this program different from generic leadership courses?
    It’s construction-specific, field-tested, and focused on real project application.
    How do foremen and field engineers apply this training immediately?
    They can use new systems for planning, coordination, and daily crew management right away.
    Is the training suitable for small construction companies?
    Yes. Small and large teams alike benefit from building flow-based leadership skills.

    Testimonials

    Testimonials

    "The bootcamp I was apart of was amazing. Its was great while it was happening but also had a very profound long-term motivation that is still pushing me to do more, be more. It sounds a little strange to say that a construction bootcamp changed my life, but it has. It has opened my eyes to many possibilities on how a project can be successfully run. It’s also provided some very positive ideas on how people can and should be treated in construction.

    I am a hungry person by nature, so it doesn’t take a lot to get to participate. I loved the way it was not just about participating, it was also about doing it with conviction, passion, humility and if it wasn’t portrayed that way you had to do it again."

    "It's great to be a part of a company that has similar values to my own, especially regarding how we treat our trade partners. The idea of "you gotta make them feel worse to make them do better" has been preached at me for years. I struggled with this as you will not find a single psychology textbook stating these beliefs. In fact it is quite the opposite, and causing conflict is a recipe for disaster. I'm still honestly in shock I have found a company that has based its values on scientific facts based on human nature. That along with the Takt scheduling system makes everything even better. I am happy to be a part of a change that has been long overdue in our industry!"

    "Wicked team building, so valuable for the forehumans of the sub trades to know the how and why. Great tools and resources. Even though I am involved and use the tools every day, I feel like everything is fresh and at the forefront to use"

    "Jason and his team did an incredible job passing on the overall theory of what they do. After 3 days of running through the course I cannot see any holes in their concept. It works. it's proven to work and I am on board!"

    "Loved the pull planning, Takt planning, and logistic model planning. Well thought out and professional"

    "The Super/PM Boot Camp was an excellent experience that furthered my understanding of Lean Practices. The collaboration, group involvement, passion about real project site experiences, and POSITIVE ENERGY. There are no dull moments when you head into this training. Jason and Mr. Montero were always on point and available to help in the break outs sessions. Easily approachable to talk too during breaks and YES, it was fun. I recommend this training for any PM or Superintendent that wants to further their career."

    agenda

    Day 1

    Foundations & Macro Planning

    • Introduction to Takt Production System® principles
    • CPM vs TAKT comparison
    • Macro planning, zoning, and density analysis
    • Quantities and production rates
    • Hands-on application to participants’ projects with LeanTakt PM experts

    day2

    Norm Planning & Flow Optimization

    • Review and refinement of Day 1 work
    • Pull planning and sequence optimization
    • Work packaging for balanced flow
    • Project integration session with LeanTakt PM coaching

    day3

    Advanced Tools & Comparisons

    • Macro work packaging and example walkthrough
    • Calculator Norm for production optimization
    • Stacking comparison to avoid trade conflicts
    • Hands-on application to participants’ own schedules

    day4

    Buffers, Controls & Finalization

    • Review of Day 3 implementation
    • Buffer management strategies and placement
    • Takt control principles and steering methods
    • Project plan finalization with expert guidance

    day5

    Control Systems & Presentations

    • Takt steering, control systems, and real project examples
    • Participant project presentations with LeanTakt PM feedback
    • Wrap-up, feedback, and action planning for post-training implementation

    faq

    UNDERSTANDING THE TRAINING

    What is the Virtual Takt Production System® Training by LeanTakt?
    It’s an expert-led online program designed to teach construction professionals how to implement Takt Planning to create flow, eliminate chaos, and align teams across the project lifecycle.
    Who should take the LeanTakt virtual training?
    This training is ideal for Superintendents, Project Managers, Engineers, Schedulers, Trade Partners, and Lean Champions looking to improve planning and execution.
    What topics are covered in the online Takt Production System® course?
    The course covers macro and micro Takt planning, zone creation, buffers, weekly updates, flow management, trade coordination, and integration with CPM tools.
    What makes LeanTakt’s virtual training different from other Lean construction courses?
    Unlike theory-based courses, this training is hands-on, practical, field-tested, and includes live coaching tailored to your actual projects.
    Do I get a certificate after completing the online training?
    Yes. Upon successful completion, participants receive a LeanTakt Certificate of Completion, which validates your knowledge and readiness to implement Takt.

    VALUE AND RESULTS

    What are the benefits of Takt Production System® training for my team?
    It helps teams eliminate bottlenecks, improve planning reliability, align trades, and reduce the chaos typically seen in traditional construction schedules.
    How much time and money can I save with Takt Planning?
    Many projects using Takt see 15–30% reductions in time and cost due to better coordination, fewer delays, and increased team accountability.
    What’s the ROI of virtual Takt training for construction teams?
    The ROI comes from faster project delivery, reduced rework, improved communication, and better resource utilization — often 10x the investment.
    Will this training reduce project delays or rework?
    Yes. By visualizing flow and aligning trades, Takt Planning reduces miscommunication and late handoffs — major causes of delay and rework.
    How soon can I expect to see results on my projects?
    Most teams report seeing improvement in coordination and productivity within the first 2–4 weeks of implementation.

    PLANNING AND SCHEDULING TOPICS

    What is Takt Planning and how is it used in construction?
    Takt Planning is a Lean scheduling method that creates flow by aligning work with time and space, using rhythm-based planning to coordinate teams and reduce waste.
    What’s the difference between macro and micro Takt plans?
    Macro Takt plans focus on the overall project flow and phase durations, while micro Takt plans break down detailed weekly tasks by zone and crew.
    Will I learn how to build a complete Takt plan from scratch?
    Yes. The training teaches you how to build both macro and micro Takt plans tailored to your project, including workflows, buffers, and sequencing.
    How do I update and maintain a Takt schedule each week?
    You’ll learn how to conduct weekly updates using lookaheads, trade feedback, zone progress, and digital tools to maintain schedule reliability.
    Can I integrate Takt Planning with CPM or Primavera P6?
    Yes. The training includes guidance on aligning Takt plans with CPM logic, showing how both systems can work together effectively.
    Will I have access to the instructors during the training?
    Yes. You’ll have opportunities to ask questions, share challenges, and get real-time feedback from LeanTakt coaches.
    Can I ask questions specific to my current project?
    Absolutely. In fact, we encourage it — the training is designed to help you apply Takt to your active jobs.
    Is support available after the training ends?
    Yes. You can access follow-up support, coaching, and community forums to help reinforce implementation.
    Can your tools be customized to my project or team?
    Yes. We offer customizable templates and implementation options to fit different project types, teams, and tech stacks.
    When is the best time in a project lifecycle to take this training?
    Ideally before or during preconstruction, but teams have seen success implementing it mid-project as well.

    APPLICATION & TEAM ADOPTION

    What changes does my team need to adopt Takt Planning?
    Teams must shift from reactive scheduling to proactive, flow-based planning with clear commitments, reliable handoffs, and a visual management mindset.
    Do I need any prior Lean or scheduling experience?
    No prior Lean experience is required. The course is structured to take you from foundational principles to advanced application.
    How long does it take for teams to adapt to Takt Planning?
    Most teams adapt within 2–6 weeks, depending on project size and how fully the system is adopted across roles.
    Can this training work for smaller companies or projects?
    Absolutely. Takt is scalable and especially powerful for small teams seeking better structure and predictability.
    What role do trade partners play in using Takt successfully?
    Trade partners are key collaborators. They help shape realistic flow, manage buffers, and provide feedback during weekly updates.

    VIRTUAL FORMAT & ACCESSIBILITY

    Can I access the virtual training from anywhere?
    Yes. The training is fully accessible online, making it ideal for distributed teams across regions or countries.
    Is this training available internationally?
    Yes. LeanTakt trains teams around the world and supports global implementations.
    Can I watch recordings if I miss a session?
    Yes. All sessions are recorded and made available for later viewing through your training portal.
    Do you offer group access or company licenses?
    Yes. Teams can enroll together at discounted rates, and we offer licenses for enterprise rollouts.
    What technology or setup do I need to join the virtual training?
    A reliable internet connection, webcam, Miro, Spreadsheets, and access to Zoom.

    faq

    GENERAL FAQS

    What is the Superintendent / PM Boot Camp?
    It’s a hands-on leadership training for Superintendents and Project Managers in the construction industry focused on Lean systems, planning, and communication.
    Who is this Boot Camp for?
    Construction professionals including Superintendents, Project Managers, Field Engineers, and Foremen looking to improve planning, leadership, and project flow.
    What makes this construction boot camp different?
    Real-world project simulations, expert coaching, Lean principles, team-based learning, and post-camp support — all built for field leaders.
    Is this just a seminar or classroom training?
    No. It’s a hands-on, immersive experience. You’ll plan, simulate, collaborate, and get feedback — not sit through lectures.
    What is the focus of the training?
    Leadership, project planning, communication, Lean systems, and integrating office-field coordination.

    CURRICULUM & OUTCOMES

    What topics are covered in the Boot Camp?
    Takt planning, day planning, logistics, pre-construction, team health, communication systems, and more.
    What is Takt Planning and why is it taught?
    Takt is a Lean planning method that creates flow and removes chaos. It helps teams deliver projects on time with less stress.
    Will I learn how to lead field teams more effectively?
    Yes. This boot camp focuses on real leadership challenges and gives you systems and strategies to lead high-performing teams.
    Do you cover daily huddles and meeting systems?
    Yes. You’ll learn how to run day huddles, team meetings, worker huddles, and Lean coordination processes.
    What kind of real-world challenges do we simulate?
    You’ll work through real project schedules, logistical constraints, leadership decisions, and field-office communication breakdowns.

    LOGISTICS & FORMAT

    Is the training in-person or virtual?
    It’s 100% in-person to maximize learning, feedback, and team-based interaction.
    How long is the Boot Camp?
    It runs for 5 full days.
    Where is the Boot Camp held?
    Locations vary — typically hosted in a professional training center or project setting. Contact us for the next available city/date.
    Do you offer follow-up coaching after the Boot Camp?
    Yes. Post-camp support is included so you can apply what you’ve learned on your projects.
    Can I ask questions about my actual project?
    Absolutely. That’s encouraged — bring your current challenges.

    PRICING & VALUE

    How much does the Boot Camp cost?
    $5,000 per person.
    Are there any group discounts?
    Yes — get 10% off when 4 or more people from the same company attend.
    What’s the ROI for sending my team?
    Better planning = fewer delays, smoother coordination, and higher team morale — all of which boost productivity and reduce costs.
    Will I see results immediately?
    Most participants apply what they’ve learned as soon as they return to the jobsite — especially with follow-up support.
    Can this replace other leadership training?
    In many cases, yes. This Boot Camp is tailored to construction professionals, unlike generic leadership seminars.

    SEO-BASED / HIGH-INTENT SEARCH QUESTIONS

    What is the best leadership training for construction Superintendents?
    Our Boot Camp offers real-world, field-focused leadership training tailored for construction leaders.
    What’s included in a Superintendent Boot Camp?
    Takt planning, day planning, logistics, pre-construction systems, huddles, simulations, and more.
    Where can I find Lean construction training near me?
    Check our upcoming in-person sessions or request a private boot camp in your city.
    How can I improve field and office communication on a project?
    This Boot Camp teaches you tools and systems to connect field and office workflows seamlessly.
    Is there a training to help reduce chaos on construction sites?
    Yes — this program is built specifically to turn project chaos into flow through structured leadership.

    agenda

    Day 1

    Agenda

    • Intro to Camp
    • Set Expectations
    • Morning Routine
    • Plan Day
    • Explain "Why"
    • Teams Intros + Yells + Expectation
    • Focus, Physiology, Words + Yells
    • Blocks to Leadership
    • 50 Million
    • Biggest Thing
    • Choose Your Word
    • Marketing Exercise
    • Interview for the Project
    • PO Homework and Close the Day

    Outcomes

    • Understand how to get into a proper state to lead
    • Understand how to dig deep to find the confidence to lead
    • Team work and collaboration
    • Understand marketing
    • Understand how to interview for and win a project

    Day 2

    Agenda

    • Morning Routine
    • Day Planner
    • Plus & Delta
    • Macro Takt planning
    • Setup jobs + Signs + Logistics
    • Explain the IPCS™
    • Detailed logistics training
    • Team balance & health training

    Outcomes

    • Learn the IPCS™ understand how to integrate the entire project from start to finish with First Planners™ and Last Planners® through the Takt Production System®
    • Learn how to review a project
    • Learn advanced logistics
    • Learn team balance and health

    Day 3

    Agenda

    • Morning Routine
    • Day Planner
    • Plus & Delta
    • Review How Big Things Get Done
    • Review IPCSTM
    • Fix (Schedule, zone, logistics, trailer, org & procurement)
    • Fresh Eyes Meeting
    • Pre-Con Overview
    • TAKT SIMULATION
    • Recap and Review

    Outcomes

    • Understand why and how to plan
    • Understand the benefits of using a Takt production plan
    • Learn the steps to proper pre-con that sets the project up for success
    • Learn how to review a project in a Fresh Eyes Meeting
    • Learn flow from Takt planning

    Day 4

    Agenda

    • Morning Routine
    • Day Planner
    • Plus & Delta
    • Opposing Squares
    • Pull Plan
    • Takt Remaining
    • Norm Update
    • Re Zoning
    • Risks & Pre-Con Align
    • Meeting System
    • Problems
    • Recap

    Outcomes

    • Understand the Norm level Takt plan for weekly/daily planning
    • Benefits and outcomes of rezoning strategies
    • Using meetings to feed information through the system and to the Foremen

    Day 5

    Agenda

    • Morning Routine
    • Day Planner
    • Plus & Delta
    • Huddle I.D.S
    • Day Plan
    • Worker Huddle
    • Norm Update
    • Team Huddle
    • Lean Systems Recap
    • Feedback Exercise
    • Final & Close

    Outcomes

    • Know what information is needed and how to get it to the Workers
    • Better understand how to give feedback and why it’s crucial for everyone
    • How to problem solve as a team
    • Understand how all systems tie together
    • Know how the information gets all the way to the worker
    • Have perfect clarity on the individual’s personal organization planner