In Sync

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

Read 28 min

Getting in Sync: Why Flow Happens When Trades Focus on Each Other, Not Just Their Tasks

There is a moment in every Takt simulation when the group stops struggling and something clicks. The work that was chaotic and colliding becomes smooth. The rhythm that was absent becomes palpable. And every time it happens, the shift is not in the tasks. The tasks are the same. The shift is in where people are looking. They stopped watching their own work and started watching each other. They stopped processing the activity and started anticipating the person. That moment, in a simulation in Germany, or in a church activity room, or on the floor of a construction project, is what flow actually feels like. And it is entirely available to every trade partner on every project, the moment the system is designed to make it possible.

The Problem That Nobody Names Correctly

The construction industry has been trying to improve production for decades by focusing on the tasks. Better CPM schedules. More detailed look-aheads. More frequent planning meetings. More detailed procurement logs. These are all task-focused interventions, and they all produce marginal results because they are solving the wrong problem. The problem is not that the tasks are poorly tracked. The problem is that the trades are not in sync with each other. They are executing their individual scopes in isolation, handing off to the next trade when their work is nominally complete, and moving on without any real awareness of whether the people behind them are ready to receive what was left for them. That is not a scheduling failure. It is a system design failure.

The Failure Pattern

The failure pattern is predictable. A trade gets into an area, executes their scope, finishes when the schedule says to finish or when the work runs out, and moves to the next area. What they leave behind may or may not be ready for the next trade. Punch list items remain in the space. Materials from the previous scope are still staged in the way. The connection points between scopes have not been inspected. The area has not been cleaned. And because the next trade’s start date was set by the schedule and not by the actual state of the space, they begin work in an environment that is not fully ready. They lose time in the first day getting set up, resolving leftover conditions, and figuring out what the previous trade intended. The first day of every Takt cycle becomes a recovery day rather than a productive one. And the project never gets into flow because the conditions for flow are never fully established before the next cycle begins.

The System Failed, Not the Trade

This is not a failure of professionalism. Trades who leave areas unprepared for the next crew are not careless. They are responding rationally to a system that measures task completion, not handoff quality. If the metric is whether the drywall is installed, the drywall installer will install drywall. Whether the space is properly prepared for the painter who comes next is not their measured responsibility under most scheduling systems. The system never encoded that expectation. The system never protected the time needed to fulfill it. And so the behavior that produces poor handoffs persists, not because people do not care, but because the system never gave them the time, the expectation, or the model for something better.

What the Clapping Game Taught Jason About Flow

Jason Schroeder describes a team activity from a church setting that became one of the clearest analogies he has found for how Takt planning and trade coordination are supposed to work. In the activity, participants stand in a group and pass a clap from person to person around the circle. When people are focused on the task of clapping, they are thinking about when to clap and where to send it. The rhythm is inconsistent. Some passes are too fast, some too slow, and the group stays out of sync regardless of how hard everyone is trying.

Then something shifts. Someone makes eye contact with their partner before the clap arrives. They begin to anticipate. They can see, from the other person’s posture and timing, when the clap is coming. They are ready. They receive it smoothly and send it on in the same rhythm. When that behavior spreads around the circle, the group stops being a collection of individuals doing individual tasks and becomes a team producing a shared rhythm. The clapping is not harder or faster. It is in sync. And in sync is what flow feels like.

In construction, every trade is either focused on the task or focused on the team. A drywall crew focused only on the task installs drywall and moves to the next area. A drywall crew focused on the team installs drywall, QCs the work before demobilizing, cleans the space, removes their gang boxes, completes the punch list in that area, stages materials for themselves in the next space, and leaves the area in a condition that the painter can enter and be immediately productive. They passed the clap properly. And the painter, who knew what to expect because the system is designed that way, arrives ready to receive it.

Takt First, Then Pull: Getting the Sequence Right

One of the foundational insights this episode clarifies is that the construction industry has the system sequence backwards. Pull planning and the Last Planner System are excellent tools. They are not, however, the primary production system. They are what pulls to the primary production system, which is Takt.

Taiichi Ohno at Toyota set the car assembly line on a Takt time, meaning a governed rhythm. Everything else, the motor delivery, the seat installation, the parts supply, was pulled to that rhythm. Nobody talked about pull planning as the main event. Pull was what made the Takt system function. The Takt rhythm was the backbone.

In construction, the equivalent is a Takt plan that governs the pace and zone sequence of the project. Last Planner pull planning, Scrum for the office team, weekly work plans: all of these pull to the Takt backbone. When a project runs only on Last Planner without a Takt backbone, it is the equivalent of designing a parts delivery system without first designing the assembly line. The parts might arrive. They will not arrive in sync with a rhythm that produces flow because no rhythm was established.

What Buffers Are Actually For

The most important practical insight in this episode is what buffer time in a Takt cycle is designed to do. Most people think of buffers as time set aside in case something goes wrong. That is part of the function. But the deeper function of the buffer is preparation and quality.

When a trade finishes their scope in a Takt cycle before the end of the cycle, the correct response is not to push into the next zone early. The correct response is to use the remaining time to QC the current work thoroughly, punch list the area, clean and demobilize, stage materials for the next cycle, prepare layout, train the crew on what is coming, coordinate with the trade behind them, and walk the next area to confirm it will be ready. All of that is buffer use. All of that is what makes the next cycle start on time, in a ready space, with a crew that is prepared rather than scrambling.

In the simulation with Janos and Marco in Germany, when the batch sizes were optimized and the Takt time was right, Jason found himself finishing his work package with five to seven seconds left in the 40-second cycle. Instead of pushing into the next area, he staged materials for the trade behind him. He QC’d his own work. He prepared his materials for the next cycle. And the whole simulation ran smoother because every participant was doing the same. The buffer was not idle time. It was production time directed at making the next cycle succeed rather than pushing more work into the current one.

Here Is What Being in Sync Looks Like in Practice

Before every Takt cycle ends, a trade that is in sync with the system is asking:

Have we QC’d the completed work and resolved all open punch list items in this area?
Is the space clean and demobilized, with our materials and equipment removed or staged correctly?
Have we walked the next area to confirm it is ready to receive us at the start of the next cycle?
Have we staged the materials and equipment we need for the next cycle so we can hit the ground running on day one rather than spending day one getting set up?
Have we communicated with the trade behind us to make sure they know what they are walking into and what we are leaving for them?
Have we looked the next trade in the eyes, metaphorically or literally, and confirmed that the handoff is ready?

When those questions are answered yes before the cycle ends, the next cycle begins in a condition that allows flow. When they are not answered, the next cycle begins in recovery mode and the project never finds its rhythm.

Built for Trade Partners Who Want to Win Together

The opposing squares game that Jason describes at the close of this episode makes the team dimension of this clear. A group of people trying to navigate past each other in opposite directions will fail every time if they are each figuring it out individually. They will fail if they silo into small groups. They will fail if they focus on their own movement without coordinating with the whole. They only succeed when they appoint a leader, gather information collectively, make a shared plan, communicate it to everyone, execute together, and adapt as a group. That is not a team-building exercise. It is a description of how a Takt system functions when it works. Trades following a common rhythm, anticipating each other, preparing for each other, and measuring success not by whether they finished their own task but by whether the team produced flow. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Get in Sync and Stay There

The question that closes this episode is the right one to carry back to every project: are the trade partners on your site focused on their individual tasks, or are they focused on each other? Are they anticipating the needs of the teams ahead of and behind them? Are they using the buffer time in their Takt cycles for preparation and quality rather than pushing more work? Are they treating the trades behind them as customers whose success depends on how well the handoff is made? When the answer to those questions is yes, flow is present. When the answer is no, the project is a collection of siloed tasks that happen to be in the same building. As Jason closes with the image of the clapping circle: only when people look each other in the eyes and anticipate the rhythm does the group get in sync. That is how flow is created. Focus on the people, not the task.

On we go.

FAQ

Why is Takt planning the primary production system rather than pull planning?

Because pull planning is a coordination mechanism, not a rhythm system. Pull planning works best when it is coordinating commitments to a governing rhythm, which is what Takt provides. Toyota used Takt time as the backbone of their assembly line and pulled materials and components to that rhythm. The construction industry adopted pull planning through the Last Planner System and, in many cases, implemented it without a Takt backbone to pull toward. The result is a coordination system that produces collaborative commitments without a governing pace. Those commitments tend to drift into push behavior when variation hits because there is no rhythm to hold the sequence in place. Takt first, then Last Planner pulling to it, is the correct sequence.

What should a trade do with buffer time at the end of a Takt cycle?

Use it for preparation and quality, not for pushing work into the next cycle. When a trade finishes their scope before the Takt time ends, the productive use of the remaining time is to QC the completed work, punch list the area, clean and demobilize, stage materials and equipment for the next cycle, walk the next area to confirm it is ready, coordinate with the downstream trade, and prepare the crew mentally and physically for what comes next. All of those activities are high-value uses of buffer time that directly contribute to the next cycle starting in flow conditions. Pushing into the next area early breaks the rhythm and often creates conditions that force the downstream trade to start before their area is ready.

What does “focus on the people, not the task” mean for a foreman?

It means the foreman’s primary orientation in a Takt system is not to the completion of their own work package but to the success of the handoff between their crew and the trades around them. It means knowing what condition the downstream trade needs the space in and ensuring it is delivered in that condition. It means communicating with the upstream trade when something is preventing a clean start. It means being aware of the rhythm across the whole zone, not just within the area of current work. The clapping game analogy captures it directly: the person focused only on passing the clap stays out of sync; the person focused on the eyes and energy of their partner produces flow. A foreman focused only on finishing their scope will hand off a space that is not truly ready. A foreman focused on their trade partners will hand off a space that the next crew can enter immediately and productively.

How does Kingman’s formula relate to the idea of buffer time for preparation?

Kingman’s formula describes the relationship between utilization, variation, and delay. When a Takt cycle is packed to full utilization with no buffer, any variation produces delay that cascades into the next cycle. The buffer time that Kingman’s formula requires is not empty time. It is time that absorbs variation and, when variation has not occurred, gets used for preparation and quality. Jason describes the moment in the BMW simulation when he realized that the buffer between Takt times is where the production system actually improves: not during the active cycle, where the crew is executing the standard, but in the preparation before and after, where the conditions for the next cycle are established. The buffer is where finishing as you go happens. It is where the system learns and gets better.

What is the opposing squares game and what does it demonstrate about construction teams?

The opposing squares game is a team activity where two groups face each other across a sequence of spaces and must navigate past each other to reach the opposite side, following specific rules about who can pass whom. Every time a team plays the game without coordinating as a group, they fail. They silo into pairs. They focus on their own movement. They talk to the person next to them but not to the whole team. They lose sight of the plan. The only way to win is to appoint a leader, gather information from everyone, build a shared plan, communicate that plan to every member of the team, execute together, and regroup and adapt as conditions change. That five-step process, appoint a leader, gather information, make a plan, communicate the plan, execute and adapt, is the same process that makes a Takt system function when trade partners are treating each other as a team rather than as independent contractors who happen to share a building.

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

Personal Buffers, Feat. Brandon Montero

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

Read 24 min

Are You Creating Capacity? Why Buffers in Your Week Are the Foundation of Personal Excellence

There are people in the construction industry right now who started something remarkable. They began an improvement effort, a lean initiative, a leadership development journey, a genuine attempt to run their projects better and lead their teams more effectively. They had real momentum. And then their employer piled on more work without adding more support, and the improvement effort quietly died. Not because they stopped caring. Because they ran out of capacity. The overburdened version of a talented leader is a marginal version of what they could be. And the tragedy is that nobody intended it. The work just kept coming, the buffers disappeared, and the energy and excitement and capability that made those improvement efforts possible went with them.

