Identifying the aha-moment(s) to reduce time to value

Hi there,

I am currently thinking about how to identify the aha moment(s) of (new) users based on the quant data in Pendo? (supplemented with follow-up qual research/interviews)

Anybody can share some best-practices on leveraging Pendo to identify aha-moments? 

A special challenge is that we are currently an onboarding-heavy product with lots of CS interaction. 





  • Hey Jan,

    A way to get to the "aha" moments for your new users is to think about what parts of your product provide the most value to your new users ("aha"). Then get them to those locations as fast as possible, while maintaining full visibility of adoption. 

    We have the Core Events and Product Engagement Score (PES) concept which helps you name your product most important areas, and track how they impact user growth, stickiness and retentions.

    If you need help arriving at the "aha" moments, our Professional Services team can help (if interested reach out to your AE or CSM). We offer a workshop to help you identify "aha" moments, then set up core events, identify a PES baseline and goal setting for continues improvement.

    I hope this helps!


  • Hey all, I have a similar question: How do I specifically find the TIME metric on Pendo. I've identified my core event (assigning a course to users), but don't think that looking at total clicks on that feature for users in their first 30 days, 30-60 days, and 60-90 day segments is getting at TIME to value.

    Basically, how do I see how long it's taking a new user to click into "Assign a Course"? An actual time metric of days/hours/etc. ??

  • Hi Brittany Perna, if you have already defined this feature as a core event then you should be able to add the widget 'Core Events: Time to First Use' to a dashboard to give you the average amount of time, in days, it takes users to engage with the core event.

  • Thanks Niall Geraghty, that got me what I needed!


Please sign in to leave a comment.

Didn't find what you were looking for?

New post