Role design

Write a hiring brief that survives the real process

A strong hiring brief is the team’s decision document for the entire search. It explains why the role exists, what the person must accomplish, which capabilities deserve evidence, and which constraints are approved. Build it with the recruiter and interviewers, test it against plausible candidates, and update every downstream step when the brief changes.

On this page
  1. Explain why the role exists now
  2. Define outcomes before credentials
  3. Draw the role boundary
  4. Lock practical decisions
  5. Stress-test the brief
  6. Control changes during the search

Explain why the role exists now

Open with the business problem, current owner, and consequence of leaving the work uncovered. Distinguish a replacement from a redesigned or newly created role. If the role combines several old responsibilities, explain why they belong together. This context helps sourcers find relevant people and lets candidates judge the opportunity without relying on a generic list of duties.

Define outcomes before credentials

Describe four or five observable outcomes for the first year, in a sensible sequence. An outcome names a change the person can influence, such as establishing a planning cadence or reducing a recurring hand-off problem. Avoid promising numerical results the team cannot support. Then identify the capabilities needed to do that work, rather than copying degree or tenure requirements from an older description.

Draw the role boundary

State what the person owns, where they collaborate, and what remains with another team. Include their manager, important partners, decision rights, and resources already available. A role that is accountable for an outcome but cannot make the relevant choices needs redesign. Boundary clarity also reveals whether two leaders are trying to hire different jobs under one title.

Lock practical decisions

Confirm location or hybrid expectations, working-hour overlap, travel if genuinely required, approved level, and compensation decision owner. Record what remains flexible. In India, notice-period conversations may affect timing, but they should not be turned into assumptions about commitment. Interviewers should know which terms are fixed before discussing them with candidates.

  • Role outcome and business reason
  • Ownership and partner boundaries
  • Evidence required for selection
  • Approved and flexible constraints

Stress-test the brief

Illustrative example: a hiring manager asks for a senior operations generalist. One hypothetical candidate has deep process design experience but no people management; another has led a large team but rarely redesigned workflows. The discussion reveals that the immediate need is individual ownership of a broken hand-off, not team leadership. The level and interview plan are revised before sourcing.

Control changes during the search

Assign one owner to approve revisions. When evidence suggests the brief is wrong, pause and document the change, its reason, and its effect on active candidates. Update the job description, sourcing criteria, scorecard, and interviewer guidance together. Quietly changing one interviewer's preference creates an unfair moving target and makes earlier decisions impossible to compare. At close, compare the final job with the original brief and record which assumption proved wrong. That learning should improve the next intake rather than becoming private recruiter memory.

Next step

Before outreach, ask every interviewer to approve the same one-page brief and resolve any outcome, scope, evidence, or constraint they interpret differently.

A clearer starting point

Turn your next hire into a considered brief.

Start a hiring brief