Professional Development – Foremen

Posted on January 13, 2026January 13, 2026 by Danny Jiménez⁩

Read 17 min

Personal Development for Foremen: Invest in Your Mind and Train Your Crew Every Day

Most foremen don’t get enough training. And I don’t mean “they’re not trying.” I mean the system usually doesn’t support them. Foremen get promoted because they’re dependable, they can build, and they can keep work moving. Then we hand them a crew, a scope, and a schedule—and act like leadership will magically appear on its own. Jason Schroeder flips that story in this episode. He challenges foremen to take ownership of personal development, not as a “nice to have,” but as a core part of their job. Because foremen don’t just manage work. Foremen create the conditions for flow. And if your project is unstable, it’s usually because the system hasn’t trained the field leaders enough to stabilize it. The mindset is simple and sharp: “How you do one thing is how you do everything.”

Why Foremen Get the Least Training (And Why That Has to Change)

In most companies, training is front-loaded for new hires or reserved for management. Foremen fall into a gap. They’re too experienced to be “new,” but too busy to be “developed.” So they learn by pressure. They learn by mistakes. They learn by “sad experience” on the jobsite. The system failed them; they didn’t fail the system. If the system doesn’t create a deliberate learning path for foremen, then foremen will plateau. And when foremen plateau, crews plateau. That’s not a criticism—it’s a predictable outcome. Personal development isn’t an extra task. It’s the fuel that keeps your leadership from getting stale.

The Foreman Story: Teaching in the Work, Not Just Managing the Work

Jason shares a field picture of a foreman who understood what leadership actually looks like in production. He wasn’t just “telling people what to do.” He was teaching in the work. Every day, he was showing his crew what good looks like—how to clean, prep, and finish properly so the next step is ready and the work doesn’t come back on you later. That’s the hidden superpower of great foremen: they create capability, not dependency. The crew gets stronger because the foreman trains them through the work, not just through lectures. And here’s the kicker: when you teach daily, you have to keep learning. Teaching forces development. That’s why daily training isn’t just a gift to the crew—it’s a personal development system for the foreman.

Finish as You Go: The “Strip, Clean, Prep” Habit That Prevents Rework

One of the strongest themes in this episode is “finish as you go.” Not in a motivational way—in a practical, builder-focused way. If you strip forms and leave a mess, you’re borrowing pain from the future. If you clean and prep as part of the process, you protect the next handoff. This ties directly into flow and stability. LeanTakt thinking is built on readiness and clean handoffs. When a foreman teaches “strip, clean, prep,” they’re not just building concrete. They’re building a system where work doesn’t stack up and rework doesn’t explode. Finish as you go is a production strategy. It protects safety. It protects quality. It protects schedule. And it protects families because it reduces the “we’ve got to come back” nights and weekends.

Respect Yourself Enough to Go Get Training

Jason’s challenge to foremen is blunt: invest in your mind. Read. Take courses. Learn from others. Not because you’re broken, but because you’re responsible for leading others—and leadership requires skill. This isn’t about ego. It’s about respect. If you respect yourself and your crew, you’ll build your capability. You’ll bring better systems to the field. You’ll coach more effectively. You’ll solve problems earlier. And you won’t wait for the company to “hand you” development. You’ll pursue it.

Need vs. Want: Why Foremen Grow

People change when they need to. The question is: what do you need badly enough to grow? Jason points out the real drivers—more money, less stress, pride in craftsmanship, better safety outcomes, fewer arguments, fewer call-backs, fewer weekends destroyed by rework. Foremen don’t need development because it looks good on a résumé. They need it because the job becomes unbearable without it. If the plan requires burnout, the plan is broken. Personal development is one of the ways foremen break the burnout cycle by learning how to stabilize work instead of surviving chaos.

Train Your Crew 5 Minutes a Day (And Why That Forces You to Learn)

One of the most practical recommendations in the episode is simple: train your crew five minutes a day. Not an hour. Not a big production. Five minutes. That small habit compounds. It creates a rhythm. It makes learning normal. It creates shared language. It reinforces standards. And it makes problems easier to solve because people have been taught what “good” looks like. It also changes the foreman. Because when you commit to teaching every day, you have to show up prepared. You have to think. You have to learn. You start reading and training because you don’t want to teach the same stale message forever. Five minutes a day turns into a personal development engine.

Signs You’re Coasting Without Development

You’re leading mostly through stress and urgency because you don’t have a coaching routine.
You repeat the same frustrations every week because nothing is changing in the system.
You haven’t read anything or taken training in a long time, even though the job keeps changing.
You’re constantly reacting instead of planning and teaching, and it’s wearing you down.
Your crew depends on you for everything because development isn’t being multiplied.

The Learning Loop: Explain, Demonstrate, Guide, Enable

Jason talks about teaching as a method, not a speech. It’s not enough to tell people. People learn through a sequence: explain, demonstrate, guide, enable. You explain what good looks like. You demonstrate it. You guide them while they do it. Then you enable them to do it without you.

That’s how foremen build teams that can function even when the foreman is pulled into coordination. It’s also how you respect people: you don’t keep them dependent. You help them grow.

Repetition Is the System: Why People Need to Hear It Seven Times

One of the biggest mistakes leaders make is teaching once and expecting a permanent change. Jason reminds us that repetition is part of the system. People often need to hear something multiple times before it becomes behavior. That’s not a flaw. That’s reality. This is why five-minute daily training works so well. You don’t rely on one big moment. You rely on consistent reinforcement. And over time, the culture changes.

Start With Practical Books and Courses (Then Build a Habit)

Jason encourages foremen to start simple: pick practical learning tools and build the habit. Not because books are magic, but because consistent learning changes how you see the field. You start noticing waste. You start noticing variation. You start seeing how to stabilize work. You stop tolerating “that’s just how it is.” That mindset shift is huge. It’s what separates foremen who survive from foremen who lead. And it supports flow. Because crews with trained foremen create stable handoffs, which supports Takt rhythm and makes the whole project easier.

A Simple Daily Development System for Foremen

Teach five minutes a day in the huddle or right in the work so learning becomes normal.
Pick one skill per week to reinforce and repeat it until it becomes behavior.
Use the “finish as you go” habit: strip, clean, prep—protect the next handoff every time.
Read or learn something small daily so you always have something worth teaching.
Repeat key lessons multiple times because repetition is how culture actually changes.

Connect to Mission

At Elevate Construction, the mission is stability field teams that can plan, schedule, and flow without burnout. LeanTakt supports that by reducing variation, protecting handoffs, and building systems that make readiness visible. Foremen are the backbone of that stability. When foremen invest in personal development and train daily, crews get safer, quality improves, flow increases, and the project stops relying on heroics. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Conclusion

Here’s the challenge: don’t coast. Don’t wait. Don’t accept “good enough” leadership as the ceiling. Invest in your mind. Train your crew every day. Finish as you go. Multiply your capability. And remember the quote that should guide how you carry yourself on the jobsite and at home:“How you do one thing is how you do everything.” Build the habit. Build the standard. Build people who build things. On we go.

Frequently Asked Questions

Why is personal development important for foremen?
Because foremen shape daily production. When foremen grow, crews grow. Better coaching, better handoffs, and better stability reduce rework, stress, and schedule chaos.

What’s the simplest daily training habit a foreman can start?
Five minutes a day. A quick lesson in the huddle or in the work builds culture through repetition and helps the foreman stay sharp by learning continuously.

How does “finish as you go” help a crew?
It prevents rework and protects handoffs. Cleaning and prepping as part of the process keeps the next step ready and reduces late-night “catch-up” work.

How do I teach without sounding like I’m lecturing?
Use the learning loop: explain, demonstrate, guide, enable. Teach in the work and coach people as they do it so learning becomes practical and normal.

How does this connect to LeanTakt and Takt?
Takt requires stable handoffs and reduced variation. Foremen who train daily and finish as they go help create the stability needed for flow.

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 Capacity to Sustain

Posted on January 13, 2026January 13, 2026 by Danny Jiménez⁩

Read 18 min

The Capacity to Sustain: How to Protect Your Project Team From Overburden and Keep the Job Stable

Most project teams don’t fail because they don’t care. They fail because they get overloaded. It starts subtly. One more change. One more RFI. One more “quick” submittal. One more meeting. One more interruption. One more late night. And then suddenly the team can’t prepare, can’t plan, can’t go home, and can’t even think clearly enough to see what’s happening. Jason Schroeder asks a question that should be asked on every project, every week: “The question isn’t, do we want to do it? The question is, do we have the capacity to sustain it?” This is not a motivational question. It’s an operational question. Capacity is real. And if you ignore it, the job will take it from you in the form of burnout, mistakes, rework, and instability.

The Pain: When the Team Has No Room Left to Breathe

You can feel overburden on a project before you can measure it. Meetings get missed. Preparation stops. The jobsite gets messier. People become short with each other. Quality becomes “later.” Safety becomes “be careful” instead of a real system. Leadership becomes reaction, not planning. The system failed them; they didn’t fail the system. Overburden is often created by the project environment: incomplete design, too many decisions late, too many simultaneous priorities, or staffing that doesn’t match the reality of the workload. And when a team is over capacity, everything becomes harder. Even simple tasks feel heavy. Even good people start dropping balls.

The Set Point on Every Project: Capacity Is Real, and It Can Be Lost

Jason talks about a set point—the reality that every project team has a limit. You can stretch capacity for a short burst, but you cannot live there. If you live in stretch mode, the team will start breaking. People will stop thinking. They will start surviving. And survival mode is where the worst mistakes happen. This is why the phrase “capacity to sustain” matters. It’s not about what you can do today. It’s about what you can keep doing for weeks without destroying people. If the plan requires burnout, the plan is broken.

Muri, Mura, Muda: Why Overburden and Unevenness Matter as Much as Waste

Jason brings in a Lean lens that project teams need to understand: it’s not just waste (muda) that hurts you. Overburden (muri) and unevenness (mura) crush teams even faster. Overburden happens when workload exceeds capacity. Unevenness happens when work arrives in bursts—quiet days followed by floods of urgency, constant reprioritization, constant surprises. Those two together create chaos. And chaos creates waste. So if you want to reduce waste, you don’t start by telling people to “work harder.” You start by stabilizing the system: reduce overburden, reduce unevenness, and then remove waste.

The Research Lab Story: When Design Changes Ate the Team’s Capacity

Jason shares a research laboratory story that shows how capacity gets destroyed. The design was changing in phases. Decisions were coming late. The project team was drowning in redesign, coordination, and constant new information. That kind of environment consumes capacity because every change triggers downstream work: updated drawings, updated coordination, updated logistics, updated communication. Eventually the team had to draw a hard line. Design had to be finished. Not “mostly done.” Finished. Otherwise construction could not flow. That is a leadership move. It’s not about being difficult. It’s about protecting the system. If design remains incomplete, construction becomes a guessing game, and guessing games are expensive.

Draw the Hard Line: Finish Design So Construction Can Flow

One of the most practical takeaways from the episode is this: you can’t ask a project team to absorb endless design change and still expect stable production. At some point, you must protect the workforce and the schedule by completing design. That doesn’t mean you never process changes. It means you stop allowing “phase design” to become an excuse for constant rework. If the project is always redesigning, then the team’s capacity will be consumed by administration and coordination instead of production. Finishing design is a capacity strategy.

Don’t Ignore General Conditions: Staffing Is a Capacity Strategy

Jason also makes the point that staffing and general conditions are not just cost decisions—they’re capacity decisions. If the team is overloaded, the answer is not “try harder.” The answer is often “add support.” In the research lab story, the team negotiated for an added project engineer. That wasn’t a luxury. That was a capacity correction. It gave the core leaders room to plan, to coordinate, to lead. When you refuse to staff to reality, you push the cost into burnout and mistakes, which always costs more.

