| A | B | C | D | |
|---|---|---|---|---|
1 | Use Case Guidelines | |||
2 | A Good use case is..... | A Not-so-good use case is... | ||
3 | ||||
4 | > | Linked to a major product change made recently | > | Vague |
5 | Ex. 1: We removed 3 steps from our *checkout flow* and don't understand how that impacted our checkout conversion | Ex. 1: I would like to understand the 3 drivers of retention | ||
6 | ||||
7 | Ex. 2: We recently added 3 more features to help customers discover relevant content. We don't know if that has increased the amount of time user spends in the app | Ex. 2: I would like to figure out how to improve conversion | ||
8 | ||||
9 | > | Attached to a product team's decision/hypothesis | > | Unclear on objectives |
10 | Ex. 1: We are unsure if we should continue investing in our 'Favorites' feature and would like to understand if that feature is impacting our <enter business metric> | Ex. 1: Expand data access for product (or marketing) teams to make decisions about business | ||
11 | ||||
12 | Ex. 2: We are trying to prioritize between 3 features that we need to invest in and we would like Amplitude to help us identify which one of these features has the highest impact on our <enter business metric> | Ex. 2: Be more data driven as a product team, stop relying on the analytics team for insights | ||
13 | ||||
14 | > | Immediately actionable | > | Not measurable |
15 | Ex. 1: We would like to understand the key flows within in our product so we could build funnels on those to track which steps have the highest dropoff. Knowing this would help us build features to minimize the dropoffs and increase our conversion | Ex. 1: Understand performance of our product teams' efforts | ||
16 | ||||
17 | Deck link | |||
18 | ||||