Feature lists != experience

Posted by Mark Wickersham on Mar 17 2011
Articles >> Design

 I see it over and over.  In every area. From phones to mainframes.  "Why would you spend X for product Y.  Product Z has >= specs, and is cheaper.

The reason is simple.  While missing a certain feature may be a deal breaker for me,  just because a product has a set of features doesn't mean it'll serve my needs.  I'll take cameras as an example.  I want manual controls.  I'll spend good money for them.  But every little cheap point and shoot is offering manual controls now.  Not that I could use them.  They're usually buried so deep in the UI that I couldn't possibly get to them before my subject is nothing more than a memory.  An un-captured memory.  The camera, to be useful to me, must do what I want.  Instantly. Intuitively.  Smoothly.  It must not "get in the way" of the moment.  And, for me, that only starts to happen somewhere around the $500 price point.  It's not the money I spend that makes the camera.  It's the fact that some manufacturer is willing to spend the time, materials, and effort to understand what a photographer needs.  And then build a product aimed at photographers who know the difference. 


Think of this the next time you see a list of specs for a phone or a tablet being touted as critically important. "See!  This has better specs than..."  does not necessarily mean that the total experience of owning the product will be satisfactory. 

Last changed: Mar 17 2011 at 1:11 PM