『Two Weeks, Not Two Months: Onboarding a Cellar Hand』のカバーアート

Two Weeks, Not Two Months: Onboarding a Cellar Hand

Two Weeks, Not Two Months: Onboarding a Cellar Hand

無料で聴く

ポッドキャストの詳細を見る

【Amazonプライム会員限定】今ならプレミアムプランが4か月 月額99円。

10月19日まで。※適用条件あり

Two weeks, not two months: about $2,900 a hire lost in the gap between week three and week eight. Mac and Wren argue over why a new cellar person takes two months before they can be left alone with a transfer — what "trained" even means ("can do it unsupervised and will stop when something is off"), why the confident untrained person is the expensive one, and why the thing Mac calls judgment is mostly a list he never wrote down. Mac concedes it: thirty people's worth of the list, all in his head. Tie-in (verified against code 2026-10-09): the onboarding checklist with due dates, per-employee training records (forklift, hazmat, first aid, food safety) with due dates and completion status, and every batch stage change logged as a written, timestamped sequence on the batch. SOP storage killed in verification — no customer-facing SOP feature exists in the brewery product, so the script claims nothing about one. Ask BrewBuddy (real question, real account, whatever it says is what you hear): "Are there any training records or certifications on file for the team at FermentIQ Brewery?" — captured 2026-10-09 on org 11 (Playground Brewery, is_test=true), site context "FermentIQ Brewery" single-site via the site switcher, browser task with the saved bot login, ask #2 of 3 (ask #1, "What onboarding tasks are open for the team right now?", deflected — no tool lists onboarding checklist tasks). The answer is a truthful deflection: no training records or certifications confirmed on file, no safety standards tracked on the capture org. No customer names in the answer (nothing to anonymize). Per the runbook deflection rule, the tie-in is not strengthened by the capture: the Hot Side beat claims only the code-verified mechanism, and the post-INSERT beat answers the empty record honestly ("On this site it lives where it lives at most breweries. In people's heads."). Dry Hops: have the new person write the procedure as they learn it — the gaps in their draft are the gaps in your training. And let them make the safe mistakes early and on purpose — everybody remembers the mistake they made; nobody remembers the mistake they watched you make. Last Call: write down the CIP sequence for one tank, start to finish, and hand it to somebody who has never done it. If they can follow it without asking you a question, you wrote a procedure. If they can't, you wrote a reminder — to yourself. Cold Side is from FermentIQ — built by a brewer, fifteen years on the floor, no engineering background, who directed AI coding agents to build the ERP he couldn't buy. It runs the whole operation, grain to glass. The first thirty days are free and you can cancel anytime at ferment-iq.com.

adbl_web_anon_alc_button_suppression_t1
まだレビューはありません