EN.662.692 Chap.4 Stakeholder Jobs and Outcomes
Stakeholder Jobs and Outcomes
Describe progress, not the product
A stakeholder job captures progress someone wants in a circumstance. Functional, emotional and social dimensions may overlap, yet each adds a different constraint.
The product or feature is one possible mechanism for progress and should remain outside the job statement until alternatives have been compared.
Surface tension between stakeholders
Users, frontline staff and decision makers can value different outcomes inside the same process.
The chapter maps those differences, avoids compressing them into a generic better experience and converts evidence-backed jobs into design principles. Adoption risk remains visible even when an option succeeds technically.
Move from a quoted request to a supported job
Begin with a concrete circumstance and a progress verb.
A stakeholder who asks for a dashboard may be trying to notice exceptions early, coordinate a handoff or demonstrate control to another audience. Those are different jobs with different evidence needs. Ask about the last specific occasion, the trigger, the workaround, the trade-off and what counted as satisfactory progress.
Behavioural detail does not automatically reveal motive, but it provides a stronger basis than accepting the requested feature as the need itself.
Keep functional, emotional and social dimensions distinct enough to reason about them. A frontline employee may need to complete a transfer accurately, avoid appearing unprepared to a customer and preserve trust with a colleague.
Improving the functional step while increasing social exposure can undermine adoption. State each job as a hypothesis and attach supporting and conflicting observations. If a dimension rests on one vivid interview, label that limitation rather than turning it into a universal persona.
Compare stakeholders before deriving design principles.
Map where progress is shared, where constraints differ and who bears a burden created by another party's preferred outcome. A manager's desire for standard visibility may conflict with a user's need for discretion or a worker's need to exercise judgment.
The resulting principle should guide comparison without prescribing a feature, such as make exceptions visible to the authorised decision maker while preserving contextual explanation. Validate the principle against several plausible options, then specify what future observation would cause the team to revise the job or acknowledge a new stakeholder tension.
What this chapter covers
- 01
Functional jobs
- 02
Emotional jobs
- 03
Social jobs
- 04
Contextual progress
- 05
Desired outcomes
- 06
Stakeholder tension
Worked example · free
Map jobs for a return service
- 2State the customer's contextual functional job.
- 2Add emotional or social progress.
- 2Translate the job into a testable constraint.
Key terms
- Stakeholder Job
- A Stakeholder Job describes progress a person seeks in a particular circumstance.
- Desired Outcome
- A Desired Outcome explains how successful progress would be recognised by the stakeholder.
- Adoption Constraint
- An Adoption Constraint is a contextual condition that can block use even when an option functions technically.
Stakeholder Jobs and Outcomes FAQ
How is a job different from a task?
A task describes an activity visible in the process, while a job describes the progress a stakeholder is trying to make in context. Returning a container is a task; completing a meal without adding a difficult errand may be the broader functional progress.
Why separate functional, emotional and social jobs?
The dimensions reveal different reasons an option may succeed or fail. A service can perform the functional task while creating anxiety, loss of control or an unwanted social signal. Keeping them distinct helps teams translate stakeholder evidence into more realistic constraints.
How should conflicting jobs be handled?
Map each stakeholder's desired outcome and constraint, then identify the governance trade-off the decision maker must resolve. Do not claim one option satisfies everyone by definition. Compare alternatives, state whose burden changes and define what evidence would make the trade-off unacceptable.
Assessment move
Choose a familiar service and write separate jobs for a user, frontline worker and manager. For each, add the circumstance, progress verb, desired outcome and constraint. Remove every product noun. Introduce one stakeholder conflict and explain the decision required rather than smoothing it away. Finish with an observation that could disconfirm each job hypothesis.
Use one recent incident rather than a generic preference to support each statement. Mark whether the basis is reported motive, observed behaviour or your interpretation. Derive a design principle that could guide at least three different options, then test whether the principle protects one stakeholder by shifting an unacceptable burden to another.
Working through Stakeholder Jobs and Outcomes in EN.662.692? Sia is AskSia’s AI Management tutor — ask any EN.662.692 Stakeholder Jobs and Outcomes question and get a clear, step-by-step explanation grounded in how EN.662.692 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.