Most difficult searches are not talent-supply problems. They are definition problems. A precise brief shortens every stage that follows.
When a search stalls, the instinct is to widen the net. More often, the issue sits earlier in the process: the role was never defined precisely enough for anyone to recognise the right candidate — including the hiring team.
A usable brief describes the work, not the wish list. It states what the role owns, what it decides, who it influences, and what has to be true twelve months in for the appointment to be considered successful.
Start with the decisions the role owns
Titles travel badly between organisations. An Operations Manager in one company runs a shift; in another they own a regional budget. Listing the decisions the role holds removes that ambiguity instantly and tells candidates whether the scope matches their experience.
Separate requirements from preferences
A brief with fourteen mandatory requirements is not rigorous — it is untested. Requirements are the things without which a capable person cannot do the job. Everything else is a preference, and preferences should be ranked rather than presented as gates.
- Essential: capability the role cannot function without on day one
- Important: capability that materially shortens time to effectiveness
- Preferred: useful context that can be learned in role
Define success before you define the person
Agreeing the first-year outcomes forces useful disagreement inside the hiring team early, while it is still cheap. It also produces the interview criteria: if success requires rebuilding a reporting cycle, then evidence of rebuilding a reporting cycle is what interviews should test.
Keep the brief a living document
Market feedback is information. If the first round of conversations consistently shows the compensation band, location expectation, or seniority mix is unrealistic, the brief should change rather than the search simply continuing longer.