Product analytics can show that users leave at a particular step. Customer conversations can help explain why. This lesson brings those two forms of evidence together so a founder can choose a more useful next change.
Carlos Sanabria uses a CRM journey to show how setup, activation and retention connect. The product decision starts with the desired customer outcome, then works backward through the path to it.
What you'll learn.
- Use quantitative data to locate a pattern and qualitative evidence to investigate it.
- Define activation around a behavior connected to continuing value.
- Segment users and tie each product change to a specific outcome.
Use analytics to locate the pattern.
Examine acquisition, user paths and retention to see what happens after someone arrives. Where do people stop? Which actions do returning users complete? How does the pattern differ between groups?
These measurements give the investigation a starting point. A drop-off percentage is useful because it identifies a part of the experience worth understanding, rather than because it dictates a particular feature or redesign.
Investigate the experience behind the numbers.
Interviews, surveys, support tickets and session replays can provide context for the behavior. Look for the expectations, confusion and friction that the aggregate data cannot describe on its own.
Pair the sources around the same question. If the data points to a difficult setup step, ask users about what they were trying to accomplish at that point. That keeps research connected to the observed problem.
Map the path to the outcome.
In the CRM example, a long setup process can prevent users from reaching the experience that makes returning worthwhile. Mapping the successful journey helps distinguish necessary steps from friction that delays value.
Start with the outcome you want to improve, such as retention at a defined point. Identify the earlier behavior that may support it, then investigate what makes that behavior easier or harder. The roadmap becomes a set of changes to that journey.
Segment before concluding.
A broad average can combine people with different needs and experiences. Compare relevant groups before deciding that every user has the same problem or would benefit from the same change.
For each proposed improvement, record the outcome it is intended to affect and how you will observe that effect. Revisit retention and customer feedback together after making the change. This connects delivery to learning rather than treating release itself as the result.
Use the numbers and the conversations as complementary evidence. Together they can explain which part of the journey deserves attention and what a successful improvement should accomplish.
