How to Run a Mid-Year Hiring Retrospective That Actually Changes Your Process

The hiring process that produced your H1 misses will produce your H2 misses if nothing changes.

This is the case for the mid-year hiring retrospective: not as a way of understanding what went wrong in H1, though that matters, but as a way of ensuring that H2 does not repeat it. The companies that run this analysis change their process. The ones that do not run it attribute their results to candidate quality and proceed with the same approach that produced them.

Most Nigerian companies make hires, observe outcomes, and attribute the results to the quality of the candidates rather than to the quality of the process that selected them. This attribution is often wrong. The hiring process has consistent patterns: in where it finds candidates, how it evaluates them, and what signals it uses to make decisions. Those patterns produce consistent patterns in outcomes. A retrospective is the analysis that makes the patterns visible so they can be changed.

It takes two to three hours to run well. It generates specific, actionable changes to the H2 process. And it is the difference between a hiring function that improves over time and one that repeats its errors with confident consistency.

The Questions the Retrospective Must Answer

A. Where did the best H1 hires come from? Not in terms of job board or source channel, those are proxies, but in terms of the referral path, the candidate’s prior context that made them a fit, and what about the sourcing approach that found them could be replicated deliberately. The best hire who came through a specific referral network tells you something about where your talent density is highest. The pattern across multiple strong hires tells you where to concentrate H2 sourcing effort.

B. Which H1 hires are performing below expectation, and what does the interview process reveal in retrospect? The hire who seemed strong in the interview and is underperforming in the role is a signal about a gap in the evaluation process: something the interview assessed that was not predictive of role performance, or something the interview failed to assess that turned out to be essential. The retrospective identifies specifically what signals were present in the interview data that, in hindsight, indicated the risk that has materialised. Those signals should be part of the H2 evaluation criteria.

C. How accurate were job descriptions at representing the actual role? The most common hiring process failure in Nigerian companies is a job description that describes the role as it was conceived rather than as it will be experienced. The candidate who accepted the role based on an inaccurate job description and whose first 90 days revealed significant gaps between expectation and reality is not a bad hire. They are the output of a bad job description. The retrospective asks: for each H1 hire, did the role they accepted match the role they found?

D. What was the time-to-hire for each role, and what produced the variance? Some roles were filled in three weeks. Others took three months. The retrospective identifies what determined the difference: in sourcing efficiency, in interview process speed, in decision-making confidence, and extracts the process lessons that can reduce time-to-hire across the board in H2 without compromising selection quality.

The Three Changes Most Nigerian Companies Should Make After This Exercise

1. A more specific role brief. Not a job description, but a written account of what success in the role looks like in the first 90 days and the first year. This document, shared with candidates rather than the standard job description, reduces the expectation gap that produces early attrition. The candidate who understood the real role accepted it. The one who accepted the described role and found the real one is the attrition risk that the brief prevents.

2. A structured scorecard for each role. A document that defines the three to five specific capabilities the role requires and a scale against which each candidate is assessed. This document, completed independently by each interviewer before the debrief, reduces the recency bias, proximity bias, and halo effects that the retrospective will almost certainly have identified as contributors to the H1 misses. The scorecard is not a bureaucratic requirement. It is the correction for the specific evaluation failures the retrospective surfaced.

3. A defined fast-track path for roles that the retrospective identifies as consistently slow to fill. If engineering roles consistently took eight weeks in H1, the H2 process should include a pre-sourced pipeline, a compressed interview structure, and defined decision timelines that prevent the same delays from repeating.

The Bottom Line

The retrospective is not a celebration and it is not a blame exercise. It is the analysis that makes the pattern visible and gives the H2 process a specific chance to be better than H1.

The hiring process that produced your H1 misses will produce your H2 misses if nothing changes. The retrospective is what changes it.

Revent Technologies runs mid-year hiring retrospectives as part of ongoing advisory engagements: identifying where the process failed, redesigning the brief and scorecard for H2, and filling the roles the new process produces. This is not a one-off placement service. It is the outsourced talent partner that makes your hiring better every cycle.

Start here: www.reventtechnologies.com/site/hire-a-developer

Research Sources
– DexNova Consulting: Recruitment 2026: Nigerian hiring process failures and corrections
– Pin HR: Employee Turnover Rate 2026: early attrition and hiring process quality correlation
– Engagedly: Performance review frameworks: structured evaluation and predictive validity