Simplicity to improve product/service quality
Your users will accomplish more, faster, with a product/service tailored specifically to them than if they struggle to apply an overly-generic product to their needs.
Many consultants, developers, and marketers compete to have largest quantity of features instead of competing to be most useful. Don’t believe me? Take a look at software marketing material: all features, rarely translated to benefits. Marketing firms and consultants do the same thing in their own way and call them capabilities lists. Where are the human benefits? That’s the tone of most markets.
“But features are by definition useful!” That’s true insofar as features are functions of a program, or more raw power. But you can hand your users as much raw power as possible and it doesn’t guarantee their ability to use it. Features are useless if they diminish user understanding or success. Does each feature justify the clutter it adds? Does it justify the complexity that compounds across the whole program/package/service? Does it really help your customers accomplish more with the epicenter of your product/service?
We all have our weak moments and throw a little more in for a sake of bulk. But the additional complexity can offset the balance of features to usefulness in a way that is a detriment to our products/services. Even if its just hidden away in your marketing, website, or interface: you’re making navigation/comprehension more complicated at best and you’re steepen-ing the learning curve at worst. Either way you’re presenting a barrier to customer success.
Jason Fried from 37signals explains less as a competitive advantage in software:
“Less Software allows you to distribute your time and energy across less features. More attention to less stuff will make that less stuff better. 100% of your time across 20 things via 100% of your time across 10 things will result in a very strong 10 things. And that’s the kind of software that is satisfying to build, and satisfying to use: simple, focused, useful software that’s really polished. And that’s how you win these days.”
The wise Kathy Sierra calls this “featuritis” and what she writes about it is true (great visual on the post). Featuritis will discourage your users and give your competition an easy way to one-up you.
This isn’t just for software firms. All kinds of products suffer, and all kinds of service business fall in this hole. So why do we get sucked in?
As you specialize your product/service (or change the feature to usefulness ratio), sometimes you are creating a tool that’s increasingly useful to a decreasing number of people (unless you’re specializing to the masses, covered elsewhere). For many entrepreneurs and small/mid-sized businesses, that’s a scary thought—we think about customers in quantity. When you feel the fear creeping in, ask yourself:
- But what about the happier users and the buzz they’ll create?
- What about the people who will pay a premium for the increased quality of your product/service?
- What about the marketing gains that comes from specializing?
- What about the business flexibility from specialization?
- What about the guarantees you can provide to a more specific market and how that persuades risk-averse prospects?
Trackbacks
Use the following link to trackback from your own site:
http://www.aarongerdes.com/articles/trackback/80