The Myth of Micro-managing

Posted on January 20, 2026January 20, 2026 by Jason Schroeder

Read 15 min

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

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

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

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

That’s not progress. That’s disconnection.

Why “Micromanaging” Became a Punchline on Job Sites

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

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

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

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

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

What People Actually Hate: Bad Leadership Behaviors, Not Guidance

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

Here’s the difference:

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

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

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

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

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

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

Construction can’t run like that.

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

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

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

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

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

EDGE: Explain, Demonstrate, Guide, Enable.

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

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

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

So why do we treat jobsite coaching differently?

Why Masters Get a Pass: Stephen Curry and Skill Development

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

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

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

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

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

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

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

He references the classic phases:

Forming
Storming
Norming
Performing

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

The mistake is thinking one approach fits every phase.

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

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

Directive Leadership Is a Tool, Not a Lifestyle

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

Leadership is the same.

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

The problem isn’t directive leadership.

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

The Hidden Cost of Demonizing Micromanaging: Nobody Teaches Anymore

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

Jason says demonizing micromanaging creates disconnection:

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

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

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

Shoulder to Shoulder Support: What Construction Actually Needs

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

That’s the heart of it.

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

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

So the fix is not “be less involved.”

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

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

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

Jason draws a sharp distinction:

You lead people. You manage things.

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

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

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

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

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

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

The real questions are:

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

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

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

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

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

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

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

Conclusion

Stop treating “micromanaging” like the enemy.

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

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

FAQ

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

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

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

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

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

If you want to learn more we have:

-Takt Virtual Training: (Click here)
-Check out our Youtube channel for more info: (Click here)
-Listen to the Elevate Construction podcast: (Click here)
-Check out our training programs and certifications: (Click here)
-The Takt Book: (Click here)

Discover Jason’s Expertise:

Meet Jason Schroeder, the driving force behind Elevate Construction IST. As the company’s owner and principal consultant, he’s dedicated to taking construction to new heights. With a wealth of industry experience, he’s crafted the Field Engineer Boot Camp and Superintendent Boot Camp – intensive training programs engineered to cultivate top-tier leaders capable of steering their teams towards success. Jason’s vision? To expand his training initiatives across the nation, empowering construction firms to soar to unprecedented levels of excellence.

On we go

Logistics Staging 2

Posted on January 20, 2026January 20, 2026 by Jason Schroeder

Read 19 min

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

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

Look at the dumpsters.

Look at the cardboard.

Look at the pallets.

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

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

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

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

Why Logistics Deserves More Attention Than It Gets

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

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

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

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

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

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

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

The core Logistics 2.0 move is this:

Build a queuing yard and a gate for logistics.

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

Then and only then release them into the building.

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

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

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

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

Key detail: flat ground.

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

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

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

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

What a Logistics Queuing Yard Must Include

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

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

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

Shakeout and Inspection: Remove Trash and Risk Before Materials Move

This is where most projects lose the plot.

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

Then later becomes:

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

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

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

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

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

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

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

Not bins by trade.

Not bins by “whatever came off the truck.”

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

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

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

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

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

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

Jason is describing it as a release system.

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

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

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

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

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

That double handling is silent budget murder.

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

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

That one principle can stabilize everything.

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

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

You need to onboard the truck and the materials.

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

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

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

Standards at the Gate: What Gets You Authorized

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

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

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

Staffing the System: One Lean Logistics Lead and Repeatable Routines

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

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

That is a production leader for material flow.

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

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

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

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

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

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

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

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

Jason uses a home improvement analogy that hits hard.

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

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

That’s not soft. That’s operational.

Joy, in this context, means:

readiness
clarity
ease
stability
flow
respect for bodies and brains

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

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

Conclusion

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

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

FAQ

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

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

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

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

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

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Morning Worker Huddle 2.0

Posted on January 20, 2026January 20, 2026 by Jason Schroeder

Read 19 min

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

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

Or the hoist.

Or the crane pick plan.

Or the loading dock.

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

Logistics starts at the entry gate.

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

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

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

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

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

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

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

It is a logistics control point.

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

The beginning predicts the middle.

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

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

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

Jason takes that pattern and applies it to construction:

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

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

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

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

The parking lot.

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

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

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

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

Wayfinding Without Visual Pollution: Simple Signs That Actually Help

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

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

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

When information is clear, the workforce flows.

Wayfinding is logistics.

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

This is where Jason gets really specific.

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

Then he asks the question most job sites never ask:

Why are workers standing out there freezing or baking?

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

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

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

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

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

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

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

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

What if workers wanted to be there?

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

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

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

Small investments can create outsized engagement.

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

This is the most powerful part of the vision.

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

He gives examples:

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

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

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

Dojo Stations to Teach the Standard

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

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

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

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

Jason ties it back to the Masagura and Genkan concept.

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

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

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

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

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

Release Criteria for the Second Gate

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

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

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

Make It Interesting: Designing for Attention and Buy In

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

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

How do we make the morning worker huddle interesting?

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

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

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

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

Jason also connects this to onboarding.

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

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

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

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

Jason makes a bold claim:

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

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

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

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

That is logistics.

And it starts at the gate.

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

Conclusion

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

Start it where the workforce starts.

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

FAQ

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

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

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

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

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

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

PMs, Shield Them from Toxic Variation, Not Growth

Posted on January 20, 2026January 20, 2026 by Jason Schroeder

Read 17 min

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

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

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

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

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

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

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

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

Human beings will complain when things change.

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

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

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

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

Change Isn’t the Enemy: Variation Is

Jason makes a statement that’s worth repeating:

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

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

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

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

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

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

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

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

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

