The Takt Production System – Part 16

Read 14 min

Are You Following the 25 Steps or Guessing Your Way Through?

You want to create a Takt plan. But you don’t know where to start. So you guess. Open Excel. Draw some boxes. Color code phases. Call it Takt. And wonder why it doesn’t work. Here’s the problem: creating a Takt plan is not guessing. It’s a systematic process with 25 specific steps. Identify start and end date. Research drawings. Identify general flow based on known constraints. Identify preliminary Takt zones. Identify preliminary Takt time. Pull plan typical sequence to start. Create Takt sequence. Create Takt phase. Identify logistics flow. Optimize throughput with Little’s Law. Network phases together. Develop work steps. Trigger planning buffers in system. Add buffers. Create standard work. Identify bottlenecks. Verify with trade partners. Create logistics plans and drawings. Create Takt zone maps. Perform risk analysis. Create basis of schedule. Align procurement. Review in Fresh Eyes meetings. Create roadblock tracking maps. Track historical production. Add Takt point of no return. Twenty-five steps. Not guessing. Following systematic process building from macro level process analysis through norm level harmonization to micro level implementation. Each level has specific deliverables. Each step builds on previous steps. Skip steps and system fails. Follow all 25 and system works.

Here’s what most teams miss. They think Takt is visual schedule with colored boxes. So they create visual schedule with colored boxes and call it Takt. But that’s not Takt. That’s colored boxes. Takt has three levels of development. Macro level creates overall Takt plan identifying preliminary zones, preliminary time, preliminary sequences, Takt phases, logistical flow, optimized throughput, networked phases, critical milestones. Norm level harmonizes the plan with general leveling of resources, integrated buffers, refined work packages, identified standard space units, created and documented work steps, workable backlogs. Micro level makes work ready with detailed work packages, quality deliverables, standard work, Takt control meetings, Takt status meetings, Takt status board, continuous improvement cycle. Three levels. Not one. All three required. Skip norm level and you have zones and time without work steps making work ready. Skip micro level and you have plan without control system executing it. All three levels required for system to work.

The challenge is most teams want shortcut. They see Takt plan looking simple. Visual. One page. Color coded. So they think creating it is simple. Just draw boxes and fill in trades. But that simplicity is result of systematic 25-step process building through three levels of development. The one-page plan you see is iceberg tip. Below surface is macro level process analysis vetting overall duration from consideration of flow. Norm level harmonization leveling resources and creating work steps. Micro level implementation detailing work packages and establishing control meetings. Without systematic process building these levels, the one-page plan is just colored boxes without substance. Follow 25 steps through three levels or you’re guessing not planning.

The 25-Step Process of Creating a Takt Plan

One of the best ways to get into this system is to create your first Takt plan. Here is the process:

  • Identify your start and end date.
  • Research your drawings.
  • Identify the general flow of the project based on known constraints.
  • Identify preliminary Takt zones.
  • Identify preliminary Takt time.
  • Pull plan a typical sequence to start.
  • Create the Takt sequence.
  • Create the Takt phase.
  • Identify logistics flow.
  • Optimize the throughput with Little’s Law.
  • Network phases together.
  • Develop work steps.
  • Trigger planning buffers in the system.
  • Add buffers.
  • Create standard work.
  • Identify bottlenecks.
  • Verify with trade partners.
  • Create logistics plans and drawings.
  • Create Takt zone maps.
  • Perform a risk analysis.
  • Create a basis of schedule.
  • Align procurement.
  • Review in the Fresh Eyes meetings.
  • Create roadblock tracking maps.
  • Track historical production.
  • Add a Takt point of no return.

The Three Levels of Takt Plan Development

There are three levels of Takt plan development:

Macro Level: The Process Analysis

In the macro level, the overall Takt plan is created and the following steps are completed:

  • Preliminary Takt zones are identified.
  • A preliminary Takt time is identified.
  • Preliminary Takt sequences are created by phase.
  • Takt phases are created.
  • A logistical flow is identified as compared to constraints.
  • The throughput time is generally optimized.
  • Takt phases are networked together with interdependence ties.
  • Critical milestones are identified.

The goal for this level is to vet out an overall duration from a consideration of flow.

Norm Level: Takt Planning Harmonization

In the norm level, the Takt plan harmonization takes place. This means the following:

  • General leveling of resources occurs.
  • Buffers are integrated.
  • Work packages are refined.
  • Standard space units are identified and used in leveling between Takt zones.
  • Work steps are created for each work package, documented and leveled.
  • Workable backlogs are created for the Takt plan.

Micro Level: Implementation

This level of Takt planning is crucial to the system and cannot be omitted. In this step, the following steps occur:

  • Detailing of work packages occurs to make work ready.
  • Quality deliverables and standard work is created for work steps.
  • Takt control meetings begin and Takt status meetings begin.
  • The Takt status board is used for the daily Takt status meeting.
  • The continuous improvement cycle begins with the system.

Three Ways to Look at Takt Planning and Takt Control

There are three ways to look at Takt planning and Takt control:

Takt Planning and Takt Control (Preferred Method)

This is a total Takt management system. It entails the full use of the Takt plan, work steps and the Takt status boards. The entire project system is controlled by these three deliverables. This is the preferred method because this means you have achieved flow in all directions: workflow, logistical flow and process or trade flow.

Takt Planning and Integrated Control

This is a cross between Takt and currently short interval scheduling systems, but Takt drives all of them from the start in a one process flow using it to drive the Last Planner System from milestones and direct the Scrum sprints and control in other areas. Weekly work plans under the Last Planner or sprints under Scrum can be made from the standard work steps prepared by the Takt system in this approach.

Takt Phase Planning and Divided Control (Not Recommended)

This is a method where certain phases of the project are controlled by the Takt plan and Takt control and others may be controlled using Last Planner or Scrum entirely or as paired with CPM. This is not recommended but sometimes happens, especially when project teams are new to Takt and are in the experimentation phase with Takt planning. This causes the most amount of duplicate work and is not recommended as an overall system to any organization other than a stepping stone.

Software Options for Takt Planning

Takt planning is done well in Excel but can only reach its potential from an optimization standpoint in an application like Tacking or Timoti.

Excel

Excel will always be a very viable solution for Takt planning. It is easy to manipulate and use and it formats nicely. We typically recommend someone getting familiar with Takt using Excel because there is less friction with this approach.

Tacking

In our opinion, Tacking is a Takt time and production-based application based primarily around Takt time. When an approach is based on Takt time, the science and formulas are enabled in the system and calculations can be made to improve production. You will not go wrong using this application because it will force you to plan the proper way. Also, it forces the use of work packages and work steps. We highly recommend this application. This application is free.

Timoti

Timoti again in our opinion is a resource-based application that focuses less on Takt time, work packages, and work steps and more on resource constraints and how they play into the system. Timoti replicates the exact way we use Takt planning in North America and we recommend it to anyone wanting a system that more fully integrates with Last Planner and more metrics for overall scheduling reporting. This system has an affordable pricing model that is by project.

Others

There are other applications that support Takt planning but they are in development. It will be exciting to see them develop to their full potential. One caution though: Takt planning must meet the definition requirements, have the three critical components of rhythm, continuity, and consistency as well as follow the production laws. Be skeptical of any application that does not do this.

Last Planner-Based Applications

There are many LPS applications that are making room for Takt in their application but we would caution you not to lose the full effect of Takt by trying to adapt it to the application. Some are attempting to tack it on the end as a selling feature. Applications should adapt to the theory and concept of Takt planning first to be effective.

Best Practice for Creating Your First Takt Plan

One of the wonderful aspects of Takt is that it does not take a fancy software application to create one. You can use Excel or other free applications to automate the creation of Takt plans.

We still, as of mid-2021, find it a best practice to create your initial Takt plan in an Excel format. Adjust it through design and then transfer it into another application if desired during construction for management and control.

We would caution you to use only reliable, thoroughly tested technology that serves your people and process as explained in the 14 Principles of the Toyota Way. Excel is not only easy and thoroughly tested. Everyone can use it or already has access to it.

Before you sign up with an enterprise technology solution, be sure it does not slow you down by limiting access, visibility, and flexibility. That is why we recommend Tacking and Timoti in this book. They are thoroughly tested and adaptable.

The System Failed You

Let’s be clear. When teams create colored boxes and call it Takt, it’s not entirely their fault. The system failed by not teaching the 25-step systematic process. Nobody showed that creating Takt plan requires identifying start and end date, researching drawings, identifying flow, identifying zones, identifying time, pull planning sequence, creating sequence, creating phase, identifying logistics flow, optimizing throughput with Little’s Law, networking phases, developing work steps, triggering planning buffers, adding buffers, creating standard work, identifying bottlenecks, verifying with trade partners, creating logistics plans, creating zone maps, performing risk analysis, creating basis of schedule, aligning procurement, reviewing in Fresh Eyes meetings, creating roadblock tracking maps, tracking historical production, adding point of no return. Twenty-five steps. The system taught just draw boxes when actually systematic process creates functional plan.

The system also failed by not teaching the three levels of development. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. Macro level vets overall duration from consideration of flow identifying preliminary zones, time, sequences, phases, logistical flow, optimized throughput, networked phases, critical milestones. Norm level harmonizes plan with general leveling of resources, integrated buffers, refined work packages, identified standard space units, created work steps, workable backlogs. Micro level implements system detailing work packages to make ready, creating quality deliverables and standard work, beginning Takt control meetings and status meetings, using status board, starting continuous improvement cycle. All three levels required. The system taught Takt is one-page plan when actually one-page plan is result of three levels of systematic development.

The system fails by not teaching that applications should adapt to theory, not theory adapt to applications. Some Last Planner applications attempting to tack Takt on end as selling feature. But applications should adapt to theory and concept of Takt planning first to be effective. Must meet definition requirements, have three critical components of rhythm, continuity, and consistency, follow production laws. The system taught use whatever application when actually application must serve the theory not distort it.

The Challenge

Here’s your assignment. Stop guessing. Start following the systematic 25-step process through three levels of development.

Follow the 25 steps. Identify start and end date. Research drawings. Identify general flow based on known constraints. Identify preliminary Takt zones. Identify preliminary Takt time. Pull plan typical sequence. Create Takt sequence. Create Takt phase. Identify logistics flow. Optimize throughput with Little’s Law. Network phases together. Develop work steps. Continue through all 25 steps. Each step builds on previous steps. Skip steps and system fails.

Build through three levels of development. Macro level: vet overall duration from consideration of flow. Norm level: harmonize plan with leveling, buffers, work packages, work steps. Micro level: make work ready with detailed work packages, quality deliverables, standard work, control meetings, status meetings, status board, continuous improvement cycle. All three required.

Choose the right approach. Preferred: Takt planning and Takt control achieving flow in all directions using Takt plan, work steps, Takt status boards controlling entire project system. Alternative: Takt planning and integrated control driving Last Planner from milestones and directing Scrum sprints. Not recommended: divided control causing most duplicate work, stepping stone only.

Use reliable, thoroughly tested technology. Best practice: create initial Takt plan in Excel, adjust through design, transfer to application during construction if desired. Excel is easy, thoroughly tested, everyone can use it. Before signing up with enterprise solution, be sure it doesn’t slow you down by limiting access, visibility, flexibility. Tacking and Timoti are thoroughly tested and adaptable.

Ensure application serves theory. Takt planning must meet definition requirements, have three critical components (rhythm, continuity, consistency), follow production laws. Be skeptical of any application not doing this. Applications should adapt to theory and concept of Takt planning first, not tack it on end as selling feature.

The one-page Takt plan you see is iceberg tip. Below surface is systematic 25-step process building through three levels of development. Follow the process or you’re creating colored boxes, not Takt.

On we go.

FAQ

What are the 25 steps for creating a Takt plan?

Identify start/end date, research drawings, identify flow, identify preliminary zones, identify preliminary time, pull plan sequence, create sequence, create phase, identify logistics flow, optimize throughput with Little’s Law, network phases, develop work steps, trigger planning buffers, add buffers, create standard work, identify bottlenecks, verify with trade partners, create logistics plans, create zone maps, perform risk analysis, create basis of schedule, align procurement, review in Fresh Eyes meetings, create roadblock tracking maps, track historical production, add point of no return.

What are the three levels of Takt plan development?

Macro level (process analysis): vet overall duration from flow identifying preliminary zones, time, sequences, phases, logistical flow, optimized throughput, networked phases, critical milestones. Norm level (harmonization): level resources, integrate buffers, refine work packages, identify standard space units, create work steps, create backlogs. Micro level (implementation): detail work packages to make ready, create quality deliverables and standard work, begin control and status meetings, use status board, start continuous improvement.

What’s the difference between the three ways to look at Takt planning and control?

Takt planning and Takt control (preferred): total management system using Takt plan, work steps, status boards controlling entire project achieving flow in all directions. Takt planning and integrated control: Takt drives Last Planner from milestones and directs Scrum sprints. Takt phase planning and divided control (not recommended): certain phases controlled by Takt, others by Last Planner/Scrum, causes most duplicate work.

What software should I use for Takt planning?

Best practice: create initial plan in Excel (easy, thoroughly tested, everyone can use it), adjust through design, transfer to application during construction if desired. Tacking: Takt time and production-based, free, forces proper planning and work packages/steps. Timoti: resource-based, integrates with Last Planner, affordable pricing by project. Both thoroughly tested and adaptable.

Why can’t I just draw colored boxes and call it Takt?

One-page Takt plan is iceberg tip. Below surface is systematic 25-step process building through three levels of development. Macro level vets duration from flow. Norm level harmonizes with resources, buffers, work packages, work steps. Micro level implements with control meetings, status boards, continuous improvement. Without systematic process, colored boxes have no substance.

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

