Month: January 2026

You Are Hurting Your Back – Foremen & Workers

Posted on by Danny Jiménez⁩
Read 23 min

Lower Back Care for Construction Workers: Sitting, Hamstrings, Hydration, and Simple Daily Prevention

Most people in construction and industrial work are tough. They’ll lift, carry, climb, twist, and grind through a day that would break a lot of folks. The problem is that toughness can turn into neglect. We’ll maintain a truck better than we maintain our bodies. We’ll track a schedule down to the hour, but we won’t spend five minutes on a warm-up that could save us from months of pain.

This episode is a reminder that your body is part of the production system. If your lower back goes down, everything goes down your work, your sleep, your mood, your ability to be present at home. And when pain sticks around long enough, it starts shaping your life decisions. You stop doing the things you love, you start compensating, and you accept “that’s just how it is.”It doesn’t have to be that way. The point here isn’t to pretend you’ll never get sore. The point is to give you practical, jobsite-relevant basics that reduce symptoms, reduce risk, and help you show up strong for your team and your family.

The pain in the field is obvious. People wake up stiff. They get pain after driving. They feel a pinch bending to tie boots. They feel nerve-like symptoms down the leg. They work through it until one day it’s not a “twinge” anymore. It’s a real problem.The failure pattern is system-first. Most crews aren’t trained on body maintenance. Most companies don’t build warm-ups into the day. Most leaders don’t treat mobility like PPE. And most workers go home and “rest” in ways that actually make it worse—long sitting, collapsing into a chair, and staying immobile because movement hurts.The system failed them; they didn’t fail the system. So let’s talk about the system.

The Real Conflict: Most Workers Aren’t Caring for Their Bodies Like They Could

This isn’t about guilt. It’s about awareness. You can work hard and still work smart. You can take pride in grinding and still build habits that keep you healthy long-term. A lot of workers think back pain is just age, genetics, or bad luck. Sometimes those factors matter. But most of the time, lower back pain is a predictable outcome of predictable patterns: too much sitting, tight hamstrings, poor hydration, weak supporting muscles, and not enough movement variety.

If you’re reading this and your back already hurts, the message isn’t “try harder.” The message is “stop guessing.” Get a professional assessment when needed, learn what’s happening in your body, and then apply a simple prevention system that supports you daily.

Why the Lower Back Takes the Hit in Construction and Industrial Work

The lower back gets hit because it’s the bridge between your upper body and your lower body. When you lift, your back transmits force. When you twist, your back transmits force. When you carry awkward loads, your back transmits force. When your hips are tight, your back compensates. When your hamstrings are tight, your back compensates.

And here’s the kicker: many workers are already compromised before they even start work. They spend a long time sitting driving in, sitting in meetings, sitting in equipment then they jump straight into bending and lifting. That transition is brutal if you don’t have a warm-up and mobility routine. It’s not the work alone. It’s the combination of sitting plus work plus neglected recovery.

The Spine’s Curves and What Happens When the Low Back “Straightens”

One of the most important things to understand is that your spine has natural curves. Those curves help distribute load and absorb shock. When the lower back loses its natural curve and “straightens” under compression, the mechanics change. The spine becomes less efficient at handling stress, and symptoms show up sooner.

This is why posture and mobility matter. This is why driving posture matters. This is why sitting a lot matters. And this is why a “quick fix” without changing the daily patterns usually fails. If the daily pattern keeps compressing and flattening the system, the system will keep producing pain.

Sitting, Driving, and Compression: The Hidden Multiplier Before the Workday Even Starts

If you want one idea to remember, it’s this: sitting is not neutral. It’s a form of compression. Long sitting tightens hip structures, shortens certain muscles, and puts sustained load on the low back. Then you stand up stiff, your hamstrings feel like cables, and you try to bend. That’s why the drive to work can be a multiplier. Even if you’re physically strong, long seated time sets your back up for trouble. Equipment operators feel this even more because vibration and prolonged seated posture stack the problem. So the solution isn’t “never sit.” The solution is to break up sitting, adjust posture, move often, and warm up before you demand high output from your back.

Hamstrings: The Quiet Driver of Low Back Symptoms

Hamstrings are a quiet driver because when hamstrings are tight, they affect pelvic position and how your body moves when you hinge or bend. A tight hamstring system pulls on the mechanics upstream. And when the hips don’t move well, the low back has to move too much.A lot of workers feel low back pain and assume the back is the only issue. Sometimes the back is reacting to a problem elsewhere tight hamstrings, tight hips, weak glutes, weak core support, or poor movement patterns.That’s why hamstring flexibility isn’t just “stretching for athletes.” It’s a practical trade skill for longevity.

Hydration and Joint “Lubrication”: Why Water Changes How Your Body Responds

Hydration sounds too simple, so people ignore it. But joints and soft tissue respond differently when you’re dehydrated. Your tissue is less forgiving. Recovery is slower. Cramping and tightness are easier to trigger. Stiffness can feel worse. If you want your body to handle repetitive load and still feel decent, hydration is part of the system. This is especially true in hot conditions, in PPE, and in physically demanding scopes. This isn’t a lecture. It’s a reminder: you can’t run a machine without fluids and expect it to last. Same for you.

Symptoms to Watch For: Discomfort, Sciatic-Like Symptoms, and Morning Stiffness

The body gives you warnings before it gives you an injury. Pay attention to the early signals. Pain after sitting. Pain first thing in the morning. Tightness that feels like it “won’t loosen.” A pinch when you hinge. Symptoms that feel like they travel into the hip or leg. Those signals are not weakness. They’re feedback. And if you respond early with better habits and professional help when needed, you can often avoid turning a small issue into a big one. If symptoms are severe, worsening, or accompanied by numbness, weakness, or other red flags, don’t guess. Get medical evaluation. The goal is to be smart, not brave.

The Misbelief: “I’ll Go Home and Sit Down and Rest”

A lot of workers think rest equals sitting. But long sitting after a day of sitting-plus-lifting can be a trap. If your back is already compressed and stiff, collapsing into a chair can lock you into the very position that’s irritating the system. Rest is valuable. Recovery matters. But recovery is not always “more sitting.” Sometimes recovery is walking, gentle movement, stretching, hydration, and a few minutes of mobility. Sometimes the best way to calm a low back down is to restore motion and reduce stiffness gradually, not freeze.

Signals Your Low Back System Is Getting Compromised

  • You feel stiff or sore after driving, and the first 10–15 minutes of movement feels “rusty.”
  • Your hamstrings feel tight all the time, especially when you bend, hinge, or squat.
  • You notice discomfort when twisting, reaching, or lifting from awkward positions.
  • You wake up with morning stiffness that takes a while to loosen up.
  • You experience symptoms that feel like they travel into the hip, glute, or leg.
  • You keep thinking, “I just need to sit down and rest,” but sitting makes you feel worse later.

If that’s you, don’t panic. Just treat it like a production problem: identify the pattern, then improve the system.

A Practical Prevention System: Warm Up, Stretch, Strengthen, Then Work

The goal is not a complicated workout plan. The goal is a repeatable routine you can actually do.A simple system looks like this: warm up enough to get blood moving, stretch the key areas that pull on the low back, strengthen the supporting muscles over time, and then work with better movement patterns. Warm-up doesn’t have to be a full gym session. It can be five minutes of walking, marching, controlled hinges, and light mobility. Stretching doesn’t have to be a yoga class. It can be targeted hamstring and hip work for a few minutes. Strengthening doesn’t have to be heavy lifting. It can be consistent core and glute support work done a few times per week.If you want a construction translation: you wouldn’t cold-start a machine at full load without checking it. Treat your body with the same respect.

Don’t Forget Equipment Operators: Vibration, Seated Time, and Back Risk

Operators often get overlooked because they don’t “lift” as much, but seated time and vibration are real stressors. If you’re an operator, you may need more movement breaks, better seat setup, and a stronger daily mobility routine than you think.A simple rule: if your workday is mostly seated, your warm-up and movement breaks are not optional. They’re your equivalent of stretching out a stiff hose before you expect full flow.

Connecting to LeanTakt and Takt: Your Body Is Part of the Production System

LeanTakt is about stabilizing the system so people don’t have to be heroes. Takt is about rhythm. Your body needs rhythm too. If you ignore it for months and then try to “fix it” in one weekend, you’re going to get frustrated. Flow over busyness applies here. A small daily routine beats a big occasional effort. You don’t need perfection. You need consistency. This is also respect for people. If you’re a leader, it’s worth building a culture where crews warm up, hydrate, and take mobility seriously. Not as a “soft” thing, but as a longevity thing. We’re building people who build things.

A Simple Daily Back-Protection Routine

  • Hydrate early and consistently through the day, especially before physical work ramps up.
  • Break up sitting: after driving or long seated time, walk and loosen up before heavy bending or lifting.
  • Spend a few minutes daily on hamstring and hip mobility, focusing on consistency over intensity.
  • Build support muscles: glutes and core stability matter because they reduce how much your low back has to compensate.
  • Use movement breaks: short walks, gentle hinges, and posture resets reduce stiffness and compression.
  • If pain escalates, don’t guess—get evaluated and follow a plan instead of “toughing it out” blindly.

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

The Challenge: Build a Morning Routine That Protects Your Career and Your Family

Here’s the challenge: stop treating your body like a disposable tool. Build a five-to-ten-minute routine you can repeat. Do it before the day loads your spine. Do it after long drives. Do it consistently enough that you don’t have to rely on “luck” to feel good.And if you’re a leader, make this normal. Make warm-ups normal. Make hydration normal. Make mobility normal. Not because you’re trying to be trendy, but because you’re trying to keep your people healthy, steady, and able to earn a living without chronic pain.You don’t need to be perfect. You need to care. Take one step today. Then take one step tomorrow. That’s how careers last.

 

FAQ

Is lower back pain just part of construction work?
Soreness can happen, but chronic low back pain is often tied to fixable patterns like prolonged sitting, tight hamstrings and hips, weak support muscles, and lack of warm-up and mobility. A simple routine can reduce symptoms for many people.

Why does driving make my back feel worse?
Driving is prolonged sitting, which compresses the low back and tightens hips and hamstrings. If you step out of the truck and immediately bend and lift, your back is working from a compromised position.

Are hamstrings really connected to low back pain?
Yes. Tight hamstrings affect pelvic mechanics and can force your low back to compensate when you bend, hinge, or lift. Improving hamstring and hip mobility often helps reduce low back irritation.

What should I do if I have sciatica-like symptoms?
Treat it seriously and get evaluated if symptoms are persistent, worsening, or include numbness or weakness. Don’t rely on guessing or random stretches. A professional assessment can clarify what’s happening and what to avoid.

How does this connect to LeanTakt and Takt?
Takt is rhythm, and LeanTakt is stability and flow. Your body also needs stability and rhythm. Small daily habits—warm-up, hydration, mobility, movement breaks—protect your ability to perform consistently without heroics.

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.

Families & Construction Feat. Katie Schroeder

Posted on by Danny Jiménez⁩
Read 21 min

Families in Construction: How to Protect Your Marriage and Kids When the Job Demands More Than It Should

There’s a part of construction no one puts in the brochure. Nobody tells you at the career fair that the schedule can eat your evenings, your weekends, and your emotional bandwidth. Nobody explains that you can “win” at work and still lose at home. And nobody trains you for the moment you walk through the door after a brutal day and realize your family needs you to be a different kind of leader than you were on the jobsite.

Jason Schroeder and Katie talk about that reality with honesty. Not as a motivational speech, but as a real conversation from a real marriage. They describe what it feels like when construction becomes the third person in the relationship. They name the strain, the growth, the mistakes, and the habits that actually protect families over time.

The pain is simple and heavy. The job is intense. You come home tired. The house has been running without you all day. The kids have needs. The spouse has carried the load. And if you show up with the same edge you used to “get things done” at work, you can quietly damage the place you claim you’re working for.

The failure pattern is also predictable. We don’t set expectations. We don’t build a home operating system. We don’t agree on parameters for travel, hours, and career choices. Then we act surprised when stress erupts. We take the job home emotionally. We criticize the house. We try to control what we haven’t helped build. We treat our family like they’re another subcontractor who should comply.

The system failed them; they didn’t fail the system. Most people are never taught how to build a relationship system under high workload. They’re told to “provide,” and they assume love will automatically survive the pressure. It won’t. It has to be designed.