The Scorecard Habit: How to See Red Flags Before the Team Breaks

Jason talks about having a scorecard—something that shows you whether the project is stable or not. This matters because leaders often normalize overload until it becomes a crisis. A scorecard helps you see early warning signs: missed planning, rising RFIs, rising submittal backlog, increasing change volume, declining jobsite organization, reduced meeting quality, increased weekend work. The point isn’t paperwork. The point is visibility. You can’t protect capacity if you can’t see when it’s being consumed.

Why Jason Pushes 5S / 3S: Cleanliness and Organization Help You See Problems

Jason brings in 5S / 3S because organization isn’t just about aesthetics. It’s about signal. A clean, organized site makes problems visible early. A messy site hides problems until they explode. When the team is over capacity, the first thing that slips is organization. Tools get scattered. Material piles up. Debris accumulates. And those conditions create more variation and more waste. It becomes a feedback loop. Cleaning and organizing is not “extra.” It’s a stability strategy.

Signals Your Team Is Over Capacity

RFIs, submittals, and change requests are piling up faster than the team can process them.
People are staying late or working weekends just to keep up with basic administration.
Meetings get cancelled, rushed, or turn into reactive status updates with no planning.
Quality becomes “later,” and the jobsite gets messier because nobody has time to finish as they go.
The team is constantly interrupted, and prime work time is consumed by emergencies.

The Dials You Can Turn (and the One You Cannot)

Jason’s point is that leaders have dials they can adjust: scope sequencing, staffing, design completion, meeting cadence, prioritization, and interruption control. But there is one dial you should never turn: the overburden dial. Too many teams solve every problem by asking the same people to do more. That is not leadership. That is borrowing from the future with interest. If you keep turning the overburden dial, the team will eventually stop producing. Not because they’re weak, but because they’re human.

One-Piece Flow and First Things First: The Tire Store Story and the Jobsite Mirror

Jason tells a story about a tire store. A customer calls asking for an installation. The team puts the request on hold because they’re “busy,” but they’re not actually finishing what matters first. They’re multitasking. They’re bouncing between tasks. And the phone call becomes another piece of work-in-process that sits.This mirrors what happens on projects. Leaders interrupt prime work with non-urgent items. They start too many things and finish too few. They create their own unevenness. One-piece flow and first things first is a capacity protection strategy. Finish what’s in front of you before you start the next thing. Reduce work-in-process. Reduce context switching. Protect the team’s thinking time.

Capacity Protection Moves You Can Make This Week

Draw a hard line on design completion so construction can flow without constant re-coordination.
Staff to reality: add support before the team breaks, not after.
Use a simple scorecard to track workload signals (RFIs, submittals, change volume, meeting health).
Protect prime work time by controlling interruptions and prioritizing first things first.
Use 5S / 3S to make instability visible early, not hidden under mess and clutter.

Connect to Mission

At Elevate Construction, the goal is stability—field teams that can plan, schedule, and flow without burnout. Jason Schroeder’s teaching here is system-first: don’t blame people for overload. Fix the system that created it. LeanTakt supports this by reducing variation, stabilizing handoffs, and building flow. Takt cannot run on a team that is overloaded and constantly interrupted. Protecting capacity is protecting flow. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Conclusion

Here’s the challenge: stop measuring leadership by how much pain your team can absorb. That’s not strength. That’s neglect. Ask the question Jason gives you and act on it: “The question isn’t, do we want to do it? The question is, do we have the capacity to sustain it?” Protect the set point. Reduce overburden. Finish design. Staff correctly. Prioritize first things first. Keep the job stable so people can live a remarkable life.

On we go.

Frequently Asked Questions

What does “capacity to sustain” mean on a construction project?
It means the team can maintain the workload week after week without burnout, mistakes, and instability. It’s not about short bursts—it’s about what’s sustainable.

What is muri and why does it matter?
Muri is overburden—when workload exceeds capacity. It matters because it creates errors, rework, safety exposure, and eventually collapses planning and performance.

How do I know my team is over capacity?
Look for backlog growth (RFIs/submittals), late nights, missed planning, jobsite disorganization, reactive meetings, and constant interruptions stealing prime work time.

Is adding staff always the answer?
Not always, but staffing is a capacity strategy. Sometimes the right move is finishing design, reducing work-in-process, or stopping interruptions. But if workload truly exceeds capacity, added support can stabilize the system.

How does this connect to Takt and LeanTakt?
Takt requires stability and predictable handoffs. Overburden and unevenness create variation that breaks flow. Protecting capacity is essential for Takt to work.

If you want to learn more we have:

Discover Jason’s Expertise:

The Stockdale Paradox – Project Managers

Posted on January 13, 2026January 13, 2026 by Danny Jiménez⁩

Read 20 min

The Stockdale Paradox for Project Managers: Face the Brutal Facts Early and Still Believe You Can Win

There’s a moment on every project where reality starts whispering before it starts screaming. You can feel it. A few commitments slip. The schedule starts bending. Coordination gets tense. The team begins saying things like, “We’ll catch up,” and “It’ll be fine,” and “We just need to push for a couple weeks.” On paper, nothing looks catastrophic yet. In the field, everyone knows something is off. Project managers don’t lose jobs because they didn’t work hard. They lose jobs because they didn’t face the brutal facts early enough to act while action still mattered. Jason Schroeder’s message in this episode is a leadership calibration for that exact moment: use the Stockdale Paradox. Face reality without flinching, and keep faith without pretending.

The Pain: Projects Fail Quietly Long Before They Fail Loudly

Most project failures don’t show up as one big explosion. They show up as a slow accumulation of unspoken problems. Roadblocks aren’t tracked, so they repeat. Meetings become “status” instead of decisions. People start hiding bad news because they don’t want to be the one who “ruins the mood.” The plan becomes a story everyone tells, not a reality everyone manages. Then one day, the team realizes they’re out of time, out of options, and out of trust. The system failed them; they didn’t fail the system. If the environment punishes bad news, bad news will stay hidden. If the culture rewards optimism over truth, leaders will keep giving timelines they can’t defend. And when reality finally arrives, it arrives with interest.

The Failure Pattern: The Optimist Trap

Jason describes a trap that shows up in hard situations: false optimism. Not hope. Not confidence. False optimism—the kind that refuses to see what’s real. On projects, it sounds like this: “We’re okay,” “We can make it up later,” “Don’t worry the owner,” “Let’s not overreact,” “We’ll figure it out.” And to be clear: those phrases often come from good intent. People want to protect each other. They want to keep morale up. They want to believe. But if you use optimism as a substitute for evidence, you lose the one thing you cannot buy back: time.

Empathy: Facing Facts Can Feel Like Betrayal But It’s Actually Care

For many PMs, facing the brutal facts feels like you’re being negative. Like you’re betraying the team. Like you’re “not being a leader.” Jason flips that: the most caring thing you can do is tell the truth early while the team still has choices. You don’t create stability by ignoring problems. You create stability by surfacing them safely, debating them intelligently, and removing them fast. That’s a system, not a mood.

The Stockdale Paradox: Brutal Facts + Unwavering Faith

The Stockdale Paradox is the leadership posture Jason wants PMs to adopt: you confront reality as it is, without denial, while maintaining unwavering faith that you can still win if you respond correctly. This is not contradictory. It’s the balance.When you only have faith, you drift into the optimist trap. When you only have facts without faith, you collapse into cynicism and paralysis. The Stockdale posture gives the team both: truth and energy, realism and action.Jason summarizes it with a line that is meant to become a leadership principle: “A stoic acceptance of project realities coupled with an unwavering faith in eventual triumph.”

The PM’s Real Job: Trigger Red Flags and Remove Roadblocks

A strong PM is not a spreadsheet operator. A strong PM is an early warning system. Your job is to see what’s coming before it hits the craft. Your job is to create a culture where problems are safe to surface. Your job is to bring the right people together to debate root cause and choose countermeasures. Your job is to remove roadblocks so the team can execute without interruption. In LeanTakt terms, this is how you protect flow. Takt doesn’t survive in a culture that hides problems. Takt requires visibility, readiness, and rapid roadblock removal. If your team is always reacting, your system is already late.

Why Projects Fail Quietly: Problems Stay Hidden Until They’re Too Big

Jason’s core warning is that hidden problems don’t stay small. They grow. A small RFI delay becomes a procurement miss. A procurement miss becomes a late delivery. A late delivery becomes resequencing. Resequencing becomes trade stacking. Trade stacking becomes quality misses and safety exposure. And by the time leadership finally “sees it,” the team has lost weeks sometimes months.This is why PMs must create systems that force truth early. You cannot rely on gut feel alone. You need triggers.

Build a Culture Where Facts Are Safe

One of the most important ideas in this episode is cultural: facts must be safe. If people get punished for surfacing a problem, they will stop surfacing problems. If meetings turn into blame sessions, people will bring you “good news” even when reality is ugly. If leaders make it emotional, the team will make it quiet. System-first diagnosis fixes this. We blame the process, not the person. We assume people are doing their best with the system they have. We bring issues to the surface because we respect people enough to stop setting them up for failure.

Debate the Root Cause: Ask Questions First, Don’t Jump to Answers

Jason also pushes PMs to slow down just enough to ask better questions. Too many meetings jump straight to solutions without understanding. If you want Stockdale leadership, you need Socratic leadership. Ask: What is the real constraint? What evidence do we have? What changed? What are the options? What is the countermeasure? Who owns it? By when? How will we verify? Facing brutal facts is not just “being honest.” It’s building a disciplined thinking system.

Signals You’re Not Facing the Brutal Facts Yet

Roadblocks aren’t tracked visibly, so the same issues keep reappearing in new forms.
Meetings skip evidence and jump to optimism: “We’ll be fine” without a countermeasure.
People hide problems until they’re emergencies because they don’t feel safe surfacing them early.
You don’t debate root causes—solutions are chosen fast, then fail fast, then repeat.
The schedule becomes a promise instead of a plan, and dates move without accountability.

Roadblocks on the Board: The Daily Discipline That Protects Flow

Jason describes a practical habit: make roadblock removal the number one priority, every day. Not “one of the priorities.” The number one. When roadblocks are visible—on a huddle board, in a daily log, in a shared system leaders can swarm them. PMs, directors, and senior supers can align on what must be removed to protect field production. This is how you honor the craft. The craft should not spend its day waiting for answers. The craft should build. And if they can’t build, leadership’s job is to clear the path.

The Risk & Opportunity Register: Your Second Set of Eyes

Jason also points PMs toward a risk and opportunity register as a tool for reality. It becomes your second set of eyes. A good register isn’t bureaucracy. It’s a decision system. It forces you to name risks, assign owners, define triggers, and track whether risk is increasing or decreasing. It also helps the team see opportunities where a countermeasure could create schedule gain, cost savings, or stability. If you don’t have a place where risks live, they’ll live in people’s heads. And what lives in people’s heads usually doesn’t get managed until it hurts.

Trigger Systems: Alarm Bells Before the Date Is Lost

This is one of the most actionable parts of the episode: PMs need triggers. A trigger is an agreed-upon alarm bell that says, “If this happens, we act.” Not next week. Now. Triggers can be schedule-based: a milestone slip, a procurement lead time miss, a design deliverable late, a commissioning sequence threatened. Triggers can be production-based: missed weekly plan percent, increased unplanned work, increased RFIs. The point is you don’t wait for the date to be lost. You respond when the warning appears.Stockdale leadership is not hope. It’s early action.

Safety Triggers: Cleanliness, Organization, Morale, and Standards

Jason also reminds leaders that safety and organization are early warnings of capacity and control. When a team is overloaded, cleanliness slips. When cleanliness slips, hazards increase. When hazards increase, stress increases. When stress increases, people stop thinking clearly. A messy job is rarely just “messy.” It’s often an indicator of instability. 5S / 3S isn’t about looking pretty. It’s about seeing problems early.

