Are 64% of Features Really Rarely or Never Used?
A very oft-cited metric is that 64 percent of features in products are “rarely or never used.” The source for this claim was Jim Johnson, chairman of the Standish Group, who presented it in a keynote at the XP 2002 conference in Sardinia. The data Johnson presented can be seen in the following chart.
Johnson’s data has been repeated again and again to the extent that those citing it either don’t understand its origins or never bothered to check into them.
The misuse or perhaps just overuse of this data has been bothering me for a while, so I decided to investigate it. I was pretty sure of the facts but didn’t want to rely solely on my memory, so I got in touch with the Standish Group, and they were very helpful in clarifying the data.
The results Jim Johnson presented at XP 2002 and that have been repeated so often were based on a study of four internal applications. Yes, four applications. And, yes, all internal-use applications. No commercial products.
So, if you’re citing this data and using it to imply that every product out there contains 64 percent “rarely or never used features,” please stop. Please be clear that the study was of four internally developed projects at four companies.
This article was originally published in the Mountain Goat Software blog. To get these articles delivered to your inbox, sign up here.
Product Delivery @ Canva
8 年This is quite insightful, thank you. Have to admit I was one of those who has been repeating this (even in a paper I wrote some time ago, which will have to revamp). Nevertheless, this shows how necessary a proper study in the field is.
Principal Technical Program Manager | Strategy and Program Management Leader
8 年Too much of anything is bad and i see a lot of references to this chart. Good to know that this was a survey taken by analyzing only 4 internal products.
Director Software Engineering at Cisco | Ex - Zoho | IIM Kozhikode | NIT Rourkela.
9 年In SW one reason may be - less investment in researching the market/customers before composing the features - so the outcome is expected..
Your CTO on hire | Product Managers' Tech-comrade-in-arms | Hands-on Server-side Rust, Java, Scala programmer |
9 年64? Huh? I knew a lot is never used but that's an eye-opener for me.
5G RAN | SW DEVELOPMENT & LEADERSHIP
9 年Hey Mike , Interesting update . Excellent example of constructive challenging ,avoid taking things on face value ,rather pursue to find or contribute towards answer.