thinking-jobs-to-be-done

Guides product decisions by identifying the progress users seek, comparing existing workarounds, and ranking opportunities against evidence.

When to use it

Use when deciding what to build or prioritize, explaining low adoption, mapping competing workarounds, or resolving contested product positioning.

Give it product evidence such as a spec, tickets, notes, or logs; it returns a decision artifact covering user progress, competing alternatives, outcomes, priorities, and evidence gaps.