Field story first. Katie shares that she grew up with a dad who worked far away and was home only on weekends, and she saw what that did to the rhythm of family life. Later, she and Jason live their own version of that distance. Jason talks about coming home and feeling like he didn’t fit because Katie had built the daily system with the kids while he was gone. That discomfort can turn into criticism if you don’t recognize what’s really happening: the house has a flow, and you’re re-entering it, not running it.

And then there’s the winter storm story. Katie describes a situation where the heater went out in brutal cold, and she set up one room to keep the kids warm and safe. It’s a picture of what spouses do in construction families: they solve problems quietly, often alone, because the situation demands it. The lesson isn’t guilt. The lesson is respect, partnership, and building a system that doesn’t depend on heroics.

Construction Is Hard: The Family Cost Nobody Warns You About

Construction is an industry where the job doesn’t end when the shift ends. There’s always something coming: the next pour, the next inspection, the next crisis, the next “we need it tomorrow.” That pressure can trick leaders into believing their family will understand indefinitely, as long as they’re doing it “for them.”

But families don’t need a martyr. They need presence, kindness, and predictability. When you’re absent physically or emotionally, the home adapts. It creates a new normal. And if you keep ignoring that, you don’t just lose time. You lose connection. This is why Jason’s language about protecting people and families matters. If the plan requires burnout, the plan is broken. That’s true at work. It’s true at home.

The Deal You Make: Expectations and Parameters Before the Chaos Hits

One of the biggest themes in this conversation is that couples need a “deal” clear expectations and parameters before the chaos hits. That means talking about what travel looks like. What weekends look like. What boundaries exist around late nights. What roles each person will own. What support systems will be built. It also means revisiting the deal as life changes new kids, promotions, relocations, new projects.

If you don’t set parameters, the job will set them. And the job will always choose itself. This is where a system-first mindset helps. You don’t rely on emotions. You design agreements. You create clarity. You protect your relationship with structure.

The Spouse at Home Builds the System (So Don’t Come Home and Wreck It)

Katie makes a key point: when one spouse is gone a lot, the spouse at home builds the daily operating system. They create the routines. They manage the meals. They manage the school. They manage the bedtime flow. They manage the emotional tone. When the traveling spouse returns and feels out of place, the wrong response is to criticize the system. The right response is to respect it, learn it, and support it.

Jason describes coming home and feeling like he didn’t fit, and that experience is common for traveling superintendents and project managers. The home has flow, and you are re-entering it. Your job is not to disrupt it. Your job is to be a rejuvenating influence.

Don’t Bring the Job Home: “No Excuse to Take It Out on Your Family”

Jason and Katie are clear: there’s no excuse to take job stress out on your family.That doesn’t mean you pretend you’re fine. It means you don’t weaponize your exhaustion. You don’t come home sharp, critical, and impatient. You don’t unload your frustration onto the people who love you.This is one of the simplest leadership standards a construction professional can adopt: the job can be brutal, but your family should not feel punished for it.If you need a decompression ritual, build one. If you need a transition time, take it. If you need help, ask for it. But don’t bring the job home and call it normal.

Why Dads Matter: Kindness, Approachability, and the Mood of the Home

Katie talks about the importance of dads being kind and approachable. Kids don’t need perfection. They need safety and connection. They need a parent they can approach without fear of being snapped at.That’s not “soft.” That’s strength. A leader who can regulate their mood at home is a leader who is building a legacy. The mood of the home becomes the emotional setpoint for the kids.If a parent walks in and the whole house tightens up, that’s a signal. Not a shame signal. A system signal. Something needs to change.

Moving, Travel, and Career Growth: Make the Decision Together and Own the Consequences

Construction often requires moves and travel. Promotions can come with relocations. Projects can come with extended time away.

The principle here is not “never travel.” The principle is “decide together.” Talk through the real consequences, not just the paycheck. If the move is right, own it as a team. If it isn’t, say no as a team. When one person makes the decision unilaterally, resentment grows. When the decision is shared, sacrifice becomes partnership.

Signals the Job Is Bleeding Into Your Home

  • You come home grumpy and the family braces for your mood.
  • You criticize how the house is run even though you weren’t there carrying the day.
  • You “check out” emotionally because you’re drained, and connection fades.
  • You don’t have clear agreements about travel, hours, and boundaries, so everything becomes reactive.
  • One spouse is carrying the entire system, and you unintentionally undermine it when you return.

Stop Trying to Control the House: Support, Help, and Be a Rejuvenating Influence

Jason describes the shift that has to happen for construction leaders: stop trying to control the house and start supporting it.That might mean taking on small tasks that create relief. It might mean listening instead of correcting. It might mean entering the home with calm energy, not authority energy. It might mean asking, “How can I help?” and meaning it.The spouse at home doesn’t need another supervisor. They need a partner. The kids don’t need another inspector. They need a parent who can be present.This is respect for people, applied at home.

When It’s Brutal: The Cold-Storm Story and What Real Partnership Looks Like

The winter storm story is a perfect example of why spouses in construction need recognition and support. When the heater went out, Katie created a one-room safe zone and handled the moment. That’s what partnership looks like when the industry is demanding: one person steps up because the situation requires it.But the long-term goal is not heroics. The long-term goal is stability. Stability comes from planning, systems, and shared responsibility.If your family system relies on one person being a hero constantly, it will eventually break.

Home System Moves That Protect the Family

  • Create a “transition ritual” so you don’t walk in carrying job stress like a weapon.
  • Agree on parameters for travel, late nights, and weekends, and revisit them as life changes.
  • Support the home routine that exists; don’t criticize the system you didn’t build that day.
  • Build a weekly presence plan: specific time blocks where you are fully there, not half there.
  • Set a kindness standard: your spouse and kids should get your best, not your leftovers.

It Gets Better: Progress, Repentance, and Building a Life Over Time

Jason and Katie also talk about growth. People learn. People change. Couples can get better at this. You can build a life over time, even after mistakes.That requires humility. It requires repentance when you’ve been sharp. It requires rebuilding trust when you’ve been absent. It requires consistent small actions, not one big apology.The good news is that systems can be built. Habits can be changed. The home can become stable again.

Builders Build People: Why Healthy Families Create Better Builders

The final point connects everything back to purpose. Construction isn’t just about buildings. It’s about people.Jason’s quote fits here: “We build people who build buildings.” If you sacrifice your family to build a project, you didn’t win. You just traded the most important thing for the loudest thing.

Healthy families create better builders. Calm homes create clearer leaders. And clear leaders build safer, higher-quality projects with better flow.If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Conclusion

If you’re in construction, don’t wait until your marriage is strained or your kids are distant to build a system. Make the deal. Set the parameters. Respect the spouse who runs the home daily. Create a transition ritual. Show up kind. Show up present. Protect your family like you protect your schedule because the family is the real schedule. And remember the purpose: “We build people who build buildings.” +

Build them at home first.

FAQ

How do construction professionals avoid bringing job stress home?
Build a transition ritual that helps you decompress before entering the house. Then commit to a kindness standard at home: you can be honest about stress without taking it out on your spouse or kids.

What should couples discuss before accepting travel-heavy roles?
Talk through parameters: how many nights away, weekend expectations, how communication will work, what support will exist at home, and what the family’s non-negotiables are. Decide together and revisit as conditions change.

How can a traveling superintendent re-enter the home without conflict?
Recognize that the spouse at home built the daily system. Re-enter with humility and support. Ask how to help, learn the routine, and avoid criticizing the system you weren’t running that day.

Why is presence more important than “providing”?
Providing matters, but kids and spouses need emotional safety and connection. Presence builds trust and stability. Without presence, families adapt in ways that reduce closeness over time.

How does this connect to LeanTakt and Takt?
Flow requires stability. Your home is a system too. When you design your home rhythm intentionally agreements, routines, and calm re-entry you reduce variation and protect the people you’re building all this for.

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.

How to Implement Scrum in Construction Feat. Felipe Engineer

Posted on by Danny Jiménez⁩
Read 24 min

Scrum in Construction: How to Run Agile, Protect Flow, and Adapt Lean Tools Without Breaking People

You’ve probably felt the gap between what the schedule says and what the project is actually doing. The CPM printout looks clean. The three-week lookahead is stapled and distributed. Everyone nods. Then Monday hits, the work isn’t ready, the field improvises, and the plan becomes a story we tell ourselves to feel in control. Jason Schroeder puts it bluntly in this interview: we are not going to fix the industry by only using CPM and three-week lookahead printouts.

The pain on most projects isn’t that people don’t care. It’s that the system doesn’t give them a short feedback loop. It doesn’t make constraints visible early enough. It doesn’t help teams learn fast, especially in complex areas like interiors, energization, and functional upgrades where dependencies pile up. When the system can’t see problems early, people pay for it latewith stress, nights, weekends, and burnout.

The failure pattern is predictable. We take a tool, we treat it like a script, and then we judge teams for not “doing it right,” instead of asking the Lean question: is it working, and are we learning? Jason describes being criticized for modifying Last Planner to fit circumstances, and he pushes back with the right question if the results are there, why are we policing the template instead of improving the process?

The system failed them; they didn’t fail the system. Most teams were never trained to combine planning methods, shorten feedback loops, and adapt without shame. That’s what Scrum can help with when it’s used as a pull system to enable flow, not as another layer of bureaucracy.

Field story time. Felipe shares his own burnout trajectoryworking over 100 hours a week, seven days a week until a leader hit him at exactly the right time with exactly the right question, interrupted his habits, and helped him try a different way. Within two weeks, he gained 40 hours back, stopped working nights and weekends, and learned a lesson he now repeats: you can’t push a “silver bullet” on teams; you have to meet people exactly where they are. Why this matters is simple. If you want quality, safety, schedule reliability, and stable lives for the people doing the work, you need systems that make work visible, limit multitasking, and create learning cycles. Scrum is one way to do that especially when you integrate it with LeanTakt thinking and Takt where it fits.

Why CPM and 3-Week Lookaheads Aren’t Enough Anymore

Jason isn’t anti-schedule. He’s P6 trained and knows CPM deeply; his point is that the industry won’t get where it needs to go if we treat CPM and short lookaheads like the whole system. CPM can be useful for milestones and contractual narratives, but it doesn’t automatically create day-to-day flow in messy, constraint-heavy zones. A printout doesn’t remove roadblocks. A bar chart doesn’t create team pull. And a “critical path” label doesn’t magically focus the organization on solving the constraint. The real issue is feedback. Construction changes daily. In complex areas, you need a system that lets the team see what’s blocked, swarm it, learn quickly, and adjust without waiting for the next weekly meeting. That’s where Scrum thinking becomes practical especially when you use it to attack the most critical portions of the job instead of staring at them on a CPM report.

What Scrum Really Is in Construction Terms

Felipe demystifies Scrum by translating it into Last Planner language. A backlog is all the things you know you need to do to accomplish the project milestones in Last Planner terms. Sprint planning is similar to phase pull planning: prioritize the next phase and pull the best sequence, but with a time box and a focus on one thing at a time instead of multitasking.

Then comes the daily Scrum. Felipe explains it like this: it’s exactly like a daily huddle, except it’s 15 minutes or less and follows a standard set of questions to keep the feedback loop tight. That time box matters because it forces clarity and eliminates the “meeting for meeting’s sake” habit that kills momentum in the field. Scrum also includes a review (what did we actually accomplish with stakeholders) and a retrospective (how do we learn and change the system). Felipe frames it as minimal management bureaucracy meant to enable team workflow and value delivery, not create paperwork. He even summarizes the structure as “three roles, five events, and three artifacts,” emphasizing it’s intentionally lightweight.

Stop Treating Lean Tools Like Religion: PDCA Your Process

Jason’s stance is refreshing and necessary: we should PDCA our Lean tools. He openly admits to modifying Last Planner without shame, shifting huddles to focus more on roadblocks than PPC, because the goal is flow and results, not ritual compliance. He calls out the criticism he gets, “you have to do it the standard way”  and answers with a Lean principle: aren’t we supposed to iterate? Felipe backs this up from another angle. He describes how teams debate whether something is “textbook,” and he returns to the purpose: why are we doing it in the first place? Not for awards. Not for purity. For outcomes, learning, and stability. When the tool becomes the goal, the project suffers, and people burn out trying to “perform the process” instead of improving the work.

