I've been given the chance to set up a UX department from scratch at an existing digital agency.
The agency has about 70 really good people (designers, coders, the works) many of whom are interested in UX design. And at the moment we do a bit of usability testing and the odd bit of research. But my mission is to really put the user at the center of everything we do.
Obviously I've got a lot of ideas for how I want to approach it, but basically I'm looking for advice from anyone who's done this before.
Earlier this week at the local Utah IxDA meeting and over the last
while at various places I've heard the topic of how to deal with
developers come up. I was thinking about it and realized I had a lot
to say about it. Sorry for the length :)
I currently work at a very small company, less then 20. But compared
to the other stories I've heard lately from Interaction Designers
like myself in Utah, our company gets surprisingly consistent results
from our developers in regards to design.
Last January, 2008 The University of Kansas launched two new
professional graduate programs: one in Interaction Design and another
in Design Management. The programs were years in the making and are
headed up by myself, Michael Eckersley and Richard Branham, with other
strong contributing faculty. More on Richard and myself below.
What are people using (especially for in-house types) for requirements
management throughout the entire product management lifecycle:
1. input channels and research capture
2. concept capture
3. requirements definition
4. design docs
5. technical docs
6. QC test scripts
7. launch, rollout, marketing plans
Something that deals w/ workflow and lifecycle management
Has strong permissioning
Well designed (something I would WANT to use)
Understands that software requires a designer (sheesh!)
works well on pc and mac