• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Communicating Design
 

Communicating Design

on

  • 1,617 views

Communicating Design

Communicating Design

Statistics

Views

Total Views
1,617
Views on SlideShare
1,617
Embed Views
0

Actions

Likes
2
Downloads
37
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Communicating Design Communicating Design Presentation Transcript

    • Communicating Design By Daniel M. Brown Presented by Stanley Chang Ph.D. student, University of Michigan
    • Outline • About the Author • Introduction • Simple intro. to User Needs Documents • The good of the book
    • About the Author
    • Dan Brown IA & User experience design • Consulting work • Writing and speaking • Commitment to IA communities
    • Consulting Experience • Developed user models, interaction models, information architectures, and content models for such clients as First USA, the World Bank, webMethods, and US Airways. • Developed wireframes and user flows for major applications on USPS.gov, including ZIP Code Lookup, Online Tools, and Carrier Pickup. Designed usability tests and analyzed results to improve applications.
    • Dan Brown > Speak and Write
    • Introduction
    • Structure of the book • What is deliverable? • Why produce deliverables? – Consistency of vision – Accountability – Traceability • The Ten deliverables • Layers of each deliverable • Tips of presenting • How are they used with other documents?
    • The Ten Deliverables • User Needs Documents – Personas, Usability test plan and Usability test results • Strategy Documents – Concept models, Content inventories and Competitive analyses • Design Documents – Wireframes, Flowcharts, site maps and screen designs
    • Deliverable, Like a Cake • Layer 1 • The most important elements • Layer2 • Enhancement, some background information • Layer3 • Very further details
    • Layer Example • Layer1 • Layer2 • Layer3
    • Tips for Presenting Deliverables • Establish and • Invite the minimal number communicate a purpose of people possible • Decide what you want to • Send materials around get out of the meeting before the meeting before going into it. • Write up an account of • Think through participant the meeting. expectations, agendas, • Take pride in running a and questions good meeting • For new clients, assume the first meeting won't go well
    • User Needs Documents
    • Personas A summary representation of the system's intended users, often described as real people. Also known as: user profiles, user role definitions, audience profiles.
    • Persona > Overview • Purpose – Help prioritize system features and content that best support the audience • Audience – Design team the primary audience • Context – At the beginning of a project • Challenges – Summarizing can be tough – Dealing with companies that have done business successfully for years without personas
    • Persona > Creating > Layer 1 • Name • Motivations and needs • Scenarios
    • Persona > Creating > Layer 2 • System Feature • Behavior • Quotes
    • Persona > Creating > Layer 3 • Demographic information • Technology comfort level • Personal background • Photograph
    • Persona > Justification • Recruit for usability test • Rationalize existing design decisions • Clients not buying into personas • No time or resources • Identify extraneous content • Show how existing segmentation models are inadequate
    • Persona > Presenting > Meeting Purpose • Buy-In meeting: Selling the Idea – Only at the very beginning – Show the need for personas – Demonstrate their function • Feedback meeting: Getting input from the team – Need to be well-structured • Brainstorm meeting: Building personas Together – Review and then construct
    • Persona > Presenting > Meeting Structure • Priority order approach – Most important persona first • Steps followed approach – The most popular meeting structure – Explain the process • Family resemblance approach
    • Family resemblance approach
    • Family resemblance approach Personas Tree
    • Persona > Presenting > Key Points • Keep meeting participants engaged • Keep the agenda on track • Make use of research
    • Persona > With Other Documents • User-Needs Documents – Usability Test Plan – Usability Reports • Strategy Documents – Competitive Analysis – Concept Model • Design Documents – Wireframes – Site maps – Flowchart – Screen Designs
    • Usability Test Plan The usability test plan describes the goals, method, and approach for a usability test. .
    • Usability Test Plan > Overview • Purpose – Lay out the approach for a usability test • Audience – Everyone in the team • Context – Whenever scheduling usability testing • Challenge – Creating a multi purpose document but not out of scope
    • Usability Test Plan > Creating > Layer 1 • Test objectives • Test logistics • Test scenarios
    • Usability Test Plan > Creating > Layer 2 • User profiles and Screener • Pre-test and post-test questions • Script
    • Usability Test Plan > Creating > Layer 3 • Background • Functional details • Expected behaviors
    • Persona > Presenting > Meeting Purpose • Securing buy-in – Go through every aspect of the plan • Soliciting input • Testing the test – Mock test – Ensure you can do everything you need to in the given amount of time – Potential issues
    • Usability Test Plan > Presenting > Key Points • Risk of losing sight of objectives • Usability newbies • Methodological questions
    • Usability Test Plan > With Other Documents • User-Needs Documents – Persona – Test results • Design Documents
    • Usability Reports The usability report is the outcome of a usability test, whose results are compiled into an actionable format.
    • Usability Reports > Overview • Purpose – Highlight the main findings • Audience – Everyone • Context – As long as there is a test • Challenge – The more details you include, the more you need to explain – Distinguishing between observations and recommendations
    • Usability Report > Creating > Layer 1 • Test summary • Basic observations • A little context • Next Step
    • Usability Report > Creating > Layer 2 • Summary of observations • Summary of recommendations • Severity level • User quotes
    • Usability Report > Creating > Layer 3 • Quantitative data • User profiles • Tactical recommendations
    • Usability Report > Creating > Risks • Inflating severity • Too much or too little detail
    • Usability Report > Presenting > Meeting Purpose • Presenting findings to stakeholders: – They are more concerned about the overall tenor of the usability tests – Spend more time on the pre- and post-test questions that shed light on the audience more broadly • Presenting findings to the design team: – They are more interested in the observations & solutions
    • Usability Report > Presenting > Meeting Structure • Start with the basics: – Test objectives – Test method – Logistics • Summarize the observation first • If have to report findings ASAP – hold a usability test debriefing
    • Usability Report > Presenting > Key points • Be objective and honest – Tell the truth – Offer several explanations why Truth
    • You may face this question… “what should we do?"
    • This might not work…. “I don't solve, I just identify” • Difficult design problems do not have just one answer • So, force yourself to think of a couple different approaches for each main design problem • Explain, and then suggest
    • Usability Reports > With Other Documents • User-Needs Documents – Persona – Test plan • Design Documents – Wireframes – Site maps and flowcharts The number of users is represented by the weight (thickness)
    • The other deliverables…. • Strategy Documents – Concept models, Content inventories and Competitive analyses • Design Documents – Wireframes, Flowcharts, site maps and screen designs Please refer to the books
    • What’s Good about This Book • Use 3 layers to introduce how to create different documents • Readers can take advantage of the layer structure to create documents depending on different context • Provide practical suggestions on meeting strategies • Great reference book for people new to this field
    • Thank you