Use automated customer data collection to look like a requirements genius


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Use automated customer data collection to look like a requirements genius

  1. 1. Session: Use Automated Customer Data Collection to Look Like a Requirements Genius<br />Session Leader(s): Mike Savory, Jodi Holt<br /><ul><li>Environmental Data is captured with behind-the-scenes analytics
  2. 2. Error Message Tracking
  3. 3. In capturing usage data – we also capture how much time they spend on screens. You may find that the numbers don’t add up – the usability issues may not be an issue. Screens may just not be relevant (i.e. transaction screens may be more relevant). Really need to compare numbers between time spent and usage.
  4. 4. Look at what reports people are generating. Who is using reports and what data is important?
  5. 5. Product Enhancement Program (In product surveys)
  6. 6. Create Surveys within product as they are doing the work. It is focused on the user that is actually doing the work.
  7. 7. Person buying the software doesn’t equal person using the software. If you don’t target the buyer, aren’t getting the right data
  8. 8. Ask questions about how they are using the product and where they want to see improvements
  9. 9. Weren’t always sure we were getting the right information
  10. 10. We can send surveys to certain segments
  11. 11. If we have a concept about a new product or feature – we can send it to a specific industry or flavor and get the targeted info we are looking for
  12. 12. Have a report we can fill out that enables us to determine what segments a survey should go out to
  13. 13. Once we get surveys, can slice and dice any way we want.
  14. 14. We try to be very careful with how often we inundate people with surveys and info – want to make sure they don’t get one survey after another.
  15. 15. All of this Sage built in-house
  16. 16. What is participation rate on survey? Answer – we can get anywhere from 3% on low end and 15%. We get a lot more participation on Monday than Friday, etc, so sending out on a particular day can really make a difference
  17. 17. Can look at data and say “How does this resonate with people using Windows XP vs. Vista?” etc.
  18. 18. Do Net Promoter Score tracking through our products. How do they feel about what they are using. This is important difference between buyers vs. users
  19. 19. When and whom you send the survey too will definitely impact Net Promoter Surveys. Be careful who you send the surveys to. May get very different scores from buyers than from users. Users are a lot more critical. A challenge for us has been to reconcile those two numbers.
  20. 20. When you put data surveys *in* the product, have to be careful on timing – want to make sure you don’t interrupt an important business cycle. However, the plus is you get a real-time look at it and can get the numbers immediately.
  21. 21. Types of surveys:
  22. 22. Product feedback
  23. 23. Feature Feedback
  24. 24. Partner Satisfaction
  25. 25. Trial product usage and satisfaction
  26. 26. We started 5 years ago and started small. Started tagging a few screens and every year we add more and more.
  27. 27. Keep survey intros generic because we found opportunities to repurpose surveys in other areas i.e. Recruitment.
  28. 28. Possibilities
  29. 29. Feature awareness
  30. 30. Product configuration
  31. 31. Contextual help
  32. 32. Intelligent up-selling/cross selling
  33. 33. Smarter error messages
  34. 34. Track NPS of customers by partner/recommender