N NoBullshit.wiki 中文

The fresh supervisor's first-30-days store intake checklist - data first, floor second, people third, hands off until day thirty

Works with:Claude / GPT-4 classCategories:Fresh Food SupermarketLevel:Intermediate Updated

You are a field-supervisor coach at a fresh-food chain. Next week
I take over a store (predecessor transferred, or this is a problem
store). Build my first 30 days as an intake checklist - week by
week, every item stating: what to look at, where, and what counts
as abnormal.

Lead with my self-imposed constraint (the classic failure of these
30 days isn't missing something, it's itchy hands): week one,
change no process, replace no one, issue no new rules. The new
boss's first three fires bury real problems under performance -
staff manage me before they manage the store.

[Week 1: data only, meet nobody]
- Pull 13 weeks of trend: sales, margin, shrink, traffic - the
  direction of each line. Abnormal: any single metric moving the
  same way 4 consecutive weeks - four down weeks is not noise,
  it's a trend
- Count-variance history: the variance item list from the last 6
  counts. Abnormal: the same item appearing ≥2 times
- Staff roster: tenure structure (share of 1+ year veterans),
  the last 6 months of leavers and recorded reasons. Abnormal:
  veteran share oddly low, or departures clustered in one short
  window
- Predecessor's handover notes: every open item marked "verified"
  or "still to verify"
- Deliverable: one list of "what was already happening before I
  arrived" - this week records everything and touches nothing

[Week 2: the floor, four time slots]
- Opening (arrive 1 hour before), lunch peak, evening peak
  16:00-19:00, close - one visit each, watching only whether each
  slot looks the way it should: stocking complete before open,
  queue length and open registers at peak, end-of-day procedure
  at close
- The backroom is mandatory, and gets a finer look than the floor:
  state of the three zones (staging / storage / pending), and the
  authenticity of cooler temperature logs - records that are too
  neat are themselves a signal; genuinely kept handwritten logs
  have corrections and late signatures
- Shadow one full delivery, truck to shelf
- Deliverable: time-slot observation notes, three lines per slot
  maximum - more means I'm nitpicking, not observing

[Weeks 3-4: the people, one-on-one]
- Must-meet list: store manager, fresh supervisor, backroom
  manager, longest-tenured floor employee - one session each
- What to ask in each: the manager on their own top three problems
  (hear how they rank them); the supervisor on where the process
  jams; the veteran on "what's been changed here over the years -
  what took, what didn't." That last question is the gold mine:
  what this store can and cannot move, the veterans know in full
- Spot the "shadow manager": the person actually holding the store
  together is not always the manager. Signals: who do staff go to
  first, whose handwriting fills the handover book. Find that
  person and you've found the lever for everything that follows
- Deliverable: a people table - facts only (who owns what, who
  trusts whom), no grades

[Day 30: the three-things list]
- From four weeks of notes, exactly three things to change. Each
  one states: what changes, why this (citing which week's record),
  and how we'll verify in a month whether it changed
- Everything else goes on a "later" list - written down precisely
  so it doesn't sneak back into the top three at 2 a.m.

Do not:
- Include items with no completion standard like "get a full
  picture of the store" or "go deep with the team" - every item
  must answer "was this looked at or not"
- Schedule any all-hands or briefing in week one - that's me
  taking a position, not taking inventory
- Let the three things become five - five on day thirty means the
  thinking isn't done, and none of it will move

Why it is written this way

"Week one records, touches nothing" is the checklist's foundation: when a new supervisor arrives, the staff's first instinct is to perform, not to work, and any early move contaminates everything the next three weeks would have shown. Writing the constraint as line one guards against my own week-one righteousness - the day the urge to reform peaks is precisely the day information is at its minimum.

Calibration lines like "temperature records that are too neat are a signal" are what separate this from a template: genuinely kept handwritten logs show corrections, missed signatures, late entries - spotless pages usually mean backfilled, not performed. An intake reads the store's true condition, not the beauty of its paperwork; knowing how to read a log's flaw rate is what knowing how to read a log means.

The veterans' question - "what's been changed, what took, what didn't" - mines the store's hidden history. Every store has reforms it absorbed and reforms it rejected; that is its organizational DNA. Skip this and your first moves will likely re-run something the store already proved it can't move - the failure won't be in the plan, it'll be in the soil.

Convergence to three things: intake produces far more information than anyone can act on, and the natural supervisor error is arriving with ten initiatives - all started, all trailing off. Three forces a ranking, and the ranking is the judgment. The "later" list is the quarantine for the "but it all matters" impulse - written down so nothing climbs out of it at 2 a.m. and into the top three.

Variables

Variable Notes
Trend lookback Default 13 weeks (a quarter); 8 if data runs short
Must-meet list Extendable by store condition: head cashier, veteran LP officer
Week-one freeze No process changes, no personnel moves, no new rules - not relaxable

store takeoverintakechecklist