The Pain That Does Not Get Named

Construction is an industry that celebrates running hard. Long hours are treated as evidence of commitment. A packed calendar signals that someone is important and in demand. The leader who has no margin in their week is often the leader who gets praised for working so hard, while the slow, quiet erosion of their capacity goes unnoticed until it shows up as mediocre results, stalled initiatives, and a person who used to be on fire and now just shows up. That erosion is not weakness. It is physics. You cannot run a production system at 100% utilization without variation destroying it. You cannot run a human being at 100% utilization without variation destroying them. The same law applies.

The Failure Pattern

The pattern is recognizable to anyone who has watched it happen. A high performer gets promoted or takes on a more demanding role. The workload grows faster than the support structure. They start carrying tasks that should belong to others, either because delegation has not been set up properly or because the people below them are not yet trained to take those tasks on. They stop exercising because there is no time. They stop reading because the week is too full. They stop reflecting because reflection feels like a luxury they cannot afford. The improvement effort stalls. The creative thinking stops. The energy that made them exceptional gets consumed entirely by the urgent, leaving nothing for the important. They settle into a maintenance mode that everyone around them accepts as their new normal.

The System Did Not Support Them

This is not a story about discipline. The people who end up overburdened and marginal did not get there because they lacked grit or determination. They got there because nobody designed a system around their capacity. Nobody asked whether the workload was sustainable. Nobody built in the buffers that would have protected their thinking time, their energy, and their improvement efforts. The system created the conditions for decline and then watched it happen. That is a leadership failure at the organizational level, not a personal failure at the individual level.

What Jason, Brandon, and Effie Noticed in Mexico

This episode was recorded in a car outside Guadalajara, with Jason Schroeder, his daughter Effie, and Brandon Montero, a construction professional and close colleague. The conversation the previous day had been about people they both know well, people who had started genuinely exciting improvement efforts and whose momentum had stalled because their employers had overburdened them without providing the support those efforts required. Neither Jason nor Brandon was criticizing the people. They were lamenting the system. And out of that conversation came the question that this episode answers: what does it actually look like to have capacity, and what does a person do with it when they have it?

Effie was playing ukulele and listening to music. Brandon was making custom frames and refinishing furniture, the kind of focused, tactile, single-problem work that clears the mind and brings genuine restoration. Jason was going through old Apple Notes and flagged emails, reconnecting with ideas he had captured weeks earlier, finding inspiration he had not yet acted on. In a different mode, he was jogging in the morning, stopping at the park to do box breathing, walking in silence without music or podcasts, and returning home to kneel and think. These were not indulgences. These were the activities that made showing up at 100% possible. And every single one of them required time that had to be protected rather than filled.

What Kingman’s Formula Says About Your Week

The production law that governs this is the same one that governs every Takt wagon on every construction project: cycle time alone is not enough. You need cycle time plus a buffer for variation plus a buffer for capacity. If a drywall crew needs five full days to complete a zone and the schedule allocates exactly five days, the first interruption turns five days into six and they are working Saturday. The buffer was never there. The same logic applies to a person’s week. If every hour from 7 a.m. to 6 p.m. is committed to something, the first urgent email, unexpected call, or emotional challenge that requires a human response turns a functional day into an exhausting one. And the next day begins already behind.

The U.S. military studied this directly. Research found that soldiers could march 50 to 100% farther when they took a 10-minute break every hour than when they did not. The break was not wasted time. It was the mechanism that made the sustained performance possible. The worker who takes 10 minutes to reflect between tasks is not less productive than the one who pushes through. They are more productive, more focused, and more capable of sustaining that performance across the full day. The buffer is the thing that protects the output.

Three Things That Building Capacity Actually Requires

The first thing capacity requires is an honest assessment of current utilization. If the week is full and there is no time for exercise, reflection, meaningful relationships, thinking time, or the activities that restore energy, the week is overfull. That is not a calendar problem. It is a system design problem. And just as the solution to an overpacked Takt wagon is not to work faster but to right-size the load, the solution to an overfull week is not to be more disciplined but to redesign the schedule so the buffer exists.

The second thing capacity requires is a clear answer to the delegation question. Brandon Montero frames this precisely: there is a difference between what the people around you can do and what they should do. Tasks that belong to others but have not been transferred yet because the training has not happened represent a training priority, not a permanent responsibility. The time investment in training someone to own a task is the investment that eventually creates the capacity buffer. Leaders who hold on to tasks because they are not ready to delegate are not protecting quality. They are consuming capacity they cannot afford to lose.

The third thing capacity requires is protecting the activities that make excellence possible. These are different for every person. For Jason, it is morning exercise and reflection, thinking time, and the practice of reviewing past notes for uninvested inspiration. For Brandon, it is creative work with his hands and deep, intentional time with the people who matter to him. For Effie, it is music and the simple restoration of rest. The specific activities are not what matters. What matters is that they exist, that they are protected in the schedule, and that they are understood as production inputs rather than indulgences. You cannot help people from a depleted state. As Effie says plainly in this episode: you cannot help people if you do not have the help you need.

Here Is Where to Start on Your Calendar This Week

Before the next week begins, run through these questions:

What percentage of your waking hours are genuinely committed to active output? If the answer is above 80%, you are carrying no buffer.
Is there protected time in your week for exercise, reflection, or the activities that restore your energy? If not, that time needs to be scheduled before other commitments fill it.
Are there tasks on your plate that belong to someone else but have not been transferred because the training has not happened? That is this week’s first priority, not the task itself.
When was the last time you had genuine thinking time, uninterrupted, without inputs, to work through a real problem or capture real insights? If you cannot remember, the schedule needs to create that space.
Are you excited about your work? If the answer is no, the most likely cause is not the work itself. It is that there is no capacity left to bring energy to it.

Built for People, Not Just Projects

The North Star of Elevate Construction has always been to build people who build things. That means building people who are healthy, energized, growing, and capable of showing up at their best. A construction leader who is running at 100% utilization with no buffer is not serving their project or their crew at the level they are capable of. They are surviving rather than thriving, and the people who depend on them feel the difference. Creating capacity is not a personal preference. It is a performance strategy. Protect the buffer. Protect the thinking time. Protect the activities that make a remarkable life possible. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Plan the Buffer Before the Week Fills Up

The challenge from this episode is not complicated: go back to your calendar and plan the buffers before everything else takes the space. Protect the exercise. Protect the reflection. Protect the time with the people who help you grow. And if the calendar is already full, look honestly at what is there that belongs to someone else, train that person this week, and take the task off your plate permanently. As Keith Cunningham writes in The Road Less Stupid: the quality of your thinking determines the quality of your outcomes. You cannot think well when you are buried. You cannot lead well when you are depleted. Build the buffer and watch what comes back.

On we go.

FAQ

Why do high performers become marginal over time when their workload increases without support?

Because performance requires capacity, and capacity requires buffers. Kingman’s formula describes this mathematically: when utilization is high and variation is present, delay compounds. A person operating at 100% utilization has no response capability when variation hits, and variation always hits. The first unexpected demand consumes whatever margin existed. The second one pushes the person into reactive mode. Over time, the energy and initiative that produced improvement efforts, creative thinking, and genuine leadership get fully consumed by immediate demands. The person is still working hard. The output is marginal because the system was never designed to protect the conditions that excellent performance requires.

What is the connection between Kingman’s formula and personal capacity management?

Kingman’s formula says that the time required to complete work is not just the cycle time. It is the cycle time plus a buffer for variation plus a buffer for being near full utilization. Applied to a person’s week, it means the time required to perform excellently is not just the time the tasks take. It is that time plus margin for unexpected demands plus time for the thinking, reflection, and restoration that make sustained high performance possible. A week with no buffer is a week where the first disruption breaks the system. A week with intentional buffer is a week where disruptions are absorbed and performance stays high.

What does it mean to delegate what people should do rather than what they can do?

Brandon Montero introduces this distinction clearly. Sometimes a task stays on a leader’s plate not because they are the only one qualified to do it but because the person who should own it has not yet been trained. The leader looks at the task, concludes that the team member is not ready, and does the task themselves. That is a temporary solution that becomes permanent. The training priority is to invest time in developing the team member’s capability so the task can be transferred. Every task that is successfully transferred is a buffer permanently added to the leader’s capacity. Delegation is not just time management. It is a training strategy.

How do you protect thinking time when the week is already full?

Schedule it before anything else occupies the space. Jason Schroeder describes the experience of driving through northern Arizona with a quiet car and capturing 35 significant business ideas because there was nothing else competing for that mental space. Thinking time does not require a retreat or a dedicated day. It requires a protected 30 to 60 minutes where no input is competing for attention. That might be a morning walk, a drive without a podcast, a blocked calendar appointment that nobody can schedule over, or the 10 minutes between tasks that the military found doubles endurance. The specific format does not matter. The protection of the time does.

How does building personal capacity connect to leadership performance on a construction project?

Directly and measurably. A leader who is depleted cannot remove roadblocks with the speed and clarity the field needs. A leader who has no thinking time cannot see around corners or anticipate coordination problems before they become delays. A leader who is not exercising, reflecting, or maintaining relationships cannot sustain the energy and judgment that field leadership requires day after day. The superintendent who protects their buffer is the superintendent whose crew notices that their leader always has bandwidth for a real conversation, always has a clear answer, and always shows up ready. That is not a personality trait. It is a capacity management outcome.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Supers, Foremen, & Takt Control

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

Read 25 min

What Is Takt Control? The Short Interval Planning Standard Every Foreman and Superintendent Needs

There is a generation of foremen and assistant superintendents on construction projects right now who cannot create a three-week schedule on their own. Not in the Last Planner System. Not in Excel. Not on graph paper. They were promoted because they were good at the work. They were put in charge of crews before anyone invested in the planning capability they needed. And the superintendents above them, who do know how to schedule, are overwhelmed managing larger scopes and trying to train upward and downward simultaneously. The result is a field leadership layer that is executing from memory and instinct rather than from a plan. This is not a character failure. It is a training gap that the industry created and now has to solve.

The Problem Nobody Wants to Name

Most construction projects in the United States do not have a functional short interval planning system at the foreman and assistant superintendent level. The master schedule exists somewhere. The project superintendent may have a loose look-ahead. But the people who are closest to the daily execution of work, the foremen who lead crews and the assistant superintendents who support them, are planning their work in their heads, improvising their sequences, and restarting from scratch every Monday. There is no standard. There is no template that repeats. There is no cycle to improve. Every week is a new round of figuring it out, which means every week carries the same variation as the last. The project never gets better. It just continues.

The Failure Pattern

The failure pattern has a specific history. Before the Last Planner System, superintendents would take the CPM schedule, break it into one to six week look-aheads, and hand those to trade partners. It was a push system. The trades had no input into the sequence and no ownership of the commitments. But at least there was a written plan. Then the Last Planner System introduced pull planning, six-week make-ready look-aheads, weekly work plans built collaboratively with the trades, and a percent plan complete metric to measure execution reliability. That was better. The trades had voice in the plan. Commitments were made with genuine input.

But here is what happened over time. The people who knew how to run the Last Planner System got promoted or moved on. The next generation of foremen and assistant superintendents did not receive the training. And now, on many projects, even the collaborative work plan creation has disappeared. The weekly meeting happens. People say what they think they will work on. Nobody checks whether it aligns with the master schedule. The percent plan complete gets tracked but nobody investigates why tasks fail. And the plan, such as it is, gets rebuilt from scratch the following Monday. The system cannot improve because it never repeats anything long enough to get better at it.

