Product Usage vs. Product Utility
It sounds simple, but don’t mistake product “engagement” for product quality
A common metric cited to measure software product success is Monthly Average Usage — “MAU” — how many users does a product have in a given month?
It’s a quasi-standard metric, but I challenge teams to think hard about the difference between Utility and Usage — they aren’t necessarily the same. And in fact, I’d argue over the long run, can be inversely correlated.
Get Matt Sly’s stories in your inbox
Join Medium for free to get updates from this writer.
My favorite example to cite is TurboTax. I have serious respect (and equal parts pity) for the team that has been able to build out, maintain and update the state machine that emulates all the permutations of the state and federal tax codes.
TurboTax is a great product. I give it an enthusiastic 10/10. But I really, really, really don’t want to use it very often or for very long. In fact, the less I use TurboTax, the better I feel about the product. As TurboTax gets better and better, usage should go down, as it’s increasingly easier to do my taxes. In fact, the ideal would be that TurboTax just does my taxes for me and I never have to even use the product at all.
If you looked at TurboTax monthly usage between April (after the tax deadline) and May, I’m sure it would take a nosedive. A lazily designed analytics system would set off red alerts and meetings would ensure and PMs would get in trouble.
Another product example are the many (too many, IMHO) CRM ecosystem products. Ultimately, you want your customer teams talking to and helping customers — not using software. Sure, software is a useful tool to help them be more productive in doing so…but it’s a means, not an end.
And, getting more provocative here, even with social networks — does increased usage necessarily correlate with utility? If I have to spend more time wading through updates or ads I don’t care about, maybe my usage goes up, but my utility goes down. If Facebook is able to tune its newsfeed algorithm so effectively that I can spend less time in the product, I’m a happy customer.
Our fundamental goal as product developers is to allow people to be productive and enjoy their life. Software is a means to end. Indeed it is “eating the world”…but, ironically perhaps, in the long run, the more pervasive software becomes, the less “usage” (in the traditional sense) occurs — it’s everywhere, but, in the long game, should really feel like it’s nowhere. As Arthur C. Clarke penned: ”Any sufficiently advanced technology is indistinguishable from magic”