Symptoms of Toxic Variation to Shield the Team From

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

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

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

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

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

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

Shielding is not avoidance. Shielding is system design.

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

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

Here’s the core point of the episode.

Project managers should never shield their teams from:

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

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

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

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

Growth Variation You Must Not Block

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

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

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

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

Many teams lose years because they never install the basics.

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

But effort doesn’t create flow. Systems do.

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

If the plan requires burnout, the plan is broken.

Distress vs Eustress: The Kind of Pressure That Builds People

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

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

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

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

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

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

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

That means:

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

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

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

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

“Why is Japan, Japan? Training.”

And he highlights the focus:

People. Process. Quality.

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

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

The PM Decision Filter: Shield or Share?

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

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

This is how you protect people and still improve.

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

Conclusion

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

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

But never shield them from learning.

FAQ

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

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

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

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

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

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

POND, Not POD Meeting

Posted on January 20, 2026January 20, 2026 by Jason Schroeder

Read 21 min

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

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

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

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

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

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

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

Why the Typical Morning Huddle Fails the Field

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

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

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

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

POD vs POND: The Small Shift That Changes Everything

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

That shift in timing changes everything.

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

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

The Real Purpose: Plan, Not Roll Call

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

The purpose is to make tomorrow stable.

A good POND meeting does three things:

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

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

What a POND Meeting Must Include

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

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

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

A Rolling Meeting Cadence That Creates Flow

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

Here’s the rhythm he lays out:

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

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

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

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

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

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

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

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

Roadblocks First: How Visual Maps Change the Meeting Dynamic

Jason describes a key move that changes the entire meeting.

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

That shift is huge.

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

Roadblock Prompts to Use with Trades

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

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

These questions force real planning without blaming anyone.

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

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

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

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

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

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

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

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

But there’s another trap he calls out.

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

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

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

Jason isn’t saying “no morning meeting.”

He’s saying the morning meeting should be different.

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

The purpose is simple:

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

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

Lean Behaviors 1.0 and 2.0: Training the Team Every Day

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

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

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

How to Implement Fast Without Overwhelming People

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

But the team implemented it in a day.

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

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

Common POD Mistakes That Increase Variation

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

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

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

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

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

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

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

And you can do it, too.

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

Conclusion

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

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

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

FAQ

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

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

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

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

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

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Elevate & LeanTakt Principles

Posted on January 20, 2026January 20, 2026 by Jason Schroeder

Read 28 min

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

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

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

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

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

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

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

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

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

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

Elevate and LeanTakt Principles at a Glance

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

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

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

The First Principle: Encouragement Is Oxygen for an Organization

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

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

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

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

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

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

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

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

Team Over Hierarchy: Learn From Everyone, Act as One

Elevate does not want a hierarchical feel.

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

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

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

This principle sits at the center of the entire list.

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

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

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

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

Giving and Sharing: Why We Refuse to Hide Knowledge

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

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

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

Inventors by Default: Innovation as a Daily Expectation

Elevate sees itself as inventors of products and processes.

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

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

Training and Practice: Why Skill Beats Experience

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

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

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

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

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

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

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

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

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

This is where the principles become visibly practical.

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

Why does that matter?

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

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

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

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

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

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

Culture Behaviors We Protect

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

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

These behaviors are how the culture protects itself under pressure.

Protecting Culture: Alignment Without Tearing Things Down

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

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

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

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

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

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

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

Short Cycles and Iterations: Early Check ins as Respect

Waiting until the end is disrespectful.

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

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

Mistakes: Sloppy Isn’t OK, Learning Mistakes Are

Not all mistakes are equal.

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

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

Bring Problems to the Surface: Visibility Before Fixing

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

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

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

No Punishment: Respect Through Clarity and Support

Elevate does not believe in discipline or punishment.

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

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

Cut the Waste: Emails and Non-Value Add Admin

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

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

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

Don’t Waste Time: Mewaku and Respect for Others

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

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

Clean, Safe, Organized: The Visible Signature of Lean

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

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

Team Success Only: No Lone Geniuses

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

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

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

One Piece Flow: Plan, Do, Finish

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

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

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

Transparency: The Environment Where Everything Works

“Everything we do only succeeds in transparency.”

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

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

How to Use These Principles Tomorrow

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

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

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

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

Conclusion

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

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

FAQ

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

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

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

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

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

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Not Having the Right PM

Posted on January 20, 2026January 20, 2026 by Jason Schroeder

Read 19 min

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

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

Not “bad person” wrong. System wrong.

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

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

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

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

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

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

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

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

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

They can be helpful. They are not sufficient.

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

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

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

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

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

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

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

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

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

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

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

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

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

That’s the job.

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

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

Local Optima vs Global Optima: One Ball, One Direction

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

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

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

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

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

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

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

Signs Your PM System Is Off Track

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

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

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

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

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

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

ORCA stands for:

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

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

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

Track and Measure Without Living in Spreadsheets

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

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

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

How to Coach a PM Back On Track Before Replacing Them

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

That’s when leadership has to make a decision.

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

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

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

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

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

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

3 Traits to Hire and Train For

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

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

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

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

Conclusion

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

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

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

Take one thing. Action it.

FAQ

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

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

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

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

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

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Failing to Plan

Posted on January 20, 2026January 20, 2026 by Jason Schroeder

Read 23 min

Failing to Plan: How Projects Break Before They Start (And How to Fix the System)

You can feel it the moment you walk onto a jobsite that started too early.