Signals You’re Using Lean Tools in “Template Mode”

  • The team can recite the steps, but roadblocks still sit unresolved week after week.
  • Meetings produce notes, not decisions or experiments.
  • People are criticized for “not doing it standard” instead of being coached toward results and learning.
  • The system is treated as a script, so teams often fake compliance instead of being honest.
  • Interiors or complex zones feel impossible to manage because the tool can’t keep up with the volume of dependencies.

When Last Planner Breaks Down in Interiors and Complex Work

Jason describes a real field condition: in big hospitals, laboratories, and mega projects, Last Planner “in its designed detail can start to break down in building interiors because there are so many activities and so much interdependence. That’s not a knock on Last Planner. That’s a signal about complexity and feedback speed. In those environments, you need tighter loops, smaller batches, and a visual system that helps the team focus on the next best work while actively clearing constraints. That’s why Scrum boards, simple to-do, doing, done can be powerful in functional areas, shutdown work, upgrades, and other zones where “the plan” must be updated constantly.

Use Flow for the Standard Areas and Scrum for the Troublesome Areas

Jason outlines a practical hybrid mindset. Start with a Takt plan to get realistic about the end date and avoid the gap between what we sell and what we can actually build, then avoid letting CPM logic thrash flow back and forth. Where areas run nicely on Takt, keep them there; then focus Last Planner or Scrum energy on the most critical, constraint-heavy portions of the job elevators, MRI installs, power upgrades where dedicated teams can meet daily and push constraints out of the way. That’s the right posture: flow where flow is possible, and an agile swarm where complexity demands it. Scrum becomes a way to “attack” the most critical items instead of simply labeling them as critical and hoping the schedule survives.

“Done Means Done”: The Quality Standard That Protects Handoffs

One of the most valuable moments in the interview is Felipe’s definition of “done.” In construction terms, “done” is not “mostly done.” It’s installed right, coordinated, ready for use, and the next person in line can pick it up without rework, punch lists, or “takesies backsies.” That definition protects flow because handoffs are where projects hemorrhage time. When “done” is vague, teams push half-finished work forward, stacking defects and creating downstream chaos. When “done” is clear, teams finish as they go, stabilize quality, and maintain a rhythm the field can trust.

The Daily Scrum and the Power of Short Feedback Loops

The daily Scrum is a 15-minute-or-less check-in designed to keep the team aligned and focused on removing constraints quickly. The power here isn’t the meeting; it’s the frequency and the discipline. It keeps the team from waiting a week to discover what’s blocked. It forces prioritization. It reduces multitasking, because the work is pulled one item at a time instead of scattered across ten “in progress” tasks.That’s how you protect people from burnout: fewer open loops, fewer late surprises, and less thrashing. Short loops turn stress into action, and action into learning.

Retrospectives: Turn Complaints Into Experiments

Felipe describes running a retrospective with an IPD team and making one requirement explicit: if it’s only talk, it’s not helping. The retro must produce experiments specific changes the team will test to improve what isn’t working. He shares that the team identified issues, created experiments, and even followed up quickly with a list of what they would try next. This is the habit construction needs. Not just “lessons learned” after the job is over, but learning while it still matters.

Adoption Rule: You Can’t Force It Meet People Where They Are

Felipe learned the lesson the hard way. He tried pushing what he thought teams wanted, wasn’t invited back, and it took years to repair the relationship. Then he says the line that should be posted in every Lean implementation room: “You have to meet people exactly where they are.”

This is respect for people as a production strategy. You can’t shame teams into flow. You create an environment where they can experiment safely, get repetitions, then iterate and make it their own. That’s how you get real adoption without breaking people.

How to Start Simple: Visual Boards, Backlogs, and One Conversation at a Time

Felipe is clear: you don’t have to start with full formal Scrum on day one. Start where you are. If you’re not doing a daily huddle, start with a daily huddle. Then make a simple visual board and a backlog: to do, doing, done. Keep it visible. Keep it honest. Make the work pull-based and reduce multitasking.

Jason shares his own “ignorant” early version of Scrum big boards, stickies, meeting around the work in complex areas and the point is not the label. The point is the behavior: visualize work, focus, learn fast, and adjust with the team.

A Simple Scrum Starter Set for Construction Teams

  • Create a visible board with to do / doing / done and keep it current.
  • Build a backlog of real work and real constraints, not wish lists or vague promises.
  • Time-box the daily huddle to 15 minutes and use it to clear blockers fast.
  • Define “done” so handoffs are clean and the next crew can flow without rework.
  • Run a retrospective that produces experiments, not just opinions.

Where Takt Fits: Rhythm for the Work, Scrum for the Constraints

Jason’s hybrid approach is a practical way to keep the system stable. Takt provides rhythm and predictable flow where the work is repeatable and can be balanced. Scrum provides an agile attack system for the messy, constraint-heavy zones that require daily coordination and rapid learning especially the places where “critical path” labels aren’t enough to generate action. That combination is exactly what LeanTakt is about: flow over busyness, and systems over heroics. Not more meetings. Better feedback loops. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

The Challenge: Build a Team That Learns Fast Without Burning Out

The real win in this interview isn’t Scrum vocabulary. It’s the leadership posture behind it: shorten feedback loops, learn quickly, and adapt tools to the project while protecting people. Felipe’s story about gaining 40 hours back in two weeks is proof that better systems don’t just save schedules they save lives at home, too.

If you’re leading in the field, take this as your challenge. Don’t force tools on people. Don’t worship templates. Don’t settle for meetings that produce talk. Build a learning system. Make work visible. Define “done.” Create experiments. And lead with respect. Because the quote is true, and it’s the heart of implementation: “You have to meet people exactly where they are.”

FAQ

What is Scrum in construction, in plain language?
Scrum is a pull-based workflow system that makes work visible, limits multitasking, and creates short feedback loops through daily check-ins, reviews, and retrospectives. Felipe describes it as lightweight by design, meant to enable team workflow and learning rather than add bureaucracy.

How is Scrum different from Last Planner System?
In the interview, Felipe maps Scrum elements to Last Planner concepts backlog to milestones, sprint planning to phase pull planning, and daily Scrum to a short daily huddle while emphasizing Scrum’s time-boxed loops and visibility as a way to deliver value quickly.

Where does “done means done” fit on a jobsite?
It’s the quality standard that protects handoffs. Felipe defines “done” as fully coordinated, installed right, ready for use, and usable by the next person in line no partial completion that creates downstream rework and delays.

How do I introduce Scrum without forcing it on the team?
Start simple where the team is: daily huddle, visible board, and a basic backlog. Felipe is clear you don’t have to start with full formal Scrum on day one, and he emphasizes the adoption principle: meet people exactly where they are.

How can Scrum and Takt work together?
Jason describes using a Takt plan to establish realistic flow and end dates, then applying Scrum to focus daily energy on the most critical, constraint-heavy portions of the job like complex functional areas or specialty upgrades

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.

The Myth of Micro-managing

Posted on by Danny Jiménez⁩
Read 15 min

Micromanaging Isn’t the Problem: Construction Teams Need Clear Leadership, Training, and Support

If you’re the kind of person who loves railing against “micromanaging,” this episode might challenge you.

Because Jason Schroeder makes a strong case: micromanaging is mostly a myth. The real issue isn’t guidance. The real issue is bad leadership behaviors and unclear systems.

And when the industry demonizes micromanagement as a blanket idea, it creates a bigger problem: people stop teaching. Leaders stop coaching. Foremen stop training apprentices. Superintendents stop guiding foremen. Managers back away from helping their teams because they’re afraid of being labeled.

That’s not progress. That’s disconnection.

Why “Micromanaging” Became a Punchline on Job Sites

In construction, “micromanaging” has become a buzzword people throw around anytime they feel watched, corrected, or directed.

Sometimes that’s valid. Sometimes someone really is hovering, changing priorities every hour, and creating confusion. But Jason’s point is that the word “micromanaging” has become a catch all for problems it doesn’t actually describe.

When people complain about micromanagement, they’re often fighting one of two things:

  • A cowboy mindset: “I want to do what I want, and I don’t want to fit into a system.”
  • Bad leadership behaviors: unclear expectations, poor coaching, reactive correction, and control without training.

If we don’t separate those two, we’ll never fix the real issue.

What People Actually Hate: Bad Leadership Behaviors, Not Guidance

Jason is careful about language: he’s not calling anyone “bad.” He’s talking about bad leadership behaviors, learned traits, and wrong models.

Here’s the difference:

  • Coaching is intentional, skill based, and designed to enable independence.
  • Control is reactive, unclear, and often rooted in fear or ego.

If someone is “helicoptering” you, constantly telling you what to do, but never clarifying the target, never demonstrating the process, and never enabling you to succeed, you’ll feel the pressure. You’ll call it micromanagement.

But that isn’t micromanagement. That’s a failure of leadership.

The Cowboy Trap: “Don’t Tell Me What to Do” Isn’t a System

Jason points out something uncomfortable but true: a lot of micromanagement complaints come from a resistance to systems.

Some people don’t want training. They don’t want a standard. They don’t want a method. They want freedom without alignment.

Construction can’t run like that.

If you want flow, safety, and quality, you need systems. You need standards. You need teams moving together.

The phrase “don’t micromanage me” can sometimes be a cover for “don’t hold me to a process.”

That’s not leadership. That’s chaos wearing confidence.

Coaching Isn’t Micromanaging: The EDGE Method in Real Life

Jason gives a clear framework for how real skill building works:

EDGE: Explain, Demonstrate, Guide, Enable.

This is what masters do. This is what good leaders do. It’s not micromanagement. It’s training.

  • Explain the concept
  • Demonstrate it
  • Guide the person while they do it
  • Enable them to do it on their own

If you have a master guiding you through the EDGE method, you don’t call it micromanaging. You call it learning.

So why do we treat jobsite coaching differently?

Why Masters Get a Pass: Stephen Curry and Skill Development

Jason uses a simple example: his son is watching a master class by Stephen Curry on shooting a basketball foot placement, toe direction, stance, the whole sequence.

Nobody watches that and says, “Stephen Curry is micromanaging how I point my feet.”

Because we understand the difference between controlling and coaching when it’s obvious skill development.

Construction is no different. If you’re teaching someone how to run a total station, use an automatic level, or manage a workflow, they don’t want vague encouragement. They want clear, detailed guidance.

And when they gain the skill, the leadership approach changes.

Leadership Tools Change by Phase: Forming, Storming, Norming, Performing

Jason also reminds us that leadership isn’t one style forever. It changes depending on where the team is in its development.

He references the classic phases:

  • Forming
  • Storming
  • Norming
  • Performing

A leader who is effective in forming might need to be more directive and structured. In storming, the leader might need to be both collaborative and decisive. In performing, a leader should step back, create space, and let the team run.

The mistake is thinking one approach fits every phase.

Directive leadership is a tool. Passive leadership is a tool. Collaborative leadership is a tool.

The job is to use the right tool at the right time.

Directive Leadership Is a Tool, Not a Lifestyle

Jason uses a construction analogy that hits: you can’t show up to set forms with only a hammer. You need a full tool belt cat’s paw, square, pencil, chalk box, and more.

Leadership is the same.

If you throw out directive leadership because someone on social media demonized micromanaging, you’re throwing away a tool you’ll need especially when training new people, stabilizing a new system, or protecting safety.

The problem isn’t directive leadership.

The problem is leaders who never transition from directive to enabling.

The Hidden Cost of Demonizing Micromanaging: Nobody Teaches Anymore

This is one of the most important parts of the episode.

Jason says demonizing micromanaging creates disconnection:

  • Apprentices don’t get taught because foremen fear being “too controlling.”
  • Foremen don’t get coached because supers fear the label.
  • Managers don’t help their teams because “hands off” looks virtuous.

But construction needs more shoulder-to-shoulder leadership, not less.

If you want people to grow, you must teach. If you want teams to improve, you must coach. If you want stable systems, you must guide implementation until it sticks.

Shoulder to Shoulder Support: What Construction Actually Needs

Jason talks from experience: he’s trained thousands of people field engineers, superintendents, foremen. People didn’t call it micromanagement. They asked for help because they wanted to get competent.

That’s the heart of it.

When the goal is competence and independence, coaching feels like support.

When the goal is compliance and ego, “coaching” feels like control.

So the fix is not “be less involved.”

The fix is: be involved the right way, for the right reason, with a clear training path.

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

Lead People, Manage Things: Why Clean, Safe, Organized Sites Require Management

