The Role Discovery Brief: One Document That Changes Every Hiring Conversation

Most hiring failures happen before sourcing begins. A poorly defined role, a JD that describes what the last person did rather than what the next person needs to do, a set of "must-haves" that don't actually reflect what the role requires - these are the preconditions for a bad hire. And they're all preventable.

The Role Discovery Brief is a one-page document we produce before we source a single candidate. It takes 45 minutes to create, and it prevents most of the failures that cost weeks of sourcing and interviewing later.

What Is a Role Discovery Brief?

A Role Discovery Brief is a written summary of our understanding of a role - not a restatement of the JD, but an interpretation of what success actually looks like. It covers: the business context driving the hire, what the role needs to deliver in the first 90 days, the technical and domain signals we'll use to screen candidates, the cultural and team dynamics that will determine fit, and the red flags from previous hires or failed searches.

We share it with the hiring manager before we source. We ask them to validate it - or correct it. Then we source.

Why It Changes Everything

The act of producing the brief forces precision. Vague requirements become specific. "Strong communication skills" becomes "ability to present technical architecture decisions to a non-technical executive committee." "Relevant experience" becomes "at least one end-to-end implementation of a core banking modernisation program."

When the hiring manager validates the brief, it creates alignment before sourcing begins. Both the recruiter and the hiring manager are evaluating candidates against the same success criteria. There are no surprises at interview stage. The profile that was submitted is the profile that was expected.

The Six Elements of an Effective Brief

• Business context: Why this role exists now, what triggered the hire, what changes if it's not filled
• 90-day success definition: What does good look like at the end of the first quarter
• Technical screening signals: The specific skills and experiences we'll use to filter - not keywords, but validated capability signals
• Domain depth requirements: Industry, function, and regulatory context the candidate must bring from day one
• Team and cultural context: Team size, working style, stakeholder dynamics, and the characteristics of past successful hires
• Red flags and failure modes: What has gone wrong with previous hires in this role or similar roles

How to Implement It Today

The next time you receive a requirement from a hiring manager, block 45 minutes for a structured intake conversation using these six elements as your framework. Produce a one-page written summary. Send it to the hiring manager and ask them to validate it in writing. Do not begin sourcing until you have their sign-off.

It will feel slower at first. It will be faster overall. And the profiles you submit will be approved at a rate that makes every subsequent engagement easier to win.