Posted in All

How To Do A Feasibility Study For A Construction Project

Read 11 min

How To Do A Feasibility Study: The Filter That Saves Projects Before They Start

Projects don’t fall apart because builders forgot how to build. They fall apart because somebody committed serious money before confirming the project could actually work. There’s a filter designed to catch that exposure before it costs anyone anything real. It’s called a feasibility study. And most teams either rush it, scope it down, or quietly skip past it because momentum feels like progress. When feasibility becomes a checkbox instead of a filter, the project starts bleeding before the first drawing ever gets stamped.

This is a builder’s guide to what a real feasibility study is, where it lives in the process, and why everyone in the chain developers, designers, GCs, trade partners, and owner’s reps needs to understand it. Even if you’re not running the study yourself, your project outcomes depend on whether someone upstream ran it seriously.

When Feasibility Becomes a Checkbox, Projects Bleed Late

Every builder I know has a story about a project that died late. Design was 70% through. GCs were in contract negotiations. Trade partners had cleared backlog to make room for it. Then something that should have been confirmed up front financing, zoning, soil, access, operational fit quietly didn’t work. The project collapsed under the weight of its own momentum. People got hurt. Families got hurt. Careers got bumped sideways.

The failure pattern is predictable. A feasibility study gets rushed, scoped down, or narrowed to “we think this will work.” The team moves into schematic design because the calendar demands it. Drawings start generating invoices. Permits start generating commitments. By the time a real risk surfaces, the project has too much skin in the game to stop cleanly.

This is not a design failure or a contractor failure. It’s a process failure upstream of everyone who gets blamed downstream. Projects start wrong; they don’t go wrong. Over 60% of project success is decided before notice to proceed. If the feasibility filter was soft, the project was already leaking before anyone poured concrete. The design team didn’t fail. The GC didn’t fail. The trades didn’t fail. The system skipped the upstream go/no-go, and the downstream team inherited a problem that was never going to close. The system failed them; they didn’t fail the system.

A Project That Died After Everyone Was Committed

Here’s the story that sticks with me. A developer wanted to build. The vision was real. The city wanted the development. Designers were excited. The authorities having jurisdiction were all aligned. Permits were issued. The GC was mobilizing.

The banks were not aligned. The numbers the deal was sitting on didn’t survive underwriting. The pro forma was optimistic in places that didn’t hold up. The loan didn’t close, and the project died after everyone had already committed months of effort and real dollars.

You can’t undo that. You can’t call designers back on spec time. You can’t refund the permits. The land sits there, still owned, still on the books, and the developer has to figure out what to do with it. The hard part is that most of that exposure could have been closed on paper. A tighter feasibility study one that actually pressure-tested financial feasibility against the specific site constraints would have either fixed the deal early or killed it before anybody bled for it.

Why Feasibility Protects Everyone Downstream

Every hour of feasibility work saves days in design, weeks in the field, and months of recovery when a project goes sideways. Schedule feasibility protects the crews who will eventually build the work. Financial feasibility protects the owner and the lender. Technical feasibility protects the designers and the trades. Operational feasibility protects the end user who will live with the building for thirty years.

And all of it protects the families connected to every single person in the chain. When a project dies late, somebody’s kid doesn’t get dinner at the table that night because Dad or Mom is rebuilding their career. Feasibility is where we start protecting those families. If the plan requires burnout to succeed, the plan is broken, not the people and the plan usually got broken at feasibility.

The Six Lenses of a Real Feasibility Study

A feasibility study answers three questions: can we build this, should we build this, and what will it take if we do? It lives right after concept design early enough that you can still walk away, late enough that you have something specific to pressure-test. Before schematic design. Before design development. Before construction drawings. Before serious money commits. Think of it as mapping your route to the airport before you leave. It doesn’t promise green lights at every intersection. It confirms the roads are open and the route is real. Six lenses need to get stress-tested, and every one of them has killed projects that passed the others.

Site feasibility comes first. Zoning and land use restrictions. Utility availability power, water, sewer. Soil conditions, grading, and environmental exposure. Access, traffic, and logistics. If you want a five-story building and the site only allows three, that’s not a design problem. That’s a site problem that redefines the entire pro forma. This lens ties directly into permitting and financial strategy.

Technical feasibility is next. Can the design actually get built? Are the structural systems constructable? Are the materials and trades actually available in this market? If you’re building on a remote site or in a difficult region, availability is a real constraint, and nobody will thank you for pretending it isn’t.

Financial feasibility is where most projects get killed, or should get killed. Rough order of magnitude cost. Return on investment. Funding sources. This is the lens that catches banks before they catch you. I’ve been on deals that went south because this lens wasn’t looked at deeply enough. Soft financials at feasibility are how you lose a project after a year of design work.

Schedule feasibility is the one most teams underrate. Can this project be built in a duration that matches the pro forma, with general conditions and general requirements that actually fit the budget? A great design on an impossible schedule is not a feasible project. It’s a commitment to burnout.

Legal and regulatory feasibility covers permits, code compliance, environmental regulations, easements, and entitlements. Regulatory surprises late in design are expensive, and they tend to cluster on sites that didn’t get stress-tested at feasibility.

Operational feasibility asks the last question. Will the finished building actually serve the end goal? A building that delivers on schedule and under budget but doesn’t do what the owner needed is still a failure. This is where you connect the physical project back to the business case that paid for it.

When a project clears all six lenses, you’re not guaranteeing success. You’re confirming the project has a path to win. That’s the whole point of the filter.

Red Flags That Feasibility Was Rushed

Before design commits hard, look for signals that the feasibility study was treated as a checkbox instead of a real filter:

  • The pro forma was built on one funding scenario and never stress-tested against the bank’s actual underwriting criteria.
  • Schedule feasibility was assumed from comparable projects instead of modeled against real site and market constraints.
  • Site constraints like soils, utilities, or access were deferred to schematic design rather than confirmed at feasibility.
  • Operational feasibility was skipped because “the owner knows what they want.”
  • Legal and regulatory risks were acknowledged but not owned nobody has specific names next to specific contingencies.

If any of these are present, feasibility is still open. Close them on paper before you have to close them in the field.

Iterate on Paper, Not in the Field

The whole point of a feasibility study is to iterate cheaply. Think Pixar: they iterate a movie eight or nine times as storyboards before production starts, because erasing a whiteboard costs nothing and erasing concrete costs everything. Feasibility is the whiteboard stage for your project.

This is also where the Macro plan starts to live. A rough Macro schedule even a single sheet built at feasibility confirms the overall duration is real. It lets you test the pro forma against an actual LeanTakt sequence of zones, handoffs, long-lead procurement, and buffer structure. Without a Macro plan at feasibility, financial feasibility is a guess, and schedule feasibility is a wish. The Norm plan comes later with trade input, but the Macro has to be grounded early or the entire progression is built on sand.

Where Builders Add Value Upstream

Feasibility is primarily a design team and developer activity, but general contractors, trade partners, and owner’s reps should be in the room especially for schedule and financial feasibility. That’s where builders add the most value and where the biggest gaps usually hide. A GC pressure-tests the schedule against real Takt sequencing. A trade partner flags technical and market constraints before they become submittal fights. An owner’s rep makes sure all six lenses actually get looked at, not just the comfortable ones.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. Bringing discipline to the upstream stages is where we help teams close the window of doom before it opens on the field. Feasibility isn’t paperwork. It’s the first act of respect for the people who will eventually build the work, and for the families behind them.

Signs Your Feasibility Is Actually Real

Before you move into schematic design, confirm you’ve got the right evidence on each lens:

  • Site: independent confirmation of zoning, utilities, soils, access, and environmental constraints not assumptions.
  • Technical: the design intent is constructable with trades and materials available in this specific market.
  • Financial: the pro forma has been stress-tested against the lender’s actual underwriting, not a best-case scenario.
  • Schedule: a Macro-level Takt plan confirms the duration is achievable with realistic buffers.
  • Legal and regulatory: every permit, entitlement, and environmental risk has a specific owner with a specific contingency.
  • Operational: the end user has confirmed the building will serve the business case that paid for it.

All six. Every project. Before a single schematic sheet gets issued.

A Challenge for Builders

Walk your next project this week and ask where feasibility actually landed. Did all six lenses get pressure-tested? Does the Macro plan exist? Is the pro forma built on scenarios the bank will actually underwrite? Is every regulatory risk owned by a specific person with a specific contingency? If you can’t answer those cleanly, the project still has exposure that can be closed on paper right now.

The work of building people who build things starts upstream of the first drawing. It starts with the discipline to run the filter, respect the outcome, and iterate cheaply before the project becomes expensive to change. Plan it first, build it right, finish as you go.

As Taiichi Ohno reminded us, “Having no problems is the biggest problem of all.” Feasibility is where we go looking for problems on purpose, while problems are still cheap to find.

On we go.

Frequently Asked Questions

When does a feasibility study actually happen in the process?

After concept design and before schematic design, design development, and construction drawings. Early enough to walk away without major sunk cost, late enough that the project is specific enough to pressure-test against real constraints.

Who owns the feasibility study, the developer or the design team?

The developer owns it, and the design team usually leads it. GCs, trade partners, and owner’s reps should contribute on schedule, cost, and constructability. Feasibility is a team sport with a clear lead.

Can a project still fail after a solid feasibility study?

Yes, but not from knowable risks. A real feasibility study closes the risks that could have been seen up front. Execution then focuses on the unknowable risks instead of drowning in the knowable ones.

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

Posted in All

The Takt Production System – Part 15

Read 15 min

Are Workers Seeing 50% or 75% of the Plan?

Current industry practice using CPM: workers see almost nothing. They’re told what to do by foreman who at best attempt to follow uncollaborative dictated schedule and at worst follow their own plan and ignore requests by general contractor and their schedule. Results in environment like firefighting. People run around in different directions with false sense of urgency just to find communicated deadlines were either unnecessary or chronically too late anyway. Chaos, lack of direction, and siloed thinking accompanied by waste and variation cause project to fall behind. Teams start throwing workers, money, materials, and maybe some cats at project hoping to finish on time. It’s crazy and yet actually pretty standard in construction. Better industry practice using Last Planner and Scrum: workers might receive 50% of planned information through foreman. Huge improvement but relies on single point of failure. If foreman doesn’t communicate plan effectively, workers don’t see it. Best practice using Takt with Integrated Production Control System: workers see 75% of planned information through multiple paths. Morning worker huddle for entire project site. Crew preparation huddle with 10 to 25 minutes discussing pre-task plan, preparing work, 3Sing, eight wastes, training from work steps created in Takt work packages. Information sent all the way to workers through Takt work steps and huddles. Transfers of information take multiple paths and don’t rely on single point. Bottom line: workers can see plan and have input.

Here’s what most teams miss. They implement Last Planner and Scrum thinking they’ve solved the problem. And they have made huge improvement from CPM chaos. Phase planning with pull planning creates collaborative sequence instead of dictated plan from contractor made in silo. Make ready schedules allow team to foresee roadblocks and plan accurate dates. Weekly work plans coordinate activities ahead of time. Daily huddles discuss plans for day. Percent Plan Complete tracks tasks completed properly and on time. That’s all better than CPM firefighting. But it still relies on foreman as single point of failure for information transfer to workers. If foreman doesn’t communicate effectively, workers don’t see plan. And workers only receive 50% of planned information. But with Takt and Integrated Production Control System, information travels multiple paths. Morning worker huddle connects everyone to overall plan. Crew preparation huddle trains workers from work steps. Workers see 75% of planned information. No single points of failure.

The challenge is most teams think 50% is good enough when actually 75% is achievable. They settled for Last Planner improvement over CPM chaos without realizing Takt takes it further. They accept foreman as single point of failure without creating multiple paths for information transfer. They think daily huddles are enough without implementing afternoon format huddles giving foreman 16 hours to plan, morning worker huddles for entire project site, and crew preparation huddles training from work steps. The difference between 50% and 75% is workers truly seeing plan and having input instead of hoping foreman communicated effectively. That 25% gap is what separates good from best.

Good: Current Industry Practice Using CPM

Currently, in our industry, a master schedule is built using CPM, usually in the proposal phase and detailed to a point that it can be used for short intervals and sometimes day-to-day production. The schedules are built by superintendents or professional schedulers and are updated either weekly or monthly to track progress and identify red flags.

The schedule is usually built with a work breakdown structure, completely logic tied, and lastly, with a finish on or before constraint to force the calculation of total float throughout the system. The schedule is designed for production tracking with a large amount of detail and functions primarily to provide milestones.

Milestones are arguably the main focus of CPM scheduling in addition to the identification of the critical activities within a given month. Project teams use milestones to rally the team and track progress.

Look-ahead schedules are used by the project team to orient subcontractors and plan materials, crew sizes, information, and equipment. Subcontractors are typically given this plan as a directive from the general contractor without much collaboration and subs are expected by culture and by contract to obey the schedule and meet their dates.

Work is carried out without asking: what do workers see? The workers do not see any of this planning. They are told what to do by their foreman who at best attempt to follow the uncollaborative and dictated schedule and at worst follow their own plan and ignore the requests by the general contractor and their schedule.

This results in an environment that is like firefighting in the office. People run around in different directions with a false sense of urgency just to find that the communicated deadlines were either unnecessary or chronically too late anyway. The chaos, lack of direction, and siloed thinking is accompanied by waste and variation which caused the project to fall behind.

Before long, project teams start throwing workers, money, materials, and maybe also some cats, at the project in hopes to finish on time, which is the metaphorical equivalent of putting out a fire with $100 bills. It’s crazy and yet actually pretty standard in construction.

Better: Last Planner System and Scrum

