Module 7: Diagnosing a Miss

Why This Module Matters

Modules 1 through 6 built the full KPI vocabulary and the dashboard that displays it. This module is where that vocabulary earns its keep: when the dashboard shows a sales miss, what specific sequence of questions actually isolates the cause, rather than a manager guessing at the first plausible explanation and coaching the wrong behavior for a month. The core insight this module is built on is simple and powerful: sales decomposes cleanly into traffic multiplied by conversion multiplied by average transaction value, and a genuine diagnosis works through that decomposition in order rather than jumping straight to a conclusion.

The Sales Equation, and Why Order Matters

Sales equals traffic times conversion rate times average transaction value (which itself splits into UPT times average item price). This isn’t a new formula — it’s the same vocabulary this course built across Modules 1 through 4 — but the diagnostic discipline this module adds is a specific, sequential decision tree: compare traffic and conversion against the same period last year or the prior stable baseline first, before looking at anything else, because the answer at this first branch determines which entirely different set of follow-up questions applies next.

Branch One: Traffic Down, Conversion Holding

If traffic is down and conversion is flat or normal, the store itself is performing fine on the people who did arrive — the problem sits outside the store, in the catchment or the marketing that brings people to the door. The specific follow-up question that separates two different problems here: is passing traffic down (a location, marketing, or seasonal catchment question), or is passing traffic steady while capture rate — the share of passersby who actually walk in — has dropped (a storefront, window display, or entrance-appeal question)? These are genuinely different problems with different owners and different fixes, and treating them as the same issue wastes the specific corrective action each one actually needs.

Branch Two: Traffic Holding, Conversion Down

If traffic is holding steady but conversion has dropped, something changed inside the store, and the specific recommended approach is to work the internal funnel in order rather than guessing: did the store’s layout or a relocated category change how customers move through it, did in-store engagement (trying on, testing, asking for a demonstration) drop, did checkout lines lengthen, or did staffing coverage during the store’s actual peak hours fall short? This branch connects directly to earlier course content: a conversion drop with steady traffic is exactly the scenario Module 2’s foot-traffic-vs-conversion distinction was built to help a manager isolate, and Module 6’s dashboard should already be tracking conversion separately from traffic specifically so this branch is quick to identify.

Branch Three: Both Down

When both traffic and conversion are down together, the specific warning this module carries is important: treat the traffic problem first, but check staffing immediately, because the instinctive response to falling traffic — cutting scheduled hours to control labor cost — further depresses conversion and accelerates the exact decline a manager is trying to stop. This is a genuinely counterintuitive trap: the natural cost-control reaction to a traffic problem actively worsens the conversion half of the same problem, compounding a bad month into a worse one.

Branch Four: Neither Down, But Sales Down

If neither traffic nor conversion has fallen, but total sales still missed plan, the problem isn’t whether people buy — it’s what they buy. This points directly to Module 3’s ATV/UPT/mix content: pricing, product mix shifts, or attachment/add-on rates are the remaining suspects, and Module 3’s specific mix-versus-behavior distinction becomes the exact tool needed to isolate which of these three is actually driving the miss.

The Full Driver Tree: Beyond Traffic and Conversion

A more complete diagnostic framework breaks a sales variance into eight potential drivers: traffic, conversion, basket size, price, mix, availability (stock-outs on what customers actually wanted), promotion effects, and returns. This module’s four-branch decision tree above handles the traffic and conversion drivers directly and points toward basket/price/mix for the fourth branch, but availability, promotion, and returns deserve explicit mention as drivers a manager should rule out before concluding a miss is purely a selling-behavior problem: a genuinely well-run floor can still miss plan badly if the specific pieces customers wanted were out of stock, or if a planned promotion underperformed, or if an unusual spike in returns quietly erased what looked like a strong sales week.

A Structured Sequence for Any Diagnosis

Beyond the specific sales decision tree, a more general five-step diagnostic sequence applies to any KPI variance, not just a sales miss: first, define the variance clearly (how much, compared to what baseline); second, locate where it occurred (which category, which day-part, which associate, which week); third, decompose the variance into its specific drivers; fourth, test the likely root causes against actual data rather than assumption; and fifth, define the corrective action, its owner, and its timing. This general sequence is what a manager applies to a shrinkage-rate miss, a retention miss, or a GMROI miss just as readily as a sales miss — the specific decision tree in this module is the sales-specific version of this same general discipline.

Putting the Vocabulary to Work

The practical manager habit this module recommends: the moment the weekly dashboard from Module 6 flags a sales variance, don’t discuss it in the weekly meeting until traffic and conversion have both been checked against the prior baseline first. That single check immediately narrows the conversation to one of the four specific branches above, each with its own follow-up questions and likely owners, rather than an open-ended, unstructured discussion where everyone offers a different guess about what went wrong.

A Worked Scenario: The Miss That Looked Like a Traffic Problem

A store misses its weekly sales plan by 12 percent, and the initial instinct in the team meeting is to blame slow foot traffic during a rainy week. Checking the dashboard shows traffic actually held steady against the same week last year — the real move was in conversion, which dropped from a typical 13 percent to 9 percent. Working the internal funnel in order reveals the specific cause: a new part-time hire was scheduled alone during the store’s Saturday afternoon peak, the exact window this store’s traffic data shows as its highest-volume period, and coverage during that specific window collapsed to a single, still-training associate. The fix isn’t a traffic-generating marketing push; it’s adjusting next week’s schedule to ensure peak-hour coverage matches the traffic pattern Module 6’s dashboard already tracks.

Practice Exercise

Take your store’s most recent weekly sales miss (or, if no recent miss exists, a deliberately slower week) and run it through this module’s four-branch decision tree: check traffic and conversion against the same period last year first, identify which branch applies, and work through that branch’s specific follow-up questions. Write down the specific corrective action, its owner, and its timing before the next weekly dashboard meeting.

Key Takeaways

• Sales decomposes into traffic × conversion × average transaction value, and a genuine diagnosis checks traffic and conversion against a prior baseline first, since the answer at that first branch determines an entirely different set of follow-up questions.
• Traffic down with conversion holding points outside the store (catchment, marketing, or storefront capture); traffic holding with conversion down points inside the store (layout, engagement, checkout, or peak-hour staffing).
• When both traffic and conversion are down together, the instinctive response of cutting scheduled hours to control labor cost actively worsens conversion further and accelerates the decline — this is a genuine trap worth naming explicitly.
• When neither traffic nor conversion has fallen but sales still missed plan, the problem is what people buy, not whether they buy — pointing directly to Module 3’s ATV/UPT/mix content and its mix-versus-behavior distinction.
• Availability (stock-outs), promotion underperformance, and unusual returns spikes are additional drivers worth explicitly ruling out before concluding a miss is purely a selling-behavior problem, and the general five-step diagnostic sequence (define, locate, decompose, test, act) applies to any KPI variance, not just sales.