1. User ExperienceDeliverables !by Publicis Canada UX Team © 2010 Publicis Canada!
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. Needs AssessmentWhat is it?A needs assessment is the process of collectinginformation about an expressed or impliedorganizational need that could impact project scopeWhy do we need it?It helps us to identify hidden needs from clientsor to clarify the objectives of the projectWhen do we need it?Usually for new clients or for the projects withmultiple and complex levels of stakeholders © 2010 Publicis Canada!
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. Requirements DocumentWhat is it?List of high-level requirements for a project, inalignment with business and project objectivesWhy do we need it?Helps to deﬁne project scope, budget andrequired deliverablesWhen 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 thereis a large number of requirements, a separaterequirements document will be created. © 2010 Publicis Canada!
7. User Persona / ScenarioWhat is it?A characterization and detailed proﬁle of users basedon digital behaviour, marketing segments, anddemographicsWhy do we need it?Help clients and project teams think from varioususers points of view and create content, featuresand functionality based on user needs!When do we need it?Required when users are not well understood orwhen one design must satisfy multiple types ofusers © 2010 Publicis Canada!
8. User Persona / Scenario (cont d)Persona Example © 2010 Publicis Canada!
9. Current Site EvaluationWhat is it?A usability inspection and assessment of awebsite against established, recognized humanfactors and usability principles, usuallyconducted by a usability specialist!Why do we need it?A quick way of identifying problems, primarilywith the user interface, for redesign effortsWhen do we need it?Used to justify a site redesign, to compliment otherevaluation methods, or as a sole evaluation methodwhen resources, scope, and/or budgets are limited © 2010 Publicis Canada!
10. Current Site Evaluation (cont d)Site Evaluation Examples © 2010 Publicis Canada!
11. Competitive UX AuditWhat is it?User experience evaluation of competitive or bestpractice sites or productsWhy do we need it?To discover which competitive website delivers agood user experience and to analyze whichelements contribute in what ways to theexperience!When do we need it?For projects focusing on enhancing userexperience against competitors © 2010 Publicis Canada!
12. Competitive UX Audit (cont d)Competitive UX Audit Example © 2010 Publicis Canada!
13. Content InventoryWhat is it?An inventory of site pages, content and assets,typically delivered in excel format organizing thelist of items based on the current site structureWhy do we need it?It is a basic ﬁrst step to assess the volume andthe quality of the site content that will inﬂuenceeffort, budget, and redesign recommendationsWhen do we need it?The basic content audit is required for allprojects, but the documentation is required forcontent heavy or complex sites © 2010 Publicis Canada!
14. Content Inventory (cont d)Content Inventory Example © 2010 Publicis Canada!
15. Usability Testing / ReportingWhat is it?Users are asked to carry out tasks according todeﬁned scripts while being objectively observedWhy do we need it?To ensure that designs are usable and that userscan carry out tasks efﬁciently, effectively, andsatisfactorily. Don t guess…test!When do we need it?When knowledge about users is low or when theteam wants to conﬁrm assumptions andunderstanding of user behaviour © 2010 Publicis Canada!
17. Card SortingWhat is it?A technique that helps determine the informationhierarchy of a website by writing content items oncards and placing the cards into logical groups toreveal the relationship between the content items!Why do we need it?Card sorting is a quick, inexpensive, and reliablemethod and is an important input to theinformation design processWhen do we need it?Needed for content-heavy websites or whencontent has become unorganized after increasinggrowth over time © 2010 Publicis Canada!
18. Card SortingCard Sorting Examples © 2010 Publicis Canada!
19. UX Deliverables in the Design Phase •  User Flow! •  Interaction Flow! •  Sitemap! •  Content Matrix!DESIGN! •  Wireframe! •  Features & Functionality Speciﬁcation! •  Prototype! © 2010 Publicis Canada!
20. User FlowWhat is it?A simple diagrammatical document that follows auser down a path of activityWhy do we need it?It helps us to create a logical and intuitive interfacesby anticipating users actions and thinking of thedifferent tasks they need/want to achieveWhen do we need it?For all projects. It may not be required as a formaldeliverables to the client unless it is necessary © 2010 Publicis Canada!
21. User Flow Abc.com! Abc.com! © 2010 Publicis Canada!
22. Interaction FlowWhat is it?A diagram or ﬂow map highlighting the interactionbetween the users and site featuresWhy do we need it?It helps to overview the core interactions within theapplication and to demonstrate the relationship andconnectivity between the functionalitiesWhen do we need it?For complex applications and systems thatrequire a lot of user interactions (e.g. communitysites, software, etc.) © 2010 Publicis Canada!
23. Interaction FlowInteraction Flow Examples Home © 2010 Publicis Canada!
24. SitemapWhat is it?A hierarchical visual model of the pages of a WebsiteWhy do we need it?A sitemap is a useful way of orienting clients andteams to the content of a website by showing adiagram of the entire sites contentsWhen do we need it?Almost every website project if the site requiresmultiple pages © 2010 Publicis Canada!
25. SitemapSimple Sitemap Example Comprehensive Sitemap Example © 2010 Publicis Canada!
26. Content MatrixWhat is it?A content table or an excel chart listing all thepages and modules of the site or systemspecifying content rules, description, attributes,and statusWhy do we need it?It s a great asset of a project helping project teamand clients managing all the variations, rules andstatus of the site content and modulesWhen do we need it?Content heavy or CMS driven websites orcomplex system © 2010 Publicis Canada!
27. Content MatrixContent Matrix Examples © 2010 Publicis Canada!
28. WireframeWhat is it?A visual guide to depict functionality and toillustrate page layouts and their informationalelements, before applying creative design!Why do we need it?Critical in the process of creating usable anduseful websites or web applications and bringsproject teams to a common understanding of theproductWhen do we need it?If there s a user interface involved thenwireframes are required. © 2010 Publicis Canada!
29. Wireframe (cont d)Low fidelity Wireframe High fidelity Wireframe © 2010 Publicis Canada!
30. Features & Functionality SpeciﬁcationWhat is it?Describes, in detail, the website s or webapplication s intended capabilities and interactionwith users and tied directly to a requirementWhy do we need it?Sets the client s expectations (in conjunction withwireframes and design comps) of what will bedelivered and puts the team on the same pageWhen do we need it?Needed for large projects, when there are a largenumber of features or functions, or when featuresand functionality are complex and must beexplained in detail © 2010 Publicis Canada!
31. Features & Functionality!SpeciﬁcationFeatures & Functionality Specification Examples © 2010 Publicis Canada!
32. PrototypeWhat is it?A working model of a website, clickable with theappearance of being functional, usually built fordemonstration purposes.Why do we need it?Provides a tangible, concrete concept thatsigniﬁcantly reduces communication andcomprehension gaps between team members. Itcan also be leveraged for usability testing.When do we need it?Mainly when user ﬂow is complex. © 2010 Publicis Canada!
33. Prototype (cont d)Prototype Examples © 2010 Publicis Canada!
34. About Publicis
User Experience TeamWe are specialized ina multi-disciplinary process of UserExperience Design to create•  Corporate Websites!•  Ecommerce!•  Marketing / Campaign Microsites!•  Community Sites / Social Media!•  Intranet / Extranet / CMS System Interface!•  Mobile Sites & Applications!We provideComplex UX analyses & solutionsthroughout the project lifecycle Contact: Jenna.Yim@Publicis.ca!•  Discovery, Deﬁnition, Design, and Development! Twitter: @Publicis_UXD! © 2010 Publicis Canada!
35. Thank You! Any Questions?!Contact: Jenna.Yim@Publicis.ca!Twitter: @Publicis_UXD! © 2010 Publicis Canada!