Thankfully, the problems the construction industry has been facing have not gone unnoticed and many are committed to providing solutions to remedy the situation. Systems like Last Planner and Scrum are being adopted without mincing words about the failures of CPM and they are making a difference.

The master scheduling remains largely the same with the adjustment that these schedules should be created at a higher level of detail so Last Planner and Scrum techniques can take over at the right level of detail. The master schedule is still used by the first planners throughout pre-construction and during construction as a long-term planning tool, mainly to identify and track progress towards milestones.

Milestones take on a different role in the new system. They used to be compared to actual progress and three or six-week look-aheads, but now they form the constrained end date for phase planning efforts with pull planning techniques.

Phase planning is a process where the project team, under the direction of the project superintendent and project manager, anticipates key milestones that represent a phase of work. This planning is usually facilitated with a process called pull planning.

Pull planning is a lean process where trade partners with the project management team identify the proper sequence of work according to project needs and the needs of each individual contractor. The practitioners usually identify a milestone on the pull planning backdrop and each contractor after proper preparation and onboarding activities place tags or stickies on the wall in a format that identifies the point in the sequence, the duration, company name, crew size, and needed predecessors.

The teams create the sequence together through practices and rules that should provide a final sequence that is more realistic than a dictated plan from the contractor that may have been made in a silo.

Make ready schedules are short interval schedules which have been coordinated with on-site constraints, other activities, and the capacity of resources on their project site. It is usually the first schedule that the team uses to foresee roadblocks. Its main purpose is to allow all members of the team to plan accurate dates to which trades plan the delivery of people, equipment, materials, and information.

The weekly work plan is the plan for the next week where detail is pulled from the make ready schedules in addition to any new detail. Contractors detail out their activities ahead of time and arrive at the meeting prepared to coordinate their work for the next week so that everyone has the space, materials, time, and information needed to complete the work.

The project team huddles every day to discuss plans for the day, safety, and to coordinate logistics as the crews mobilize into key areas. The daily huddle is where on location and daily planning is done to carry out the weekly work plan.

The team’s success in doing this is tracked with what is called percent plan complete. Percent plan complete (PPC) is a percentage of tasks completed properly and on time as committed in the weekly work plan. The percentage is tracked daily, weekly, and monthly to show the team their progress in making real commitments and producing as a collaborative team.

Best: Takt Planning with Integrated Production Control System

The making ready of work will always be more effective than adapting in the moment on a project site. Roadblocks need to be tracked in a manner that everyone on the project site can see and remove them and observe progress daily.

A visual board is suggested as well as visual maps and floor plans with roadblocks shown where they will affect work. Even if roadblocks are bulleted, as long as they are visual, the system will work. Then the team, including the director, makes the removal of roadblocks their primary responsibility.

Weekly work planning can happen with tags, tasks, or stickies on the board or planning tool, but with Takt it is most effectively done directly within the Takt plan by following the work packages and the work steps within them. For standard, repeatable, and typical work it is helpful to simply prepare work based on the Takt wagons within the time scale.

For more complex work, Takt plans utilize the detail of a day-to-day format within the weekly work plan and can be shown on Takt cards, tags, stickies, dry erase markers on the board, or on your planning application.

Takt control, also known as managing at the place of work, has the goal of placing control at the place of value creation. Short cycle daily meetings on site are considered particularly important. The meetings are moderated by the superintendent and all other supers and foremen all responsible to take part.

The site is managed through Takt control boards. These boards are also standardized and serve as a medium for visualization to achieve transparency. The key to motivating employees to take part in the meetings is to integrate them in the problem-solving process.

The following key points are recorded on the Takt boards:

  • Number of workers per trade.
  • Rate of compliance with the Takt plan.
  • Defects in quality.
  • Safety figures.
  • Numbers of disruption.
  • Information on cleanliness and tidiness.

The artifacts that show this information are:

  • Takt plan.
  • Weekly work plan.
  • Takt zone map.
  • Logistics plan.
  • Day plan agenda.
  • Production tracker.

The Three Huddles Creating 75% Information Transfer

The afternoon format huddle increases the ability of foreman to plan and arrange supportive elements with roughly 16 hours in between the meeting and when the next day begins. Work is planned for the next day in detail so all leaders see together, know together, and act together.

The morning worker huddle encompasses the entire project site. For large projects, major divisions of workers by functional area huddle together every morning to form a social group with a project management team in an exchange of communication regarding expectations and needs. Workers should leave the huddle with clarity and a greater understanding of how to succeed on site, how to be safe, and feeling connected to the overall plan.

The crew preparation huddle is not new but it needs more support and standard implementation. In this huddle the foremen spend 10 to 25 minutes with the workers discussing the pre-task plan, preparing work, 3Sing, discussing the eight wastes, and doing general training from the work steps created in the Takt work packages.

These work steps can individually have checklists or feature of work boards as standard work. Every worker should leave with a pre-task plan for safety and quality and be able to work in the right environment with the materials, tools, space, information, equipment, and clear expectations to succeed in a stable environment.

This truly answers, in the right way, the question: what do workers see? In this system, the workers see as much of the plan as possible.

The System Failed You

Let’s be clear. When teams settle for 50% information transfer to workers, it’s not entirely their fault. The system failed by teaching that Last Planner solves the problem when actually it’s improvement over CPM but still relies on foreman as single point of failure. Nobody showed that if foreman doesn’t communicate plan effectively, workers don’t see it even with pull planning, make ready schedules, and weekly work plans. Nobody explained that Takt with Integrated Production Control System achieves 75% information transfer through multiple paths. The system taught Last Planner is best when actually Takt takes it further.

The system also failed by not teaching the three huddles creating 75% transfer. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. Afternoon format huddle gives foreman 16 hours to plan next day in detail. Morning worker huddle connects entire project site to overall plan creating clarity and understanding. Crew preparation huddle trains workers from work steps created in Takt work packages discussing pre-task plan, 3Sing, eight wastes. These three huddles send information to workers through multiple paths instead of relying on single point. The system taught daily huddles are enough when actually three types of huddles create comprehensive information transfer.

The system fails by not teaching that workers can see plan and have input. With CPM, workers see almost nothing told what to do by foreman. With Last Planner, workers might receive 50% through foreman. With Takt, workers see 75% through multiple paths and have input into problem-solving process. Every worker should leave crew preparation huddle with pre-task plan for safety and quality able to work in right environment with materials, tools, space, information, equipment, clear expectations. The system taught workers are told what to do when actually workers should see plan and contribute to it.

The Challenge

Here’s your assignment. Stop settling for 50% information transfer. Start implementing the three huddles achieving 75%.

Implement afternoon format huddles. Give foreman roughly 16 hours between meeting and when next day begins. Plan work for next day in detail so all leaders see together, know together, act together. Increases ability of foreman to plan and arrange supportive elements.

Implement morning worker huddles. Encompass entire project site. For large projects, major divisions by functional area huddle together every morning forming social group with project management team. Workers should leave with clarity and greater understanding of how to succeed on site, how to be safe, feeling connected to overall plan.

Implement crew preparation huddles. Foremen spend 10 to 25 minutes with workers discussing pre-task plan, preparing work, 3Sing, discussing eight wastes, doing general training from work steps created in Takt work packages. Every worker should leave with pre-task plan for safety and quality able to work in right environment.

Create multiple paths for information transfer. Don’t rely on foreman as single point of failure. Send information to workers through Takt work steps and huddles. If foreman doesn’t communicate effectively, workers still see plan through other paths.

Use Takt control boards. Record number of workers per trade, rate of compliance with Takt plan, defects in quality, safety figures, numbers of disruption, information on cleanliness and tidiness. Artifacts: Takt plan, weekly work plan, Takt zone map, logistics plan, day plan agenda, production tracker.

Make roadblock removal visible to entire team. Visual boards, maps, floor plans with roadblocks shown where they affect work. Team including director makes removal of roadblocks primary responsibility.

Answer the question: what do workers see? With Takt and Integrated Production Control System, workers see 75% of planned information. Workers can see plan and have input. That’s the difference between good, better, and best.

On we go.

FAQ

What’s the difference between Good, Better, and Best?

Good (CPM): workers see almost nothing, told what to do by foreman, chaos and firefighting. Better (Last Planner/Scrum): workers receive 50% of planned information through foreman, improvement but single point of failure. Best (Takt with Integrated Production Control): workers see 75% through multiple paths, no single points of failure.

What are the three huddles creating 75% information transfer?

Afternoon format huddle: gives foreman 16 hours to plan next day in detail. Morning worker huddle: entire project site connects to overall plan, workers leave with clarity and understanding. Crew preparation huddle: 10-25 minutes discussing pre-task plan, 3Sing, eight wastes, training from work steps created in Takt work packages.

Why is 75% better than 50%?

Last Planner achieves 50% information transfer but relies on foreman as single point of failure. If foreman doesn’t communicate effectively, workers don’t see plan. Takt achieves 75% through multiple paths. Information sent to workers through Takt work steps and huddles. Workers can see plan and have input.

What is Takt control?

Managing at place of work, placing control at place of value creation. Short cycle daily meetings on site moderated by superintendent. Site managed through Takt control boards recording worker counts, compliance rate, defects, safety figures, disruptions, cleanliness. Artifacts: Takt plan, weekly work plan, Takt zone map, logistics plan, day plan agenda, production tracker.

How does Takt eliminate single points of failure?

Last Planner relies on foreman to communicate plan to workers. If foreman fails, information doesn’t transfer. Takt sends information through multiple paths: work steps in Takt work packages, afternoon format huddle, morning worker huddle, crew preparation huddle. Even if one path fails, others still transfer information.

 

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

Posted in All

The Takt Production System – Part 14

Read 17 min

Are You Rolling Sixes and Ones or Consistent Threes?

The parade of trades simulation. Red team has normal six-sided die rolling numbers one through six representing variation. Blue team has modified die rolling only twos, threes, and fours representing reduced variation. Results after running simulation: Red team finishes in 26 weeks with 380 workers on site costing $21.7 million. Blue team finishes in 21 weeks with 280 workers on site costing $12.9 million. That’s an $8.8 million difference. Same project. Different approach. Red team tried rolling sixes to get out fast creating variation. Week looks like 6552211 representing attempt to move quickly at first followed by slowdown because of interruption eventually ending up stuck. Blue team maintained flow. Week looks like 4434322 representing steady consistent work without overwhelming rush from rolling six or painful crawl of one. When variation is eliminated, work flows from one end to the other without getting held up. The lesson: flow has very little variation. Movement doesn’t equal production. All this movement is actually waste. People start pushing and creating variation because it makes them feel good. Gives impression of progress. But requires twice as much material, 100 more people, and five more units of material inventory. Everything slows down because part of workforce is dedicated to managing, moving, inventorying, fixing, replacing, reordering, and organizing materials instead of installing work. Don’t roll sixes and ones when you can roll threes.

Here’s what most teams miss. They think pushing equals progress. Getting out of ground fast. Being aggressive with complex areas. Advancing schedule whenever possible. Bringing all materials now. Keep pushing everything for schedule. These people are trying to roll sixes in parade of trades which will later cause mess of ones. What if you told superintendent to slow down a little and keep steady flow and even pace? He might say you know absolutely nothing about construction and should get another job. And yet the data shows he will finish in 26 weeks with 380 people on site with material inventory of 10 like red team. This happens because people think movement equals production which is not the case. All this movement is actually waste. It gives impression of progress but requires twice as much material, 100 more people, and more inventory. The blue team rolling consistent threes and fours finishes five weeks earlier with 100 fewer people and $8.8 million less cost. Flow beats pushing. Data proves it.

The challenge is most superintendents were taught to push. Get work done fast. Start as early as possible. Bring materials now. Don’t slow down anything. Have workers working everywhere on site with no empty areas. But that’s exactly what destroys flow creating variation extending duration increasing costs. When superintendent won’t keep flow on schedule and hold dates, trades keep more people on site and more materials on site. When materials pile up, production slows down. Workforce dedicated to managing materials instead of installing work. CPM pushes as much work to start as early as possible putting too much work in process that must be managed, maintained, checked, monitored. When work in process increases, capacity of team and project resources reduced causing rework and eight wastes. But if you finish as you go, you have capacity to focus on work in process and complete it right first time. Don’t roll sixes and ones. Roll consistent threes.

Leveling Out Around Bottlenecks as Strategy

Some may be very concerned about our comment to slow down certain resources. But consider what happens when after we have optimized and sped up all bottlenecks, we continue to let the faster trades continue to go fast.

What happens? People are stacked in certain areas without flow, without geographical control, burying certain scopes, installing too early, which increases the amount of defects and use of resources such as the project management team’s time. This affects the trades that really need the help. There’s little merit to going faster than the general throughput.

The law of bottlenecks states that throughput time is primarily affected by the process that has the longest cycle time. In construction, the overall throughput of the phase is mostly affected by the process with the longest duration within the system.

Best practice is to first optimize the bottlenecks for the slower installations and then to even out the throughput of the remaining work. Therefore, the entire system. Because CPM does not allow us to see our bottlenecks, we cannot optimize them so the system ends up with a longer overall project duration, overproduced areas, fluctuating worker and material inventory levels, and a number of detrimental starts and stops.

The tricky thing with bottlenecks is that new ones will show up when you optimize the first ones or the largest ones so it’s a continual game of increasing flow by adjusting the throughput of the system. This is the key to achieving the shortest overall duration with the smallest crew sizes with the most minimal inventory levels and a visual system that identifies problems when they happen in a continuous flow that allows an evenness the team can use to focus their attention on the removal of roadblocks.

Finish as You Go

For Takt to work well, we have to finish as we go. Historically, superintendents have attempted to accelerate the project to gain time at the end to fix all the mistakes from going too fast and not installing it right the first time. With Takt, we cannot have and should not need to have that excessive buffer time for an excessive punch list.

