Rick Barron: User Experience Testing Methods


Published on

Published in: Design
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Rick Barron: User Experience Testing Methods

  1. 1. USER EXPERIENCE <ul><li>Various Test Methods </li></ul><ul><li>By Rick Barron </li></ul>
  2. 2. A/B TESTING <ul><li>What: A process that allows one to test two (or more) different versions of a page. The display of the various versions vary on your website to see what users respond to best. </li></ul><ul><li>Why: Provides guidance in knowing what to adjust on your web page. Altering the size, placement, color of a single element, or the wording of a single phrase can have dramatic effects. A/B testing measures the results of these changes. </li></ul>Source: Reedge
  3. 3. BACKCASTING <ul><li>What: This is a process that causes one to start backwards with their ideal scenario. Taking these steps causes one to visualize required actions, various outcomes, validating or not validating assumptions. </li></ul><ul><li>Why: Teams are better at picturing the future by working backwards from an ideal instead of forwards from the current state of things. Backcasting provides a boost for innovation and planning efforts compared to starting from the status quo. </li></ul>Source: Interactionary on Flickr
  4. 4. CARD SORTING <ul><li>What: Card sorting is a technique used as an input to the structure of a site or product. The participant sorts labeled cards into similar groups. This could be an open sort, where piles are created based only on perceived similarity of cards, or a closed sort where piles are grouped according to provided categories. </li></ul><ul><li>Why: Best used to guide navigation design. Card sorting analysis shows how often participants grouped specific cards together. Discussing why the cards are placed in a particular pile yields deeper insight into user expectations for content. </li></ul>Source: Card Sorting, Designing Usable Categories, by Donna Spencer
  5. 5. COLLABORATIVE INSPECTION <ul><li>What: A group usability review that includes stakeholders, designers, developers, and end users. These sessions typically involve walking through a number of key tasks or screens, and are moderated by a lead reviewer, recorder, and time keeper. </li></ul><ul><li>Why: Due to the fact that many points of views are represented, collaborative inspections can be more thorough and efficient than expert reviews. Collaborative sessions also allow for discussions between stakeholders that might reveal deeper insights. </li></ul>Source: brad.ac.uk
  6. 6. CONCEPT MODEL <ul><li>What: A diagram that visualizes relationships between different concepts. Nodes containing concepts are linked with labeled lines and arrows in order to explain how they are associated. </li></ul><ul><li>Why: Defines how a series of complex, interrelated ideas relate to one another. Builds an understanding of a body of knowledge, and help uncover misunderstandings. </li></ul>Source: Soldierant on Flickr
  7. 7. CONCEPT VIDEO <ul><li>What: A technique to analyze design possibilities by making short films about how customers might use a technology in the future. Concept videos often focus on the context and benefits of use, rather than on specific interaction details. </li></ul><ul><li>Why: Various prototyping methods concentrate on the fine details of a design: what functions and controls to include, and how to lay them out. Because concept videos tell stories and avoid finite details, they are better suited to explaining a new vision. </li></ul>Source: Bonnier Research & Development
  8. 8. CONVERSATIONAL SKETCHING <ul><li>What: This is a collaborative method for participants in a workshop, to iteratively sketch their thoughts about possible solutions, discuss reasons for drawing a particular solution, and then sketch revised versions. A number of sketches is helpful to explore different approaches and work towards a common vision. </li></ul><ul><li>Why: Prepares a framework for participants to articulate their ideas. Explores underlying motivations that drive feature suggestions. Looking at root causes offers more opportunities for real solutions than simply adopting requested features. </li></ul>Source: Sitepoint
  9. 9. EXPERIENCE MAP <ul><li>What: Visualization of experience across locations, time, and channels. Captures interactions between touch points. Helps illustrate what an “ideal” scenario might look like when planning, architecting and designing an interactive experience. </li></ul><ul><li>Why: A holistic view of experience through time with specific touch points. This process helps contribute to better coordination of cross-channel design and reveals opportunities for new or improved interactions. </li></ul>Source: nForm
  10. 10. HEURISTIC EVALUATION <ul><li>What: A form of usability inspection where specialists assess how well an interface complies with recognized usability principles (heuristics). Usually two or three experts review a system, noting and ranking problems. </li></ul><ul><li>Why: Provides quick, inexpensive usability feedback. Can be a good method early in a development process, as it concentrates on the basics, ensuring that an interface is fundamentally sound before more in-depth testing with real users. </li></ul>Source: Rebeccallena on Flickr
  11. 11. PAGE DESCRIPTION DIAGRAM <ul><li>What: A comprehensive inventory of all design elements, content, and interface components on a page, arranged in three columns of high, medium, and low priority. The content areas of the page are described in prose, as in a functional specification. </li></ul><ul><li>Why: Documents the elements of each page without specifying layout. May be used instead of wireframes, or preceding wireframes. Allows greater collaboration between team members responsible for visual design and functional specification. </li></ul>Source: PebbleRoad
  12. 12. PARTICIPATORY DESIGN <ul><li>What: This method to design actively involves stakeholders in the design process. Exercises help the group to explore the problem space, current and ideal experiences, and ways of achieving the ideal. </li></ul><ul><li>Why: These sessions enable people with different expertise and skills to contribute videos tell stories and avoid minutiae, they are better suited to explaining a new vision. </li></ul>Source: Sam Shoulders
  13. 13. PERSONAS <ul><li>What: Personas are archetypal users of an intranet or website that represent the needs of larger groups of user, in terms of their goals and personal characteristics. Includes a name, picture, user quotes and other info with a focus on goals, motivation, and behavior. </li></ul><ul><li>Why: Crates empathy for the specific user and avoids self-referential design. Focus on accomplishing specific goals allows the product to satisfy many people with that goal, whether or not they match a specific market segment. </li></ul>Source: Fluid
  14. 14. SCENARIO PLANNING <ul><li>What: Scenario planning is not about predicting the future. Rather, it attempts to describe, via story-telling methods, what is possible. The result of a scenario analysis is a group of distinct futures, all of which are plausible. The challenge is how to deal with each of the possible scenarios. </li></ul><ul><li>Why: Many planning techniques focus on current data and fail to address the unpredictability of future events. Divergent stories help to increase our understanding of our operating environment, and expose our basic assumptions about how the world works. </li></ul>Source: Future of Health IT: Trends & Scenarios
  15. 15. SKETCHBOARD <ul><li>What: Sketch boarding is a collaborative design technique developed to capture concepts, iterate through low-fidelity comps and work toward more detailed interfaces. All of this is staged on a large sheet of paper. Starts by posting criteria like discovery findings and then sketching and arranging potential solutions nearby, first as thumbnail sketches and then as detailed screens. </li></ul><ul><li>Why: Design the big picture of a site or application without getting bogged down in incremental detail like wireframes can. Collaborative low-fi format keeps project criteria at hand to build common ground. </li></ul>Source: UX Booth
  16. 16. STICKY NOTES <ul><li>What: Using simple post-it notes enables ease of use in re-positioning without having to deal with written mistakes on paper. Can be attached to a wide variety of flat surfaces, including documents, walls, monitors, and white boards. </li></ul><ul><li>Why: UX professionals are indecisive. They answer most questions with ‘it depends’. Myriad bits of paper (or ‘data’) can be useful for creating the impression that we know a lot of stuff, so ‘stakeholders’ shouldn’t mess with conclusions. </li></ul>Source: Jason Robb on Flickr
  17. 17. SWIMLANES <ul><li>What: Diagram that displays parallel streams for users, business, and technical process flows. May also include a storyboard stream. A diagram is created for each core product scenario or activity. Provides foundation for use cases. </li></ul><ul><li>Why: Provides alignment and integration of task flow with process and technical requirements. Establishes understanding of all components of a specific process in one document, while allowing clearer separation, responsibility, and delegation. </li></ul>Source: nForm
  18. 18. TASK ANALYSIS <ul><li>What: A study of the actions and cognitive processes required in order for a person to complete a given task. Task Analysis is helpful when trying to understand a system and its information flows. </li></ul><ul><li>Why: Provides deep insight into the steps needed to complete a task. Task Analysis also helps in understanding the mental model formed by people performing the task. </li></ul>Source: The Information Architecture Institute
  19. 19. USABILITY TESTING <ul><li>What: Where users test drive a prototype or production system. Usually one-on-one, with a participant and moderator, the participants are asked to think out loud as they complete representative tasks. Typically 6-8 participants per user segment. </li></ul><ul><li>Why: Usability testings helps one understand what works and what doesn’t. The process helps focus in finding specific interface issues, layout, labeling, and interaction. </li></ul>Source: Ryerson University
  20. 20. USER SCENARIO <ul><li>What: Storytelling approach to design that captures user motivations and actions in short, focused, narrative form. Each scenario captures the moment for a particular set of action focused on meeting a specific need for a user. Typically written, sometimes captured through pictures or video. </li></ul><ul><li>Why: Brings users to life while keeping focus on tasks and behavior. Scenarios can link together to tell the entire story of a product or service. Easy to explore and iterate, scenarios complement personas, and can lead to more detailed use cases. </li></ul>Source: Linlin Designs
  21. 21. WEB ANALYTICS <ul><li>What: Measurement tool that provides insight into the analysis of user behavior based on logs of activity on a website. These tools provide information such as entry and exit pages, most popular pages, paths through the site, links from other sites, and search terms. </li></ul><ul><li>Why: Allows real time view of user behavior on websites. Particularly strong for measuring user intent through search terms, trouble spots where users leave, and conversion goals for marketing and sales. </li></ul>Source: Linlin Designs
  22. 22. WIREFLOW <ul><li>What: This method visualizes interaction within a system by laying out the various screens of an application in one large document and drawing the connections between related screen elements. </li></ul><ul><li>Why: Provides comprehensive canonical picture of system interaction in one document. Can see key interactions and relationships at a glance. Caution: very labor-intensive to maintain as the system changes through iterations. </li></ul>Source: Wireframes.linowski
  23. 23. WIREFRAME <ul><li>What: A wireframe is a basic visual guide used in interface design to suggest the structure of a website. It describes each element and behavior. Focus is on layout, labels, interactions, and relationships between other pages. Finished design elements such as color and photos are not used. </li></ul><ul><li>Why: Focus is on specifications for individual pages or templates. Can use as prototype for usability testing. Prevents premature conversations about surface issues like color, instead focuses discussion on correct and complete content and functionality. </li></ul>Source: h2g2