Jason draws a sharp distinction:

You lead people. You manage things.

And there is nothing wrong with micromanaging things on a construction site in the literal sense cleanliness, safety, organization, logistics, signage, quality. Those require standards and management.

If a leader wants the site “perfectly clean, perfectly organized, perfectly safe,” that is not a character flaw. That is a professional expectation.

The mistake is applying that same management approach to people without training, trust, and enablement.

So, we don’t need less management. We need better leadership.

When “Micromanaging” Is a Symptom: Clarity, Trust, and Enabling

If someone says they’re being micromanaged, take it seriously but diagnose it correctly.

The real questions are:

  • Was the target clear?
  • Was there training?
  • Was there practice with guidance?
  • Did the leader enable independence?
  • Or did the leader hover without a system?

Because when leadership is clear, training based, and enabling, people don’t feel controlled. They feel supported.

And when leadership is reactive and unclear, even small guidance will feel like pressure.

The Real Crisis: Hands Off Leadership That Leaves People to Figure It Out

Jason closes with a controversial point: the United States doesn’t have a micromanaging problem. It has a hands-off problem.

Leaders leave people to figure things out. Teams get undertrained. Standards stay vague. Systems don’t get implemented. Then we wonder why performance is inconsistent.

A culture that’s afraid to coach is a culture that will keep repeating avoidable mistakes.

Conclusion

Stop treating “micromanaging” like the enemy.

The enemy is unclear leadership, missing training, and systems that never get taught.

Use directive leadership when the team needs it. Use coaching to build skill. Use the EDGE method to enable independence. Then step back when competence is earned.

FAQ

What’s the difference between micromanaging and coaching?
Coaching is structured skill building with a clear path to independence. Micromanaging, as people experience it, is usually control without clarity, training, or enablement.

What is the EDGE method Jason mentions?
EDGE stands for Explain, Demonstrate, Guide, Enable. It’s a teaching sequence where leaders build competence by showing the work, guiding practice, and then enabling autonomy.

Why do people complain about micromanagement on job sites?
Often they’re reacting to unclear expectations, constant reactive corrections, or leaders who hover without a training system. Sometimes it’s also resistance to standards and systems.

Should superintendents and foremen be directive sometimes?
Yes. Directive leadership is a tool. It’s required during onboarding, safety critical work, early team phases, and when implementing new systems then it should transition toward enablement.

How can a leader avoid being perceived as micromanaging?
Be clear about the target, teach the process, guide practice, and enable independence. When people see your intent is to help them succeed, guidance feels supportive instead of controlling.

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

Logistics Staging 2

Posted on by Danny Jiménez⁩
Read 19 min

Logistics 2.0: Build a Queuing Yard and Gate So Only the Right Materials Enter the Site

If you want to see where most projects lose money, don’t start by looking at the schedule.

Look at the dumpsters.

Look at the cardboard.

Look at the pallets.

Look at the telehandler running back and forth all day doing nothing but moving waste.

Jason Schroeder’s Logistics 2.0 concept is a simple shift with massive leverage: stop trying to manage logistics inside the building after chaos has already entered. Manage it at the entry. Control it before it hits production.

And do it in a way that makes work easier to start, easier to do, and easier to finish.

That’s not “nice.” That’s LeanTakt thinking applied to real world job sites.

Why Logistics Deserves More Attention Than It Gets

Jason says it plainly: logistics is one of the most important considerations on a project site, and it doesn’t get enough attention.

Most teams treat logistics like a background function. Something you deal with when it becomes a problem. Something you assign to “whoever is available” until it turns into a fire.

But logistics is not a support function. It’s a production system.

If the system brings materials into the building in bulk, with packaging, trash, uninspected items, and no zone logic, you are creating waste on purpose. You are guaranteeing extra handling. You are guaranteeing safety risk. You are guaranteeing lost time and rework.

So the question isn’t, “Can we manage it better in the field?”

The question is, “Why are we letting chaos enter the field at all?”

The Big Shift: Manage Materials at the Entry, Not in the Building

The core Logistics 2.0 move is this:

Build a queuing yard and a gate for logistics.

In other words, do not allow materials, trucks, and crews to go “rogue” on the project site and then try to manage the mess later. Bring materials into a controlled entry space where they get shaken out, inspected, kitted, and staged by zone.

Then and only then release them into the building.

Jason’s point is blunt and true: if you can’t manage it at a queuing yard, you can’t manage it in the field. And if you can’t manage it in the field, crews will spend their day tripping over waste and chasing materials instead of installing.

This is system first thinking. The people aren’t the problem. The system is flooding them with junk.

The Queuing Yard Concept: Flat Ground, Shop Forklift, and Grid Zones

Jason imagines a dedicated logistics entry area that is intentionally designed, not improvised.

Key detail: flat ground.

So flat that you can use a shop forklift to unload deliveries, instead of relying on a lull or telehandler bouncing over ruts and mud. He’s not saying those machines disappear. He’s saying the unloading and shakeout should happen in a controlled, stable environment.

He describes a gridded space where each trade has designated zones. He even gives a conceptual footprint something like 40 feet wide by 200 feet long where trade partner materials can be staged and processed.

This is not about exact dimensions. It’s about the principle: give logistics a workface.

Because right now, on most jobs, logistics has no workface. It has chaos.

What a Logistics Queuing Yard Must Include

To make Jason’s concept real, the queuing yard needs baseline features that support flow:

  • Flat, stable surface for unloading and shakeout
  • A shop forklift as the primary offload tool
  • Clearly gridded trade spaces (designated staging areas)
  • Recycling and waste dumpsters placed intentionally
  • A scrap metal bin and a clear discard routine
  • A “staging deck” side where kitted bins get queued for release

When this exists, the site stops acting like a landfill and starts acting like a production system.

Shakeout and Inspection: Remove Trash and Risk Before Materials Move

This is where most projects lose the plot.

They bring materials into the building still wrapped in packaging, strapped to pallets, full of cardboard, full of extra cuts, full of “we’ll deal with it later.”

Then later becomes:

  • The crew’s problem
  • The foreman’s problem
  • The safety team’s problem
  • The telehandler operator’s problem
  • The superintendent’s problem
  • The dumpster’s problem
  • The schedule’s problem

Jason’s approach is to shake out materials in the yard:

Break them down. Inspect them. Remove packaging. Sort waste into the right bins. Confirm you actually received what you ordered.

Then kit what’s needed, by zone, so what enters the building is only value.

This is the quiet secret of great logistics: the project doesn’t get cleaner by yelling at people. It gets cleaner by preventing trash from entering in the first place.

Bins by Zone: Kitting Work Packages for One Piece Flow in the Field

Here’s the kicker in Jason’s system: bins by zone.

Not bins by trade.

Not bins by “whatever came off the truck.”

Bins by zone or by grouping of zones so the crew receives a kit that matches the workface.

This is the center of one piece flow: plan it, do it, finish it. Plan, do, finish. If you deliver bulk, you batch. If you batch, you create variation, waiting, and confusion.

Jason describes a staging deck where bins are labeled with zone info, instructions, and a work package. He even imagines visual flags that show “ready to go.”

This is what workers actually need: a clear package they can install from without hunting.

The Plywood Deck and “Ready Flags”: A Simple Visual System for Release

A big mistake in jobsite logistics is treating the yard like storage.

Jason is describing it as a release system.

Materials get processed, put into bins, staged on the deck, and then released into the site when they are ready and needed. That’s a pull system, even if you don’t use the word.

The point is not to create a bigger pile. The point is to create a smarter stream.

And because it’s visual labels, zones, readiness markers the logistics lead can see what’s going, what’s stuck, and what needs attention without a spreadsheet fight.

Waste Out, Only Value In: Stop Hauling Cardboard and Pallets Through the Project

Jason calls it out directly: we should stop bringing cardboard, pallets, wood, packaging, and trash into the building and then hauling it back out again.

That double handling is silent budget murder.

It overloads your crane, hoist, forklift routes, elevators, corridors, and laydown areas. It slows installers down. It creates clutter and trip hazards. It burns supervision bandwidth. It makes crews hate the job.

Logistics 2.0 is about bringing into the building only what you need, just in time, per zone, per plan.

That one principle can stabilize everything.

The Logistics Gate: Onboard the Crew, the Truck, and the Materials

Jason goes one level deeper and says: it’s not enough to onboard people.

You need to onboard the truck and the materials.

He imagines a gate concept: crews and vehicles don’t just show up and go wherever they want. They go through a simple entry process that confirms baseline standards are met.

The objective isn’t to be controlling. The objective is to protect flow and safety by preventing rogue behavior and random dumping.

If the site is a system, the gate protects the system.

Standards at the Gate: What Gets You Authorized

Jason lists practical standards that would qualify a crew and vehicle to enter without constant supervision:

  • Crew completes onboarding and understands the system
  • Vehicle and tools are 5S’d and organized
  • Safety basics are verified (like a fire extinguisher)
  • Legal and insurance requirements are in place
  • Materials are shaken out and inspected before entering
  • No trash dumping and no bulk chaos entering the site

This is respect for people applied through standards: we protect workers by creating stable conditions.

Staffing the System: One Lean Logistics Lead and Repeatable Routines

Jason suggests this system could be run with one logistics person who is trained in Lean systems.

That’s not a “yard cop.” That’s not a “traffic controller.”

That is a production leader for material flow.

With basic supplies available straps, shrink wrap, tarps, labels, signage, paint, boards the yard becomes a kitting and release engine.

This is what’s missing on most sites: not effort, but design.

The ROI Logic: Less Handling, Less Forklift Time, Less Site Management

Jason throws out a rough idea that this could be pulled off for something like $30k plus one logistics lead, and he believes it would save significantly more by reducing waste.

Whether you agree with the numbers or not, the logic is solid:

  • Less double handling
  • Less equipment time wasted hauling packaging
  • Less labor time spent hunting parts
  • Less cleanup and safety management
  • Less crane and hoist overload
  • More installation time per hour worked

When crews install instead of search, the schedule improves without burnout.

Logistics That Brings Joy: Make Work Easy to Start and Easy to Finish

Jason uses a home improvement analogy that hits hard.

When you start a project at home and you don’t have the drill, the right screws, or the right tools, the job becomes miserable. You waste time. You run to the store. You get frustrated. The work feels heavier than it should.

But when everything is delivered, kitted, and ready, the job becomes fun. You flow.

That’s not soft. That’s operational.

Joy, in this context, means:

  • readiness
  • clarity
  • ease
  • stability
  • flow
  • respect for bodies and brains

If you can make logistics joyful, you can make production stable.

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

Conclusion

Logistics 2.0 is a system first solution to a predictable problem: we keep letting waste enter the project and then we act surprised when the field is drowning.

Build a queuing yard. Shake materials out. Inspect them. Kit by zone. Stage for release. Gate what enters. Protect the system. Then deliver only what is needed, when it’s needed, to the exact workface.

FAQ

What is a logistics “queuing yard” on a construction project?
It’s a designated entry area where materials are offloaded, shaken out, inspected, and kitted before they enter the building, so the site receives only what’s needed and avoids bulk waste.

Why kit materials by zone instead of by trade?
Because zone based kits match the workface. Crews can install directly from a bin without hunting, and it supports one piece flow instead of batching.

What does “shakeout” mean in Logistics 2.0?
Shakeout is breaking down deliveries in the yard, removing packaging, sorting trash, verifying quantities and condition, and preparing materials into install ready kits.

How does a logistics gate improve a job site?
It prevents rogue deliveries and chaotic dumping. It ensures crews, vehicles, and materials meet basic standards (onboarding, 5S, safety, inspection) before entering production areas.

Is this system only for large projects?
The exact layout may vary, but the principal scales: manage at the entry, remove waste before it enters, kit by workface, and release materials intentionally rather than flooding the site.Top of FormBottom of Form

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

Morning Worker Huddle 2.0

Posted on by Danny Jiménez⁩
Read 19 min

Construction Logistics Starts at the Gate: Redesign the Morning Worker Huddle to Create Flow

Most people talk about logistics like it starts at the laydown yard.

Or the hoist.

Or the crane pick plan.

Or the loading dock.

But Jason Schroeder makes a different argument here, and it’s one of those “why didn’t I see that sooner” moments:

Logistics starts at the entry gate.

Not the project gate where trucks come in. The human gate. The moment workers arrive, park, orient, queue, connect, learn, and then get released into production.