There’s motion everywhere, but it’s not progress. Crews are working hard, foremen are making calls, the project team is scrambling, and everyone is “doing their best.” Yet the site feels like a pinball machine: people bouncing from issue to issue, waiting on answers, waiting on materials, waiting on access, waiting on a decision that should’ve been made weeks ago. It’s loud, it’s tense, and it’s expensive.

That’s what failing to plan looks like in real life. And it’s one of the most common causes of project failure because it starts the failure cycle before the project even gets a fair chance.

The “No Plan” Jobsite: Chaos That Looks Like a People Problem

When planning is missing, the job doesn’t slow down. It speeds up in the wrong direction.

Workers show up ready to work, but they don’t know where to go. They can’t get to the work because the work isn’t ready. The team tries to “make it look like the project is moving,” so more people arrive, more activity starts, and the site turns into organized confusion. Everyone is busy. Nobody is flowing.

This is the moment where the industry falls into the same trap: blaming the people. The talk becomes, “We can’t get good workers,” or “This trade is killing us,” or “The foreman can’t run a crew.” But in the conversation between Jason Schroeder and Adam “Beanie” Bean, the diagnosis is clear: the people are often failing despite their best efforts because the system didn’t set them up to win.

Why Projects Start Before They’re Ready

So why does it happen? Why do projects start before they’re ready?

Because time gets burned upstream.

Before crews ever mobilize, time is consumed by decisions, buyout, design coordination, approvals, and the back and forth that happens when leaders are still trying to align budgets, scope, and direction. That upstream time doesn’t disappear. It steals from construction time.

Then the panic sets in. The schedule looks tight, leadership feels pressure, and the project team hears the same message: “Just get it moving.”

Planning takes time, and when teams feel behind, planning is the first thing they cut. That’s the trap. When the pressure rises, the system does the one thing it cannot afford to do: it abandons the plan.

Compressed Construction Time: The Hidden Damage Done Upstream

When construction time gets compressed, the project doesn’t become “faster.” It becomes unstable.

The team starts making decisions in the field that should’ve been made in preconstruction. Constraints aren’t removed ahead of time, so crews run into walls all day long. The schedule stops being a plan and becomes a document people point at while they improvise around reality.

This is where leaders need to tell the truth: if the job needs more time, pretending it doesn’t won’t make it so. A compressed timeline without a plan doesn’t produce heroics. It produces overtime, stress, rework, quality drift, and safety risk. It breaks people and families. And if the plan requires burnout, the plan is broken.

Stop the Line: Full Kit and the Discipline to Pause

One of the most powerful ideas in this transcript is the discipline to stop.

Not stop as punishment. Stop as a production strategy.

Beanie calls out the tendency to “ready, fire, aim” and the reflex to throw the schedule out the window to “get things moving.” Jason connects it to the idea of stopping the line so you can fix the process, not blame the person. This is where Lean thinking becomes practical: if something isn’t ready, you don’t muscle through it and punish the field for the consequences. You stop, you make it ready, and you flow.

Full kit is the simplest way to describe it: don’t start work until the crew has what they need to succeed. If we wouldn’t skip civil work and pour foundations on dirt, why would we skip planning and expect stability?

Go to the Gemba: How to See the Real Problem (Flow)

Planning doesn’t live in spreadsheets. Planning lives at the work front.

Beanie describes walking the job “10 to a dozen times a day,” not to micromanage, but to see where the system is stopping. Where is the crane idle? Where are groups of people standing around waiting? Where is work not flowing?

That’s not a personality trait. That’s operational excellence.

When you go to the Gemba, you stop debating opinions and start seeing facts. And the people doing the work will tell you what’s broken in the system. They usually want to tell you. The issue isn’t that the field is hiding problems; the issue is that leadership isn’t close enough to see them and humble enough to ask.

Find the Constraint, Fix the Constraint, Restore Flow

Once you can see stoppages, the next move is to find the constraint.

Beanie’s story about a cooling tower rebuild at a power station makes this real. The site wasn’t “a workforce problem.” The site was clean and organized. The workforce was capable. The issue was that decisions, materials, design responses, and information weren’t arriving fast enough. The system’s biggest constraint was controlling the speed of everything.

So instead of yelling at crews to go faster, he attacked the constraint. He focused on restoring flow. And the results were dramatic: same people, different process, radically different production.

That’s the point: the system sets the ceiling. Crews can only move as fast as the biggest constraint in the system.

Why Good People “Fail Despite Their Best Efforts”

Jason said something that should hit every leader in the gut: the trades are bending over backwards. They add labor when asked. They rush when asked. They push when pushed. They try hard.

And still the project fails.

Not because they don’t care. Not because they’re not capable. But because they are being asked to execute in chaos. They are being asked to perform without a stable plan, without full kit, without reliable information flow, and without an environment designed for success.

This is where the leadership posture matters. The system failed them; they didn’t fail the system.

Early Warning Signs You’re Starting Too Soon

When you walk the site, these are the signals that planning and readiness are missing:

Crews waiting in groups for materials, access, answers, or direction
Equipment sitting idle while labor burns time “staying busy”
Work fronts opening and closing rapidly because constraints weren’t removed
Frequent “we don’t have design, so we can’t plan” statements used as a shield
Leaders adding bodies to the site before the site can support them
A schedule that exists on paper but is ignored in the field

Those aren’t character flaws. Those are system alarms.

Precon Is Production Too: Plan It Like You Mean It

Here’s the trap: many teams act like preconstruction is “administration” and construction is “production.”

That’s backwards.

Preconstruction is the first production system. If you want flow in the field, you must build flow in precon. If you want reliable commitments in the field, you must create reliable decision making upstream. If you want Takt to work, you must create conditions where crews can actually hold the beat.

