Are You Pushing Through or Creating Flow?

You’re pouring water from a bottle the normal way. Tipping it over letting gravity do the work. And it takes ten seconds because air keeps blocking the water creating starts and stops. Meanwhile, someone else swirls their bottle creating a vortex. The water flows in a common direction leaving room for air to rise. Five seconds. Half the time. Same amount of water. Different technique. One pushes through hitting roadblocks. The other creates stable flow allowing roadblocks to rise to the surface and clear. Your project is the first bottle. Pushing work through all at once. Plans change. Changes get pushed through. Every roadblock slows work creating variation. The concrete crew looks rushed and frustrated spending significant time moving around finding supplies. An uncoordinated frenzy. Three out of four porta-potties are disgusting with graffiti. Workers aren’t happy. The site isn’t clean enough. And cleanliness is always a key indicator of project success. You’re going too fast and the project isn’t stable. Dates shift week to week. Last Planner and Scrum are well organized but rendered inefficient by unstable master schedule. No team, no matter how proficient, can thrive when the target is always moving.

Here’s what most teams miss. The problem isn’t people. It’s flow. The team isn’t headed in the same direction. When you get the product heading in a stable direction and create space for roadblocks to rise to the surface, work proceeds unhindered. But that requires regulating the pace of the project, creating stability, and letting problems rise to the surface faster so you can remove them before they impact work. That’s what Takt does. It schedules right flow and pace into projects. Design, procurement, schedule, and start of work all get leveled and stabilized. Takt is the only way to do that. That’s why trades can’t commit and meet dates or even enjoy the system. The supply chain is not stable and you’re going too fast. You have pull planning and you know how to push. But you need to start first with flow. Your scheduling system is broken and needs immediate fix.

The challenge is most teams masterfully implement Last Planner and Scrum but wonder why they still struggle. Those systems need stable foundations. Predictable supply chains. When the master schedule constantly shifts, collaborative planning happens around moving targets. Teams plan well together but absence of resources always slows them down and interrupts their plans. No matter how well you do with Last Planner and Scrum, you will not succeed until you have predictable supply chain. All those systems need is Takt to succeed. Takt creates the rhythm. The vortex. The stable flow enabling roadblocks to rise to the surface early enough to remove them. Then Last Planner and Scrum work beautifully on top of that stable foundation.

What David Observed On Site

David arrives Monday morning trying to be objective. Brad is busy fighting fires, answering questions, solving problems. All predictable actions based on trouble the project is having. The project is well designed and fairly organized. About 120 people currently on site. At peak, 380 workers. David can see there’s care there but it won’t safely sustain the increase.

The site is a little cluttered and not clean enough. Cleanliness is always a key indicator of project success and a clear signal the project has fundamental issues. David inspects the porta-potties. Three out of four are disgusting messes with significant graffiti. Workers are not happy.

David watches the concrete crew putting in work. They seem rushed and frustrated. They spend significant time and effort moving around and finding supplies. It’s an uncoordinated frenzy to get things placed. The bottom line: they’re going too fast and the project isn’t especially stable.

After observing for a few days, it’s clear dates shift week to week. Implementation of Last Planner by interior and exterior teams and Scrum for medical equipment team is well organized. But they’re rendered inefficient with instability of the master schedule. No team, no matter how proficient, can thrive in an environment when the target is always moving. The project is simply moving too fast and is too chaotic.

David is hopeful that adjusted pace would stabilize the project and give the team and their lean systems a chance to be successful. Takt would be the best solution. However, implementing it mid-project would be hard on the on-site team. David is excited for the opportunity.

The Water Bottle Demonstration

David needs two volunteers and someone to keep time. Juan and Brad volunteer. Paul keeps time. David gives them each a 2-liter water bottle. The point: pour water into the bucket fastest without squeezing the bottle.

Brad goes first. Tips the bottle over with exaggerated flourish. Ten seconds. Juan swirls his bottle gently creating a vortex inside like a tornado. Five seconds. Half the time.

