In July 2017 we have the Data Scientist's Challenge: Data-driven web design with A/B testing and experimentation.
Jordan Read and the Data Science team from the Office of Water Information help us think about how we can get quantitative information for improving science communication through our websites and apps.
This is a very timely topic since it is related to the issue of user needs and user experience for our sites and apps, which came up at our CDI Workshop.
"Use data, not opinion!"
Comment below to continue the discussion, we'll come back to share the results at a future monthly meeting.
How do you decide how to add a feature?
What metrics do you use to judge feature success?
What types of applications/websites are high priorities for testing?