If we start logistics deep in the site, we miss the biggest leverage point: how the workforce begins the day.

And if you want flow, you have to design the beginning.

The Logistics Blind Spot: We Start Too Late and Too Deep in the Site

Most job sites spend real effort on logistics after the day has already begun.

They fight about deliveries. They scramble around access. They adjust for crews stepping on each other. They try to fix problems that were baked in at the start of the day.

Jason’s “universe revelation” is that the morning worker huddle is not a soft thing. It’s not a motivational add on. It’s not a nice to have.

It is a logistics control point.

If the workforce enters the site in chaos, they will build in chaos. If they start in discomfort, they carry it into the day. If they start disconnected, they act disconnected. If they start without clarity, you will get variation and waiting all day.

The beginning predicts the middle.

Masagura and Genkan: The Entry Gate and the Holding Box Concept

Jason introduces two Japanese words he’s used before: Masagura and Genkan.

He explains the origin story from visiting the Japanese imperial palace with Paul Akers. There were an entry gate and a holding box area a queuing space where visitors could be assessed. Friend or foe. Then the next gate opened only when it was appropriate.

Jason takes that pattern and applies it to construction:

  • A first entry gate where workers come in for the morning worker huddle
  • A queuing area where they gather, orient, and get ready
  • A second gate that opens only when the team is aligned and ready

The concept is simple: don’t release the workforce into production until the system is ready to support them.

The Parking Lot Is the First Workface: Leveling, Stalls, and Safety

Jason describes something most of us don’t treat like “logistics,” but it is:

The parking lot.

He imagines it leveled and gridded with clearly defined stalls and safe circulation so workers aren’t squeezing into chaos, getting dinged by vehicles, or starting the day stressed. He adds something practical: room to open doors, easy routes in and out, and a layout designed to prevent accidents.

This is not about being fancy. It’s about removing friction at the very first touchpoint.

Then he adds a baseline of dignity: restrooms, a hand wash station, and trash cans right there. Not hidden. Not “somewhere.” Right there.

This is what respecting workers looks like in logistics terms: design the first five minutes.

Wayfinding Without Visual Pollution: Simple Signs That Actually Help

Jason calls out something that matters: wayfinding without “visual pollution.”

In other words, don’t plaster the fence with chaos. Don’t overwhelm people with noise. Give simple, clear signage that tells people what they need, where to go, and what to do.

When information is hard to find, workers waste time and patience trying to interpret the site.

When information is clear, the workforce flows.

Wayfinding is logistics.

The Queuing Area: Comfort, Dignity, and Readiness Before the Day Starts

This is where Jason gets really specific.

He describes a queuing area that’s leveled and clean so workers are not standing in mud, cold, or misery. A place where the worker huddle boards live. A place where there’s a stage, a microphone, and the tools to communicate clearly.

Then he asks the question most job sites never ask:

Why are workers standing out there freezing or baking?

If you can design a staging area for materials, why can’t you design a staging area for people?

Warmth and Cooling as a System: Heaters, Misters, and Practical Setups

Jason shares a simple example: a propane heater from Home Depot that heats a meaningful radius. He imagines having multiple heaters available so workers who want warmth can get it.

He also notes that in hot climates, misters around the perimeter could help. The point isn’t the specific tool. The point is the principle:

Comfort is not “extra.” It’s a production strategy.

When workers start the day physically miserable, you are wasting their energy before they even begin the work.

Coffee, Water, and Small Wins: Why Tiny Investments Change Behavior

Jason starts brainstorming something that feels almost too simple to say out loud:

What if workers wanted to be there?

He talks about coffee, water, ice, maybe small snacks. Not because you’re bribing people. Because you’re creating an environment that signals, “You matter,” and, “We’re ready,” and, “We’re a team.”

Then he asks a practical question: what would coffee cost over the lifecycle of a job? He throws out a number like $1,500 and points out how small that is compared to the waste we tolerate daily.

The point is not coffee. The point is the math of respect.

Small investments can create outsized engagement.

The Worker Huddle “Dojo”: Training Stations That Teach the Standards

This is the most powerful part of the vision.

Jason describes a “dojo” setup training stations in the queuing area where the team can teach standards visually, quickly, and repeatedly.

He gives examples:

  • A bathroom/hand wash station setup you can point to and teach cleanliness standards
  • A crew huddle board and how to use it
  • A pre kitted set of parts and bins to demonstrate material handling standards
  • Signage examples so workers know what to look for around the site
  • Safety demos like hardhat impact tests or fall protection displays
  • Occasionally pulling equipment forward (forklift, excavator, key tools) to teach correct interaction

This is the missing link for most projects: we expect people to comply with standards they were never taught in a way they can see.

Training isn’t an email. Training is a visual, physical practice environment.

Dojo Stations to Teach the Standard

If you were to build a simple worker huddle dojo, Jason’s examples translate into stations like:

  • “How we keep restrooms clean here” station
  • “How to read and use the crew board” station
  • “How we pre kit, bin, pallet, and label materials” station
  • “Our standard signs and what they mean” station
  • “Safety demonstration / PPE standard” station
  • “Equipment interaction basics” station

These stations turn the morning huddle into skill building, not just announcements.

The Second Gate: Don’t Release the Workforce Until the Team Is Ready

Jason ties it back to the Masagura and Genkan concept.

If the team is distracted, disengaged, or not aligned, you don’t open the second gate.

If the huddle isn’t clean, organized, and respectful, you don’t release the day.

If the plan isn’t clear and the workers don’t have access to it, you don’t pretend it’s “fine.”

You stage, align, train, and then you release.

This is not about control. It’s about stability.

Release Criteria for the Second Gate

Jason’s logic implies a simple “release checklist” before the workforce disperses:

  • Workers understand the plan and key change points
  • People have access to the plan (QR code / boards)
  • Roadblocks are surfaced and owned by someone
  • Standards are reinforced (safety, cleanliness, organization)
  • The environment is respectful and ready (no chaos, no trash, no confusion)
  • The team shows readiness and alignment before dispersing

If you release crews without this, you’re releasing variation.

Make It Interesting: Designing for Attention and Buy In

Jason shares an insight that is less about logistics and more about learning.

He talks about the difference between doing something for dopamine reward versus doing something because it’s interesting. Then he asks a question leaders should ask more often:

How do we make the morning worker huddle interesting?

Not gimmicky. Not childish. Interesting. Visual. Useful. Engaging.

If workers wanted to be there without being forced, what would you design?

That question alone will change how you think about logistics, leadership, and culture.

Orientation as Logistics: How New Workers Learn “How We Do It Here”

Jason also connects this to onboarding.

If you have a dojo area and visual standards, then when new workers arrive, you can show them:

  • how bathrooms are cared for
  • how hand wash stations are maintained
  • what cooling and heating stations look like
  • how to interact with boards and plans
  • how material handling is done here
  • what the signage means across the job

That is the fastest way to protect culture and stabilize performance: show people what “good” looks like on day one.

Why This Beats Everything Else: The Morning Worker Huddle as the Biggest Opportunity

Jason makes a bold claim:

“The morning worker huddle is the most misunderstood, not used, and largest opportunity in the entire world of construction.”

You can argue with that if you want. Most people do. He even calls it out: people fight, argue, and dismiss the idea.

But the logic is hard to escape. If you could start every day with connection, clarity, training, and readiness and then release workers into a stable plan what would happen?

Quality would improve. Safety would improve. Coordination would improve. Stress would drop. Families would get more stable schedules. Workers would feel respected. The entire project experience would change.

That is logistics.

And it starts at the gate.

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

Conclusion

If you want a logistics breakthrough, stop starting logistics at the laydown yard.

Start it where the workforce starts.

Design the entry gate. Design the queuing area. Design the worker huddle. Teach standards visually. Make the plan accessible. Release the workforce only when the system is ready.

FAQ

What does Jason mean by Masagura and Genkan on a job site?
He’s describing an “entry gate” and a “holding box” concept: workers enter a queuing area for alignment and training, and the workforce is released into production only when the team is ready.

Why is the parking lot part of construction logistics?
Because it’s the first workface for the workforce. If parking, wayfinding, and basic services are chaotic, the day begins with friction, stress, and wasted time before work even starts.

What is a worker huddle “dojo”?
It’s a set of visual training stations near the worker huddle where leaders can teach standards (cleanliness, boards, material handling, signage, safety) in a practical, repeatable way.

Why does Jason suggest coffee and comfort items at the huddle?
Not as a gimmick, but as a small investment that signals respect, increases engagement, and improves readiness. Comfort and dignity help crews start the day aligned and focused.

How does the “second gate” concept improve flow?
It prevents releasing the workforce into chaos. If the plan isn’t clear, standards aren’t reinforced, and roadblocks aren’t surfaced, releasing crews increases variation. The second gate opens only when the system is ready.

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

PMs, Shield Them from Toxic Variation, Not Growth

Posted on by Danny Jiménez⁩
Read 17 min

What Project Managers Should Shield the Team From (and What They Must Not)

There’s a phrase I hear all the time on job sites:

“This is just a lot of change for the job site team.”

Usually, it’s said with good intentions. The project manager is trying to “protect” the project delivery team. They don’t want people overwhelmed. They don’t want morale to drop. They don’t want the team frustrated.

But here’s the problem: we’re mixing two very different categories of “change.”

Some change is toxic. Some change is necessary. Some variation should be blocked. Some variation must be embraced. If we don’t sort those categories correctly, we end up doing the opposite of what we intended: we shield teams from growth, and we expose them to waste.

This episode is Jason Schroeder making that distinction as clearly as he can, because it impacts the quality of the work, the health of the team, and the long-term capability of the organization.

The “Too Much Change” Complaint: Why It Shows Up on Every Job

Human beings will complain when things change.

That’s not negativity. That’s wiring. Jason explains that as soon as something changes, your brain will automatically generate resistance:

  • “It’s too expensive.”
  • “We don’t have the people.”
  • “We don’t have the time.”
  • “My boss isn’t doing it, why should I?”
  • “It doesn’t apply to me.”

That’s normal. Just like we’re wired to be fearful, we’re wired to be resistant to change. The mistake is treating that initial resistance as a reason to stop improving.

If we “sympathy vote” the team into stagnation just because the brain complains, we are not protecting people. We are limiting them.

Change Isn’t the Enemy: Variation Is

Jason makes a statement that’s worth repeating:

“Change is not the problem. It’s certain types of variation that are bad.”

Think about what we build. If you’re building a stadium, a museum, a hospital, an airport, a school, or a complex commercial building, everything is different. Different assemblies. Different conditions. Different constraints. Different sequences. Difference is normal in construction.

The reason construction can still work is because we have standard systems for dealing with that difference. We use repeatable planning routines. We use standard approaches for layout, safety, quality, production control, and coordination.

The problem is when process change shows up without a standard way to handle it. That’s when variation becomes destructive. That’s when things start to take longer. That’s when people get overloaded and quality suffers.

That’s also why a project manager has a real responsibility: to filter harmful variation out of the system.

What a PM Should Shield the Team From: Toxic Variation in the System

A project manager should absolutely shield the project delivery team from toxic variation.

Jason gives clear examples. If there are excessive owner changes, shield the team. If there is a toxic owner, shield the team. If change orders are out of control and you need resources, shield the team and add support. If there’s RFI churn that keeps dumping uncertainty into the field, shield the team and stabilize the inputs.

This is not about hiding reality. It’s about controlling the inputs so the team can execute with stability. That is respect for people. That is leadership.

Symptoms of Toxic Variation to Shield the Team From

Here are the patterns Jason is pointing to when he says “shield the team”:

  • Owner driven changes that constantly disrupt the plan
  • Toxic interactions that create fear, drama, or emotional chaos
  • Excessive change orders without added resources
  • Too many RFIs and unresolved information churn
  • Overburden and unevenness created by bad upstream decisions
  • External noise that forces the team to react instead of build

Toxic variation isn’t “hard work.” Toxic variation is waste entering the system and being dumped on the people.

Owner Chaos, Excessive Changes, and RFIs: How to Protect the Field Without Hiding Reality

A good project manager doesn’t pretend the chaos isn’t happening.

A good project manager absorbs it, filters it, and converts it into stable execution conditions for the field. That might mean consolidating changes before releasing them. That might mean pushing back on the owner until there is clarity. That might mean protecting the superintendent from constant re direction. That might mean adding resources to cover the demand being created.

