[IxDA Discuss] design by committee??

[Bret Hekking]

> When the discussion gets to UI design
> (as it always does), I say "I've noted that idea, but let's not worry
> about details of the UI design until we get all the requirements down."
This approach has worked for me as well. Since I began focusing on design &
usability (rather than implementation...in a former life) I've had to be
vigilant about catching and deflecting the "what vs. how" tendencies of
stakeholders.

I do my best to make sure we all agree on (and write down) the problem we're
solving, for whom, and what the priorities are. Then, I'll sketch a few ideas,
get feedback if I can, *then* start scheduling design sessions.

> I find that it is useful to have developers, marketers, QA, etc involved
> at this stage
Early on, I like to invite "special guests" to design sessions - stakeholders
who are not involved with the project - for feedback. We almost always learn
something new that matters to the design.

> We design the UI outside of that meeting, and then usability test and
> refine it.  Then we bring it back.  We still run into debate about the
> UI at this point, of course, but it's powerful to be able to say "Well,
> it meets all the requirements we came up with together, and it tested
> really well.  Which part of that do you want to change?"
I've found that partners/customers/users comments usually win the debate for
me. If I've done my homework and vetted early ideas with external stakeholders,
internal design sessions focus on users and tasks rather than peoples' personal
opinions.

Finally, your mileage will vary as each company's culture and level of
experience with "design" as part of the development process will have a major
influence on what you're able to achieve.

Bret Hekking
Sr. UX Designer
Applix, Inc.

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com