-
Notifications
You must be signed in to change notification settings - Fork 38
Clearly document audience #7
Comments
For who is using it now, there's database, plus we can always do a Google Poll that saves data in Google Spreadsheet. Share through social media etc. Gives a decent probe without doing interviews. Also I think we should talk to people who do a lot of Open Source. I know a few :) |
Though we don't presort people (the way Patreon and Subbable do), there are two basic categories:
We have some basic stats on our Stats page:
|
Amongst givers, there's a further distinction:
Based on the content summary on IA (snapshotted below), I infer that we have roughly 25% general givers, and 65% specific givers (though this data isn't scoped to these categories by any means). |
Some relevant threads:
|
Another way to slice the pie is:
We started with a strong focus on individuals, and then gradually realized we needed some higher level of aggregation. Groups are supported in a two ways:
The Communities feature is kind of related (and we sometimes confuse people with the difference between Teams and Communities and plain old accounts that represent a company/non-profit/etc.). |
The individual/group distinction is orthogonal to the giver(specific/general)/receiver distinction. I don't have numbers to demonstrate this, however. |
@whit537 Nice wrap up 👍 |
Started a page on this: http://building.gittip.com/audience/. |
Where is it linked from? |
@zwn It's now linked from the homepage. |
Namely, http://building.gittip.com/. |
We need to understand the two different types of user groups:
We then need to document who these people are, where they are, what they care about, and make them real.
Without a real understanding of the audience we don't know who we're designing for, what to say, how to say it, where to say it, etc.
The text was updated successfully, but these errors were encountered: