A VP of Talent at a 60-warehouse logistics company tests an Operations proposal against its own numbers and brings back a counter-proposal, with any AI chat her company allows.
A proposal from Operations, a CHRO who half-believes it, and four reports. The proposal sounds sensible. Operations' own breakdown says the problem is somewhere else.
Here the AI tests someone else's proposal. The prompt asks where the time actually goes.
Use the AI tool your company approves: ChatGPT, Claude, Gemini or Copilot.
Copy the prompt and the five fictional inputs from the appendix into one message.
Add up the days yourself. Then turn the AI's ideas into a short proposal your colleague can say yes to.
I'm VP of Talent at a logistics company with about 18,000 people in 60 warehouses in the US and Canada. Peak season is starting. Our SVP of Operations wants to cut new-hire onboarding from three days to one, to get people on the floor faster. My CHRO wants my view by Thursday. Below are her email, our onboarding report, the SVP's note, our 30-day turnover figures and a safety note.
Please give me:
Be skeptical. Check what each number counts, whether a change is a trend or a season, where the time actually goes, and what we would lose by cutting. If something is missing, say so. Don't add facts that aren't in the inputs.
Exactly as it came back, not edited. Read it the way Renee did: check each point against the source it cites.
Only partly. By Dan's own breakdown, onboarding is 3 of the 9 days from offer to first shift, and the background check alone takes 5. Cutting onboarding to 1 day would save at most 2 days, and it would put the warehouse safety day (Day 2) at risk at the moment injuries are concentrated among new starters. The turnover figures don't show that onboarding is failing, so "fixing" onboarding by shortening it doesn't address a problem the data has proven.
Time to first shift: the biggest delay is the background check, not onboarding [3]
The onboarding report's "%" is not a completion rate [2]
30-day turnover: the October jump is mixed with a season and a definition change [4]
Safety: new starters are involved in most injuries, and Day 2 is the safety day [5]
What we'd lose by cutting
Proposal: keep the safety content intact and attack the 6 days before onboarding starts.
Short version for Janet: Onboarding is a third of the delay, not the bottleneck. The October turnover jump is partly temporary contracts ending, and nothing in the data links turnover to onboarding. The day we'd most likely lose is the safety day, at a time when new starters account for 14 of 22 injuries. Go after the 6 days before onboarding first, and trim Days 1 and 3 only where content isn't needed before the first shift.
Claude found every planted problem and even spotted that the turnover footnote doesn't add up. Renee's edits are about turning a good analysis into a proposal Operations can accept.
Use it whenever someone proposes a fix you're not sure about: cutting a programme, adding a course, changing a process.
I'm the [your role] at a [industry] company with about [number] people in [number] sites. [Who] wants to [the proposed fix] to [their goal]. [Your leader] wants my view by [date]. Below are [the proposal and the reports that bear on it].
Please give me: 1. Does [the proposed fix] solve the problem [they] describe? Answer in two sentences. 2. What the numbers really show, with the input each point comes from. 3. A counter-proposal I can take to [them].
Be skeptical. Check what each number counts, whether a change is a trend or a season, where the time actually goes, and what we would lose by cutting. If something is missing, say so. Don't add facts that aren't in the inputs.
Copy the prompt, then all five inputs, into one message in a new chat. Everything here is fictional and safe to paste.
I'm VP of Talent at a logistics company with about 18,000 people in 60 warehouses in the US and Canada. Peak season is starting. Our SVP of Operations wants to cut new-hire onboarding from three days to one, to get people on the floor faster. My CHRO wants my view by Thursday. Below are her email, our onboarding report, the SVP's note, our 30-day turnover figures and a safety note. Please give me: 1. Does cutting onboarding solve the problem Operations describes? Answer in two sentences. 2. What the numbers really show, with the input each point comes from. 3. A counter-proposal I can take to Operations. Be skeptical. Check what each number counts, whether a change is a trend or a season, where the time actually goes, and what we would lose by cutting. If something is missing, say so. Don't add facts that aren't in the inputs. [1] Email from Janet Cole, CHRO Subject: Ops onboarding proposal Renee, Dan wants to cut onboarding from 3 days to 1 for peak. He says onboarding is the bottleneck and our onboarding clearly isn't working, given turnover. Your view by Thursday please. [2] Onboarding report, October | Region | Hires | Onboarding completions | % | |---|---|---|---| | East | 1,240 | 1,302 | 105% | | Central | 980 | 902 | 92% | | West | 860 | 791 | 92% | Note: a completion is counted each time someone finishes the programme. People who leave and are rehired in the same month are counted again. Site 51 (Moncton) has not submitted onboarding data since June. [3] Note from Dan Reyes, SVP Operations Offer to first shift is 9 days on average. Onboarding is 3 of those. Cut it to 1 and we get people on the floor 2 days faster for peak. Breakdown: offer to background check cleared, 5 days; check cleared to onboarding start, 1 day; onboarding, 3 days. [4] HR analytics: people who leave within 30 days August 18% · September 21% · October 27% Analyst note: "30-day turnover rising sharply. Onboarding isn't working." Footnote: October includes peak-season temporary hires on 6-week contracts, counted as leavers when the contract ends. [5] Safety note, October 22 recordable injuries in the network. 14 involved people in their first 30 days. Day 2 of onboarding is the warehouse safety day (powered equipment, lifting, pedestrian routes).I'm VP of Talent at a logistics company with about 18,000 people in 60 warehouses in the US and Canada. Peak season is starting. Our SVP of Operations wants to cut new-hire onboarding from three days to one, to get people on the floor faster. My CHRO wants my view by Thursday. Below are her email, our onboarding report, the SVP's note, our 30-day turnover figures and a safety note.
Please give me:
Be skeptical. Check what each number counts, whether a change is a trend or a season, where the time actually goes, and what we would lose by cutting. If something is missing, say so. Don't add facts that aren't in the inputs.
Subject: Ops onboarding proposal
Renee, Dan wants to cut onboarding from 3 days to 1 for peak. He says onboarding is the bottleneck and our onboarding clearly isn't working, given turnover. Your view by Thursday please.
| Region | Hires | Onboarding completions | % |
|---|---|---|---|
| East | 1,240 | 1,302 | 105% |
| Central | 980 | 902 | 92% |
| West | 860 | 791 | 92% |
Note: a completion is counted each time someone finishes the programme. People who leave and are rehired in the same month are counted again. Site 51 (Moncton) has not submitted onboarding data since June.
Offer to first shift is 9 days on average. Onboarding is 3 of those. Cut it to 1 and we get people on the floor 2 days faster for peak. Breakdown: offer to background check cleared, 5 days; check cleared to onboarding start, 1 day; onboarding, 3 days.
August 18% · September 21% · October 27% Analyst note: "30-day turnover rising sharply. Onboarding isn't working." Footnote: October includes peak-season temporary hires on 6-week contracts, counted as leavers when the contract ends.
22 recordable injuries in the network. 14 involved people in their first 30 days. Day 2 of onboarding is the warehouse safety day (powered equipment, lifting, pedestrian routes).