After establishing design principles based on good assessment data, I typically turn to some quick pen-and-paper sketching to wrap my mind around design problems and areas of potential confusion. These sketches are quick, low-fidelity, and really only meant to inform small-group conversations with those closest to the project. Depending on the task at hand, I will sketch full pages, discrete interactions (such as a specific form element), or a narrative storyboard to visualize a potential user path.
As Erin mentioned in her last post, I serve as the U.Va. Library’s User Experience Web Developer. But what exactly is a UX developer and how is the role different from a web designer, front-end developer, or generalist programmer?
Perhaps foremost, a User Experience Developer allows assessment to lead design. When we set out to create a new tool or feature, we don’t start with sketches or Photoshop documents or the like, but with surveys, focus groups, and user testing.