Calm Response to Hard Data: Professional, Direct, and Fast

Stockdale PMs don’t freak out when data is bad. They get calm. Calm doesn’t mean passive. Calm means professional. Direct. Fast. You treat hard data as a gift because it gave you time to respond. You don’t attack people. You attack the constraint. You don’t shame. You align. This is the leadership tone that makes truth safe. When PMs respond calmly to brutal facts, the team learns: “We can surface problems here.” That is a competitive advantage.

A Stockdale System for PMs: Triggers + Roadblock Removal

Track roadblocks daily and make removal the #1 leadership priority so the craft can keep building.
Run meetings with evidence and questions first; debate root cause before choosing countermeasures.
Build schedule and safety triggers so you act on warning signs before dates and trust are lost.
Use a risk & opportunity register as a living system with owners, triggers, and weekly updates.
Respond calmly to bad news—professional, direct, fast—so facts stay safe to surface.

Connect to Mission

At Elevate Construction, the goal is stability—teams that can plan, schedule, and flow without burnout. Jason Schroeder teaches system-first leadership because hiding problems creates chaos, and chaos punishes people. LeanTakt and Takt require visible constraints, reliable commitments, and daily roadblock removal. The Stockdale Paradox is a leadership posture that supports those systems: face reality early, protect the team, and act fast enough to win. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Conclusion

Here’s the challenge for every project manager: stop letting “optimism” become denial. Stop waiting for problems to become emergencies. Build trigger systems. Make roadblock removal the main event. Create a culture where facts are safe, not punished. And hold the posture Jason gives you as your leadership standard: “A stoic acceptance of project realities coupled with an unwavering faith in eventual triumph.” Face the brutal facts early. Believe you can still win. Then do the work that proves it. On we go.

Frequently Asked Questions

What is the Stockdale Paradox in construction project management?
It’s the ability to confront brutal facts early—without denial—while maintaining unwavering faith that the project can still succeed if you act in time.

How do I know if my team is stuck in the “optimist trap”?
If meetings produce reassurance instead of countermeasures, if roadblocks aren’t tracked, and if issues keep surfacing as emergencies instead of being handled early, optimism has replaced evidence.

What are “triggers” and why are they important?
Triggers are alarm bells that tell the team when to act. They prevent “wait and hope” by defining early warning signs that require immediate countermeasures.

How does roadblock removal protect the schedule?
Because roadblocks are the constraints that stop production. When leadership removes them quickly, the craft stays productive and the team avoids resequencing and trade stacking.

How does this connect to Takt and LeanTakt?
Takt relies on predictable handoffs and readiness. Stockdale leadership supports Takt by surfacing constraints early, removing roadblocks daily, and reducing variation that breaks flow.

If you want to learn more we have:

Discover Jason’s Expertise:

Don’t Lose Your Temper – Supers

Posted on January 13, 2026January 13, 2026 by Danny Jiménez⁩

Read 18 min

Expectations Without Anger: How Superintendents Hold the Standard and Still Respect People

Every superintendent wants the same thing: a clean job, a safe job, a predictable job, a job where commitments mean something and the schedule isn’t held together with panic. And when the job falls short of that—when meetings go sideways, when work isn’t ready, when quality slips, when people don’t follow through—the pressure builds. Expectations rise. Frustration rises. And if you don’t have a leadership system, frustration turns into anger. Jason Schroeder’s reset for superintendents is simple and powerful: “Expect the best in yourself and appreciate the best in others.”That quote isn’t soft. It’s a standard. It’s how you hold the line without losing your dignity or theirs.

The Pain: When a Leader “Loses It” and Can’t Get the Day Back

Jason describes a moment most leaders recognize. You come out of a sub-meeting. The trade partner didn’t deliver. The plan isn’t being followed. You’re already carrying the schedule on your back. You feel disrespected. You feel like nobody cares. And then you blow up—cussing, yelling, throwing blame around, maybe even throwing something. Then you walk out and you know it: you lost today. You can’t get that moment back. You might repair the relationship over weeks, but you can’t undo the damage to trust and credibility in that instant. That’s why this matters. Anger doesn’t just hurt feelings. It creates variation. It destabilizes the system. It makes people hide problems instead of surfacing them. It makes your job harder tomorrow. The system failed them; they didn’t fail the system. Leaders blow up when they don’t have a method to convert frustration into productive action.

The Failure Pattern: Frustrated Expectations Turning Into Anger

Expectations are not the problem. Standards are necessary. Respect equals high expectations. The problem is when expectations become personal. When the gap between “what should be happening” and “what is happening” turns into a story in your head: they don’t care, they’re lazy, they’re disrespectful, they’re trying to screw me. That story lights the fuse. Jason teaches leaders to separate the standard from the person. Your job is to protect the standard and the process. Your job is not to emotionally punish someone into compliance. Emotional punishment is manipulation, and it always backfires.

The Quote That Resets Leadership: Expect the Best in Yourself, Appreciate the Best in Others

This quote contains the whole system if you let it. Expect the best in yourself means you don’t demand what you don’t model. You show up prepared. You communicate clearly. You follow through. You keep your commitments. You stay calm. You do your part first. Appreciate the best in others means you assume people want to do well. You look for effort. You acknowledge progress. You treat people with dignity even when you are correcting them. You build trust so you can hold the line without needing anger to prop you up. That’s leadership. High standard, low drama.

Why Hypocrisy Breaks the Jobsite: You Can’t Demand What You Don’t Model

Jason makes this point bluntly: if you want accountability, you have to be accountable. If you want clean work, you must protect cleanliness. If you want people to be on time, you must start on time. If you want huddles to matter, you must run them with discipline. When leaders demand standards they don’t live, the crew feels it immediately. Hypocrisy destroys authority faster than any mistake. And once authority is gone, leaders reach for anger to regain control. But anger never creates real control. It creates compliance at best—and resistance underneath.

Respect Equals High Expectations: What Standards Really Mean

Jason ties respect directly to expectations. Low expectations are disrespectful because they assume people can’t rise. High expectations, delivered with dignity, are respect in action. But you must deliver them the right way. Standards are not personal attacks. Standards are shared agreements about what “good” looks like, what “ready” means, and what “done” is. Standards create stability, and stability protects people. This is why Takt and LeanTakt matter here. Takt relies on stable handoffs and predictable readiness. When leaders introduce emotional volatility, they introduce variation. When leaders hold standards with calm consistency, they create flow.

Separate the Standard from the Person: Attack the Process First

Jason’s core method is process-first leadership. Before you jump to blaming a person, you attack the process. You ask:

Is the plan clear?
Were prerequisites made ready?
Were resources available?
Were standards communicated?
Was training provided?
Did we set them up to succeed?

This is system-first diagnosis. It doesn’t excuse poor performance. It simply ensures you correct the right root cause. If you correct the wrong thing, you’ll keep having the same issue no matter how angry you get.

Signals Your Expectations Are Turning Into Anger

You feel your body tighten before meetings because you’re expecting conflict.
You start cussing, accusing, or making it personal instead of staying on facts.
You demand perfection in the moment rather than building a process that produces quality.
You leave a meeting thinking, “I lost today,” because your reaction took control.
You see people shutting down, hiding issues, or avoiding you instead of collaborating.

The Superintendent Method: Process → Resources → Standards → Support → Then Role Fit

Jason outlines a progression that protects both results and dignity. First, check the process. Was the sequence correct? Was the work made ready? Second, check resources. Did they have materials, tools, access, information? Third, check standards. Was “done” defined clearly? Were tolerances and expectations visible Fourth, check support. Did we coach, train, and reinforce the standard? Only after those steps do you evaluate role fit. Not as punishment—just as reality. Sometimes a person needs more training. Sometimes they need a different role. But you don’t skip straight to condemnation. You fix the system first. This is how you hold high expectations without anger: you become a problem-solver, not a judge.

Consequences Without Punishment: How to Change Circumstances the Right Way

Jason makes a distinction between consequences and punishment. Punishment is emotional. Punishment is humiliation. Punishment is yelling and threats. Consequences are operational. Consequences are changes in circumstance designed to protect the project and support performance. That might mean adjusting the plan, adding a quality check, changing handoff requirements, requiring a pre-task plan, modifying access, or escalating for additional support. The goal is not to “get even.” The goal is to stabilize production. When leaders use consequences instead of anger, the team learns that standards are real and predictable not random explosions.

Stop Emotional Manipulation: Why Yelling, Cussing, and Threats Backfire

Jason calls out a truth superintendents need to hear: anger is often an attempt to control other people’s emotions. It’s emotional manipulation disguised as leadership. It might work briefly. People might scramble. But it creates hidden cost: resentment, silence, defensiveness, and loss of trust. People stop surfacing problems early because they don’t want to be the target. That increases variation and makes the job less safe. Leadership isn’t about being feared. It’s about being trusted.

Certainty and Significance: The Hidden Trigger Behind Blowups

Jason ties blowups to human need certainty and significance. When the schedule feels uncertain, leaders feel threatened. When leaders feel disrespected, they feel insignificant. Those emotions trigger reaction. The fix isn’t to suppress emotion. The fix is to redirect it into contribution and growth. If you’re focused on improving the system and serving the team, you don’t need anger to feel important. You gain certainty by building stability through process.

Growth and Contribution: The Shift That Keeps You Calm and Effective

Jason’s alternative posture is leadership maturity: focus on growth and contribution. Grow your systems. Grow your people. Contribute to clarity. Contribute to stability. Contribute to the mission. When leaders live in growth and contribution, they still hold high expectations—but they do it calmly. They correct without condemnation. They coach without humiliation. They protect standards without needing to “win” emotionally.

The Expectation System: High Standards With Respect for People

Model the standard first: be prepared, be consistent, and keep your own commitments.
Separate the person from the process: attack system gaps before judging performance.
Verify resources and clarity: tools, materials, access, information, and “done” defined.
Provide support and training, then enforce consequences that protect the project—not punishment.
Appreciate effort and progress while still holding the line on safety, quality, and commitments.

Connect to Mission

At Elevate Construction, the goal is stability projects that plan, schedule, and flow without burnout. Jason Schroeder teaches that respect for people is a production strategy, and this episode is exactly that: high expectations delivered with dignity. LeanTakt supports this by reducing variation and creating predictable handoffs. Anger creates variation. Calm standards create flow. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Conclusion

Here’s the challenge: stop sacrificing your leadership credibility in emotional moments. You can be firm without being furious. You can hold high standards without disrespect. You can enforce expectations without losing your temper. Start with the quote and live it daily: “Expect the best in yourself and appreciate the best in others.” Hold the standard. Fix the process. Use consequences, not punishment. Keep dignity intact. Keep the project moving.

Frequently Asked Questions

Isn’t anger sometimes necessary to get people to listen?
Anger may get short-term attention, but it creates long-term cost: fear, silence, and hidden problems. Calm clarity and consistent consequences build real accountability.

How do I hold high expectations without becoming “soft”?
High expectations are not softened by respect. They are strengthened. Use clear standards, visible “done,” and consistent consequences. Respect keeps people engaged.

What does “attack the process before the person” mean?
It means checking readiness, resources, standards, and support before assuming the issue is someone’s character. Fixing the system often fixes performance.

What are examples of consequences without punishment?
Adding quality checks, requiring pre-task planning, changing handoff requirements, adjusting sequencing, escalating for support, or changing roles when needed—without humiliation.

How does this connect to Takt and LeanTakt?
Takt needs stability and predictable handoffs. Anger and emotional volatility create variation. Calm standards and make-ready systems protect flow.

If you want to learn more we have:

Discover Jason’s Expertise:

