Executive search
Executive search decision rights: who can change the brief?
A decision-rights worksheet for search partners: clarify the client process, distinguish advice from approval and keep unresolved authority visible.
The sponsor wants a broader shortlist. A functional leader asks for a narrower background. Another stakeholder tells the researcher to prioritize a different location. Each instruction sounds reasonable when heard alone. The difficulty is knowing which instruction the search team is authorized to use.
A decision-rights map makes the client's working process explicit. It names the decision, the person coordinating it, the authority needed and the evidence that confirms the outcome. It also gives the consultant a place to record an unresolved question without presenting it to researchers as an agreed change.
Create the map alongside the mandate kickoff record. Keep it separate enough to update when client responsibilities change. The worksheet below is an original process aid; it does not determine the client's governance or replace an engagement agreement.
TL;DR
- Map decisions individually. Giving someone a general stakeholder label does not explain which instructions they can approve.
- Distinguish the person collecting input from the authority that confirms the outcome.
- Record how an approval becomes usable evidence, including any agreed joint or committee process.
- When authority is uncertain, hold the dependent action and ask a precise clarification question.
A decision-rights worksheet for a live assignment
Start with decisions the search team actually expects to face. A useful first version can fit on a page. Add detail where a real ambiguity appears rather than cataloguing every possible conversation.
| Decision | Coordinate | Input needed | Client confirmation | Evidence and dependent action |
|---|---|---|---|---|
| Change a research criterion | Named consultant | Relevant client and research context | Follow agreed client authority | Link the confirmed wording before updating the research brief |
| Extend the company boundary | Research lead with consultant | Reason, coverage implications and restrictions | Named client process | Record the decision and what research may proceed |
| Share a working candidate summary | Assigned consultant | Accuracy, recipient and sharing limits | Agreed review route | Keep confirmation with the version that will be shared |
| Resolve conflicting feedback | Client-facing consultant | Specific disagreement and evidence | Authorized decision route | Record what remains open and the next owner |
| Change a delivery expectation | Assignment lead | Effect on work and dependencies | Appropriate client authority | Update the agreed working expectation and notify affected owners |
The rows are suggestions, not a universal allocation of authority. Replace the role labels with actual responsibilities. A named sponsor might coordinate several decisions while another client process confirms them.
Ask about the decision process before the disagreement
At the start of the assignment, ask which choices need which kind of confirmation. Use concrete examples: a change to the research boundary, a new stakeholder's request, a decision about progressing a candidate or a revised delivery expectation.
The AESC Client Bill of Rights includes written clarity about the assignment and lead advisor for member engagements. Use the client's own agreed arrangements as the starting point. This worksheet does not establish that Laisy or a particular firm is an AESC member.
Ask the client to describe a decision that went well on a previous project and one that became difficult to resolve. You are looking for the working route: who collected the information, who needed to be involved and how the outcome was communicated. Do not record those examples as verified facts about people who were not part of the discussion.
Check the absence case too. If the sponsor is away, what can continue? Which choices wait? Who can arrange a clarification? A workable answer can be a defined pause with an owner. It does not need to invent an alternate approver for convenience.
Separate coordination, advice and confirmation
One person may arrange a discussion, collect the documents and chase the response. Another may provide essential subject knowledge. Neither role necessarily carries authority to confirm the final instruction.
Atlassian's DACI playbook describes four roles: Driver, Approver, Contributors and Informed. Its model places a decision with one approver. That is a useful lens for identifying responsibility, not a rule that overrides a client's joint or committee arrangements.
For a search assignment, translate the distinction into plain questions. Who gets this decision ready? Whose input must be considered? What client process makes the outcome authoritative? Who needs the result to do their next task?
Keep only the confirmed working instruction and permitted source pointers in the shared record. Avoid copying confidential deliberations into a broader team document.
If a client uses collective decisions, record how that process works. A liaison can provide the resulting instruction without being the sole decision-maker. Be explicit about the evidence the consultant should retain. Avoid replacing an actual collective process with a single name merely because a worksheet has a convenient field for it.
Define the question at a useful level
“Approve the search strategy” can be too broad to help when a particular criterion changes. Break a vague approval into the practical question being asked. For example, does experience in a neighboring market meet the requirement when the operating challenge is comparable? Which evidence would the client need to decide?
For federal assessment, OPM's job-analysis guidance connects job tasks with required competencies. That distinction can help make the client's question concrete. The worksheet is not a job-analysis certification or a validated method for selecting executives.
State the question without implying its answer. Record the current instruction, the requested revision, the evidence available and the choice that remains open. Give contributors a clear opportunity to explain what they know and which assumptions they are making.
If the discussion concerns a candidate, preserve the difference between a factual question and an evaluation. “What evidence is available?” and “Does that evidence satisfy our agreed criterion?” may need different inputs. Keep the client's authorized decision process visible for both.
Synthetic example: the sponsor can coordinate but cannot confirm alone
This example is fictional. Its people, counts and decisions illustrate the worksheet; they are not a customer story or a recommended governance structure.
A search team is working with three client participants: a sponsor, a functional leader and a finance representative. The sponsor coordinates the assignment. The client has already agreed that changes affecting the role's operating scope require a joint confirmation through its own process.
The functional leader suggests expanding a criterion. The sponsor tells the consultant that the suggestion sounds sensible. The consultant records the proposal and asks how the required confirmation will be provided. The research question can be prepared while the instruction remains open.
| Record | What the team writes |
|---|---|
| Decision question | Can the revised operating scope be used in the research brief? |
| Coordination owner | Search consultant, working through the sponsor |
| Required input | The functional leader's explanation and the relevant assignment context |
| Confirmation route | The client's existing joint-confirmation process |
| Interim boundary | Prepare the research impact; do not present the proposal as approved |
| Closure evidence | The confirmed wording, its date and a pointer to the retained instruction |
The sponsor remains helpful and accountable for coordination. The record simply avoids attributing a different authority to that role. Once confirmation arrives, the consultant can tell researchers which instruction has changed and which work needs review.
Keep software access separate from decision authority
Seeing a project, leaving a comment and confirming a client instruction are different activities. Review the actual controls in the system the team uses, then document the business responsibilities alongside them.
For example, Clockwork's project-team documentation describes explicit membership management and requires a user to exist before project assignment. That describes Clockwork. Membership in a software project does not, by itself, establish a person's authority under the client's arrangements.
When reviewing the map, ask whether the right people can obtain the information they need without broader access than the task requires. If an owner cannot open the supporting record, arrange an appropriate permitted view or handback. Do not treat a forwarded link as proof that access has been checked.
Check notifications too. A person can be informed of a decision without being invited to make it, and receiving an email does not mean they have approved its contents. Make the requested response explicit in the message.
Handle conflicting instructions without creating a hidden decision
Write the disagreement in a form the client can resolve. Identify the competing instructions, their sources and the action that depends on clarification. Ask the authorized client contact to confirm the route for resolving it.
Use the shortlist feedback record when the disagreement concerns candidate comments or missing evidence. Keep that record connected to the relevant criterion and decision process. A reaction, a preference and an agreed instruction can have different meanings.
Give affected researchers a bounded interim action. They might continue independent work, prepare the missing evidence or hold the disputed step. Ask them to confirm that boundary in their own words. Avoid passing along an informal interpretation simply to keep every part of the assignment moving.
If two colleagues have already acted on different instructions, review what happened before correcting the shared record. Identify affected outputs and conversations. Assign a consultant to agree any necessary external clarification, then retain enough history to explain why the working instruction changed.
Keep the map useful when people change
Review the map when a new stakeholder joins, the sponsor changes, someone becomes unavailable or the scope of the assignment shifts. Those events can affect which information is needed and how confirmation is obtained.
Use the next client update to request a specific outstanding decision where appropriate. State the question, why it matters and what work is waiting. Describe the dependency without turning it into a claim about an individual's performance.
During an internal consultant handover, ask the incoming colleague to locate the current authority map and explain one open decision. That readback tests whether the record can be used. A list of stakeholder names is less useful if the colleague cannot tell what response they need next.
Test the worksheet on a bounded task
Choose one unresolved question in a suitable live search. Agree the permitted context, the person reviewing the record and the evidence that would make it useful. The result might be a clear confirmation route and an interim instruction everyone affected can explain.
You can discuss that task with Laisy alongside your existing tools. Keep the test to selected inputs and reviewed output, with an agreed point to continue or stop. A discussion does not promise access, a decision from the client or a particular result.
Frequently asked questions
Is a stakeholder map the same as a decision-rights map?
A stakeholder map identifies people and relationships. A decision-rights map describes what must happen for a particular outcome to become an authorized instruction. The same person can have different responsibilities for different decisions.
Must every decision have one individual approver?
Follow the client's actual arrangements. A single-approver model can clarify some decisions, but it does not replace collective, delegated or committee procedures. Record the applicable route and how its result will be confirmed.
What if the client will not clarify authority?
Explain the specific action that depends on the answer and propose an interim boundary. Keep the question, follow-up owner and next review point visible. Do not convert uncertainty into assumed approval.
Can software permissions settle the issue?
Permissions determine what a user can do in a tool. Business authority comes from the client's arrangements and the engagement. Check both, and keep a traceable instruction for consequential changes.