Production Control – Part 4 – Roadblock Removal

Takt Control Part 4: Roadblock Removal and Why It Comes Before Everything Else

If the construction industry’s approach to lean were a child, it would be grounded until it got serious about roadblock removal. The industry loves percent plan complete. Leaders talk about it in weekly meetings, track it in reports, and use it to evaluate trade partner performance. But percent plan complete is a lagging indicator. It tells you what happened last week. Roadblock removal is the leading indicator that determines whether next week’s plan complete will be high or low. And yet most projects treat roadblock removal as something that happens reactively in meetings, when items happen to surface, rather than as a system that is built, maintained, and taken with the same seriousness that people apply to PPC. Part four of this series addresses that gap directly.

Why PPC Comes Second

Percent plan complete measures the percentage of tasks that were completed in the week they were committed to. It is a useful signal when it is used correctly, meaning when it triggers a root cause conversation about why tasks failed and what system change can prevent the same failure next week. But it cannot be the primary focus of a lean production system because it measures outcomes rather than causes. A project team that is fanatical about tracking PPC and casual about removing roadblocks is measuring the quality of their firefighting rather than preventing the fires.

Roadblock removal is what percent plan complete depends on. When roadblocks are cleared ahead of the work, the crew has what they need to execute, and PPC climbs naturally. When roadblocks are not cleared, PPC falls regardless of how carefully the weekly plan was built. The sequence is not optional: roadblock removal first, then plan complete as a check on whether the roadblock removal is working. Any project that has not built a reliable roadblock removal system has no business treating PPC as its primary production metric.

What the Takt Plan Does for Roadblock Visibility

One of the reasons Takt planning is superior to CPM as a production management tool is precisely what it does for roadblock visibility. The Takt plan is a visual, repeating, sequence-based schedule that everyone on the project can see and update regularly. When work happens on a consistent rhythm and is represented on a visual plan, deviations from that plan become visible almost immediately. A crew that is falling behind its expected cycle time can be seen on the board. A zone that is not finishing on time is visible to the foreman and superintendent before it becomes a handoff problem for the downstream trade.

Beyond visibility, the Takt plan allows the team to do three specific things with roadblocks. It allows them to see roadblocks earlier, because the repetitive nature of the work and the visual representation of the schedule make deviations obvious. It allows them to remove roadblocks more effectively, because the team is farther ahead of the work and has more time to act before the roadblock reaches the crew. And it allows them to absorb roadblocks when they cannot be fully removed, because the buffer system built into a Takt plan can be used to shift the schedule by a day or two without collapsing the production rhythm. CPM does not have any of those properties. It is not agile. It does not absorb variation. It does not make deviations visible in real time. Takt planning does all three.

The Six Elements of an Effective Roadblock Removal System

A roadblock removal system is not a meeting. It is a structured, visual, actively managed set of practices that work together to identify, track, and eliminate the things that will stop the crew from executing. Six elements make that system function.

Using Buffers Intentionally

Buffers in a Takt plan are not idle time. They are the system’s response capacity. When a roadblock hits, the buffer is what allows the production rhythm to absorb the hit without cascading into the next wagon, the next zone, or the next trade. But buffers only work if they are preserved rather than consumed. When the team uses buffer time to stage materials, prepare the next area, and close out inspections in the current one, the buffer remains available when an actual disruption occurs. When the buffer is consumed by pushing work forward prematurely, the production system has no response capacity when variation hits, and every roadblock becomes a crisis rather than an absorbed interruption.

A well-managed Takt plan maintains the buffer as a real and tracked quantity. The superintendent knows how many buffer days remain at any point in the project. When buffers are consumed by delays, the implications are visible and the team can decide whether to protect the end date by recovering through leveling, or to accept an extended duration with appropriate financial analysis.

Seeing Deviations Through a Live Visual System

