Helped us quickly launch and test MVP
Overall Satisfaction with FullStory
When we developed the product MVP, we needed to understand on the first users how they behave on our platform. We chose the solution that seemed to us the most suitable for this, and we were not mistaken. I spent only half an hour a day studying user behavior and based on this, I immediately wrote new tasks and errors to the backlog.
Pros
- View only actions in video.
- Fast rewind without losing focus.
- Triggering events.
Cons
- Iframe still not recorded.
- Sometimes missing fragments in video.
- Need more customization for triggers.
- Prevent bugs.
- Spent less time for finding bugs.
- Spent less time talking about details with user.
- Hotjar and Yandex.Metrica
FullStory focus on one important feature and do it really well. all other solutions are inherently harvesters, multitools, they are overloaded with features and unnecessary information. The system is convenient for both the pros and the beginner to work with, but other solutions are not so friendly in terms of usability.
Do you think Fullstory delivers good value for the price?
Yes
Are you happy with Fullstory's feature set?
Yes
Did Fullstory live up to sales and marketing promises?
Yes
Did implementation of Fullstory go as expected?
Yes
Would you buy Fullstory again?
Yes
Using FullStory
4 - All the people from product team in our startup using Fullstory on everyday basis to discover and solve business issues. It's a great altrernative to tons of Customer Developement interviews if you have no time but have a ready-made product.
Their roles:
- CEO/Product Owner
- R&D Manager
- CTO
- Customer Happiness Manager
Their roles:
- CEO/Product Owner
- R&D Manager
- CTO
- Customer Happiness Manager
1 -
Our Customer Happinness Manager on the daily basis do perform such tasks:
- analyze customer behaviour through the website
- analyze summary for website usage
- react to red flags raised by another members in the product team
- raise the flag in the critical cases
- describes the found issues in the product backlog
- Cutomer behaviour paths detection
- Looking for the issues in the interface and business logic
- Monitoring website stability
- Ticketing system via raised flags by all people in the product team
- Knowledge base of the video records for important cases
Comments
Please log in to join the conversation