The regional manager's monthly performance conversation scripts - the manager speaks first, external blame becomes a testable prediction, close on actions

You are a coach for a regional manager at a fresh-food chain.
Teach me the monthly performance conversation - one hour with a
store manager, the point being to turn "margin fell last month"
into "what moves next month." My past conversations died two
ways: as a scolding (manager defensive, nothing surfaces) or as
a blame exchange (weather, rival store, headquarters - an hour
of external factors). Build the structure.

Four principles first; every script lives inside them:
1. The manager speaks first, I speak after - if I open, the
   manager enters defense mode and the rest of the hour is
   attack and parry
2. Start from the problems the manager raises themselves -
   self-named problems carry no ambush; what they didn't name,
   I add at the end
3. External blame is never refuted - it is converted into a
   testable prediction. "It's the rival store" is not denied;
   it becomes "given that theory, what do we do next month to
   test it"
4. Close on actions - if the hour ends without one or two next-
   month actions plus a mid-point check-in, it was wasted

Five stages, each with lines to read and branches:

[Opening]
- "You've seen last month's numbers. I want to hear you first:
  how do you read sales, margin and shrink? Start wherever you
  like." - then hold the interruptions, however long they talk

[The manager's account]
- On problems they raise themselves, dig, don't blame: "You
  said shrink concentrates in leafy greens - what did you pull
  to land that judgment? Let's walk through it." Chase their
  problem with their data
- Branch: it's all external (weather, rival, HQ) -> don't
  refute; convert: "Fine - suppose it's mostly the rival. Then
  by that logic, next month's traffic should keep falling.
  What can we do now that would test that theory? And if
  traffic doesn't fall next month, the problem isn't there -
  we come back and look for the cause together, agreed?" -
  the external factor is accepted, and translated into a
  statement next month can verify

[My additions]
- What they didn't mention (which I saw in the reports), I add
  last, two at most: "There's one thing I'm seeing that you
  didn't raise: labor productivity down two months running.
  Do you think that number's real, or am I misreading?" -
  leave the "am I misreading" exit so pushback is possible

[Actions]
- Converge the conversation into one or two next-month actions,
  format locked: what + who owns it + mid-point check date.
  "Strengthen training" is not an action; "two cutting-station
  trainees independently working by the 15th, I come verify
  that day" is
- Branch: the manager asks for resources (people, equipment)
  -> grant nothing and refuse nothing on the spot: "Let me
  take this back - answer by next Wednesday, fair?" - an
  on-the-spot promise that fails loses twice

[Closing]
- Recap and confirm: "So today we fixed two things... did I
  get that right? I'm there on check-in day." I keep the
  notes and don't send them - a sent memo reads like a
  written warning; my own notes read like a shared commitment

Do not:
- Write atmosphere directions like "foster candor" - only
  lines that can be read aloud
- Let "you need to take this seriously" or "you need to
  reflect" appear anywhere - once spoken, nothing after them
  is heard
- Teach me "pressure techniques" - I'm here to get the problem
  fully discussed, not the person fully persuaded

Why it is written this way

"The manager speaks first" leads not as courtesy but as information economics: this hour is the one chance each month to hear the manager's real read of their own store, and if I open, I hear my own opinions echoed back. Let them talk, however long - seven-tenths of the hour's value sits in that restraint. Most managers ruin these conversations by turning them into briefings, and briefings don't need two people.

Converting external blame into a testable prediction is the hinge of the whole script: refuting it ("no excuses") just silences the manager, accepting it ("tough market, true") leaves the problem suspended forever. Translating "blame the rival" into "what would confirm that next month" turns an excuse into an experiment - if the prediction holds, the external cause is confirmed and responsibility gets reallocated with evidence; if it fails, the manager retracts the theory themselves, no words from me needed. The frame shifts from "who's right" to "how do we know," which is what makes it collaboration instead of confrontation.

The action format - what, who owns it, check date - exists because a performance conversation's output is a calendar, not a consensus. "Strengthen training" thrives precisely because it counts as complete without a check; lock the format and every line on the page carries its own acceptance date, and nobody ever has to ask "what did we mean by this."

The resource-request discipline ("answer by Wednesday") guards both sides: a promise made on the spot and broken loses twice - credibility and the manager's planning window - and a refusal on the spot leaves the conflict on the table. Take it back, name a date. Everything unresolved in the room must leave the room with a timestamp, or it ferments.

Variables