With Takt, and while working to prevent roadblocks, the team, and especially the engineers, will be inspecting work, identifying punch list items, and working with trades to correct as they go. Meaning, finish as they go. Before a trade leaves the area or the project, they should not only install the production work, but they should finish the scope in its entirety.

This will take a mindset shift for most of our leaders in construction, but when this path is taken, we will see a better quality product delivered to the customer sooner.

Limiting Work in Process

This inherently ensures work in process is limited. CPM pushes as much work to the start as early as possible. That is a normal thought and concept, but it does something that is detrimental to our construction operations. It puts too much work in process.

Work in process that must be managed, maintained, checked, monitored, supported, and which utilizes precious resources. When work in process increases needlessly, the capacity of the team and the project resources are reduced, which causes rework and a number of the other eight wastes. It also causes unevenness and overburden.

The goal is to keep the project management team balanced, healthy, with workers going at a reasonable speed, and trade resources working in a flow and not over capacity, so the team can continue preparing and executing work with quality at the source.

When we increase work in process, the team is so focused on handling the overburden on the project and the project resources, they do not see roadblocks and remove them ahead of the work. Their ability to prepare work diminishes, and more defective work is passed through the system.

But if we finish as we go, we will have the capacity to focus on the work that is in process and complete it right the first time. Then, quality at the source becomes a culture.

Quality at the Source

Quality at the source is a concept that states a culture and condition in which each employee and worker is held responsible for ensuring the quality of products at the place of work or when the work is produced. To do this, the culture and project systems must include standardized work, self checks, peer checks, visual management, mistake proofing, and continuous improvement of the system.

The Law of the Effect of Variation

The law of the effect of variation is that throughput time and, in effect, the overall project duration is affected as variation increases. Variation has a higher effect on throughput time as the process gets closer to 100% utilization.

For construction, this means that variation is detrimental to flow. Variation comes in two forms:

  • Inevitable variation: This type of variation comes from sources that are not under the control of the project team or the contractor. Examples of this would be weather, acts of God, or customer change requests.
  • Non-inevitable variation: This type of variation comes from sources that are under the control of the project team or the contractor. Examples of these would be defects that cause delays, RFIs that slow the work, and interruptions in trade flow.

When we assert that Takt planning creates stability and reduces variation, the frequent response is: things change on a construction site. How can you reduce variation? The answer is we reduce non-inevitable variation. We don’t want everything changing, especially if we are unable to respond. What do we do? We stabilize what we can so we can focus where we need to.

The Parade of Trades Simulation Explained

The parade of trades simulation proves flow beats pushing. The tricky secret is that the red team had a regular six-sided die with numbers ranging from 1 to 6. The blue team had a die that could only roll 4s, 3s, and 2s.

A week with a normal die would be something like 6552211 and would represent an attempt to move quickly at first, followed by a slowdown because of an interruption and eventually ending up stuck. A week with the blue team’s die might look like 4434322.

This is synonymous with the concept of maintaining the flow of work. A flow has very little variation. When that variation is eliminated, the chips, or the work, could flow from one end to the other without getting held up by the overwhelming rush from rolling a 6 or the painful crawl of a 1.

The Current State of Our Industry

We often hear people say: we need to get out of the ground fast when we can influence a fewer number of contractors. This is correct. We also hear that we need to be aggressive with complex and unknown areas and scopes on our projects. This is also correct.

Sometimes, though, well-meaning folks will apply both of those concepts to the entire project and say things like: advance the schedule whenever possible, or I want all my materials here now, or just bring it, or I’m a pusher, or keep pushing everything that you can for the schedule. These people are trying to roll 6s in the parade of trades, which will later cause a mess of 1s.

Consider this: What if we told a superintendent to slow down a little and keep a steady flow and an even pace? What would he say? He might say we know absolutely nothing about construction and should go get another job, and yet the data shows he will finish in 26 weeks with 380 people on site with a material inventory of 10 like the red team parade of trades.

This happens because people think movement equals production, which is not the case. All this movement is actually a waste. People start pushing and creating variation because it makes them feel good. It gives an impression of progress, but it requires twice as much material, 100 more people, and 5 more units of material inventory in a week.

What Happens When You Don’t Keep Flow

What happens when a superintendent won’t keep a flow on the schedule and hold dates? If you’re a trade partner, how would you react? You would possibly keep more people on site and most definitely keep more materials on site.

What happens when materials pile up on site? You guessed it. Production slows down. Everything slows down because part of our workforce is dedicated to managing, moving, material inventorying, fixing, replacing, reordering and organizing materials.

The Factory Analogy

Imagine a factory with an assembly line that produces a certain number of finished items every hour. The throughput is the rate at which the factory can process the raw materials into finished items. Say you have 4 machines in the factory that work together to produce the final finished product.

The first machine can work on 4 items per hour, the second at 2 items per hour, and both the third and fourth machines produce 4 items per hour. What is the throughput of the system per hour? The answer is 2 because of the bottleneck.

But here is the moment. The throughput in the example where we had all machines working at full efficiency, even though they were going different speeds, is likely going to be 1.25 or 1.5 finished items per hour, not 2.

Consider what happens between the first and second machines. An inventory of materials begins to pile up. Manpower is then allocated to manage the material inventory. Space in the factory diminishes. People who would otherwise be running machines are now managing the machines and the material inventory. Workers down the line are waiting, and more resources are needed to manage materials on the third and fourth machines.

Waste increases and the speed of the system decreases. Therefore, the throughput is 1.5 or fewer finished items per hour instead of 2. They would have been better off to increase the 2 part per hour machine to a 4 part per hour machine or slow everything down to 2.

The Cost Difference

The cost associated with variation is staggering. Compare just this little example the cost difference between the red team and the blue team:

  • Red team: 26 weeks with 380 workers = 380 people × $55 per hour × 40 hours per week × 26 weeks = $21.7 million
  • Blue team: 21 weeks with 280 workers = 280 people × $55 per hour × 40 hours per week × 21 weeks = $12.9 million

This is an $8.8 million difference. This ratio can be scaled for whatever size project we are talking about. The difference is in the man hours spent in waste because of a lack of flow. Pushing literally destroys projects, and our industry superintendents must protect us from this.

The System Failed You

Let’s be clear. When superintendents push instead of creating flow, it’s not entirely their fault. The system failed by teaching that movement equals production when actually movement is waste. Nobody showed the parade of trades simulation proving flow beats pushing. Nobody explained that red team rolling sixes and ones finishes in 26 weeks with 380 workers costing $21.7 million while blue team rolling consistent threes and fours finishes in 21 weeks with 280 workers costing $12.9 million. That’s $8.8 million difference on same project. The system taught push when actually flow beats push every time.

The system also failed by not teaching to finish as you go. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. Historically, superintendents accelerate project to gain time at end to fix mistakes from going too fast and not installing right first time. With Takt, cannot and should not need excessive buffer time for excessive punch list. Team inspects work, identifies punch, corrects as they go. Before trade leaves area, should install production work AND finish scope in entirety. Mindset shift but delivers better quality product sooner. The system taught create buffer for rework when actually finish as you go prevents rework.

The system fails by teaching to push work to start as early as possible putting too much work in process. Work in process must be managed, maintained, checked, monitored, supported utilizing precious resources. When work in process increases, capacity of team and project resources reduced causing rework and eight wastes. Team so focused on handling overburden they don’t see roadblocks and remove them ahead of work. Ability to prepare work diminishes. More defective work passed through system. The system taught maximize work in process when actually limiting work in process creates capacity to complete work right first time.

The Challenge

Here’s your assignment. Stop rolling sixes and ones. Start rolling consistent threes and fours.

Understand the data. Red team (variation) finishes in 26 weeks with 380 workers costing $21.7 million. Blue team (flow) finishes in 21 weeks with 280 workers costing $12.9 million. $8.8 million difference. Flow beats pushing. Movement doesn’t equal production. Movement is waste.

Level out around bottlenecks. First optimize bottlenecks for slower installations. Then even out throughput of remaining work. Little merit to going faster than general throughput. When faster trades continue going fast, people stacked in areas without flow, burying scopes, installing too early, increasing defects.

Finish as you go. Don’t accelerate project to gain time at end to fix mistakes. Inspect work, identify punch, correct as you go. Before trade leaves area, install production work AND finish scope in entirety. Delivers better quality product sooner.

Limit work in process. Don’t push as much work to start as early as possible. Too much work in process must be managed, maintained, checked, monitored. When work in process increases, capacity of team and project resources reduced. If you finish as you go, have capacity to focus on work in process and complete right first time.

Reduce non-inevitable variation. Stabilize what you can so you can focus where you need to. Don’t want everything changing especially when unable to respond. Variation is detrimental to flow. Variation has higher effect on throughput time as process gets closer to 100% utilization.

Stop pushing. If you hear someone ask to create variation in schedules and flow, be skeptical. If you hear folks ask for increase of material inventory, give it second look. Want to create stable environments, keep workers installing work they plan for day or week, have plan for everything.

Don’t roll sixes and ones when you can roll threes. The answer is not to push. Flow will always reduce materials, manpower, mistakes, and time it takes to do something.

On we go.

FAQ

What is the parade of trades simulation?

Red team has normal die (1-6) representing variation. Blue team has modified die (2s, 3s, 4s) representing flow. Red team finishes 26 weeks, 380 workers, $21.7 million. Blue team finishes 21 weeks, 280 workers, $12.9 million. $8.8 million difference. Flow beats pushing. Consistent threes and fours beat sixes and ones.

Why does pushing slow down production?

When materials pile up on site, part of workforce dedicated to managing, moving, inventorying, fixing, replacing, reordering, organizing materials instead of installing work. Waste increases and speed of system decreases. Movement doesn’t equal production. Movement is waste creating impression of progress but requiring twice as much material, 100 more people.

What does “finish as you go” mean?

Before trade leaves area, should install production work AND finish scope in entirety. Don’t accelerate project to gain time at end to fix mistakes. Inspect work, identify punch, correct as you go. Delivers better quality product sooner. No excessive buffer time for excessive punch list.

Why limit work in process?

CPM pushes work to start as early as possible putting too much work in process that must be managed, maintained, checked, monitored. When work in process increases, capacity of team and project resources reduced causing rework and eight wastes. Team focused on handling overburden doesn’t see roadblocks. If you finish as you go, have capacity to complete work right first time.

What’s the difference between inevitable and non-inevitable variation?

Inevitable variation: not under control of project team (weather, acts of God, customer changes). Non-inevitable variation: under control of project team (defects causing delays, RFIs slowing work, interruptions in trade flow). Reduce non-inevitable variation. Stabilize what you can so you can focus where you need to.

 

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

Posted in All

The Takt Production System – Part 13

Read 16 min

Are You Obeying Production Laws or Fighting Them?

You’re fighting production laws and wondering why projects extend. Little’s Law states throughput time equals number of flow units times cycle time. In construction, duration equals number of processes times process time per unit. Only Takt allows you to calculate this. CPM doesn’t allow calculating optimal batch sizes. Doesn’t help reduce work in process. In fact, makes it easy to increase it with forward and backward paths. Doesn’t enable finishing as you go in a rhythm. CPM does not obey this scientific and mathematical law. Rather ends up fighting it. The Law of Bottlenecks says every system has at least one constraint limiting performance. Process with longest cycle time increases overall throughput time. Therefore bottlenecks must be identified, optimized, or eliminated. But CPM can’t visualize trade flow so can’t find bottlenecks let alone optimize them. Critical path focuses on longest network of activities from beginning to end rippling through different trades and different phases. Doesn’t isolate and make visual trade flow within phases. Takt, on the other hand, makes workflow, trade flow, and logistical flow easily visible. Bottlenecks easily seen and easily optimized with standard work steps packaged within Takt wagons. The Law of Variation says as variation increases, throughput times increase. Project end date extends. Must see and prevent roadblocks, create standards and consistency. CPM is so chaotic it’s difficult to see problems and takes so much management capacity there’s little time to prevent them. Takt takes one-twelfth time to manage so team focuses on making work ready and preventing roadblocks.

Here’s what most teams miss. They schedule projects without understanding the production laws governing them. They don’t know Little’s Law determining duration based on flow units and cycle time. They don’t know the Law of Bottlenecks requiring identification and optimization of constraints. They don’t know the Law of Variation showing that variation increases duration. And because they don’t know the laws, they use CPM fighting every single one. CPM can’t calculate optimal throughput times using the formula. Can’t reduce work in process by calculating ideal batch sizes. Can’t finish as you go by showing clearly when to finish sequences in rhythm. Can’t visualize trade flow to find bottlenecks. Can’t create standards reducing variation. The system fights the laws then teams wonder why projects extend and chaos reigns. Because you can’t fight production laws and win. You must obey them. And only Takt allows this.

The challenge is most teams think scheduling is art or guesswork when actually it’s science and mathematics. Production laws govern construction whether you acknowledge them or not. Little’s Law determines throughput time. The Law of Bottlenecks shows process with longest cycle time increases duration. The Law of Variation proves variation extends end dates. These are mathematical certainties, not opinions. But CPM ignores them all creating chaos instead of flow. Takt obeys them all creating predictable outcomes. The formula proves it: number of Takt wagons plus number of Takt areas minus one, sum of that multiplied by Takt time equals throughput time. That’s Little’s Law applied to construction. Scientific. Mathematical. Predictable.

Little’s Law: Throughput Time Equals Flow Units Times Cycle Time

Little’s Law is a theorem that determines the average number of items in a stationary queuing system based on the average waiting time of an item within a system and the average number of items arriving at the system per unit of time.