What Good, Better, and Best Actually Look Like

Before defining Takt Control, it helps to be honest about where most projects sit on the capability spectrum.

Good means the superintendent creates a three-week look-ahead schedule in Excel and distributes it to the trades. That is better than running without any written short-interval plan. It is still a push system because the trades did not build it, but it at least makes the upcoming work visible and creates a reference point for daily decisions.

Better means the project has a functioning Last Planner System. The trades participate in pull planning. A six-week make-ready look-ahead tracks what needs to be ready and who is responsible for making it ready. Weekly work plans are built collaboratively and the team targets above 80% plan complete. Trade partners have genuine input and the plan reflects real commitments.

Best is Takt Control. Every Takt wagon, meaning every work package that moves through each zone on a defined Takt time, has a standard sequence of work steps mapped out for each day of the cycle. A four-day Takt time means day one, day two, day three, and day four are each defined. The trades participate in building that standard template once, during the initial pull planning process. Then that template repeats through every zone, floor, or area of the building, up to fifty or more repetitions on a large project. The foreman and the assistant superintendent do not recreate the weekly work plan from scratch each Monday. They execute the standard, track whether it is flowing, identify where the cycle time can be reduced, and refine the template as they go. That is the plan-do-check-act cycle applied to production.

What Takt Control Means in Practice

Takt Control is the practice of managing the work steps within each Takt wagon to create flow. The project superintendent or senior superintendent manages the overall Takt plan: the zone sequence, the train of trades, the buffer system, the overall rhythm. The assistant superintendent and foreman manage what happens inside each wagon: are the work steps being executed in sequence, are the cycle times matching the plan, is the crew appropriately loaded or being overutilized, is there a small buffer at the end of each cycle that confirms the wagon is not overpacked?

The target inside a Takt wagon is not 80% plan complete. It is 100%. The difference matters. A percent plan complete target at the weekly work plan level acknowledges that some tasks will not get done and measures how many did. A Takt Control target at the wagon level says that within this four-day cycle, in this zone, all of the work steps must complete. If they do not, the flow breaks. The next zone starts at a disadvantage. The sequence degrades. The standard is not a suggestion; it is the minimum acceptable outcome for that cycle.

When the foreman and assistant superintendent are on the floor watching the work flow through the cycle, they are answering three questions continuously. Is the work following the standard sequence? Is the cycle time matching the plan or is it running long? Is the crew at the right utilization level, meaning not so loaded that any variation pushes them into overburden? The answers to those three questions drive the adjustments that make each subsequent cycle faster, more reliable, and better buffered than the previous one.

Why This Matters More Than Last Planner Alone

The Last Planner System is excellent at what it does: creating collaborative commitments and surfacing coordination problems early. What it does not provide on its own is a standard that repeats and can be improved. When a trade partner is asked every week, from scratch, what they think they should be doing this week, two problems occur. First, the answer may not align with the Takt rhythm or the master schedule because it is being generated independently without reference to a repeating standard. Second, the cognitive load of recreating the weekly work plan from scratch every week consumes capacity that should be going into execution and improvement.

Compare that to a foreman who has a standard four-day sequence template for their scope of work. Once the template is created, the weekly planning meeting is not about invention. It is about confirmation and refinement. Did the last cycle match the template? Where did variation come from? What can be adjusted to make the next cycle more reliable? That conversation is faster, more specific, and more productive than starting from a blank page every Monday. And because the template repeats, every improvement sticks. The work gets better over time in a way that new-from-scratch weekly planning never enables.

The Minimum Standard and What Comes Next

Every foreman and every superintendent must be able to schedule. That is not negotiable. The minimum acceptable standard is a hand-drawn Gantt chart on graph paper if no computer is available, though every foreman and assistant superintendent should be able to use Excel for this purpose. The inability to schedule is not a technology problem. It is a training gap that needs to be closed, and it needs to be closed before someone is put in charge of a crew.

Once the scheduling capability exists, the path is clear: build the Takt plan at the project level, pull plan the standard work sequences with the trades for each Takt wagon, document the day-by-day work steps within each cycle, and then execute, track, and refine that standard through every repetition. The foreman and assistant superintendent are the people who live inside that cycle. Their job is not to manage paperwork. Their job is to stand on the floor, watch the work flow, and make it better every time it repeats.

Takt Control is what happens when all of that comes together. Flow is the measure that tells you whether it is working. If work is moving steadily through each zone, finishing the wagon on time, and starting the next zone without trades stacking, the system is functioning. If wagons are colliding, cycle times are running long, and every week feels like the first week, the standard is not yet working. Fix the standard. Improve the standard. Repeat.

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

The Industry’s Next Step

The construction industry has the tools it needs to run production-level field operations. Takt planning provides the rhythm. Last Planner provides the collaborative commitment framework. Takt Control provides the standard work loop that makes improvement possible through repetition. What is missing is the training and the culture that makes all three of those function at the foreman and assistant superintendent level. As Jason closes this episode from a hotel room in Guadalajara, the ask is direct: get your foremen and assistant superintendents scheduling. Get the standard work steps into each Takt wagon. Get them on the floor watching the cycle and making it better every time. That is how this industry builds the manufacturing-level consistency it has always been capable of but never quite achieved.

On we go.

FAQ

What is the difference between the Last Planner System and Takt Control?

The Last Planner System is a collaborative commitment system where trade partners pull plan to milestones, identify make-ready requirements in a six-week look-ahead, and build weekly work plans together. It measures execution reliability through percent plan complete and targets above 80%. Takt Control operates at a more granular level: within each Takt wagon, a standard sequence of work steps is defined for each day of the cycle. That standard repeats through every zone of the building and gets refined with each repetition. Where Last Planner asks trades to commit to what they will do this week, Takt Control defines what right looks like in advance and then measures whether the cycle achieved it. The two systems are complementary: Last Planner coordinates commitments between trades at the project level, and Takt Control optimizes the execution within each wagon at the floor level.

Why must every foreman and superintendent know how to schedule?

Because a foreman or superintendent who cannot create a schedule cannot see the future. They cannot identify what preparation needs to happen before the crew arrives. They cannot communicate commitments with precision. They cannot align their work with the trades ahead of and behind them. Scheduling is not a clerical function. It is the mechanism through which field leadership converts the plan into executable daily direction. The minimum standard is a Gantt chart on graph paper. The practical standard is an Excel-based short-interval schedule. The aspirational standard is a Takt wagon with documented work steps that are tracked and improved every cycle. None of those are possible for someone who has not developed the capability to schedule.

What does it mean to target 100% plan complete inside a Takt wagon?

It means that the standard for execution within a Takt cycle is completion, not a percentage of completion. When a Last Planner weekly work plan targets above 80% plan complete, it acknowledges that some tasks will not get done and measures the proportion that did. Inside a Takt wagon, the wagon must complete. All the work steps assigned to that zone in that cycle need to finish, because the next trade is entering that zone at the start of the next cycle. If 80% of the tasks complete, the next trade enters a zone that is not ready, the sequence breaks, and the trades begin to stack. The 100% target is not about being harder on people. It is about protecting the sequence that makes flow possible.

How does Takt Control apply the plan-do-check-act cycle?

The Takt wagon standard is the plan. Executing the work steps within the cycle is the do. Measuring whether the cycle time matched the plan, whether variation was absorbed within the cycle, and whether the crew was appropriately loaded is the check. Adjusting the standard, reducing a step that was taking longer than expected, resequencing two activities that were interfering with each other, or right-sizing the crew for the actual work content, is the act. Because the wagon repeats through every zone of the building, every improvement made in one cycle carries forward into the next. Over twelve to fifty repetitions, the cycle time decreases, variation reduces, and the crew develops a reliable rhythm that produces the flow the project needs.

What should the assistant superintendent be doing in a Takt Control system?

The assistant superintendent’s job is to live inside the Takt wagon. That means being on the floor where the work is happening, watching the sequence unfold against the standard, identifying where cycle times are running long or variation is entering the system, and working with the foreman to adjust the sequence, the crew loading, or the material delivery timing to make the next cycle better. The assistant superintendent is not managing paperwork. They are the quality control mechanism for the production rhythm. They are the person who notices that a particular work step is consistently taking six hours instead of the planned four, investigates why, fixes the input condition, and carries that fix forward into every subsequent repetition. That is Takt Control.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Why Your 5 Day Takt Time Isn’t Working…

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

Read 23 min

Why Your Five-Day Takt Time Is Probably Working Against You

About 75% of the people who have tried Takt planning come away as raving fans. The project moved better. The trades coordinated more reliably. The schedule became a real tool rather than a document. That is the overwhelming experience. The other 25% say they tried it and it did not work. And in almost every case where it did not work, the diagnosis is the same: they locked themselves into a five-day Takt time, forced it to run between Monday and Saturday, and never escaped the constraints that created. The tool did not fail them. The way they used it did. This episode, recorded in Guadalajara, Mexico before a Takt training session at LCI Mexico, addresses that directly.

The Problem Nobody Names

The five-day Takt time has become the default setting for almost everyone who learns Takt planning. It makes intuitive sense: the workweek is five days, the weekend provides a natural buffer, and organizing everything into weekly rhythms feels clean and manageable. The problem is that defaulting to five days without asking whether five is the right number for the project produces a schedule that is not optimized. It produces a schedule that happens to fit a calendar rather than one that is calculated to fit the production system. And a schedule that fits the calendar rather than the production system will eventually descend into a push scenario when the inevitable interruption hits.

The Failure Pattern

The failure mode is specific and predictable. A team adopts Takt planning with a five-day rhythm locked between Monday and Saturday. They pack their Takt wagons, the work packages that move through each zone, at or near full capacity for the five-day window. Everything looks structured and intentional. Then a delay hits. A material shortage on Tuesday. A rain day. An inspection that does not get scheduled in time. The interruption eats into the five-day cycle and the work for that wagon does not finish by Saturday. The superintendent, trained to keep the project moving, starts the next wagon on Monday anyway, because that is when it was scheduled to start. Now two wagons are in the same zone at the same time. The trades are stacked. The flow is gone. What looked like Takt planning has become a push system dressed in Takt language, and the team concludes that Takt planning does not work.

The System Did Not Fail. The Buffer Did.

The buffer capacity was there. But because the schedule was locked between Monday and Saturday in five-day increments, the only way to eat into a buffer was to delay the entire sequence by a full five days, which nobody was willing to do for a one-day interruption. So instead of shifting the phase by one day to maintain the sequence, the superintendent pushed through. The wagons collided. The chaos followed.

Jason Schroeder used a five-day Takt time for the majority of his construction career without running into this problem, and the reason is instructive. His wagons were never packed above 80% of the five-day capacity. The cycle time inside each wagon was closer to four to four and a half days, not five. That slack inside the wagon was enough to absorb the routine variation that every project generates. When the wagon was not overpacked and the schedule was not rigidly locked to calendar weeks, small delays did not cascade. The system could breathe. But that approach required discipline about not filling every available moment with planned work, and most teams using Takt today are not applying that discipline.

Two Different Jobs for the Five-Day Takt Time

Here is the critical distinction that this episode makes clear: the five-day Takt time has a legitimate and valuable role in preconstruction, and a different and more complicated role once the project moves to detailed planning.

At the macro level, meaning during schematic design, design development, and the proposal phase, a five-day Takt time is the right tool for establishing an honest overall project duration. When you plan a project at the macro level in five-day increments, blocking out holidays and mapping the flow at a high level, you build natural buffers into the system. The result is a project duration that is typically within 5% of what it actually takes to build. Compare that to CPM schedules, which in Jason’s tracked experience undercut the actual project duration by approximately 20% on average. That 15-percentage-point gap represents projects that were promised at durations they could never achieve, which is why teams end up pushing, crashing, and spending more than the budget to try to hit a date that was unrealistic from the beginning.

