Case 53
Hiring Manager Intake Interview
Scenario
You are a talent partner at Fernway Logistics. Priya, Head of Operations Planning, needs a planning analyst. Her draft job description lists fourteen "essential" skills, and the last two hires in her team left within a year. You have a 45 minute intake call tomorrow.
Why this framework
Uses full PINPOINT because everything later in the hiring chain depends on this output. A vague intake leads to a vague job description, an unfair screen and inconsistent interviews.
Example context
Draft job description (old), Planning Analyst, Fernway Logistics: 14 essential items, including: degree in maths or a related subject from a leading university; 5+ years in logistics planning; advanced Excel; SQL; Power BI; Python; knowledge of warehouse management systems; forklift awareness; native English speaker; strong communicator; good culture fit; self-starter; works well under pressure; full driving licence. Team structure: Priya Nair, Head of Operations Planning; 2 senior planners; 3 planning analysts (this is a replacement); supports 4 depots and the transport desk. Role works on site at the Daventry hub 3 days a week. HR fair hiring policy (extract): criteria must be job-related and evidenced; no requirements based on protected characteristics or proxies (age, years since graduation, nationality, accent, named universities); years of experience may only be required where justified; reasonable adjustments offered at every stage. Hiring manager's answers (Priya, given in advance for this run; treat as her answers in the interview): First 6 months: own the weekly labour capacity plan for 2 depots and get forecast accuracy to within 5% of actual hours. 12 months: build a shift-pattern model the depots use for peak season. Must have: strong Excel modelling; explaining numbers to depot managers who push back; reliable weekly routine. SQL is nice to have (data team can help). Python and Power BI not needed now. Degree: not essential if they can model. 5+ years: "I want someone experienced", but would accept a fast learner with 1 to 2 years. Last two hires left because the role was more stakeholder pressure than expected and they preferred pure analysis. Previous successful analyst came from a retail store planning role. Driving licence: not needed, hub is on a bus route. "Native English speaker": she meant clear written English for reports. Deal-breaker: missing the Monday plan deadline repeatedly.
Prompt
Purpose: Interview me, the hiring manager, one question at a time, to find out what this role really needs. The output becomes the agreed hiring brief that the job description, screening and interviews will all use.
Context: Use the attached draft job description and team structure as the starting point. My answers in this conversation are the final word on what I want. Our HR policy on fair hiring, attached, overrides any preference I state.
Narrow the ask:
1. Ask me one question at a time, no more than 15 in total. Start with the outcomes this person must deliver in their first six and twelve months, then work back to skills.
2. Probe vague answers. If I say "strong communicator" or "good culture fit", ask what that looks like in a real week in this team and how we would see evidence of it.
3. Test every "essential" item: "Would you reject an otherwise excellent candidate who lacked this?" If not, move it to nice-to-have.
4. Ask about trade-offs (for example depth of experience against speed of learning), deal-breakers I have not written down, and why the last people in the role succeeded or left.
5. When we finish, give me a hiring brief with: outcomes; must-haves (no more than five) with what counts as evidence; nice-to-haves with suggested weights adding to 100; non-criteria we agree not to judge on; open questions marked [GAP].
Persona and role: Act as an experienced, independent talent partner. Be polite but challenge me. Your job is a clearer, fairer brief, not to agree with me.
Examples: Good must-have: "Has built a weekly capacity plan that others relied on; evidence is a described example or work sample." Bad must-have: "Young and energetic self-starter."
Check your work: If any preference I state relies on a protected characteristic or a likely proxy for one (age, years since graduation, nationality, family plans, "native speaker", a named university), flag it, explain why, and suggest a job-related alternative. Label each brief item as [Stated by manager], [Inference] or [Assumption].
Before I use it: I will review the brief and confirm it in writing. HR will check it against policy. The approved brief is version 1 and is saved with the vacancy record.
Tweak and test: If the questions feel generic, I will change one thing, such as adding notes on the previous hire, and run it again.
Materials (pasted here in place of the attachments):
Draft job description (old), Planning Analyst, Fernway Logistics: 14 essential items, including: degree in maths or a related subject from a leading university; 5+ years in logistics planning; advanced Excel; SQL; Power BI; Python; knowledge of warehouse management systems; forklift awareness; native English speaker; strong communicator; good culture fit; self-starter; works well under pressure; full driving licence.
Team structure: Priya Nair, Head of Operations Planning; 2 senior planners; 3 planning analysts (this is a replacement); supports 4 depots and the transport desk. Role works on site at the Daventry hub 3 days a week.
HR fair hiring policy (extract): criteria must be job-related and evidenced; no requirements based on protected characteristics or proxies (age, years since graduation, nationality, accent, named universities); years of experience may only be required where justified; reasonable adjustments offered at every stage.
Hiring manager's answers (Priya, given in advance for this run; treat as her answers in the interview): First 6 months: own the weekly labour capacity plan for 2 depots and get forecast accuracy to within 5% of actual hours. 12 months: build a shift-pattern model the depots use for peak season. Must have: strong Excel modelling; explaining numbers to depot managers who push back; reliable weekly routine. SQL is nice to have (data team can help). Python and Power BI not needed now. Degree: not essential if they can model. 5+ years: "I want someone experienced", but would accept a fast learner with 1 to 2 years. Last two hires left because the role was more stakeholder pressure than expected and they preferred pure analysis. Previous successful analyst came from a retail store planning role. Driving licence: not needed, hub is on a bus route. "Native English speaker": she meant clear written English for reports. Deal-breaker: missing the Monday plan deadline repeatedly.Example output from ChatGPT
We’ll build the hiring brief for the Planning Analyst, Fernway Logistics, using your answers as the final word, subject to HR's fair hiring policy.
I’ll challenge requirements that are vague, unnecessary or difficult to assess fairly. We’ll work through no more than 15 questions, one at a time.
Your advance notes already establish two important outcomes:
- First 6 months: Own the weekly labour capacity plan for two depots, achieving forecast accuracy within 5% of actual hours.
- First 12 months: Build a shift-pattern model that depots use for peak-season planning.
I also see potential problems in the old job description. The named-university requirement and "native English speaker" requirement conflict with the fair hiring policy. We'll replace them with demonstrable, job-related capabilities.
Question 1 of up to 15: Defining success
You want forecast accuracy within 5% after six months.
What exactly should that 5% measure, and what would convince you the analyst genuinely owns the planning process rather than simply produces a spreadsheet?
For example, should accuracy be measured separately for each depot or across both combined? And what decisions should depot managers be able to make using the plan?
I want to make the outcome specific enough that we can assess candidates against it and later measure performance fairly.
