FW: [Sigia-l] strategy to mocking wireframes?

[David Heller]

Eric, I think this depends on the placement on the information < >
application continuum your project falls.

For what I do, we don't even do sitemaps for our projects as we are
completely use-case driven. When I worked on sites as opposed to
applications I was completely sitemap driven, when I worked on something
more in the middle my sitemaps were more based on my use-cases and acted
more as interaction flow than information mapping.

As for prototyping ... The quicker you can get to an interactive designed
item the quicker you can move to the next step.

-- dave 


-----Original Message-----
From: Eric Scheid [mailto:eric.scheid at ironclad.net.au]
Sent: Sunday, April 13, 2003 2:37 AM
To: sigia l

On 13/4/03 6:42 PM, "Gunnar Langemark" <gunnar at langemark.com> wrote:
> Information and interaction is not the same.

Indeed.

Something I should have added to the first message is the impetus for my
questions: so much of contemporary IA is about "structuring content" -
content inventories, card sorts, taxonomies, categories, labeling, facets,
hierarchies, site maps, etc; and we also like doing wireframes ... but is
the information-heavy analysis the proper foundation for wireframe
development, as the web-quote pointed out...

    Many times you end up with better results if you start to
    drafting the mockup based on use-case scenarios rather than
    a information content map (users do not necessarily browse
    the site hierarchically, rather they go through cross sections
    of the site structure).

So, "many times" one particular way is better than the other. What are the
factors involved that determine one

> Is this an either or?

If you mean absolutely, then no, there will always be fringe cases and
exceptions. I don't think you meant absolutely though, but rather "is this
an either-or for the majority of situations?", to which while I suspect not
I also suppose one would take a greater emphasis than the other. Ying and
Yang.

e.

------------
When replying, please *trim your post* as much as possible.
*Plain text, please; NO Attachments

Searchable list archive:   http://www.info-arch.org/lists/sigia-l/
________________________________________
Sigia-l mailing list -- post to: Sigia-l at asis.org Changes to subscription:
http://mail.asis.org/mailman/listinfo/sigia-l