Discover what stakeholders value

Value to a person and product behavior

Identifying participants is a first step; discovering what they value in the product is additional work. An APS owner may value being able to explain an instruction’s state before retrying it. A Business team may value knowing early that a rejection requires action.

Both may request a dashboard, but that request alone does not reveal the important outcome or the consequence of losing it. Ask which decision the information supports, what changes if it arrives late and under what circumstances the person would accept an alternative.

Record the distinction between valued outcome and suggested solution. A dashboard is an option; confidence in state and the ability to respond are candidate outcomes. Do not assign preferences automatically by job title: two operators may face different conditions and consequences.

Analysis needs supplied and confirmed information, not an imagined persona used as a substitute for participation.

Questions that reveal consequences

Start with a concrete episode: at the last closing with an uncertain state, which decision was blocked and what information would have enabled progress? Then ask for an example where the same capability would make no difference. Comparison helps avoid generic answers such as speed, security or ease.

Explore what improvement means: fewer uncertain retries, less time before identifying a necessary action or less effort explaining an outcome to a client. The stakeholder need not provide a final metric during the interview. They may describe a consequence that later analysis and collaboration turn into a measure.

Keep their language and the analyst’s interpretation in separate fields. When someone requests more alerts, ask which decision they are missing and how they would recognize a useful alert. More notifications may add noise; value may lie in an actionable warning at the right time with an understandable origin.

Make preference conditions explicit

Use bounded comparisons to explore trade-offs without promising a solution. In an exercise, option A shows a response in ten seconds but does not distinguish pending from completed; B takes twenty seconds and distinguishes those states. A person may prefer A when viewing an already reconciled instruction and B before deciding on a retry.

This does not establish inconsistency. The decision depending on the information has changed. Record the scenario, presented options, attributes held constant, choice and rationale.

Ask where the preference would change: until when is extra waiting acceptable and with what consequence? Do not turn a hypothetical choice into a contractual commitment or approved latency. If option cost, coverage or accessibility is unknown, retain that limitation.

Comparison discovers values and conditions that will inform prioritization; it does not yet establish feasibility or determine investment.

Interpret votes and scores without invented precision

A hundred-point allocation can help one person express relative priorities within a supplied scenario. Giving sixty points to state confirmation and forty to speed does not make the points euros or guarantee that the first outcome is worth one and a half times the second in every situation.

Automatically adding points across groups with different populations or mandates is also unwarranted. First confirm that they received the same definitions, conditions and scale. A vote with twenty day participants and two night participants describes who responded; it does not establish that night value is ten times smaller.

To understand that perspective, elicit its missing context and consequences. If an agreed aggregation or weighting rule exists later, apply it within its limits. Value discovery supplies information for that decision without inventing a governance rule for computational convenience.

Retain differences useful for prioritization

Return a short summary to each source to confirm understanding: in a retry context, they value distinguishing pending from completed because it reduces decisions made with unknown state. Record whether the source confirmed, corrected or has not responded.

Retain differences representing real work rather than removing them to produce an apparently consensual list. Participants may agree on avoiding duplication while differing on waiting tolerance. The information can justify alternatives, phases or a trade-off decision by the authorized owner.

In international teams, send terms and examples before the session and allow a written response with time for review. Confirm translated meaning, especially where words such as accepted or executed imply different commitments. Confirmation of the record establishes intended meaning; it does not automatically approve a baseline, a control exemption or the implementation choice.

Workshop: from preferences to a usable record

Open part A of the workshop. Business requests an immediate message; the APS note describes retries without knowing whether the previous request finished; the night team wants to understand a rejection without contacting an unavailable person.

For each note, write a valued outcome, a consequence, a condition still needing confirmation and a neutral question. Then compare an informational inquiry with a retry decision involving uncertain outcome. The worked reasoning explains why the same person may choose speed for the first and confirmation for the second.

There is no universal priority table to discover. In your summary, separate what was actually said, interpretation and what remains hypothetical. Complete the response template before consulting the example.

Review it against the rubric: sufficient context, a non-leading question, no invented priorities, retained origin and explicit limitations. Notes and answers were created for learning; they do not represent completed interviews or an institution’s internal policies.

Common pitfalls

Job title treated as preference; vote counts treated as value; subjective scores treated as money; a desired condition treated as an approved obligation; changing the scenario without revisiting interpretation.