LeanTakt thinking makes this visible: stability is not created by pushing harder. It’s created by making ready.

Build It Virtually First: Models, Simulation, and “If We Can’t Draw It…”

Jason shared a key line from his experience: “If we can’t draw it, we can’t build it.”

That statement is more than a slogan. It’s a requirement for reliability.

When teams fail to plan, they skip the act of building the project virtually first. They don’t simulate it. They don’t physically visualize it. They don’t walk through it with trade partners. They don’t use models, mockups, or simple physical representations to see the work before it happens.

You can’t “wing” complexity.

If the project is complicated, the team must slow down long enough to design the work. That’s how you eliminate chaos before it hits the field. That’s how you protect safety, quality, and families.

The Trap of Task Switching in Precon

Beanie added another preconstruction killer: task switching.

When precon teams stack too many tasks into a day, they lose massive time to context switching. Work doesn’t finish; it just gets “touched.” People feel busy, but output is low. And when precon output is low, construction readiness is low. Then construction time gets compressed. Then leadership panics. Then planning gets cut. Then the field pays for it.

Precon must be managed like production: clear outputs, focused batches of work, and visible flow.

What “Good” Looks Like: Benchmarking to Excellence, Not Average

One of the most important mindsets in this conversation is the refusal to benchmark against “industry average.”

Industry average is not the target. Excellence is the target.

Jason and Beanie both point to learning from better systems, better planning habits, and better operational models. When you see what “good” looks like, you stop accepting chaos as normal. You stop tolerating planning gaps as “just construction.”

Respect for people is a production strategy. When the plan is stable, the work is safer, the quality is higher, and the stress drops. Flow over busyness.

Daily Learning Loops: ORCA and Not Waiting Until the End to Learn

Most companies wait until the end of the project to do “lessons learned.” Then they shelve them, forget them, and repeat the same mistakes.

Beanie calls out a better way: daily learning loops that improve tomorrow’s plan using what happened today. The point is simple: don’t delay learning until it’s too late to matter.

If you want reliability, you must build feedback into the system while the work is happening.

Precon Fixes That Restore Time and Flow

If your precon process is chewing up construction time, start here:

Define the output of every major precon task before you start it
Reduce task stacking so work can finish instead of constantly switching
Use visual models and simulations to “build it” before you build it
Align decisions, buyout, and design responses to protect field flow
Plan the work with trade partners early so constraints surface early
Treat precon like a production system with flow, not a calendar of meetings

That’s how you stop stealing time from the field.

When you do this work, you are building a system that can actually support people doing the work. And that is the mission, whether you say it directly or not: we’re building people who build things.

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

Conclusion

If your project is behind before it starts, the answer is not to push harder. The answer is to plan better, make ready, and restore flow.

Go to the Gemba. Find where the work stops. Fix the constraint. Stop the line when full kit isn’t present. Build it virtually before you build it physically. Treat precon like production. And protect people by designing a system that sets them up to succeed.

Because when planning is missing, the most dedicated crews in the world will still struggle. As Jason put it, “We’re failing despite our best efforts.”

FAQ

What does “failing to plan” look like on a jobsite?
It usually shows up as motion without progress: crews waiting, equipment idle, constant questions, and a schedule that’s ignored because the work isn’t truly ready. People look busy, but flow is broken, and the project starts burning time and money immediately.

Why do projects start before they’re ready?
Upstream time gets burned in decisions, approvals, design churn, and buyout delays. That stolen time compresses construction, and leadership feels pressure to “get it moving,” which often causes teams to abandon planning right when they need it most.

How do I know if the problem is the people or the system?
Start by examining the process: are crews getting materials, answers, access, and workable information when they need it? If not, the system is the constraint. Good people can only perform as well as the environment allows.

What is the fastest way to diagnose what’s really wrong in the field?
Go to the Gemba and look for stoppages in flow: where work is waiting, where equipment isn’t moving, where crews are stacked up. Then ask the people doing the work what’s blocking them. That usually reveals the constraint quickly.

How can preconstruction planning reduce stress and rework during construction?
When precon builds the project virtually, reduces task switching, clarifies outputs, and removes constraints early, construction starts stable. That stability reduces panic, overtime, rework, and safety risk because the work can flow the way it was intended.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

How To Access Construction Project Digital Plans

Posted on January 20, 2026January 20, 2026 by Jason Schroeder

Read 24 min

How to Control Digital Plans So the Field Always Builds the Right Thing

Most teams think they have a “digital plans” problem. They don’t.

Most teams have an information control problem.

Because getting drawings onto an iPad is not the hard part anymore. Bluebeam, Procore, and modern platforms have made access pretty frictionless. The hard part is making sure the field is seeing the right information, at the right time, in the right place and that nobody is accidentally building unapproved scope because a bulletin got forwarded, an RFI response got shared early, or somebody printed an old sheet.

That’s why this topic matters. If you want flow in the field, you have to protect the foremen and crews from bad inputs. Not because anyone is careless. Because the system is usually set up with too many “sources” and not enough “truth.”

And if you want to run a clean job, the digital plan set has to be treated like a production system, not a file cabinet.

The Real Problem Isn’t “Access,” It’s Information Control

Access is easy. Control is hard.

A crew can have a tablet, an app, a login, and a synced folder and still build the wrong thing if the information ecosystem is messy. When you have multiple plan sets floating around, a “latest” folder that isn’t actually latest, and changes coming in faster than your posting process can handle, you are not managing digital plans. You are gambling.

Here’s what “control” really means in the field:

The team knows exactly where to look for current buildable information.
Everyone agrees that the single source of truth is the only truth.
Changes are not “socialized” as buildable until they’re financially approved and formally issued.
The process is fast enough that people don’t create workarounds.