The Courage To Be Disliked

Posted on January 13, 2026January 13, 2026 by Danny Jiménez⁩

Read 14 min

The Courage to Be Disliked: Lead Without Needing Approval and Stop Giving Your Self-Worth Away

There’s a quiet pressure that ruins leaders the need to be liked. You feel it when someone criticizes your plan. You feel it when a crew resists change. You feel it when a client questions your decision. And if you’re not careful, that pressure will pull you off your purpose. In construction, we call it leadership fatigue — when good people stop leading because they’re tired of being disliked. Jason Schroeder calls the antidote “the courage to be disliked.” It’s the ability to do the right thing without chasing approval. It’s what separates healthy leaders from those who crumble under pressure.

Why This Matters: You Can’t Lead If You Need to Be Liked

You can’t build remarkable projects by making everyone happy. Leadership means guiding people through friction, enforcing standards, and holding clarity when others drift. If your confidence depends on everyone approving, you’ll end up chasing comfort instead of progress. The best leaders Jason’s coached have backbone. They speak truth, protect stability, and hold the line even when it costs them popularity. The system needs that kind of strength especially when others resist accountability.

The Trap: When Your Self-Worth Lives in Other People’s Opinions

Many leaders don’t realize they’re outsourcing their self-worth. They measure success by how others respond praise feels like oxygen, criticism feels like failure. The problem is, that cycle never ends. You’ll be anxious, defensive, and inconsistent because you’ve made other people the source of your peace. Jason explains it simply: if your happiness depends on what others think, you’re not leading you’re performing. Leadership requires separating your task (doing what’s right) from theirs (how they feel about it).

Signs You’re Leading for Approval Instead of Purpose

You avoid hard conversations because you don’t want to disappoint people.
You over-explain or apologize for enforcing standards.
You replay criticism in your head long after the meeting.
You feel crushed when your efforts aren’t recognized.
You base your worth on temporary reactions instead of long-term results.

“In the Arena”: What to Remember When Critics Show Up

Jason often reminds leaders of Theodore Roosevelt’s quote “It is not the critic who counts… the credit belongs to the man who is actually in the arena.” You are in the arena. The dust, noise, and pushback are proof that you’re leading. The critics aren’t your problem they’re part of the process. Great leaders don’t get smaller to fit other people’s comfort zones. They stay grounded in purpose. They separate feedback that’s useful from noise that’s emotional. And they keep leading anyway.

Field Story: When the Project Team Didn’t Want Him There

Early in Jason’s director years, he visited a project team to help stabilize the schedule. Instead of gratitude, he got resistance. The team didn’t like the “oversight.” He left that day frustrated questioning whether he was doing something wrong. Then he read The Courage to Be Disliked. It reframed everything. He realized the team’s reaction was their task, not his. His task was to bring clarity and support. Their task was to receive it however they chose. From that day forward, he led with freedom — calm, direct, and unshaken by popularity.

Primary vs. Secondary Happiness: Where Peace Actually Comes From

Adlerian psychology distinguishes between two types of happiness. Secondary happiness comes from comfort, praise, and circumstances. Primary happiness comes from contribution, growth, and living by your principles. The first fades; the second compounds.vLeaders anchored in primary happiness make hard calls without losing peace. They can be firm and kind at the same time because their worth doesn’t depend on reactions.

Personality Patterns: Why Some Leaders Crave Praise

Jason points out that certain personalities often feelers or harmonizers equate peace with approval. They’ve been rewarded for being agreeable their whole lives. But leadership flips that pattern: now, clarity is kindness. Protecting the system is love. And sometimes the most respectful thing you can do is tell the truth others won’t.

The Shift That Changes Everything: Separation of Tasks

The central idea from The Courage to Be Disliked is separation of tasks. In simple terms: your task is to do what’s right. Other people’s task is how they respond. You don’t cross into their task, and they don’t cross into yours. When you stop trying to control reactions, you gain peace. When you stop personalizing disagreement, you gain power. You start leading from principle instead of pressure.

Anger and Yelling as Control: Why Emotional Manipulation Backfires

Some leaders replace approval-chasing with domination shouting, intimidating, using anger to control outcomes. It feels powerful in the moment, but it’s the same fear in disguise. Whether you’re begging for approval or demanding compliance, you’re still letting other people’s reactions drive you. Real leadership is calm clarity. You can hold standards without aggression. You can correct behavior without humiliation. You can enforce systems with respect.

A Practical System to Build the Courage to Be Disliked

Anchor your worth in contribution, not approval.
Practice separation of tasks — their feelings aren’t your responsibility.
Deny the craving for recognition; act from conviction instead.
Replace praise/criticism cycles with gratitude for progress.
Choose growth and contribution over comfort and certainty.

Deny the Desire for Recognition: Freedom Costs the Risk of Being Disliked

This is the price of freedom not everyone will like you. But if you trade your integrity for approval, you lose both. Leaders who can withstand disapproval are the ones who create lasting respect. They aren’t arrogant; they’re grounded. Jason calls this “freedom from emotional slavery.” It’s the ability to listen, learn, adjust, and still stand firm in your values.

Build a Healthier Leadership Posture

Stop praising or condemning constantly just state the facts. Replace manipulation with collaboration. Replace “good job” or “you messed up” with “here’s what happened, and here’s what we’ll do next.” Gratitude and clarity outlast praise and punishment. This balance creates stability. It shows respect for people while holding the system accountable.

The New Aim: Community, Growth, and Contribution

When you stop living for likes, your leadership shifts from self to service. You start focusing on contribution instead of validation. You build community instead of compliance. You grow because you’re free to make mistakes and learn.This is where Lean and Elevate Construction’s mission meet: Respect for people is a production strategy. You can’t respect others fully if you’re addicted to their approval. You lead best when your heart is free. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Conclusion

Here’s the challenge: this week, notice every time you shape your behavior to avoid disapproval. Catch it. Then separate the task. Do what’s right anyway. Leadership isn’t a popularity contest. It’s a stewardship of truth. As Roosevelt said, “It is not the critic who counts… the credit belongs to the man who is actually in the arena.” You’re that person.Be courageous enough to be disliked and free enough to lead with love.

Frequently Asked Questions

What does “separation of tasks” mean in leadership?
It means you’re responsible for your actions and principles not for how others feel about them. Clarity replaces control.

How does this apply to construction leadership?
Project leaders face daily pressure to please owners, clients, and teams. Separating tasks allows them to hold the line with calm confidence instead of emotional reaction.

Isn’t it important to care what people think?
Yes — but caring and depending aren’t the same. You can value feedback without letting it define you. Seek truth, not validation.

What’s the danger of needing approval?
It creates inconsistency. You’ll bend rules, overwork, or avoid conflict to stay liked — and the system will eventually collapse.

How does this align with Lean and Takt principles?
Lean and Takt depend on stability and respect. When leaders stop reacting to emotion and act from principle, the whole system flows smoother.The Courage To Be Disliked

If you want to learn more we have:

Discover Jason’s Expertise:

Figure Things Out! – Field Engineers

Posted on January 13, 2026January 13, 2026 by Danny Jiménez⁩

Read 18 min

Figure Things Out: The Field Engineer’s Job Is to Absorb Chaos and Create Stability for the Craft

Every jobsite has chaos. Missing information. Late decisions. Conflicting drawings. Material delays. Layout questions. Inspections. Weather. Design changes. People needing answers right now. And in the middle of all that noise, the craft still needs stability to build safely, cleanly, and on time. That’s where the field engineer comes in. Jason Schroeder says the real job description of a field engineer can be boiled down to three commands: figure things out, enable the craft, be the badger. Not because field engineers are supposed to be tough for toughness’ sake, but because they are the shock absorber of the project. They take variation and convert it into clarity. They take confusion and convert it into readiness. They live in the messy middle so the craft can work in stability.

The Pain: Field Engineers Get Hit From Every Direction

If you’ve been a field engineer, you’ve felt it. People pull you into everything. A foreman needs layout. A superintendent needs a revised plan. A trade partner needs an answer on embeds. The office needs quantities. The inspector needs documentation. Someone says, “It’s urgent,” and it’s always urgent. The easy response is to feel like a victim of the chaos. To believe the job should be plug-and-play. To wish somebody would hand you the answer or train you perfectly so you never struggle. Jason’s message is: that mindset will cap you. The system failed them; they didn’t fail the system—but if you stay in the victim posture, you’ll never become the kind of field engineer the craft can rely on.

The Failure Pattern: Wanting It on a Platter Instead of Owning the Struggle

A field engineer who expects everything to be explained perfectly, documented perfectly, and handed over cleanly will constantly feel behind. Construction is not built in a lab. You build something where nothing existed. There will be missing pieces. There will be variation. And if your mindset is “this shouldn’t be happening,” you’ll spend your energy complaining instead of solving. Jason describes this as the difference between a victim mindset and an ownership mindset. The ownership mindset says: good. Don’t care. Now what? What do I need to learn? Who do I need to call? What do I need to verify? What system do I need to build so the craft can keep moving? That’s the Honey Badger mindset.

The Field Engineer’s Real Job Description: “Figure Things Out”

Jason is blunt: your job is to figure things out. That means you don’t just answer questions you build clarity. You don’t just chase information—you create reliable handoffs. You don’t just survive daily fires—you set up systems so fewer fires happen tomorrow. That’s why the best field engineers aren’t only “smart.” They’re relentless about learning, resourceful, and calm under pressure. They don’t wait for permission to solve problems. They go get what they need. And when you do that consistently, people trust you. The craft trusts you. The superintendent trusts you. The project stabilizes.

Why the “Honey Badger” Mindset Matters in Construction

The Honey Badger metaphor is about attitude toward struggle. Honey badgers don’t panic. They don’t whine. They don’t wait for someone to rescue them. They keep moving, they adapt, and they finish. In construction, that doesn’t mean being reckless. It means being resilient. It means you don’t fold when something changes. You don’t get offended by confusion. You treat variation as the training ground of your career. If you want to grow fast as a field engineer, you must stop wishing the job was easier and start using the difficulty to get better.

Field Engineers Live in Chaos So the Craft Can Work in Stability

This is the most important system-first point in the episode: craft productivity depends on stability. Flow depends on readiness. Takt depends on predictable handoffs and constraints removed early. Field engineers are one of the key roles that make that stability possible. They make-ready. They handle submittals. They check drawings. They coordinate information. They prepare layout. They ensure materials and tools are where they need to be. They close loops. When field engineers do this well, trades don’t lose time. They don’t wait. They don’t restart work. They don’t have to “figure it out in the field” while standing on a ladder. They build. That’s respect for people as a production strategy.

The Boot Camp Origin Story: Why “Explaining More” Didn’t Create Retention

Jason describes a lesson learned while training field engineers. The initial instinct was to explain more—teach harder, talk longer, provide more information. But the problem wasn’t lack of explanation. The problem was lack of retention and ability. So the training shifted to something better: a learning system that forces real learning through doing. Instead of telling someone how to do layout, you guide them through it. You make them work through placing footings from two points and plans. You let them struggle a bit. Then you coach them through the struggle. That’s how capability is built. Not through being handed the answer, but through earning it.

Explain, Demonstrate, Guide, Enable: The System That Forces Real Learning

Jason points to a method that works because it mirrors how people actually learn: explain, demonstrate, guide, enable. You explain the concept. You demonstrate the skill. You guide them while they do it. Then you enable them to do it without you. The “guide” phase is the key. It’s where the struggle lives. It’s where growth happens. And it’s where most people try to shortcut by asking for the answer instead of doing the work. A Honey Badger field engineer doesn’t shortcut that phase. They embrace it.

Signs You’re Waiting to Be Babysat Instead of Figuring It Out

