Quantifying Users

Quantifying your project's users

This question is similar to last week's question, but focusing on user behavior.

Propose two experiments that might shed useful light on how people use your project. What would you seek to understand? How would you design the experiment? What would different possible outcomes be and what would they mean? What would be complications/confounding factors that make interpreting the result difficult?

Keep in mind that a "user" may be a developer. For example, you could propose measuring how many developers use a new API method you released. And you could provide different populations of developers with different announcements about the API (technical announcements, no announcement, announcements that have example code, announcements that have example benefits, etc).

Please submit your response by class time on each Monday. Here are the Journal guidelines and submission instructions.