David asks: what happened? The air. It kept holding back the water and slowed it down. Exactly. Think of it like this:

• The air is like roadblocks.
• The water is the product.
• Roadblocks kept starting and stopping work because you were trying to push it through all at once.
• When you spin it creating a vortex, water leaves room for air to come up by heading in a common direction.
• When we get product heading in stable direction and create space for roadblocks to rise to the surface, work proceeds unhindered.

This applies to the project. The team is not headed in the same direction. Plans change. Those changes get pushed through. Then every roadblock slows down work and creates variation. You need to regulate the pace, create stability, and then problems will rise to the surface faster. You can remove them before they impact work. What you need is Takt.

Why Last Planner and Scrum Need Takt

You’ve masterfully implemented Last Planner and Scrum with your medical equipment teams. But those systems, and more importantly your team, cannot win this game when their goal changes every day. Design, procurement, the schedule, and the start of work all need to be leveled and stabilized. Takt is the only way to do that.

That’s why your trades can’t commit and meet dates or even enjoy the system. The supply chain is not stable and you’re going too fast. You have pull and you know how to push. But you need to start first with flow. Your scheduling system is broken and needs immediate fix.

CPM doesn’t really work. It pushes you in frenzied chaotic rush. If you still need to use CPM because it’s a requirement, at the very least align CPM with the Takt flow and rhythm. Create a master project Takt plan that shows when every Takt zone will be completed in a rhythm. This will unify everyone and get people working to the same rhythm. Workers, materials, information, and ultimately completion of design. If you can get everything working to the same beat, then all resources will be available for your Last Planner and Scrum systems.

All the day-to-day planning will be easy because those systems have predictable supply chains and the things they need. Right now you plan well together, but the absence of resources always slows you down and interrupts your plans. No matter how well you do with Last Planner and Scrum, you will not succeed until you have predictable supply chain. All those systems need is Takt to succeed.

Using Takt means you’ll have time to remove roadblocks in a system like this and enough time to finish as you go. Implementing it will not be easy and you’ll have to move now.

The Train Analogy: How Olivia Reframed Everything

Olivia was playing trains with her daughter that weekend. She started tipping over trees and putting things onto the track in her daughter’s way. Her daughter kept going through them. Do you know what she told Olivia? The cow catcher is the triangular attachment at the front of the engine used to clear the path, to clear the track.

Olivia makes the connection. David’s sequence looks a lot like a train. Another thing: trains start and stop on time when they arrive at the station in a certain rhythm. Could they use a train analogy instead of the river?

David loves it. Here’s how the train analogy works:

• Takt trains: Each process by zone (like 10,000 square foot areas).
• Takt freight cars or wagons: Scopes of work flowing through zones.
• Front engine: The preparation team making area ready.
• Cow catcher: The roadblock removal system clearing obstacles.
• Tracks: Operations, the foundation.
• Rails: Prefabrication (the thing that really makes Takt go fast).
• Leveling the track: Leveling trades and contracts (key to keeping good pace).
• Mountains: Constraints you have to work around.
• Speed of the train: Takt time.
• Arrival sequence of trains to the station: Throughput.
• Caboose: Finish as you go.

The key is to get each car going at the right speed on a level track headed toward the next station at a consistent rate. If you do that, it isn’t chaotic. If you keep the system moving just like a train yard, then all your short interval systems will work predictably.

What Complete Overhaul Looks Like

David suggests complete overhaul starting with respectful field conditions for workers, stabilizing all operations, and continuously improving. This includes meeting systems and operational tactics to really gain time in the field. Everyone would need to buy in and understand these.

Olivia isn’t overwhelmed by proposed changes. Instead, she’s grateful David has an actual plan to solve their problems. Everyone on the team is putting in massive amount of effort daily. Takt would give the team optimal output.

The plan:

• Create project Takt plan
• Discuss with One Care team
• Rally trades
• Issue zero dollar change orders
• Implement fast
• Ensure everyone’s heading in the same direction

The method:

