696b70e75affe8dd507bc38a83fbd965.ppt
- Количество слайдов: 117
Designing the Complete User Experience Day 2 Adaptive Path www. adaptivepath. com/presentations/complete/ info@adaptivepath. com
Yesterday • Discovery • Personas and scenarios • User research • Task analysis and mental models • High-level information architecture Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 2
Today • Designing the deep structures – Competitive analysis, content inventory, low-level IA • Prioritizing features • Interaction design – With notes on visual design • Prototyping, process, patterns in design • Usability testing • Design in the organization Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 3
Defining Web Design • Mastering applications • Understanding technologies • Techniques and methodologies for creating more effective design solutions Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 4
Defining Web Design • Functional Design The design of systems that support end-users' tasks and goals – User research – Information Architecture – Interaction Design • Communication Design The design of how these systems are expressed to the user – Interface design – Visual design – Content strategy Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 5
Overview Mostly “Big Projects, ” scaled down for small projects - yearly, quarterly Mental Model This is “Business as Usual” - daily/weekly (small & fast) Define the Audience Align MM & Content Model IA & Interaction Diagrams and Prototypes Prioritize Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 6
Designing the IA: A Bottom-Up Approach
What Is Information Architecture? A structure based on the patterns inherent in data that allows users to accomplish their goals. Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 8
Yesterday We Talked About High-Level Structures and Mental Models: 1. Figure out what users need: develop a mental model 2. Figure out what you have: develop a content model 3. Match them up. 4. Use it to create your IA • • Make a high-level structure based on mental model Make the detailed structure based on the content model Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 9
Today We’ll Talk About Deep Structures and Content 1. Figure out what users need: develop a mental model 2. Figure out what you have: develop a content model 3. Match them up 4. Use it to create your IA • • Make a high-level structure based on mental model Make the detailed structure based on the content model Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 10
The Process: Two Tracks Mental Model User Task Interviews Task Data Analysis Mental Model Diagram IA & Interaction Diagrams and Prototypes Align MM & Content Define the Audience Content Model Current State Research Competitive Content Model Review Content Model Diagram Prioritize Features Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 11
The Two Tracks, Diagrammed Surface architecture comes from Mental Model Deep architecture comes from the Content Model Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 12
The Two Tracks, Described 1. Task-based information architecture • • • Based on ethnography and usability principles Take user tasks apart (analysis) Then put them back together into a Mental Model (synthesis) Tasks become major content ‘buckets’ High-level model yields high-level architecture 2. Content-based information architecture • • Based on library science and information retrieval principles Take all the content and features apart (analysis) Then put it all back together again (synthesis) Content groups form deep structures of the architecture Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 13
Current State Research: Figure Out What You Have Mental Model User Task Interviews Task Data Analysis Mental Model Diagram IA & Interaction Diagrams and Prototypes Align MM & Content Define the Audience Content Model Current State Research Competitive Content Model Review Content Model Diagram Prioritize Features Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 14
Four Things To Look At • Content • Architecture • Interaction • Technology Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 15
What To Do • Walk through the existing site • Pay attention to details of implementation • Don’t think like a user – but don’t forget the user either Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 16
General Rules • Use existing documentation • Use the knowledge in people’s heads • Do all four activities concurrently Final Goal: “Blueprints” of the existing site Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 17
Content Audit • Content audit looks at broad categories – Sampling of pages – Sufficient for most projects • A more detailed content inventory looks is more thorough – Make a big list of every piece and its URL – Give each piece a unique ID – Use this for CMS and other migration projects Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 18
Identify Broad Types of Content • Typical Examples: – – – – Executive biographies Press releases Product descriptions Product documentation Contact information Tutorials Case studies Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 19
Content Audit - Basic Questions For each piece of content on the site, ask: • What is it about? • Who is it for? • What type is it? • Where does it come from? Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 20
Content Audit - Strategic Questions • Is it redundant? • Is it in line with current thinking? • Is it outdated? • Is it trivial? • Does it have historical value? -->In other words. . . can we get rid of it? Traffic analysis can help answer these questions. Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 21
Content Audit - Final Result • Spreadsheet with hundreds or thousands of lines, one line per page Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 22
Architecture Review • An overview of how content is structured • Identify organizational schemes • Map the site – Outline – Diagram • Refine content types (content types will be very important in a little while…) Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 23
Q: Can you automate the architecture review? A: Not really. Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 24
Typical Site-Mapping Tool Output Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 25
What You Actually Need To Know Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 26
The Desired Result Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 27
Interaction Review • Walk through existing interactive functionality – – Registration process Shopping cart Newsletter signup Etc. • Play out scenarios with a test account • Document interaction • Think like a QA tester – try to generate errors Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 28
Documenting Interactions: The Visual Vocabulary http: //jjg. net/visvocab/ Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 29
Technology Review • Identify technologies during walk-through: – Server-side technologies such as Cold Fusion, JSP, PHP, etc. – Client-side technologies such as DHTML, Java. Script, etc. • Talk to the technical people • Don’t be afraid to ask dumb questions • Ask “What’s that connected to? ” Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 30
Current State Analysis Deliverables Content Audit Spreadsheet or database showing content by type and topic Architecture Review Outlines or diagrams of site structure Interaction Review Diagrams, notes, lists Technology Review Technical brief Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 31
Next, Figure Out What They Have Mental Model User Task Interviews Task Data Analysis Mental Model Diagram IA & Interaction Diagrams and Prototypes Align MM & Content Define the Audience Content Model Current State Research Competitive Content Model Review Content Model Diagram Prioritize Features Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 32
Competitive Analysis • A thorough deconstruction of your competitors’ Web sites • Similar to market and customer research, but with an emphasis on functional implementations • Not simply limited to direct competitors Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 33
Identifying Competitors • Start with known rivals – See: marketing plan, business plan, etc. • Use online tools to broaden scope – “What’s related, ” Alexa, browse online directories • Look for other sites with similar features, even if they’re in a completely different industry – Search work, navigation, interface widgets, etc. • Use analyst reports to identify industry trends – Forrester, Jupiter, et al. Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 34
The Competitive Matrix • List features against competitors in a spreadsheet (build off of your findings from the current state analysis) • Use online tools to help fill in the technical details – www. websitegarage. com – www. siteowner. com Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 35
The Competitive Matrix • Build spreadsheet with feature-set against competitors’ sites • Fill in short descriptions of similarities and differences • Point out radically different solutions • Use principles of Heuristic Evaluation Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 36
The Competitive Matrix • Feature set and content types • Interface characteristics – Navigation vocabulary – Renderings (Tabs, Pull-down menus, etc. ) • Technology choices – Browser targeting – Advanced CSS or Javascript usage • Performance Statistics – Bandwidth usage and rendering speed for page types • Meta Tag Contents Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 37
Make Your Research Usable Mental Model User Task Interviews Task Data Analysis Mental Model Diagram IA & Interaction Diagrams and Prototypes Align MM & Content Define the Audience Content Model Current State Research Competitive Content Model Review Content Model Diagram Prioritize Features Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 38
“Chunk” Up the Existing and Desired Content • Review content audit and competitive matrix • Identify patterns within the content (subject, doc type, etc. ) • Group similar content together • Organize groups into hierarchies --> For a whole site, you want maybe 50 -100 “chunks” Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 39
Primary and Secondary Taxonomies - Wine. com Bestcellars. com Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 40
Content Map • Same type of tool as the Wine Cheese Gift Basket Product Detail Wine Product Detail Cheese Product Detail Basket Product Detail Category Info Varietal Profile Organic Cheesemaking Specialty Baskest mental model diagram • Lets you understand what you have and want in a single glance Region Profile • Arrange the chunks in a Review Wine Spectator Reprints Tools Varietal Comparison Chart meaningful way (e. g. , subject + type) Cheese Selector • We use Visio Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 41
Bringing Content Together with the Mental Model User Task Interviews Task Data Analysis Mental Model Diagram Align MM & Align the MM & Content Model Define the Audience IA & Interaction Diagrams and Prototypes Content Model Current State Research Competitive Content Model Review Content Model Diagram Prioritize Features Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 42
Slot Content Analysis Results Where it Fits the Mental Model • Content goes below the line • Review gaps (from yesterday) Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 43
Deep-Structure Architecture Revealed Surface structures come from the mental model. Deep structures come from the taxonomy-based Content Map Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 44
Prioritizing: What do we do first…second…never?
Prioritize the Features Mental Model User Task Interviews Task Data Analysis Mental Model Diagram Align MM & Align the MM & Content Model Define the Audience IA & Interaction Diagrams and Prototypes Content Model Current State Research Competitive Content Model Review Content Model Diagram Prioritize Features Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 46
Step 1: The “Big List” 1. Content Analysis and Content Map 2. Ten people in a room for an hour or two • • Blue sky • • Talk through scenarios Focus on what it should be (brainstorming rules) General Rule: People don’t have any problem telling you what they want, as long as they don’t have to make it or pay for it. • Real Challenge: Choosing which features to build Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 47
Step 2: Identify Dependencies and Baseline • What things must happen first? What are the mandatory groupings? • What is baseline? What are the “Must-Haves” that you can’t launch without? Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 48
Step 3: Have Stakeholders Figure Out • Feasibility: easy or hard, expensive or not, short or long to implement Rate each item in the list § 1 = low feasibility § 5 = high feasibility • Importance: to business, to user Rate each item in the list § 1 = low importance § 5 = high importance Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 49
Step 4: Graph the Findings High importance+ Low feasibility = HI High importance+ High feasibility = Watch for new technology Do Now Importance LOW Low importance+ Low feasibility = Low importance+ High feasibility = Don’t Bother LOW Consider Feasibility HI Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 50
Now Let’s BUILD Stuff!! Mental Model Iterative Process Define the Audience Align MM & Content Model IA & Interaction Diagrams and Prototypes Prioritize Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 51
Quick Iteration vs. Long Process • Operating a site – day to day • Adding features – weekly/monthly launches • “Big” projects – significant redesigns, yearly/quarterly Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 52
Now Let’s BUILD Stuff!! Mostly “Big Projects, ” scaled down for small projects - yearly, quarterly Mental Model This is “Business as Usual” - daily/weekly (small & fast) Define the Audience Align MM & Content Model IA & Interaction Diagrams and Prototypes Prioritize Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 53
Interaction Design
Information Architecture and Interaction Design • IA is about content and the structure in which it is located – How is it organized? – Where is it located? – Navigation and way finding systems • Interaction Design is about functions, and the flows that enable the user to accomplish them – What actions can the user do? – Entering and retrieving data – Exposing system capabilities Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 55
How Are They Different? Information Architecture Interaction Design Architecture Diagram Flow Diagram Organizing Content Interacting with Systems Hierarchies and Words Processes and Activities Seek help from librarians Seek help from engineers Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 56
Common Web-Based Interactions • Registration • Web-based Email • Shopping cart • Checkout • Setting up personal web pages, like “My Yahoo” and “My Netscape” • Online banking Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 57
The Interaction Designer’s Job • Understand how the user thinks about the tasks at hand • Show the parts of the system that enable the user to accomplish those tasks • Craft the visible parts to convey the right messages and clues Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 58
Good Thinking “Our conscious mind is constantly reducing visual input into patterns…. The philosophy is to present the components on the screen as recognizable visual patterns [so that] the user can choose, on a purely pattern-matching, unconscious level, which objects to consider consciously. ” - Alan Cooper, About Face Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 59
Principles of Interaction Design • Controls disappear when they use natural signals that can be unconsciously interpreted Interaction Visual Design* Discoverable Proximity Feedback Alignment Recoverable Repetition Context Contrast *From Robin Williams, Non-Designer’s Design Book Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 60
Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 61
Methods: Flow Diagrams • Use standard symbols • Include a Legend explaining the symbols • Avoid crossing lines • Include meaningful labels for all lines that need them • Follow all pathways to their natural end, OR • Clearly mark where your flow connects with another flow • Use good visual design principles • Include error cases Visual Vocabulary: http: //www. jjg. net/ia/visvocab Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 62
Methods: Schematics • • Make schematics that correlate to the flow diagram Use standard symbols to represent interaction devices • Show all functions • Use consistent names and labels across all flows and schematics • DO NOT include any visual design direction! • Use call-outs to describe any functionality that isn’t self-explanatory • Use good visual design principles • One schematic can serve multiple pages Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 63
Prototyping, Process and Patterns
Some Problems With Design Process • Research is effective and valuable, but never gets applied to end product • Communication gaps between research, design and development • Architects (or consultants) spending days creating deliverables nobody ever bothers to read • “Show me the numbers” Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 65
Historically, Page Design Didn’t Scale • In the olden days, designers would design HTML pages and put them on a server • But sites grew. . . – And grew. . . • Suddenly, redesigning or adding site-wide features was nearly impossible • Everyone clamored for template-based design – Put content in databases, squirt it out through consistent designs • Today’s dilemma: We need the flexibility of dynamic design, but the rigidity of templates is often too much Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 66
Prototyping Tips • Try to work in the Web’s native language if possible • Extremely tight iterations (daily!) serves as high-bandwidth team communication • Documentation captures “What we’ve learned, ” not “What I want you to do” • Avoid the “handoff” – the team refines a prototype through higher resolution versions, testing frequently Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 67
Going Dynamic • Prototype is built according mental model and architecture diagrams • Templates and content components can go through iterative design • Changes can be viewed globally and instantly tested Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 68
Benefits of Dynamic Sites • Higher initial development cost, but much lower maintenance • Separates operations of site from development • Do more with fewer resources • Inherent interface consistency benefits user experience Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 69
The Process: Before Dynamic Sites Author Editor Copy Edit Production Design QA Post Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 70
The Process: After Dynamic Sites Operations Development Author Production Design Editor Copy Edit Post Template System Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 71
Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 72
Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 73
Patterns in Design • Patterns are abstracted solutions to common problems in context • Think of a tailor’s pattern for a garment. • Applicable not only to architecture, but computer science, corporate organization, and (of course) Web design Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 74
Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 75
Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 76
• “Text Input boxes should be sized based on expected query length” • “For selecting between distinct search options, radio buttons are most appropriate” • “HTML submit buttons are more appropriate than image buttons” Remember: In Context Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 77
A hierarchy of patterns An almost infinite number of decisions at this level Knobs Doors Walls Rooms Buildings Communities Regions Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 78
A hierarchy of patterns Radio Button Forms Search Interface Page Layout Navigation System Site Architecture Integration Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 79
Patterns and Components • Group smallest patterns together into either content-inspired or user task-based components • Creates a heuristically-derived system of interface Legos • Can be mixed and matched to create site designs Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 80
Components Content List Item Detail Input Tabular Data Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 81
Standard Page Elements • Network Nav Bar • Personalization • Brand header – – Logo Search Cobrand Structured Navigation • Topic Path • Page Footer Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 82
Page Types • Components can be grouped together in any number of ways to create pages. Pages have distinct types, based on the tasks that can be accomplished on them. Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 83
Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 84
Usability Testing
Usability Testing = Easy Validation of Your Designs Mental Model Define the Audience Align MM & Content Model IA & Interaction Diagrams and Prototypes Validate Prioritize Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 87
Usability Testing: An Overview • Protocol development • Recruiting • Facilitating • Analysis Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 88
When To Test? NOW! • Anyone can do user research • A fast, easy and effective way to evaluate if your audience can use your product or site • Start simple: Friends and Family Test • Only one prerequisite: a semi-working prototype Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 89
Recruiting Users • For a simple test, find 3 -4 people similar to your site’s audience – Friends, family, coworkers from other departments • Personas should determine your test group • Start immediately: the better the subjects, the better the outcome Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 90
Recruiting Users • Determine target audience – demographic/webographic/psychographic • Seek them out – Existing user base, customer support inquiries, advertise on existing site – User groups, email discussion lists – Traditional means: classified ads, etc. – Use a recruiter: Charge per user based on how specialized your population needs to be Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 91
Developing the Screener • A simple script to weed out subjects • Write 20 questions that narrow in on who you’re after • Order questions from generic to specific • Be very clear and specific • Avoid jargon Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 92
Developing a Protocol • What is your site about? • What five features are most important? • Create a list of “tasks” – Two sentence mini-scenario for each feature • For more focused tests, do a feature prioritization exercise – Map feature importance with implementation difficulty Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 93
More on Tasks. . . • Testable tasks should be: – – – – Reasonable Specific Doable Described as end goals Appropriately sequenced Domain neutral Not too long, not too short Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 94
Running the Test (Mechanics) • Have the room ready – Computer set up in a generic state – Have appropriate start pages bookmarked • Make users comfortable – Describe how the test works and what they’ll have to do – Be clear that they are testing a product, they’re not being tested themselves Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 95
Running the Test (Interview Style) • Ask the right questions – “Describe this. ” – “What do you expect? ” – “Did that surprise you? Why? ” • Don’t offer help – If a task is too difficult for the user, tell them to stop and ask them to describe what happened Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 96
Logistics • Record the session with a camcorder arranged to capture both the screen and user • Have a partner take notes throughout session • Convince decision makers of the value of watching the tests – from coders to marketing to the CEO Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 97
What Did You Learn? • Did the evaluators consistently misunderstand anything? • Were they ever confused? What were they doing? • What mistakes were consistently made? • Which tasks did they have the most trouble with? • When did they look frustrated? What were they doing? • How many of the tasks were they able to do? Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 98
What Did You Learn? • Did they do the things that you had expected them to do? • Did they do things in the order in which you had expected? If not, what order did they do them in? • What did they find interesting? What did you expect them to find interesting, which they did not? • Did the site meet their expectations? If not, where did it fail them? • Do you know what their expectations were? • Did they know what the site is for? Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 99
Usability Test Timeline Timing Activity t – 2 weeks Determine test audience, start recruiting immediately t – 2 weeks Determine feature set to be tested t – 1 week Write first version of guide, discuss with team, check on recruiting t – 3 days Write second version of guide, recruiting should be completed t – 2 days Complete guide, schedule practice test, set up and check equipment t – 1 day Do practice test in the morning, adjust guide/tasks as appropriate t Test (usually 1 -2 days, depending on scheduling) t +1 day Discuss with observers, collect copies of all notes t +3 days Watch all tapes, take notes t +1 week Combine notes, write analysis t +1 week Present to team, discuss and note directions for further research Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 100
How It All Fits Together
Design Isn’t Performed in a Vacuum • Like project management, a hub in the multi-disciplinary process • Many disciplines contribute to what the user experiences Web Development Brand / Marketing Content Strategy PM Design Database Architecture Server Engineering Visual Design Data Analysis Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 102
Design in the Organization • In agencies, typically grouped with “Creative” disciplines • In-house, often a part of marketing • In Web-centered companies, a separate department Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 103
Visual Design • Big Picture thinking • Strong visualization skills • Task: To develop a visual language – Colors – Typography – Graphic style Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 104
Content Strategy and Writing • It’s The Content, Stupid • Visitors interact with your site for the content, not the design • Task: To define a voice – Copy guidelines – Style manual – Nomenclature Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 105
Brand Strategy and Marketing • The user experience is a key component of an organization’s brand • A user experience can be informed by brand attributes • Tasks: – To identify brand attributes – To provide market segmentation Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 106
Data Analysis and Reporting • Components of a user’s experience can be measured through interaction data • Usability and data analysis often go hand-in-hand • Task – analyze usage statistics (typically server logs) for important trends Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 107
Web Development and Engineering • Technologists clue user experience designers in to feasibility • Web developers know what’s possible on the front end – Help you create flows/schematics • Server engineers tackle deeper “Can we do that? ” questions – How long will a process take? How many hits to the database? • Database architects will develop schemas that impact the information architecture Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 108
Project Management • User Experience types tend to work closely with Project Managers • Both have “process” focus • Task – to make sure the project moves forward smoothly Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 109
So Who Does All of This?
There Are a Million Titles in This Business… • Art Director • Developer • Creative Director • Web Developer • Design Director • XYZ “Specialist” • UI Designer • Creative Integrator • Human Factors • DBA Engineer • System Specialist • Producer • Program Manager • Product Manager • Project Manager • Site Manager • Information Architect • Interaction Designer • Usability Engineer • Designer • Content Specialist • QA Manager • Visual Designer • Content Strategist • QA Specialist • Editor Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 111
One Title Can Mean Many Things… PRODUCER as Leader PRODUCER as Builder PRODUCER as Facilitator • Plans the project • • • Manages team • Creates requirements Java. Script, XML • documentation • from internal client • Hires and manages • external design or code the project meeting objectives Manages delivery of Receives request front-end display Takes responsibility for business and user Writes HTML, development vendor Implements pages • as specified by design team Reviews interim deliverables • Coordinates approval cycle Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 112
And Many Titles Can Mean the Same Thing… Wanted: Experienced professional to provide leadership for multiple sections of the web site. This person will establish a mission for each section, define business and user requirements, manage internal and external designers, developers, and copy writers to launch content and applications supporting the Company’s business goals. Some hands-on design and development work required. What’s the title? Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 113
The Title Could Be… – – – Producer Program Manager Product Manager Site Manager Creative Director Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 114
A Typical Project Team Lead Producer or Product Manager Creative Information Architect Visual Designer or Art Director Research Producer, IA, or Researcher Implement Developers HTML/Java. Script/XML coders Production Artists Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 115
This Project Internal Discovery Producer Task Analysis Researcher, IA Personas & Scenarios Prod. , Team, Stakeholders Competitive Analysis Producer Current State Analysis IA Model Comparison Researcher, IA, Prod. (Stakeholders) Info Architecture IA Interaction Design IA, Producer Prototype Team Usability Testing Researcher, Vendor (Team) Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 116
www. adaptivepath. com/presentations/complete/ info@adaptivepath. com Copyright 2001 Adaptive Path, LLC · info@adaptivepath. com · Designing the Complete User Experience · http: //adaptivepath. com/presentations/complete/ 117


