Progress Models: Snapshots Masquerading as Stories

Deconstruction Series: 4

Progress models hit you with instant credibility. Side-by-side views, color-coded deltas, before-and-after flythroughs—they look clinical, objective, undeniable. Change leaps off the screen in red and green; progress feels quantified, proven, ready for the monthly report or the claims meeting.

They’re not.

What you’re actually looking at is a carefully curated comparison between two frozen instants—two drone flights, two laser scans, two discrete captures separated by days, weeks, or months. Everything that happened in the invisible middle—the frantic weekend pour, the temporary access reroute, the material staging shuffle, the weather delay that shifted sequencing—never makes it into the record. Those moments are erased the instant the second capture ends. The model doesn’t preserve sequence; it manufactures narrative from subtraction.

Alignment between the two datasets is never perfect. Small registration errors compound across large sites: a few centimeters of drift here, a mismatched GCP there, and suddenly a wall appears to have “moved,” a stockpile looks inflated, or an area seems untouched when it was heavily trafficked. Coverage inconsistencies amplify the deception—shadows or occlusions in one flight vanish in the next, making change appear where none occurred, or hiding real work entirely. Yet the visualization stays pristine. The software forces visual harmony, overlays snap into place, and the brain fills in continuity that was never documented.

That’s the trap: the model looks continuous, so we assume the progress was linear and fully observed. But continuity isn’t captured—it’s assumed. Progress models are not time machines; they’re binary snapshots with a fancy diff tool. They show difference, not evolution. They reveal that something changed between Point A and Point B, but they remain silent on how, when, or why.

And silence matters when the stakes are high. Schedule validation, payment applications, delay claims, stakeholder reporting—these decisions lean heavily on progress models as “proof.” If the unseen interval hides acceleration, rework, safety issues, or critical path deviations, the narrative you’re selling (or defending) is incomplete at best, misleading at worst.

What This Means Going Forward

Progress models are powerful communication tools. They cut through complexity, spotlight broad advancement, and help teams align quickly on the big picture. Embrace them for general awareness, visual reporting, and spotting macro-level shifts.

But never confuse snapshot comparison with temporal truth. Be ruthless when precision or sequence is on the line:

• Precise reconstruction of events or causation

• Forensic dispute analysis

• Verification of exact conditions at exact dates

• High-stakes claims or litigation support

In those moments, the real question flips from “What changed between these two models?” to “What happened between these two captures—and how do we prove it?”

Because true progress isn’t defined by what two models agree looks different. It’s defined by the unbroken chain of events on the ground. If that chain isn’t documented through consistent, frequent, controlled captures—or supplemented with timestamps, daily logs, video, or ground surveys—the story you’re telling is only half-written.

And half a story, no matter how polished the visuals, is a liability waiting to surface.

THE FLYING LIZARD®

Aviation-Driven Drone Intelligence™

         Where People and Data Take Flight™