I'm new to this list, so forgive any ignorance on my part.
I'm part of a team that's trying to make our design
processes more user-centered, and as part of that effort
I'm proposing that we start building HTML prototypes /
functional wireframes for certain types of projects.
We are a marketing company that builds every kind of thing
from interstitial ads to full-blown web-sites with lots of
features. Seems to me that basic brochure-type sites have
little or no need for HTML prototyping, but perhaps for
anything more complex, a functional prototype is worth
However, I'm trying to spell out specific criteria that
will clarify the parameters within which the prototyping is
more than just a good idea, so management doesn't think
we're just asking for yet more resources for *every*