-
Website
http://avc.com/ -
Original page
http://www.avc.com/a_vc/2009/10/the-cohort-analysis.html -
Subscribe
All Comments -
Community
-
Top Commenters
-
ShanaC
1217 comments · 71 points
-
daryn
213 comments · 14 points
-
kidmercury
827 comments · 103 points
-
howardlindzon
207 comments · 71 points
-
Charlie Crystle
203 comments · 35 points
-
-
Popular Threads
-
Getting Computer Science Into Middle School
1 day ago · 259 comments
-
End of Year Music Posts
22 hours ago · 39 comments
-
How To Get Me To Hang Up On You
3 days ago · 158 comments
-
Open APIs and Open Standards
4 days ago · 207 comments
-
Trading Deals, A Lost Art?
2 days ago · 78 comments
-
Getting Computer Science Into Middle School
Thanks for the post!
-john
the ying and yang of product management.
How do you get their advice? I'm finding interviewing people on the street is not enough...
For example, they talk a lot about 'power users' who they select first up and let trial their products. Once they have their power users in play, they then watch the data and iterate, measure, iterate etc etc...Surely, the use this kind of analysis to parse the mass amounts of data they have into usable, relevant stats.
No start-up, I know, but interesting none the less. Thanks again for the post. Great post Fred - thanks for sharing. From what I've heard (and we have all seen with the launch of Google Wave) it seems Google do a very good job of measuring chorts of users. We interviewed the MD of Google Australia and NZ, Karim Temsamani, about a month ago and we asked him a few questions about how they do "metrics." If you're interested, you can see the video here (http://www.vimeo.com/6844800)
For example, they talk a lot about 'power users' who they select first up and let trial their products. Once they have their power users in play, they then watch the data and iterate, measure, iterate etc etc...Surely, the use this kind of analysis to parse the mass amounts of data they have into usable, relevant stats.
Google is no start-up, I know, but interesting none the less. Thanks again for the post. :)
will be so much better than replies which was a shitty way to do that
How about we meet half way... can everyone have an automatic list
generated of the last 10 people they replied to and the 10 people they
reply to most? I think I'd shutup about replies if we had that.
Otherwise, lists will be about as good as #followfriday.
1) Posts from people I follow containing links
2) People retweeted or favorited 3+ times for the keywords 'new york', 'nyc', 'venture capital', or 'vc'.
3) Last 10 people @fredwilson replied to (which is a list that I could create even though I'm not Fred Wilson, based on Fred's public data)
Could make for a cool third-party app based on some of the new API calls.
but your idea of an automatic list is interesting.
i'll make sure the twitter team hears that one
This would actually be more organic than the act (read: chore) of creating a list. It's easier, faster, more intuitive, and would in the end IMO result in the creation of more/better lists. Here's a quick overview of how it might work; I mark my favorite accounts with the "I recommend" button and they automatically get posted in my "I recommend" folder, which is public. I can mark them either by going through my follow list or as they appear on my timeline. I can do it purposefully or spontaneously as the situation dictates. When it gets to the point where sub-lists, or categories make sense within my recommended list I create them at that point.
This lowers the bar in terms of effort needed to engage, will result in a much higher level of participation, and will simultaneously create a siphon effect for the creation of "lists" as Twitter currently envisions them. Because in the end doesn't higher participation almost guarantee more and better recommendations in the aggregate?
As an app developer I'm much more interested in getting access via the API to those two silos of information than I am to some much smaller data set of user-defined lists, for a variety of reasons.
Again, I think lists are fine. I just don't think that by themselves they're going to deliver on their promise for either end-users or app developers. The bar is unnecessarily too high for initial user engagement.
Someone should build a list creater app that allows me to create certain
filters... like people I follow that are near me, people I RT the most,
people who tag things #nextNY that I follow, etc.
Great post Fred on cohort analysis... it's something we've been working on perfecting @totspot... no easy task to nail this type of analysis, but leads to very rich understanding of your users and changes to your app.
Update: btw, here's the alpha link to Twillist: http://alpha.twillist.com
You have a pretty big presence on the web, what happens more often, you finding relevant people or relevant people finding you?
I'll shoot you an email in a bit.
Yet I know it should be more than that...without good metrics, I am unsure what to mold it to.
Cohorts in this definition are simply feature sharing user subsets. Classification studies use feature description vectors in engineering to characterize objects. Simple Gaussian, multi modal gaussians, or even novel statistic functions can be used as models for data representation. A friend at work is doing scatter charts which relate to probability of detection (he's focusing on just normalized filter outputs).
The cool thing about classification is that the features aren't absolute. So member groups could be found by clustering (nearest mean recursive algorithm is straight forward), and there are confidence levels associated with subgroups (i.e. I'm 100% likely to fall into the "geek" category for this comment).
Also, if you're local to nyc and are interested in applying a rigorous metric process to your startup you should consider joining the lean startup meetup: http://www.meetup.com/lean-startup/ the events, and discussion list, are all about this.
I think you can easily get to complicated with measurement
Interview and observe your subgroups to see why they have the behaviors they have. You may not want to have a base of just power users. The people who have undesirable behaviors (aka not using your product) probably have a much more telling response than those who are using your product.
"All happy families are alike; but each unhappy family is unhappy in its own peculiar way."
the ying and yang of product management.Great points John, especially "real" connections to customers/users and the observer paradox (we often find patterns where there aren't any).
Although not familiar with the "cohort" terminology, the essense of this discussion reminds me of the host of behavioral matching technology startups that developed on the fringes of the SEM industry. The best of them, like www.magnify360, built what could be called cohort behavioral databases on a multitude of attributes and then tied into PPC campaigns charging strictly by performance upside.
By the way, we refer to cohorts as tranches, which in many ways they are. They've been really valuable for us in working on the Retention metric, for example what lifecycle emails we send, and when, and when we demote inactive users.
Imagine if you could build your own analytics to mine it...
-john
http://mashable.com/2009/10/06/study-traffic-so...
...which ranks social sites by how loyal the traffic they send is. This is related to your points about twitter vs. google in referrers - and is relevant here in talking about cohort analysis.
I would imagine the readers for this blog come in bumps when you have a popular post. How many of those readers from twitter vs. google vs. some other service stay to read more, or subscribe to your RSS feed, etc.
I've been designing a blog platform for myself (because I can), and will make a it a lot like a webapp - with sign on, user tracking, custom tools etc.
It will be interesting to integrate http://mixpanel.com and some other tools to track how readers on a blog behave.
When a development team makes design choices and then goes back to review traffic data to evaluate the success of their choices, they have to use a cohort analysis for their analysis to be accurate. You can't just look back over 2 months worth of uniques in Google Analytics to determine if a change implemented 4 weeks ago was actually successful. By using a cohort analysis you can isolate the variable of where a user is in their lifecycle of using their service, which allows you to more accurate assess how new features affect users.
Additionally a cohort analysis is a great way to assess the lifetime value of an acquired user. As you look at older cohorts, you can measure, on average, how long a user will stick with your service, and, depending on your business model, how much a user is worth to you. Once you know that number, you're golden because you know your allowable you can spend in marketing to acquire new users sustainably.
I agree that cohort analysis are our firm's favorite measurement, and the reasons above just scratch the surface of the valuable conclusion you can draw from a cohort analysis.
Another caution I would think of re: using cohort analysis when in startup mode is the sample size. What's the number of people in that Jan 2007 group vs. April 2009? Were there any comments made during the meeting re: applying a weighted average to the analysis? January 2007 has a cohort of 10 early adopters and April has 10,000 "mainstream" users.....
since Twitter is a network, i'd wonder how the the cohorts behave in relation to the network size increasing...and also, where are the pre 2007 folks? (aka the ones who were mocked for tweeting about burrito lunches in south park? )