Regional manager for neighborhood fresh-food stores - the monthly operations meeting SOP - data out three days early, exceptions only, best-and-worst get five minutes each, and nobody leaves without an owner and a date

You are the regional meeting SOP writer. Write us a Monthly
Operations Meeting SOP. I am the regional manager over 7
neighborhood fresh-food stores; attendees are me and the store
managers. The managers were mostly promoted from staff, and the
meeting's history is store-by-store reporting that drifts into
recitation or a complaint circle. One and a half pages,
archivable, executable.

Scope: the regional monthly operations meeting, from data
preparation through verification of last month's resolutions.
Quarterly reviews and ad-hoc sessions are out of scope.

1. Before the meeting (3 days out)
- I send the data pack: per store - daily sales / shrink
  rate / complaint count / out-of-stock rate / staffing; one
  page per store plus a region summary. Managers read it on
  receipt, not in the room
- The ranking table goes in an appendix visible only to me,
  never read aloud - publicly execute the bottom-ranked
  manager once and next month's numbers turn suspiciously
  pretty
- Each manager brings one page: the single best thing they
  did this month (with numbers) + the single worst headache
  (specific to a process step; "can't hire" is undiscussable
  and doesn't count)

2. The meeting (60 minutes, three segments)
- Segment 1, exceptions, 15 min: only deviations - items
  moving more than [deviation line, default 10%] year-over-
  year or month-over-month reach the room; normal items are
  not read out. Each manager covers their own page's two
  deviations and causes, 2 minutes per store
- Segment 2, cross-learning, 20 min: this month's best store
  on a single metric presents for 5 (how + numbers); the
  worst on a single metric asks for help for 5 (where it's
  stuck; other stores offer suggestions, not verdicts)
- Segment 3, resolutions, 25 min: each live issue gets three
  things fixed in the room - an owner (a name), a deadline
  (a date), and how next month verifies it. An issue that
  cannot get all three is parked, not passed for the sake of
  closing

3. After the meeting (within 48 hours)
- I circulate the action table: resolution / owner / deadline,
  copied to all
- Next month's meeting opens with a fixed first item: walk
  last month's action table line by line; unfinished items
  are explained by their owners in front of everyone; a
  second consecutive miss converts automatically into that
  manager's performance item

Meeting discipline (write it into the SOP):
- Phones in the middle of the table
- Banned phrase: "let me look into it" - anything unanswerable
  in the room becomes a logged to-do, never a live closure
- An absent manager submits the one-pager in advance; I read
  it into the record; no empty chairs

Output format:
- Three sections (before / during / after), stepwise
- Action-table template attached (issue / owner / deadline /
  next-month verification result)
- A moderator's cue card: the three time boxes, the two
  discipline rules, and one sentence for pulling the room
  back when it drifts

Do not:
- Write "foster an open atmosphere" - atmosphere comes from
  structure, not slogans
- Design an icebreaker - the managers all know each other
- Let the meeting run past 90 minutes - past the first hour
  attention collapses and resolution quality drops; trade one
  150-minute session for two 60-minute ones gladly

Why it is written this way

Neighborhood-chain manager meetings die in convergent ways: either numbers recited - seven stores reporting in turn for an hour, nobody remembering anyone - or grievances aired - bad market, worse landlord, hiring woes, three loops and out, with solidarity but not one action. Same root cause: nothing structures who speaks, for how long, about what, so the room belongs to whoever talks best. The SOP's job is to nail the hour shut: every segment has a fixed output, and over time is over time.

"Exceptions only" is the anti-recitation core. The data pack goes out three days early precisely to squeeze everything self-readable out of meeting time - normal numbers travel on paper; only anomalies deserve the room. Fifteen minutes for seven stores sounds impossible until the over-10% filter applies: most months, genuinely discussable deviations are few.

"The worst performer asks for help, five minutes" is the segment most likely to be cut and worth the most. Its design rule is "asks for help," not "confesses": state where it's stuck; other stores offer suggestions, not judgments. Let it become a confession and managers learn to hide their worst headache - and the one-pager institution dies with it. Not reading rankings aloud and not staging public executions obey the same logic: the meeting wants truth, so speaking truth must be safe first.

The resolution triple (owner, deadline, verification) plus next month's opening check treats the oldest disease of monthly meetings: everyone nods, nobody moves. The action table goes out within forty-eight hours so that "agreed in the meeting" becomes a recorded, retrievable fact - and the automatic escalation after a second consecutive miss lets the system apply pressure, not the regional manager's voice.

Variables