To simplify this, Little’s Law states that the throughput time, phase duration, or project duration in construction equals the number of flow units or process units in construction times the cycle time. That means the amount of processes in the system multiplied by the process time per unit determines the overall duration.

In construction, this is only calculated with Takt. It enables us to do the following:

  • Plan smaller batch sizes.
  • Limit work in process.
  • Finish as we go.

In Takt, the formula shows the number of Takt wagons plus the number of Takt areas minus one. The sum of that multiplied by the Takt time equals the throughput time or duration based on Little’s Law.

The only way to stabilize and optimize a project is to obey the production laws and not fight against them. Only Takt allows this.

Consider this: Does CPM allow us to calculate optimal batch sizes? No. Does CPM help us reduce work in process? No. In fact, it makes it easy to increase it with its forward and backward paths. Does CPM enable us to finish as we go? Not really. Maybe. But it definitely does not allow us to see when we need to finish in a rhythm.

CPM does not obey this scientific and mathematical law, but rather ends up fighting it.

Takt obeys this law in the following ways:

  • Takt allows us to calculate optimal throughput times and use the formula.
  • Takt allows us to reduce work in process not only by calculating ideal batch sizes, but also by putting work into a rhythm that makes work happen only when it is needed per the flow.
  • Takt allows us to finish as we go by showing clearly and visually when we need to finish sequences, and it puts materials, information, and worker counts into a consistent rhythm so we have the capacity to do so.

The Law of Bottlenecks: Find Them, Optimize Them, Start Again

The bottleneck law has its origin in the theory of constraints created by Dr. Elihu Goldratt and published in 1984 in his book The Goal. The law says that every system, regardless of how well it works, has at least one constraint, a bottleneck, that limits performance.

This law also states that when the largest constraint is optimized or removed, the other bottlenecks will show up in the system. To apply this to construction, we need to understand that the process with the longest cycle time will increase the overall throughput time or duration. Therefore, bottlenecks must be identified, optimized, or eliminated.

In the book The Bottleneck Rules by Clark Ching, the author provides an acronym that might be easy for us to remember: FOCCCUS.

  • Find the bottleneck.
  • Optimize it. Once you know where the bottleneck is, you can increase the process capacity and reduce cycle time.
  • Coordinate with other non-bottleneck work to increase the capacity of the bottleneck.
  • Collaborate with other non-bottleneck work and see if those processes can help the bottleneck process.
  • Curate the work needed for the bottleneck to reduce the demand on the process.
  • Upgrade the resources that compose the process to increase the capacity.
  • Start again finding other bottlenecks.

In order to obey the second production law, we must be able to see and optimize bottlenecks. And because bottlenecks are mainly found in the cycle time of a process, we will find most bottlenecks by visualizing trade flow, not just workflow.

CPM does not do this because you cannot see all three types of flow. You can barely see some parts of the workflow, but no one can easily see trade flow and therefore no one can easily find bottlenecks in CPM, let alone optimize them.

The very nature of a critical path focuses on the longest network of activities from beginning to end. Not only does this ripple through different trades, but it also ripples through different phases as well. CPM does not have the ability to identify bottlenecks because it does not isolate and make visual trade flow within phases.

Takt, on the other hand, gets an A-plus for this. In Takt, anyone can easily visualize workflow, trade flow, and logistical flow. And bottlenecks are easily seen and easily optimized with the standard work steps packaged within Takt wagons. Takt is the only scheduling system that obeys the law of bottlenecks.

The Law of the Effect of Variation: Variation Increases Duration

The law of variation is defined as the difference between an ideal and an actual situation. Variation or variability is most often encountered as a change in data, expected outcomes, or slight changes in production quality. Variation in construction usually comes from waste, unevenness, or an overburden on resources.

As variation increases, throughput times or duration increases. That means that as variation increases on our projects, then the project end date will extend. This means that we must see and prevent roadblocks and create standards and consistency.

CPM again fails miserably on both counts. A CPM sequence is so chaotic it is difficult to see problems within the system. It also takes so much management capacity to manage as a schedule, there is very little time to even try doing so. And for the second point, again, CPM is so inconsistent and chaotic, typical and standard work steps are not created to baseline processes and cycle times so that roadblocks can be more easily seen.

Conversely, Takt cares for both considerations. Takt takes one-twelfth of the time to manage as a scheduling system so the team’s main focus can be on making work ready and preventing roadblocks. Takt also creates a visual schedule where it is easy to see roadblocks.

Focusing on Throughput, Not Individual Efficiency

The throughput through the entire system is our focus, not individual efficiencies for trades. We want collective efficiency for trades. We want trades going at relatively the same rate of production. Stated differently, we want everyone to succeed together as a group and to optimize the project, not just their individual companies.

The throughput is defined as the rate at which a certain amount of material or items, or in this case the construction processes, pass through a system or process. More efficient that this process is as it passes through the system or building, the better our throughput.

Individual efficiency is concerned with the production or utilization of individual resources or contractors which does not always help the overall throughput. In fact, it interrupts it. We need all contractors working at relatively the same throughput according to the Takt time in order for there to be flow.

If contractors are working faster or slower than average, it might seem helpful to that individual trade partner’s productivity, but it interrupts the overall throughput, creates variation, then increases inventory levels, which increases defects.

Applying Little’s Law to Balance the System

According to Modig, Little’s Law states that the throughput time is equal to the number of flow units in the process multiplied by the cycle time. In translating this to construction, we can say that throughput time equals the number of areas needing a process multiplied by the process duration.

For example, if the throughput time for the framer equals 10 areas multiplied by 5 days, it would result in 50 days. If the in-wall electrical roughing contractor has a throughput time that equals 10 areas times 10 days, it would result in 100 days.

Let’s now say that the remaining contractors all have throughput times of 50 like the framers. That would mean we need to speed up the electrician. How do we do that? By adjusting resources to match the throughput times of the other trades. We need to get 2 crews and the formula would be as follows: throughput time equals 10 areas times 5 days with 2 crews equals 50 days.

We now have a balanced system and are all going at the same rate together. These are the types of decisions we have to make to optimize the whole of the project sometimes at the expense of individual contractor efficiencies. In some instances, we have to speed up certain resources and slow down others. This is called leveling out around bottlenecks as our strategy.

Takt Requires Discipline and Accountability

With Takt systems, we need to hold the line, keep the rhythm, and be disciplined. Otherwise, we leave the system and the project descends into chaos. Therefore, Takt planning requires project teams to hold others accountable, control the site, and hold the line.

This is very difficult for a team and can be a reason project teams may be hesitant to use the Takt system. It is also why trades may be hesitant to participate with Takt because they will be held accountable. You can be sure that weak leaders and non-accountable trades will not like Takt.

Prefabrication Supports Takt

Takt keeps the system stable and then the team can accelerate when we prefabricate as much as we can. Consistent and stable scheduling systems need to be supported by prefabrication. When a project is entirely stick built, it will generally experience uncoordinated work issues with slow and unpredictable installation rates, which will not fully enable flow.

To be as effective with Takt planning as we can be, we need to prefabricate as much as possible within the project budget. Basically, following an assembly schedule is easier when you can piece it together like Legos or IKEA furniture. We must prefabricate as much as we can to create consistency and flow, and we prefabricate to the beat or rhythm of a production schedule, namely Takt.

The System Failed You

Let’s be clear. When teams don’t understand production laws, it’s not entirely their fault. The system failed by teaching CPM without explaining that it violates Little’s Law, the Law of Bottlenecks, and the Law of Variation. Nobody showed that CPM can’t calculate optimal batch sizes, can’t reduce work in process, can’t visualize trade flow to find bottlenecks, can’t create standards reducing variation. Nobody explained that the formula for throughput time requires Takt: number of Takt wagons plus number of Takt areas minus one, multiplied by Takt time. The system taught ignore production laws when actually obeying them is what creates predictable outcomes.

The system also failed by not teaching that individual efficiency interrupts overall throughput. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. Contractors working faster or slower than average interrupts overall throughput, creates variation, increases inventory levels, increases defects. Need all contractors working at relatively same throughput according to Takt time for flow. But CPM encourages individual efficiency maximizing resources instead of collective efficiency optimizing system. The system taught wrong metric preventing flow from happening.

The system fails by not teaching FOCCCUS for bottlenecks. Find the bottleneck, optimize it, coordinate with non-bottleneck work, collaborate with other processes, curate work needed, upgrade resources, start again finding other bottlenecks. When largest constraint is optimized or removed, other bottlenecks show up. This is continuous improvement at system level. But CPM can’t visualize trade flow so can’t find bottlenecks. The system taught react to problems when actually identifying and optimizing bottlenecks prevents problems from limiting performance.

The Challenge

Here’s your assignment. Stop fighting production laws. Start obeying them through Takt planning.

Apply Little’s Law. Throughput time equals number of flow units times cycle time. In construction: duration equals number of processes times process time per unit. Formula: number of Takt wagons plus number of Takt areas minus one, multiplied by Takt time equals throughput time. Use this to calculate optimal batch sizes, reduce work in process, finish as you go.

Obey the Law of Bottlenecks. Find them, optimize them, start again. Use FOCCCUS: Find, Optimize, Coordinate, Collaborate, Curate, Upgrade, Start again. Process with longest cycle time increases overall throughput time. Visualize trade flow to identify bottlenecks. Optimize with standard work steps. When largest constraint is optimized, other bottlenecks show up. This is continuous improvement.

Follow the Law of Variation. As variation increases, duration increases. See and prevent roadblocks. Create standards and consistency. Use Takt taking one-twelfth time to manage enabling team to focus on making work ready and preventing roadblocks. Visual schedule makes roadblocks easy to see.

Focus on throughput, not individual efficiency. Want collective efficiency with trades going at relatively same rate of production. Everyone succeeds together as group optimizing project, not just individual companies. Balance system using Little’s Law to match throughput times. Sometimes speed up resources, sometimes slow down. Level out around bottlenecks.

Hold the line, keep the rhythm, be disciplined. Takt requires accountability. Hold others accountable, control the site, hold the line. Otherwise leave system and project descends into chaos.

Support Takt with prefabrication creating consistency and flow. Prefabricate as much as possible to beat or rhythm of production schedule. Assembly schedules easier when piecing together like Legos.

Production laws are scientific and mathematical. Not opinions. Obey them or fight them. Only one option works.

On we go.

FAQ

What is Little’s Law and how does it apply to construction?

Throughput time equals number of flow units times cycle time. In construction: duration equals number of processes times process time per unit. Formula: number of Takt wagons plus number of Takt areas minus one, multiplied by Takt time equals throughput time. Enables planning smaller batch sizes, limiting work in process, finishing as you go. CPM doesn’t allow this.

What is the Law of Bottlenecks?

Every system has at least one constraint limiting performance. Process with longest cycle time increases overall throughput time. Therefore bottlenecks must be identified, optimized, or eliminated. FOCCCUS: Find, Optimize, Coordinate, Collaborate, Curate, Upgrade, Start again. When largest constraint is optimized, other bottlenecks show up. CPM can’t visualize trade flow so can’t find bottlenecks.

What is the Law of Variation?

As variation increases, throughput times increase. Project end date extends. Must see and prevent roadblocks, create standards and consistency. CPM is chaotic making it difficult to see problems and takes too much management capacity. Takt takes 1/12 time to manage so team focuses on making work ready preventing roadblocks.

Why focus on throughput instead of individual efficiency?

Individual efficiency interrupts overall throughput. If contractors work faster or slower than average, it interrupts throughput, creates variation, increases inventory, increases defects. Need all contractors working at relatively same throughput according to Takt time for flow. Want collective efficiency optimizing project, not individual companies.

How do you balance the system using Little’s Law?

Calculate throughput time for each trade: number of areas times process duration. If one trade has longer throughput time, adjust resources to match others. Add crews to speed up. Add buffer to slow down. Result: balanced system with all trades going at same rate together. Leveling out around bottlenecks as strategy.

 

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

Posted in All

The Takt Production System – Part 12

Read 15 min

Are You Building Boats or Building Trains?

You’re floating on a river. The current takes you where it wants. You react to obstacles appearing suddenly. You can’t control the flow. You hope for the best in the moment. That’s most lean scheduling systems encouraging reactionary planning at the moment. It’s a lot like floating on a river you can’t control. Conversely, creating a railroad, creating a system of control is akin to Takt where you make your own destiny and control the work. So don’t build boats when you can build trains and railways. Takt is a collaborative system where you predict as much of what should take place in your future as possible and prepare for success instead of hoping for the best in the moment. On construction projects today, you need stability rather than reduction of resources. Stability is created when you start tasks on time, build them right, and finish as you go. Just like a train must leave the station on time, drive at the right speed, not have any accidents, and arrive at the destination on time. This stability, these trains, and Takt relies heavily on rhythm. And rhythm is smooth and smooth is fast. Rushing takes longer than going at the right rate.

Here’s what most teams miss. They think the decision is between going fast and finishing early versus going at the right rhythm and finishing later. But that’s wrong. The decision is between going fast and failing versus going at the right rhythm and finishing at the soonest possible moment. The decision is between going fast and finishing late versus going at the right rhythm and finishing on the earliest possible date. Rushing creates chaos preventing flow extending duration. Rhythm creates stability enabling flow reducing duration. The Navy SEALs say slow is smooth and smooth is fast. In Takt we say rhythm is smooth and smooth is fast. Because rhythm determined by capacity is the pace at which you can actually complete work. Faster than capacity fails. At capacity succeeds. And that rhythm is what brings problems to the surface. Takt shows what should be done based on capacity and flow. CPM guesses what will be done based on projections. When work doesn’t meet rhythm, you see deviation immediately and correct it immediately. When work doesn’t meet CPM path, you just make another path, then another, then another until only options remaining result in crash landing.

