Feature Fatigue
5 min read · 4 principles · apply it by lunch
Good morning. The feature that wins the deal and the feature that keeps the customer are rarely the same feature.
Of the last three things you shipped because a prospect asked for them on a sales call, how many of the customers you already had have opened any of them since? You don’t have to guess — the number is sitting in your analytics this morning, and it’s almost always a good deal lower than the person who asked for it would believe.
In 2005 three marketing researchers — Debora Viana Thompson, Rebecca Hamilton and Roland Rust, then at the University of Maryland — published a paper in the Journal of Marketing Research that named something everyone had felt: feature fatigue. Their experiments did what most product research doesn’t bother with. They had one group pick a digital video player from screens and feature lists, and another pick after using one for a set of tasks. Before use, people reliably preferred the model with more capability; loaded with features, it simply looked like the better deal, so they picked it. After use, the advantage disappeared. Usability now weighed as much as capability in satisfaction, and fewer than half of those who had used the feature-rich model picked it to use again. The follow-up in Harvard Business Review in February 2006 was titled Defeating Feature Fatigue. The trap is that both halves are true at once and they arrive at different times: capability is what gets bought, usability is what gets renewed, and only the first has a salesperson reporting back on it. So the roadmap fills with things that close deals and empties of things that keep customers, and every quarter the call looks right.
Feature Fatigue is Day 340 of 365.
In the Daily, each of its four principles is explained in full, with a one-page template to apply it the same day. A new framework arrives every morning at 7am for a year, across all fifteen courses of the FutureMBA curriculum.
$29 a month · cancel any time · 7-day money-back guarantee