Research: A review of what data we collect from our users, and what we can use to improve our site #2071
Labels
data
Issue involves data management and analysis.
Feature: Analytics
Google Analytics, Microsoft Clarity, other instrumentation & tools
Ready for dev lead
Issue ready for dev lead to review
Research
Role: User Research
Tasks related to understanding users, needs, context
size: 8pt
The lift to complete this user story 16-24hrs
Overview
What data do we / can we collect from our users? This is super useful for researchers and FO planning.
This small project would involve a researcher and a dev who can gather info about how we process user inputs (from the search field, from pressing buttons, etc.)
Usefulness: 4/5 (where 5 is extremely useful)
Description
To help us improve our site, we’ve been relying on various analytics packages (like Google Analytics), but they are very difficult to use and actually, we have much better ways to learn about how our users use our site — by anonymously collecting what they enter into the search field, what orgs they view and share.
So with that in mind, let’s do an audit of our capabilities:
This project would probably involve a researcher talking to devs, perhaps John D, to learn about what we do and then evaluate level of difficulty of collecting additional data.
Along the way, this will likely spur some ideas for what data we can also collect or how we can use collected data to infer our user’s needs. It could also be useful for Hack for LA data miners to report and help other food-provider organizations or government.
Examples
Discussion
Some thoughts about how we can use this data in our own analysis
If we can collect address inputs and default languages, we can map that out to find out hotspots of need. Cross-reference that with a population and language needs map, we can discover if we’re overlooking particular language needs.
We may also able to find out if there are too-few food providers in certain areas.
Hack for LA is already doing data-mining to show food provider deserts and the like. They would surely love additional details if we can provide it.
Action Items
So with that in mind, let’s do an audit of our capabilities:
Part 1: Audit
Part 2: Export data
At this point, this might spawn sub-projects:
Part 3: Build new capabilities, if there are things we want
Resources/Instructions
This will involve working with devs and asking questions.
One industry term for this is ‘instrumentation’ — i.e. instrumentation = tools we have built into the app that gathers metrics and measurements. Like “what type of instrumentation do we have on our site?”, or ‘adding instrumentation’
The text was updated successfully, but these errors were encountered: