Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Detailed Design: Preserving the UX Vision

jsokohl
September 26, 2011

Detailed Design: Preserving the UX Vision

How to make sure the UX vision actually gets communicated to your team.

jsokohl

September 26, 2011
Tweet

Other Decks in Design

Transcript

  1. CONFIDENTIALITY The concepts and methodologies contained herein are proprietary to

    Regular Joe Consulting LLC. Duplication, reproduction or disclosure of information is this document without the express written permission of Regular Joe Consulting is prohibited. Enjoy the work. We hope you find it useful. Detailed Design Preserving the UX from concept through delivery UX Australia ’11 Joe Sokohl @mojoguzzi @RegJoeConsults Friday, September 2, 2011
  2. § What is “detailed design,” anyway? § What’s the problem

    § What are some solutions @mojoguzzi @RegJoeConsults Agenda 2 Friday, September 2, 2011
  3. § What is “detailed design,” anyway? § What’s the problem

    § What are some solutions @mojoguzzi @RegJoeConsults Agenda 2 Friday, September 2, 2011
  4. @mojoguzzi @RegJoeConsults Schedule Intros What is detailed design? Who does

    it? Where does it break down? Why? Break What are some solutions? How do we work within our projects? Break How does Agile fit in? Open discussion, Q&A 3 Friday, September 2, 2011
  5. @mojoguzzi @RegJoeConsults Who this workshop applies to § Agencies §

    Independent UXers § Highly regulated areas: healthcare, government, military § Anyone working with distributed teams (including cross-border, multiple time zone teams) 6 Friday, September 2, 2011
  6. @mojoguzzi @RegJoeConsults Who this workshop might not apply to §

    Heterogenous teams § UXers who also do the front-end development of their apps § Co-located, nimble teams who don’t have a need to retrace steps § Teams in which no one dies, no one leaves, and no new people come on board 7 Friday, September 2, 2011
  7. @mojoguzzi @RegJoeConsults Who this workshop might not apply to §

    Heterogenous teams § UXers who also do the front-end development of their apps § Co-located, nimble teams who don’t have a need to retrace steps § Teams in which no one dies, no one leaves, and no new people come on board 7 Then again.... Friday, September 2, 2011
  8. Determining what the problem is So what’s the big deal,

    anyway? 10 Friday, September 2, 2011
  9. @mojoguzzi @RegJoeConsults Typical documentation approaches § Research artifacts such as

    competitive reviews, heuristic analysis, mental models/affinity diagrams, and personas § User/task matrixes § Hi-level wireframes § Concept models § Card sorts § And on and on and on... 11 Friday, September 2, 2011
  10. @mojoguzzi @RegJoeConsults Typical documentation approaches § Research artifacts such as

    competitive reviews, heuristic analysis, mental models/affinity diagrams, and personas § User/task matrixes § Hi-level wireframes § Concept models § Card sorts § And on and on and on... 11 Friday, September 2, 2011
  11. @mojoguzzi @RegJoeConsults Exercise 1: Create your own details § Look

    at the wireframe. § You need to let the development team know how to realize this wireframe as a functioning Web-based experience. § In 10 minutes, identify what you think would be needed. If you run short of time, circle items on the page that you would communicate. § Think how you would do this. 12 Friday, September 2, 2011
  12. @mojoguzzi @RegJoeConsults What’s the difference between reqs & specs? §

    Requirements § Requirements cannot be “gathered” § Requirements are not features § Requirements are not specifications § Specifications § “Effective documentation combines text and images to describe the anatomy and physiology of a product.” § “With a complete spec in hand, engineers should not have to make a single guess about the appearance or behavior of the product.” 16 Friday, September 2, 2011
  13. @mojoguzzi @RegJoeConsults What’s the difference between reqs & specs? §

    Requirements § “Anything that drives design choices” (B. Lawrence, 1997) § Minimal Specifications § “This might work for a tightly integrated team....In most cases, though, it frustrates the developer... and disappoints the customers....” § Understand the Goal § “Instead of being dogmatic about how much detail to include...remem- ber your goal: to understand the user’s objectives with the system well enough to enable developers proceed at low risk of having to do rework.” 17 Friday, September 2, 2011
  14. @mojoguzzi @RegJoeConsults Levels of requirements 18 § Levels of requirements

    § Business § User § Functional § System § Business rules § Quality Friday, September 2, 2011
  15. @mojoguzzi @RegJoeConsults 19 VIEWW Summary Activities • Gather Input on

    Business, User and System Requirements • Define Business Requirements • Define User Requirements • Develop Creative Brief • Define System Requirements REQUIREMENTS DOCUMENT Discover the project goals, define requirements, and frame the initial scope of an application. VISION INCEPTION ELABORATION WORK WEB Activities • Create High-Level User Experience Design • Create User Proof-of-Concept • Conduct Usability Testing • Create High-Level System Architecture • Create Technical Proof-of- Concept • Develop Initial Deployment Specification HIGH-LEVEL DESIGN DOCUMENT Activities • Usability Testing • User POC • Create Detailed User Experience Design • Assess and Select Technologies • Deployment Plan • Detailed Architecture • Create Technical POC • Coding Standards • Plan and Implement Development Environment DETAILED DESIGN DOCUMENT Activities • Create Deployment Plan • Update Detailed Design Document • Develop Components (Component Source) • Conduct Code Review FUNCTIONAL TESTING RESULTS Activities • Initial Data Load • Deployment • Create Administrative Guide • Develop User Education Manual • Transition to Maintenance Team USER ACCEPTANCE TESTING RESULTS Design the information structure and system architecture of the application. Refine the User Experience Design & System Design so an application can be built. Develop the application, integrating front end and back end systems. Deploy the finished application into production, transfer ownership to support and maintenance teams. Friday, September 2, 2011
  16. @mojoguzzi @RegJoeConsults FiveDs Summary Discover Design Define Develop Deliver Define

    project goals, business reqs, and initial scope. Activities •Define goals •Key success factors •VOC workshops •EOC interviews •B/U/S requirements •Site analysis •Audience analysis •Initial use cases •Business processes Further define a set of requirements and create systems and UX models Activities •Brainstorming •Scenario building •Wireframes •Visual direction •HL Info Architecture •HL Sys Architecture •Define technology Refine design details, create final design and obtain signoff. Activities •Merge visual and functional design •Final content •Test scenarios •Object analysis, modeling, design •Database analysis and design •Design documentation Build and integrate front-end and back-end systems. Activities •Image and page creation •Content integration •Coding •Unit testing •System staging in QA environment •Incremental QA and testing on multiple platforms Complete the commercialization of the product Activities •Acceptance testing •System and knowledge transfer •Product deployment •Marketing campaign 20 Friday, September 2, 2011
  17. @mojoguzzi @RegJoeConsults FiveDs Summary Discover Design Define Develop Deliver Define

    project goals, business reqs, and initial scope. Activities •Define goals •Key success factors •VOC workshops •EOC interviews •B/U/S requirements •Site analysis •Audience analysis •Initial use cases •Business processes Further define a set of requirements and create systems and UX models Activities •Brainstorming •Scenario building •Wireframes •Visual direction •HL Info Architecture •HL Sys Architecture •Define technology Refine design details, create final design and obtain signoff. Activities •Merge visual and functional design •Final content •Test scenarios •Object analysis, modeling, design •Database analysis and design •Design documentation Build and integrate front-end and back-end systems. Activities •Image and page creation •Content integration •Coding •Unit testing •System staging in QA environment •Incremental QA and testing on multiple platforms Complete the commercialization of the product Activities •Acceptance testing •System and knowledge transfer •Product deployment •Marketing campaign 21 Friday, September 2, 2011
  18. @mojoguzzi @RegJoeConsults 22 • • • User Experiences Go Beyond

    the User Interface Rich Internet Application Solutions Users achieve goals by performing tasks Reliable content and data form the foundations of a strong user experience Single, reliable view of the user’s entire relationship with the enterprise supports business processes critical to the delivery of a seamless experience They accomplish tasks by interacting with content, features, and functions in the agent portal and other applications, software and tools User interfaces bring the user experience alive, providing simplified, enjoyable online interactions and instant feedback in flexible, intuitive and forgiving workspaces Loosely joined customer- facing and internal business processes support quick and continuous experience improvement Powerful Interactions Single View of the Customer Information Delivery Transactional Marketing Campaign Management Analytics Reporting and Monitoring Notification Workflow Others Content Management Authentication and Authorization Identity Management Syndication Web Sites Distributed Content and Functionality product / service content & data analytic data meta data user Business Processes User Interfaces Experience Enablers Software / Tools Applications Expectations frame users’ experiences through brand perception and prior experience Beautiful experiences are more than pixel deep Friday, September 2, 2011
  19. @mojoguzzi @RegJoeConsults Like any UX project... § How does your

    artifact help further the UX vision? § Who are you creating artifact for? Who’s going to use it? § What do they need? § How can you meet their needs while not losing sight of the UX vision? § Do you have a need to proceed? 24 Friday, September 2, 2011
  20. @mojoguzzi @RegJoeConsults An extended design process metaphor 25 The genius

    in our styling department is that they not only have a great feel for design, but also for the fact that the design needs to function properly on a motorcycle. That melding of functionality and styling is what makes our motorcycles very, very special. Friday, September 2, 2011
  21. @mojoguzzi @RegJoeConsults Detailed Design Activities § Detailed sketches § Detailed

    scenarios with branching § User-centered use cases § Visual design specifications § Database design, specifically, fields & interactions § Exact interaction design, to include motion § High-fidelity (and possibly evolutionary) prototypes § L10N/I14N/A11Y § What else? 32 Friday, September 2, 2011
  22. @mojoguzzi @RegJoeConsults Exercise 2: Who Does What § Typical roles

    on a project § IA Information architect § IxD Interaction designer § VisD Visual designer § BA Business analyst § PO Product owner § PM Project manager § SA Systems architect § DA Data architect § DBA Database analyst § Dev Developer § QA Quality assurance analyst 33 Friday, September 2, 2011
  23. @mojoguzzi @RegJoeConsults Exercise 2: RACI § Decide what role does

    which task § RACI § Responsible: Does the task § Accountable: Signs off the work Responsible does § Consulted: Provides input, opinions, advice § Informed: Consumes output & information from the team § Only 1 Accountable per task § Work in teams, then we’ll gather to discuss 34 Friday, September 2, 2011
  24. @mojoguzzi @RegJoeConsults What’s Your Definition? • How do you define

    “detailed design”? 35 Friday, September 2, 2011
  25. @mojoguzzi @RegJoeConsults What’s Your Definition? • How do you define

    “detailed design”? • My definition? A detailed design is • The body of information that conveys sufficient detail to communicate that which can be coded. • Just enough detail to enable the non-UX team (dev, biz, mkt, release) to understand the UX designer’s intent. 35 Friday, September 2, 2011
  26. @mojoguzzi @RegJoeConsults Maybe a bit tooooo much detail.... 38 Planning

    Track BaselineCM Baseline Configuration Management Release Manager once per project BaselineCM Create a Scenario Business Analyst Every iteration User QoS Requirements Scenario List Scenarios BaselineCM Create a Quality of Service Requirement Every iteration Lifestyle Snapshot Scenario List Iteration Start CM Plan CM Guidelines CM Access Control Policy CM Baseline Report CM Guidelines scenarios BaselineCM Plan Project IPM Officer Once, at start of project Project Manager Dev Manager QA Manager Master Schedule Org Process Guidance Tailoring Guidelines Vision Statement Personas Project Process Instance Project Plan Master Schedule Risk Management Strategy Project Commitments Track Complete Define-Update Test Approach Architect Test Approach Test Metrics Test Approach UATs QoS Req List Subject Friday, September 2, 2011
  27. @mojoguzzi @RegJoeConsults Maybe a bit tooooo much detail.... 38 BaselineCM

    Create a Scenario Business Analyst Every iteration User Experience Architect QoS Requirements Scenario List Scenarios BaselineCM Create a Quality of Service Requirement Every iteration Lifestyle Snapshot Scenario List Iteration Start BaselineCM Create Product Requirements Every iteration Application Architect scenarios QoS Requirements Lead Developer Service Specifications Reference Solution Application Diagram System Diagram Functional Requirements UI Flow Model Operational Requirements BaselineCM Establish Environments Build Engineer Once per iteration Integration Sequence Rationale for Integration Sequence Support Docs for Integration Environment Product Integration Criteria BaselineCM Create Solution Architecture Once at the start of a project and on-going at start of each iteration Threat Model Performance Model Existing Architecture Vision Statement Org Coding Guidelines Static Analysis Guidelines Static Analysis Rules Coding Guidelines Architect UATs QoS Req List Domain Model Subject Matter Expert Deployment Diagram Logical Data Center Diagram Selection Justification Infrastr… Architect Peer Review Feedback Friday, September 2, 2011
  28. @mojoguzzi @RegJoeConsults Where do they break? Why 39 Team proximity/regulatory

    need/system complexity Need for Detailed Design Friday, September 2, 2011
  29. @mojoguzzi @RegJoeConsults Where do they break? Why 39 Team proximity/regulatory

    need/system complexity Need for Detailed Design Friday, September 2, 2011
  30. @mojoguzzi @RegJoeConsults Requirements masquerading as specifications Traditional approach §1.1.1. The

    system shall allow the teacher to click a control which displays the first answer in the lesson. NOTE: Subsequent answers can be accessed by individual controls after the first answer is displayed. The “Show Answers” and “Show First Answer” controls shall be displayed outside of lessons in a toolbar in the Learning Environment. Answers should be displayed to both the teacher 40 Friday, September 2, 2011
  31. @mojoguzzi @RegJoeConsults Requirements masquerading as specifications 40 User story approach

    As a clinician and/or front desk assistant, I need to record the writer, provider(s), assistant(s), as well as the date and time of entry for every clinical note, so that I can maintain accurate clinical records. Friday, September 2, 2011
  32. @mojoguzzi @RegJoeConsults 41 Requirement: Turn indicators 1.3.2.5a: The system shall

    include the ability for the operator to indicate a changed direction of travel Friday, September 2, 2011
  33. @mojoguzzi @RegJoeConsults 43 BA’s Doing UX In the 10+ companies

    I consulted for in the past 6 years, only one had UX professionals contributing to the project. http://www.modernanalyst.com/Resources/Articles/tabid/115/articleType/ArticleView/articleId/1735/ Are-you-ready-to-wear-your-UX-hat-when-duty-calls.aspx Friday, September 2, 2011
  34. @mojoguzzi @RegJoeConsults Special order 191 47 Major Taylor will proceed

    to Leesburg, Va., and arrange for transportation of the sick and those unable to walk to Winchester, securing the transportation of the country for this purpose. The route between this and Culpeper Court-House east of the mountains being unsafe will no longer be traveled. Those on the way to this army already across the river will move up promptly; all others will proceed to Winchester collectively and under command of officers, at which point, being the general depot of this army, its movements will be known and instructions given by commanding officer regulating further movements. III. The army will resume its march tomorrow, taking the Hagerstown road. General Jackson's command will form the advance, and, after passing Middletown, with such portion as he may select, take the route toward Sharpsburg, cross the Potomac at the most convenient point, and by Friday morning take possession of the Baltimore and Ohio Railroad, capture such of them as may be at Martinsburg, and intercept such as may attempt to escape from Harper's Ferry. IV. General Longstreet's command will pursue the main road as far as Boonsborough, where it will halt, with reserve, supply, and baggage trains of the army. V.General McLaws, with his own division and that of General R. H. Anderson, will follow General Longstreet. On reaching Middletown will take the route to Harper's Ferry, and by Friday morning possess himself of the Maryland Heights and endeavor to capture the enemy at Harper's Ferry and vicinity. Friday, September 2, 2011
  35. @mojoguzzi @RegJoeConsults Big, grandiose statement 50 Anything that specifies user

    behavior or activities that affect users belongs to the user experience team Friday, September 2, 2011
  36. @mojoguzzi @RegJoeConsults A more realistic way to say it 51

    Anything that specifies user behavior or activities that affect users belongs to the purview of the user experience team Friday, September 2, 2011
  37. @mojoguzzi @RegJoeConsults What Are Some Solutions § Frameworks § Style

    guides and pattern libraries § Accurate diagrams and traceable notes § A proverbial seat at the table. 52 Friday, September 2, 2011
  38. @mojoguzzi @RegJoeConsults What Are Some Solutions § Frameworks § Style

    guides and pattern libraries § Accurate diagrams and traceable notes § A proverbial seat at the table. 52 Friday, September 2, 2011
  39. @mojoguzzi @RegJoeConsults Frameworks and design principles § Windows Presentation Framework

    § Well-commented HTML5/CSS3 § Product-specific Frameworks § NextGen Design Principles & Frameworks: a Case Study 53 Friday, September 2, 2011
  40. § OS style and programming guides § YUI! § Search

    Patterns from Peter Morville @mojoguzzi @RegJoeConsults Style guides and pattern libraries 57 Friday, September 2, 2011
  41. § OS style and programming guides § YUI! § Search

    Patterns from Peter Morville @mojoguzzi @RegJoeConsults Style guides and pattern libraries 57 Friday, September 2, 2011
  42. 60 Display All Taxes & Fees - Currency References Use

    Case: 3.3 Requirements Matrix: 4.A.1, 4.A.2, 4.A.3, 4.A.4 Site Map: site_map_display_all_fees Base Wireframe: 4.1,4.2,4.3,4.4,4.5 Separated Rooms and Fees 1 The room stay is separated by first the total for all rooms reserved, without any taxes or fees. Then the estimated taxes and fees appears, followed by the total stay amount. If taxes and fees are included in the rate, use the term “included”. Breakdown of Taxes and Fees 2 The system breaks out and identifies all taxes, separate from any optional service charges. The CPM system provides the tax and fee information. If taxes and fees are included in the rate, use the term “included in reservation amount”. Optional Service Charges 3 If the property assesses any additional yet optional charges, they appear here. If there are no optional charges, do not display anything. 1 3 Functionality of this page is based on the current reservation review, reserve, and confirmation pages. It covers reservations made in currency amounts. The GCCI free night reservation confirmation wireframe appears on the next page. All modified items should be consistent with existing functionality and visual standards. 2 4 Additional Confirmations 4 The Reservation Amount module appears the same on the following pages: • Reservation Confirmation Email • Change Reservation • View Reservation • Cancel Reservation It contains the same information as the Reservation summary, just in a different layout. Friday, September 2, 2011
  43. 61 Display All Taxes & Fees - Currency References Use

    Case: 3.3 Requirements Matrix: 4.A.1, 4.A.2, 4.A.3, 4.A.4 Site Map: site_map_display_all_fees Base Wireframe: 4.1,4.2,4.3,4.4,4.5 Separated Rooms and Fees 1 The room stay is separated by first the total for all rooms reserved, without any taxes or fees. Then the estimated taxes and fees appears, followed by the total stay amount. If taxes and fees are included in the rate, use the term “included”. Breakdown of Taxes and Fees 2 The system breaks out and identifies all taxes, separate from any optional service charges. The CPM system provides the tax and fee information. If taxes and fees are included in the rate, use the term “included in reservation amount”. Optional Service Charges 3 If the property assesses any additional yet optional charges, they appear here. If there are no optional charges, do not display anything. 1 3 Functionality of this page is based on the current reservation review, reserve, and confirmation pages. It covers reservations made in currency amounts. The GCCI free night reservation confirmation wireframe appears on the next page. All modified items should be consistent with existing functionality and visual standards. 2 4 Additional Confirmations 4 The Reservation Amount module appears the same on the following pages: • Reservation Confirmation Email • Change Reservation • View Reservation • Cancel Reservation It contains the same information as the Reservation summary, just in a different layout. Friday, September 2, 2011
  44. 61 References Use Case: 3.3 Requirements Matrix: 4.A.1, 4.A.2, 4.A.3,

    4.A.4 Site Map: site_map_display_all_fees Base Wireframe: 4.1,4.2,4.3,4.4,4.5 Separated Rooms and Fees 1 The room stay is separated by first the total for all rooms reserved, without any taxes or fees. Then the estimated taxes and fees appears, followed by the total stay amount. If taxes and fees are included in the rate, use the term “included”. Breakdown of Taxes and Fees 2 The system breaks out and identifies all taxes, separate from any optional service charges. The CPM system provides the tax and fee information. If taxes and fees are included in the rate, use the term “included in reservation amount”. Optional Service Charges 3 If the property assesses any additional yet optional charges, they appear here. If there are no optional charges, do not display anything. 1 3 Functionality of this page is based on the current reservation review, reserve, and confirmation pages. It covers reservations made in currency amounts. The GCCI free night reservation confirmation wireframe appears on the next page. All modified items should be consistent with existing functionality and visual standards. 2 4 Additional Confirmations 4 The Reservation Amount module appears the same on the following pages: • Reservation Confirmation Email • Change Reservation • View Reservation • Cancel Reservation It contains the same information as the Reservation summary, just in a different layout. Friday, September 2, 2011
  45. @mojoguzzi @RegJoeConsults Things to keep in mind § Integrate requirements

    and specifications closely. § Provide iterative guidance to engineers, product manager, and marketers. § Use well-structured, carefully written language that avoids ambiguity. § Highlight language with diagrams that support the specification of experience. § Strive to limit the formality of documentation to just enough, just in time. 64 Friday, September 2, 2011
  46. @mojoguzzi @RegJoeConsults Agile and an FDA-Compliant Company “One can never

    get away from needing to provide 'objective evidence' of design inputs, verification & validation and design outputs, this being the bare framework of what is required by the FDA and most, if not all the international medical device quality requirements.” 67 Friday, September 2, 2011
  47. @mojoguzzi @RegJoeConsults “The Problem with ‘Quick and Dirty’...” 68 “...‘dirty’

    is remembered long after ‘quick’ is forgotten.” Friday, September 2, 2011
  48. @mojoguzzi @RegJoeConsults Find a way to detail your design §

    You can’t develop a user-centered product from user stories § You can use personas to ask, “What would Juan do?” § Take photos of sketches. Place them in the backlog. § Embed scenarios into the backlog for empathy traceability 70 Friday, September 2, 2011
  49. @mojoguzzi @RegJoeConsults Exercise 3: The Challenge Game § Divide into

    two teams § Challenge team creates potential probs/challenges § Solution team creates features & strengths of the product § Challenge team selects a card from the deck and plays it face up § Solution team tries to find a card that can provide a solution to it. § If the Solution team can’t play a reasonable solution card, the Challenge team gets a point. Otherwise, the point goes to the Solution team. § Work together on each challenge to find that solution. 71 Friday, September 2, 2011
  50. @mojoguzzi @RegJoeConsults 74 In preparing for battle, I have always

    found that plans are useless... “ Friday, September 2, 2011
  51. @mojoguzzi @RegJoeConsults 74 In preparing for battle, I have always

    found that plans are useless... ...but planning is indispensable. —Dwight Eisenhower “ ” Friday, September 2, 2011
  52. @mojoguzzi @RegJoeConsults So... 75 Detailed design is... § The body

    of information that conveys sufficient detail to communicate that which can be coded. § Just enough detail to enable the developer to understand the UX designer’s intent. § The codification of empathy, tracing UX vision through development Friday, September 2, 2011
  53. @mojoguzzi @RegJoeConsults Sources and Inspiration § Axure Rapid Protoyping §

    axure.com § Brown, Dan § Communicating Design: Developing Web Site Documentation for Design and Planning, Second Edition. New Riders § Goodwin, Kim § Designing for the Digital Age: How to Create Human-centered Products and Services. John Wiley & Sons § Morville, Peter & Jeffrey Callender § Search Patterns. O’Reilly Media, Inc § Wiegers, Karl § Software Requirements, 2nd Edition. Microsoft Press § Zaki Warfel, Todd § A Practitioner’s Guide to Prototyping. Rosenfeld Media 77 Friday, September 2, 2011