The challenge is most teams never learned why Takt works. They know CPM. They’ve heard about location-based scheduling. But they don’t understand that Takt is fundamentally different because it’s visual showing everyone the plan enabling them to see as group, know as group, and act as group. If you could get all people in an organization rowing in the same direction, you could dominate any industry in any market against any competition at any time. That’s what Takt does. It allows everyone to see the plan making collaboration real instead of theoretical. And it brings problems to surface faster in visible way enabling teams to see and fix problems as they go instead of responding to massive issues when it’s almost too late. Plus it takes about one-twelfth the time to manage a project with Takt as with CPM. The genius is it’s visual and easy to use once understood and created.

The Railroad vs. River Analogy

A railway is intentionally made. A river is based on circumstances at the moment. Think about it. Most lean scheduling systems encourage reactionary planning at the moment, which is a lot like floating on a river you can’t control. Conversely, creating a railroad, creating a system of control is akin to Takt where we may make our own destiny and control the work.

So don’t build boats when you can build trains and railways. It should be noted that Takt has nothing to do with siloed leadership or old-time command-and-control systems. Takt is a collaborative system where we predict as much of what should take place in our future as possible and prepare for success instead of hoping for the best in the moment.

On construction projects today, we need stability rather than the reduction of resources. Stability is created when we start tasks on time, build them right, and finish as we go. Just like a train must leave the station on time, drive at the right speed, not have any accidents, and arrive at the destination on time.

This stability, these trains, and Takt relies heavily on rhythm.

Rhythm Is Smooth and Smooth Is Fast

There’s a famous saying from the US Navy SEALs: slow is smooth and smooth is fast. We would like to repurpose it as rhythm is smooth and smooth is fast.

The point is that rushing takes longer than going at the right rate. The decision is not between going fast and finishing early versus going at the right rhythm and finishing later. The decision is between going fast and failing versus going at the right rhythm and finishing at the soonest possible moment.

The decision is between going fast and finishing late versus going at the right rhythm and finishing on the earliest possible date.

Rhythm is key. It is the pace at which processes work or work is completed within the project. It represents the stagger between the start of Takt trains or sequences per the Takt time. Rhythm is a key consideration to the concept of flow, and that rhythm is determined by capacity.

The rate at which we can complete buildings is determined by the capacity of resources in the local market and how many professional workers are available. It is determined by how many materials can be produced, how many trained workers are available, and how much money an owner will pay for the project. Each of these resources have a capacity.

It is critical to understand that capacity and adjust the Takt time, rhythm, and throughput time and incorporate it into the overall plan. There’s little merit to just making a plan to fit the stipulated end date when there’s no capacity to do it.

Four Considerations for Flow

We increase our capacity and capability on a project within resource constraints when we increase consistency. All four of these considerations are important for flow:

  • Rhythm: The pace at which processes work or work is completed. The stagger between start of Takt trains per Takt time.
  • Capacity: The rate at which resources can perform determined by local market, materials production, trained workers, and owner budget.
  • Consistency: The leveling of materials, information distribution, crew counts, equipment needs, and other resource needs throughout system and throughput time. Enables consistent and standardized work without overburdening of context switching, increased communication complexity, overproduction.
  • Continuity: The flow of work within a sequence in uninterrupted flow without efficiency gaps. When work is done on rhythm consistently with stable crew sizes and inventory levels, team is able to fully support flow.

These four stabilize work and allow processes to flow through construction. They also answer the question: why does Takt bring problems to the surface?

Why Takt Brings Problems to the Surface

Takt brings problems to the surface because stable rhythms, capacities, consistent workflows, and workflows with continuity occur. It shows what should be done (Takt) and stops trying to project or guess what will be done (CPM).

If you want to know you are off course, you have to know the correct course. If you simply compare your course with another possible course, then it becomes a matter of opinion. Only Takt maps out a scientific flow for the project through simulation. It shows the most ideal synchronous flow for all sequences working together.

When a work step within a work package does not meet that production rhythm, the team sees it as a deviation immediately and is able to correct it immediately with the smallest amount of latency or time delay.

When problems show up in CPM, it is seen as a deviation to the current path only. Therefore teams simply make another path by adjusting logic in a silo, then another one, and another one, and another one until the only remaining options result in a crash landing.

To see a problem you need the following things:

  • Know the target.
  • See the deviation where it is.
  • See the deviation in what it affects.
  • See the deviation within five to 48 hours of occurrence.

Only Takt does the following:

  • You can see the target clearly on a single page schedule.
  • Each Takt wagon with its work packages and work steps are tracked daily so you can see any deviations.
  • The Takt trains move with the deviation so you can see what happens to the system to maintain flow.
  • You are able to see this real time without waiting two weeks to update a schedule and hit F9 or run the forward and backward pass in CPM.

The Two Genius Elements of Takt

Here’s the genius of Takt:

First genius: It is visual and other scheduling systems are not yet in the long term. Takt is a great communication tool for the project team to see what needs to be done and when. If we can all see that, we can make decisions and collaborate with common knowledge and therefore act or head in the same direction together.

As Patrick Lencioni quoted in his book The Five Dysfunctions of a Team: “If you could get all the people in an organization rowing in the same direction, you could dominate any industry in any market against any competition at any time.”

This is what Takt planning does for us. Takt, along with Scrum and Last Planner, help us to move in the same direction by allowing us to see as a group, know as a group, and act as a group. Seeing the plan is powerful. This is the main reason Takt is better for the team.

The fact that Takt planning and Takt control brings problems to the surface faster in a visible way is the very reason it is better for the team. The team is able to see and fix problems as they go instead of responding to massive issues when it is or is almost too late.

This increases capacity by reducing the load on the team dealing with massive issues too late. Additionally, it improves morale. When the team feels helpless in overcoming or getting ahead of issues, the enjoyment and fulfillment is reduced on the project which decreases the productivity of the team.

Second genius: Takt planning and Takt control are easier systems to manage. It takes about one-twelfth of the time to manage a project with Takt as with CPM.

You can always tell the difference between a non-Takt project weekly work planning meeting and daily huddle meeting and a Takt-centered meeting system. In the non-Takt system, the team will be focused on when things should be happening and coordinating trades together within the week or day. In a Takt-centered system, the team already knows when things should be happening and then they focus on making work ready and removing roadblocks.

And the more work is made ready, the fewer problems there are to deal with. The truth is when project teams use CPM impaired with Last Planner, the team spends most of the time managing the schedule instead of making work ready. And when projects exceed sixty million dollars, the complexity of creating weekly work plans from scratch becomes too burdensome for the entire team and the system breaks down and causes more harm than good.

The only real way to create increased capacity for the team with scheduling is to implement Takt planning and Takt control and manage the deviations, not just the schedule.

The bottom line is that project teams must be balanced. They cannot be spending increased amounts of time managing a schedule and they need to have the capacity to prevent problems that will further reduce their capacity. This is the second major genius of the system. Once understood and created, it is easy to use.

The System Failed You

Let’s be clear. When teams don’t understand why Takt works, it’s not entirely their fault. The system failed by teaching CPM as standard without explaining that it guesses what will be done based on projections instead of showing what should be done based on capacity. Nobody showed that when problems show up in CPM, teams just make another path, then another, then another until only options remaining result in crash landing. Nobody explained that to see problems you need to know target, see deviation where it is, see what it affects, and see it within five to 48 hours. Only Takt does all four. The system taught react to problems when actually prevent problems beats react every time.

The system also failed by not teaching the railroad vs. river analogy. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. Rivers are reactionary planning you can’t control. Railroads are systems you create controlling your destiny. Don’t build boats when you can build trains. Takt is collaborative system predicting future and preparing for success instead of hoping for best in moment. But teams taught to react wonder why they’re always behind when the answer is they’re floating on rivers instead of building railroads.

The system fails by not teaching that rhythm is smooth and smooth is fast. Rushing takes longer than going at right rate. Decision isn’t between fast and early vs. rhythm and late. Decision is between fast and failing vs. rhythm and finishing soonest. Rushing creates chaos preventing flow extending duration. Rhythm creates stability enabling flow reducing duration. But teams taught to push wonder why pushing makes things worse when the answer is rhythm determined by capacity beats rushing beyond capacity every time.

The Challenge

Here’s your assignment. Stop building boats floating on rivers you can’t control. Start building trains and railways creating systems controlling your destiny.

Understand the decision. Not between going fast and finishing early vs. going at rhythm and finishing later. Between going fast and failing vs. going at right rhythm and finishing at soonest possible moment. Between going fast and finishing late vs. going at right rhythm and finishing on earliest possible date. Rhythm beats rushing.

Create the four considerations for flow. Rhythm (pace at which work completes). Capacity (rate at which resources can perform). Consistency (leveling of materials, information, crew counts, equipment). Continuity (flow without interruption). These stabilize work allowing processes to flow.

Bring problems to surface. Know the target (single page schedule showing it clearly). See deviations where they are (work packages tracked daily). See what deviations affect (trains move with deviation showing system impact). See deviations within five to 48 hours (real time not waiting two weeks to update). Only Takt does all four.

Use the two genius elements. First: visual enabling everyone to see as group, know as group, act as group. If you could get all people rowing in same direction, you could dominate any industry. Second: easy to use taking one-twelfth time to manage vs. CPM. Team focuses on making work ready and removing roadblocks instead of managing schedule.

Implement Takt creating collaborative system where you predict what should take place in future and prepare for success instead of hoping for best in moment. Create stability starting tasks on time, building right, finishing as you go. Just like train leaving station on time, driving right speed, having no accidents, arriving on time.

Rhythm is smooth and smooth is fast. Stop rushing. Start creating rhythm determined by capacity enabling flow.

On we go.

FAQ

What’s the railroad vs. river analogy?

River: reactionary planning you can’t control (most lean scheduling systems). Railroad: system you create controlling your destiny (Takt). Don’t build boats when you can build trains. Takt is collaborative system predicting future and preparing for success instead of hoping for best in moment.

What does “rhythm is smooth and smooth is fast” mean?

Rushing takes longer than going at right rate. Decision is between going fast and failing vs. going at right rhythm and finishing soonest. Rushing creates chaos preventing flow extending duration. Rhythm creates stability enabling flow reducing duration. Rhythm determined by capacity beats rushing beyond capacity.

What are the four considerations for flow?

Rhythm (pace at which work completes), capacity (rate resources can perform determined by local market), consistency (leveling of materials, information, crew counts, equipment), and continuity (flow without interruption). These stabilize work allowing processes to flow through construction.

Why does Takt bring problems to surface faster than CPM?

To see problem: know target, see deviation where it is, see what it affects, see within 5-48 hours. Takt does all four: single page showing target, work packages tracked daily, trains move with deviation showing impact, see real-time not waiting two weeks. CPM only shows deviation to current path, so teams make another path until crash landing.

What are the two genius elements of Takt?

First: visual enabling everyone to see as group, know as group, act as group. Gets all people rowing same direction. Second: easy to use taking 1/12 time to manage vs. CPM. Team focuses on making work ready and removing roadblocks instead of managing schedule.

 

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

Posted in All

CPM vs. Gantt vs. PERT vs. Takt vs. Pull Planning: The Complete Guide to Construction Scheduling Methods

Read 11 min

CPM vs. Gantt vs. PERT vs. Takt vs. Pull Planning: The Complete Guide to Construction Scheduling Methods

Walk onto five different jobsites and you will hear five different scheduling languages. One superintendent lives by the Gantt chart on the trailer wall. The project engineer is updating a P6 CPM schedule. A consultant is pushing PERT for a high-uncertainty phase. The Lean coach is running pull planning sessions with the trades. And somewhere, a Takt planner is moving crews through zones in perfect rhythm. Ninety-one percent of construction projects finish over schedule, over budget, or both. That is not primarily a labor problem. It is not a materials problem. More often than not, it is a scheduling problem specifically, the wrong scheduling method applied to the wrong situation.

The most important thing to understand before evaluating any individual method is this: your scheduling method shapes your behavior. A CPM-only schedule tends to create a push environment where work is shoved onto the next trade whether they are ready or not. A Gantt chart alone hides dependencies that cost weeks. A pull-planned schedule changes the conversation in the trailer. A Takt plan changes the flow of the entire jobsite. Choose poorly and you are fighting your own system. Choose well and the schedule starts doing the work for you.

Gantt Charts: The Display Format That Got Mistaken for a Method

Henry Gantt developed the horizontal bar chart in the early 1900s and it remains the most recognizable schedule format in the industry. Columns of time, bars of activity, positions showing start and finish any owner, architect, or field crew member can read it without training. For simple projects with limited interdependencies, a Gantt chart on the wall is often all that is needed for high-level communication and status reporting.

The breakdown happens when teams treat the Gantt chart as a scheduling methodology rather than a display format. A Gantt chart shows what and when. It does not show why. It does not tell you which tasks drive the end date, which have float, or what happens when one slips. On complex projects, a standalone Gantt chart is a picture of the plan not a tool for managing it. The important clarification: most modern schedules are displayed as Gantt charts but built using CPM, Takt, or another underlying methodology. The chart is the output. The method is the engine.

CPM: The Industry Standard With One Critical Flaw

Critical Path Method was developed in the late 1950s by DuPont and Remington Rand to manage plant shutdowns. It calculates the longest sequence of dependent activities through a project the critical path which determines the minimum possible project duration. Every activity gets a duration, predecessors and successors, early and late start and finish dates, and float. Activities on the critical path have zero float. Slip one, and the entire job slips.

CPM is essential for complex projects with clear dependencies infrastructure, industrial, high-rise construction, anywhere sequencing drives the outcome. It is the legal standard for delay claims and contractual requirements. Most public owners, major developers, and lenders require a CPM baseline. You cannot run a Time Impact Analysis without one.

