Usability Requirements: Translating User Research Into Successful Products |
|
| Event | Interactive 2011 |
| Format | Solo |
| Organizer | Karen Bachmann – Perficient |
| Description | Defining usability requirements at a project’s start helps meet users’ goals and deliver satisfying user experiences. These non-functional requirements translate user research into meaningful guidance for design and into measures of success for testing. Usability requirements translate user goals into successful products. Usability requirements are non-functional requirements that define the expected and desired user reaction to a system. They describe how well a product should work for intended users and define target user satisfaction goals. User research, usability testing, competitive analysis, and business goals are some of the sources where usability requirements are discovered, and these sources inform their development and prioritization. Whether as part of a traditional requirements specification or an elaboration of a user story, usability requirements define user expectations that may not otherwise be articulated directly in these artifacts, but that users expect a successful product to deliver them. By understanding from the beginning of a project what usability requirements are and how they will be measured, teams can work together to deliver a usable product at all phases of development. Recommendations from usability testing now relate to the requirements, which are traced directly to the user goals. This traceability helps inform decisions on implementing recommendations, especially as release deadlines approach. |
| Questions Answered |
|
| Level | Intermediate |
| Category | User Experience |