criteria for HTML prototyping

28 Jan 2005 - 2:59pm
9 years ago
3 replies
721 reads
lauras2010
2005

Hi all,

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
having.

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*
project.

Thanks in advance!

Laura Segel

Comments

28 Jan 2005 - 3:36pm
Peters, Craig M...
2004

> 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*
> project.

What's the purpose and audience? Internal only to communicate with
engineering, PM's, etc. or are you planning on creating a workable
smoke-and-mirrors version to test with users? Or both?

Craig

28 Jan 2005 - 3:59pm
James Melzer
2004

I just heard a really interesting prototyping concept yesterday
wherein a structural/conceptual prototype would be constructed and put
into staging to assess the impact of the new material on site
architecture. All this before any content is actually approved.

To Laura, I agree with Craig; it really depends on how your prototype
is going to be used. If it's for user testing, do it every time. If it
is to win stakeholder approval, then I'd build a prototype where it
supports the narrative you are trying to show/sell. If the purpose is
to work out engineering specifics, I would say prototyping is only
necessary where the interaction is fairly complex - i.e. more than
simple linking and form submissions. The last case is where the page
templates are numerous or complex, where you would need a large
subsection of the site to demonstrate the content's interaction with
them all.

Ziya would say you should prototype every single project.

~ James

On Fri, 28 Jan 2005 12:36:54 -0800, Peters, Craig M. (UI)
<craig.m.peters at documentum.com> wrote:
> [Please voluntarily trim replies to include only relevant quoted material.]
>
> > 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*
> > project.
>
> What's the purpose and audience? Internal only to communicate with
> engineering, PM's, etc. or are you planning on creating a workable
> smoke-and-mirrors version to test with users? Or both?
>
> Craig
> _______________________________________________
> Welcome to the Interaction Design Group!
> To post to this list ... discuss at ixdg.org
> Subscription Options (+ unsubscribe) ... http://discuss.ixdg.org/
> Announcements List ..... http://subscribe-announce.ixdg.org/
> Questions .............. lists at ixdg.org
> Home ................... http://ixdg.org/
>

31 Jan 2005 - 4:39pm
Thomas Vander Wal
2004

I have been doing this for the last four years or so. The functional
structural wireframes give us a tool to discuss flow, placement,
content needed, post-delivery maintenace issues, and design needs.
Getting this up and running as soon as possible is quite helpful and
has cut out a lot of time from our development process and also has us
throwing out fewer iterations (we modify and extend not build and
toss).

Getting a functional prototype in wireframe also requires us setting
the semantic structure for the site and tools (branding bar, global
navigation, local navigation, feature box, main content, etc.). We are
able to get stakeholders focussing on content short comings before
they focus on visual design and this has saved numerous headaches.

All the best,
Thomas

On Fri, 28 Jan 2005 15:59:55 -0500, James Melzer <jamesmelzer at gmail.com> wrote:
> [Please voluntarily trim replies to include only relevant quoted material.]
>
> I just heard a really interesting prototyping concept yesterday
> wherein a structural/conceptual prototype would be constructed and put
> into staging to assess the impact of the new material on site
> architecture. All this before any content is actually approved.
>
> To Laura, I agree with Craig; it really depends on how your prototype
> is going to be used. If it's for user testing, do it every time. If it
> is to win stakeholder approval, then I'd build a prototype where it
> supports the narrative you are trying to show/sell. If the purpose is
> to work out engineering specifics, I would say prototyping is only
> necessary where the interaction is fairly complex - i.e. more than
> simple linking and form submissions. The last case is where the page
> templates are numerous or complex, where you would need a large
> subsection of the site to demonstrate the content's interaction with
> them all.
>
> Ziya would say you should prototype every single project.
>
> ~ James
>
> On Fri, 28 Jan 2005 12:36:54 -0800, Peters, Craig M. (UI)
> <craig.m.peters at documentum.com> wrote:
> > [Please voluntarily trim replies to include only relevant quoted material.]
> >
> > > 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*
> > > project.
> >
> > What's the purpose and audience? Internal only to communicate with
> > engineering, PM's, etc. or are you planning on creating a workable
> > smoke-and-mirrors version to test with users? Or both?
> >
> > Craig
> > _______________________________________________
> > Welcome to the Interaction Design Group!
> > To post to this list ... discuss at ixdg.org
> > Subscription Options (+ unsubscribe) ... http://discuss.ixdg.org/
> > Announcements List ..... http://subscribe-announce.ixdg.org/
> > Questions .............. lists at ixdg.org
> > Home ................... http://ixdg.org/
> >
> _______________________________________________
> Welcome to the Interaction Design Group!
> To post to this list ... discuss at ixdg.org
> Subscription Options (+ unsubscribe) ... http://discuss.ixdg.org/
> Announcements List ..... http://subscribe-announce.ixdg.org/
> Questions .............. lists at ixdg.org
> Home ................... http://ixdg.org/
>

Syndicate content Get the feed