The spine of this program is one metric: Time-to-Productivity (TTP) — days until a new receiver handles chilled loads solo at quality parity with veterans.
Baseline: 41 days (median of last 3 cohorts, measured retroactively from scan-log + error data). Target: 26 days.
Every phase below states which TTP driver it attacks. The four drivers: knowledge fluency · environment navigation · confidence · error-recovery. A week that cannot name its driver does not belong in this program.
Phase 1 — Dock-ready (d1–5) · drivers: confidence + environment navigation
Objective: survive week 1 oriented, not overwhelmed. The cold, the noise and the pace of the dock are the first thing that kills onboarding (see failure mode 1) — so week 1 is designed as orientation therapy, not content delivery.
- d1: Kit 1 explainer (90-second dock scene) before first dock entry. Safety zones, 2–8 °C band, the 30-minute dock-door rule.
- d2: Kit 1 module started (self-paced, diagnostic only — no gate pressure yet).
- d3: first supervised physical task: unload one pallet with the buddy. An early physical win beats a week of watching.
- d4–5: scan-gun basics drills; module attempt 1 allowed (diagnostic).
- Assets: Kit 1 explainer + module, full-time buddy (same shift pattern), day-3 win design.
- Assessment gate (d5): name the 4 receiving gates + diagnostic module attempt. No stakes — this gate measures the program, not the person.
- TTP contribution: baseline orientation took ~9 scattered days; compressed to 5 by front-loading the explainer.
- Drop-risk monitored: dock-shock signals (silence at huddle, late returns from break), scan-gun avoidance. Buddy logs both.
Phase 2 — Supervised flows (d6–20) · drivers: knowledge fluency + error-recovery
Objective: run full receiving flows with the buddy within arm's reach, and learn to fail loudly.
- Full-flow reps with buddy present; buddy steps back to observer from d12.
- 3 rehearsed borderline cases per week from the 12-case card deck (pre-briefed, then debriefed) — this is the direct counter to failure mode 2 (certified but frozen).
- The no-blame recovery ritual starts d6: flag → log → fix → debrief. The shift lead publicly logs their own error in week 1 — the ritual is only believed if leadership goes first.
- Shift lead takes one coached flow per week from d10 (buddy relief + leadership visibility).
- Assets: Kit 1 module (certification attempts now scheduled, not ad-hoc — what changed since Kit 1), borderline-case card deck, error log.
- Assessment gate (d20): flow audit — one full incoming load handled with ≤1 prompted intervention. Audit scores system entries as well as physical handling (failure mode 4).
- TTP contribution: module pass by d18 for ≥80% of the cohort (baseline median was d27).
- Drop-risk monitored: silent errors (scan-log vs. error-log audit weekly), paperwork drift (>15-min entry lag).
Phase 3 — Solo-with-net (d21–35) · drivers: confidence + knowledge fluency
Objective: solo work with a radio, not a shadow — and the program's formal checkpoint.
- Solo handling of chilled loads; buddy reachable by radio only.
- First unscripted borderline call expected around d23–25 — the call-the-lead script card (laminated at every scan station) makes asking for help a scripted move, not an admission.
- d28: Kit 1 module final certification must be passed (≥85%, 21 decision points).
- d30 skills gate: practical 4-gate run + 3 scenario questions, scored jointly by shift lead + L&D. This is the go/no-go of the whole program.
- Assets: Kit 1 module (final cert), call-the-lead script card, d30 gate instrument.
- Assessment gate (d30): skills gate pass. Intervention trigger: cohort pass-rate <80% → buddy-hours +50% for that cohort (see measurement framework).
- TTP contribution: solo error-rate tracked from d31; target is inside the veteran band (≤2.1 errors/100 lines) by d35.
- Drop-risk monitored: borderline freeze (failure mode 2's second wave — now without the buddy beside you).
Phase 4 — Full parity (d36–41) · driver: confidence
Objective: the net comes off, and TTP day is recorded, not assumed.
- Buddy released; normal rotation, normal quotas.
- Error-recovery without prompting: the flag → log → fix → debrief loop runs unaided.
- TTP day is logged the moment two consecutive shifts sit at veteran-band error rate — confirmed from the dashboard by shift lead + L&D (two independent sign-offs; no vibes-based parity).
- Assets: solo error-rate dashboard (daily, vs. veteran band), parity sign-off form.
- Assessment gate: two consecutive shifts at veteran band → TTP day logged. Target d26, ceiling d41.
- TTP contribution: this is the metric. Median days-to-parity per cohort: baseline 41 → target 26.
- Drop-risk monitored: confirmation drift (parity signed on anecdote instead of dashboard data).
Phase 5 — Growth track (d42–90) · all four drivers — the retention engine
Objective: hold people past the danger window. Parity is not the finish line; a receiver who reaches parity and then plateaus is a quit waiting to happen (failure mode 5).
- d42–56: cross-dock rotation — two weeks in outbound + cross-dock flows.
- d55: borderline-case masterclass — the 12 hardest cases from the incident log, run as a facilitated clinic by shift leads.
- d75+: mentor eligibility — parity receivers start shadowing as buddy candidates (structured, observed, feedback-fed).
- d90: review — TTP re-confirmed from dashboard, retention interview, mentor candidacy decided, next-90 development talk.
- Assets: masterclass clinic, buddy-candidate shadowing structure, cohort dashboard.
- Assessment gate (d90): still employed, parity confirmed, ≥1 rotation completed, mentor candidacy decided.
- TTP contribution: retention is the silent TTP driver — every week-2 quit resets a cohort's median and burns a hiring cycle. The growth track exists to protect the investment the first 41 days created.
- Drop-risk monitored: coasting signals (plateau + quiet disengagement), rotation scheduling conflicts (the growth track is the first thing busy weeks eat — it is protected in the rota, not optional).
What changed since Kit 1 (artifact continuity note)
Kit 1 built the certification module and the explainer as standalone artifacts. In this program they are named, scheduled components: the explainer is pinned to d1-before-dock-entry, the module's attempts are scheduled (diagnostic d4, certification d28) instead of ad-hoc, and its item-level remediation feeds the borderline-case deck. Same assets, new architecture — the difference between having content and having a curriculum.
Fictional disclosure: VanDijk Logistics, cohort figures and failure patterns are a fictionalized composite built from realistic logistics onboarding data. Program map drafted with AI assistance; architecture, thresholds and final copy are human-owned.