So at the macro level: use the five-day Takt time. It calibrates the overall duration honestly. It protects the general conditions and general requirements budget from being consumed by design scope that the project could not afford. It gives the owner and the team a realistic target from the beginning.

At the norm level, which is where the detailed day-by-day production plan lives, the five-day Takt time needs to be questioned and potentially replaced with whatever Takt time actually optimizes the project.

How to Find the Right Takt Time for Your Project

The optimization process works like this. You break the building into Takt zones, pull plan a representative zone to establish the work sequence, package that sequence into a Takt wagon, and then use Little’s Law to calculate the project duration: Takt wagons plus Takt zones minus one, multiplied by the Takt time, equals the phase duration. You then vary the number of zones and the Takt time to find the combination that gives you the most buffers within the target project duration.

If you start with a five-day Takt time and run the optimization, you may find that a three-day or four-day Takt time with a different number of zones produces 35 additional buffer days. Or 60. Or 120. Those buffer days are available to you, but only if you allow the Takt time to be something other than five. If you lock yourself into five before you run the optimization, you never discover the alternative. You leave those buffers on the table and run the project tighter than it needs to be.

Here Is What to Apply on Your Next Project

Before you finalize your Takt plan at the norm level, work through these questions:

Have you run the optimization to find the Takt time and zone count that produces the most buffer days within the needed project duration, or did you default to five?
Are your Takt wagons packed to 100% of the Takt time, or is there room inside each cycle to absorb routine variation without cascading?
Is your schedule locked between Monday and Saturday in a way that prevents you from shifting the phase by one or two days when an interruption hits?
Do you have a defined method for eating into buffers, shifting the entire phase by days rather than pushing wagons into each other when a delay occurs?
Does each Takt wagon have standard work steps documented so that the team can track whether the sequence is flowing and improving?

If most of those answers reveal a locked five-day system, the production plan has an optimization problem that will show up as either wasted time or a push scenario, and usually both.

What the Assistant Superintendent’s Job Actually Is Inside a Takt System

Jason closes this episode with a role definition that is worth stating directly. Each Takt plan needs wagons with documented work packages and work steps. The assistant superintendent’s job is to know, within each wagon, how the sequence flows for every trade in every zone. Not in a general sense. Specifically. And then to help each trade get faster and better at that sequence every cycle. The feedback loop of standard work, plan-do-check-act, improving cycle time through repetition and observation: that is where Takt planning delivers its manufacturing-level consistency. That is how a construction project gets faster over time rather than slower. And none of it is available if the Takt time was never optimized in the first place.

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

Open Your Mind to a Different Number

The invitation is simple. Stop assuming five is the answer before you have asked the question. Use five at the macro level in preconstruction because it builds honest buffers into your overall duration estimate. Then, when you move into norm-level planning, run the optimization. Let the math tell you whether the right Takt time is two, three, or four. Build your buffers into the plan. And when delays come, which they will, shift the entire phase by days to protect the sequence rather than pushing wagons into each other to protect the Monday start date. As Hal Macomber observed in the previous episode: Takt is a countermeasure to variation. A five-day Takt time locked to the calendar is a system that cannot countermeasure variation because it has no room to flex. Give the system room. Give the trades room. And watch what happens when the plan finally has enough buffer to absorb the reality of the field.

On we go.

FAQ

What is the difference between a macro-level and a norm-level Takt plan?

The macro level is the high-altitude view used in preconstruction, schematic design, and the proposal phase. At this level, a five-day Takt time is appropriate because it builds natural buffers into the overall project duration estimate. When planned this way, the project duration comes in within about 5% of what the project actually takes, compared to CPM schedules that typically undercut by around 20%. The norm level is the detailed day-by-day production plan where the actual Takt time and zone count are optimized using Little’s Law. At this level, defaulting to five days without running the optimization leaves buffer days on the table and can lead to a push scenario when interruptions occur.

Why does a locked five-day Takt time prevent you from eating into buffers properly?

Because eating into a buffer in a five-day system locked between Monday and Saturday requires delaying the entire sequence by a full five days, which teams almost never do for a one or two day interruption. Instead, they push the next wagon into the zone on Monday as scheduled, even though the previous wagon has not finished. The wagons collide, the trades stack, and what was Takt planning becomes a push system. If the Takt time is three or four days, and the schedule is not locked to the calendar week, the team can shift the entire phase by one or two days when a delay hits, maintain the sequence, and absorb the interruption without stacking trades.

How do you optimize a Takt plan to find the right Takt time for a project?

The process starts with breaking the building into Takt zones, pull planning a representative zone to establish the work sequence, and packaging that sequence into a Takt wagon with documented work steps. Then you apply Little’s Law: Takt wagons plus Takt zones minus one, multiplied by the Takt time, equals the phase duration. By varying the number of zones and the Takt time, you find the combination that produces the most buffer days within the needed overall project duration. The Takt time that results from that optimization might be two, three, or four days rather than five. Accepting whatever the math produces is what gives you the buffer to absorb variation without pushing.

What happens when Takt wagons are overpacked in a five-day system?

When wagons are packed to full capacity for five days and a delay occurs on Tuesday, the work for that cycle does not finish by Saturday. If the superintendent starts the next cycle on Monday because that is what the schedule says, two cycles are now occupying the same zone at the same time. The trades are stacked. The flow breaks. The system is now a push system. Jason’s practice for most of his career was to pack wagons to no more than 80% of the five-day capacity, which left a natural cushion inside each cycle. The internal cycle time was closer to four days, which meant small delays were absorbed without cascading. That discipline, which most teams do not apply when they are defaulting to five days, is what kept the system from decomposing.

What is the assistant superintendent’s role within a Takt production system?

The assistant superintendent’s specific job is to know the standard work sequence within each Takt wagon for every trade in every zone, and then to help each trade execute that sequence faster and more reliably with each repetition. This is where the plan-do-check-act improvement cycle lives in Takt planning. By tracking whether the sequence is being followed, identifying where the cycle time is longer than planned, and working with the trade to find a faster sequence, the assistant superintendent is the person who drives the continuous improvement that Takt planning makes possible. This function only works when the Takt time is right, the wagons are not overpacked, and the trades have room to improve rather than just survive.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

The Jack in the Box Effect

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

Read 24 min

The Jack in the Box Effect: Why Leadership Decisions Made in a Silo Always Backfire

Somewhere inside Jack in the Box headquarters, someone made a decision that seemed entirely reasonable. Set a timer. Measure how long each car waits in the drive-thru. Create accountability for speed. Deliver the food faster. Take better care of customers. The logic is clean and the intention is good. The result is that employees at Jack in the Box locations across the country now ask customers, mid-transaction, to put their cars in reverse and back up two car lengths so that a timer resets and the metric looks better. The food is no slower. The customer is no happier. The experience is now worse because the customer has been inconvenienced, possibly put at risk from the car behind them, and left with the distinct impression that something strange just happened. The strategy produced the opposite of its intended effect. That is not bad luck. That is what happens when you try to fix a culture problem with a policy.

The Pain on Every Jobsite

The same dynamic plays out on construction projects constantly. A company decides to measure something: safety incidents, PPC scores, schedule adherence, self-perform costs. A metric is defined. Accountability is attached. The people being measured respond not by improving the underlying behavior, but by adapting to the metric in ways that make the number look better without changing the reality. Safety incidents get underreported. PPC scores get inflated by superintendents who put things on the weekly plan they know will get done regardless. Schedule dates get managed by adjusting logic rather than executing work. Self-perform gets avoided to keep safety numbers clean. The measurement system produces behavior that is exactly opposite to what it was designed to produce.

The Failure Pattern

The pattern is consistent and it starts in a conference room. A leadership team or a continuous improvement team or a development group identifies a problem, designs a solution, defines a metric, and issues a policy without going to the place where the work actually happens and asking the people who do it whether the solution will work. The people who receive the policy understand immediately whether it is grounded in field reality or not. They can see the loopholes. They know what the workaround looks like. And because they were not part of the design, they do not feel ownership of the outcome. When a policy imposes accountability without providing influence, the people affected will find ways to look compliant without actually changing anything. That is not a character problem. That is a rational response to a bad system.

Leadership Teams Are Often the Last to Know

Here is the uncomfortable truth that this episode names directly: leadership teams are frequently unqualified to make the decisions they are making, not because they are unintelligent, but because they do not have the information that only exists at the place of work. A continuous improvement team that designs a safety program without ever consulting a foreman, a superintendent, or a field engineer does not know what problems that program will create in the field. A company that grades superintendents on self-perform safety outcomes they have no authority over has created a system where the metric and the authority are disconnected, which means the metric will be gamed and the outcome will be the opposite of what was intended. Superintendents who have no control over how self-perform crews are composed, trained, or managed will respond to safety accountability by doing everything they can to keep self-perform off their projects. The company loses the margin that self-perform provides. The intended safety improvement never materializes. The Jack in the Box effect.

What Happened at the Drive-Thru and What It Means

Jason Schroeder went to Jack in the Box after donating blood, ordered food for himself and his kids, and was asked by the drive-thru attendant to back up two car lengths. The attendant did not explain why. Jason had to guess. The car behind him did not know he was coming. He backed up, saw a hand gesture telling him to stay, waited, then was waved forward. The food came. He was annoyed. He has had this happen six or seven times. He still goes to In-N-Out and Culver’s instead of Jack in the Box by default.

The drive-thru timer was supposed to improve customer service. It made the service measurably worse for customers who encountered it. The employees were not trying to create a bad experience. They were responding to a metric that their culture had not prepared them to treat as meaningful. When the culture does not genuinely care about customer experience, a timer does not create that care. It creates a workaround. And the workaround produces the Jack in the Box effect.

You cannot multiply negatives. If the food is not good and the service adds friction, those are not two separate problems with separate solutions. They compound. Two negatives multiplied make the situation worse, not better. A policy that adds a third negative, the annoyance of being asked to back up your car mid-transaction, does not cancel out the others. It deepens the hole.

What Culture Actually Is and Why Strategy Cannot Fix It

Culture is not a mission statement or a set of values on a conference room wall. Culture is the story a team actually lives by, the behaviors that get reinforced and the ones that get tolerated, and the beliefs that shape how every individual responds when nobody is watching and no policy is being enforced. Peter Drucker’s observation that culture eats strategy for breakfast is not hyperbole. It is a description of what happens when a strategic decision meets a culture that was not built to support it. The decision does not change the culture. The culture absorbs the decision and converts it into something consistent with existing behavior.

Jack in the Box did not have a culture built around genuine customer care. When they added a timer, the culture responded by finding the fastest way to manage the timer rather than the fastest way to genuinely serve the customer. The timer was a strategy. The culture was the reality. The culture won.

In construction, this plays out in every company that has tried to implement lean tools, scheduling systems, or quality programs without first building the culture that makes those tools meaningful. The Takt plan becomes a document the field ignores. The Last Planner system becomes a PPC exercise that nobody believes reflects real commitments. The 5S initiative runs for three weeks and then the site returns to its previous condition. Not because the tools are wrong. Because the culture was not built to support them.

Here Is What Total Participation Actually Requires

Before any policy, metric, program, or system is implemented, ask these questions honestly:

