Todd? If a best in class designer as yourself isn't using wireframes and hasn't for ages (2 yrs in our biz = ages) it seems to me that you are just being open to be nice.
1st, I didn't say don't do storyboards. I did say don't do wireframes and YES I do teach my students to work in interactive ALL the time. Sketch > scenarios/storyboards (that are ALWAYS human situated; more on this below) > low-fi interactive > hi-fi interactive Ok, storyboards have to be character/human situated. The point of the storyboards is to tell the story of use (IMHO) than to relay early concepts of UI. This means that you would do better to do comic strips with lightly sketched UI (See the Drawing Board series by Cooper as great examples of this) instead of doing "wireframes" as story boards. There is ALWAYS a point where you have to do what is best for your context and for your skillsets but the conversation is about direction and the fact that you say "yet" already implies that a documentation centric approach to your design is the past. So why wait!?! -- dave On Thu, Mar 12, 2009 at 7:52 AM, Todd Zaki Warfel <[email protected]>wrote: > > On Mar 12, 2009, at 6:20 AM, David Malouf wrote: > > If I never see "wireframe" as a deliverable again, I will be a happy man. > The age of visio, omniograffle, axure, iRise, etc. I hope come crashing down > (now offense to all the coders who worked hard on these tools), in favor of > Fireworks, Catalyst, Flash, Blend and Illustrator, Coda, etc. > > > I sure hope this isn't what you're teaching your students at SCAD. I would > hope that as practitioners and educators we can realize the value for > various methods and when they are appropriate. > > Animators and game developers use storyboards and wireframes in their > process. If there's any question, watch a documentation on how Pixar makes > films or speak to people working at EA. > > Axure and iRise are not wireframing tools. They are documentation and > simulation tools, which are used much more for creating prototypes than > static wireframes. > > For the time being and foreseeable future, there is and will be a great > deal of fantastic design work done incorporating wireframes in the design > delivery process. > > We haven't done a wireframe in 2 years. We only prototype these days. > However, I still realize the value of wireframes and how they can help in > the design process. Would I rather see more prototyping and less > wireframing? Sure. But at the same time, I realize that there are companies > who are much more documentation driven and prototyping might not be right > for them (yet). > > > Cheers! > > Todd Zaki Warfel > Principal Design Researcher > Messagefirst | Designing Information. Beautifully. > ---------------------------------- > *Contact Info* > Voice: (215) 825-7423Email: [email protected] > AIM: [email protected] > Blog: http://toddwarfel.com <http://toddwarfel/> > Twitter: zakiwarfel > ---------------------------------- > In theory, theory and practice are the same. > In practice, they are not. > > > > > -- Dave Malouf http://davemalouf.com/ http://twitter.com/daveixd http://scad.edu/industrialdesign http://ixda.org/ ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
