What the Jobs That Went Wrong Are Trying to Tell You.

Every trade business has jobs that go wrong. Jobs that run 30% over budget. Jobs that generate callbacks. Jobs where the crew struggled and nobody is quite sure why.

Most companies handle these jobs the same way: they absorb the loss, have a brief conversation about what happened, and move on. The job is over. There are new jobs to worry about. Life continues.

The problem is that without a systematic process for learning from the jobs that went wrong, those jobs keep going wrong — the same way, on the same job types, with the same patterns that nobody ever examined closely enough to break.

Why the same bad jobs keep repeating

There are three reasons bad jobs repeat:

First, the debrief doesn't happen, or happens once and doesn't lead to anything actionable. The conversation is "that was a rough job" and then everyone moves on.

Second, the debrief focuses on blame rather than diagnosis. When the debrief is really about assigning fault, nobody tells you the real story of what happened. They tell you the version that minimizes their exposure. The actual cause — a bad estimate, a staging problem, an equipment issue — stays buried.

Third, even when the right lessons are identified, they don't get systematically applied to similar jobs going forward. The foreman on that job might adjust their approach, but the foreman on the next similar job doesn't know what happened.

Data vs. blame: how to structure the debrief that actually works

The key to a productive debrief is starting with data, not impressions. Pull up the Protiv job report before anyone says anything. Here's the estimate. Here's the actual hours. Here's where the variance occurred — which day, which phase of the job.

When the conversation starts with data, there's less room for competing narratives. The variance is a fact. The question becomes: what caused it? And that question can be answered systematically rather than defensively.

• Was the estimate wrong? If so, what assumption was incorrect?
• Was there a scope change that wasn't accounted for?
• Did the crew encounter something on site that wasn't anticipated?
• Was there a management issue — materials late, instructions unclear, equipment unavailable?
• Was it a crew execution issue — slow pace, quality problems that required rework?

The pattern analysis most companies skip

Individual job debriefs are valuable but limited. The real learning happens when you look across multiple jobs of the same type over a month or quarter.

Are your HVAC jobs consistently over budget on the second day of multi-day installs? That's a pattern. Are your painting jobs that include significant prep work coming in at a different margin than the pure coat jobs? That's a pattern. Is there one foreman whose jobs run tight and another whose jobs always seem to find surprises? That's a pattern too.

Performance data from Protiv makes this analysis straightforward — and it changes what you learn from it. You stop responding to individual job failures and start understanding systematic issues that, once fixed, improve your entire operation.

Turning findings into changes that actually stick

The output of a good debrief — or a pattern analysis — needs to be one specific, operational change. Not a general principle, not an admonition to do better. Something concrete: "We're adding material staging to the pre-job checklist for jobs over 16 hours" or "We're adjusting the estimate for drywall prep from 0.8 hours per sheet to 1.1 hours."

One concrete change, applied consistently to all future similar jobs, is worth more than a dozen general lessons that exist only in the debrief notes.