Consulting assignment and boundaries · Lesson 2

Mapping stakeholders and decision authority

9 min read

Lesson objectives

  • Map sponsor, recipient, process owner and affected staff with authority and communication needs. Use the influence-impact map and decision-rights table to produce a interview and sign-off map and verify each requested action has an accountable client authority.
Reading tools

A precise scope card can still fail if the person requesting the analysis cannot grant data access, affected workers are not heard, or the party paying for the option never joins the trade-off. A stakeholder map is more than names for a slide. It identifies who supplies evidence, who can check its meaning, who lives with the recommendation, and who can authorize an action. Those roles call for different conversations: exploration, access request, factual review and decision request. A single large meeting can conceal the difference between them.

Suppose the service-experience director sponsors the assignment. She wants faster resolution. The operations supervisor knows how tickets are reclassified. The data steward knows what IDs and timestamps mean. Finance pays for staff or a new system. Front-line employees must use any new triage rule, and customers experience the result. An executive may authorize hiring, while a privacy officer may set conditions for access to personal records. High influence is not the same as legal or organizational authority. The person controlling a budget may not have authority to release sensitive records. Different decisions have different owners.

For each party, fill four practical cells: What decision or task do they own? What evidence or perspective can they provide? How are they affected by the options? How and when should they participate? Add a confidence note: is a statement a direct observation, an inference or an interest in a particular solution? An interest does not make testimony false, but it is a reason to seek a cross-check. Treat the map as a participation hypothesis. The first interview can reveal a missing actor or a different approval route.

In a fictional case, the sponsor insists on four hires. Operations says the team spends extra time recategorizing tickets. The data steward reports a 15% reopened share, but her definition includes tickets automatically closed and reopened when a customer has a different question. Finance says payroll is frozen, though a small budget exists for a classification pilot. I do not rank the highest-influence voice first and adopt its account. I ask the sponsor which decision is due and when; operations which process steps create reclassification; data how “reopened” is counted; finance what the actual funding constraint and pilot duration are. Each interview tests a different part of the assignment.

A compact responsibility table might say that the sponsor approves the assignment question and report acceptance criteria; the process owner validates the workflow and approves an operational pilot within delegated authority; the data steward releases a de-identified dataset and explains fields; finance confirms cost bounds but does not hire for the executive; and the human-resources decision owner decides on recruitment if it becomes relevant. The specialist prepares analysis and options. The specialist does not grant any of those approvals to themselves. If the organization divides authority differently, revise the table against its actual delegated powers.

Separate influence over the decision from exposure to its consequences. The sponsor and finance may have strong influence. A front-line employee who must use a new triage tool may have little formal influence but high exposure. Hearing only influential people can yield a feasible-looking design that fails on the floor. Every customer need not attend every meeting; representative complaint data or permitted interviews may suffice. “Low influence” is not a reason to silence a group. It helps choose a suitable engagement method. Interview priority follows the evidence the decision needs now, not job title alone.

Open an interview with a neutral account of actual work: “Walk me through a ticket reopened last week. Where did it move, and who chose to close it?” This can expose a process step better than “Why did the new classification fail?”, which plants a cause in the question. Ask for a traceable example with personal details removed. Mark what the person saw separately from what they infer. Read back a concise account: “I understand that automatic closure occurs after 48 hours without a reply and that a customer's return may get a new ID. Is that true in every channel?” The read-back prevents one person's description becoming a universal rule without system evidence.

Disagreement is diagnostic material, not merely a relationship problem. If operations blames reclassification and data says the “reopened” category is broader than real rework, do not choose the person closest to the sponsor. Request a split between reopening caused by classification error and a customer's new question, and inspect samples of both. If the system cannot separate them, record uncertainty; do not present 15% as confirmed waste. When numbers differ, request the definition, period and unit behind each one before debating solutions. Sometimes the disagreement is about labels. Sometimes it is a real conflict of interest that needs a decision owner.

There is a professional boundary when a sponsor asks the specialist to share attributed employee interview quotes to justify reducing another team. The assignment concerns a process, and the original interview purpose may not cover individual performance appraisal. Pause the release of names, check the organization's policy, mandate and purpose with the appropriate owner, and explain that the report can present an anonymized operating pattern when evidence supports it. This does not promise absolute confidentiality. It states what can be done within the assignment. ICMCI's framework discusses role clarity, mandate, objectivity and respect for stakeholders; the specific procedure here follows the client's authorized policy rather than an invented universal legal rule.

Lesson summary

A consulting assignment starts with a decision question, not the sponsor’s preferred remedy