You use victim language: “Nobody told me,” “They didn’t train me,” “This shouldn’t be like this.”
You wait for answers instead of tracking the right person down and closing the loop.
You avoid struggle and then wonder why the skill isn’t sticking.
You treat variation as an excuse instead of as training for your career.
You expect construction to be plug-and-play instead of accepting that it’s built in real conditions.

Jason’s Story: Buying the Computer, Learning AutoCAD, and Going to Get It

Jason shares a personal “go get it” story that’s the heart of this episode. He wanted to be a field engineer. He didn’t have all the tools or knowledge at first. So he bought an old Dell on credit and taught himself the skills he needed—AutoCAD and Excel—so he could do the job. That’s what “figure things out” looks like. It’s not motivation. It’s action. It’s ownership. It’s refusing to wait for a perfect system before you start becoming excellent.

Construction Isn’t Plug-and-Play: You Build Something Where Nothing Existed

This might be the most freeing concept for a young field engineer: if you expect construction to feel smooth and predictable, you’ll constantly feel disappointed. The work is inherently complex. Every job is different. You are building in real time with real constraints. The job of a field engineer is not to wish that complexity away. It’s to turn complexity into clarity. That’s why the role is so valuable.

“Good. Don’t Care.” Using Variation as Training Instead of an Excuse

Jason’s posture is clear: when variation hits, don’t complain. Solve. When plans are missing, don’t panic. Find. When people need answers, don’t avoid. Close loops. That’s not being cold. That’s being effective. When you treat variation as training, you level up faster. You become the person who can walk into a new project and stabilize it quickly. You become a multiplier.

How a Field Engineer Enables Flow: Materials, Tools, Information, Layout Ready

A Honey Badger field engineer doesn’t just “work hard.” They create readiness. They ensure the craft has what it needs: correct information, verified layout, materials staged, tools available, and constraints removed. This is where Takt connects naturally. If you want Takt and LeanTakt systems to work, you must make-ready. You must remove variation. You must create predictable handoffs. Field engineers are often the backbone of that readiness system.

The Honey Badger Operating System for Field Engineers

Go get it: track answers down, learn skills fast, and refuse to wait for perfect conditions.
Absorb chaos so the craft doesn’t have to—convert variation into clarity and readiness.
Build make-ready habits daily: layout, information, tools, materials, and constraints removed.
Embrace the guide phase: struggle, learn, and earn the skill so it sticks.
Stabilize flow: protect handoffs and reduce interruptions so production can run predictably.

Connect to Mission

At Elevate Construction, the goal is stability teams that can plan, schedule, and flow without burnout. LeanTakt supports that stability by reducing variation and making readiness visible. Jason Schroeder’s message to field engineers fits perfectly: don’t blame people for chaos. Fix the system. Absorb variation. Enable the craft. Create stability so the project can flow. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Conclusion

Here’s the challenge: stop waiting to be hand-held. Stop wishing the job was easier. Decide that you’re going to become the kind of field engineer who can walk into chaos and create stability. Remember the three-part job description Jason gives you: figure things out, enable the craft, be the badger. Own the struggle. Learn fast. Close loops. Protect the craft. That’s how you become great tomorrow.

Frequently Asked Questions

What does “figure things out” mean for a field engineer?
It means taking ownership of uncertainty—tracking answers down, learning the skills you need, and turning jobsite variation into clarity so the craft can keep moving.

Why does Jason call it the “Honey Badger” mindset?
Because it represents resilience and forward motion. You don’t panic or complain when things change—you adapt, solve, and keep progress moving.

How does a field engineer “enable the craft”?
By making-ready: providing accurate information, verified layout, staged materials, available tools, and removing constraints so crews can work with stability.

What is the best way for a new field engineer to learn fast?
Use the explain–demonstrate–guide–enable method and embrace the guide phase. Struggle through real tasks with coaching so skills stick instead of being memorized.

How does this connect to LeanTakt and Takt?
Takt relies on stable handoffs and reduced variation. Field engineers support Takt by making work ready and removing interruptions before crews arrive.

If you want to learn more we have:

Discover Jason’s Expertise:

Remarkable Negotiation

Posted on January 13, 2026January 13, 2026 by Danny Jiménez⁩

Read 21 min

Negotiation for Construction Leaders: Win-Win Techniques for Change Orders, Training, and Real Trust

A lot of people hear the word “negotiation” and immediately check out. They picture slick tactics, pressure, and somebody “winning” while somebody else loses. Jason Schroeder starts this episode by pushing back on that assumption hard. Negotiation, done right, is one of the biggest game changers a project leader can learn not just for change orders, but for training, resources, and even how you communicate at home.

And he makes the ethical boundary crystal clear: this is not about lying, manipulation, deceit, or “getting one over” on people. It’s about creating win-wins, building trust, and presenting the full story in a way the other party can actually hear. If you’ve ever walked away from a change order conversation thinking, “They didn’t even listen,” this episode explains why. Jason gives the quote that anchors everything: “It is emotion, not logic, that determines the success or failure of negotiations.” That one sentence should change how you show up because most of us have been trained to “argue the facts” as if facts alone move people.

Why Negotiation Is a Game Changer for PMs, Supers, and Families

Negotiation isn’t reserved for executives. Project managers negotiate fair change orders. Superintendents negotiate field support, manpower, and time. Project engineers negotiate information turnaround. Leaders negotiate training budgets that make the entire company better. When negotiation is weak, everything becomes a grind. Conversations turn into fights. Emails get tense. People start ghosting. You spend time proving you’re right instead of getting things resolved. And the cost isn’t just money, it’s trust, morale, schedule stability, and the stress you bring home. When negotiation is strong, you get something different: clarity and momentum. Not because you “tricked” anyone, but because you gave them the full picture—facts plus the emotional context so they could make a fair decision without defensiveness.

The Non-Negotiable Rule: This Is Not Manipulation It’s Win-Win and Trust

Jason shares a story from How to Win Friends and Influence People where Dale Carnegie addresses the accusation that persuasion is just getting something from people. Carnegie’s response is essentially: the goal is appreciation, connection, spreading cheer, and creating more win-win situations not using people. Jason uses that story to make the point: if your intent is to take without giving, you’ll earn the lonely outcomes that come with that behavior. In construction, win-lose negotiation backfires. You might “win” the moment and lose the relationship. You might push through a decision and then get slow-walked later. The goal here is honesty, transparency, and fair outcomes presented in a way that restores trust so the other party can actually consider the facts.

The Real Truth: Emotion Beats Logic in Negotiations

Jason doesn’t say logic is unimportant. He says logic often isn’t received until emotion is addressed. If you’ve ever tried to “logic” your way through an argument with your spouse and watched it go nowhere, you already understand the point. The reception is emotional. The relationship is emotional. The trust is emotional. So the question becomes: how do we show up in a way that connects emotionally, reduces defensiveness, and makes it possible for the other person to consider the facts? That’s what the rest of the episode delivers: proven techniques from Chris Voss (former hostage negotiator), especially from the book Never Split the Difference, and the “Negotiation One Sheet” preparation tool available through BlackSwanLTD.

The Change Order Story: When a PM Prepared Like a Professional

Jason tells a story about a project manager who read Never Split the Difference and then used the Negotiation One Sheet to prepare for a change order situation with an owner. What he was negotiating was fair and previously agreed in principle, but the “tendency” on the other side was to deny the request. Instead of walking in with a pile of facts and hoping they would land, the PM used the worksheet to build a narrative one that included facts, emotional connection, research, and backup. The goal wasn’t to force acceptance. It was to make the communication receivable, reduce the trust barriers, and give the owner the full story so they could judge it fairly. That’s the shift: negotiation isn’t “more arguing.” It’s better preparation and better delivery.

Technique 1: Mirroring Build Rapport by Reflecting Their Words

The first technique Jason highlights is mirroring. The concept is simple: repeat the last few words the other person said, or repeat their phrasing back to them. Jason explains why it works: people are drawn to what’s similar and distrustful of what feels alien. When they hear their own words reflected, it builds rapport. Mirroring isn’t a magic spell. It’s a signal. It says, “I’m listening. I’m with you. I’m not here to fight you.” And when you reduce that “fight posture,” the conversation opens up.

Technique 2: Accusation Audits Pull the Negatives Into the Open

Accusation audits are one of the most practical ideas in the episode. Jason describes it as labeling your counterpart’s negative emotions about you by listing the bad things they could say about you at the beginning of the negotiation. The idea is not to self-destruct. The idea is to clear the air. In many negotiations, the other party is already thinking, “You’re hiding something,” or “You’re trying to confuse me,” or “You’re pushing your problem onto me.” Those thoughts don’t disappear just because you ignore them. They sit under the surface and poison the conversation. When you name them first—respectfully—you diffuse the situation. People often respond by reassuring you, clarifying what they’re actually concerned about, and seeking common ground.

Technique 3: Get Them to Say “No”Because “Yes” Can Be Fake

Most people have heard, “Get them to say yes.” Jason flips it with Chris Voss’s idea: get them to say no. Why? Because “no” gives them agency and control. It helps them set boundaries. It creates a safer environment for real negotiation instead of forcing polite agreement.

Jason also explains the danger of false yeses. Everyone has experienced the yes that’s really a shutdown: “Sure,” meaning, “I want you out of my face.” That kind of yes wastes time because you think you have agreement, and then nothing happens. A clear “no” is often more valuable than a fake yes because it gives you real information to work with.

Technique 4: Calibrated Questions Use “How” and “What” to Create Collaboration

Calibrated questions are open-ended “how” and “what” questions that prompt longer answers, reveal key information, and introduce needs without sounding aggressive. Jason gives examples like “How am I supposed to do that?” and “What are we really trying to accomplish here?” The power is that you put the problem in their hands in a respectful way. You invite them into the solution. You get more data. And you keep the negotiation from turning into a yes/no fight.

Signals You’re Negotiating With Logic Only (And Losing)

You keep adding facts, but the other party gets more defensive instead of more cooperative.
You get a polite “yes” that never becomes action, and approvals drift into silence.
Emails turn into long arguments, and trust drops with every message.
Change orders feel “stuck,” not because the facts are unclear, but because the relationship is tense.
You feel yourself escalating because the conversation became personal instead of productive.

The Negotiation One Sheet: A Simple System That Changes Outcomes

One of the best parts of the episode is how Jason walks through the Negotiation One Sheet, because it turns negotiation from improvisation into a repeatable system. He describes these core steps: You start by clarifying the goal—writing down the best-case scenario and opening with it. Then you summarize the known facts that led to the negotiation and aim to get the other party to acknowledge the reality of the situation. Then you run the accusation audit to bring negative assumptions into the open. After that, you use calibrated questions to reveal value, uncover deal killers, and gather data. Then you label what you’ve learned (“It seems like…”). And finally, you get into offers—identifying what each side can offer, including non-cash items. Jason’s point is not that you need a script. His point is you need preparation. If you want a win-win outcome, you can’t show up with hope and frustration. You show up with clarity, empathy, and a plan.

The Follow-Up Move That Breaks Ghosting

Jason shares a simple follow-up line from the book that he says works when people stop responding: “Have you given up on this?” He explains he’s used it multiple times and gets responses, especially when the topic is important and people are avoiding it. This matters on projects because ghosting is a form of delay, and delay increases variation. A clean, direct follow-up can reopen the door without escalating.

What This Changes on Projects: More Trust, More Resources, More Flow

Jason’s bigger vision is that construction needs more trust and more win-win outcomes. He says we’re losing money, hurting relationships, and turning everything into fights—when, in many cases, there’s a fair solution available if we negotiate properly.

This connects directly to flow. When negotiations stall, the field gets punished. When PMs can negotiate better, they can secure training, staffing, and fair compensation for scope changes—meaning the workforce gets what they need to execute safely and predictably. That’s what LeanTakt and Takt systems require: stability, clarity, and reduced variation.

