Turn a vague feature request into a JTBD interview guide
Build a short JTBD-style interview guide from a vague stakeholder request.
A stakeholder request says “customers need better alerts,” but the team does not yet know what job the alerts are supposed to help customers accomplish. JTBD interviewing starts from a recent story: trigger, progress sought, obstacles, workaround, and desired outcome. The common trap is writing questions that ask customers to evaluate an idea before they have described the last real situation where the problem occurred. Name the trigger moment Rewrite the request into a real episode: “Tell me about the last time you realized a workspace was going off track.” This opens a story instead of a feature wishlist. Probe…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in