Distinguish stakeholder solution requests from underlying user jobs before writing requirements.
The first solution is rarely the whole requirement. It is a clue to a need, not proof that the need has been understood. Jobs to Be Done asks what progress a person or organization is trying to make in a circumstance. In requirements engineering, that gives you a practical filter: if two very different designs could satisfy the same need, you are closer to a requirement; if only one design fits, you may still be holding a solution. Ask for the circumstance Good requirements describe when the need appears. "During renewal prep" is more useful than "on the dashboard" because…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in