Are You Finding Problems Before They Happen?

You create the plan. You think you’ve got it dialed in. And you present it to the team hoping they’ll accept it and move forward. But that’s not enough. You need fresh eyes. Outside perspectives. And you need to spend time just finding what could possibly go wrong with this before it actually happens. Put on your risk glasses. No compliments allowed. No sympathy votes. No positive feedback. Only problems. What will break this plan? Where will it fail? What haven’t we considered? Then brainstorm solutions linking problems to possible fixes. Then decide what to adjust. This creates a plan protecting your people, your team, your families, and the owner. Everyone has input. Everyone knows the plan together. Everyone expresses thoughts and concerns. There’s camaraderie. Everyone feels bought in. Because you found problems before they happened instead of discovering them when they break the project. Meanwhile, most teams skip this step. They create plans in isolation. Present them expecting acceptance. Then wonder why execution fails when the answer is they never found the problems early enough to fix them.

Here’s what most teams miss. Creating the Takt plan takes one week. Translating systems from CPM into systematic flow is fast when you understand the process. Identify preliminary Takt zones. Identify Takt sequences from historical information or pull planning. Create the Takt plan. Analyze throughput time with formulas. Insert buffers. Connect it with Last Planner system getting reliable tasks for weekly work plan. Each Takt wagon has work packages. Each work package has work steps. Transfer work steps to weekly work plan for collaboration and commitment from trades. For Scrum, move work steps to sprint backlog. The structure enables both systems to work. But the magic isn’t just creating the plan. It’s vetting the plan with fresh eyes finding every possible problem before execution begins. The Fresh Eyes meeting accomplishes in three hours what months of reactive problem-solving can’t accomplish. It surfaces issues early when they’re easy to fix instead of late when they’re expensive to solve.

The challenge is most teams think finding problems is negative. They want positive feedback. Compliment sandwiches. Sympathy votes. Being supportive. But that’s exactly what prevents finding real issues. You need to put on risk glasses deliberately looking for what could go wrong. Not to be pessimistic. To be prepared. The only stupid idea is the one nobody brings up. When you create safe space for finding problems, teams surface concerns they’d otherwise hide. They ask questions about procurement alignment, specialty room staging, commissioning detail, climate control timing, and dozens of other issues that would break the plan if not addressed. The Fresh Eyes meeting transforms plans from hopeful guesses into vetted strategies everyone understands and supports.

Creating the Plan in One Week

Brad and David created the Takt plan for OneCare in one week. It took only one week to translate their systems from CPM into systematic flow. The first steps were simple:

• Identify preliminary Takt zones.
• Identify Takt sequences (from historical information or pull planning).
• Create the Takt plan.
• Analyze the throughput time with formulas.
• Insert buffers.

The trick was connecting it with the Last Planner system and getting reliable tasks for weekly work plan in addition to new items. Brad soon realized this was easy with Takt because each Takt wagon had work packages in its composition. Each work package had work steps.

They used Excel for the first round with promise to upgrade once the system was stable. In Excel, the Takt plan at macro and norm level were shown in time scale. On the micro level, work steps were shown on separate tab categorized by work package. These were items transferred to weekly work plan and were easily listed there.

Brad saw how David could copy work steps within a work package and paste them into weekly work plan for collaboration and commitment from trades. For Scrum, work steps moved to sprint backlog to be moved to in progress and then to complete. Both formats worked.

How Takt Creates Stable Supply Chains

Brad asked: “You said Takt helps create stable supply chains for Last Planner and Scrum at the short interval level. Can you explain how that works?”

David: “This is the best part. First, the Excel procurement log is aligned with our rhythm per the Takt plan now, correct?”

Brad: “Correct, and now they are in the same document too which I like.”

David: “Second, the design, even before procurement, is leveled per our Takt plan. Are you following?”

Brad was happy to say he was. “So now we have design, submittals, fabrication, deliveries, information, equipment, coordination, contracts, and permits, all queuing up ahead of the work in a level chain of activities.”

This is the key. Stable supply chain means everything queues up ahead of work in level chain. Not chaotic. Not reactive. Predictable and systematic. Design leveled per Takt plan. Procurement aligned with rhythm. Deliveries, information, equipment, coordination, contracts, permits all flowing in synchronized sequence. This creates the predictable foundation enabling Last Planner and Scrum to work.

Make-Ready Work Steps Placed Weeks Ahead

