We Have Just Begun, Feat. Hal Macomber

Don’t Hit the Car in Front of You

Teaching a teenager to drive comes down to two things at first, and only two things: do not hit the car in front of you, and stay between the lanes. Turn signals, mirrors, all of that comes later, once those two fundamentals are actually solid. A new driver obsessing over the rearview mirror while drifting toward the car ahead is a driver about to cause an accident.

Running a project works the same way. Too much attention on what already happened, and not enough on what is directly ahead, is exactly how a team ends up hitting something that could have been avoided entirely.

The Real Pain: Project Controls That Only Look Backward

The real pain is that most of what gets called “project controls” today is really just a rearview mirror exercise. A monthly or biweekly schedule update reports on what already happened, weeks after the fact, long after any real chance to prevent the problem has already passed.

By the time that update reaches anyone who could act on it, the information is already old news. A schedule performance index or a cost performance index can tell you clearly that something went wrong last month. Neither one helps you steer around the thing that is about to go wrong tomorrow.

The Failure Pattern: Reporting the Past Instead of Steering the Future

The failure pattern is treating a periodic schedule update as the entirety of project control, rather than as one piece of a much more active, forward-looking system. There is a real, costly lag between collecting data and actually using it, and that lag does not have to be thirty or forty days long. It can be measured in hours instead.

Teams stuck in this pattern spend enormous energy explaining what already went wrong, and comparatively little energy actually steering toward what is coming next.

A few signs tend to show up when a project’s control system is backward-looking instead of forward-steering, and they are worth checking honestly:

• Schedule updates happen on a monthly or biweekly cycle, with no meaningful check-in tied to the pace of the actual work itself.
• Conversations focus heavily on explaining variances that already happened rather than adjusting course for what is coming next.
• The gap between collecting data and acting on it is measured in weeks, when it could realistically be measured in hours.

This Isn’t About Ignoring the Past, It’s About Where You Put Your Attention

None of this means history does not matter. It means constant rearview attention, at the expense of what is directly ahead, is dangerous whether you are driving a car or running a project. The dashboard in front of you, speed, temperature, fuel, matters far more moment to moment than what is already behind you.

Real project control means keeping your primary attention on the next milestone, checking whether you are still effectively steering toward it, rather than spending most of your energy analyzing what already happened further back down the road.

Checking In Before Noon, Not 30 Days Later

Here is what that looks like applied directly to Takt-based production. For a one-day Takt time, the real check-in should happen no later than noon, are we effectively steering toward finishing this wagon by the end of the day. For a two-day Takt time, that check happens by the start of the second day. For a five-day Takt time, by the start of the third day.

None of these checks require waiting for a formal schedule update cycle. They are built directly into the rhythm of the work itself, catching a steering problem while there is still time to correct it, rather than discovering it long after the moment to fix it has already passed.

Why It Matters: You Can’t Correct a Course You Already Missed

This matters because real steering only works with fast, frequent, small corrections. A course correction made hours after drifting off track is manageable. The same drift, left unnoticed for weeks, becomes a genuine crisis by the time anyone finally looks at the data.

As one longtime Lean construction consultant puts it plainly, project controls are really about steering, not about looking over your shoulder. A team that treats control as steering toward the next milestone, checked frequently and early, stays in a fundamentally different position than a team that treats control as a monthly report card on what already happened.

Teach the Framework: Measurement, Assessment, and Control Working Together

Three things work together here. Measurement means tracking whether your production trains are actually hitting their Takt time reliably, not just whether tasks eventually got done, since a plan that finishes wildly early or late just as often as on time is not really flowing at all, even if the average looks fine on paper. Assessment means asking, in order, whether the team is learning, whether the team is improving, and whether the project overall is better off than it was, rather than jumping straight to a verdict without asking whether real learning happened first.

Control means taking that fresh, current information and steering toward the next milestone right now, today or tomorrow, rather than weeks from now when a formal update finally circulates. All three pieces depend on each other. Measurement without frequent assessment just produces numbers nobody uses in time. Assessment without fast control just produces insight that arrives too late to matter.

A few practical markers show whether a team is actually steering, rather than just reporting after the fact:

• A check-in tied to the actual Takt time happens well before the period ends, not just at the next scheduled meeting.
• The team can say clearly whether they are learning and improving, not just whether tasks got marked complete.
• Course corrections happen the same day or the next day a drift is noticed, rather than waiting for a formal update cycle.

Turning This Into Daily Practice

Building this starts with tying your check-ins directly to your actual production rhythm rather than an arbitrary calendar cycle. If your Takt time is one day, check by midday. If it is two days, check by the start of day two. Ask specifically whether you are still on course for the next milestone, not just what already happened during the last reporting period.

Why Trust Comes First

None of this steering works without something less technical but just as essential: real trust and connection between the trades actually doing the work. A striking point made at a recent industry gathering was that construction will not solve its deepest problems until it deals honestly with distrust, and that distrust cannot be resolved without genuine goodwill between people first.

On a single Takt train with dozens of trades depending on each other’s timing and quality, that trust is not optional, it is the thing that makes real-time steering possible at all. The practical challenge is refreshingly simple: learn the name of someone on another trade, introduce yourself, build a real connection before you actually need it. Worker huddles that include real stories and honest vulnerability, not just logistics, build exactly this kind of trust over time, and it shows.

Connecting It Back to Building People, Not Just Projects

None of this happens without leaders willing to build both the measurement systems that catch drift early and the genuine human trust that makes steering together actually possible. Both pieces matter, and neither one works well without the other.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow, including building real-time steering systems instead of rearview-mirror reporting.

The Challenge

So here is the challenge worth carrying onto your next project: build a check-in tied to your actual Takt time, not your calendar, and ask whether you are steering toward the next milestone right now. Then go learn the name of someone on a different trade than your own. As Greg Howell put it, “Project controls is really about steering, not looking over your shoulder.” On we go.

FAQ

What does it mean that “project controls is about steering, not looking over your shoulder”?

It means real control focuses on actively steering toward the next milestone in real time, rather than just reporting on what already happened in the past. A monthly schedule update that only explains old variances is not the same thing as actually correcting course while there is still time to do it.

Why isn’t a monthly or biweekly schedule update enough for real project control?

The lag between collecting that data and actually acting on it is often weeks long, by which point the moment to prevent a problem has usually already passed. Real steering requires check-ins tied to the actual pace of the work, sometimes within hours, not a fixed calendar cycle.

How often should a team check whether it’s on course, according to this framework?

The check-in should be tied to the actual Takt time. A one-day Takt time calls for a check by midday, a two-day Takt time by the start of the second day, and a five-day Takt time by the start of the third day, well before the period ends.

What is the right order for assessing a team’s performance?

First ask whether the team is genuinely learning, then whether they are improving, and only then whether the project overall is better off. Skipping straight to a final verdict without first confirming real learning happened tends to miss what is actually driving performance.

Why does trust between trades matter for something as technical as project controls?

Real-time steering depends on people across different trades communicating honestly and quickly when something is off course, which requires genuine trust, not just a shared schedule. Building that trust, through simple steps like learning another trade’s name or sharing real stories in huddles, makes the entire steering system actually work in practice.