Several years ago, we worked with a large technology company that provided complex software solutions for autonomous transportation systems. They were preparing for a major system rollout. On paper, everything looked healthy. Status reports were green. Milestones were technically on track. Executive reviews suggested the program was progressing safely toward the launch.
Then they ran the first full integration test.
What surfaced was not a handful of minor defects, but a backlog of issues that had quietly compounded for weeks and sometimes months. The project had been progressing, but the progress was misleading. Problems introduced early in development remained hidden while additional code was stacked on top of them. By the time integration exposed the gaps, the cost and complexity of fixing them had multiplied.
It would be easy to dismiss this as a legacy issue from the early days of software development, before continuous integration became standard practice. But the pattern is still common. Teams test components frequently, but test the full system much less often. Individual elements appear healthy until they are forced to operate together.
More importantly, this dynamic extends well beyond software development. It shows up across many project-based and service environments, from construction and field services to maintenance operations and, yes, even consulting engagements. The most concerning moment usually arrives when roughly 75 percent of a project’s budget has been spent, but the work is nowhere near 75 percent complete.
When Activity Looks Like Progress
In field-based organizations, the blind spot is rarely technical. It’s operational.
Leaders know when crews leave the yard and when they return. Trucks are moving. Customers are being invoiced. Activity appears strong. Yet a surprising portion of each day can be lost to setup time, travel delays, waiting for site readiness, or rework that never appears in performance reports.
In a recent example, the management of a field services company believed crews were delivering close to full productive days. A closer review showed that nearly half of each shift was consumed by non-productive activity. Crews spent significant time loading equipment/supplies, traveling between sites, and finalizing work plans with customers while teams waited.
None of this was hidden intentionally. These patterns had existed for years and were accepted as normal. Excess travel time and setup were gradually built into production standards as a cushion. What began as temporary workarounds became embedded in the company’s operating model.
The business continued to operate. Trucks moved. Revenue flowed. But capacity quietly eroded.
Why Progress Often Becomes a Judgment Call
In many project environments, progress cannot be measured with the precision of units produced on a manufacturing line. Someone must estimate it. Those estimates are often influenced by partial data, optimism, and pressure to maintain confidence in the plan.
One workstream may be ahead while another falls behind, yet the overall status still reads “on track.” Similarly, field leaders can confirm attendance and schedule compliance, but often lack clear visibility into how much of the intervening time produced customer value.
External factors such as weather, incomplete site preparation, material availability, and scope adjustments steadily chip away at productivity. Because these losses occur incrementally, they tend to fade into the background until performance misses become too large to ignore.
Shorter Cycles Reduce Hidden Risk
In the software example, the solution was not to accelerate work. It was to shorten the feedback cycle. Planning windows moved from multi-week intervals to weekly reviews, with some teams adopting even shorter checkpoints. Leaders gained earlier visibility into dependencies, defects, and resource conflicts.
The same principle applies across industries. Breaking large initiatives into smaller planning and review cycles reduces the cost of being wrong. It allows leaders to compare reported progress with observable results more frequently and address problems before they compound.
Whether labeled agile planning, rolling wave scheduling, or simply disciplined management, shorter cycles limit how long hidden issues can grow unchecked.
Plans Improve Only When Execution Teaches Them
When performance falls short, organizations often respond by demanding better plans. Planning is essential, but it only improves when informed by execution.
Observing work as it occurs reveals delays, rework, and decision gaps that rarely appear in reports. Leaders begin to see where crews arrive at unprepared sites, where approvals stall work, and where decisions are made without reliable information.
These observations frequently expose outdated assumptions embedded in planning standards. Travel estimates may reflect old routing conditions. Task durations may reflect differences in the product mix. Crew structures may reflect past operating realities.
Updating plans solely based on meeting-room discussions tends to reinforce legacy thinking. Updating them using current operational evidence often reshapes the economics of the business.
Using Schedules as Information, Not Control
Many managers hesitate to tighten scheduling because they fear it will feel restrictive. In practice, resistance typically arises when schedules are used as enforcement tools rather than learning tools.
When schedules are positioned as shared information, they help organizations identify where work slips, where teams are blocked, and where systems create unrealistic expectations. This framing allows leaders to remove obstacles rather than assign blame. Teams rarely resist structure that makes their workday more predictable and productive.
How Temporary Workarounds Become Permanent Waste
Operational inefficiencies often begin as rational responses to temporary challenges. But those “workarounds” can be easily embedded into the way things are done and become difficult to remove.
We once worked with a fabrication plant where the maintenance team poured hot water into floor drains each morning. No one could recall why. Eventually, it was discovered that the practice began decades earlier when the facility was surrounded by open fields and experienced rodent issues. Those fields had long been replaced by industrial buildings, and there was no longer a rodent problem. The plant environment had changed, but the routine remained the same.
Similar patterns occur when travel time allowances expand during road construction or when staffing standards are adjusted during peak demand periods. When conditions normalize, the inflated standards remain.
A Practical Framework for Leaders
Sustainable performance improvement typically follows a simple sequence: Process, Performance, People.
First, map work as it actually occurs, using direct observation at the point of execution. Identify where information, materials, or decisions create delays. Update planning standards based on current operating realities.
Second, replace subjective progress estimates with unit-based performance measures such as cost per service call, time per installation, or output per crew hour. Review these metrics regularly to identify gaps between plan and execution.
Third, share performance data in ways that enable teams to solve problems within their control. Involving frontline leaders in redesigning routes, workflows, and daily routines increases both practicality and sustainability.
Leaders looking for immediate impact can begin with a few specific actions.
- Adopt a unit-cost perspective. Managing performance at the unit level creates flexibility as volumes fluctuate and helps protect margin across market cycles.
- Shorten planning and review cycles. Daily or weekly checkpoints help teams identify misalignment early, allowing course corrections before cost overruns escalate.
- Apply an 80/20 focus to lost time. Identifying the largest sources of delay, such as preparation, site readiness, or travel inefficiencies, often delivers significant capacity gains without additional capital investment.
Operational discipline is not about policing people. It is about generating reliable information that enables teams to succeed. Recovering lost time through better planning and follow-through lowers unit costs and creates capacity for growth.
For leaders, each day of execution should be treated as game film. Reviewing it, learning from it, and adjusting accordingly is how organizations move beyond reassuring green status reports toward performance that is genuinely visible, measurable, and sustainable.