The Takt plan is only as useful as the regularity with which it is updated and reviewed. A plan that was current two weeks ago and has not been touched since is not a production management tool. It is a historical record. For the Takt plan to function as a roadblock detection system, it needs to be updated daily and reviewed in every production meeting. When the plan is live and current, deviations become visible immediately: a crew that is one day behind shows up on the board before the problem compounds. A zone that is not going to be ready for the incoming trade appears in the lookahead before the handoff fails.

The superintendent and foreman’s daily field walk, done with the Takt plan or roadblock map in hand, is the primary mechanism for keeping the visual system current. What they see in the field needs to get onto the plan, and what the plan shows needs to inform what they look for in the field. That loop between the visual system and the daily walk is where deviation detection actually happens.

Make-Ready Look-Ahead Conversations

The six-week make-ready look-ahead is the production system’s early warning mechanism. In the window between six weeks out and the current week, every item that needs to be ready before the crew begins its work, materials, equipment, approvals, coordination, inspections, information, should be identified, assigned an owner, and actively tracked toward resolution. When the make-ready conversation happens well, roadblocks that would have stopped the crew in week one are visible in week four and get cleared before they matter.

What makes make-ready conversations effective is not just asking whether items are ready but helping the trade partner visualize what the area will need to look like and what inputs will have to be in place for the work to start cleanly. That deeper conversation surfaces assumptions and dependencies that a simple status check misses. It transforms the look-ahead from a reporting exercise into a genuine preparation system.

These Signs Mean Your Look-Ahead Is Not Working

If the make-ready system is functioning in name but not in practice, these signals will appear in the field:

• Crews discover missing materials or missing approvals on day one of a new Takt cycle
• Coordination conflicts between trades surface during execution rather than during the look-ahead window
• Inspections that should have been scheduled three weeks out are being scheduled the week of the work
• Trade partners are consistently surprised by what is expected of them in the coming cycle
• The six-week look-ahead is reviewed in meetings but items rarely have defined owners or resolution dates

Any of those signals means the make-ready system is collecting information but not driving action. The fix is not a better template. It is a culture where open items get owners, due dates, and daily accountability until they are closed.

Roadblock Maps as Visual Production Intelligence

Roadblock maps are one of the most powerful and underused tools in lean construction. In Bluebeam, each room and area on the project floors can be represented as a polygon with a status that matches the Takt wagon colors in the Takt plan. When a zone is progressing on schedule, the polygon reflects the wagon color. When a roadblock is present, red text on the polygon identifies the specific issue. When an area has been detached from the normal sequence because of an owner change or a scope adjustment, the map shows that disconnection visually.

The result is a floor-by-floor picture of the production system’s health that anyone can read in thirty seconds. In every planning meeting, walking through the roadblock maps reveals where the production is flowing, where it is stuck, and where the sequence has been disrupted. That visibility drives the right conversations: not what did we accomplish last week, but what is blocking the next three weeks and who is going to clear it.

Actually Removing Roadblocks

Visibility is necessary but not sufficient. The roadblock list is only valuable if the people with authority and accountability to clear items are acting on it with genuine urgency every day. Jason Schroeder describes the standard he holds for this: the project superintendent, project manager, and project executive should approach the roadblock board the way someone approaches something they cannot stop thinking about. Not checking it occasionally. Not reviewing it in the weekly meeting. Being drawn to it first thing each day, leaning in, and doing whatever it takes to clear the items on it before they reach the crew.

That level of engagement is not achievable through policy or expectation alone. It requires leaders who genuinely understand that the crew’s production depends on what the leaders clear ahead of them, and who have built the habit of acting on that understanding daily. The meeting system creates the opportunity to surface and assign roadblocks. The leader’s daily discipline is what ensures those assignments turn into cleared paths.

Managing Buffers as a Tracked Resource

The final element is treating the project’s buffer as a tracked resource rather than an assumed cushion. How many buffer days remain in the current phase? At the current rate of consumption, is the end buffer likely to be positive or negative? What are the identified risks in the coming six weeks, and is there enough buffer in the system to absorb them without impacting the contract date?

