A job description can be accurate and still leave a search team pulling in different directions. One stakeholder wants a builder. Another wants stability. A third expects the new leader to repair a relationship nobody has named. Before the search begins, those expectations need to become a shared brief.
Start with the work that must change
Ask each decision-maker to finish this sentence: “One year after this person arrives, we need to see…” Collect the answers before meeting together. That gives quieter voices room to contribute and exposes disagreements early.
Choose three to five outcomes that are important, realistic, and within the role’s influence. “Improve leadership” is too broad. “Establish a monthly operating review with clear owners for stalled priorities” tells a candidate what the organization actually needs.
Separate requirements from preferences
For every requested qualification, ask which part of the work depends on it. Some experience is essential. Other experience is helpful but could come from a different sector, organization size, or career path.
Document the distinction. Otherwise a preference can quietly become a screening rule halfway through the search, excluding people the team would have seriously considered at the beginning.
Make the decision process visible
The brief should identify who interviews, who advises, who approves, and who communicates with candidates. Include the expected sequence and the dates when the team will compare evidence. Confirm that those people can actually protect time on their calendars.
A useful search brief is short enough to revisit during a debrief. Include the role’s purpose, first-year outcomes, decision authority, essential experience, and selection process. Give candidates a clear version of that picture, too.
Before launching, ask every decision-maker to explain the role back to the group. If the answers still sound like different jobs, the brief needs another conversation. That time is part of the search, not a delay to it.