Hiring operations
Run a hiring retrospective that changes one mechanism
Hold a hiring retrospective soon after a role closes or stops. Compare the original plan with actual events, include recruiter, manager, operations, and candidate signals, and separate individual effort from system design. Choose one or two changes with owners and review dates, preserving practices that worked instead of producing a long unowned lesson list.
On this page
Select a useful scope
Review a completed, cancelled, or materially reset search while records and memories remain available. State the question: perhaps why the brief changed, where candidates waited, or which assessment predicted the decision. Avoid using a retro to relitigate the selected person or assign blame. The unit of learning is the hiring process for this kind of work.
Reconstruct the search from evidence
Bring the approved requisition, kickoff brief, timeline, pipeline movements, feedback records, candidate communications, offer decision, and known decline or withdrawal reasons. Mark changes and their decision owners. Use participant memory to explain gaps, not replace records. Include what happened after selection, such as handoff readiness, where it reveals whether the process prepared the next step.
Ask mechanism questions
What assumption proved wrong? Which step created or removed uncertainty? Where did the team repeat work? Which candidate message arrived too late? What helped decision quality? Distinguish a one-off event from a rule likely to affect future searches. Keep strengths visible so the team does not remove a useful practice while correcting a nearby problem.
- Original plan versus actual path
- Decision that changed the search
- Candidate wait or repeated work
- Practice worth preserving
- One mechanism to test next time
Convert a lesson into design
Illustrative example: a design search required an extra portfolio stage for every finalist. The retro finds that the first interview never tested the same evidence, so interviewers added the stage late. The team rewrites the first-stage prompt and removes the default extra round. It will review the next two searches for decision evidence and candidate burden before keeping the change.
Close actions into operating work
Assign each improvement to a system, template, training, or meeting owner with a due date. Define where its effect will appear and when to review it. Share relevant learning with partners and managers who were not in the retro. Limit actions to what the team can complete; a backlog of ten worthy ideas often protects the original process from any actual change. Begin the next relevant search by reviewing the previous action and confirming it is actually in the workflow. If the same issue returns, inspect whether the change was adopted, misunderstood, or aimed at the wrong cause. Do not count an action complete because a document was updated. Close the retro by thanking participants for specific candour and separating process learning from any individual performance follow-up, which belongs in its proper forum.
Next step
Schedule a forty-five-minute retro for the latest closed search, bring the actual timeline, and leave with one mechanism change, owner, and review case.