jobs-to-be-done

To conduct customer discovery interviews for jobs-to-be-done, you analyze timelines and interview data to reveal true customer jobs, emotions, and social dimensions. This process identifies the actual progress customers seek without naming specific products.

You identify non-obvious competitors using JTBD by considering all alternative ways customers hire solutions for the same job across different categories. This maps competitive landscapes beyond direct feature parity to broader customer progress alternatives.

The four forces of progress—Push, Pull, Anxiety, and Habit—apply to product design by mapping interventions that reduce switching barriers and friction. This framework helps teams design solutions that overcome customer hesitation and habitual resistance.

You can align product roadmaps and metrics around customer jobs by defining job-based metrics that guide decisions and measurement. This approach prioritizes features based on job completion and customer progress rather than feature speculation.

You should use a job statement instead of a feature request when you need to describe customer progress in concrete circumstances without naming a product. This format captures the desired outcome and result, preventing premature solution assumptions during product discovery.