Unarticulated Customer Needs

I’d venture to say that most products and services are bloated with features that customers most likely don’t care for;  I’ve been part of product development teams where the focus is on features, with an implicit goal to stuffing as many features as possible — in consumer packaged goods and in software.   This is the wrong approach to developing memorable and sticky products.

The above statement might be best described by Kathy Sierra’s Featuritis Curve:

In my own personal venture in product and package design (a side project), I employ ethnography — the science of watching people do stuff; of learning about unarticulated customer needs, which is otherwise known as ethnography; Toyota calls it Genchi Genbutsu.

A.G. Lafley, the CEO of Procter and Gamble, understands this well:

JANUARY 28, 2005, Business Week

I wanted to get after what we call unarticulated consumer needs. What she wants that she can’t tell us about. And there are lots of techniques we have developed or are developing to do that. And two, I wanted to focus more on the consumer experiences as much as on the product and technology.

People remember experiences. They don’t remember attributes or benefits or features.  We talk a lot about how you create a delightful experience.  Now, when you’re dealing with underarm deodorants and cleaning dirty floors, you have to work real hard to try and deliver a less unpleasant experience.

The key phrase here is this:

People remember experiences. They don’t remember attributes or benefits or features.

What a simple, yet profound statement that still many, many companies fail to understand. 


Short URL: http://bit.ly/S9UU

Share This Post:



  • Digg
  • Twitter
  • Facebook
  • Google Bookmarks
  • del.icio.us
  • StumbleUpon
  • LinkedIn
  • MySpace
  • HackerNews
  • Reddit
  • Live
  • email

2-pizza teams (10)
3 C's (3)
37signals (1)
5S (38)
A3 Report (9)
adoption (7)
agile/software (59)
ajax (4)
amazon (53)
apple (3)
apple iphone (7)
axiom (3)
Aza Raskin (9)
backcountry.com (2)
berlin (1)
bill gates (1)
bill marriott (1)
blog tag (1)
book reviews (4)
bullwhip effect (5)
business (397)
business plans (3)
busm361 (13)
BzzAgent (12)
call center and queueing (11)
car buying (2)
Carbonite (1)
change management (5)
chicago (1)
click fraud (1)
click-to-ship (21)
clocky (2)
colin powell (2)
community (2)
company interviews (18)
company interviews (6)
complexity (32)
costs (8)
culture (7)
customer experience (10)
customer obsession (52)
customer recovery function (1)
customer segmentation (8)
customer service (17)
design thinking (14)
digg (4)
drum-buffer-rope (38)
dublin (1)
dynamic systems (24)
eBay (6)
economics (3)
efficiency (4)
ethnography (29)
family (18)
featuritis (15)
flexibility (1)
forecasting (2)
four performance dimensions (2)
Fun With The 2×2 Matrix (1)
game theory (7)
Gemba (67)
genchi genbutsu (68)
general (135)
germany (1)
google (15)
Gretchen Rubin (1)
heijunka (65)
holidays (1)
hoshin kanri (1)
how to be a human (1)
IDEO (2)
image uploading (1)
interviews (4)
iphone (5)
ishikawa (69)
IT at Toyota (67)
jason fried (1)
just-in-time (4)
kaizen (4)
kanban (46)
law of instinct (1)
Leadership (46)
lean (167)
Lean Consumption Maps (98)
learning curve (1)
licketyship (1)
mark cuban (1)
martin luther king (1)
mary poppendieck (1)
metrics (73)
microsoft (6)
milton friedman (1)
moving average (1)
muda (68)
nba fines (1)
net promoter score (nps) (1)
obeya (39)
Off-Topic (1)
onstar (1)
operations (108)
pageviews (3)
pareto principle (39)
patent (1)
peanut butter manifesto (2)
philosophy (3)
Poka-Yoke (6)
poppendieck (3)
powerpoint sucks (2)
private equity (4)
process measures (6)
product development (20)
productivity (4)
quality (41)
quasimodal design (1)
queueing theory (41)
Raffle (1)
rational choice (2)
regression analysis (18)
respect for people (6)
root cause analysis (60)
sarah+palin (2)
seth godin (1)
simplicity principle (10)
six sigma (128)
snowboarding (2)
social media (3)
spam (1)
statistical process control (46)
strategy (46)
suburban (1)
supply chain (24)
takt time (8)
teaching (2)
team size (9)
technology (104)
the beer distribution game (1)
The Happiness Project (1)
the profit tree (7)
The Visual Factory (11)
theory of constraints (41)
time (2)
timeline (3)
tony+hsieh (11)
toyota (75)
travel (1)
trump bankruptcy (1)
turnaround (5)
twitter (8)
uspto (1)
utah deal flow (2)
variation (69)
venture capital (1)
Visual Management (11)
waste (59)
website traffic (2)
Wing Chun (2)
wisdom of crowds (1)
wisdom teeth (1)
word-of-mouth marketing (18)
yahoo (2)
zappos.com (12)
zero defects (3)

WP Cumulus Flash tag cloud by Roy Tanck and Luke Morton requires Flash Player 9 or better.


If you enjoyed this post, please consider to leave a comment or subscribe to the feed and get future articles delivered to your feed reader.

Comments

This is awesome! That’s a great chart to get people off the bandwagon that more features = better. I am so tired of product after product that is crammed 95% full of features that I will never use. Case in point – my Treo. It does this and that and camera and bluetooth and file transfers and mp3’s and excel spreadsheet, etc. etc. The only thing it doesn’t do? WORK AS A PHONE. I’m on the product side for the company I work for and it’s a constant battle to talk end-user benefits/experiences instead of new, cool features that we COULD do. Developers are obsessed with their capabilities way more than what the customers actually want.

I haven’t heard of the Genchi Genbutsu before – I’ll have to look into that more.
Great post.

This is so true..I work in the software industry too and have observed that the client does not care about the features but the experiences. We try to cover the system deficiency of being flexible by giving good customer service that they remember us for.

Leave a comment

(required)

(required)


Additional comments powered by BackType