These questions should be answered from real data, not intuition. When buffer management is treated with the same rigor as cost management, the project team has genuine predictability rather than a hope that things will work out. Roadblock removal protects the buffer. Buffer management tracks whether the protection is working.

Built for Projects That Finish as Promised

A Takt plan without a roadblock removal system is a schedule that will be undone by the first serious interruption. A project with a functioning roadblock removal system is a project that absorbs interruptions, maintains its rhythm, and finishes when and how it promised. The six elements in this episode are what that system requires: intentional buffers, live deviation detection, deep make-ready conversations, visual roadblock maps, leaders addicted to clearing the way, and buffer management as a tracked production metric. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Remove What Is in the Way, Then Watch the Production Flow

Roadblock removal is not a meeting agenda item. It is the daily discipline of the field leadership team, sustained from the first day of the project to the last. When it works, crews arrive at their zones to find everything they need in place. Handoffs happen cleanly. PPC climbs without anyone having to chase it. The Takt rhythm holds. And the project finishes. As Jason Schroeder puts it directly: Takt planning does not work unless you have a remarkable roadblock removal system. Build that system first. Everything else follows from it.

On we go.

FAQ

Why should roadblock removal come before percent plan complete as a focus?

Because roadblock removal is a leading indicator and percent plan complete is a lagging one. PPC tells you how many tasks were completed last week. Roadblock removal determines whether next week’s tasks will be executable. A project team that tracks PPC without a functional roadblock removal system is measuring the quality of its reactions to problems that a better system would have prevented. The sequence is: build a roadblock removal system, use it consistently, and then measure PPC as a check on whether the roadblock removal is working.

What does it mean that the Takt plan allows you to see, remove, and absorb roadblocks?

The Takt plan creates visibility because it is a live, visual, repeating schedule that makes deviations from the expected rhythm apparent in real time. It creates roadblock removal capacity because the team is farther ahead of the work than in a CPM environment and has more time to act before a roadblock reaches the crew. And it creates absorption capacity through its buffer system, which allows the schedule to shift by a day or two when an interruption occurs without collapsing the production rhythm. CPM does not have any of those properties. It is not a visual system, it does not provide the lead time for proactive removal, and it has no agile response mechanism for absorbing variation.

What are roadblock maps and how do they work in practice?

Roadblock maps are visual representations of the project’s floors, typically built in Bluebeam, where each room or area is shown as a polygon with a color status that matches the Takt wagon it belongs to in the Takt plan. When a zone is progressing on schedule, it displays the appropriate wagon color. When a roadblock is present, red text on the polygon identifies the specific issue. When an area has been detached from the normal sequence because of an owner change or scope adjustment, the map shows that disconnection. Walking through the roadblock maps in every planning meeting gives the team a floor-by-floor picture of where the production is flowing, where it is stuck, and where the sequence has been disrupted.

What makes a make-ready look-ahead system effective rather than just a reporting exercise?

The difference is whether open items have owners, due dates, and daily accountability. A make-ready system that collects information but does not drive action is an expensive status meeting. An effective make-ready system treats every open item as a production threat that needs to be resolved before it reaches the crew, assigns it to a specific person, sets a specific resolution date, and tracks it daily until it is closed. Beyond the mechanics, effective make-ready conversations help trade partners visualize what the area will need to look like and what inputs will have to be in place, rather than just asking whether items are ready. That deeper conversation surfaces assumptions and dependencies that a status check misses.

How should buffers be managed in a Takt system?

As a tracked production resource, not an assumed cushion. The superintendent should know at any point in the project how many buffer days remain in the current phase, at what rate buffers are being consumed, and whether the remaining buffers are sufficient to absorb the identified risks in the coming weeks. That analysis should be updated regularly and reviewed in the strategic planning meeting. When buffers are being consumed faster than the risk profile justifies, the team needs to accelerate roadblock removal, adjust the production strategy, or have an honest conversation about the end date. Buffer management is what converts a Takt plan from an optimistic schedule into a realistic production forecast.