That last point matters. If the system is slow, humans will route around it. They’ll screenshot. They’ll text a PDF. They’ll forward an email thread. They’ll print something “for convenience.” And that’s not because workers or foremen are the problem. It’s because the system made the right way too hard.

The system failed them; they didn’t fail the system.

Make Field Access a Contractual Given

If you want stability, start with a few non negotiables.

One of my favorites is simple: foremen are contractually required to have a tablet Windows tablet or iPad and, on that device, they have access to the current drawings and the information they need. Then, at key stations in the field, you provide a digital field kiosk so crews can access the model and information when they need it.

That’s not fancy. That’s basic.

When you set this up as a given, you eliminate half the friction immediately. You’re not scrambling to “get the drawings out there.” You’re designing the system so the drawings are always there, and you’re designing the job so the team can actually use them.

And you’re sending a message: information belongs in the field. Not locked behind an office wall, not trapped in email threads, not guarded as a “PM only” resource.

One Source of Truth or You Get Chaos

Once access is handled, the next step is even more important: one source of truth.

You need one official digital plan set. One location. One workflow. One way of posting and distributing changes. If the project has more than one “official” place where people can get drawings, it’s not official. It’s a rumor mill.

The reason this is so crucial is because variation is normal. Field conditions change. Designers issue updates. Owner decisions evolve. The project moves. That’s fine.

But if you don’t have a stable baseline one plan set, one schedule, one operating system then when variation shows up, the team can’t focus on solving the problem. They waste time asking:

“Which drawing are we on?”
“Did you see the latest?”
“Is that bulletin approved?”
“Was that RFI response posted?”

That kind of chaos doesn’t just burn time. It destroys trust. And once trust is gone, people stop coordinating with precision. They start protecting themselves. They start buffering with extra paperwork. And the project gets heavier every day.

The Moment Changes Hit, Your Job Is at Risk

On most projects, the biggest risk isn’t the first issue set.

The biggest risk is changes.

As soon as ASIs, bulletins, and RFI responses start flying, you have a choice. You can either build a system that controls them or you can let them control you.

Here’s the truth: if information gets distributed without a disciplined gate, trades will build it. Not because they’re reckless. Because they’re builders. They’re trying to keep production moving. If the jobsite team sends something that looks “official enough,” it will get installed, and then the project will pay for that confusion later.

So the question becomes: what is your gate?

The Bioscience Lab Story: Systems That Kept Changes From Wrecking Flow

Let me ground this with a field story.

On the Bioscience Research Laboratory in Tucson, Arizona, the team had a strong digital ecosystem running. The project had CMIC in the background for project management and finances, BIM 360 Field for QC, BIM 360 Glue for the model, and a Bluebeam project (that distinction matters) for drawings and documents. Foremen had iPads. The model was used heavily. The information was accessible.

And yes, it took work.

There was also a posting workflow where V Construct (an offshore support resource at the time) would post drawings, hyperlink details, and help structure the information so it was easy to use. The result was that field access was real. Not theoretical.

But here’s the part that matters: the job had a lot of changes. By the end, roughly 30% of the project was under changes rooms changed, areas changed, the cafe changed yet the team was able to finish on time because the system prevented change chaos from infecting production.

That’s the key. Digital plans are not about “cool tools.” They’re about protecting flow.

The Two Rules: Financial Approval + No Untracked Distribution

The system had two rules that acted like guardrails.

First: financial approval all the time.

Second: never distribute official buildable information without the change being tracked financially.

This is the part most teams miss. They think the posting process is the process. It’s not.

Posting is the last step of a larger system.

If an ASI, bulletin, or RFI response is issued and distributed, trades have to be notified and you have to ensure financial approval is in place or you’ve just set the project up for a scope fight.

So the workflow was disciplined: before anything was posted and routed as buildable information, the team issued a PCO (Potential Change Order) with a ROM (Rough Order of Magnitude) dollar amount. That meant the change was either going to be paid by the owner, come out of contingency, or be projected in the right place. Either way, it was never invisible.

And once changes became heavy enough, the team tightened the gate further: they got written owner approval for the change before it was posted and distributed as buildable.

That wasn’t bureaucracy for the sake of bureaucracy. That was respect for the field. Because the field should never be put in a position where they build something and then get told, “Who told you to install that work? Nobody is paying for it.”

That’s a system failure.

Why PCO + ROM Comes Before Posting Anything “Buildable”

If you want the field to trust the plan set, you have to earn it.

Here’s what happens when you don’t do this:

The plan set becomes “maybe information.”
Foremen start asking for “confirmation” on everything.
The team reverts to email and phone calls to validate the drawings.
Work slows down because nobody wants to get burned.

When you enforce the PCO + ROM gate, you make a promise to the field:

“If it’s posted as buildable, it’s real.”

That simple promise stabilizes the job.

It also makes your change management clean. You don’t lose track. You don’t get surprised later. And you stop the slow bleed of unapproved scope.

Posting and Hyperlinking Is a System, Not a Task

A lot of companies treat posting as a clerical activity. “Get it posted when you can.”

That’s not good enough.

When the field is building in Takt and you’re trying to maintain rhythm, the plan set has to be current. You need a process that is fast, consistent, and predictable. Whether you use offshore support, an internal VDC/document control resource, or a dedicated workflow in your platform, the point is the same:

The change gets processed.
The change gets linked and placed correctly.
The right people get notified.
The field knows it’s official.
The system logs it and tracks it financially.

That’s what professionals do. They don’t just “share drawings.” They run an information production system.

