Why Visio wireframes are outmoded (Was [Sigia-l] NYU IA class description link)

[Dave]

On 7/11/05, Lyle_Kantrovich at cargill.com <Lyle_Kantrovich at cargill.com> wrote:
> I hate to ask the obvious, but what about non-web applications?  Let's
> talk traditional GUI, handheld, mobile and rich-client applications for
> a moment...

That's why I prototype in Flash.

Personally, I think the main problem of this discussion is that it
assumes that the tool we design in should be the same tool we document
in. I know this goes counter to Donna's point, but I feel this has
been a big process flaw from the IA community b/c we have always been
put into this position of pounding out documentation. In fact most of
my IA roles has been more about documenting my ideas then about
actually ideating them in the first place.

By saying more strongly that first we need to visualize a design
(seems we are talking about interface design here in this discussion,
though I can imagine the importance of visualizing an IA/structure)
and then after that visualization is approved then document it for
clear communication, I feel we will be doing more justice to both
roles.

Our designs are done in Flash, and our documentation is done in word
(though I'd love to switch to inDesign at some point). I do agree w/
Anders that designing interactive systems should be done in an
interactive environment.

-- dave

-- 
David Heller
E: dheller (at) gmail (dot) com
W: www (dot) synapticburn (dot) com