Have the people who will be directly affected by this decision been asked for their input before the decision was made?
Do the people being held accountable to this metric have genuine influence over the outcome it measures?
Has anyone gone to the place of work and observed what actually happens there before designing a solution?
Are there loopholes or workarounds in this policy that, if used by someone not committed to the culture, would produce the opposite of the intended result?
Is the leadership team that is making this decision living under the same rules they are implementing?

If any of those answers is no, the Jack in the Box effect is a real risk. The solution is not to refine the policy in the conference room. It is to go to the field and ask the people who will implement it whether it will work.

What Good Looks Like

Ryan Schmidt and Lauren Atwell of Petty Coach Smith Civil Contractors in Florida provide the counterexample. Every job visit involves them being present. Every training deployment involves them being there. Every consultation includes pulling in the superintendents and subject matter experts who are closest to the work. When decisions are made that affect the field, the field is part of making them. The organizational transformation work they are doing with Elevate Construction includes the people who will have to implement it from day one. That is not a soft cultural preference. It is a production strategy. When people have input into the decisions that affect their work, they own the outcomes of those decisions. When they do not have input, they manage the metrics while the underlying problem continues.

The goal at Elevate Construction is a construction industry where decisions about how work is done are made with the people who do the work, not for them. That is the only approach that produces outcomes that are durable rather than gamed. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Stop Managing From a Distance and Start Leading From the Work

The closing challenge from this episode is direct: stop making decisions in a silo and expecting them to change a culture. Leadership does not produce culture through policy. It produces culture through presence, participation, and consistency. If you would not want to live under a rule yourself, you should not implement it without understanding how the people who will live under it will respond. If you are grading someone on an outcome they cannot control, you are setting up a system that will produce exactly what Jack in the Box produced: people gaming a metric to avoid consequences, with results that are worse than if the metric had never been introduced. As W. Edwards Deming put it: every system is perfectly designed to get the results it gets. Design the system with the people inside it, and the results will be what you actually want.

On we go.

FAQ

What is the Jack in the Box effect and how does it apply to construction?

The Jack in the Box effect is what happens when a leadership decision made without frontline input produces the opposite of its intended result. At Jack in the Box, a drive-thru timer designed to improve customer service led employees to ask customers to back up their cars and reset the clock, which worsened the customer experience. In construction, the equivalent is any policy, metric, or system implemented from a conference room without field input that causes the people affected to find workarounds that make the measurement look better without improving the underlying condition. Self-perform safety programs that grade superintendents on outcomes they cannot control, scheduling metrics that get managed by adjusting logic rather than executing work, and quality programs that get documented but not followed are all versions of the same effect.

Why does culture eat strategy for breakfast in construction?

Because the people doing the work respond to the culture they are embedded in, not to the strategy that was written above them. A strategy that says to implement Takt planning does not produce Takt planning in a culture that does not believe in it. A policy that says to report safety incidents does not produce honest reporting in a culture where reporting is associated with punishment rather than system improvement. Strategy defines what the organization wants. Culture defines what the organization actually does. When they are misaligned, culture wins. The only way to make strategy effective is to build the culture that makes following the strategy feel like the natural and right thing to do.

How do you avoid the Jack in the Box effect when implementing a new policy or system?

Go to the place of work before the decision is finalized. Ask the people who will be most affected by the decision what they think will happen when it is implemented. Ask specifically whether there are ways the policy could be gamed or worked around that would produce results worse than the current condition. Give those people genuine influence over the design of the policy, not just an opportunity to provide feedback that gets ignored. And do not hold people accountable for outcomes they have no authority over. If any of those conditions cannot be met, the implementation should be delayed until they can.

What does it mean to hold someone accountable to something they have no influence over?

It means creating a metric that measures an outcome the person cannot meaningfully affect, and then attaching consequences to their performance on that metric. The superintendent who is graded on self-perform safety in a company where self-perform crews are independently managed, composed, and trained cannot improve that metric by doing their job better. They can only avoid the consequence by keeping self-perform off their project entirely, which is exactly what happens. The metric produces the opposite of the intended outcome. Accountability is only meaningful when the person being held accountable has genuine authority over the inputs that produce the outcome being measured. Otherwise it is punishment disguised as management.

What is total participation and why does it matter for organizational change?

Total participation means that the people who will be affected by a decision, at every level of the organization, have genuine input into that decision before it is made. Not a survey after the fact. Not a town hall where the decision has already been made and the purpose is to explain it. Genuine involvement in designing the solution. Hal Macomber described this principle in the previous episode: the expertise and experience of the whole workforce, including the people handling material and using physical tools, is required to improve flow. Jason extends that principle to organizational decisions: if the decision affects the field, the field must be part of making it. Companies that operate this way, like Ryan Schmidt and Lauren Atwell’s organization, build cultures where people own the outcomes of decisions rather than managing around them.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Miro

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

Read 24 min

Why Miro Will Change the Way You Run Your Construction Project

There is a version of every project meeting where the person running it knows exactly what the plan is, has it fully formed in their head, and then spends forty-five minutes watching it get partially communicated, partially understood, and mostly forgotten by the time everyone returns to their desks. A follow-up email goes out. The email gets buried. Someone asks a week later what the next step was. The meeting has to happen again. This cycle is not a communication failure. It is a system design failure. And the fix is not a longer email or a more detailed agenda. It is a shift from verbal, text-based communication to visual, shared, persistent collaboration. That is what tools like Miro make possible, and once you use it consistently, you will wonder how you managed projects without it.

The Problem That Never Gets Named

Most project coordination in construction still runs through a combination of emails, phone calls, and verbal updates in meetings. The problem with all three of those channels is the same: the information lives in one place, in the mind of the person who delivered it, and disappears the moment the call ends or the meeting wraps. The person who received the update leaves with their own partial interpretation of what was said. Two weeks later, their interpretation and the original intent have diverged enough to create a real coordination problem. Nobody meant for that to happen. The system made it inevitable.

This compounds on large teams. When coordination between a superintendent, two project engineers, a project manager, and four trade partners runs through individual email threads, every one of those people is working from a slightly different version of the project plan. When something changes, the update has to reach all of them through the same unreliable, non-visual channel. Some people get it. Some do not. The project carries that misalignment in its execution until a collision makes it visible.

The Failure Pattern

The pattern shows up in a recognizable way. A coaching conversation or a project planning session produces genuine clarity in the room. Action items are agreed on. The call ends. The follow-up email is sent. Three days later, the person who received it cannot find the email, is not certain what the priority order was, and has a vague sense of what they were supposed to do but no clear reference to return to. They follow up with a question. The explanation has to happen again. The relationship between the person doing the coaching or planning and the person doing the implementation is characterized by repeated clarification rather than confident execution.

Jason Schroeder describes this pattern from his own coaching work before he switched to visual boards: clients would ask where a particular email was, whether a recommendation had been the second or the third suggestion, what the intended sequence of steps was. The information was all there, but it was buried in a format that is inherently difficult to navigate and impossible to see as a whole. Once the coaching moved onto a shared visual board, those questions stopped. The client had the link, the board was always current, and the plan was visible any time they needed to reference it.

The Shift That Changed Everything

The evolution Jason describes started with exposure to visual collaboration tools through lean and Scrum training environments. Felipe Engineer Manriquez’s Scrum course used Mural for interactive training boards, and the ability to place sticky notes, draw connections, build out templates in real time, and keep everything visible on a shared canvas demonstrated a fundamentally different way of working through complex information. Later, working with Nicholas Modig on organizational transformation programs, Jason experienced Miro and found its sketching, outlining, and mapping capabilities well-suited to the kind of visual thinking that construction systems planning requires.

The Green Street proposal is the moment where the full potential became clear. Rather than walking a potential client through a verbal description of an organizational transformation plan, Jason mapped it out on a Miro board in real time during the conversation. The client could see exactly what was being proposed, in what sequence, with what dependencies and deliverables. The response was immediate and clear. They could see the plan. They understood it. They were confident in what they were agreeing to. The board did not replace the conversation. It made the conversation produce something lasting and shared rather than something that lived only in two sets of notes.

What Visual Boards Actually Do for a Project

The first thing a visual board does is get information out of people’s heads and into a shared space. Kevin, who works internally with Elevate Construction, described the experience of mapping things out on a Miro board during a call as therapeutic. His word, not a performance review phrase. Therapeutic. Because the act of externalizing what is in your head into a visible format removes the cognitive load of trying to hold it all in working memory. You stop worrying about forgetting something because it is already on the board. You stop tracking who said what because it is already documented. You can focus on the thinking and the problem-solving rather than the record-keeping.

The second thing a visual board does is create a persistent reference. After a coaching call, the client has a link. After a planning session, the team has a board. After a proposal, the client has a shared document that shows exactly what was agreed to and in what sequence. That reference does not degrade over time the way a memory does. It is the same on day twenty as it was on day one, except that it has been updated with progress and new decisions. The question of what we agreed to in that meeting is no longer a question. The answer is on the board.

The third thing a visual board does is make complex systems comprehensible at a glance. A Takt plan, a weekly work plan, a pull plan, a scrum board for the project management team: all of these are inherently visual structures. When they are displayed and managed on a visual board that the whole team can see and interact with, the structure of the production system becomes legible to everyone who needs to work within it. Alignment is not something that has to be achieved through repeated communication. It is something that exists in the visible structure of the board.

Here Is Where to Start on Your Project

If you want to move your project coordination from email-based to visual-board-based, begin with the most confusing coordination challenge you currently have:

Move your weekly work plan to a visual board and run your weekly planning meeting from it rather than from a spreadsheet or whiteboard.
Create a coaching board for each foreman or team member in your organization that tracks their current assignments, progress, and next steps in a visible format.
Map your Takt plan backbone on the board and pull your Last Planner commitments to it so the connection between the rhythm and the short-interval work is visible.
Run your scrum meeting for the project management team from the board so that who has what, what is blocked, and what is coming next is always visible to the whole team.
Use the board during client calls and proposals so that the plan is built in front of them rather than described to them.

Expect it to take approximately seven meaningful interactions with the tool before it starts to feel natural. Use it once. Use it again. Find a real scenario where it changes how a conversation goes. Then it will become a habit rather than an experiment.

Built for Builders Who Think Visually

Construction is an inherently visual discipline. Builders read drawings, not paragraphs. They think in spaces, sequences, and layouts. They understand a project plan better when they can see it than when they hear it described. Visual collaboration tools are not a technology trend. They are a better match for how construction professionals actually think than the text-based, email-driven communication systems that most projects still rely on. Lean construction has always known this: all lean systems are seeing systems. The weekly work plan, the Takt plan, the huddle board, the pull plan, all of them exist to make the invisible visible. A visual collaboration platform extends that principle to every level of the project, from the field crew’s daily plan to the organizational transformation program the owner is committed to. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Get on the Board and Stay There

The transition from email-based coordination to visual-board-based coordination is not a software upgrade. It is a shift in how the team thinks about shared information. Information that is visible to everyone is information that can be acted on by everyone. Information that is buried in someone’s inbox or held in someone’s memory is a single point of failure. As Jason puts it plainly: once you get fast at it, once you can build a board in real time while a client is watching, the impact is immediate and lasting. People comprehend better. They retain more. They come back to the reference instead of asking again. And they are genuinely impressed by the clarity of a leader who can make a complex plan visible in real time. That is what visual systems do. Start there.

On we go.

FAQ

What is Miro and how is it different from a standard whiteboard or shared document?

Miro is a digital visual collaboration platform that allows teams to create shared boards containing sticky notes, diagrams, maps, images, links, trackers, and freehand sketches, all in a single persistent canvas that every member of the team can access, edit, and reference at any time. Unlike a physical whiteboard, it does not get erased. Unlike a shared document, it is inherently spatial and visual rather than text-sequential. Unlike an email thread, it keeps everything in one place where anyone with the link can see the current state of the plan without having to read through a chain of messages to reconstruct it. For construction teams, it is the closest digital equivalent of the visual management boards that lean construction has always relied on.

