Stakeholders and assumptions
4 min read
Lesson objectives
- Map stakeholders' interests, influence and evidence, then identify and test an assumption capable of changing the recommendation.
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
After identifying the decision owner, do not reduce everyone else to anonymous ‘inputs’. A service user may know where provision fails, an operator knows a delivery constraint, a funder knows the commitment limit, and an affected non-user may bear congestion or cost. Give each stakeholder a column for interest, influence on the choice, evidence supplied, and a possible way to disconfirm the claim. Influence is not accuracy: a funder can veto a project while being mistaken about user demand. Nor does a high complaint count measure the number of affected residents; people unable to use the complaint channel are missing from the sample. When a sponsor says ‘everyone wants faster service’, ask who ‘everyone’ includes, how the preference was measured, and whether speed matters more than reliability to different groups. The point is to expose narrative limits before assigning decision weights.
Write assumptions as propositions that evidence could defeat: ‘the operations team can provide a flexible service without more failures’ or ‘increased demand persists beyond one season’. For each assumption, note how its failure would affect the alternatives, evidence for it, evidence against it, a feasible test, and a date. A critical assumption could reorder the options if false; it is not merely an interesting idea. Prioritise testing by the assumption's effect on the choice and the possibility of credible evidence before the deadline. A high-impact assumption that cannot be tested now must remain visible through staged commitment or a review condition. A low-impact assumption should not consume a week before a decision. If parties disagree on a value criterion, such as priority for underserved districts, do not pretend a technical survey resolves the value judgment. Show the owner how two plausible weights change the recommendation and leave the normative choice explicit.
Use short, open interviews instead of questions that invite superficial assent. Ask an operator, ‘What would stop the trial from working?’ Ask a user, ‘Which trip fails now, at what time, and what did you do instead?’ Ask a critic, ‘What evidence might change your view?’ Record each answer as one person's account from a known sample, not a population fact. Compare accounts with operations data or direct observation where feasible, and deliberately find someone the sponsor did not invite. The interviews are not a statistically representative community survey. Their value is in revealing assumptions and risks absent from tables. Preserve disagreement rather than fabricating consensus; separate shared facts, competing interpretations, and different goals. If the owner insists on choosing today, make the remaining unknowns and the cost of an irreversible choice explicit.
Before sending the map to the board, run a simple reversal test: suppose the number of poorly connected students is twice management's working assumption. Would the full platform still outrank the trial or better in-person provision? No invented population estimate is required for this hypothetical sensitivity check. It reveals whether the option order depends on a missing group. If it reverses, sampling access becomes more urgent than asking another general preference question. If it does not, document why the ranking holds without claiming that the group does not matter. Keep separate the people affected by a choice, the people who can veto it, and the people who can supply evidence. One person may occupy multiple roles, but the roles answer different analytic questions.
Lesson summary
Use short, open interviews instead of questions that invite superficial assent.