[IxDA Discuss] "web 2.0" prototyping

[Will Parker]

On May 21, 2007, at 11:29 PM, Björn Simonson wrote:

> You're right in that many functions have no place in a prototype.  
> But you nevertheless what the user to have a good idea of how  
> elements will behave.
>
> I'm thinking that some kind of "interaction mood-board" would be in  
> place. An interaction mood-board would show the user what she could  
> expect from different elements in the prototype and aid in making  
> the prototype seem more alive?
>
> Has anyone tried an approach similar to this?

I'm getting into the habit of maintaining a personal library of  
interface behavior storyboards, focusing on the small details that  
give designs their flavor but might get lost in a proto.

If reviewers seem to not 'get' the overall design, I whip out my  
handy Moleskine Storyboard and give an impromptu description of the  
intended behavioral details and a restatement of how these effect the  
user experience.

One particularly good point to having these detail storyboards on  
hand in a single collection is that it prompts discussion of  
alternate behaviors _before_ code -- even proto code -- is written.  
(Bring pens and a big sketch pad to the meeting; that way you'll keep  
the non-IxD people engaged in specifics, and if you're lucky, you'll  
get some real surprises.)

Yes, a few mood boards could serve the same purpose, but as part of  
my training is in film animation, I'm more comfortable with  
_storyboards_ focusing on the general layout and action in the early  
stages, and mood boards as a way of showing alternative static visual  
details.

- Will

Will Parker
wparker at ChannelingDesign.com

“I wish developing great products was as easy as writing a check. If  
that were the case, then Microsoft would have great products.” -  
Steve Jobs