Signs Your Digital Plan System Is Failing

Foremen ask, “Which sheet are we on?” more than once a week.
Trades are building off PDFs sent in emails or text messages.
RFIs and bulletins circulate before the team knows cost and approval.
The project has multiple “official” folders, binders, or plan sets.
People complain the system is “too slow,” so they create workarounds.

Protect the Field From “Maybe” Information

If you want to lead well, your job is to reduce uncertainty for the people doing the work.

That’s why I like the idea of “givens.” It’s a given that the plan set is current. It’s a given that trades know where to find it. It’s a given that there is one source of truth. It’s a given that you have one schedule. It’s a given you have one quality process. It’s a given you have one operating system.

When those givens are true, the team can focus on real problems. When those givens are not true, the team spends its energy chasing information instead of building.

And that’s where you see the hidden cost of weak digital plan control: stress, rework, delays, strained relationships, and that constant low grade panic that comes from never being sure what’s real.

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

That’s not a sales pitch. That’s an invitation to build a system that protects people.

Technology Changes, Principles Don’t

Back when I was running projects, BIM 360 Glue was a big part of how we accessed models and information. Today, platforms evolve fast. You’ve got Bluebeam, Procore, model viewers, 360 cameras tied to schedules, drones tied to schedules, underlays, augmented reality, virtual reality the list keeps growing.

That’s all fine.

But the principles don’t change:

The field needs current information at all times.
Changes must be controlled.
Information must be buildable before it’s distributed.
Financial approval must be integrated with distribution.
There must be one source of truth.

If you do those things, you can use almost any tool. If you don’t do those things, no tool will save you.

Your Operating System: One Schedule, One Quality Process, One Way of Working

This is where the conversation connects to Lean Takt, to Takt, and to the way we teach this at Elevate Construction.

If you want flow, you need stability. And stability starts with alignment. One schedule. One quality process. One information system. One operating cadence.

When I talk about tracking rooms in a Takt Plan inside Bluebeam, that’s not about Bluebeam. That’s about making the plan visible so the team can manage production. Digital plans should support that visibility, not fight it.

The jobsite does not exist to serve paperwork. Paperwork exists to serve production.

And production comes from the field.

Non-Negotiables for a Clean Digital Plan System

Require foremen to have tablets and make digital access a contractual given.
Establish a single source of truth and eliminate duplicate “official” sets.
Do not distribute buildable changes without PCO/ROM tracking at minimum.
When change volume is high, require written owner approval before posting buildable information.
Notify trades through a consistent channel so they don’t guess what changed.

Here’s the challenge: stop treating digital plans like a convenience and start treating them like a production system.

If you build a system where access is guaranteed, truth is singular, and changes are gated through financial approval before they ever reach the field, you will feel the difference immediately. The job gets lighter. Trust goes up. Coordination improves. Rework drops. And the field can build with confidence instead of caution.

And remember this line, because it’s the heart of professional information control: “The two rules were financial approval all the time, and we never, ever, ever allowed it to get distributed without the PCO being open.”

That’s how you protect flow. That’s how you respect people. That’s how you run a clean project.

FAQ

What’s the difference between “accessing” digital plans and “controlling” digital plans?
Access is simply getting drawings onto devices and platforms. Control is making sure everyone uses one source of truth, and that only financially approved, officially issued information is distributed as buildable so the field never builds from outdated or unapproved scope.

Should we post ASIs, bulletins, or RFI responses as soon as we receive them?
Not as buildable information. The safe approach is to track changes financially first (PCO with ROM at minimum), and when changes are heavy, require written owner approval before posting and distributing the change as official buildable information.

Why is “one source of truth” such a big deal on a job?
Because variation is guaranteed. If the team has multiple “official” plan sets, every change creates confusion about what’s current. One source of truth stabilizes the system so the team can focus on solving real problems instead of chasing information.

Do we really need tablets for foremen and field kiosks?
If you want reliable flow, yes. Treating field access as a contractual given removes friction and prevents the project from slipping back into paper binders, email attachments, and outdated prints that create rework and delays.

How do we stop trades from building something that isn’t financially approved?
Don’t put them in that position. Build the gate into your system: no change gets distributed as buildable until it’s tracked (PCO/ROM) and approved to the standard your project requires. That’s system first leadership, and it protects everyone.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

How to Deal with Disappointment

Posted on January 20, 2026January 20, 2026 by Jason Schroeder

Read 22 min

How to Deal With Disappointment Without Losing Momentum in Construction

You can feel disappointment in your body before you can explain it. A plan collapses. An event gets canceled. A goal you were chasing suddenly looks like it’s slipping away. And for a moment, it’s not just “a setback.” It feels personal.

That moment is where a lot of builders get stuck. Not because they’re weak, but because they care. They were invested. They put in the hours. They rallied people. They pictured the finish line. And when the finish line disappears, it’s easy to start telling yourself a story you don’t want to believe: “Maybe I’m not successful. Maybe this isn’t working. Maybe I’m wasting my effort.” Here’s the pain in the field and at home: disappointment doesn’t just slow your mood. It can hijack your thinking. It can make you reactive, short, and exhausted. It can make a leader stop leading and start merely surviving. The failure pattern is usually this: we measure success by one visible outcome, and when that outcome gets delayed or taken away, we assume the whole mission failed. We stare at the “box of cookies,” and because the box isn’t coming out right now, we decide the whole factory is broken.

The system failed them; they didn’t fail the system. Most of us were never taught a reliable way to process disappointment, reset our mindset, and rebuild our next steps without turning the setback into an identity crisis. A stable way forward starts with a simple truth: disappointment is human. You don’t have to deny it to grow through it.

