Map the Job Before the Feature
Use Jobs to Be Done to translate a feature request into the underlying progress, constraint, and success measure.
The request is evidence. The job is the thing to reason from. Capture the circumstance Jobs appear in situations. Ask when the user reaches for the requested feature, what just happened, and what deadline or risk is present. Name the progress Progress is not the same as usage. The customer may want to reduce effort, gain confidence, coordinate others, avoid risk, or look prepared in front of a stakeholder. Compare solutions against the job Once the job is clear, compare options by job fit, cost, reversibility, and reuse. A smaller solution can be better if it addresses the real progress…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in