SlideShare began with an idea. We built it on instinct, launched it. People liked it, it grew. Our active users wrote to us, blogged, sent us feedback about what they liked or did not like. We took that into account as we planned features.
Its great to listen to active users, but it can bias you towards the superuser. As our userbase is growing, we need to take into account the different user segments, the people who don’t blog and write to us.
There is only way to keep in mind all the user types, to end the endless debates within the company about what we need to do next. And that is to be driven by data. Period.
For the past few months, I have become increasingly focused on data. Every feature we build, we think of metrics we will track. Once we launch, we watch those metrics change, decide how to refine, what to add, what to take away (yes, we regularly take away stuff that is not working out).
How we track metrics
-Server logs: This gives us broad about overall activity, but its often too broad to be actionable.
-Google Analytics: Its easy to setup Google Analytics out of the box, but you can get more sophisticated and track your users on a more granular level. Currently, our Google analytics is very basic. In the next week or more, we will be making adjustments to become more sophisticated in our tracking and track some metrics that we care about.
-SlideShadow: Its our internal shadow app, a dashboard that tracks a bunch of metrics on a hourly basis. As we add more features, the shadow app is increasingly getting more complex. This is the primary way we monitor what’s happening on SlideShare.
-Feedback emails / Blog posts: While each feedback mail is just one data point, we try to pay attention to trends.
-Database reports: The final, most flexible method is to simply generate the reports that you need, when you need them. Its too much to put every bit of data you need into SlideShadow. So if we need data fast, we write a custom sql query and save it in a mysql client that is pointed at a slave database. Reports written this way that turn out to be useful are migrated to SlideShadow.
With metrics, I have realized that the mindset is important. When we think of new features or refinements, I try to think with a metrics mindset. Why are we building this? What metrics are we trying to impact. There are four or five core metrics that a website like ours cares about, and pretty much every change relates to one or more of this. This is also helpful in working with developers. They are aware of what metrics they need to impact, and the success or failure of a project is very clear – did the metric move in the right direction.
As we grow (both the site and the team), I find that metrics is good way to manage growth. It helps me stay focused!
What metrics do you use? How do you use them? What helps you stay metrics-driven?