§4.6
Visual Decision Brief Studio
Part II has taught a visual vocabulary — baselines and indexes, small multiples, uncertainty intervals, statistical charts, and the dashboard as a decision system. This studio is where that vocabulary stops being a gallery of chart types and becomes a single executive artifact. You will take the Progresso soup case that ran through Chapters 3 and 4 — the countercyclical pattern where soup demand collapses in summer while price drifts up — and assemble its scattered visuals into one thing a category manager can act on: a visual decision brief that ends in a pricing question, not another chart. The data is the same retail-scanner panel you have already seen indexed and faceted; the new skill is sequencing those views into an argument.
The decision the visuals have to earn
The board does not want a dashboard. It wants an answer to one question: should Progresso investigate whether its soup prices are countercyclical — moving against demand in a way that may be leaving margin on the table or pushing volume away in the wrong season? That is a pricing question, and Part II cannot answer it. What Part II can do is build the visual case that the question is worth a pricing test — and, just as importantly, mark the line the charts cannot cross into causal claims.
The brief is built in six moves. Each one is a chart or a sentence you already know how to make; the studio discipline is doing them in order, so the page reads as a decision and not as an inventory.
Decision question
DeliverableThis brief asks whether Progresso should investigate a pricing policy that appears to raise price when seasonal soup demand is weak. The decision is not an immediate price cut; it is whether the pattern deserves a pricing test or deeper causal analysis.
Artifact to produce
One sentence naming lever, outcome, unit, and time.
Evidence standard
Names the lever as price, the outcome as volume/share, the unit as store-month, and the season window as winter versus non-winter.
Red flag: The brief starts with a dashboard screenshot instead of a pricing question.
Limit to name: A broad statement about seasonality is not enough; the brief must name the possible managerial action.
How the brief is graded
Soup case anchored
Students reuse one business setting while learning multiple chart forms.
Comparison visible
The eye can see season, region, brand, and price-volume contrasts.
Limits named
The dashboard does not turn descriptive evidence into causal proof.
Next test clear
The brief hands off naturally to pricing, regression, and causal chapters.
Show the pattern, then name the comparison
A brief that opens with a screenshot of every panel has already lost the reader. The two panels below are the spine of the argument: an indexed seasonality line that makes the countercyclical pattern legible, and the one comparison the brief turns on — winter versus the rest of the year. Switch the metric and watch volume and share collapse out of season while price climbs. The storyboard is deliberately unfinished: the panels are real, but the one-sentence finding is yours to write, because committing to a sentence is what separates a brief from a gallery.
Storyboard panel · fill the metric and the finding
Which metric carries the seasonal argument?
Limit to keep next to this panel: a volume index gap is descriptive. It shows the seasonal pattern; it does not prove that price caused the volume move. That claim needs the pricing test named in the brief.
Notice what the indexed view buys you. In raw cases-sold, the soup numbers are too large to compare against price at all; indexed to January, volume, share, and price land on one scale and the scissors open in plain sight — demand at roughly a fifth of its winter level by June, price up by nearly half. That is the baseline-and-index move from Chapter 4.1 doing exactly the job it was built for: making a comparison visible that the raw units hide.
What good looks like
The deliverable is a one-page visual brief plus the panels it points to. It opens with the pricing question, walks the six moves above in order, and closes with the single sentence a manager can act on — investigate this pattern with a pricing test, not cut prices now. Both the page and the panels should be readable in under three minutes by someone who has not seen the scanner data. The temptation in a visual studio is to show every chart form Part II taught; the discipline is to show only the views the pricing question needs, each one answering a named comparison and handing off to the next.