Four stakeholder perspectives
Executive sponsor
Explains the strategic objective, commercial pressure and decision context.Process owner
Understands the intended workflow, controls, metrics and accountability.Frontline practitioner
Shows how work actually happens, including exceptions, workarounds and informal tools.Adjacent stakeholder
Reveals handoffs and downstream consequences that the core team may not see. Depending on the process, adjacent roles may include IT, finance, compliance, customer-facing teams or data owners.How many stakeholders?
There is no universal number. Use enough coverage to capture materially different roles, variants and viewpoints. Stop adding interviews when they are no longer changing the picture in a meaningful way, while still ensuring important roles and exceptions are represented.Selection questions
Ask:- Who owns the outcome?
- Who performs the work most frequently?
- Who handles exceptions?
- Who receives the output downstream?
- Who sees failures or escalations?
- Who understands the systems and data?
- Who may disagree with the official process description?
Common mistake
Do not let the sponsor nominate only senior managers. This creates an elegant description of the intended process rather than evidence of the real one.Consultant talk track
We want a small but representative cross-section: someone who owns the outcome, someone who manages the process, people who perform the work, and relevant adjacent teams. That lets us compare the intended workflow with what actually happens in practice.