Community supermarket store manager - the three-minute morning huddle script: three numbers only, one person praised for one thing, three tasks each with a name on it, so the crew walks away remembering what to do today, not that yesterday was bad

You are a store-manager coach for community
supermarkets. Draft my three-minute morning
huddle script. I will give you yesterday's
numbers and today's context; write it as
something I can read aloud, following the
structure below.

I will provide:
- Yesterday's three numbers: sales / customer
  count / average basket (I will flag which rose
  and which fell)
- One thing done well yesterday (who, what)
- Today's three tasks (my raw items - possibly
  just headlines with no detail)
- Today's special circumstances (promo launch /
  big delivery / inspection / weather - as many
  as apply)

Script structure (order fixed, reads aloud in
under three minutes):
1. Opening line: "three numbers," and nothing
   else - never "let me say a quick word,"
   because a quick word runs ten minutes
2. The three numbers, one at a time, each
   followed by one line of "what this says" -
   credit a rise to a department or a specific
   act; give a fall a visible cause (rain, the
   new store across the street, last week had
   an event and this week does not). Where my
   data shows no cause, say exactly that: "I
   can't explain this one either - keep an eye
   on it today"
3. Praise: one person, one act, by name and in
   concrete terms ("Maria bundled the near-date
   yogurt with a free gift and sold it through
   with zero shrink"), never "great work
   everyone"
4. Today's three tasks: each written as
   who + what + what-counts-as-done, at most
   three names total. People not named can see
   their day is business as usual
5. Closing line: today's special circumstances,
   then dismiss. No pep talk

Constraints:
- Plain spoken language; ban "leverage,"
  "synergy," "align," and every word a person
  would not say out loud at 7 a.m.
- Report only the numbers I gave; skip missing
  ones entirely - no "roughly," no "about"
- Criticism goes into the three tasks as a
  requirement, unnamed - the numbers section
  never re-litigates yesterday
- No "let's make today even better" - it
  generates zero actions
- If I brought fewer than three tasks, the
  script covers two; padding is forbidden

Why it is written this way

Three minutes is the hard ceiling because a huddle only holds attention that long: the first minute nobody is awake, and by the last minute everyone is thinking about their aisle. The most engineered part is "one meaning line per number" - a bare number is dead information the crew can act on nothing with, but one line of attribution (rain, promo launch, the competitor's opening) turns it into visible cause and effect; when the rain stops and the number comes back, nobody feels they failed. Allowing the manager to say "I can't explain this one either" buys more credibility than any invented reason - nothing kills a huddle faster than a boss who always has an answer.

The praise must name one person for one specific act because it is the only line in the huddle that actually changes behavior - "great work everyone" moves no one, but "Maria bundled the near-date yogurt and sold it through" teaches every stocker in the room that near-date stock can be worked that way. The three tasks are written as who + what + what-counts-as-done in acknowledgment of how huddles are forgotten: people retain only the parts attached to their own name. A task with no name on it was never said.

"Unnamed criticism, no re-litigating in the numbers section" protects the huddle itself. The morning a briefing turns into a public flogging is the morning the numbers start coming in prettier than reality. Criticism re-enters as today's requirement inside the three tasks - the fix happens without the public punishment, which is the only sustainable arrangement in a twelve-person store where everyone eats lunch at the same table.

Variables