May 17, 2006

Adaptive Path blogs! And, oh yeah, Steven Johnson Speaks!

Adaptive Path recently started a blog (as Lane points out, it only took us 5 years!)

I just posted about how Steven Johnson, whom I've written about at various times on this site, has been an inspiration to me, and is our plenary speaker on the opening day of User Experience Week.

It's been great fun planning User Experience Week this year. We've decided to spend some money to turn it into a must-attend event, with great folks like Steven, and Michael Bierut, as well as Adaptive Path favorites like Jared Spool.

Anyway, consider this a bit of self-promotion.

Posted by peterme at 08:41 PM | TrackBack

May 14, 2006

dcamp chat on "design for appropriation"

Yesterday I attended DCamp, a gathering comprised mostly of user interface researchers and designers. I lead a discussion on "Design for Appropriation," inspired by a talk that took place at UC Berkeley, which I've written about before.

Our discussion was wide-ranging, and I didn't take notes, so I can't capture much of it. One of the most salient points was that there seems to be a cultural shift towards appropriation being acceptable, and Pete Stahl reminded us that most of us got into web design and development through browser-supported appropriation -- the ability to "View Source."

For me, the big question continues to be, "if we are designing things for our users/participants/customers/whathaveyou to appropriate, than what are we designing?" What is the *thing* that we point to and say, "I made that"?

I guess I've come away with two answers to the question. The first, and the easier answer, is that we are designing the frame, the container, the shell, within which users create and appropriate.

The second, and harder answer, is that it's not about designing a thing, an artifact (even digital) at all. That that is a trap of legacy thinking. That we as designers need to think about how we design, or use design tools and methods, to address aspects that aren't about the artifact. This puts me in the mind of Doblin's Innovation Landscapes , which help remind me that the "offering" is only one part of considering the product, and that there are many other aspects (business model, processes, channel, customer experience, etc.) that designers should address.

The other major concept that I kept coming back to was trust, and how trust gets associated with transparency and authenticity. But it does so in a funny way. Users tend to place a lot of trust in systems that are transparent and appropriate-able (such as Flickr) because we see the mechanisms by which things work, and that gives us comfort. We also, though, have a lot of trust (in fact, all we have is trust) in systems that are utterly opaque, such as financial service firms -- I don't want Schwab's systems to be appropriate-able.

As in the UC Berkeley conversation, I definitely come away from these discussions with more questions than answers. Suffice to say we design in interesting times.

Technorati Tags: , , ,

Posted by peterme at 05:01 PM | TrackBack


See Me Travel
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
Archives from June 13, 2001 to January 2003
Archives from before June 13, 2001
Recent Entries
Adaptive Path blogs! And, oh yeah, Steven Johnson Speaks!
dcamp chat on "design for appropriation"
Subscribe to my feed:
Powered by
Movable Type 3.2