The Ethical Negotiation System to Use Before Any Change Order Call

Clarify the goal: define the best-case outcome and open with it clearly.
Summarize the facts to create shared reality before you push for any decision.
Use an accusation audit to diffuse distrust and bring hidden concerns into the open early.
Ask calibrated “how/what” questions so the other party helps solve the problem with you.
Label what you learn (“It seems like…”) and then move into offers to find a true win-win.

Connect to Mission

At Elevate Construction, the aim is stability teams that can plan, schedule, and flow without burnout. Jason Schroeder’s system-first lens applies here too: if negotiations constantly turn into conflict, the system is creating variation through distrust and poor communication. Better negotiation reduces that variation. It protects relationships. It helps secure the resources the field needs to execute. And it supports stable flow especially when you’re trying to run Takt with disciplined handoffs and fewer interruptions. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Conclusion

Negotiation isn’t about being slick. It’s about being prepared. It’s about honesty, transparency, and finding the win-win that’s already possible—if you present the full story in a way the other party can actually receive. If you remember one line from this episode, make it this: “It is emotion, not logic, that determines the success or failure of negotiations.” Show up with empathy. Use the tools. Download the one sheet. Read Never Split the Difference. Practice. And then take that skill back to your projects so we can have more trust, more fairness, and more win-wins.

Frequently Asked Questions

How is win-win negotiation different from manipulation?
Win-win negotiation aims for a fair outcome that protects both parties and the relationship. Manipulation tries to “win” by harming or cornering the other side, which destroys trust over time.

Why do facts and contract language often fail in change order negotiations?
Because people decide emotionally first. If the other party feels attacked or unsafe, they resist—even if your facts are correct. Rapport and trust make the facts usable.

What is an accusation audit and why does it work?
It’s when you name the negative assumptions up front (“This may sound like…”). It reduces defensiveness and builds trust because you’re addressing reality instead of pretending it isn’t there.

What are calibrated questions?
They are “how” and “what” questions that invite the other party to help solve the problem (e.g., “How do we solve this without impacting the schedule?”). They shift the conversation from arguing to collaborating.

How does negotiation help flow on a project?
Better negotiation reduces friction and delays in decisions, approvals, staffing, and change orders. Less friction means less variation, which supports stable planning and flow.

If you want to learn more we have:

Discover Jason’s Expertise:

Good to Great – Project Managers

Posted on January 13, 2026January 13, 2026 by Danny Jiménez⁩

Read 19 min

Good Is the Enemy of Great: How Project Leaders Raise the Standard and Take Teams to the Next Level

A “good” project can be the most dangerous kind of project. Not the project that’s on fire. Not the project that’s clearly failing. The dangerous one is the project that’s just good enough to keep everyone comfortable. The schedule is mostly okay. The team is mostly okay. The meetings are mostly okay. People stop feeling urgency. They stop training. They stop improving. And slowly—quietly—the standard drops.

Jason Schroeder’s challenge in this episode is a wake-up call for project managers: “The distance from good to great is so big that few teams even dare to try.” That’s not motivational fluff. It’s a warning. Going from good to great requires a level of leadership that most teams never experience because it requires discomfort, discipline, and a refusal to “arrive.”

The Pain: Good Enough Creates Hidden Drift in the Field

When a project is obviously struggling, leaders pay attention. They tighten up planning. They increase cadence. They remove roadblocks. They coach. They get serious. But when a project is “good,” leaders often relax. They tolerate sloppier handoffs. They stop pushing for clean zones. They allow meetings to get longer and less useful. They accept variation as normal. They postpone training because “we’re busy.”And that drift is expensive. It doesn’t show up all at once. It shows up later as rework, missed commitments, quality issues, safety exposure, schedule creep, and burnout during the final stretch. The project coasts early and then sprints late, which is the exact opposite of stable delivery.The system failed them; they didn’t fail the system. If leaders don’t build a system that continuously raises the standard, the standard will fall on its own.

The Failure Pattern: Comfort Turns Into Complacency, Complacency Turns Into Stagnation

Jason describes the “Good Place” problem: when teams reach a comfortable level of performance and assume that’s the destination. The work feels familiar. People feel competent. Leaders stop pushing. Improvement slows down. And the team becomes less sharp over time. Here’s the hard truth: construction punishes complacency. Every new phase introduces new risks. Every new trade partner adds new variation. Every new handoff is an opportunity for failure. If your culture isn’t improving, it’s decaying. Going from good to great is not a one-time push. It’s a culture of discipline that keeps the flywheel moving—day after day, even when you’re “doing fine.”

Empathy: Most Teams Don’t Intend to Settle They Just Stop Being Intentional

Most leaders don’t wake up and decide, “We’re going to be average.” They simply stop being intentional. They get busy. They get tired. They get caught in the noise. And “good enough” starts to feel like relief. Jason doesn’t blame people for this pattern he blames the lack of a system that creates continuous improvement and disciplined execution. Respect for people is a production strategy, and part of that respect is building a system that trains, supports, and challenges the team without requiring heroics. Greatness should not require burnout. It should require better design.

The Gap Nobody Talks About: Why “Good to Great” Is a Massive Leap

Jason’s quote is true because good and great aren’t separated by a small difference. They’re separated by a different operating system.Good teams rely on effort and experience. Great teams rely on systems and discipline. Good teams “make it work.” Great teams make it work repeatedly, predictably, and calmly—because the system supports them. Good teams get results sometimes. Great teams get results consistently. The leap is big because it requires leaders to change how they lead. It requires Level 4 leadership.

Fanaticism and the Relentless Standard: What Great Requires That Good Never Will

Jason uses a strong word: fanaticism. Not fanaticism as chaos or ego. Fanaticism as relentless adherence to the standard. Great teams don’t “kind of” do the basics. They do them every day. They keep the job clean. They plan. They make work ready. They hold huddles. They track roadblocks. They close loops. They train. They improve. And they do this even when they’re tired. Even when it’s inconvenient. Even when the job is “fine.” That’s the difference. Greatness is boring excellence, repeated.

Learn From the Best: Paul Akers and the Habit of Never “Arriving”

Jason references Paul Akers as an example of someone who never acts like they’ve arrived. The standard keeps rising because the learning never stops. That’s the Two Second Lean mindset: see waste, remove it, repeat. The key isn’t the tool. It’s the posture. Great leaders assume there is always a better way. They build that assumption into daily life. They look for waste in planning, handoffs, meetings, logistics, and communication. They improve systems, not just outcomes. This is how teams grow without relying on raw intensity.

First Who, Then What: Why the Leader Driving the Bus Matters

Jason points back to a central “Good to Great” principle: first who, then what. The leader driving the bus matters more than the plan on the wall. If the leader tolerates mediocrity, the team will drift. If the leader models discipline, the team will rise. Level 4 leadership is where this becomes visible. Level 4 leaders don’t just manage tasks. They catalyze commitment. They raise standards. They align people around a vision and a disciplined operating system.

The Five Levels of Leadership: What Changes Between Level 3, 4, and 5

Jason’s emphasis is on the shift that happens as leaders develop. Level 3 leaders often succeed through competence and personal execution. They can solve problems. They can manage schedules. They can carry load. Level 4 leaders are different. They become multipliers. They build systems that help others succeed. They create culture. They raise performance standards across the team, not just within themselves. And that’s how teams go from good to great: not by one person being extraordinary, but by one leader creating an environment where extraordinary becomes normal.

The Level 4 Leader’s Job: Catalyze Commitment and Raise Performance Standards

Jason frames Level 4 leadership as catalytic. You create a compelling vision, and you create a disciplined path to achieve it. You don’t just “ask for excellence.” You build the system that makes excellence repeatable.

That means:

you confront brutal facts without drama,
you coach standards without blame,
you train without waiting for failures,
and you keep the flywheel moving even when things are comfortable.

Level 4 leaders don’t wait for problems to push them into discipline. They live disciplined. They use discipline to prevent problems.

Signs Your Team Is Stuck at Good

Meetings drift into long updates instead of decisions and roadblock removal.
Cleanliness and organization slip because “we’re busy” and “it’s not that bad.”
Training stops because the team assumes experience is enough.
Leaders tolerate variation and rework as normal instead of attacking root causes.
The project relies on late pushes and heroics instead of stable daily execution.

What Great Looks Like: The Research Lab Example

Jason references a research laboratory example as a picture of what “great” can look like. Projects like that demand high performance: design-build or IPD alignment, strong BIM execution, prefabrication strategy, remarkable preconstruction planning, disciplined huddles, visuals, training systems, and a culture that treats quality and safety as non-negotiable. The point isn’t that every project must look identical. The point is that great projects are designed. They don’t happen by personality. They happen because leadership created the environment: clear expectations, clear systems, and relentless follow-through.

This is where LeanTakt thinking fits naturally. Great teams reduce variation, protect flow, and stabilize handoffs so the workforce can work without constant interruption. That is respect for people in action. Stockdale, Hedgehog, Discipline, and Accelerators: The Next Steps Toward Greatness Jason points to concepts like confronting brutal facts (Stockdale), finding your “hedgehog” focus (what you can be best at), building discipline, and using accelerators wisely. In construction terms, it means you don’t chase every initiative. You pick what will truly move the flywheel: planning systems, visual management, training, Takt where appropriate, and daily execution discipline. Then you stick with it long enough for the culture to change. Greatness is not a week-long campaign. It’s a long-term commitment.

How a Level 4 Leader Takes a Team to Great

Set a clear vision of what “great” looks like, then raise standards consistently without drama.
Confront brutal facts early and use them to improve systems, not to blame people.
Build daily discipline: clean zones, huddles, make-ready, roadblock removal, and closed-loop commitments.
Train continuously so the team improves before failures force learning the hard way.
Protect flow by reducing variation and stabilizing handoffs—use Takt and LeanTakt principles where they fit.

Connect to Mission

At Elevate Construction, the mission is stability—field teams that can plan, schedule, and flow without burnout. Jason Schroeder’s coaching is system-first because teams don’t rise by being yelled at. They rise by being supported with training, standards, visuals, and disciplined follow-through. LeanTakt supports that mission by reducing variation and creating flow so excellence becomes repeatable, not exhausting. 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 to go from good to great, you have to stop treating “good” like a finish line. Good is not safe. Good is comfortable. And comfort is where standards quietly die. Remember the quote Jason uses to shake leaders awake: “The distance from good to great is so big that few teams even dare to try.” Dare to try anyway. Raise the standard. Build a culture of discipline. Keep improving even when things feel fine. And lead like greatness is a system, not a mood.

Frequently Asked Questions

What does “good is the enemy of great” mean in construction?
It means “good enough” can create comfort and complacency. Teams stop improving, standards drift, and problems show up later as rework, schedule creep, and burnout.

What is Level 4 leadership in project management?
It’s leadership that goes beyond personal competence and becomes catalytic—raising standards, building culture, and creating systems that help the whole team perform at a higher level.

How do you know a project is drifting from good toward average?
Meetings stop producing decisions, cleanliness slips, training fades, variation increases, and the team starts relying on late pushes instead of steady daily execution.

How does LeanTakt connect to going from good to great?
LeanTakt focuses on stability, flow, and reducing variation. Those are foundational to great performance because they make excellence repeatable without constant firefighting.

What is the first step to raising the standard?
Get brutally honest about current reality, then choose a few non-negotiables (cleanliness, huddles, make-ready, roadblock removal) and enforce them consistently with respect.

If you want to learn more we have:

Discover Jason’s Expertise:

Implementing BIM Part 1 Feat. Greg Low

Posted on January 13, 2026January 13, 2026 by Danny Jiménez⁩

Read 21 min

