Deal A3 — win-rate root cause analysis

A deal A3 is the same A3 — background, a Pareto-driven root cause chain, a tested countermeasure tracked against a TAGS metric — pointed at a sales problem instead of an operational one. The lean connection is direct, not decorative: a sales team that says "reps need to try harder" every quarter is doing exactly what a shop floor does when it blames operators instead of the process, and it fails for the same reason. A3 discipline forces the same question sales usually skips — what specifically, in the process, produces this pattern of losses — rather than settling for a vibe about the pipeline.

Background

State the pattern in plain terms and why it matters now — a win-rate trend, a segment, a deal source. One paragraph. If you can't say why this matters to the forecast in one paragraph, the pattern isn't bounded enough yet.

Problem statement

One or two sentences, separate from the background: the specific, bounded gap — which segment or source, what the win rate actually is versus its own standard. Not "we're losing too many deals."

Target · Actual · Gap · Standard

Standard is the win rate this segment has historically run at; Target is the goal you're committing to. Actual is a real time series pulled from the CRM, not a single quarter-end number — a trend is what tells you whether this is a blip or a pattern worth an RCA.

Pareto — where to look

Rank loss reasons from real CRM data, and choose the axis on purpose: ranking by count of deals lost is the most common way this misleads, because a handful of large deals lost to the same cause can matter more than a long tail of small ones. Dollar value of lost pipeline is usually the right axis for a forecast-driving RCA.

5-Whys — root cause

Start from the Pareto's vital-few loss category, not "we're losing deals" in general, and follow the strongest evidence — actual call notes, CRM stage history — at each step rather than the most convenient story. Stop when you reach something the process actually controls, not "the rep should have worked harder."

Countermeasures

Each countermeasure must trace to the stated root cause in the sales process — a stage gate, a script, a qualification requirement — not a general exhortation to sell better. Name an owner and a due date; a countermeasure with no owner doesn't happen in sales any more than it does on a shop floor.

Effect confirmation

Decide before you act which number moves first. A process change usually shows up in a leading indicator (stage conversion, a logged qualification field) before it shows up in win rate itself, which lags by a full sales cycle. Track both.

Follow-up actions

Capture what makes the fix stick — playbook updates, rep training, CRM field/stage-gate changes. This is what turns a good quarter into a durable process change instead of a one-time correction.

The example below is a full worked deal A3: a TAGS box and trend showing a real win-rate gap against its own historical standard; a Pareto over loss reasons weighted by lost pipeline value, not deal count — including a second-level stratification of the dominant loss category; a causal chain that ends in a specific, fixable gap in the qualification process rather than "reps need to try harder"; and countermeasures that each name the process gap they close.

• Root cause lands on "reps need to work harder" or "reps aren't following the playbook."

  Same failure mode as blaming operators on a shop floor — it's rarely wrong that more effort would help, and it's never actionable. Ask why the playbook wasn't followed, or why following it wasn't enough; that's usually a gap in the process itself, which is something a manager can actually fix.

• The Pareto is ranked by count of lost deals instead of lost pipeline value.

  A long tail of small lost deals can outnumber a handful of large ones without outweighing them — ranking by count routes attention to the wrong category. Choose the axis on purpose and say which one.

• Loss reasons come from the CRM's dropdown field, filled in from memory at deal-close time, not from the actual deal history.

  A rep closing out a deal under time pressure tends to pick the easiest plausible reason, not necessarily the real one. Where it matters, go back to call notes and CRM stage history rather than trusting the dropdown alone.

• Countermeasures are playbook-wide retraining with no link to the specific root cause.

  General retraining fixes the mood in the next sales meeting, not the process gap — and afterward there's no way to tell whether it actually moved the number that mattered.

• Win rate is tracked as a single number instead of a real time series with its own standard.

  One quarter-end percentage can't tell you if this is a new pattern or normal variation. The standard (historical baseline) is what makes the gap real instead of a guess.