How does Miro support lean construction systems like Takt and Last Planner?

Directly and practically. The Takt plan backbone, which governs the rhythm and zone sequence of the project, can be built and displayed on a Miro board where the whole team can see and interact with it. The Last Planner pull planning process, which coordinates short-interval commitments from the trades to support that rhythm, can happen on the same board. Scrum boards for the project management team, which track what each person is working on, what is blocked, and what is coming next, can run on Miro. Weekly work plans and daily huddle boards can be managed there as well. The result is a single visual environment where every layer of the production control system is visible and connected rather than scattered across different spreadsheets, email threads, and whiteboards that nobody outside the immediate meeting room can see.

Why is visual communication more effective than verbal or email-based communication for project teams?

Because construction professionals think spatially and visually. They read drawings, not paragraphs. When information is presented visually, in a diagram, a map, a board with explicit spatial relationships between items, it is processed and retained differently than when it is delivered verbally or in text form. Jason observes four specific improvements when coordination moves to visual boards: retention goes up, comprehension goes up, the team has a persistent reference to return to rather than relying on memory, and clients and partners are genuinely more confident in the plan because they can see its structure rather than having to take the presenter’s word for how it fits together. All of those outcomes directly reduce the rework in coordination and alignment that absorbs a significant portion of every project manager’s week.

What is the Takt-as-flow, Scrum-as-pull framework and how does it apply to a visual board?

Jason describes the structure of a well-run construction project this way: the Takt plan is the backbone of the project, governing the rhythm and pace at which work moves through zones. It is the flow system. The Scrum process used by the project management team governs how the support work, the procurement, the coordination, the RFI management, the inspection scheduling, is pulled toward that backbone to keep the field productive. It is the pull system. On a visual board, you can make both layers visible and connected: the Takt rhythm as the governing structure, and the sprint-based commitments of the office team explicitly tied to the milestones in that rhythm. When both are visible in the same environment, the connection between what the office team is doing and what the field team needs is no longer abstract. It is visible.

How long does it take to become comfortable enough with Miro to use it confidently with clients?

Jason’s estimate from direct experience is approximately seven meaningful uses before the tool starts to feel natural rather than effortful. The progression is: use it once to understand the interface, use it again on a real problem, find one scenario where it changes how a conversation goes in a way you could not have achieved without it, and repeat until the tool becomes the default rather than the exception. At that point, the ability to build a visual plan in real time during a client conversation, in a way that the client can see developing and respond to, becomes one of the most impactful things a construction leader or consultant can do to demonstrate competence and earn alignment. The investment in learning the tool is small relative to the return.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

The Three Things Our Industry Needs! Feat. Hal Macomber

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

Read 23 min

Are You Measuring Flow? The Three Things Every High-Performing Industry Does That Construction Does Not

Here is a fact that should bother everyone in this industry: construction productivity in North America has been declining since 1987. Not stagnating. Declining. While other industries have grown dramatically in output per worker, per dollar, and per unit of time, construction has moved backward. The tools are better. The technology is more powerful. The workforce is not less capable. And the results are getting worse. Something fundamental is being missed, and it is not a tool or a software upgrade. It is the way the production system is being designed, measured, and improved. That is the conversation that Hal Macomber, a lean construction researcher and practitioner with decades of experience applying production theory to the built environment, brought to this episode of the Elevate Construction podcast.

The Pain Nobody Wants to Own

The standard diagnosis of construction’s productivity problem blames labor costs, material costs, regulation, and supply chain complexity. Those are real factors. They are not the root cause. The root cause is a production system that was not designed according to production laws, that does not use flow as its primary improvement metric, and that ignores the expertise of the people closest to the work when it comes to making things better. The industry is measuring the wrong things, designing systems that create the delays they then try to manage, and leaving most of its collective intelligence untapped.

The Failure Pattern

The pattern shows up on almost every project in an almost identical way. The schedule is built around CPM logic, which tells you what to start and when, without governing the pace at which trades work or the rhythm of handoffs between them. Trades are pushed into work as soon as their predecessors finish, regardless of whether the downstream trade is ready to receive the work or whether the upstream trade can sustain the pace. When variation hits, and variation always hits, highly utilized crews have no response capacity. One delay cascades into the next. The project lengthens. More people are added to compress the schedule. Utilization goes up. Variation stays high. Delay compounds. The system produces the result it was designed to produce, which is not flow.

The Gap Is a Design Problem

The people doing this work are not failing. The system they are working inside was never designed for flow. A foreman who is managing a crew in a space where two other trades are also working is not incompetent. They are surviving a production design that put too many things in the same space at the same time because the schedule said it was possible, not because the physics of work said it was. A superintendent who is firefighting material delays is not disorganized. They are managing the consequences of a procurement system that was never synchronized to the production rhythm. The system failed them. The job is to fix the system.

What Two Identical Towers Proved

Hal Macomber and Corey Hackler, now a lean leader at DPR Construction, worked together in the early 2000s on a project in La Jolla, California involving two identical bed towers. The senior superintendent on one tower managed to the CPM schedule, starting everything when the schedule said to start it. Corey took a different approach on the second tower, focusing on flow rather than starts. The result was measurable and striking: the flow-managed tower started one month later and finished two and a half months earlier. Same building. Same trades. One production philosophy created a dramatically different outcome.

This is the proof of concept that the industry has had access to for more than two decades and has not fully acted on. Takt planning, which governs the pace and rhythm of trade handoffs rather than simply tracking start dates, was the framework that made flow possible on that tower. The trades made a commitment to each other: by 9 a.m. Monday morning, the space will be ready for whoever is coming in next. That commitment, grounded in a shared rhythm and enforced by mutual accountability, is what flow actually looks like in practice.

Three Things the Rest of the World Is Doing

Hal identifies three practices that high-performing industries use consistently and that construction, for the most part, does not. The first is using flow as the principal improvement measure. This means that the question driving every decision is not whether the schedule has green bars but whether work is actually moving steadily through the production system without stopping, waiting, or stacking. The second is designing the production system based on production laws, specifically Little’s Law, Kingman’s formula, and the law of variation. Most construction professionals have not studied these laws and are therefore designing systems that violate them, without knowing why the results are so consistently poor. The third is tapping into the expertise of the whole workforce. The people handling the material, using the tools, and doing the physical work know exactly where flow is breaking down. Construction, by and large, does not ask them.

Why Kingman’s Formula Changes Everything

Kingman’s formula describes the relationship between utilization and variation in producing delay. When crews are fully utilized and variation is high, delay does not increase linearly. It curves toward infinity. Think of highway congestion before the pandemic: a road that is 70% utilized handles variation smoothly. A road at 95% utilization turns a single tapped brake light into a traffic jam that lasts six hours. Construction sites run at high utilization by design, because the CPM schedule pushes as much work forward as fast as possible. When variation enters a system at that utilization level, the delay it produces is far greater than intuition suggests. The only countermeasures are reducing variation, reducing utilization by building in capacity buffers, or both. Takt planning does both simultaneously.

What Takt Actually Does That CPM Cannot

Takt is not a more sophisticated version of CPM scheduling. It is a different production design philosophy. CPM tracks starts and finishes in sequence. Takt governs pace and rhythm. CPM allows work to stack in spaces. Takt prohibits it by design. CPM does not require trades to coordinate their pace with each other. Takt requires it explicitly. The fishbone analogy that Hal describes captures the structure clearly: the Takt backbone governs the rhythm of the whole project, and everything else, materials, labor, information, inspections, is pulled to that rhythm. The backbone is flow. The ribs are what is pulled to support it.

Little’s Law adds the mathematical foundation. When batch sizes are smaller, lead times are shorter and waiting time decreases. A trade that finishes its portion of a floor in two days and hands off rather than finishing the whole floor in five days and then handing off creates opportunities for downstream trades to enter the space sooner, reduces the amount of work in process, and shortens the overall project duration. The counterintuitive insight is that finishing faster by doing less at a time produces better outcomes than pushing as much work forward simultaneously as the schedule will allow.

Here Is What to Start Measuring on Your Project

Before running another weekly schedule update, ask these questions about flow instead:

How many times did a trade stop work today because the space was not ready, the material was not available, or the information was missing?
Are wagons in your Takt plan starting and finishing as planned, not just starting?
Is the number of daily stops trending down from week to week, or holding steady?
Do your crews have capacity buffers built in so that variation can be absorbed without cascading into the downstream trade?
Are you tracking flow efficiency across zones, or only tracking whether the overall schedule date is still holding?

If those questions are hard to answer, the production system is not yet measuring what matters.

Built for Every Person on the Project, Not Just the Scheduler

The third of Hal’s three practices is the one most consistently ignored. The people running pipe crews, framing walls, and installing mechanical systems know exactly where flow is breaking down on their portion of the project. They know which handoffs are rough, which materials arrive late, which coordination gaps slow them down every week. A production system that does not capture their input is designing improvements without its best data source. Morning worker huddles, short-interval planning sessions with foremen, and genuine two-way communication about what is blocking flow are not soft cultural initiatives. They are production strategy. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Run Toward These Principles

Hal’s closing advice to the industry is the right one: start practicing. Do not wait for a perfectly repetitive building sequence to try Takt. Take the next non-repetitive scope of work and Takt plan it. Learn the rhythm. Learn the handoff. Learn how variation affects the pace and what buffers are needed to absorb it. Build the expertise before the stakes are at their highest. Jason’s version of the same advice is equally direct: run to these principles, not away from them. Imagine what the industry looks like when it has given Takt planning the same decades of development that CPM has received. That day starts with one project team deciding to measure flow, design accordingly, and engage everyone doing the work. As Iris Tommelein, director of the Project Production Systems Lab at UC Berkeley, stated plainly: Takt applies to all work, even non-repetitive work. There is no scope that is exempt and no project too small to begin.

On we go.

FAQ

What are the three things high-performing industries do that construction does not?

Hal Macomber identifies them clearly. First, they use flow as the principal improvement measure, meaning every decision is evaluated by whether it improves or degrades the steady movement of work through the production system. Second, they design their production systems based on sound production laws, specifically Little’s Law, Kingman’s formula, and the law of variation, rather than intuition or tradition. Third, they tap into the expertise of the whole workforce, including the people closest to the physical work, when identifying where flow breaks down and how to improve it. Construction has access to all three practices and consistently underutilizes them.

What is Kingman’s formula and why does it matter for construction scheduling?

Kingman’s formula describes the mathematical relationship between utilization, variation, and delay. When both utilization and variation are high, delay does not increase proportionally. It compounds toward infinity. A fully utilized crew that encounters variation has no capacity to absorb it and cascades the delay downstream. A crew with some capacity buffer can absorb variation locally and protect the downstream trade from feeling it. The construction implication is direct: CPM scheduling pushes utilization to its maximum because every crew starts as early as possible. This makes the system maximally sensitive to variation. Takt planning builds in rhythm and buffer, which reduces both utilization pressure and the cascading effect of variation.

What does it mean that Toyota’s production line was a flow system, not a pull system?

The distinction Hal draws is important. When people describe Toyota as a pull system, they are describing how material is pulled to the production line based on demand signals rather than pushed in advance. But the line itself is a flow system: every station operates at the same rhythm, governed by Takt time, and work moves steadily from one operation to the next at a consistent pace. The construction parallel is that Takt governs the rhythm of the entire project, and Last Planner pull planning coordinates the short-interval commitments of the trades to that rhythm. They are not competing systems. Takt sets the pace and Last Planner makes the commitments that allow the pace to be kept.