BIM on Real Projects: How to Get Buy-In, Start at the Right Time, Run Kickoffs, and Stop “Figure It Out in the Field”

A lot of teams talk about BIM like it’s a “nice to have.” Something you do on the big jobs. Something you do when you’ve got extra time. Something you do when the trade partners are already into it. That mindset is exactly why BIM fails. This episode is a listener Q&A with Greg Lowe, and the theme is practical: BIM is not a fancy add-on. BIM is a field advantage when you treat it like an execution system. If you treat it like a side project, it becomes an argument about fees. If you treat it like a system that protects flow, safety, and schedule, it becomes non-negotiable.

The real issue isn’t software. The issue is leadership. And the quote that anchors this entire conversation is a leadership habit every PM and superintendent needs: “The number one question a PM should learn is: what do you need?”

The Hook: Why BIM Keeps Turning Into Drama

Most BIM drama starts the same way. A job is awarded. The schedule is tight. The design is incomplete. Trades mobilize fast. Someone says, “We should do BIM.” Another person says, “That’s an alternate.” Another says, “We’ll figure it out in the field.” And then the project pays for that decision in rework, clashes, delays, and stress. The pain isn’t just technical. It’s human. Crews get stuck with conflicts they didn’t create. Foremen spend their days solving design problems instead of building. Leaders become referees. The job goes reactive. The system failed them; they didn’t fail the system. If the project didn’t set up coordination early with clear expectations, the field gets punished for it later. BIM is one of the best ways to prevent that if it’s done with discipline.

BIM Isn’t a Fancy Add-On: It’s a Field Advantage When It’s Done Right

Greg and Jason both reinforce the same truth: BIM’s value is not in the model. BIM’s value is in the decisions the model forces early before the job is stacked, before the ceilings are closed, before the schedule is bleeding. BIM becomes powerful when it’s tied to constructability and prefabrication, when it reduces variation, and when it stabilizes handoffs. That’s why it fits so naturally with Lean thinking and LeanTakt systems. Flow doesn’t happen by wishing. Flow happens by removing conflicts before crews hit them. If BIM is set up as a production tool, it protects the workforce. If BIM is set up as a design exercise, it becomes overhead that people resent.

The First Question: How Do You Get Trade Partner Buy-In Without “BIM as an Alternate”?

The trade partner buy-in question is real. Many subs have been burned by BIM being treated as “extra work” without clear scope, clear leadership, or clear return. That’s why you can’t sell BIM with vague promises. You sell BIM with clarity. Buy-in comes from a BIM execution plan that answers: What’s the purpose? Who owns what? What level of detail is required? What’s the schedule cadence? What decisions will be made with the model? What’s the clash process? What are the deliverables? When trade partners see that BIM will reduce rework and stabilize field production, buy-in increases. When they see BIM as ambiguous coordination meetings that never end, buy-in disappears.

Confidence Comes From the Plan: Why the BIM Execution Plan Is the Whole Game

This episode makes the execution plan the centerpiece, and for good reason. A BIM execution plan is not paperwork. It’s the operating agreement for coordination. It creates control.

Without it, the project will suffer from:

unclear expectations,
unclear model responsibility,
unclear LOD,
mismatched file naming and version control,
slow responses,
and coordination meetings that produce noise instead of resolution.

With it, BIM becomes a disciplined production system. That’s why Greg and Jason keep pushing back on the idea of “we’ll sort it out as we go.” Sorting it out later is exactly what creates the field pain.

“Death Ground” Scheduling: When Prefab Is Non-Negotiable and the Data Proves It

A key idea in the episode is the moment when the schedule makes prefabrication unavoidable. If you’re on “death ground”—no buffer, tight milestones, high complexitythe only way through is to reduce field variability. Prefab is one of the strongest ways to do that, but prefab without BIM is risky. BIM gives you the confidence to prefab. It lets you spool and assemble offsite with fewer surprises. It reduces exposure time in the field. It turns installation into production rather than improvisation. That’s not theoretical. It shows up in the field story about prefabricated underground racks—spooled, color-coded, and installed fast because coordination happened early and clearly.

When Do You Start BIM on Hard-Bid Jobs? The Truth: You’re Already Late

One of the sharpest lessons in this Q&A is about timing. On hard-bid jobs, teams often wait until after award to “consider BIM.” By that time, you’re already behind. You’re already mobilizing. You’re already buying materials. You’re already scheduling rough-in.The “empty shopping cart” analogy lands because it highlights urgency: if you’re trying to coordinate after the job is already underway, you’re shopping after the shelves are empty. You don’t have choices. You’re reacting. Hard-bid doesn’t mean “no BIM.” Hard-bid means you must decide fast and set expectations immediately, or the field will coordinate with saws and hammers.

When Do You Start on Design-Build? Get In During Design

Design-build is where BIM can deliver the biggest value because you can influence decisions before they’re locked. You can shape layouts, resolve major conflicts, and reduce constructability misses while there is still time to change the plan cheaply. This is not a software decision. It’s a risk decision. If you wait until late design or early construction, you lose the best opportunity: preventing problems instead of reacting to them.

Align BIM to the Rhythm: Using Takt to Time the Last-Level Coordination

This is where the conversation ties beautifully into production. BIM coordination must be aligned to the project rhythm. If you’re running Takt zones, you don’t coordinate “whenever.” You coordinate to the upcoming zones. You create last planner-style make-ready through BIM. You resolve clashes before the zone is active. This prevents a common failure: re-coordinating the same area multiple times because the schedule keeps shifting. When BIM is aligned to Takt, the team knows what must be ready and when. It creates a cadence for coordination, not a never-ending loop.

The First Meeting Agenda: Roles, LOD, Naming, Clash Process, Ownership

The kickoff meeting is where BIM either becomes real or becomes a mess. This episode emphasizes practical agenda items: define roles, define LOD expectations, define naming and file control, define the clash detection process, define meeting frequency, and define what “done” looks like. BIM meetings must produce decisions. If meetings become status updates with no resolution, the model will drift and the field will suffer.

A strong kickoff is the difference between:

a coordinated install,
and “we’ll figure it out in the field.”

Fast Signals Your BIM Effort Will Stall

The BIM execution plan is vague or missing, so expectations are unclear from day one.
Coordination meetings happen, but decisions don’t get made and ownership isn’t assigned.
You start BIM late on a hard-bid job, after procurement and mobilization have already begun.
Trade partners are asked to model without clear LOD, naming standards, or deliverables.
Someone is still relying on “we’ll figure it out in the field” as the default strategy.

Meeting Frequency and Communication: Why “We’ll Talk Next Week” Breaks Coordination

One practical point that matters: BIM coordination needs a cadence that matches the work. If your zones are turning every week, then a slow coordination response time becomes a schedule risk. Waiting a week to answer a clash question is a week of exposure. That exposure shows up later as rework. Communication speed is part of production. This is why leaders must treat BIM like an operational system: fast feedback, clear ownership, and reliable commitments.

The 2D Holdout Problem: What to Do When Someone Says “We’ll Figure It Out in the Field”

Greg and Jason talk about the 2D holdout someone who refuses to participate in coordination and expects the field to solve it. The response cannot be aggression toward people. It must be system clarity. You make expectations explicit. You define required deliverables. You tie coordination participation to schedule risk. You escalate appropriately when needed, but you do it with facts. And you keep returning to the production truth: field coordination is expensive. Early coordination is cheaper.When a partner truly can’t model, you still need a plan: who models for them, how information is captured, and how their conflicts are resolved before installation.

The PM Question That Changes Everything: “What Do You Need?”

This quote is the leadership hinge. When PMs ask “what do you need?” they stop managing from assumptions. They start supporting production. They uncover constraints early. They build trust with trade partners. They turn coordination into collaboration. That question belongs everywhere: in BIM kickoff, in weekly coordination, in field huddles. It is a system-first mindset, and it’s how you prevent people from getting set up to fail.

A Practical BIM Playbook for PMs and Supers

Build and publish a BIM execution plan early, with clear scope, LOD expectations, and ownership.
Run a disciplined kickoff meeting that defines naming, clash process, meeting cadence, and “done.”
Start BIM immediately on hard-bid jobs and during design on design-build jobs to prevent late pain.
Align coordination to Takt or zone rhythm so the next areas are ready before crews arrive.
Handle 2D holdouts with clear expectations, defined support, and facts about risk—not blame.

Connect to Mission

At Elevate Construction, the goal is stability teams that can plan, schedule, and flow without burnout. LeanTakt supports that stability by reducing variation and making work ready before it starts. BIM, when executed properly, is a major weapon against variation. It prevents conflicts from landing on the field. It protects foremen and crews from constant restarts. Jason Schroeder’s system-first lens is consistent: don’t blame the workforce for design conflicts. Fix the system early.

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

Conclusion

BIM is not about being fancy. It’s about refusing to “figure it out in the field.” It’s about reducing waste and variation by making decisions early with the right people in the room. If you want BIM to work, stop treating it like a side project. Build the execution plan. Start early. Run kickoffs with discipline. Align coordination to the zone rhythm. And lead with the most important question a PM can learn:

“The number one question a PM should learn is: what do you need?”Ask it. Mean it. Build the system around the answer.

Frequently Asked Questions:

What is a BIM execution plan and why does it matter?
It’s the operating agreement for coordination defining roles, deliverables, LOD expectations, meeting cadence, file naming, and clash resolution. Without it, BIM becomes noise instead of control.

When should a team start BIM on a hard-bid job?
Immediately. Waiting until after mobilization increases schedule risk and forces the field to solve conflicts during installation.

How does BIM connect to Takt and LeanTakt?
Takt relies on stable zones and predictable handoffs. BIM supports make-ready by resolving clashes ahead of the zone work, reducing variation and protecting flow.

How do you get subcontractor buy-in for BIM?
Provide clarity: scope, expectations, deliverables, and how BIM will reduce rework and protect production. Buy-in increases when BIM is a system, not an undefined extra.

What do you do when someone refuses to participate and wants to “figure it out in the field”?
Set clear expectations, define who will model or coordinate the missing scope, tie the risk to schedule and cost with facts, and keep the focus on protecting the workforce from rework not blaming people.

If you want to learn more we have:

Discover Jason’s Expertise:

Ask for Help – Supers

Posted on January 13, 2026January 13, 2026 by Danny Jiménez⁩

Read 19 min

Asking for Help as a Superintendent: Learn From Wisdom, Not Sad Experience

Construction has a lone wolf problem.Not because superintendents don’t care, and not because they aren’t tough. It’s because the industry quietly rewards “rugged independence.” We celebrate the person who figures it out alone, takes the hit, stays late, and carries the stress like it’s part of the job description. Then we act surprised when people burn out, repeat the same mistakes, and feel isolated on an island of decisions. Jason Schroeder calls that out directly in this episode, and he replaces it with a better standard: asking for help is not weakness. It’s a leadership skill. And it’s one of the fastest ways to improve your planning, protect your people, and stabilize your project. Because you can learn one of two ways: “You can learn from wisdom or sad experience.”

The Pain in the Field: When the Superintendent Carries Everything

If you’ve ever run a project where you felt like you couldn’t ask for help, you know the symptoms. You hesitate to call someone because you don’t want to look incompetent. You avoid inviting feedback because you’re already overwhelmed. You stop touring other projects because you can’t “spare the time.” You make decisions in a vacuum, then deal with the consequences alone. The job becomes heavy. Logistics get messy. The plan becomes fuzzy. You start reacting instead of leading. You spend your time solving the same problems repeatedly because you’re reinventing solutions that other people already learned the hard way. And the worst part is, you start thinking that’s normal.

The Failure Pattern: Pride Creates Isolation, Isolation Creates Rework

