VettaraThe job title is not the assignment
“Head of Operations” could mean stabilizing service delivery, opening new locations, managing a turnaround, or building processes for a growing company. Those are different searches, even if the title is identical.
Before requesting names, finish this sentence: “We need this person because the business must…” Then describe the work without mentioning a preferred employer, fashionable job title or vague personality label.
This reflects a basic selection principle: understand the job's tasks and relevant competencies before deciding how to assess people. The US Office of Personnel Management explains that connection in its job-analysis guidance. The practical framework below is our suggested way to make that conversation concrete; it is not a legal checklist.
Separate a requirement from a preference
An essential requirement should earn its place in the brief. What would fail if it were missing? Could the capability be demonstrated another way? Is it needed on day one, or could the person learn it?
If nobody can answer, it may be a preference wearing an “essential” label.
Consider a fictional business seeking an operations leader. Experience coordinating multiple locations may be central to the work. Experience at one named competitor may simply be familiar to the hiring manager. Treating both as equally necessary can narrow the research before anyone has examined the evidence.
Company lists are useful search boundaries, not certificates of competence. A familiar logo does not explain what someone personally owned or achieved.
Write down the evidence you would accept
“Strategic” is an adjective. “Has led a documented change to how a multi-site operation plans and measures delivery” is a question research and assessment can investigate.
For each important requirement, write three short entries:
Do not force every question into profile research. A public biography can suggest relevant experience; it cannot conduct a structured interview or establish a candidate's interest in your role.
- What we need: the job-related capability or responsibility.
- What would support it: role history, a work example, an interview answer or another appropriate source.
- What research cannot settle: personal ownership of an outcome, current interest, or a fact requiring confirmation.
Stop hiding disagreements inside the brief
One stakeholder wants someone who has built a function. Another wants experience operating a mature one. Both expectations appear under “leadership experience,” so the contradiction survives until the interviews.
Bring that disagreement forward. State the trade-off, record the decision and name the person who can approve changes. If the mandate changes after sourcing begins, version the brief and reconsider the research. Do not quietly assess the next candidates against a new standard.
Before launch, confirm the role's scope, reporting line, work arrangement, realistic market boundaries and unresolved commercial details. Keep confidential information out of public examples and restrict a real brief to the people who need it.
Use software after the decision is clear
Vettara supports brief-led candidate research and shortlist review. That is useful when the team can explain what it is looking for. It is not a substitute for deciding what the job should be.
In a demo, start with a non-confidential brief. Ask whether the research preserves its requirements, whether a reviewer can inspect the supporting information, and what happens when an assumption is wrong. Do not accept a long list as the only success measure.
The better question is: “Can our team explain why each person deserves the next conversation?”