logo
dan@odannyboy.com
12 Forbes Terrace
Pittsburgh, PA 15217
412.422.0555

WHO I AM

WHAT I DO

WHAT I'M
THINKING ABOUT

WHAT I'M STUDYING

 

 

 

 

 

 

WHAT I'M STUDYING :: ARCHIVED ENTRY

Monday, February 16, 2004

Adaptive Worlds
John Rheinfrank, a self-described "trickster," was our guest during design seminar last week, and his topic was adaptive worlds and how to design for them.

John defines a world as a meaningful cluster of activities and objects that form around extended groups of people and that contain multiple, meaningful living structures. Worlds are full of static objects that force us to adapt to them or that we adapt for use. But surrounding the world of static objects are adaptive worlds that contain things that learn, react, respond, do meaningful things, and understand context. They respond to humans by changing shape (ie their form and content) depending on the context of use. We co-create adaptive worlds with these sorts of tools.

In these co-constructed adaptive worlds, people and objects adapt and respond to each other. There is flow (in the Csikszentmihalyi sense), state changes depending on context, and mutual sensing and responding. We co-evolve as dynamic living structures, able to coordinate complex activities, and affect powerful transformations.

Design has slowly moved from user-centered (not for use or meaning) to activity-centered (task-oriented) to ability-centered (both the users' abilities and the product's abilities). "User-Centered" is no longer adequate, because the purpose of objects and systems isn't only to serve the user. The term (and way of designing) doesn't provide for unconceivable, unknown needs. It is about using products in particular ways. Designers need to understand that once a product is launched, users will use them in unexpected ways for unexpected purposes. And as these adaptive tools are launched, more and more the products we design will be out of our control. (Obviously, the ethical implications of this are many.)

So how do you design for adaptive use? In general, you have to build for autonomy, yet retain control over some of the parts. Designers will need to understand the deep structure of their products, but allow the surface structure to be adaptable and responsive. Some guidelines (from a user's viewpoint):

  • Let me do. Make sure the activity is of real value. Let my actions and changes in the resulting array feel as though they have been designed for me personally.
  • Orient me. Give me a journey I can take. Don't steer, just give me a map to help me visualize what I want to accomplish and plan where I want to go.
  • Let me win. Reward me when I accomplish something.
  • Push me. Help me learn. Help me reveal my potential, don't let me get by. Combine doing with understanding. Skill me.
  • Sense and respond. Personalize it for me. Let me feel the artifact is alive. Make its operation transparent like a window.
  • Connect me. Help me make connections with the subject matter or across destinations with other people.
  • Immerse me. Plunge me into the experience. I can't tell the difference between me and it, it is so much a part of me.

A successful design will be one where the experience of using it fits. By engaging users in co-discovery and co-creation of these adaptive worlds, we'll transform their work, their business, their community, and their lives.

posted at 08:47 AM in big ideas, special guest stars, techniques | comments (0) | trackback (0)

 

‹‹ preceding entries

 

SEARCH ENTRIES

 

CATEGORIES
3D (2)
alumni (3)
assistantships (3)
big ideas (23)
classes (16)
classmates (17)
cmu (12)
cognition (1)
cpid program (3)
design 101 (25)
design theory (20)
extracurricular (11)
faculty (8)
field trips (5)
hci program (4)
info design (3)
interface design (6)
meta (6)
money (5)
papers (4)
photography (5)
preparation (6)
projects (43)
readings (29)
software (8)
special guest stars (10)
student life (16)
teaching (1)
techniques (12)
thesis paper (4)
thesis project (1)
typography (7)
visualization (8)

 

WEEKLY ARCHIVES
Week of Mar 14, 2004
Week of Feb 29, 2004
Week of Feb 22, 2004
Week of Feb 15, 2004
Week of Feb 8, 2004
Week of Feb 1, 2004
Week of Jan 25, 2004
Week of Jan 18, 2004
Week of Jan 11, 2004
Week of Jan 4, 2004
Week of Dec 7, 2003
Week of Nov 30, 2003
Week of Nov 23, 2003
Week of Nov 16, 2003
Week of Nov 9, 2003
Week of Nov 2, 2003
Week of Oct 26, 2003
Week of Oct 19, 2003
Week of Oct 12, 2003
Week of Oct 5, 2003
Week of Sep 28, 2003
Week of Sep 21, 2003
Week of Sep 14, 2003
Week of Sep 7, 2003
Week of Aug 31, 2003
Week of Aug 24, 2003
Week of Aug 17, 2003
Week of Aug 3, 2003
Week of Jul 27, 2003
Week of Jul 20, 2003
Week of Jul 13, 2003
Week of Jul 6, 2003
Week of Jun 29, 2003
Week of Jun 22, 2003
Week of Jun 8, 2003
Week of Jun 1, 2003
Week of May 25, 2003
Week of May 18, 2003
Week of May 11, 2003

 

RSS FEEDS
Summaries
Full Entries

 

SUBSCRIBE
Want more spam? Sign up to receive this blog via email:


 


All straight lines circle sometime. - The Weakerthans