In my experience, usability reports go largely unread. The business wants to know the quick wins as well as the longer term issues, but they need to be easy to digest, engaging and prioritised: filter out the stuff people dont need to know right now. As a UX designer working in an agile environment, I try to save as much time as possible, by taking screenshots to sessions for my observers to annotate. I take developers, BAs and business owners to the sessions to give them an overview of the main issues. I bring the screenshots back into work and get them straight onto the wall. Whilst the feedback is clear in my mind, I stick large index cards up next to the screens highlighting the major issues, and include some quotes from users. My main objective is to engage the development team enough to read these snapshots. We always record our sessions on video, so if we need to look back or really highlight something, a quick video showcase can provide compelling evidence. These screens provide a quick and easy way to communicate with the team and give a quick round up of the major issues. They can also stay up on the wall and act as a reference to decisions made earlier in the project. Meanwhile I can go about implementing change rather than trawling through video and audio material and writing long reports.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=44960 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