The flaw is not in the method. It is in how it is applied. CPM schedules built in an office by someone who has never walked the site produce durations that have been massaged to make the end date work on paper. Industry audits routinely find that twenty to forty percent of activities in real-world CPM schedules have logic problems broken ties, open-ended activities, optimistic production rates. And the most fundamental limitation: CPM tells the field what should happen. It never asks the field whether they are actually ready. That gap is where projects fall apart.

PERT: The Right Tool for the Wrong Industry

The Program Evaluation and Review Technique was developed around the same time as CPM by the United States Navy for the Polaris missile program. It works almost identically to CPM with one key difference: instead of a single duration per activity, PERT uses three optimistic, most likely, and pessimistic weighted into an expected duration that accounts for uncertainty.

For research and development work, first-of-a-kind construction, or experimental facilities where crews genuinely cannot predict how long tasks will take, PERT is more honest than CPM’s single-point estimates. It naturally produces probability distributions for end dates rather than false precision. But for most construction where trades have established production rates and tasks repeat across similar conditions the three-point estimating adds effort without adding much accuracy. Monte Carlo risk analysis layered onto a CPM schedule has largely replaced pure PERT in modern practice. PERT is a specialized tool for genuinely high-uncertainty work, which is a smaller category in construction than most schedulers acknowledge.

Pull Planning: The Collaboration Layer CPM Was Missing

Pull planning is the scheduling engine behind the Last Planner System, developed by Glenn Ballard and Greg Howell. It inverts traditional scheduling entirely. Instead of pushing a master schedule down from a planner to the field, pull planning starts with a milestone and works backward with the last planners, the foremen and trade partners who will actually do the work, committing to what they can genuinely deliver.

The pull planning session gathers the team in front of a wall or a virtual board. Each trade writes their activities on sticky notes. Working backward from the milestone, trades place their activities in sequence and negotiate handoffs with the trades before and after them. Coordination conflicts, long durations, and missing predecessors surface immediately in the room, before they surface in the field at maximum cost. The output is a schedule that the people doing the work actually believe in because they built it.

Here are the conditions where pull planning produces its greatest value:

  • Complex MEP-heavy interior phases where handoff precision between trades determines whether the zone clears on time
  • Hospital renovations and occupied-building work where coordination failures have immediate operational consequences
  • Projects where trade trust has been low and commitments have not been honored pull planning makes commitments visible and peer-to-peer rather than imposed from above
  • Six-week and weekly planning cycles where short-interval reliability is the difference between flow and firefighting

Pull planning is the collaboration layer. It fixes CPM’s biggest structural weakness the field was never asked. It does not replace CPM for controls and claims purposes, and it requires skilled facilitation to produce genuine commitments rather than a sticky-note exercise.

Takt Planning: The Production System That Changes Everything

Takt time planning, borrowed from the Toyota Production System, is the closest thing construction has to a manufacturing-grade production system. The word Takt is German for rhythm or beat. The core idea is to divide the project into zones apartments, floors, bays, rooms and establish a fixed Takt time for crews to move through those zones in sequence. A framing crew spends one week in zone one, then moves to zone two while drywall enters zone one. Trades flow through the building in rhythm, handing off on time, every time, in one-process flow.

Where Takt planning transforms project performance is in repetitive work multifamily housing, hotels, hospitals, data centers, healthcare anywhere floors, rooms, or zones repeat in predictable configurations. Trades know exactly where they will be next week, next month, and the month after. Crew sizes level out. Material deliveries align to the rhythm. Supervision attention focuses on roadblock removal rather than daily firefighting. The production system does what CPM always promised but never delivered: predictable, on-time, on-budget execution.

The breakdown happens when Takt is applied without the pre-planning it requires. Takt does not tolerate scope creep or half-finished design. Trades accustomed to getting ahead on their own schedule must learn to work in rhythm with the trades around them. Superintendents and project managers must understand both the planning and the control discipline that keeps the Takt plan alive in the field which is why hands-on training with simulations and real-project application develops the capability that reading about Takt cannot.

The Layered System That Actually Works

Here is what the best schedulers will tell you: the question is not which method to use. The question is how to layer them correctly for the project at hand. The mistake teams make is picking one method and forcing every problem into it. CPM alone gives a legally defensible schedule that the field ignores. Takt alone gives beautiful flow that does not hold up in a claim. Pull planning alone gives excellent collaboration with no controls infrastructure. Each method answers a different question. The layered system answers all of them.

Here is what the layered system looks like on a well-run modern project:

  • CPM as the contractual baseline and controls backbone required for legal protection, delay analysis, and owner reporting
  • Takt planning as the production system driving daily and weekly field execution the engine that keeps trades flowing zone to zone
  • Pull planning at the six-week and weekly level to align trades, surface constraints, and build the commitments the Takt plan depends on
  • Gantt chart views for owner and stakeholder communication the display layer everyone can read
  • PERT-style three-point estimating on the handful of genuinely high-uncertainty activities where single-point estimates would be dishonest

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

Walk your next project and ask which scheduling language the field actually uses to make decisions and whether the controls team and the production team are looking at the same plan. If the answer reveals a gap, that gap is where schedule days are being lost. Build the layered system. Connect the planning to the production to the controls. The teams winning right now are not better at CPM they have built a complete production system that CPM alone was never designed to deliver. 

Edwards Deming said, “It does not matter when you start, so long as you begin today. Nothing is so good that it cannot be made better.”

On we go.

Frequently Asked Questions

What is the difference between a Gantt chart and CPM? A Gantt chart is a visual display format bars on a timeline. CPM is a methodology for calculating durations, dependencies, float, and the critical path. Most CPM schedules are displayed as Gantt charts, but the chart alone does not tell you which tasks are critical or what slippage costs.

Is Takt planning better than CPM?

They answer different questions and work best together. CPM is a controls and forecasting tool excellent for tracking, delay claims, and contractual requirements. Takt is a production system excellent for executing work in the field in stable, rhythmic flow. The best projects use both.

What is the difference between Takt planning and pull planning?

Pull planning is a collaborative sequencing technique where trades build the schedule backward from milestones, negotiating handoffs and surfacing conflicts before they reach the field. Takt planning is a production system that moves trades through defined zones in synchronized rhythm. They complement each other pull planning builds the logic, Takt establishes the flow.

Why do most CPM schedules not reflect what actually happens in the field?

Because they are typically built in an office with durations optimized to hit the end date rather than reflect actual production rates and the field was never asked whether the plan is achievable. Pull planning and Takt planning both fix this by involving the people doing the work in building the plan they will execute.

Do I need special software to run Takt planning?

No. Many teams start with a spreadsheet, a Miro board, or a physical wall with sticky notes. Software helps at scale, but the most important investment is in trained leadership superintendents and project managers who understand how to design the Takt plan and control it in the field.

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

Posted in All

Tips For Written Communication In Construction

Read 9 min

Written Communication in Construction: Seven Practices That Keep You Out of Trouble and In Flow

The legal counsel who came to do a training at Hensel Phelps made a joke that was not entirely a joke. If they could get rid of email entirely, they would because it gets companies in so much trouble. The examples they showed the room were not of fraud or malicious intent. They were superintendents writing things in an email that they never would have said the same way face to face. Frustrated tones. Dismissive phrasing. “Try again.” Words that looked fine in the heat of a difficult moment and looked catastrophic in a conference room or a courtroom.

That training delivered a principle that shapes everything about how written communication in construction should be approached: never write anything in an email or text that you would not feel comfortable saying in court. That single standard eliminates most of the written communication problems that construction teams create for themselves. It does not eliminate email. It changes what goes into it.

The Philosophy: Less Documentation, Done Better

There is a spectrum in how construction professionals approach documentation. At one end are the professional documenters everything goes in writing, every interaction becomes a record, every conversation spawns a follow-up email. At the other end are the teams that document almost nothing, relying on relationships and verbal communication to carry the project. Neither extreme serves the project or the people on it.

The right position is closer to the less documentation end but with a critical qualifier. Some things must be documented, and when they are, they must be done professionally, accurately, and completely. The documentation that exists on a well-run project is sharp. It is precise. It does exactly what it was designed to do and nothing else.

The principle for internal communication is direct: default to no email. Teams, WhatsApp, Asana, Monday, ClickUp, meetings, verbal, text whatever platform the team has standardized on for quick internal exchange. Fast, direct, low friction. If an email must be sent, it is external only. The belief that everything must be documented for legal protection is not entirely true and the defensive documentation spiral it produces often does more damage than it prevents.

What does deserve documentation? The trade partner preparation sequence: contract execution, pre-mobilization meetings, pre-construction meetings, follow-up inspections, final inspections, quality sign-offs. Anything that touches the contractual agreement, establishes expectations, or creates a record of shared understanding. These get documented well. Everything else gets communicated effectively.

Here is the diagnostic that reveals how a project is actually running: if the job is going well, there will be fewer RFIs, fewer reworked submittals, and less administrative overhead. The documentation that exists will be accurate and professional. A project drowning in defensive documentation has problems and the documentation is usually making those problems worse, not better.

Eight Practices for Written Communication That Actually Works

The first practice is knowing why something is going in writing before writing a word. Every written communication serves one of two purposes: to clearly communicate, or to clearly document from a risk standpoint. Both have legitimate value. Confusing them produces documents that do neither well communication written so defensively it fails to communicate, and documentation so casual it provides no protection. Know which one you are doing. Then do it cleanly.

The second practice is stating the purpose immediately. The first line of any written communication should tell the reader exactly what this document is and why it exists. “This email documents the installation requirements for the overhead MEP in zones three through six.” Or: “This email confirms the conditions needed for your crew to mobilize Monday morning.” The reader should know within five seconds what this is, why it was sent, and what they need to do with it. If they have to read three paragraphs to figure that out, the communication has already failed.

The third practice is maintaining tone discipline under all circumstances. Emotions do not belong in written construction communication. Not urgency, not frustration, not sarcasm none of it. AI tools are genuinely useful here. Draft the substance, use an AI assistant to check the tone, and send something that reads professionally regardless of how the situation feels. The test is not whether the email accurately reflects your frustration. The test is whether you would be comfortable reading it aloud in a formal setting.

The fourth practice is treating RFIs, submittals, and meeting minutes with the seriousness they carry. These documents have contractual weight. RFIs must be precise not vague requests that invite misinterpretation or that are actually doing design work that belongs elsewhere. Submittals must follow the proper process and must not become a vehicle for redesigning through the submittal cycle. Meeting minutes and daily reports must be accurate, complete, and written without language that would be damaging if read back to the people who were in the room.

These four practices address what to write and how to write it. The next four address the system around the writing.

The fifth practice is building communication around the goal of preventing claims, not winning arguments. The point is not to pin something on somebody. The point is to communicate so clearly and so early that there is nothing to pin. Ask of every written communication: is it effective? Is it visual? Is it clear? Is it accessible to the person who needs to act on it? Not: did I send it? Not: is it buried in one of thirty-five folders in the project management application? Is it working?

Here are the don’ts that consistently make written construction communication worse rather than better:

  • Emotional tone in any form it converts professional documentation into evidence of a broken culture
  • Vague language “can you put that wall up Tuesday?” communicates nothing, creates confusion, and generates the RFIs you were trying to avoid
  • Missing context assuming the recipient knows what you are referring to without establishing the reference produces misunderstandings that cost more time and money to unwind than the original communication would have taken to write clearly

The sixth practice which is closely related is understanding that the communication system on a construction project is its nervous system. Text, radio, meetings, field coordination, office alignment: when these channels are functioning, information reaches the right people at the right time in the right form. When they break down through adversarial documentation, siloed platforms, or teams that have stopped trusting each other enough to communicate directly the project loses the coordination it needs to flow.

A military principle applies directly: the first objective in defeating an enemy is to shut down their communications. Construction teams should not do this to themselves by turning their internal communication into a legal exercise. Embrace the communication system. Protect it. Make it strong enough that no disconnect is possible between the field and the office.

The seventh practice is establishing standard work for written communication. Set up templates for RFIs, meeting minutes, pre-mobilization documentation, and the other recurring written communication forms. Set those standards not just for yourself but for every person on the team. When the whole team writes from the same standards and the same habits, the quality of the documentation rises and the individual burden of producing it well falls.

Here are the signals that written communication is supporting the project rather than complicating it:

  • Every external email states its purpose in the first sentence
  • Internal communication flows through fast, direct tools rather than email chains
  • RFIs are clear, specific, and traceable back to a genuine information need
  • Meeting minutes and daily reports are accurate and professionally written
  • The team can locate every relevant document without hunting through multiple systems

Connecting to the Mission

The connection between written communication and production flow is direct and underappreciated. A project that generates fewer RFIs is a project where the design was coordinated, the trades were prepared, and the pre-construction process was done well. A project with professional, accurate meeting minutes is a project where decisions are made clearly and commitments are tracked honestly. Written communication is not a separate administrative function it is the information layer that either supports or undermines the production system running in the field.

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

Take thirty minutes this week and audit one category of written communication on your project RFIs, meeting minutes, or your internal email volume. Ask honestly: is this communication serving the project, or is it protecting individual positions? If it is the latter, the production system has a problem the documentation is hiding rather than solving. Find it. Fix the system. Reduce the paper.

Jason Schroeder said, “The goal is not to be excellent at documenting problems. The goal is to build systems good enough that the problems don’t happen.”

On we go.

Frequently Asked Questions

Why is the internal default for communication “no email” on a well-run project?

Because email is slow, creates adversarial documentation culture, and generates communication overhead that fast, direct tools eliminate. Internal communication needs to be immediate and frictionless. Email is for external communication and for formal documentation that needs to exist as a retrievable professional record.

