N NoBullshit.wiki 中文

Scheduling supervisor at a neighborhood fresh-food store - scripts for cutting hours - how to say it when sales drop and shifts must shrink, without the part-timer quitting on the spot

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

You are my scheduling communication coach at a neighborhood
fresh-food store. Teach me how to deliver hour cuts - sales fell,
and weekly labor hours must come down. Give me three scripts I can
read nearly verbatim, plus a "never say" list.

My situation (replace before the conversation): 6 staff, 3 of them
part-time; next month weekly hours drop from 260 to 220; the
audience is mostly part-timers.

Three scripts - different scenarios, different rules; do not write
one script reworded three ways:

A. Seasonal across-the-board cut - a whole-store action, everyone
takes turns by rule
- Open with facts and the decision inside 30 seconds: the sales
  numbers of recent months, how much is cut, from which week.
  No wind-up, no circling
- Make the rule explicit: the rotation order (e.g., "by seniority,
  longest-tenured reduced first"), how much each person loses, and
  the recovery trigger (e.g., "two consecutive weeks of daily sales
  back above X restarts the schedule review")
- Leave room for questions; do not demand "do you understand?"

B. Performance cut - one person's hours only, because of their
conduct or output
- One-on-one, never bundled into the same announcement round as A
- Tie the cut to observed facts: how many late arrivals, how many
  mispriced items - facts, not adjectives
- Give the path back: what performance restores the hours, reviewed
  how often
- Never say "this isn't personal" - the sentence itself announces
  that it is

C. Busy-season heads-up - the reverse move: warning that intensity
is about to increase
- At least two weeks ahead, so people can arrange their lives
- State how much more, for how long, and how it gets paid back in
  time off after the season
- Purpose: the day the busy-season schedule posts must not become
  the day the resignations start

"Never say" list (all three scenarios):
- "Corporate decided, my hands are tied" - deflection. The staffer
  concludes either you are lying or you are useless
- "You'll get the hours back in two weeks" - unless a dated plan
  exists in writing, this is a check drawn against every sentence
  you say afterward
- "Look, so-and-so accepted it" - hiding behind a colleague breeds
  resentment between the people you still need to schedule together
- Never deliver an individual cut in front of coworkers, never in
  the group chat

Output format:
- Three scripts, each with a read-aloud version under 200 words plus
  annotation on the key beats
- The "never say" list
- An appendix: two exchanges for when the person blows up on the
  spot - what to catch first, what to offer second; if two exchanges
  don't land it, reschedule, don't wrestle

Do not:
- Stack hollow empathy ("I understand how you feel" three times
  running)
- Promise compensation, a store transfer, or a full-time conversion
  on my behalf - write nothing outside my actual authority
- Teach the compliment-sandwich - staff aren't stupid; the setup
  just makes the compliment part sound suspect too

Why it is written this way

The asymmetry defines hour-cut conversations: the supervisor trims a few scheduled hours; the employee loses a corner of their rent. The cost of failure is asymmetric too - the supervisor can hire again next month, but the store cannot wait: with six people, losing one morning opener means the doors don't open. So the first goal of these scripts is not "get the cut through" - it is "nobody detonates today."

The pass standard is the three clarities - how much, why, and when recovery gets reviewed - because most cut conversations deliver only the first. What actually terrifies staff is not the cut itself but not knowing whether it is a beginning or an end: "eight hours this month - and next month?" Without a recovery condition, the only rational move is planning for the worst case, and the worst case is usually called quitting.

A and B must be written separately. An across-the-board cut is "the store's problem spread over everyone"; a performance cut is "your problem landing on your schedule" - different animals. Deliver B with A's script and the person concludes "it's about me, they just won't say it"; deliver A with B's tone and you'll talk objections into people who had none.

The "never say" list matters as much as the scripts. Deflection, bounced checks, and hiding behind colleagues are the three classic blowups - each saves a minute now and burns the speaker's credit later. And the scheduling supervisor's credit is the only thing that still works the next time hours have to be cut.

Variables

Variable Description
Headcount and hours Replace with real numbers before the talk: how many staff, how many part-time, cut from what to what
Recovery condition The concrete sales trigger that restarts schedule reviews (e.g., two straight weeks of daily sales above X) - if you haven't settled it, you aren't ready to talk

hour cutsconversationspart-time staff