[Sigia-l] pre-wireframe specs?

• Next message: Susan Zeyher: "[Sigia-l] Re: SIGIA-L: Most abusive user experience?"
• Previous message: PeterV: "[Sigia-l] Re: SIGIA-L: A specific ROI question"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Hi all,

I'm looking for examples of pre-wireframe specs. These would be documents
that lay out what would go into wireframe designs, but without doing so
in a visual way (which would be a wireframe).

It might include things like primary purpose of page, required elements,
secondary elements, global navigation requirements, preferred reading
flow for the page, items to de-emphasise, branding requirements,
theme/voice/style of presentation, etc.

Pretty much a page spec as it would be handed over to the webdesigner in
the pre-IA days.

What I'm looking for are specifics of the specification, so as to decide
on a delineation of what gets done by the wireframer, and what gets done
by the graphic designer. Perhaps that will alleviate some of the "being
treated like a painter" designer angst (or perhaps not?)

e.

______________________________________________________________________
eric_at_ironclad.net.au i r o n c l a d n e t w o r k s
information architect http://www.ironclad.net.au/

_______________________________________________
Sigia-l mailing list
Sigia-l_at_asis.org
http://mail.asis.org/mailman/listinfo/sigia-l

• Next message: Susan Zeyher: "[Sigia-l] Re: SIGIA-L: Most abusive user experience?"
• Previous message: PeterV: "[Sigia-l] Re: SIGIA-L: A specific ROI question"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.2 : Sun Nov 23 2003 - 22:55:08 EST