A real example makes this clear. A boot camp was planned, the team invested a lot of hours into it, and then it got canceled unexpectedly close to the event. That kind of sudden shift tips you over. It did for the people involved. For a couple of days, clarity was gone. But the recovery didn’t come from pretending it didn’t hurt. It came from going back to purpose, adjusting the process, and pivoting toward serving people in other ways. And that matters because disappointment isn’t rare in construction. It’s normal. The question isn’t whether you’ll face it. The question is whether you’ll have a system to recover fast, without losing your momentum, your dignity, or your relationships.

When the Plan Gets Pulled Out From Under You

Disappointment hits hardest when you are doing everything “right.” You were preparing. You were organizing. You were building something good. And then a variable outside your control changes the whole map.

This is where leaders often make the wrong move: they try to think their way out of emotion immediately. They jump straight to logic and skip the human part. But you can’t skip it. If you don’t process disappointment, it doesn’t disappear. It just leaks out as frustration, negativity, and burnout.It’s okay to be upset. It’s okay to be down. It’s okay to be bummed. It’s okay to be tipped over. You’re a human being. Denying it doesn’t make you strong; it just makes you numb. The win is not “never feel disappointment.” The win is “feel it, then recover.”

The Hidden Failure Pattern: Measuring Success Only by the “Cookie Box”

Here’s a powerful analogy that fits builders perfectly: imagine a cookie factory. Ingredients go in. Conveyor belts move products through steps. Systems apply frosting. People check quality. And eventually, a box of cookies comes out at the end. A lot of us treat our goals like that box. We fixate on the finished outcome as if it’s the only evidence we’re succeeding. But when disappointment hits, the box is the first thing to disappear. And if the box is your whole identity, you collapse with it. A stronger mindset is to measure the factory, not just the box. How are the ingredients? How are the conveyor belts? Are the steps still working? Are we developing people? Are we building capability? Are we strengthening the system that produces results over time? When you focus on the process, disappointment becomes a pivot point, not a dead end.

The System Failed Them; They Didn’t Fail the System

Disappointment often turns into self-blame because people don’t have a supportive system around them. They don’t have coaching. They don’t have a framework. They don’t have a stable routine for resetting after a hit. That’s not a personal weakness. That’s a missing system. The answer is to build a recovery system the same way we build production systems: clear purpose, clear steps, and steady progress. That’s leadership. And it’s also compassion.

A Field Story: The Boot Camp Gets Canceled and Everyone Feels It

When the boot camp got canceled close to the event, it created shock. The investment was real. The expectations were real. The disappointment was real. And the first reaction was exactly what you’d expect: getting stuck in the mud. The mind started spinning stories about what the cancellation “meant.” It felt like a verdict on success. The recovery started with one question: what was the purpose? The purpose wasn’t the event itself. The purpose was developing people. So the path forward became: adjust, be nimble, react, and keep serving. The “box of cookies” changed. The factory still mattered. That shift didn’t erase disappointment. It restored direction.

Recenter on Purpose Before You Rebuild the Plan

The purpose is the stabilizer. When you lose an outcome, purpose tells you what doesn’t change. If your purpose is to develop people, you can develop people in a boot camp, in short training clips, in site visits, in coaching, in a phone call, in a message of encouragement, and in daily improvement. The delivery method can change without losing the mission. This is where builders get their footing back: purpose first, plan second.

Keep It Simple: Excellence Over Perfection

One of the sneakiest traps in disappointment is perfection. When you’re already tipped over, perfection becomes an excuse to freeze. You start telling yourself you’ll move when it’s “right” again. But “right” is a moving target, and waiting for perfection is how momentum dies. Excellence is different. Excellence says: do the best you can with what you know today, then improve tomorrow. Get the message out. Make the next call. Teach the next lesson. Take the next step. That mindset is how you keep moving without burning out.

Progress Is Happiness: Why Small Steps Beat Big Emotional Swings

There’s a quote worth tattooing on your brain: progress is happiness. Not perfection. Not applause. Not the finish line. Progress. That matters because disappointment makes you feel like you went backward. The fastest antidote is to create a small, undeniable forward step. It can be tiny. But it needs to be real. Micro-actions do two things: they rebuild confidence, and they rebuild identity. You stop being “the person who got disappointed” and become “the person who keeps moving.” This is also Lean thinking in life: continuous improvement through small steps every day. Move the needle just a little, consistently, and over time the results become exponential.

Signs You’re Stuck in the Outcome Trap

You’re telling yourself the goal is “ruined” because one event or milestone didn’t happen the way you expected.
You keep replaying the disappointment and can’t identify the next smallest step forward.
You’ve tied your identity to one outcome, so the setback feels like a verdict on your worth.
You’re waiting for motivation to return before you act, instead of acting to restore motivation.
You’re isolating, getting bitter, or withdrawing from the people you were trying to serve.

If you see these signs, don’t shame yourself. Just recognize the pattern and return to the process.

Pivot the Process: Strengthen the “Conveyor Belts,” Not the Outcome Fantasy

When disappointment hits, the best question is: what part of the process can we strengthen right now? Maybe you can shift from a big in-person event to smaller training touches. Maybe you can build a steady cadence of coaching. Maybe you can focus on supporting a group that’s already hungry for improvement. Maybe you can keep the mission alive through consistent communication. This is how builders win: we don’t worship one outcome. We build systems that produce outcomes. In construction terms, we don’t wait for perfect conditions. We make ready, remove constraints, and keep production flowing.

Bring It Back to Flow: Building a Steady Rhythm