What categories of communication always deserve formal documentation?

The trade partner preparation sequence: contracts, pre-mobilization meetings, pre-construction meetings, follow-up inspections, final inspections, and quality sign-offs. Anything that establishes contractual expectations or creates a record of shared understanding deserves to be documented professionally.

Why do projects with more documentation often have more problems?

A well-run project generates less documentation because the conditions that produce RFIs, change orders, and claims are being managed proactively through strong planning and clear communication.

What is the most damaging type of written communication error in construction?

Emotional tone. It converts professional documentation into evidence of a problematic culture, creates legal exposure, and damages the relationships that collaborative production depends on. Once it is in writing, it exists permanently, discoverably, and exactly as damaging in a conference room as it was intended in a frustrated moment.

How does standard work apply to written communication?

By establishing templates and consistent practices for recurring document types RFIs, meeting minutes, pre-mobilization checklists, daily reports so that every person on the team produces documents to the same quality standard.

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

Posted in All

The Takt Production System – Part 11

Read 13 min

Are You Implementing the Toyota Way or Just Talking About It?

You say you’re lean. You talk about respect for people. Continuous improvement. Flow. But you’re not implementing the 14 principles of the Toyota Way. Principle four says level out the workload, work like the tortoise not the hare. But you’re pushing hard, crashing schedules, working like the hare. Principle two says create continuous process flow to bring problems to the surface. But you’re using CPM creating chaos hiding problems until they explode. Principle three says use pull systems to avoid overproduction. But you’re pushing materials onto site based on projections and guesses creating excess inventory. Principle six says standardized tasks and processes are the foundation for continuous improvement. But you have no standard work, no rhythm, no predictable sequence. And here’s the realization Jason had reading these principles: there is no other system other than Takt that will implement these. There is no other system out there that adheres to these. You really can’t understand Takt planning until you understand these fundamental principles of the Toyota Way. Because Takt is how you actually implement them, not just talk about them.

Here’s what most teams miss. They learn lean concepts. Respect for people. Eight wastes. Stop call and wait principle. 3S for cleanliness and organization. Pull versus push. Just-in-time deliveries. And they try implementing them with CPM scheduling. But CPM fights every principle. It left justifies activities to early start dates instead of leveling workload. It pushes activities through network as fast as possible instead of pulling based on readiness. It creates chaos instead of continuous process flow. It hides problems in critical path instead of bringing them to surface. You can’t implement Toyota Way with CPM. You need Takt. Because Takt levels the workload creating rhythm. Creates continuous process flow bringing problems to surface. Uses pull systems avoiding overproduction. Standardizes tasks and processes as foundation for continuous improvement. Takt is the vehicle implementing Toyota Way in construction, not just discussing it.

The challenge is most teams think they’re lean when actually they’re just talking about lean while using systems preventing lean from working. They respect people in theory but put them in chaotic environments preventing them from doing good work. They want continuous improvement but don’t create stable environments with flow enabling teams to see and fix problems. They talk about total participation but don’t create visual systems showing everyone what winning looks like daily. They pursue quality but don’t build culture of stopping to fix problems to get quality right first time. The concepts sound good. But without Takt creating the stable foundation, they remain theory instead of practice. Takt turns lean concepts from aspirations into systems.

The Four Foundations of Lean in Construction

Everything starts with four foundations:

  • Respect for people and resources: Everything we do must align with highest standards of respect for people and psychological safety. Also respect for resources. Cannot be wasteful simply because we live in economy of abundance.
  • Stable environments with flow and culture that sees and fixes problems: Stable environments with standardization of flow are the only environments that will bring problems and issues to surface real time so teams can fix them, resolve them, and remove them.
  • Total participation with visual systems: Continuous improvement is only supported when entire project site is participating in lean culture and can see what winning looks like daily at their place of work.
  • Continuous improvement and fanatical quality: If respect, stability, and total participation are present in culture, project culture can begin efforts to continuously improve flow of supply chains, processes, and systems. Everyone sees and fixes problems every day.

These four foundations build on each other. Respect creates foundation. Stability enables seeing problems. Total participation engages everyone. Continuous improvement drives daily progress. Without all four, the system fails.

Flow Is the Single Most Important Condition

Flow is the single most important condition to strive for in construction. It is the most value-added effort on our journey to increase safety, customer delight, profits, employee satisfaction, and reduce production durations. We focus on three types of flow:

  • Workflow: The flow of work through areas without interruption.
  • Trade flow: The flow of trades through zones in predictable sequence.
  • Logistical flow: The flow of materials, information, and resources supporting work.

Enabling flow drives the most appropriate continuous improvement efforts. To do this we need to differentiate between resource efficiency versus flow efficiency:

  • Resource efficiency: Maximize use of individual resources and attach work to resources (people, equipment, crews, tools).
  • Flow efficiency: Focus on flow of product to customer or customer to their end goal and attach resources to flow units.

We always attempt to achieve both in harmony. In construction we utilize one process flow instead of one piece flow because the process flows through a stationary project site. As we optimize flow for areas and processes we need to optimize the bottlenecks.

A bottleneck is any resource whose capacity is equal to or less than the demand placed upon it by the entire system or a slowdown in flow of work. We look for and increase capacity of bottlenecks to improve flow. Once this is done, bottlenecks will show up in other locations and will become our new focus.

The Eight Wastes We Must Eliminate

We are looking for the eight wastes:

  • Overproduction.
  • Excess material inventory.
  • Transportation.
  • Motion.
  • Defects.
  • Overprocessing.
  • Waiting.
  • Not using wisdom or experience of team.

Overproduction and inventory are the mother and father of all wastes. Typically in construction when we overproduce, we have excess inventory which then needs to be transported and which causes excess motion. The distraction and process of moving inventory creates defects or allows us to ignore them. Defects then need to be fixed which causes overprocessing and that creates waiting and lost crew hours. It is all waste because we know better and could have worked as a team.

In addition to waste, we need to watch out for overburden and unevenness:

  • Overburden: When workers are made to work too fast or a floor is stocked with too much material or when project management team has to process too much paperwork. Occurs when a resource is utilized over 100% of its reasonable capacity.
  • Unevenness (Mura): Non-uniformity or irregularity in construction. Variation in flow of work or variation in resources available to do the work. Causes waste because it causes variation.

Stop, Call, and Wait Principle

This principle relies on four steps:

  • Discover an abnormality.
  • Stop the process.
  • Fix the immediate problem.
  • Investigate and solve the root cause.

We create environments where people and teams can see as a group, know as a group, and act as a group to see, stop, fix the problem, and prevent it in the future. We must see what winning looks like as we work.

3S: Creating Clean, Organized, Enjoyable Environments

3S is a standard practice all teams and crews perform daily:

  • Sort: Remove what is not needed.
  • Straighten: Organize what remains.
  • Sweep or shine: Clean your area in detail.

3S creates cleanliness, organization, and enjoyment. It results in ability to find and see problems so they can be fixed. We are able to observe these at the place of work. We do not focus on numbers and reports from a distance. We observe numbers and reports and observe at the place of work close to the work. We determine if we are winning as close to place of work as possible with total participation with people doing the work.

Pull vs. Push Systems

Pull is where we bring material onto the project when it is needed. It is based on demand. Push is where the material arrives based on projections and guesses. Pull prevents overproduction. Push creates excess inventory.

Just-in-time deliveries are a strategy synchronizing orders from suppliers by production areas and standard delivery schedules to project site in right amounts at right time to supply material inventory buffers. This is pull, not push.

The 14 Principles of the Toyota Way

We follow the following principles of the Toyota Way:

  • Base management decisions on long-term philosophy even at expense of short-term financial goals.
  • Create continuous process flow to bring problems to surface.
  • Use pull systems to avoid overproduction.
  • Level out the workload, work like the tortoise not the hare.
  • Build culture of stopping to fix problems to get quality right first time.
  • Standardized tasks and processes are foundation for continuous improvement and employee empowerment.
  • Use visual control so no problems are hidden.
  • Use only reliable, thoroughly tested technologies that serve your people and process.
  • Grow leaders who thoroughly understand the work, live the philosophy, and teach it to others.
  • Develop exceptional people and teams who follow your company’s philosophy.
  • Respect your extended network of partners and suppliers by challenging them and helping them improve.
  • Go and see for yourself to thoroughly understand the situation.
  • Make decisions slowly by consensus, thoroughly considering all options. Implement decisions rapidly.
  • Become learning organization through relentless reflection and continuous improvement.

Jason’s realization: There is no other system other than Takt that will implement these. There is no other system out there that adheres to these. Level out the workload, work like the tortoise not the hare. Build culture of stopping to fix problems. Use pull systems. Create continuous process flow. Standardize tasks. This is all Takt.

Workers Make the Money in Construction

Workers make the money in construction. They are the heroes. We optimize and stabilize their environment first. Information, materials, layout, quality expectations, equipment, permissions, and safety planning should be prioritized in steady flow to create safe, clean, organized, and productive environment for the worker.

We do not lose money while crews are working. We lose money when flow of work or crews are interrupted. Our focus should be on clearing the path for work to progress. We do not track production while crews are in flow. We track interruptions to flow and continuously improve to create more flow.

The System Failed You

Let’s be clear. When teams talk about lean but don’t implement it, it’s not entirely their fault. The system failed by teaching lean concepts without teaching the scheduling system enabling those concepts to work. Nobody showed that you can’t implement Toyota Way with CPM. Nobody explained that leveling workload requires Takt creating rhythm, not CPM left justifying to early start dates. Nobody demonstrated that continuous process flow bringing problems to surface requires stable environment Takt creates, not chaotic critical paths CPM generates. The system taught concepts without vehicles implementing them.

The system also failed by not teaching that overproduction and excess inventory are mother and father of all wastes. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. When you overproduce, you create excess inventory needing transportation causing motion creating defects requiring overprocessing producing waiting. The chain reaction starts with overproduction. But CPM encourages overproduction by pushing activities to early start dates. Takt prevents overproduction by pulling based on readiness and leveling workload. The system taught push when actually pull prevents the waste cascade.

The system fails by not teaching that workers are heroes we optimize for, not resources we maximize. Workers make the money in construction. We optimize and stabilize their environment first. But resource efficiency thinking maximizes utilization of workers instead of creating stable flow enabling them to work productively. Flow efficiency focuses on product flow to customer attaching resources to flow units. This respects workers by creating conditions enabling them to do good work instead of squeezing maximum utilization from them regardless of conditions. The system taught wrong efficiency metric preventing respect for people from becoming reality.

The Challenge

Here’s your assignment. Stop just talking about lean. Start implementing the 14 principles of the Toyota Way through Takt planning.

Level out the workload. Work like the tortoise not the hare. Use Takt creating rhythm and predictable pace instead of CPM pushing to early start dates creating chaos.

Create continuous process flow bringing problems to surface. Stable environments with standardization of flow bring problems to surface real time enabling teams to fix them. CPM hides problems in critical paths until they explode.

Use pull systems avoiding overproduction. Pull brings materials when needed based on demand. Push brings materials based on projections creating excess inventory. Just-in-time deliveries synchronized with production areas prevent overproduction.

Build culture of stopping to fix problems getting quality right first time. Stop call and wait principle: discover abnormality, stop the process, fix immediate problem, investigate and solve root cause. Create environments where teams see as group, know as group, act as group.

Standardize tasks and processes as foundation for continuous improvement. Takt creates standardized work with rhythm. Each Takt wagon has work packages. Each work package has work steps. This standardization enables improvement.

Implement 3S daily. Sort (remove what’s not needed). Straighten (organize what remains). Sweep (clean your area). Creates cleanliness, organization, and ability to see problems enabling fixing them.

Eliminate the eight wastes starting with overproduction and excess inventory. They are mother and father of all wastes creating transportation, motion, defects, overprocessing, waiting, and underutilizing team wisdom.

Respect workers by optimizing and stabilizing their environment first. Information, materials, layout, quality expectations, equipment, permissions, and safety in steady flow creating safe, clean, organized, productive environment. Workers are heroes making money in construction.

Track interruptions to flow, not production while in flow. We lose money when flow is interrupted, not while crews are working. Focus on clearing path for work to progress.

You really can’t understand Takt planning until you understand fundamental principles of Toyota Way. And you can’t implement Toyota Way without Takt. They go together.

On we go.

FAQ

Why is Takt the only system implementing the Toyota Way?

Principle four: level workload (Takt creates rhythm). Principle two: continuous process flow (Takt creates stable flow). Principle three: pull systems (Takt pulls based on readiness). Principle six: standardized tasks (Takt creates standardized work packages and steps). CPM fights these principles. Takt implements them.

What are the four foundations of lean in construction?

Respect for people and resources. Stable environments with flow and culture seeing and fixing problems. Total participation with visual systems showing what winning looks like daily. Continuous improvement and fanatical quality. These build on each other creating conditions enabling lean to work.

What are the eight wastes?

Overproduction, excess material inventory, transportation, motion, defects, overprocessing, waiting, and not using wisdom/experience of team. Overproduction and inventory are mother and father of all wastes. When you overproduce, you create excess inventory needing transportation causing motion creating defects requiring overprocessing producing waiting.

What’s the difference between pull and push?

Pull brings material when needed based on demand. Push brings material based on projections and guesses. Pull prevents overproduction. Push creates excess inventory. Just-in-time deliveries synchronized with production areas are pull. CPM pushing to early start dates is push.

What is the stop, call, and wait principle?

Four steps: discover abnormality, stop the process, fix immediate problem, investigate and solve root cause. Create environments where teams see as group, know as group, act as group to see, stop, fix problem, and prevent it in future. Requires culture valuing quality over speed.

 

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

Posted in All