Brainstorming the Entire System

Are You Looking at All Parts of the System? The Friction Problem Nobody Is Solving

Here is a question worth sitting with before you read any further: when was the last time a training effort, a new system, or an improvement initiative on your project did not stick? Not because people were unwilling. Not because the concept was wrong. But because something in the surrounding environment made it harder than it needed to be, and eventually the effort ran out before the friction did. That is not a discipline problem. That is a system design problem. And it is one of the most consistent reasons that good ideas fail to produce lasting change in construction.

The Plan That Makes Perfect Sense and Still Does Not Work

Most improvement efforts in construction start with a reasonable goal and a logical plan. Implement Takt planning on the next project. Run weekly foreman huddles consistently. Get the site clean and keep it that way. Train the team on the new scheduling software. These are not bad ideas. The people who bring them to the table are not wrong about what is needed. What they are missing, almost every time, is an honest assessment of the friction that will resist the effort from the moment it starts. The goal is clear. The path to the goal is assumed to be straightforward. The friction in between is invisible until it stops the progress cold.

The Pattern That Keeps Repeating

The failure pattern is predictable. A leader commits to a change. They communicate it to the team. The first week goes reasonably well because novelty creates momentum. By week three, the surrounding conditions are working against the effort. The healthy food that was supposed to be in the kitchen was never ordered because nobody assigned that task to a specific person. The treadmill is in the garage with boxes stacked on it because nobody cleared the path. The foreman huddle keeps getting cut short because there is no defined location, no standard agenda, and no system to make it easy to run at the same time every morning. The new software is installed but nobody is using it because the training was a one-time event and the old spreadsheet is still sitting on the shared drive. The initiative fades. The leader tries something else. The cycle repeats.

This Is Not a Willpower Problem

It needs to be said plainly because the alternative explanation is damaging: when improvement efforts fail, the most common conclusion drawn is that the team lacked commitment or the leader lacked follow-through. That framing is wrong, and it is harmful. Self-control and willpower are exhaustible resources. When the environment surrounding a new behavior requires constant willpower to sustain, the behavior will eventually stop. Not because the person gave up. Because no system was ever designed to support what they were trying to do. The system failed them; they did not fail the system. The job of the leader is not to find more committed people. It is to design an environment where doing the right thing is the path of least resistance.

A Quick Stop by the Road That Said Everything

Jason Schroeder recorded this episode by the side of the road while waiting for a ride, fresh off a leadership session with a company where these exact ideas had been alive in the room. The weight loss analogy came to him directly from that conversation and from the one he had with Kevin Rice in the previous episode about the aggregation of marginal gains.

The scenario is simple. Someone wants to lose ten pounds. What does the advice sound like? Exercise. Eat healthy. Get enough sleep. Make a plan with real targets. Get an accountability partner. Five domains, all pointing at one goal. And here is what that conversation almost never includes: what does it take to reduce the friction in each of those five areas so that actually doing them becomes possible?

Eating healthy does not happen because someone decided to eat better. It happens when the kitchen has the right food already in it, when the menu is planned in advance, when the preparation is fast and the result tastes good enough that willpower does not have to carry the whole load. Exercise does not happen because someone wants to be in shape. It happens when the treadmill is in a useful location, when the schedule has a protected window for it, and when it is tied to something already chemically rewarding, like watching a show with a spouse. The accountability partner does not work because someone chose one. It works when the system between them is defined: what gets sent, how often, in what format, and what happens when the plan goes off track. Each domain has its own friction. Each friction point is a place where the effort can fail without anyone intending it to.

Why Friction Is a Production Problem

In construction, friction is not a personal inconvenience. It is a production cost. Every step that is harder than it needs to be consumes time, energy, and attention that could be going into value-adding work. A crew that has to search for materials before they can install is losing production time to a friction problem that should have been solved by a material staging system. A foreman who has to recreate the weekly work plan from scratch every Monday because there is no template is spending cognitive energy on administration that should be going into leading the crew. A superintendent who cannot pull up the schedule on a tablet in the field because the software was never properly configured is making decisions without the information they need because nobody reduced the friction in the technology adoption.

This is why 5S is not a housekeeping program. It is a friction reduction system. Sort means removing the things that create unnecessary decisions and obstacles. Set in Order means that every tool, material, and piece of information has a defined location that is easy to access. Shine means the environment is clean enough that problems are visible and nothing extra has to be worked around. Standardize means the team agrees on the friction-free method and uses it consistently. Sustain means the leader protects those friction-free conditions through reinforcement and regular audit. The goal of 5S is not a tidy jobsite. The goal is an environment where the right behavior is easy and the wrong behavior is obvious.

Look at the Whole System Before You Start

Here is the discipline that separates improvement efforts that stick from the ones that fade: before implementing anything, map every domain that the goal depends on, identify the friction in each domain, and reduce that friction before asking people to push through it with willpower.