This is where LeanTakt and Takt fit naturally. Takt is about rhythm. LeanTakt is about designing stability so people can work in flow instead of chaos. Disappointment is a disruption. The recovery is restoring rhythm.Rhythm looks like this: one small improvement daily, one meaningful conversation daily, one act of service daily, one step that moves the mission forward daily. Flow over busyness. If you’re moving, you can steer. If you’re frozen, everything piles up.If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

The Two Traps That Make Disappointment Worse

The first trap is denial. Acting like you’re fine when you’re not. That doesn’t heal anything. It just delays recovery. The second trap is catastrophizing. Taking a real disappointment and turning it into a permanent story: “This always happens. I’m not good enough. Nothing works.” That story is poison.The healthier path is to acknowledge the disappointment, then choose your lenses. You can put on the “this is horrible” lenses, or you can put on the “let’s go to work” lenses. You’re human, so the emotional lenses show up. The leadership move is switching lenses on purpose.

Turn Disappointment into Contribution

One of the most powerful reframes is this: disappointment can push you into deeper contribution. Sometimes adversity is the soil where growth happens. Not because hardship is fun, but because hardship forces clarity. It forces gratitude. It forces you to stop drifting and start living intentionally. That’s why it’s worth asking: can I fast-track the good in my life right now without waiting for a crisis? Can I prioritize my family, my health, my relationships, and my purpose now? You don’t have to wait for an “end in sight” moment to live fully.

Three Micro-Actions to Regain Momentum This Week

Name what you’re feeling, then ask: “What was the purpose?” Write the purpose in one sentence, and let it guide your next move.
Take one tiny action within 24 hours that serves someone: a call, a message, a short training clip, a check-in, a coaching moment.
Choose your lenses on purpose: take off the “poop glasses” and put on the “let’s get to work” glasses by identifying one process improvement you can make today.Tiny steps, repeated, become a life.

The Challenge: Choose Your Next Tiny Step Today

Disappointment will visit you again. That’s not pessimism. That’s life. The difference-maker is whether you’ll have a system to recover quickly and keep going. So here’s the challenge: don’t camp in disappointment. Feel it. Learn from it. Then take the next tiny step. Progress is happiness. And progress is available today. You can live heaven on earth right now: service, family, giving, growth, contribution. That’s not a fantasy. That’s a choice you can start making in the next five minutes. Keep moving. Keep learning. Keep serving.

Frequently Asked Questions:

Is it normal to feel knocked down by disappointment as a leader?
Yes. It’s human to be upset, down, or tipped over when something doesn’t meet your expectations. The healthier approach is to acknowledge the emotion, then recenter on purpose and take the next small step.

How do I stop tying my self-worth to one outcome?
Shift from outcome obsession to process focus. Measure the “factory,” not just the “box of cookies.” If you’re strengthening the system, developing people, and improving daily, you’re still succeeding even if one event or milestone changes.

What does “progress is happiness” look like in daily life?
It means taking micro-actions that move you forward: a short coaching moment, a small improvement to your routine, a single constraint removed, or one meaningful conversation. Small progress restores momentum and confidence.

How does this connect to LeanTakt and Takt?
Takt is rhythm, and LeanTakt is stability and flow. Disappointment disrupts rhythm. Recovery is restoring rhythm through steady daily improvement, removing constraints, and keeping the system moving without heroics.

What if my disappointment is serious, not just a minor setback?
The principle still holds: don’t deny it, and don’t camp there. Get support, lean into purpose, and find the next smallest action you can take. Serious hardship may require more time and help, but it doesn’t remove your ability to move forward one step at a time.

If you want to learn more we have:

Discover Jason’s Expertise:

General Offerings

Company Offerings

Systems

How to Deal With Disappointment Without Losing Momentum in Construction

When the Plan Gets Pulled Out From Under You

The Hidden Failure Pattern: Measuring Success Only by the “Cookie Box”

The System Failed Them; They Didn’t Fail the System

A Field Story: The Boot Camp Gets Canceled and Everyone Feels It

Recenter on Purpose Before You Rebuild the Plan

Keep It Simple: Excellence Over Perfection

Progress Is Happiness: Why Small Steps Beat Big Emotional Swings

Signs You’re Stuck in the Outcome Trap

Pivot the Process: Strengthen the “Conveyor Belts,” Not the Outcome Fantasy

Bring It Back to Flow: Building a Steady Rhythm

The Two Traps That Make Disappointment Worse

Turn Disappointment into Contribution

Three Micro-Actions to Regain Momentum This Week

The Challenge: Choose Your Next Tiny Step Today

Frequently Asked Questions:

SUBSCRIBE NOW !

Subscribe to our newsletters and stay updated!

Important Scam Alert: Fake Elevate Construction Job Emails

Related Books

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

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

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

Related Books

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

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

Related Books

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

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

Calumet "K"

faq

General Training Overview

Superintendent / PM Boot Camp

Takt Production System® Virtual Training

Onsite Takt Simulation

Foreman & Field Engineer Training

Testimonials

Testimonials

agenda

Day 1

Foundations & Macro Planning

day2

Norm Planning & Flow Optimization

day3

Advanced Tools & Comparisons

day4

Buffers, Controls & Finalization

day5

Control Systems & Presentations

faq

UNDERSTANDING THE TRAINING

VALUE AND RESULTS

PLANNING AND SCHEDULING TOPICS

APPLICATION & TEAM ADOPTION

VIRTUAL FORMAT & ACCESSIBILITY

faq

GENERAL FAQS

CURRICULUM & OUTCOMES

LOGISTICS & FORMAT

PRICING & VALUE

SEO-BASED / HIGH-INTENT SEARCH QUESTIONS