Shielding is not avoidance. Shielding is system design.

And it’s one of the most indispensable roles a great project manager plays.

What a PM Must Never Shield the Team From: Learning, Training, and Growth

Here’s the core point of the episode.

Project managers should never shield their teams from:

  • growing
  • learning
  • reading
  • training
  • improving
  • implementing the base systems needed for the job

If a project manager tries to keep the team “comfortable” by refusing to implement the core systems, refusing to train, refusing to learn, refusing to improve, and refusing to upgrade the way the team runs meetings and production control, the project gets stuck in mediocrity.

And it will waste more time than it ever “saved” by avoiding change.

Jason frames it clearly: toxic external variation should be excluded, but internal growth variation must be allowed. If we block the growth, we block excellence.

Growth Variation You Must Not Block

This is the kind of “change” that looks hard at first, but pays back forever:

  • Implementing the base meeting cadence and production control system
  • Doing a book challenge, reading challenge, or learning routine
  • Training that helps the field execute the plan with confidence
  • Coaching that increases capability and consistency
  • Continuous improvement work that upgrades the process
  • Standard systems that reduce firefighting and chaos

This is not “extra.” This is the pathway out of waste.

Base Systems Aren’t Optional: Why “Shielding” Becomes Mediocrity

Many teams lose years because they never install the basics.

They don’t want the discomfort of change. They avoid training because it feels like “too much.” They avoid upgrading meetings because it feels like “a lot.” They skip the core systems and try to compensate with effort.

But effort doesn’t create flow. Systems do.

When we don’t implement base systems, we don’t avoid variation. We increase it. We create bigger rework cycles. We create more stress. We extend durations. We burn people out.

If the plan requires burnout, the plan is broken.

Distress vs Eustress: The Kind of Pressure That Builds People

Jason makes a key distinction: distress is toxic, but stress can be good.

Distress is when you are criticized, pressured, pushed, or overloaded without support. Distress damages people and damages performance.

Eustress is positive stress. It’s when the team rallies toward a challenge they can rise up to. It’s when learning and growth happen with support. It’s when the project needs the team and the team steps up together.

Project managers must learn to shield teams from distress while not protecting them from eustress. Growth requires challenge. The key is that the challenge is supported and meaningful.

The PM’s Real Role: Remove Toxicity, Build Capability

Jason gives project managers a clear shout out: a good project manager is indispensable.

But the job is not to keep the team from feeling uncomfortable. The job is to remove toxic inputs and build capability inside the team.

That means:

  • filter owner chaos
  • stabilize information flow
  • protect the team from waste and overburden
  • and then push learning, training, and improvement intentionally

This is how you protect people and still raise the bar.

Japan’s Pattern: Why “People, Process, Quality” Beats Money and Goals

Jason references a key refrain from Paul Akers during the Japan trip:

“Why is Japan, Japan? Training.”

And he highlights the focus:

People. Process. Quality.

Not money and goals first. Those outcomes come after. The way to rise to excellence is to build people and build process so quality becomes predictable.

If we want to rise to operational excellence, we must stop shielding teams from learning and start shielding them from waste.

The PM Decision Filter: Shield or Share?

Here is a simple decision filter that matches the message in the transcript:

  • If it’s waste, overburden, or unevenness, shield the team and stabilize it.
  • If it’s training, growth, learning, and base system implementation, do not block it.
  • If it’s toxic inputs, absorb it, filter it, and protect the field.
  • If it’s positive change, lead it, support it, and train toward it.

This is how you protect people and still improve.

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

Conclusion

Project managers are not the problem. Confusion about what to shield teams from is the problem.

Shield your team from toxic variation. Shield them from waste. Shield them from overburden. Shield them from unevenness that will grind them down.

But never shield them from learning.

FAQ

What should a project manager shield the team from?
A project manager should shield the team from toxic variation like owner chaos, excessive changes without support, RFI churn, and any wasteful overburden that destabilizes flow and increases stress.

Is change bad on a construction project?
Not inherently. Construction is full of difference and change. The problem is harmful variation without a standard way to manage it, which increases duration and creates instability.

What should a project manager not shield the team from?
A project manager should not shield the team from training, learning, implementing base systems, and continuous improvement. Those are positive changes that build capability and reduce waste long term.

What’s the difference between distress and good stress?
Distress is toxic pressure, criticism, and overburden without support. Positive stress is a challenge the team can rise to with clarity, training, and support, leading to growth and improvement.

Why does Jason mention Japan and training in this context?
Because the pattern emphasized is people, process, and quality. Training is a core driver of excellence, and teams should be protected from waste, not from growth.

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

POND, Not POD Meeting

Posted on by Danny Jiménez⁩
Read 21 min

The POND Meeting: Plan the Next Day to Reduce Variation and Create Flow

Most job sites have a “daily huddle.” Most of them are also wasting that moment.

Not because the intent is bad. The intent is usually good. People want connection, coordination, and a plan. But what Jason Schroeder describes in this episode is what many of us have seen: the daily huddle turns into roll call.

“Hey, I’m in this area with three people.”
“Hey, I’m in this area with five people.”
“Hey, we’re over here with six.”

It sounds organized. It feels like accountability. But it rarely creates flow. And it almost never creates a real plan.

This is why Jason makes a bold statement: the morning huddle is one of the most distracting concepts taught in Lean construction not because the idea of meeting is wrong, but because the industry locked the format in place and never improved it.

The fix is not to cancel huddles. The fix is to shift them into a system that actually plans, communicates, and executes with stability.

Why the Typical Morning Huddle Fails the Field

A same day “plan of the day” meeting often fails for two reasons.

First, it doesn’t plan anything. It reports where people are. That’s status, not production planning. It might help the GC know how much labor is supposedly on site, but it does not reliably coordinate change points, handoffs, constraints, or needs.

Second, when teams try to use the morning of meeting to “plan,” they frequently change the plan right before work begins. That increases variation and destabilizes production. The field gets whiplash. Foremen have no time to properly sequence work. Crews lose confidence in the plan because the plan is always moving.

If the plan changes morning of, you didn’t plan. You improvised.

POD vs POND: The Small Shift That Changes Everything

Jason clarifies the language: some people say POD Plan of the Day. But he makes the case for POND Plan of the Next Day.

That shift in timing changes everything.

When you plan the next day in advance, you give foremen time to actually think, coordinate, and make ready. You give trades time to surface roadblocks while there is still time to remove them. You reduce morning chaos. You build stability into the system.

And once the team starts operating this way, the job begins to feel different. Not “busy.” Stable. Predictable. Flowing.

The Real Purpose: Plan, Not Roll Call

The purpose of the POND meeting is not to hear where everyone is standing today.

The purpose is to make tomorrow stable.

A good POND meeting does three things:

  • Locks the plan for tomorrow in a “day tight compartment”
  • Surfaces roadblocks early enough to remove them
  • Coordinates change points and handoffs so trades can flow

That means we stop treating daily planning as a ceremonial meeting and start treating it as a production system.

What a POND Meeting Must Include

If your POND meeting doesn’t include these, it will drift back into roll call:

  • A clear focus on tomorrow (not today) and what must be ready
  • Visuals that show zones, logistics, and current conditions
  • A structured moment for trades to surface roadblocks and ask for help
  • A conversation about handoffs and change points, not just manpower counts
  • A visible link to the weekly work plan, so daily work stays aligned
  • A way to publish the plan to the field so every worker can see it

A POND meeting without visibility and roadblocks is just a meeting.

A Rolling Meeting Cadence That Creates Flow

Jason describes building a rolling cadence of meetings where each meeting supports the next one, creating a seamless system for the field.

Here’s the rhythm he lays out:

  • POND meeting (plan of the next day)
  • Morning worker huddle with stretch and flex (communicate the plan to the workforce)
  • Short team daily huddle/standup (5–15 minutes, often with Kanban, for the project delivery team)

That cadence creates flow because planning happens early, communication happens clearly, and the team’s daily standup is used for real support work not chaos management.

This is what “plan, communicate, execute” looks like as a system, not a slogan.

What Goes on the Screen: Weekly Work Plan + Aerial Zone Map

To improve the POND meeting, Jason describes how the visuals were redesigned.

The team moved the visual logistics and zone maps to one side of the screen and the macro level attack plan to the other. They pulled up the weekly work plan (from Intakt) and showed the most recent aerial photo with logistics and zoning overlaid.

That matters because people plan better when they can see reality.

When the team sees the zones, logistics, access points, and current site conditions, they stop talking in abstractions. They stop guessing. They start coordinating around what is actually possible tomorrow.

Roadblocks First: How Visual Maps Change the Meeting Dynamic

Jason describes a key move that changes the entire meeting.

Before the meeting, trades mark on the visual maps their problems and roadblocks. Then when they come up to speak, they don’t just say where they are. They say what’s blocking them and what they need.

That shift is huge.

Now the meeting becomes a place where constraints are surfaced, the GC and trades can help each other, and reroutes can happen early. Instead of “we’ll deal with it tomorrow,” the team deals with it today so tomorrow can flow.

Roadblock Prompts to Use with Trades

If you want the meeting to stop being status and start being planning, use prompts like these:

  • “What is the one thing that could stop you tomorrow, and who can help remove it?”
  • “Where is your handoff tomorrow, and what do you need from the trade before you?”
  • “What access, layout, inspection, or material constraint is still unresolved?”
  • “If you had to reroute your plan, what is your next best option?”
  • “What change point tomorrow requires coordination with another crew?”
  • “What do you need from the GC today so tomorrow is day tight?”

These questions force real planning without blaming anyone.

From Plan to Workforce: QR Codes, Translation, and Real Connection

The POND meeting only matters if the plan reaches the workforce.

Jason describes a system where the day plan is created in Canva and automatically shows up via QR code in the field. Every worker can see the plan not just the foremen. Then the team creates a social group so communication stays consistent.

He also gives an important shout out: the morning worker huddle was done with genuine appreciation, workers actually leaned in because they cared, and there was English and Spanish translation. The superintendent talked about change points, did two minutes of training, and communicated clearly.

That’s what “respect for people” looks like as a production strategy: clarity, training, and support.

Day Tight Compartments: Why Changing the Plan Morning of Adds Variation

Jason makes a key production point: if you change the plan the morning of, you increase variation.

He calls out the law of the effect of variation: variation extends your project and destabilizes the day. When you change the plan right before executing, you create ripple effects material issues, access conflicts, crews stepping on each other, and unnecessary waiting.

But there’s another trap he calls out.

If you don’t change the plan in a morning of huddle, then you’re often just doing roll call and that’s useless. So the industry gets stuck in a lose lose: change the plan and create chaos, or don’t change it and waste time.

That’s why the plan has to be made the day before.

What to Do the Morning of Instead: A Short Team Standup with Kanban

Jason isn’t saying “no morning meeting.”

He’s saying the morning meeting should be different.

After the POND meeting locks tomorrow’s plan and the worker huddle communicates it to the workforce, the project delivery team can hold a short standup five to fifteen minutes often using Kanban.

The purpose is simple:

  • Identify key needs for that day
  • Clear key problems and roadblocks
  • Support flow based on what was surfaced in the POND meeting

That is the right use of morning time: clearing constraints, not rewriting plans.

Lean Behaviors 1.0 and 2.0: Training the Team Every Day

Jason describes adding two visuals Lean behaviors 1.0 and Lean behaviors 2.0 and using them as daily training topics.

This is one of the most overlooked parts of operational excellence: teams don’t magically improve because they want to. They improve because the system trains and reinforces better behaviors daily.

If the meeting cadence includes micro training and consistent expectations, the project gets better and better because learning becomes built into the work.

How to Implement Fast Without Overwhelming People

Jason notes that some people initially said, “This is a lot of change.”

But the team implemented it in a day.

That’s important: the system does not require months of “change management.” It requires clarity, the right visuals, the right cadence, and a willingness to try.

He also describes a feedback loop: meetings are recorded, uploaded internally, and Jason gives feedback daily. That’s short cycles, frequent iterations, and fast learning exactly how Lean is supposed to work.

Common POD Mistakes That Increase Variation

If you want your POND system to work, avoid these common traps:

  • Planning the same day and constantly changing the plan morning of
  • Not surfacing roadblocks in the meeting
  • Giving foremen no time to actually plan tomorrow
  • Using the meeting as a manpower count instead of coordination
  • Failing to publish the plan so only a few people “know” it
  • Skipping handoffs and change points, then reacting to conflicts later