Implementing a new scheduling tool requires more than a training session. It requires removing the old tool from the workflow, assigning someone to configure the new one properly, establishing a daily habit loop that makes opening it the default behavior, and building a support system for the people who will struggle with it in the first few weeks. Implementing a foreman huddle system requires a defined location, a standard agenda, a time that is protected from competing demands, and a clear expectation about what happens when the huddle gets skipped. Implementing Takt on a project requires preconstruction work, procurement alignment, zone definition, make-ready systems, and a steering meeting structure, all reduced to the point where running them is not a heroic effort but a routine one.

Before You Launch the Next Initiative, Answer These:

• Have you identified every domain that contributes to the goal you are trying to achieve?
• Have you looked honestly at the friction in each domain and addressed it before asking the team to push through it?
• Is there a plan with real targets, and is that plan embedded in a system with reminders and checkpoints rather than relying on memory?
• Does the accountability structure have a defined method: what gets reported, to whom, how often, and what triggers a course correction?
• Have you removed the old system, the old spreadsheet, the old habit, so the new one does not have to compete with it?
• Can the right behavior be done consistently without extraordinary willpower, or does it still depend on heroic effort every time?

Built for People Who Actually Have to Execute

This matters because the people in construction who are trying to implement better systems are real people with full days, competing demands, and limited bandwidth. They do not fail because they lack commitment. They fail because the systems designed to support their goals were never friction-proofed. The leader who understands this does not push harder when something is not working. They ask what is making it hard, remove that obstacle, and then ask again. That is make-ready discipline applied not just to the production plan but to every improvement effort the team is asked to carry. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Design for the Realistic Human, Not the Ideal One

The closing question from this episode is the right one to sit with: are you looking at all parts of the system? Not just the goal, not just the primary method, but every domain the goal depends on and every friction point within each of those domains. Design the environment for the realistic version of the people who have to use it, not the ideal version who never gets tired, never forgets, and never needs the path to be cleared for them. As W. Edwards Deming observed, a bad system will beat a good person every time. Design a good system and the good person inside every member of your team has a real chance.

On we go.

FAQ

Why do improvement initiatives in construction fail even when the goal is clear?

Because a clear goal does not automatically produce a clear path. Every goal depends on multiple domains working together, and each domain has its own friction that resists the effort. An initiative to run consistent foreman huddles fails not because the superintendent does not care about huddles, but because there is no defined location, no standard agenda, and no protected time slot. The friction in the surrounding environment eventually defeats the willpower required to push through it every day. The solution is not more commitment. It is friction reduction in every domain the goal depends on before asking people to sustain the effort.

What does reducing friction mean in practice on a construction project?

It means removing every unnecessary obstacle between the right behavior and the person being asked to do it. For material management, it means staging materials at point of use so crews do not search before they can install. For training, it means building the habit into the existing workflow rather than adding it as a separate event. For scheduling software adoption, it means removing the old tool from the shared drive so the new one does not have to compete with it. For daily inspections, it means having the checklist on the tablet already open rather than requiring someone to navigate to it each time. Every friction point addressed is one less reason for the improvement effort to stall.

How does this connect to the 5S lean framework?

5S is fundamentally a friction reduction system. Sort removes everything that creates unnecessary decisions and obstacles. Set in Order creates defined locations that make finding the right tool or information immediate rather than effortful. Shine creates visibility so that deviations from the standard are obvious rather than hidden in clutter. Standardize locks in the friction-free method so it does not have to be reinvented each time. Sustain protects those conditions through leadership reinforcement. The end result of a functioning 5S system is an environment where the right behavior is the easy behavior, which is the exact goal of friction reduction in any domain.

How do you identify all the domains a goal depends on before launching an initiative?

Start by naming the goal clearly and then asking: what has to be true for this to work? Work through the answer systematically. If the goal is consistent foreman huddles, the domains include location, timing, agenda, attendance accountability, and integration with the weekly work plan. If the goal is better field quality, the domains include standard work at the point of installation, foreman training protocols, inspection checkpoints, rework tracking, and root cause response. Map every domain, then walk through each one asking where the friction is. That process will surface the real obstacles before the initiative launches rather than after it stalls.

What is the relationship between accountability partners and system design?

An accountability partner is only as effective as the system built around them. Two people agreeing to hold each other accountable without defining how that accountability works, what gets reported, on what schedule, in what format, and what happens when something goes off track, is not a system. It is an intention. The friction is in the undefined method. Once the system is designed, the accountability partner becomes a genuine lever because both people know exactly what they are tracking, when to check in, and what a successful week looks like. The same principle applies to project teams: accountability is not a cultural stance. It is a designed mechanism with clear inputs and clear responses when the plan deviates.