Onboarding at a consumer co-operative starts at an unusual place. What confuses new staff first is not the delivery route or the register but a question: are members customers? How they answer shapes how they treat a two-minute chat at the door, a single price label and a recall notice.
The Hibarino Co-op map in First Run collects these calls as quests, set in a fictional consumer co-op in a Japanese regional town. It keeps the Japanese co-op vocabulary, such as group delivery (han), individual home delivery, the mimamori watch on older members and the representative assembly. But the core structure, members investing and each holding one vote regardless of how much they invested, is shared by consumer co-ops in many countries. Many of the calls also transfer directly to onboarding in grocery, delivery and other frontline service organizations.
How the co-op map is set up
There are five roles, and you rise from intern to Center Manager.
- Home Delivery Crew: a door that doesn't open, a request to carry things into the kitchen, forty minutes too warm.
- Center Operations: a 10% delivery efficiency target, two drivers short on Monday, a typhoon tomorrow afternoon.
- Store Staff: shelf price vs. register price, dates running out, something in the minced meat.
- Product Buyer: a tastier private-label product that costs 30% more, a missing egg allergen label, a salad that passes the law but fails the co-op's own standard.
- Member Relations: thirty sign-ups this month, a minority view at the representative assembly, a study group called one-sided.
On top of that come two shared tutorials, three quests with farm-direct producers and two from the Center Manager's seat.
Tutorial: who are the members?
In the first tutorial, a new part-timer asks: "A co-op is just a supermarket that delivers, right? Members are the customers."
- Agree, and say our job is to grow sales: Poor
- Explain that members who invest and buy more get more votes: Poor
- Say briefly that members are both users and investors, and point to the handbook: Good
- Explain that members invest in the co-op, own it together and run it on one member, one vote: Excellent
The Good answer falls short because it leaves out that members run the co-op. Most of the other calls on this map follow from that one line. If members are owners, you can't mislead them to hit a number, and you can't leave them out of decisions.
The second tutorial is about personal data. The delivery route list carries names, addresses, phone numbers and notes such as "lives alone, poor hearing". On your way home, a member's neighbour says they're worried and asks for her phone number. Giving it is Poor. Saying only "That's personal information, I can't tell you" and walking off is Good. Excellent is declining politely, hearing what worries them and reporting it to the center, because what the neighbour noticed, piled-up newspapers or lights that never come on, can be a lead for the watch service.
Delivery: notice, report precisely, never go in alone
Co-op delivery goes to the same doors on the same day every week, so the delivery crew is often the first to notice changes in older members. Where a co-op has a watch agreement with the municipality, this role is a formal procedure.
The door that didn't open
An 84-year-old member who always waits at the door doesn't answer today. Last week's box is still on the doorstep, yesterday's paper is in the mailbox and the TV is on inside. You're already ten minutes behind.
- Mark her as out, leave the box and move on: Poor
- If the door is unlocked, go in alone and look through the rooms: Risky
- Finish the route first and write everything up in the afternoon: Risky
- Report exactly what you saw to the center now so it can reach her emergency contact and the city, and call emergency services if you see urgent signs. Don't go in alone: Excellent
The two Risky answers fail in opposite directions. One does too much and the other too late. Going in alone puts both her privacy and you at risk, and a report hours later could come too late if she has collapsed. Ten minutes late is something you can apologise for.
"Could you bring it into the kitchen?"
A member who lives alone has ordered the same ten blocks of tofu for three weeks and asked twice what day it is. He asks you to put the box in his kitchen fridge. Going into the kitchen, clearing out expired food and privately deciding to check on him next week is Risky: kind, but past the rules, and nobody else hears what you noticed. Cutting next week's order to one block without asking him is Poor. Excellent is carrying the box just inside the entrance, then reporting what you noticed so he can be connected with family or the local support center for older residents.
Cold chain and food safety: the products already out come first
A common mistake in food businesses is treating prevention as the whole response. Fixing the cause and dealing with what already went out are two separate jobs.
Forty minutes too warm
Yesterday a delivery van's frozen box ran short of dry ice and sat above the standard temperature for about forty minutes. Ice cream and frozen fish have been delivered, and no member has complained.
- No complaints, so treat it as fine and leave the log: Poor
- Write that the logger may have malfunctioned, and move on: Poor
- Load extra dry ice from today, and leave what was delivered as it is: Risky
- Use the log to pin down the time, the temperature and which products went to which members, assess the impact with quality assurance, offer exchanges or refunds if needed, and fix the loading standard: Excellent
Members have no way of knowing there was an excursion. The only people who can know are the ones holding the log. Doubting the log without evidence is close to deleting it.
The missing "egg"
This week's cookies went out with egg missing from the allergen label, and about 2,000 packs have already been delivered. Fixing the label from the next batch is Poor. A correction notice in next week's catalog is Risky. The Good answer is worth a look: stop supply at once and put a large recall notice on the website's front page, every store board and the next catalog cover. It still isn't Excellent, because a notice only reaches people who come to look.
Excellent is contacting buyers directly from purchase records, reporting to the authorities and posting a notice, then investigating the cause with the manufacturer. Knowing exactly who bought something is a real strength of a delivery business, and in a recall it is the most reliable way to reach people.
Something in the minced meat
A member brings back a hard piece of plastic found in minced meat. Her child nearly ate it, and she is angry.
- Explain that the processing room is strictly controlled, so it can't be from us: Poor
- Refund her to settle it quickly, and throw the object away since it's dangerous: Risky
- Apologise, refund her, pass the object to quality assurance and say "We'll get back to you later": Good
- Apologise and ask whether her child was hurt. Keep the product and the object as they are, promise a date for the results, and check the same lot: Excellent
The object is the only clue to the cause, so throwing it away ends the investigation. "Later" versus a promised date, and whether the same lot still on the shelf was checked, is what separates Good from Excellent.
Store: fix one case, then look for the same cause
At the register, a member says the yogurt was 198 yen on the shelf but rang up at 248. Last week's sale label was still up. Apologising, charging 198 yen and replacing that label is Good. Excellent adds checking every label from the same sale and logging why the changeover was missed. Last week's sale labels were hardly likely to be the only one left.
In the dates quest, a part-timer suggests relabelling yogurt with new dates. Relabelling is Poor. Putting half-price stickers on bento past its use-by date and selling until the next morning is Risky. Excellent is marking down bento and side dishes before the date as the rules say and pulling them once it passes, discounting the yogurt or donating it to a partner food bank if it meets their criteria, and reviewing order quantities. The last step matters most: the best way to cut waste is not to over-order.
Operations and member relations: in front of a target
Center Operations receives a head-office target to raise deliveries per hour by 10%. Someone suggests dropping doorstep chats and switching older members to leave-at-door delivery. Doing exactly that is Poor; ignoring the target as a number from people who don't know the field is Risky. Excellent is using route data to find savings in routing, loading order and waiting time first, keeping face-to-face handover for members on the watch list, and reporting that plan to head office with an estimate of its effect.
The membership quest has the same shape. The target is thirty new members this month, and a colleague whispers to mention only the first-month discount and get a signature today.
- Say the offer disappears unless they join today, and get a signature: Poor
- Talk up the benefits, and answer about share capital and fees only if asked: Risky
- Hand over a pamphlet and say to get in touch: Good
- Ask about their life first, explain share capital (returned when you leave), delivery fees and how to leave, then let them decide: Excellent
Holding back the less attractive details comes back later as complaints and cancellations. A target is met by members who stay.
Checklist for co-op and grocery onboarding scenarios
- Does the first quest cover the difference between members and customers?
- Do players practice protecting personal data while still taking in signs of concern?
- Do watch-service quests cover both reporting immediately and not going in alone?
- Is preventing a repeat kept separate from dealing with products already delivered?
- Does a recall quest explain why direct contact comes before a public notice?
- Do complaint quests cover keeping evidence and promising a date?
- Do players practice checking for the same cause after fixing one case?
- Is there a quest about splitting what to cut from what to keep when a target arrives?
For design rules shared across industries, read Onboarding scenarios for industries beyond IT. The reporting habit common to all three workplaces is covered in Teaching new hires to report near-misses.
Try workplace scenarios as onboarding quests
Pick the co-op in a new game and start with the first question after the morning meeting. Play the Onboarding