These mistakes don’t mean people don’t care. They mean the system isn’t designed for flow.

What Operational Excellence Looks Like in the Wild (and Why It Works)

Jason makes a strong claim: this is how operationally excellent projects run.

He references major builders and examples of clean, organized, safe projects where planning happens the day before. He also ties it to Japan and the way Lean systems create stability through advance planning and clear communication.

The point isn’t to name drop. The point is to give you a benchmark: what you’re trying to build is not theoretical. It’s already being done on high performing projects.

And you can do it, too.

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

Conclusion

If your daily huddle is rolling call, you’re not planning. You’re just meeting.

If your daily huddle changes the plan morning of, you’re injecting variation into the day and paying for it with waiting, conflict, and stress.

The fix is simple and powerful: plan the day before, publish the plan, surface roadblocks early, and use the morning time to support flow.

FAQ

What is a POND meeting in construction?
A POND meeting is a Plan of the Next Day meeting where foremen and the project team coordinate tomorrow’s work, surface roadblocks, and lock in a stable day plan before crews arrive.

How is a POND meeting different from a POD meeting?
A POD (Plan of the Day) meeting often happens the morning of and becomes either roll call or last-minute replanning. A POND meeting happens the day before, giving the team time to make ready and reducing variation.

Why is changing the plan the morning of a problem?
Changing the plan morning of increases variation, destabilizes production, and creates ripple effects like waiting, access conflicts, and missed handoffs. Planning the day before protects a “day tight compartment.”

What should be discussed in a POND meeting?
Focus on tomorrow’s plan, roadblocks, handoffs, and change points. Use visual logistics and zone maps and tie the conversation to the weekly work plan so the day stays aligned.

What meeting should happen the morning of if POND is done the day before?
Do a short (5–15 minute) team standup often with Kanban to clear roadblocks and support the field based on what was surfaced during POND, then communicate the plan to workers in a structured worker huddle.

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

Elevate & LeanTakt Principles

Posted on by Danny Jiménez⁩
Read 28 min

27 Elevate and LeanTakt Principles: How We Lead, Learn, and Build People

Most companies talk about culture like it’s a poster on the wall.

But culture is not a poster. Culture is a system.

It’s the repeated behaviors that show up under pressure. It’s what people do when no one is watching. It’s what leaders tolerate, reinforce, and protect. And if you don’t define it on purpose, you’ll get whatever shows up by default.

In this episode, Jason Schroeder shares the Elevate Construction and LeanTakt principles exactly as he recorded them for the internal team. These principles were inspired by what Paul Akers does at Fast Cap and by lessons learned through Lean thinking, including a visit to Japan. They are designed to be lived, practiced, improved, and protected.

Why Principles Matter: Culture Is a System, Not a Slogan

Principles aren’t here to make us feel good. They’re here to make us consistent.

When teams don’t have shared principles, they rely on personalities. That’s when projects become unpredictable, decisions become emotional, and performance depends on who is in the room. Principles are the operating system that keeps the team stable even when conditions change.

Jason describes these principles as something that can be modified over time, but they are meant to encapsulate how Elevate thinks and how Elevate behaves. They are not theoretical. They are practical guardrails that shape leadership, teamwork, improvement, and flow.

And if you want to understand what Elevate Construction and LeanTakt stand for, these 27 principles are the simplest window into the system.

Elevate and LeanTakt Principles at a Glance

These are some of the core themes you’ll see repeated across the principles:

  • We build people first, and that drives everything else.
  • Leadership is clarity, training, and support shoulder to shoulder.
  • We don’t blame people; we blame systems and fix environments.
  • We move fast in short cycles with frequent check ins.
  • One piece flow and transparency are non-negotiable.
  • We protect culture through respect, standards, and teamwork.

These are not “nice ideas.” They are production strategies.

The First Principle: Encouragement Is Oxygen for an Organization

Jason starts with a powerful concept: “The breath of an organization is positive encouragement.”

He explains it like this: an organization needs breadth to have life, and it needs to breathe to stay alive. If people don’t feel encouraged, morale dies. Culture dies. Joy dies. And when the culture dies, performance is not far behind.

This principle is also deeply practical. Encouragement is not fluff. It’s what gives people the resilience to try again, learn, grow, and improve. If leadership is not actively encouraging people, the system is starving the organization of oxygen.

Leadership Defined: Clarity, Training, and Support Shoulder to Shoulder

This is one of the cleanest leadership definitions you’ll ever hear in construction.

Jason says leadership is clarity, training, and support shoulder to shoulder. Leaders provide clarity. Leaders train people toward that clarity. Leaders help people reach the target.

That matters because most leadership confusion comes from people thinking leadership is “authority,” “charisma,” “pressure,” or “control.” Elevate’s definition is simpler and more useful: if you provide clarity, if you train, and if you help people, you are a leader.

This principle also aligns with Lean: hard on the process, easy on the people. If leaders do their job, people are not forced to guess. They aren’t left alone. They aren’t punished for system failures. They are coached and supported toward a clear destination.

Team Over Hierarchy: Learn From Everyone, Act as One

Elevate does not want a hierarchical feel.

Jason emphasizes learning from everyone and acting as a team. That’s what makes the company different. When people are listened to and leadership gets better at using the genius of the group, performance rises and trust grows.

The practical takeaway is simple: if you want results, you have to create a system where truth can travel upward. The people closest to the work see the problems first. If they can’t speak, the system becomes blind. That’s why learning from everyone is not “kindness.” It’s operational intelligence.

It’s About People: We Build People Who Build Things

This principle sits at the center of the entire list.

Jason says, “We are not here to build projects… We are here to build people…”

That’s not marketing language. That’s a decision filter.

Elevate is not here because of a goal. Elevate is not here just to provide a product. The work is consulting, but the mission is building people. Jason even uses a simple analogy: if the company sold ice cream, the mission would still be building people and the ice cream sales would fund it.

This is the principle that protects dignity. It’s the principle that prevents burnout. It’s the principle that keeps respect for people at the core.

Giving and Sharing: Why We Refuse to Hide Knowledge

“We are givers. Give, give, give, give, and share.”

This is a core operating philosophy at Elevate and LeanTakt. Jason says there is no value in hiding or holding. The world changes when we share. Anything that doesn’t need to be charged for should be given away, even if people think it’s ridiculous.

This principle is also aligned with how Elevate shows up publicly. Tools, templates, teaching, and guidance are shared widely because the goal is not scarcity. The goal is impact. And when the industry gets better, workers and families benefit.

Inventors by Default: Innovation as a Daily Expectation

Elevate sees itself as inventors of products and processes.

Jason says the company is research and development first. Innovation is not a quarterly initiative. It’s a daily expectation. The team used to call themselves process improvement engineers and shifted to “lean engineers” because it better encapsulated what they do and how the work translates professionally.

This matters because invention is how systems improve. And systems improving is how people’s lives improve. If you don’t invent, you repeat.

Training and Practice: Why Skill Beats Experience

Jason emphasizes a principle that separates high performing systems from average ones: training, education, practice, and implementation are key.

“You will not rise to your ambitions. You will fall to the level of your training.”

Training isn’t a perk. It’s the foundation. It’s how you build consistency. It’s how you reduce stress. It’s how you prevent “tribal knowledge” from being the only way people succeed.

This is also why Elevate believes it can train anyone. Experience can be useful, but it can also come with bad habits. Training creates the common language and the common standard.

Move Fast Together: Change Isn’t the Problem, Confusion Is

“We move fast. We learn fast. We change fast.”

Jason makes a key point: change itself usually isn’t the problem. The problem is failing to go together and failing to be clear. When people know where they’re going and they are supported, change becomes manageable.

He even gives a simple tactic: set a timer, grab a video, and learn the new thing. Most resistance is a failure to start, not a true inability.

Professionalism Everywhere: Show Up Ready, Then 5S the World

This is where the principles become visibly practical.

Jason shares a story: the team bought plungers, scrub brushes, and cleaning kits at Target for the USF Manhattan Project because the bathrooms lacked basic supplies. Then they planned to go in and 5S the conference room, kitchen, and bathroom.

Why does that matter?

Because it demonstrates professionalism. It demonstrates competence. It demonstrates that the team doesn’t just talk Lean they apply it in real spaces. Elevate shows up in clean, professional PPE, communicates well, and improves the environment wherever they go. That’s how trust is built: not through claims, but through visible action.

System First Diagnosis: Blame Process, Never the Person’s True Self

This principle is foundational for how Elevate thinks about performance and mistakes.

Jason says Elevate blames the system, process, environment, culture, behavior, prompting, or genetic wiring but never the person’s true self. If someone is struggling, the first move is not “that person is bad.” The first move is to examine what’s influencing behavior and performance.

This is a dignity principle and a production principle. When you blame people, you hide problems. When you blame systems, you expose causes and you can actually improve.

Jason also notes that if someone is not a fit and wants to leave, the company will help them find work elsewhere. That is aligned with respect for people. The goal is not to “throw people away.” The goal is to find fit and build success.

Culture Behaviors We Protect

These principles show up as real behavioral expectations inside the system:

  • Stop, call, wait when something is wrong and ask for help
  • Bring all problems to the surface instead of hiding them
  • Use short cycles with early check ins instead of waiting until the end
  • No punishment or discipline clarity, training, and support instead
  • Feedback as improvement and compliments, not criticism
  • Transparency as the only environment where the system works

These behaviors are how the culture protects itself under pressure.

Protecting Culture: Alignment Without Tearing Things Down

Jason is clear: it is okay to make mistakes and the company will train people. But the company will not allow dissent that tears down the culture.

This is not about control. It’s about respect. Coming into a culture and trying to destroy it is disrespectful and beneath human dignity. If someone does not align, they should say so and find a better fit rather than tearing down what others are building.

That’s how you protect the system. That’s how you protect people.

Stop, Call, Wait: Asking for Help Is a Requirement

This principle is one of the sharpest lines in the list.

If something is wrong, you stop, call, and wait. You ask for help. You don’t hide. You don’t pretend. You don’t “prove yourself” by suffering silently. That behavior is not aligned with the culture.

This is how you prevent small problems from becoming big problems. It’s also how you build trust: people know they won’t be punished for surfacing issues. They’ll be supported.

Short Cycles and Iterations: Early Check ins as Respect

Waiting until the end is disrespectful.

Jason emphasizes that work should be delivered in short cycles with frequent iterations and fast check ins early and often. If someone wait a month to deliver a final, the risk is that it misses expectations and wastes time. Frequent iterations allow alignment while the work is still in motion.

This is Lean thinking applied to knowledge work. It’s also respect for the customer and respect for the team.

Mistakes: Sloppy Isn’t OK, Learning Mistakes Are

Not all mistakes are equal.

Jason draws a clear line: sloppy mistakes from ignoring the process are not okay. Mistakes made while sincerely following the process and doing your best are okay even a million times. Those are learning mistakes.

This principle protects standards without punishing people. It reinforces that the system is the pathway. If you disregard the system intentionally, you create waste and disrespect the team and the brand. If you follow the system and learn, you are exactly what the culture is designed to support.

Bring Problems to the Surface: Visibility Before Fixing

One of the most compelling parts of the principles is how direct Jason is about problem visibility.

He says everyone has problems. Families have problems. Businesses have problems. The world has problems. The only difference is whether we can see them and fix them.

He gives a strong analogy: if you had stage one cancer, would you want to know right away or wait until it’s terminal? The answer is obvious. Bring problems to the surface so they can be addressed early.

No Punishment: Respect Through Clarity and Support

Elevate does not believe in discipline or punishment.

The belief is clarity, training, helping, and respect. This is a major distinction from traditional construction culture where “accountability” gets used as a weapon.

At Elevate, accountability looks like clear expectations, training, feedback, and support. It’s growth based. It’s human. And it is more effective because it aligns with how people actually improve.

Cut the Waste: Emails and Non-Value Add Admin

Jason states it plainly: the industry does a lot of “absolute garbage” non value add administration.

Elevate does not believe in emails as a default operating system. It does not believe in useless paperwork and wasteful admin. This aligns directly with Lean: if it does not add value, stop doing it.

The point isn’t to be rebellious. The point is to protect time and attention for work that actually helps people and improves outcomes.

Don’t Waste Time: Mewaku and Respect for Others