David explains: “Each Takt wagon has work packages and work steps. The question is, how do we make sure the work in these work packages and Takt wagons is ready without roadblocks? The answer is that we do it with work steps.”

There are different categories of work steps. For instance, if there’s a work step with the title pre-construction meeting, you wouldn’t want to see it a day before the Takt wagon. Brad gets confused: “I get the procurement thing, but how do we plan the work if we’re not focused on that particular Takt wagon until the week of the actual work?”

David: “You’re right. We don’t start looking at the work just beforehand. It isn’t ever supposed to come as a surprise. We have to look at it before we come to it, weeks ahead in some cases. For the pre-construction meeting, for instance, we want that at least three weeks ahead or three Takt times ahead of the work, so we simply put that work step within the Takt wagon three weeks earlier than the meeting is scheduled.”

Brad gets it. “Oh, I see. So it’s like a pop-up reminder that goes off during the Takt wagon it’s inserted into, and then we look ahead to that Takt wagon and complete the work, and we keep popping up reminders as we go for inspections, RFIs, procurement, and so on.”

Exactly. The system creates visibility weeks ahead enabling proactive preparation instead of reactive scrambling.

The Fresh Eyes Meeting Structure

David announces when the appointed day arrived: “I love these meetings and I’m confident this one will be amazing.”

Olivia teases: “You think everything is amazing.”

David: “I know I do, but this time it’s warranted.”

He explains the structure. “We essentially have five parts to this meeting. The overview, poop glasses time, brainstorming, solutions, and finally action items and assignments.”

Brad: “What the hell did you say? Did you say poop?”

David: “I sure did. What’s the problem?”

Brad: “Well, generally, we use a more adult term.”

David laughs. “Well, generally, I would have to, but I’m working on not cussing and it’s the first thing that came to my mind.”

Brad: “David, you are amazing and this meeting is amazing, but you need to try again.”

David settles on “risk glasses.” The rules: “We’re not allowed to say nice things, provide compliment sandwiches, sympathy vote people, or be positive. We want to spend some time just finding what could possibly go wrong with this before it actually happens. We need to put on our risk glasses.”

Once they have all possible problems on the table and found all reasons why the plan won’t work, they go into brainstorming mode to link problems to possible solutions. Remember, they’re not deciding yet. Only putting down all ideas. The only stupid idea is the one no one brings up.

After that, they decide what to adjust on the Takt plan, logistics drawing, Takt zone and sequence drawings, and basis of schedule. Each action item gets an assignment tracked weekly.

The Critical Questions That Surface

The Fresh Eyes meeting surfaced dozens of critical questions that would have broken the plan if not addressed:

• Does the schedule have weather and schedule contingency?
• Have trade partners vetted their durations in some form?
• Has early or long lead procurement items been identified?
• Have we included mockups?
• Does exterior mockup trigger release of all materials or is it assembly mockup not performance mockup?
• Will field measurements be required before material is ordered?
• Have we accounted for procurement duration of owner-provided items?
• Is procurement strategically entered?
• Has the PM reviewed and confirmed durations and is it leveled for designers?
• Look at completion of exterior to interiors and ensure there are no comeback areas.
• Look at staging of elevator on Level 1 or basement.
• Can you go top down?
• Do we have plan for when permanent power will be turned on?
• Will there be need for temporary roof?
• Does flow incorporate specialty rooms properly?
• Ensure skin and roof are completed enough by time drywall and insulation starts.
• Is there some form of climate control functioning before high-end millwork is installed?
• Have we accounted for time for wood products to acclimatize to the building?
• Ensure commissioning is detailed enough at end of schedule.
• Is the path for turning power on built in the schedule?

Each item was assigned with due date affixed. The team would have all documents updated and ready to show to Jeff on Wednesday.

The Remarkable Outcome

The remarkable outcome of this meeting and process was that everyone had input and knew the plan together. Everyone was able to express thoughts and concerns. There was sense of camaraderie. Everyone felt bought in.

Meanwhile, Paul and Juan informed trades of upcoming changes in preparation for zero dollar change order that would contract them to new plan so everyone was aware and expected it before Wednesday. The team felt resolute in their new path.

This is the power of Fresh Eyes meetings. Not just creating plans. Vetting them collaboratively. Finding problems before they happen. Getting everyone’s input. Building buy-in through participation. Creating shared understanding enabling coordinated execution.

The System Failed You

