Use Case is a complete user scenario in a product. For example, Create context-rich features specification, or Create and maintain public product changelog. Use Case can include many Features & Insights from different Product Areas.
Use Cases help to focus on user needs and not just add top features mechanically. Overall, it is better to release Use Cases than Features.
Examples:
Prioritize insights and features Prioritize insights and features
Create context-rich specifications / PRD Create context-rich specifications / PRD
Use Case is related to product strategy. For example, if you are focusing on product companies now, all current Use Cases should be related to product companies as well. Use Case is linked to Strategic Theme.
Use Case always has a person who will do it (Product Owner, Developer, etc). It may include many persons.
Use Case should be a dream scenario 🦄, but then grounded to what is possible 🐌.
Use Case is a complete scenario that focuses on some complete business process or practice.
💎 Good → Prioritize work based on feedback
💩 Bad → Undo recent changes (this is a Feature, but not a Use Case)
Try to use narrative, images and videos when describing a Use Case. It should resonate with the target persona.
Use Case links marketing and product development, it's a good sync point for these teams.
Use Case can be promoted on a web site, it can have an ads campaign, etc.
Use Case has several Features.
Use Case has the following states:
Icebox. Default state for all Use Cases.
Next. We are going to take this Use Case in near future.
In Focus. We are implementing Features to implement this Use Case or make it better. It is recommended to have 2-3 Use Cases in this state.
Archived. This Use Case is no longer supported or completely done and will not be improved.
We don't have a culture to focus on Use Cases right now and trying to fix this. Sometimes we take Features that are not relevant to current Use Cases.
Marketing is somewhat separated from product development.
