Jobs To Be Done

This walks you through the Jobs-to-be-Done framework to figure out what customers are actually trying to accomplish, not just what features they say they want. You'll map functional jobs (tasks to complete), social jobs (how they want to be perceived), and emotional jobs (feelings they seek or avoid), then dig into pains and gains in a structured way. It's most useful during early discovery, repositioning, or when your roadmap feels like a feature wishlist instead of solving real problems. The framework forces you to separate the job from the solution, so "communicate with my team" instead of "I need Slack." Solid for product validation before you build, less useful if you're already knee-deep in implementation.