Let’s be clear. When teams create plans in isolation and present them expecting acceptance, it’s not entirely their fault. The system failed by teaching that planning is expert work done by schedulers and presented to teams. Nobody showed that the best plans emerge from collaborative vetting finding problems before execution. Nobody explained that Fresh Eyes meetings accomplish in three hours what months of reactive problem-solving can’t accomplish. Nobody demonstrated that finding problems early is cheaper and faster than fixing them late. The system taught planning as individual expertise instead of collaborative process.

The system also failed by teaching that finding problems is negative. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. Teams want positive feedback, compliment sandwiches, sympathy votes. But that’s exactly what prevents surfacing real issues. Put on risk glasses deliberately looking for what could go wrong. Not to be pessimistic. To be prepared. The only stupid idea is the one nobody brings up. But teams never taught this keep hiding concerns until they break projects.

The system fails by not teaching the structure enabling Takt to work. Each Takt wagon has work packages. Each work package has work steps. Transfer work steps to weekly work plan for collaboration. Move them to sprint backlog for Scrum. Place make-ready work steps weeks ahead creating visibility enabling proactive preparation. Align procurement with rhythm. Level design per Takt plan. Create stable supply chain with everything queuing up ahead in level chain. But teams never taught this wonder why Last Planner and Scrum struggle when the answer is they lack the systematic foundation Takt provides.

The Challenge

Here’s your assignment. Stop creating plans in isolation. Start vetting them with fresh eyes finding problems before they happen.

Use the Fresh Eyes meeting structure. Overview, risk glasses time (no compliments, only problems), brainstorming solutions, deciding adjustments, action items and assignments. Create safe space for finding what could go wrong. The only stupid idea is the one nobody brings up.

Ask the critical questions. Does the schedule have contingency? Have trade partners vetted durations? Are long lead procurement items identified? Are mockups included? Will field measurements be required? Is climate control functioning before high-end finishes? Is commissioning detailed? Is the path to power and air on built in? Surface dozens of issues early when they’re easy to fix.

Create Takt plans in one week. Identify preliminary zones. Identify sequences from pull planning. Create the plan. Analyze throughput. Insert buffers. Connect with Last Planner getting reliable weekly work plan tasks. Each Takt wagon has work packages. Each work package has work steps. Transfer to weekly work plan or sprint backlog.

Place make-ready work steps weeks ahead. Pre-construction meetings three weeks before work. RFIs, procurement, inspections all queued systematically creating visibility enabling proactive preparation instead of reactive scrambling.

Create stable supply chains. Align procurement log with rhythm. Level design per Takt plan. Get design, submittals, fabrication, deliveries, information, equipment, coordination, contracts, permits all queuing up ahead in level chain. This gives Last Planner and Scrum the predictable foundation they need.

Get everyone’s input. Build buy-in through participation. Create shared understanding enabling coordinated execution. When everyone knows the plan together and feels bought in, execution succeeds.

On we go.

FAQ

How long does creating a Takt plan take?

One week to translate from CPM into systematic flow. Identify preliminary zones, identify sequences from pull planning, create the plan, analyze throughput with formulas, insert buffers, connect with Last Planner. Each Takt wagon has work packages with work steps that transfer to weekly work plan or sprint backlog.

What’s a Fresh Eyes meeting?

Collaborative vetting session with five parts: overview, risk glasses time (no compliments, only find problems), brainstorming solutions, deciding adjustments, action items and assignments. Creates safe space for finding what could go wrong before it happens. Surfaces dozens of critical issues early when they’re easy to fix.

How does Takt create stable supply chains?

Procurement log aligned with rhythm per Takt plan. Design leveled per Takt plan. Design, submittals, fabrication, deliveries, information, equipment, coordination, contracts, permits all queuing up ahead of work in level chain. Creates predictable foundation enabling Last Planner and Scrum to work.

What are make-ready work steps?

Work steps placed weeks ahead of when work happens. Pre-construction meetings three weeks before. RFIs, procurement, inspections queued systematically. Creates pop-up reminders during Takt wagons prompting team to look ahead and complete preparation. Enables proactive readiness instead of reactive scrambling.

Why is finding problems before they happen important?

Finding problems early when they’re easy to fix is cheaper and faster than fixing them late when they’re expensive. Fresh Eyes meetings surface issues about procurement, staging, specialty rooms, commissioning, climate control timing that would break projects if not addressed. Creates buy-in through participation and shared understanding.