Jason references a Japanese concept: mewaku, don’t be a burden to others.

This principle pushes the team to respect time, reduce friction, and avoid unnecessary work that steals attention from real priorities. Wasting time isn’t a small issue. It’s a dignity issue. It’s a respect issue. It’s a production issue.

Clean, Safe, Organized: The Visible Signature of Lean

Wherever Elevate goes, the team organizes, tidies, and improves safety. This is a visible signature.

People see it and think, “These people have it together.” That matters. It builds credibility. It also builds stability. Clean, safe, organized environments reduce stress and errors, which protects people and improves performance.

Team Success Only: No Lone Geniuses

Jason is emphatic: individuals do not exist here in the way construction culture often imagines.

The idea of a lone genius is a myth. Even if someone is visible publicly, what you see is a team. Decisions improve with the team. Outcomes improve with the team. The company succeeds as a team or not at all.

That is a leadership principle and a humility principle, but it’s also operational truth.

One Piece Flow: Plan, Do, Finish

Jason says one piece flow is at the center of everything.

Plan something, do it, finish it. Plan, do, finish. If the team works outside of that rhythm, it will batch, waste time, and bring the company down.

This is a daily discipline. It applies to projects, tasks, communication, and deliverables. One piece flow keeps work moving and reduces the hidden cost of half-finished efforts.

Transparency: The Environment Where Everything Works

“Everything we do only succeeds in transparency.”

Transparency is not just reporting. It is the ability for the team to see reality, share information, and solve problems together. Transparency removes politics. It removes guessing. It removes hiding.

When everything is visible, improvement becomes possible. When things are hidden, the system fails.

How to Use These Principles Tomorrow

If you want to apply these principles immediately, start small and be consistent:

  • Pick one principle and practice it intentionally for one week
  • Run work in short cycles and ask for early feedback instead of waiting
  • Reduce admin and email and replace it with real time clarity and support
  • Practice one piece flow: plan, do, finish then start the next
  • Bring problems to the surface the moment you see them
  • Add a quick 5S improvement wherever you work to reinforce standards

That’s how principles turn into culture. That’s how culture turns into results.

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

Conclusion

Principles aren’t meant to be admired. They’re meant to be lived.

Elevate Construction and LeanTakt use these principles to build clarity, protect culture, eliminate waste, and create a system where people can grow and succeed. When the system is right, the work becomes more stable, the stress drops, and the team gets better together.

FAQ

What are the Elevate Construction and LeanTakt principles?
They are 27 internal operating principles shared by Jason Schroeder that define how Elevate leads, learns, supports people, protects culture, and runs work with Lean behaviors like transparency, short cycles, and one-piece flow.

Why do company principles matter in construction?
Because principles create consistent behaviors under pressure. They reduce personality driven decision making, help teams align quickly, and create a stable culture that improves safety, quality, and flow.

What does “stop, call, wait” mean?
It means when something is wrong, you stop the work, ask for help, and wait long enough to get clarity. It is a cultural requirement to prevent hiding problems and to protect people through support and teamwork.

How does one piece flow apply to knowledge work?
One piece flow means plan, do, finish before starting the next thing. In office work, it prevents batching, half-finished tasks, and context switching that creates delays and confusion.

How should leaders handle mistakes according to these principles?
Sloppy mistakes made by ignoring the process are not acceptable. Mistakes made while sincerely following the process and learning are acceptable and expected. The response is clarity, training, support, and improvement not punishment.Top of FormBottom of Form

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

Not Having the Right PM

Posted on by Danny Jiménez⁩
Read 19 min

Not Having the Right Project Manager: The System Fix That Makes the Other Problems Disappear

A project can start with a good budget, a decent schedule, strong trade partners, and a team that genuinely wants to win and still fall apart fast if the project manager seat is wrong.

Not “bad person” wrong. System wrong.

In this transcript, Jason Schroeder and Adam “Beanie” Bean go straight at a truth the industry dances around: we often choose PMs using the wrong criteria, then we “prompt” them into the wrong behaviors, then we act surprised when projects stall. It’s not a mystery. It’s a system design issue.

If we fix the PM selection and support system, we remove a major cause of project failure before it shows up in the field. That’s why Beanie says this one can make the other causes disappear. When the team rows in one direction, the work flows.

Why This Cause Hurts: The PM Seat Is a System Decision

This topic hurts because there’s no polite way to say it: putting the wrong person in the PM seat costs time, money, trust, and momentum. It also damages relationships between the office and field, because the field feels unsupported while the office feels attacked.

But the key distinction matters. Jason and Beanie aren’t here to tear down people. They’re tearing down the process that selects, trains, and incentivizes PMs.

If the system trains PMs to be spreadsheet administrators instead of flow leaders, then the system failed them. The job of leadership is to redesign the role, the expectations, and the feedback loops so the PM can succeed.

How We Accidentally Choose the Wrong PM (Excel + Technical = “Promoted”)

Beanie describes the common pattern: a young engineer is technically competent, sharp in Excel, looks professional, and seems “bright and shiny.” So, the company says, “That bloke’s going to make a project manager.”

But those two skills technical depth and spreadsheet ability are not the job.

They can be helpful. They are not sufficient.

Communication, alignment, decision flow, and the ability to see constraints in the system are what keep a project stable. And if the selection process ignores those traits, the project is set up wrong from the beginning.

The Office Trap: How the System “Prompts” PMs to Fail

Jason’s “prompt” analogy lands because it’s true. If your prompt someone all day with emails, reports, and admin demands, you’ll get more emails, more reports, and more admin.

That becomes their identity. That becomes their “success.”

Then the field wonders why no one is walking, looking, listening, clearing constraints, and supporting production. Meanwhile the PM is drowning in “deliverables” that don’t move the job forward. The system taught them to win the wrong game.

This is why the “office-only PM” isn’t a personality flaw. It’s a structure flaw. We incentivized it, measured it, promoted it, and normalized it.

The Workplace Is the Teacher: Why Answers Live at the Gemba

This episode reinforces a foundational Lean principle: you can’t manage what you refuse to see.

Beanie describes how site leaders used to be builders visible, present, walking the work, seeing the real constraints. Then computers arrived, and the people who could drive computers got promoted into leadership. The industry gradually replaced field presence with reporting.

Jason shares a simple truth from Lean thinking: “The workplace is a teacher. You can only find answers on the shop floor.”

The PM role has to reconnect to that. The most important project information is not in a report. It is in the flow of work, the delays, the waiting, the handoffs, the constraints, and the strain you can see with your own eyes.

The Real Mission of a PM: Get Everyone Rowing the Same Direction

Beanie answers Jason’s question about the PM’s true mission with a quote from Patrick Lencioni: if you can get everyone in an organization rowing in the same direction, you can dominate any market under any conditions.

That’s the job.

The PM is not the “report person.” The PM is the alignment leader. They clarify the destination, ensure the team understands it, and keep everyone moving toward it through communication, coordination, and removal of roadblocks.

And it’s not a one-time speech. The direction drifts. The conditions change. The PM continually brings the team back to center.

Local Optima vs Global Optima: One Ball, One Direction

Jason’s high-rise story shows what happens when the team loses alignment. Everyone might be skilled. Everyone might be productive in their own silo. But if each group is optimizing their own outcomes, the project can still stall.

Beanie uses a strong analogy: if every team is running around with their own football, you’ll never get one ball from one end of the field to the other. That’s local optimization.

The PM must keep the project focused on the global optima: the project destination. If that destination is unclear or if KPIs incentivize teams to win their own game the flow breaks even with good crews.

What the “Right PM” Looks Like: The 3 Non-Negotiables

Beanie gives three traits that matter more than “good at Excel”:

  1. Exceptional communication up and down the system
  2. Tracking and measuring discipline without living inside spreadsheets
  3. Understanding flow so they interpret data correctly and prioritize the right actions

This matters because data without flow understanding is dangerous. You can “improve” the wrong thing at the wrong time and create a bigger constraint. If you don’t understand flow, you may believe you’re helping while you’re actually adding friction.

Signs Your PM System Is Off Track

These are the symptoms that show the PM role has been mis-designed or mis-supported:

  • The PM is almost never at the work front and primarily lives in the office
  • Communication is mostly email and reports, not real-time coordination
  • Teams hit their own KPIs but the overall project doesn’t move smoothly
  • Field leaders feel unsupported and office leaders feel constantly “behind”
  • Data exists everywhere but decisions are slow and priorities are unclear
  • The PM reacts to noise instead of protecting flow and clearing constraints

Those signs don’t mean “PMs are bad.” They mean the system is not producing the PM behavior the project actually needs.

How ORCA Creates a Daily Improvement Loop (Nameless, Rankless, Blameless)

This is one of the most practical solutions in the conversation: ORCA.

Beanie explains it as a debrief loop used in aviation. The key conditions matter: it is nameless, rankless, and blameless. That means the meeting is not about status, ego, or punishment. It’s about learning and improving.

ORCA stands for:

  • Objective: What were we trying to do?
  • Results: What actually happened?
  • Causes: What created those results?
  • Actions: What will we change next time?

This is a virtual Andon. It forces the team to stop, see reality, identify causes, and improve the system immediately not at the end of the project when it’s too late to matter.

If a PM adopts ORCA daily, they stop being a report generator and become a learning leader. The project improves by iteration. The team gets stronger by repetition.

Track and Measure Without Living in Spreadsheets

Tracking and measuring matters. But the point is not to type forever. The point is to see the system.

Beanie’s emphasis is simple: a PM should be able to see key signals quickly through dashboards and observation, then spend time where the information is real at the work front, with the people doing the work, where constraints show up.

Data should drive better decisions, not more “admin.” The PM’s job is to interpret the data through the lens of flow and translate it into support: materials, answers, access, sequencing, and coordination.

How to Coach a PM Back On Track Before Replacing Them

Jason shared a hard but important reality: sometimes the system gets fixed, the expectations get clarified, coaching is provided, and the person still won’t align to the team direction.

That’s when leadership has to make a decision.

The goal is not to “punish” someone. The goal is to put people where they can thrive. Jason’s story ends with a key detail: the PM left, got a role that fit better, and was happier. The project got a PM who engaged the team, and the project moved.

That’s not cruelty. That’s respect for people through role fit.

A Gut Check for PMs: 14.4 Minutes to Reconnect With Reality

Beanie gives a gut check that is simple and powerful: 1% of your day is 14.4 minutes.

Take that time and go ask people what’s happening. Don’t assume. Don’t accuse. Go to the Gemba, listen, and learn.

If you’re a PM and you feel off track, don’t try to fix it by writing a better report. Fix it by reconnecting to the system and the people doing the work.

3 Traits to Hire and Train For

If you want to select and develop the right PMs, prioritize these traits and build them intentionally:

  • Communication skill that aligns teams up and down the system
  • Measurement discipline that makes performance visible without drowning in admin
  • Flow understanding so priorities protect the constraint and keep work moving

That’s the job description that actually matches the mission.

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

Conclusion

Not having the right project manager is rarely a surprise. It’s usually the outcome of a selection system that rewards the wrong behaviors and a project environment that “prompts” PMs into isolation.

The fix is not to shame PMs. The fix is to redesign the role around alignment and flow, train the right skills, and build daily feedback loops that keep the team rowing in the same direction.

The workplace is a teacher. You can only find answers on the shop floor.

Take one thing. Action it.

FAQ

What is the most important job of a construction project manager?
The PM’s primary mission is to align the team toward one destination and keep them moving in the same direction. That means clear communication, coordinated priorities, and consistent removal of roadblocks so the work can flow.

Why do companies choose the wrong project manager?
Many organizations promote people based on technical ability and spreadsheet performance rather than communication skill, flow understanding, and leadership presence. That selection process sets the project up wrong before it starts.

What is ORCA and how does it help a project?
ORCA is a debrief loop: Objective, Results, Causes, Actions. When run in a nameless, rankless, blameless way, it creates daily learning that improves planning and execution in real time, similar to a virtual Andon.

How can a PM know if they’re getting disconnected from the field?
If most of your day is spent in email and reports and you’re rarely at the work front, you’re likely disconnected. A practical gut check is to take 14.4 minutes (1% of your day) to ask field teams what’s working and what’s blocking flow.

What skills should a PM develop to become “the right PM”?
Focus on communication, measuring what matters, and understanding flow. Those skills help you interpret data correctly, support the team effectively, and keep the project aligned to the destination.

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

    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