How do you measure flow on a construction project?

Hal offers two complementary measures. The first is whether wagons in the Takt plan are starting and finishing as planned. A wagon that starts on time but finishes late is breaking flow downstream, even if the start metric looks good. The second and more powerful measure is tracking stops: how many times did work fail to proceed because the space was not ready, materials were unavailable, qualified workers were not present, or the preceding trade had not completed their work? Tracking stops and driving that number down over time is a direct measure of improving flow. The goal is not zero variation. The goal is a system that can absorb variation without stopping.

Why does Takt apply to non-repetitive work, not just repetitive sequences?

Hal’s argument is that non-repetitive work is actually the best place to practice Takt, because each sequence only runs once. A mistake in one train does not cascade to twenty subsequent trains. That makes non-repetitive work a lower-risk learning environment where teams can develop the habits, relationships, and timing discipline that Takt requires before applying it to large repetitive sequences where errors are more costly. Beyond the practice rationale, Iris Tommelein’s 2018 statement makes the theoretical case clear: the production laws that Takt honors apply to all work, regardless of whether it repeats. Variation compounds with dependence in any sequence. Rhythm and handoff discipline reduce that compounding in any sequence. There is no construction scope where flow is irrelevant.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Coaching – Dress & Appearance – Implementation Series

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

Read 17 min

Are You Dressing for the Role You Have or the Role You Want?

There is a general superintendent Jason Schroeder watched for years who was exceptional at his craft. His notekeeping was disciplined. His projects ran well. He wanted to be promoted and could not understand why it was not happening. When he finally sat down with leadership, the feedback was direct: he was not showing up to enough public events and was not visible enough for people to advocate for him. He changed that habit. He started showing up. He started being seen. The promotion came. The work had never been the issue. The advertising had.

Dress and appearance work the same way. They are how a construction professional advertises for the position they want before anyone has agreed to give it to them.

You Have to Campaign

Jason used a political analogy in this episode that is worth sitting with. In a presidential race, the candidate who shows up everywhere, who talks to people, who makes themselves visible and present, tends to win over the candidate who believes their record should speak for itself. The record matters. But the record alone does not close the gap. The showing up closes the gap.

In construction, the equivalent of showing up is how you carry yourself every day in front of the people who will eventually make decisions about your career. Your dress, your grooming, your posture, your presence in meetings, your willingness to be visible on the project, all of it communicates something before you say a word. And the question is not whether it communicates. It always does. The question is what it communicates.

Jason has watched more than fifty people over his career scratch and beg for promotions while simultaneously refusing to do the things that would signal readiness. They did not dress for the next role. They did not show up to company events. They did not adjust how they presented themselves in meetings with owners and clients. And then they were surprised when the promotion went to someone else who, by the measures that mattered, had been advertising for the role more consistently than they had.

The Foreman Story

One of the most direct examples Jason shared in this episode involved a foreman he invested everything into. He helped this person get into a concrete superintendent position. He worked on their per diem package. He moved them to the right location. He trained them, coached them, and advocated for them internally. And then the promotion stalled.

Jason went to a general superintendent he respected and laid out the situation. The response was brief and final. Look at how he dresses. Look at how he shaves. Look at how he keeps his hair. That is all I need to tell you. He is not ready. Someone with that much experience reading people had already made the assessment from appearance alone, not because appearance is the deepest measure of a person, but because how you handle the details you can control tells a trained observer exactly how you will handle the details you cannot. Dress is a leading indicator. It signals whether the habits of excellence have been extended into every corner of a person’s life or only the areas that feel important to them.

How You Do One Thing Is How You Do Everything

This phrase runs through the episode and it is the real argument Jason is making. It is not that a nice shirt makes someone a better superintendent. It is that the discipline required to dress intentionally every day, to take care of your appearance consistently, to show up looking like you meant to, is the same discipline that shows up in every other area of professional performance.

The person who lets their handwriting be careless is often the same person who lets their daily report be careless, who lets their field notes be incomplete, who lets the punch list accumulate. The person who cannot be bothered to iron a shirt or trim their beard is often the same person who cannot be bothered to read the specifications before the pre-construction meeting. These are not coincidences. They are expressions of the same underlying standard applied consistently across everything the person does.

Jason was clear that this is not about expensive clothes or a particular style. He spent years in ties when no one else was wearing them, looking a little out of place, and found that the change in his own mindset was worth more than any reaction from anyone around him. He then evolved past the tie into a standard that fit the culture he was working in. The point was never the tie. The point was the intentionality behind it.

Jason also made a point that runs deeper than career strategy. When you get up in the morning and dress with intention, even on a day when you are working from home or heading to a routine site walk, it shapes how the rest of the day unfolds. Leaders who look the part tend to act the part. The morning routine of dressing intentionally is a signal to your own brain about what kind of day you are about to have. This is not motivational language. It is how habits and identity reinforce each other. The standard you hold for yourself in the mirror is the same standard that shows up when things get hard in the field.

Here is the top-to-bottom standard Jason described for showing up professionally in construction:

Hair: trimmed and well kept, whatever the length or style
Face: washed daily, facial hair trimmed and intentional, not neglected
Teeth: brushed without exception, basic hygiene is non-negotiable
Shirt: solid color, no logos or graphics, clean and wrinkle-free
Arms and hands: washed, fingernails clipped and clean
Belt: present and appropriate for the setting
Pants: no holes, no fading, no casual wear in professional settings
Shoes: clean and in good condition every day

This is not a high bar. It is a minimum standard. And meeting it consistently over time changes how others see you and how you see yourself.

Dress for the Position Above You

The practical principle Jason offered is simple: dress one level above where you currently are. If you are a foreman who wants to be a superintendent, dress like a superintendent before the promotion arrives. If you are a superintendent who wants to move into a director role, start closing that gap in your presentation now.

This is not dishonest. It is not pretending to be something you are not. It is signaling to the people around you and to yourself that you are serious about the next step. When a foreman shows up to an OAC meeting in a clean colored shirt and neat pants, the owner notices. The project manager notices. The general superintendent notices. And the next time there is a conversation about who is ready for a bigger role, that foreman has already answered the question before it was asked.

Jason also made a point about updating the wardrobe consistently over time rather than treating it as a one-time decision. He described reinventing his own professional appearance as he moved from field roles to speaking engagements and training, each time asking what the next level looked like and moving toward it deliberately. The wardrobe is not a destination. It is a practice.

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

The Challenge

Look in the mirror before your next workday and ask one question: does this person look ready for the role they want? If the answer is not a clear yes, make one change. Not everything at once. One change. A shirt without a logo. A pair of pants without holes. A trimmed beard. Clean shoes. Start there and build from it. Every upgrade is a signal to yourself and to everyone watching that the standard is moving in the right direction.

“Dress for the job you want, not the job you have.” Brian Tracy

On we go.

FAQ

Does appearance really affect career advancement in construction?

Yes, directly. Jason watched a seasoned general superintendent assess a foreman’s readiness for promotion based on how he dressed and groomed. Appearance communicates the standard a person holds themselves to across all areas of their work.

Does this mean I have to wear a tie or dress formally on a job site?

No. The standard is intentional, clean, and appropriate for the level you are working toward. A solid color shirt, clean pants, and well-kept grooming communicate professionalism without requiring formal attire.

What does dressing one level up actually look like in practice?

If you are a foreman, it looks like what a superintendent wears to a client meeting. Clean, solid-colored shirt, neat pants, groomed face and hair. It does not require expensive clothing. It requires intentionality and consistency.

Why does Jason say appearance reflects discipline in other areas?

Because how you handle the details you can control tells observers how you will handle the details of your work. Carelessness in appearance tends to show up in field notes, daily reports, and quality checks. Intentionality works the same way.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

The Builder ETHOS

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

Read 17 min

Are You a Guardian or Just Someone Running a Project?

In October 2011, an aid worker named Jessica Buchanan was captured by armed pirates in southern Somalia. For ninety-three days she was held in the open desert with no medicine, sleeping on mats while her husband and family waited in anguish for any word. The US government negotiated. The kidnappers refused every offer. And then Navy SEAL Team Six, the same unit that had killed Osama bin Laden months earlier, was dispatched. When those SEALs hit the ground that night, the outcome was already settled. That is what a guardian is. And Jason Schroeder believes construction leaders are called to the same identity.

The Story That Started It

Jason heard this story in a church talk and was moved enough to ask permission to share it publicly. He then went and read the full account, watched the interviews, and sat with what it meant. Jessica Buchanan recalled the moment she was rescued: she heard gunfire in the night and feared she was about to be taken by an even more dangerous group. Then someone pulled the blanket from her face and said her name. She had not heard her own name spoken in so long that the sound of it stopped her. He told her the American military was there. That she was safe. That they were taking her home.

One of the SEALs carried her across the desert. Another went back into what was effectively a war zone to retrieve a small bag she had asked for, a bag containing a ring her recently deceased mother had made. When the team suspected additional gunfire, they laid their own bodies on top of her, willing to absorb the impact so she would not. When the helicopter came and she was lifted in, she never learned their names. She never saw them again. They did not stay for recognition. The mission was the protection. Once she was safe, they were done.

That willingness to place another person’s survival above their own, not as an abstract value but as a physical, practiced, daily commitment, is what the SEAL ethos describes. And it is what Jason believed builders are also capable of becoming.

The SEAL Ethos and What It Demands

Jason read the SEAL ethos in this episode, and it is worth engaging with seriously. Not as borrowed military language but as a standard of professional identity that translates directly to construction leadership. The ethos calls for common citizens with uncommon desire. It calls for loyalty beyond reproach, for humility in service, for refusing to advertise or seek recognition. It calls for uncompromising integrity, for a word that is a bond, for leading by example in all situations.

It calls for never quitting. For getting back up every time. For drawing on every remaining ounce of strength to protect the team and accomplish the mission. For demanding discipline and innovation simultaneously. For training that is never complete. For attention to detail that keeps people alive.

Every one of those qualities has an exact counterpart on a construction project site. The superintendent who refuses to let a safety violation slide even when the schedule is tight. The foreman who checks in with a struggling worker rather than assuming they are fine. The project manager who goes back to the owner with honest data rather than the number they want to hear. The leader who is there when the crane is being set, when the concrete is being poured, when the crew is navigating something unfamiliar. These are not administrative acts. They are guardian acts.

The Builder Ethos

Jason wrote his own version of this ethos for construction leaders and shared it in this episode. It is worth carrying.

There have been builders of old who tamed the wild, forged raw materials into useful assemblies, and built some of the most awe-inspiring and near-impossible structures mankind can conceive. The builder protects the innocent: the workers, the neighbors, the pedestrians, the motorists, and anyone who comes in contact with the construction environment. The builder protects the families of all who work on the site. They are counting on the builder to send their loved ones home safely.

The builder’s projects are clean, safe, and organized in all circumstances. The builder does not push. The builder does not complete or order out-of-sequence work. The builder does not tolerate uncleanness, a lack of organization and discipline, or any compromise on safety. The builder respects people, and because of that respect, enforces the rules. Because of that respect, treats every worker with the same conditions and amenities the builder would want for their own family.

As soon as the builder sets foot on a project, winning is already the intention. And winning means on time, on budget, safely, with remarkable quality, where the team meets their career goals and develops, and where the owner becomes a raving fan. That is the minimum standard. Nothing less is tolerated.

Here are the questions Jason closed the episode with, worth sitting with as a personal audit:

