[Sigia-l] strategy to mocking wireframes?

Eric Scheid eric.scheid at ironclad.net.au
Sun Apr 13 05:36:38 EDT 2003


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.




More information about the Sigia-l mailing list