As we've been working to revamp a couple of existing EdLab projects (Survey Sidekick
, Pocket Knowledge
), I've been thinking a lot about how people will be using these products and how we should design these tools so that people will prefer to use them over anything else. For example, with Survey Sidekick, I know that I've always preferred to begin the survey brainstorming process in a plain text editor before moving it to the actual creator. What features should Survey Sidekick therefore have to possess to compel me to use it through all stages of survey development? How do we redesign Pocket Knowledge so people think to continually return to it as a resource for research?
TechCrunch article discusses “habit testing” -- measuring and collecting data about user habits in order to understand who
your users are, what
aspects of the product is habit forming, and why
those qualities are habit forming.
Some things to ask while habit testing:
1. How often should users ideally be using the site?
2. How many users are currently meeting this bar?
3. Understand the “habit paths” of these users. What are the steps they took to using the product, and what hooked them?
4. Talk to users to learn why and how they use the tool. What about it has made them a devotee?
I'd like to keep these questions all in mind as we continue to develop each of our tools. I'm also wondering -- what are your thoughts on the best analytics tools to get insights on user habits?