• Improve worker conditions
• Stabilize all operations
• Measure continuous improvement

The System Failed You

Let’s be clear. When teams implement Last Planner and Scrum but still struggle, it’s not entirely their fault. The system failed by teaching collaborative planning without teaching stable master scheduling underneath. Nobody showed that Last Planner needs predictable supply chain. Nobody explained that you can’t plan well together when absence of resources always interrupts plans. Nobody demonstrated that Takt creates the rhythm and stability enabling collaboration to work. The system taught tools without teaching the foundation those tools need.

The system also failed by not teaching the water bottle principle. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. Pushing work through all at once creates starts and stops as roadblocks block flow. Creating a vortex allowing work to flow in stable direction with space for roadblocks to rise creates unhindered progress. But teams never taught this keep pushing wondering why it’s chaotic when the answer is they’re fighting flow instead of creating it.

The system fails by teaching CPM as standard. CPM pushes frenzied chaotic rush. It doesn’t create rhythm or stability. It doesn’t level the track. It doesn’t unify everyone working to the same beat. Even if required, it must be aligned with Takt flow and rhythm. But teams using CPM alone wonder why dates shift weekly and targets constantly move when the answer is CPM doesn’t create the stable foundation collaboration needs.

The Challenge

Here’s your assignment. Stop pushing work through all at once. Create stable flow allowing roadblocks to rise to the surface.

Use the water bottle principle. When you push through, air blocks water creating starts and stops. When you create vortex, water flows in stable direction leaving room for air to rise. Get product heading in stable direction with space for roadblocks to surface. Work proceeds unhindered.

Implement Takt creating master project plan showing when every zone completes in rhythm. Unify everyone working to the same beat. Workers, materials, information, design completion all to the same rhythm. This gives Last Planner and Scrum the predictable supply chain they need to work.

Use the train analogy. Takt trains flowing through zones. Preparation team as front engine. Cow catcher removing roadblocks. Level track through leveling trades and contracts. Right speed (Takt time) with consistent arrival sequence (throughput). Caboose finishing as you go. Keep system moving like train yard.

Implement complete overhaul: respectful field conditions for workers, stabilizing all operations, continuously improving. This isn’t just scheduling change. It’s fundamental transformation creating conditions for success.

Recognize when you’re going too fast and project isn’t stable. Dates shifting week to week. Workers rushed and frustrated. Site not clean. Porta-potties disgusting. Uncoordinated frenzy. These are signals you need adjusted pace creating stability so problems rise to surface early enough to remove them.

On we go.

FAQ

Why do Last Planner and Scrum struggle without Takt?

Those systems need predictable supply chains. When master schedule constantly shifts, teams plan well together but absence of resources always interrupts plans. No matter how well you do with collaborative planning, you won’t succeed until you have predictable supply chain. All those systems need is Takt creating rhythm and stability.

What does the water bottle demonstration teach?

Pushing water through all at once creates starts and stops as air blocks flow. Creating vortex allows water to flow in stable direction leaving room for air to rise. Air represents roadblocks. Water represents product. When product heads in stable direction with space for roadblocks to surface, work proceeds unhindered.

How does the train analogy work?

Takt trains flow through zones (like 10,000 square foot areas). Each scope of work is a freight car. Preparation team is front engine. Cow catcher removes roadblocks. Level track comes from leveling trades and contracts. Speed of train is Takt time. Arrival sequence is throughput. Caboose is finish as you go. System moves like train yard.

What are signs you’re going too fast without stability?

Dates shift week to week. Workers rushed and frustrated. Uncoordinated frenzy. Site not clean. Porta-potties disgusting. Concrete crew spending significant time moving around finding supplies. No team can thrive when target always moving. Plans change and changes get pushed through creating variation.

What does complete overhaul include?

Respectful field conditions for workers. Stabilizing all operations. Continuously improving. Meeting systems and operational tactics. Create project Takt plan. Rally trades. Implement fast. Ensure everyone heading in same direction. This gives team optimal output instead of massive effort with chaotic results.