Track feature value

Published by Søren Houen on

From the hidden cost of long-tail maintenance we see the cost of maintaining a feature in your product. We know a feature costs money, and the more features you build, the more each feature costs.

Because of this it is important to track the performance of your features. By tracking them we can remove those that do not perform.

To track performance, first we must try to quantify how much true business value a feature is bringing in. Did you change the way the signup process works - how did that affect drop-off rate during signups?

The best way to get data on which features are performing is with raw analytics data. So a feature introduced a new call-to-action (CTA) button on a page. How is that new button converting? Do not simply look at the raw click-through rate. Here are some suggestions:

Tracking non-trackable features

Sometimes, there is no simple or hard-and-fast way to measure a features performance. But we must still make an effort to try. At least make it a regular topic in the regular product meetings.

Just opening a conversation around “how is feature x, y and z performing? And how do we know they are performing this way” will improve your product pipeline. The last part is very important.

It is not enough that someone simply states that something is performing wonderfully. These are likely the same people who pitched the feature in the first place. They put their ass on the line to make this happen. Of course they are going to stand up for their work. We need to understand how we know that something is performing.

We prefer data. Sometimes we don’t have that. We only have feelings and anecdotes. At the very least we need to know how we arrived at a feeling concerning a feature.

Revisiting my work guide.

I have been working on a work guide for a while now. That is an understatement. I started it in 2011. Then I left it to sit for many years. I will try to revisit it again now in little bite-sized posts.

See the work guide page for all parts.

· software development, work guide, product development, reducing risk