Use Case or Jobs?
New to building / product. I want to start using a framework for designing and delivering features that people want and use and get value from.
What is better: Use Cases, or Jobs To Be Done?
Why?
Any examples or resources to share to help me learn more?
Thanks!
Use Cases feels a bit lighter weight to me which seems like the right approach for someone who is just getting started.
If I were you I'd really hone in on the learning to listen skills that are inherent to both these frameworks since being able to get folks to tell you what they really NEED (not want mind you) will be key to finding a successful niche.
I often recommend a summary of The Lean Startup as starting pt for ppl headed down this path. Good luck!
Very helpful, thanks @gimelgabriel!
I found this summary...let me know if you have a better one :)
https://tdevroome.medium.com/book-summary-the-lean-startup-2113c0cf4289