Do you train like you are a guardian or do you coast on experience?
Are you pushing through adversity or looking for a reason to wait?
Do you consider your position a symbol of honor and heritage?
Are you loyal to your team when things get hard?
Do you serve the workers on your site the way you would want your own family served?
When you are knocked down, do you stay down or do you get back up?
Have you resolved not to fail?

These are not rhetorical questions. They are a professional self-assessment. The answers reveal the gap between where a leader currently operates and the standard the guardian identity demands.

Why This Matters in Construction

Jason connected the guardian identity to something he believes most people in the industry have not fully considered: the stakes are real. A worker who goes home at the end of the day goes home to a family. Children. A partner. People who need that person to show up tomorrow. Every decision a superintendent makes about safety, about sequencing, about how a crew is treated, about whether the site is clean and organized, carries those stakes in the background whether the leader acknowledges them or not.

The Navy SEALs in Somalia did not decide in the moment of the mission whether they cared about Jessica Buchanan. That decision was made in training, in the ethos they had committed to, in the identity they had built over years of preparation. The moment of crisis simply revealed what had already been built. Construction leaders face the same structure. The moment something goes wrong on a project reveals what has already been built in the leader’s character, standards, and habits. A project that is clean and organized before the crisis is a project that is managed through the crisis. A leader who has established trust before the storm is a leader the crew follows into it.

Jason was also direct about the legacy dimension of this. He came from a lineage of builders, German heritage known for precision, cleanliness, and regimented discipline. And he acknowledged that workers of every background carry their own legacies of craftsmanship, excellence, and hard work. Construction is not an accidental profession. For those who take it seriously, it is a calling. And people in a calling carry an identity that goes beyond a job title.

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

The Challenge

Read the Builder Ethos again. Not quickly. Read it the way you would read something you intend to live by. Then ask yourself honestly: which lines describe who you already are and which lines describe who you are still becoming? That gap is not a source of shame. It is a training plan. The guardians who rescued Jessica Buchanan did not become what they were overnight. They built it, day by day, through commitment to a standard that most people never hold themselves to.

You are a builder. You are a guardian. Start living like it.

“In times of war or uncertainty, there is a special breed of warrior ready to answer the nation’s call.” Navy SEAL Ethos

On we go.

FAQ

What is the Builder Ethos?

It is Jason’s adaptation of the SEAL ethos for construction leaders. It defines a builder as a guardian of workers, families, neighbors, and owners, committed to safety, respect, quality, and winning in the fullest sense of the word.

Why does Jason connect military identity to construction leadership?

Because both require the same core qualities: preparation before the crisis, commitment to the team, willingness to hold a standard under pressure, and a sense of identity that goes deeper than a job title.

What does winning mean in the Builder Ethos?

On time, on budget, safely, with remarkable quality, where the team develops professionally and the owner becomes a raving fan. That is the minimum standard, not the stretch goal.

How do I start living the guardian identity?

Answer the audit questions Jason posed honestly. Identify where your current standards fall short of the guardian standard. Then close that gap one habit, one decision, and one day at a time.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Coaching – Keep a To Do List – Implementation Series

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

Read 17 min

Are You Trying to Lead from Memory or from a System?

There is a person Jason Schroeder has watched for twenty-two years. Early in their career, a well-meaning area superintendent told them their to-do list was too long and suggested throwing it away. They listened. They made area superintendent. They have been stuck there ever since while their colleagues became project superintendents, general superintendents, and directors. The to-do list was not the only factor. But the habit that came with abandoning it, the habit of relying on memory, staying reactive, and never building a capture system, has been the invisible ceiling over everything they have tried to build since.

Your Mind Is for Having Ideas, Not Holding Them

Jason cited David Allen’s book Getting Things Done as the framework that best captures why a to-do list is not optional. The premise is simple and worth sitting with. Your brain is not a storage device. It is a processing device. Every time you try to remember something rather than writing it down, you are asking your brain to carry a load it was not designed to carry. Open loops, tasks not captured, ideas not recorded, things someone told you that you meant to act on, all of them cycle continuously through the mind and consume capacity that should be available for thinking, solving, and leading.

Jason described walking with project managers and superintendents and watching them nod while he assigns tasks without writing a single thing down. His reaction is not frustration. It is devastation. Because he knows what that moment means for the arc of that person’s career. If they will not write it down when a task arrives, they will not follow through reliably. If they will not follow through reliably, they cannot be trusted with greater responsibility. And if they cannot be trusted, they will not be promoted regardless of how smart or capable they actually are.

The to-do list is not about managing small tasks. It is about signaling to yourself and to everyone around you that you take your role seriously enough to track what it demands.

The System Behind the List

Jason walked through the four-phase capture system from Getting Things Done that makes a to-do list function as a genuine personal organization tool rather than a source of overwhelm.

The first phase is collection. Every idea, task, assignment, inspiration, and obligation gets captured the moment it arrives. In the shower. In the car. On a field walk. In a meeting. The moment it enters your awareness, it goes on the list. Not into your memory. Onto paper or into your digital capture system. The discipline here is non-negotiable because one uncaptured item is enough to send the loop cycling through your brain at the wrong moment.

The second phase is clarification. Once something is captured, you decide what it actually is. Is it something you need to do? Is it information to file? Is it something to delegate? Is it something to delete? Leaving captured items in an ambiguous state is how lists grow into sources of anxiety rather than sources of clarity.

The third phase is organization through triage. Jason returned to the Eisenhower matrix here, the same framework he has applied throughout his career. Urgent and important: do it. Important but not urgent: schedule it. Urgent but not important: delegate it. Neither urgent nor important: eliminate it. He was direct about the target: 20 to 40 percent of what goes onto a to-do list should be deleted. If everything feels important, the system is not working.

The fourth phase is engagement, meaning you check your list regularly and work from it deliberately. Jason described the vision of success for this practice: you should only know what you are supposed to do next by looking at your list. Not by trying to remember it. Not by waiting for something to feel urgent. By checking the system three times a day and trusting what it tells you.

Here are the three requirements Jason named for a to-do list system that actually works:

Every open loop must be in your capture system, no ideas or tasks left cycling in your mind
You must maintain as few capturing buckets as possible so nothing gets lost between systems
You must empty and process those buckets regularly so the list stays current and actionable

When all three conditions are met, something remarkable happens. The mind quiets. The background noise of what might be forgotten clears out. And in that quiet, solutions arrive. Ideas surface. The creative and strategic thinking that leadership actually requires becomes possible because the brain is no longer trying to double as a filing cabinet.

The Handwriting Standard

Jason made a point in this episode that will land hard for some people and needs to be heard. The quality of your handwriting is not a cosmetic issue. It is a professional signal. It reflects the standard you hold yourself to in every other area of your work.

He was blunt about it. If your handwriting is illegible, messy, or careless, you are communicating something to every person who reads it: that you do not take the detail seriously enough to do it well. In construction, where field notes, daily reports, drawing markups, and to-do items live on paper and in shared systems every day, that communication matters. Jason committed years ago to block lettering in capital letters and describes it as a practice that changed his relationship to precision across every other part of his work. How you do one thing is how you do everything. The handwriting is not a minor thing. It is a leading indicator.

For those working digitally, the standard is the same. Correct spelling. Proper capitalization. Complete sentences where they are needed. The phone is not an excuse for carelessness. The platform is different. The standard is the same.

Why This Comes Before Everything Else

Jason placed the to-do list and personal organization system early in this coaching and implementation series for a reason. Every other system he teaches, Takt planning, quality control, make-ready look-aheads, weekly work planning, roadblock removal, all of it requires a person who is organized enough to execute it consistently. A leader without a personal organization system cannot reliably follow through on project systems. The personal level has to be functioning before the professional level can perform.

Jason also connected this practice to something larger than professional performance. The leaders he most admires in this industry all share one trait: they are not running around reacting to whatever is loudest. They are working from a plan. They leave meetings on time. They return calls. They follow through on what they said they would do. They are home for dinner. That reliability is not an accident. It is the downstream effect of a personal organization system that has been maintained long enough to become automatic. The to-do list is where all of that starts.

This is also why the habit requires sixty days of disciplined practice before it becomes reliable. Not twenty-three days. Not four weeks. Sixty days of writing everything down, triaging consistently, checking the list three times daily, and clearing the capture buckets regularly. After sixty days, the system begins to run on its own and the mental quiet that comes with it becomes the new baseline.

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

The Challenge

Start today. Not next Monday. Not after the current push wraps up. Today. Write down every open loop currently cycling in your mind. Every task, every follow-up, every thing someone asked you to do, every idea you have been carrying. Get it all out. Then triage it. Delete what does not belong. Schedule what does. Delegate what someone else should handle. Work what only you can do. Then check that list three times tomorrow and the day after that. Sixty days from now, your mind will be quieter and your results will be louder.

“Your mind is for having ideas, not holding them.” David Allen

On we go.

FAQ

Why do social media influencers say to get rid of your to-do list?

It is a bait-and-switch. They create controversy to capture attention and then tell you the same thing Jason teaches: keep a to-do list, just do it the right way. Do not fall for it.

What is the Eisenhower matrix and how do I use it?

It sorts tasks into four categories: urgent and important, important but not urgent, urgent but not important, and neither. Do the first, schedule the second, delegate the third, and delete the fourth.

How long does it take to build the to-do list habit?

Jason says sixty days of consistent practice. Not twenty-three, not thirty. Sixty days of writing everything down, triaging daily, and checking the list three times a day before the system becomes reliable.

Why does handwriting quality matter for a construction professional?

Because it signals the standard you hold yourself to across all detail-oriented work. Careless handwriting communicates carelessness. Block lettering in capital letters is the professional standard Jason holds and teaches.

If you want to learn more we have:

Discover Jason’s Expertise:

On we go

Are You Dressing for the Role You Have or the Role You Want?

You Have to Campaign

The Foreman Story

How You Do One Thing Is How You Do Everything

Dress for the Position Above You

The Challenge

Are You a Guardian or Just Someone Running a Project?

The Story That Started It

The SEAL Ethos and What It Demands

The Builder Ethos

Why This Matters in Construction

The Challenge

Are You Trying to Lead from Memory or from a System?

Your Mind Is for Having Ideas, Not Holding Them

The System Behind the List

The Handwriting Standard

Why This Comes Before Everything Else

The Challenge

Subscribe Now !

Sign Up & Start Learning

The Foundation of Construction Excellence

© 2026 elevate construction ist LLC All Rights Reserved. |

SUBSCRIBE NOW !

Subscribe to our newsletters and stay updated!

Related Books

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

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

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

Related Books

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

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

Related Books

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

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

Calumet "K"

faq

General Training Overview

Superintendent / PM Boot Camp

Takt Production System® Virtual Training

Onsite Takt Simulation

Foreman & Field Engineer Training

Testimonials

Testimonials

agenda

Day 1

Foundations & Macro Planning

day2

Norm Planning & Flow Optimization

day3

Advanced Tools & Comparisons

day4

Buffers, Controls & Finalization

day5

Control Systems & Presentations

faq

UNDERSTANDING THE TRAINING

VALUE AND RESULTS

PLANNING AND SCHEDULING TOPICS

APPLICATION & TEAM ADOPTION

VIRTUAL FORMAT & ACCESSIBILITY

faq

GENERAL FAQS

CURRICULUM & OUTCOMES

LOGISTICS & FORMAT

PRICING & VALUE

SEO-BASED / HIGH-INTENT SEARCH QUESTIONS

agenda

Day 1

Agenda

Outcomes

Day 2

Agenda

Outcomes

Day 3

Agenda

Outcomes

Day 4

Agenda

Outcomes

Day 5