[Sigia-l] Axure

[W Evans]

"which is a vehicle for communicating design
intend."

Sometimes - depends on where in the process you are. Far upstream you may be
using prototypes to validate good/bad ideas during the ideation phase - way
before you have arrived at a design worthy or tossing around some
requirements and specifications.

"Then you have to figure out if you want a prototype that shows how the
design works or one that
shows how to build that design."

Amen - or if you want three or four quick prototypes to makes sure you are
traveling down the right path, see which one/s resonate most with user test
groups.

I am moving far away from the old "define, document, wireframe, prototype,
test, build, deploy" process - and thinking that prototyping, fast, nasty,
ugly prototyping - should move far upstream in the process - way before a
prototype for the purposes of functional and design specification is even
thought of being done.
-- 
~ will

"Where you innovate, how you innovate,
and what you innovate are design problems"
-------------------------------------------------------
will evans
user experience architect
wkevans4 at gmail.com
-------------------------------------------------------