Posts tagged as Product


Memory is More Important Than Actuality

Don Norman reminds us how humans evaluate and interpret experiences before, during and after they’ve occurred:

Rosy projection: “the tendency for people to anticipate events as more favorable and positive than they describe the experience at the time of its occurrence”;

Dampening: “the tendency for people to minimize the favorability or pleasure of events they are currently experiencing”;

Rosy Retrospection: the tendency for people to remember and recollect events they experience more fondly and positively than they evaluated them to be at the time of their occurrence.”

The insights are directly applicable to design:

Design for memory. Exploit it. What is the most important part of an experience? Psychologists emphasize what they call the primacy and recency effects, with recency being the most important. In other words, what is most important? The ending. What is next most important? The start. So make sure the beginning and the end are wonderful… Accent the positive and it will overwhelm the memory for the negative.

Aug 2 2009

Anatomy of a Feature

If you’ve ever implemented or designed a feature, this account of the process will likely resonate with you. What on the surface looks like a simple tweak easily snowballs into an avalanche of repercussions. My favorite quip comes in the end:

Applying the 80/20 rule means you will get feature requests from the 20.

Aug 1 2009

Reid Hoffman on Launching

If you’re not embarrassed – in the consumer internet – by the first version of the product you launched, you’ve launched too late.

Reid Hoffman

Jun 11 2009

On Everyday Apps

In his latest post, Joshua Porter riffs on the concept of ‘every-day apps’, something I’ve talked about in the past (although I used ‘destination sites’ to describe such properties). In my post, I made some base assumptions suggesting that our capacity to visit sites on a regular basis is finite. It was nice to see Joshua cite a study reaffirming my guess, demonstrating that most people regularly visit only about 10 sites.

I found this description of product design particularly poignant, mostly because I’ve made this same mistake:

In general, most people think they’re building an everyday app, but they’re not. When the actual use patterns are discovered, most apps will be used every few days or less.

The rest of the article is spent postulating on how LinkedIn could bridge their ambitions to be an everyday site. For me, the more interesting problem is acknowledging that you’re not an everday app while still positioning the product to succeed.

May 13 2009

Java Applets 2.0

AIR apps are like modern day Java applets… sure, they run on every platform. But they also suck on every platform

Loren Brichter

[via Marco]

Apr 24 2009

Posts tagged as Product