I agree that doing task flows first is probably the standard, but I'll play devil's advocate here: you can actually get some pretty interesting results by diving right away into super sketchy, lo-fi wireframing.
Task flows can sometimes make a process seem linear and sequential even though people may approach it by fits and starts, through weird back doors, and in otherwise unpredictable ways. Starting with the most interesting moment in a process and envisioning what that might look like and then brainstorming around what hangs off that moment -- before, after, and parallel to it -- can be another good way to start to get your hands around how much complexity you're dealing with. Then on to task flows and more traditional wireframing... Leah . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=29516 ________________________________________________________________ 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
