home | books | articles | gleanings | case studies | hire
other sites: widgetopia | blueprints for the web | metafooder | Mammahood


 
 





May 11, 2006


No Keraoke
Posted in :: Design :: Documentation :: Information Design ::

IMGP5353
Originally uploaded by Box and Arrow.
It's moments like this when I really feel for all the icon designers of the world.

What the heck is this, and why do the lawyers think it is common enough to need to be represented iconicly?

MORE...
Posted by christina at
permalink | 2 Comments


February 27, 2003


get help, give help
Posted in :: Documentation ::

A reader sent me Cherryleaf - Article - nine trends in online user assistance

There are places where I think they are right on:

"Applications can suffer from Help windows being placed in inconvenient locations -- often covering the portion of the interface on which the user is working. You can embed Help into the application and make information viewable as part of the application window itself. "

Contextual help that prevents errors is some of the most useful help you can provide. Contextual help that appears in close proximity to an error or problem is the next best help you can provide. Context is a key to understanding, proximity for relevence... it's just good.

Other things in the article I found a bit wonky: "This movement towards organizations creating customizable products and services is likely to create a need for personalized and customizable user documentation that is quick and cheap to produce."

I"m moderately certain they are suggesting allowing customers to customize help. I reread it a couple times, and I'm feeling pretty confident this is the point (it's a bit less clear than some other sections)

If that is true, it's a bad idea. My experience with customization and personalization is that it is highly task-context sensitive.

Customizing a personal homepage is perceived as useful by users, customizing a help page is not. The users I've seen would first prefer not to go to help at all (under any circumstance, once the reasons contextual help is so much better than documentation-style help) BUT if they do you go help they want to go in, find the answer and get out as fast as possible. No lingering over whether their headers should be sea green or sky blue, just "get me my frigging answer now please."

Personalization in shopping is good... but I shudder to think what personalization might do in help-- imagine the user seeing related help to a problem they had once before "Hey, why does the help keep telling em that? Sure, I goofed up once, but I figured it out! Why does this program hate me?"

Okay, that might be a bit excessive. But still... i think product managers should be wary of trends in design. Just because the industry is excited about this or that cool feature, doesn't mean your product should do it too.

Anyhow, lots to think about in this article.

Posted by christina at
permalink | 10 Comments


June 04, 2002


hipquick
Posted in :: Documentation ::

Thanks to HOW 2 BE HIP TIPS, there will be no more 45 degree angles here, no way man!

Posted by christina at
permalink


May 17, 2002


good lecture
Posted in :: Architecture :: Design :: Documentation ::

I saw Lebbeus Wood talk last night, and it was very interesting. He's an architect of many peculiar things, including uninhabitable spaces. He believes that an architect should not wait for clients to design, but that an architect is a social agent with an obligation to try to answer hard questions. So he makes things like scars for buildings wounded by war.

He said one thing that got me a it het up (well several, but this is relevent to the things I've been thinking about lately). He said "Design is about predcition." i.e. we create designs because we are predicting how space will be used, and what will exist.

Which knocked me on the head so I realized that there are two kinds of design

Design as planning
Design as articulation

Design as articulation is what we think of when we hear design most of the time. You know, line-color-font to communicate and evoke. la.

Design as planning is what we mean when "non-designers" (and designers, sure) design something. Software design, interaction design and so on. Strategy for the act of building.

I've been thinking my nascent Venn diagram and thinkingit is half the picture. I realize it is... the planning half, with InfoD wandering into the articulation half. I'm working on a new diagram. Will post as soon as it's vaguely acceptible.

This is probably old school for folks who did design in college (I did fine art, so I have a different vocabulary, where I have one....) so I'd love to hear from folks.

Posted by christina at
permalink | 3 Comments


December 12, 2001


documentation spotting!
Posted in :: Documentation ::

Ryan's portfolio sports a nicely organized and well thought out style guide.

Posted by christina at
permalink


November 17, 2001


ya think?
Posted in :: Documentation ::

How non-programmers use documentation. Short, simple and from what I've seen in testing, quite accurate.

Posted by christina at
permalink

 

home | books | articles | gleanings | case studies | hire
other sites: widgetopia | blueprints for the web | metafooder | Mammahood