Connect a proposed feature to the user's job, pain, or gain before writing requirements.
The move: map the value before you map the feature. A feature request is often a hypothesis about value. The analyst's job is to make that hypothesis explicit. The Value Proposition Canvas gives you a compact structure: customer jobs, pains, gains, products, pain relievers, and gain creators. Customer job A job is what the user is trying to get done. It may be functional, social, or emotional. "Prepare for a renewal call" is a better job statement than "use CRM summaries" because it leaves room for multiple solutions. Pain Pain is what makes the job costly, slow, risky, embarrassing, or…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in