Jason’s system-first diagnosis is that superintendents often get trapped in isolation by the way the system trains and rewards them. If leaders are praised for never needing support, they will stop asking. If asking questions gets treated like weakness, people will hide. If the culture expects superintendents to be superheroes, then the project will be built on heroics.The system failed them; they didn’t fail the system. But the outcome is predictable: isolated leaders learn by “sad experience.” They make avoidable mistakes, not because they’re bad, but because they didn’t have a feedback loop. They didn’t have fresh eyes. They didn’t have a network. They didn’t hunt as a pack.

The Quote That Should Sting: Embarrassment Is Insecurity Knocking

Jason hits on the emotional core of why people don’t ask for help. It’s embarrassment. It’s the fear of being judged. It’s insecurity knocking at the door, saying, “If you admit you need help, they’ll think you’re not good enough.” That voice is lying. The best builders ask for help constantly. They ask because they want to win. They ask because they care about outcomes. They ask because they understand that nobody can see everything, and nobody should carry everything alone. A leader who can ask for help is a leader who can learn fast and learning fast is a competitive advantage in construction.

Wisdom vs. Sad Experience: The Hidden Cost of Not Asking

“Sad experience” is expensive. It shows up as rework, delays, safety exposure, stress, and weekends that disappear. It shows up as problems that could have been prevented if someone had said, “Hey, I’ve seen this before watch out for that.”m Wisdom is cheaper. Wisdom is a phone call. Wisdom is a job walk. Wisdom is a mentor. Wisdom is a quick review of your plan by someone who’s done it. Wisdom is the gift of fresh eyes before the field teaches you the lesson with pain. Jason’s message is clear: if you want to be a professional, stop paying for lessons with schedule damage. Pay for them with humility.

You’re Not an Island: Collaboration as a Leadership Standard

Jason frames collaboration as a leadership requirement, not a personality preference. Asking for help isn’t optional if you want stable outcomes. It’s part of your operational system. It’s how you build capability faster than the project can punish you.

This is especially true in complex scopes like basements, logistics-heavy interiors, or projects with tight access and critical sequencing. Those environments don’t forgive first-time learning. If you’re the first person on your company’s team to face a certain condition, you need outside experience in the room fast.

Field Story: The Phoenix Basement Visit That Changed the Outcome

Jason shares a story that shows exactly how this works. He was facing a basement scope getting out of the hole where logistics, sequencing, and day-by-day control matter. Instead of pretending he could figure it out alone, he did something smarter: he went to Phoenix and toured another project. He looked at what went wrong, what slowed them down, and what decisions created pain.

That visit changed his approach. He came back and applied day-by-day geographical planning to the basement logistics. He built a more controlled plan, and the outcome was not vague or theoretical he describes finishing the structure within four hours of the projected finish. That isn’t luck. That is wisdom replacing sad experience.

Day-by-Day Geographical Planning: Turning Logistics Into a Real Plan

A major takeaway from the episode is that logistics can’t be left to “we’ll figure it out.” Basements, holes, tight access, and heavy sequencing require daily geographic planning. You plan where material goes, how it moves, what the crane or hoist sequence is, what areas will be active, and how you prevent congestion. When you ask for help, you get better at this fast. You learn how others staged, how they protected access, how they avoided stacking trades, and what they wish they had done earlier. This is where systems save projects. Not heroics. Not toughness. Systems.

“Go See and Steal”: Shameless Learning Is a Superintendent Superpower

Jason encourages leaders to “go see and steal.” Not steal unethically steal ideas, systems, visuals, and methods. If another project is doing something better, go learn it. Copy what works. Improve it. Bring it back to your job. The industry loses so much time because people insist on reinventing the wheel. The wheel has been invented. Go get it. And when you build a network of superintendents who share ideas, everyone wins. That’s how teams become multipliers instead of isolated fighters.

Signs You’re Acting Like a Lone Wolf

You avoid asking questions because you’re afraid it will make you look weak.
You stop inviting feedback because you assume you should already know the answers.
You don’t tour other projects or ask others to review your plan, even at major milestones.
You keep repeating the same problems because you’re reinventing solutions in isolation.
You wear burnout like a badge because “that’s just what supers do.”

Fresh Eyes Systems: Get Better Before the Project Teaches You the Hard Way

Jason’s real point is that asking for help should be a system, not a rescue move. You don’t wait until the project is on fire. You build fresh eyes into the plan early: at mobilization, before major pours, before interior ramps up, before turnover, before big access changes. Fresh eyes reveal blind spots. They catch missing constraints. They ask the uncomfortable question you avoided. They see the risk you normalized. That is priceless. It’s also a way to protect families. When the plan is better, weekends come back. When logistics are controlled, stress drops. When the system is stable, people can go home.

Hunt as a Pack: The Superintendent Advantage That Creates a Winning Culture

Jason uses a phrase that should become a leadership identity: hunt as a pack. In nature, the pack wins because it shares intelligence. It moves together. It supports. It covers blind spots. Construction leadership should work the same way. When superintendents share planning techniques, logistics strategies, safety systems, and sequencing lessons, the whole company levels up. That’s culture. That’s training. That’s stability. This is also how you create a workplace where people stay. People don’t leave because the work is hard. They leave because they feel alone in it.

The Ask-for-Help System You Can Calendar Today

Tour another project once a month and take pictures of what’s working (then apply it).
Invite “fresh eyes” reviews at key milestones, before the work ramps up.
Ask one trusted superintendent to review your day-by-day geographic plan for logistics-heavy scopes.
Build a “go see and steal” habit: copy proven visuals, checklists, and meeting rhythms.
Create a small network (3–5 people) and trade lessons weekly so learning stays consistent.

Connect to Mission

At Elevate Construction, the goal is stability field teams that can plan, schedule, and flow without burnout. LeanTakt supports that mission by making work visual, reducing variation, and building systems that protect people. Jason Schroeder’s teaching is always system-first: if a superint endent is drowning, the system didn’t support them. Asking for help is one of the fastest ways to correct that system gap because it brings wisdom into the plan before sad experience does. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Conclusion

Here’s the challenge: stop trying to prove you can do it alone. That is not leadership. That is insecurity dressed up as toughness. Real leadership is humility, learning, and building a network that makes everyone better. And remember the choice Jason puts in front of every superintendent: “You can learn from wisdom or sad experience.” Choose wisdom. Ask for help early. Build fresh eyes into your plan. Hunt as a pack.

Frequently Asked Questions

Why is asking for help so hard for superintendents?
Because many jobsite cultures reward rugged independence and treat questions like weakness. That creates isolation, even when the superintendent is doing their best.

How does asking for help improve schedule performance?
It brings proven solutions into your plan early—especially for logistics-heavy work—reducing rework, interruptions, and avoidable delays that come from learning by “sad experience.”

What is a “fresh eyes” review and when should I use it?
It’s when another experienced leader reviews your plan and site conditions to catch blind spots. Use it at mobilization and before major milestones or complex scope transitions.

What does “hunt as a pack” mean in construction?
It means building a network of leaders who share lessons, review each other’s plans, and solve problems together so no one is isolated and the whole team improves faster.

How does this connect to LeanTakt and Takt?
Takt and LeanTakt rely on stable planning and reduced variation. Asking for help improves planning quality, strengthens logistics, and helps teams protect flow through better systems.

If you want to learn more we have:

Discover Jason’s Expertise:

General Offerings

Company Offerings

Systems

Personal Development for Foremen: Invest in Your Mind and Train Your Crew Every Day

Why Foremen Get the Least Training (And Why That Has to Change)

The Foreman Story: Teaching in the Work, Not Just Managing the Work

Finish as You Go: The “Strip, Clean, Prep” Habit That Prevents Rework

Respect Yourself Enough to Go Get Training

Need vs. Want: Why Foremen Grow

Train Your Crew 5 Minutes a Day (And Why That Forces You to Learn)

Signs You’re Coasting Without Development

The Learning Loop: Explain, Demonstrate, Guide, Enable

Repetition Is the System: Why People Need to Hear It Seven Times

Start With Practical Books and Courses (Then Build a Habit)

A Simple Daily Development System for Foremen

Connect to Mission

Conclusion

Frequently Asked Questions

The Capacity to Sustain: How to Protect Your Project Team From Overburden and Keep the Job Stable

The Pain: When the Team Has No Room Left to Breathe

The Set Point on Every Project: Capacity Is Real, and It Can Be Lost

Muri, Mura, Muda: Why Overburden and Unevenness Matter as Much as Waste

The Research Lab Story: When Design Changes Ate the Team’s Capacity

Draw the Hard Line: Finish Design So Construction Can Flow

Don’t Ignore General Conditions: Staffing Is a Capacity Strategy

The Scorecard Habit: How to See Red Flags Before the Team Breaks

Why Jason Pushes 5S / 3S: Cleanliness and Organization Help You See Problems

Signals Your Team Is Over Capacity

The Dials You Can Turn (and the One You Cannot)

One-Piece Flow and First Things First: The Tire Store Story and the Jobsite Mirror

Capacity Protection Moves You Can Make This Week

Connect to Mission

Conclusion

Frequently Asked Questions

The Stockdale Paradox for Project Managers: Face the Brutal Facts Early and Still Believe You Can Win

The Pain: Projects Fail Quietly Long Before They Fail Loudly

The Failure Pattern: The Optimist Trap

Empathy: Facing Facts Can Feel Like Betrayal But It’s Actually Care

The Stockdale Paradox: Brutal Facts + Unwavering Faith

The PM’s Real Job: Trigger Red Flags and Remove Roadblocks

Why Projects Fail Quietly: Problems Stay Hidden Until They’re Too Big

Build a Culture Where Facts Are Safe

Debate the Root Cause: Ask Questions First, Don’t Jump to Answers

Signals You’re Not Facing the Brutal Facts Yet

Roadblocks on the Board: The Daily Discipline That Protects Flow

The Risk & Opportunity Register: Your Second Set of Eyes

Trigger Systems: Alarm Bells Before the Date Is Lost

Safety Triggers: Cleanliness, Organization, Morale, and Standards

Calm Response to Hard Data: Professional, Direct, and Fast

A Stockdale System for PMs: Triggers + Roadblock Removal

Connect to Mission

Conclusion

Frequently Asked Questions

Expectations Without Anger: How Superintendents Hold the Standard and Still Respect People

The Pain: When a Leader “Loses It” and Can’t Get the Day Back

The Failure Pattern: Frustrated Expectations Turning Into Anger

The Quote That Resets Leadership: Expect the Best in Yourself, Appreciate the Best in Others

Why Hypocrisy Breaks the Jobsite: You Can’t Demand What You Don’t Model

Respect Equals High Expectations: What Standards Really Mean

Separate the Standard from the Person: Attack the Process First

Signals Your Expectations Are Turning Into Anger

The Superintendent Method: Process → Resources → Standards → Support → Then Role Fit

Consequences Without Punishment: How to Change Circumstances the Right Way

Stop Emotional Manipulation: Why Yelling, Cussing, and Threats Backfire

Certainty and Significance: The Hidden Trigger Behind Blowups

Growth and Contribution: The Shift That Keeps You Calm and Effective

The Expectation System: High Standards With Respect for People

Connect to Mission

Conclusion

Frequently Asked Questions

The Courage to Be Disliked: Lead Without Needing Approval and Stop Giving Your Self-Worth Away

Why This Matters: You Can’t Lead If You Need to Be Liked

The Trap: When Your Self-Worth Lives in Other People’s Opinions

Signs You’re Leading for Approval Instead of Purpose

“In the Arena”: What to Remember When Critics Show Up

Field Story: When the Project Team Didn’t Want Him There

Primary vs. Secondary Happiness: Where Peace Actually Comes From

Personality Patterns: Why Some Leaders Crave Praise

The Shift That Changes Everything: Separation of Tasks

Anger and Yelling as Control: Why Emotional Manipulation Backfires