Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Upcoming SlideShare
DIY UX Audit


User Experience Deliverables

Learn the different kinds of UX deliverables, when to use them, and how to create them with examples.

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all

User Experience Deliverables

  1. 1. User Experience Deliverables ! by Publicis Canada UX Team © 2010 Publicis Canada!
  2. 2. UX Deliverables in the Discovery Phase •  Needs Assessment! •  Requirements Document! •  User Persona / Scenario! DISCOVERY! •  Current Site Evaluation! •  Competitive UX Audit! •  Content Inventory! •  Usability Testing / Reporting! •  Card Sorting! © 2010 Publicis Canada!
  3. 3. Needs Assessment What is it? A needs assessment is the process of collecting information about an expressed or implied organizational need that could impact project scope Why do we need it? It helps us to identify hidden needs from clients or to clarify the objectives of the project When do we need it? Usually for new clients or for the projects with multiple and complex levels of stakeholders © 2010 Publicis Canada!
  4. 4. Needs Assessment (cont d) Four different methods of needs assessment Client Briefs! Stakeholder In general, client briefs Interviews! include the business needs & Stakeholder interviews can be conducted during the objectives of the projects discovery phase when there are multiple and complex levels of stakeholders Needs Assessment Needs Assessment Survey! Workshop! A document including A series of workshops can be questions about objectives, held with key stakeholders for brand, target audience, each session content/design/technical needs © 2010 Publicis Canada!
  5. 5. Requirements Document What is it? List of high-level requirements for a project, in alignment with business and project objectives Why do we need it? Helps to define project scope, budget and required deliverables When do we need it? Required for all projects. For small projects, requirements can be included as a part of the SOW. When the requirements are complex or when there is a large number of requirements, a separate requirements document will be created. © 2010 Publicis Canada!
  6. 6. Requirements Document (cont d) Requirements document examples © 2010 Publicis Canada!
  7. 7. User Persona / Scenario What is it? A characterization and detailed profile of users based on digital behaviour, marketing segments, and demographics Why do we need it? Help clients and project teams think from various users points of view and create content, features and functionality based on user needs! When do we need it? Required when users are not well understood or when one design must satisfy multiple types of users © 2010 Publicis Canada!
  8. 8. User Persona / Scenario (cont d) Persona Example © 2010 Publicis Canada!
  9. 9. Current Site Evaluation What is it? A usability inspection and assessment of a website against established, recognized human factors and usability principles, usually conducted by a usability specialist! Why do we need it? A quick way of identifying problems, primarily with the user interface, for redesign efforts When do we need it? Used to justify a site redesign, to compliment other evaluation methods, or as a sole evaluation method when resources, scope, and/or budgets are limited © 2010 Publicis Canada!
  10. 10. Current Site Evaluation (cont d) Site Evaluation Examples © 2010 Publicis Canada!
  11. 11. Competitive UX Audit What is it? User experience evaluation of competitive or best practice sites or products Why do we need it? To discover which competitive website delivers a good user experience and to analyze which elements contribute in what ways to the experience! When do we need it? For projects focusing on enhancing user experience against competitors © 2010 Publicis Canada!
  12. 12. Competitive UX Audit (cont d) Competitive UX Audit Example © 2010 Publicis Canada!
  13. 13. Content Inventory What is it? An inventory of site pages, content and assets, typically delivered in excel format organizing the list of items based on the current site structure Why do we need it? It is a basic first step to assess the volume and the quality of the site content that will influence effort, budget, and redesign recommendations When do we need it? The basic content audit is required for all projects, but the documentation is required for content heavy or complex sites © 2010 Publicis Canada!
  14. 14. Content Inventory (cont d) Content Inventory Example © 2010 Publicis Canada!
  15. 15. Usability Testing / Reporting What is it? Users are asked to carry out tasks according to defined scripts while being objectively observed Why do we need it? To ensure that designs are usable and that users can carry out tasks efficiently, effectively, and satisfactorily. Don t guess…test! When do we need it? When knowledge about users is low or when the team wants to confirm assumptions and understanding of user behaviour © 2010 Publicis Canada!
  16. 16. Usability Testing / Reporting Usability Testing Examples © 2010 Publicis Canada!
  17. 17. Card Sorting What is it? A technique that helps determine the information hierarchy of a website by writing content items on cards and placing the cards into logical groups to reveal the relationship between the content items! Why do we need it? Card sorting is a quick, inexpensive, and reliable method and is an important input to the information design process When do we need it? Needed for content-heavy websites or when content has become unorganized after increasing growth over time © 2010 Publicis Canada!
  18. 18. Card Sorting Card Sorting Examples © 2010 Publicis Canada!
  19. 19. UX Deliverables in the Design Phase •  User Flow! •  Interaction Flow! •  Sitemap! •  Content Matrix! DESIGN! •  Wireframe! •  Features & Functionality Specification! •  Prototype! © 2010 Publicis Canada!
  20. 20. User Flow What is it? A simple diagrammatical document that follows a user down a path of activity Why do we need it? It helps us to create a logical and intuitive interfaces by anticipating users actions and thinking of the different tasks they need/want to achieve When do we need it? For all projects. It may not be required as a formal deliverables to the client unless it is necessary © 2010 Publicis Canada!
  21. 21. User Flow!! © 2010 Publicis Canada!
  22. 22. Interaction Flow What is it? A diagram or flow map highlighting the interaction between the users and site features Why do we need it? It helps to overview the core interactions within the application and to demonstrate the relationship and connectivity between the functionalities When do we need it? For complex applications and systems that require a lot of user interactions (e.g. community sites, software, etc.) © 2010 Publicis Canada!
  23. 23. Interaction Flow Interaction Flow Examples Home © 2010 Publicis Canada!
  24. 24. Sitemap What is it? A hierarchical visual model of the pages of a Web site Why do we need it? A sitemap is a useful way of orienting clients and teams to the content of a website by showing a diagram of the entire site's contents When do we need it? Almost every website project if the site requires multiple pages © 2010 Publicis Canada!
  25. 25. Sitemap Simple Sitemap Example Comprehensive Sitemap Example © 2010 Publicis Canada!
  26. 26. Content Matrix What is it? A content table or an excel chart listing all the pages and modules of the site or system specifying content rules, description, attributes, and status Why do we need it? It s a great asset of a project helping project team and clients managing all the variations, rules and status of the site content and modules When do we need it? Content heavy or CMS driven websites or complex system © 2010 Publicis Canada!
  27. 27. Content Matrix Content Matrix Examples © 2010 Publicis Canada!
  28. 28. Wireframe What is it? A visual guide to depict functionality and to illustrate page layouts and their informational elements, before applying creative design! Why do we need it? Critical in the process of creating usable and useful websites or web applications and brings project teams to a common understanding of the product When do we need it? If there s a user interface involved then wireframes are required. © 2010 Publicis Canada!
  29. 29. Wireframe (cont d) Low fidelity Wireframe High fidelity Wireframe © 2010 Publicis Canada!
  30. 30. Features & Functionality Specification What is it? Describes, in detail, the website s or web application s intended capabilities and interaction with users and tied directly to a requirement Why do we need it? Sets the client s expectations (in conjunction with wireframes and design comps) of what will be delivered and puts the team on the same page When do we need it? Needed for large projects, when there are a large number of features or functions, or when features and functionality are complex and must be explained in detail © 2010 Publicis Canada!
  31. 31. Features & Functionality! Specification Features & Functionality Specification Examples © 2010 Publicis Canada!
  32. 32. Prototype What is it? A working model of a website, clickable with the appearance of being functional, usually built for demonstration purposes. Why do we need it? Provides a tangible, concrete concept that significantly reduces communication and comprehension gaps between team members. It can also be leveraged for usability testing. When do we need it? Mainly when user flow is complex. © 2010 Publicis Canada!
  33. 33. Prototype (cont d) Prototype Examples © 2010 Publicis Canada!
  34. 34. About Publicis 
 User Experience Team We are specialized in a multi-disciplinary process of User Experience Design to create •  Corporate Websites! •  Ecommerce! •  Marketing / Campaign Microsites! •  Community Sites / Social Media! •  Intranet / Extranet / CMS System Interface! •  Mobile Sites & Applications! We provide Complex UX analyses & solutions throughout the project lifecycle Contact:! •  Discovery, Definition, Design, and Development! Twitter: @Publicis_UXD! © 2010 Publicis Canada!
  35. 35. Thank You! Any Questions?! Contact:! Twitter: @Publicis_UXD! © 2010 Publicis Canada!
  • RandyHui1

    Oct. 19, 2019
  • nareshbobade

    Sep. 14, 2019
  • VictorDeLaCruz28

    Sep. 7, 2019
  • LesleyLuciano

    Apr. 1, 2018
  • TimSalau

    Nov. 1, 2017
  • angybrooks

    Sep. 12, 2017
  • beschwar

    Aug. 6, 2017
  • ndoedo

    Jul. 28, 2017
  • casghar

    Jul. 26, 2017
  • DebMcD

    May. 25, 2017
  • SamHan13

    May. 23, 2017
  • RomanBabin1

    Apr. 18, 2017
  • MohitThukral

    Mar. 22, 2017
  • LoCabannes

    Feb. 13, 2017
  • XiaoleiGu

    Dec. 29, 2016
  • LucasWeber

    Dec. 28, 2016
  • DhinyNurdinahFadilla

    Nov. 22, 2016
  • solomonyonas

    Nov. 16, 2016
  • gnlogic

    Oct. 27, 2016
  • RamilDerogongun

    Aug. 8, 2016

Learn the different kinds of UX deliverables, when to use them, and how to create them with examples.


Total views


On Slideshare


From embeds


Number of embeds