1 / 36

Designing the Information Experience

Designing the Information Experience . Linda Lior Rayne Wiselman. IX is a subset of UX. Information Design: D esigning the presentation of information to facilitate understanding

errin
Télécharger la présentation

Designing the Information Experience

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Designing the Information Experience Linda Lior Rayne Wiselman

  2. IX is a subset of UX Information Design: Designing the presentation of information to facilitate understanding Information Architecture: Structural design of the information space to facilitate intuitive access to content

  3. Designing the IX

  4. Evaluate!

  5. Research Understanding users and tasks Computer Programmer Thinks in mathematical models (Algorithms, Boolean logic)

  6. IX within the application The user interface is communication between the user and the technology (Everett McKay) • Your text provides the context and meaning

  7. Movement for Inductive User Interface Software can be made easier and simpler by: • Breaking down features into screens that are easy to explain • Focusing each screen on a single task • Suiting a screen's contents to the task • Making it obvious how to complete a task using the controls on the screen

  8. Shift towards providing assistance within the UI

  9. Is this inductive or deductive?

  10. Creating the IX

  11. Planning • Define the workflows – is the first time experience different? What is the learning curve? Are there prerequisite steps? • Where does the main UI content go? • Create UI text guidelines – consistency gives users confidence • Lock down terminology – start by reading the specs and creating a terminology list. Then investigate the terms used • Identify possible pitfalls and usability issues

  12. Identify content types • Splash pages and landing pages • Navigation elements (i.e., trees, tabs) • Tooltips and hover text • Buttons and labels • Wizards (welcome pages, titles, subtitles, explanatory text, options) • Status indicators and monitoring information • Popup and Error messages

  13. Example – Landing Pages

  14. Even a bit helps…

  15. UI text scrub process

  16. Define Highest Ring of Quality (RoQ) • Core to golden scenarios, high visibility, high impact • Core to silver scenarios, high-medium visibility, medium impact • Legacy, low visibility, non-core, low impact • Focus on the Gold

  17. GeneralGuidelines • Think about the purpose of the page • What does the user need to do? • What does the user need to know? • What is the most likely action? • Less is more - Avoid length blocks of text (Eye-tracking studies show that online readers tend to skip large blocks of text.) • Keep the text close to the options it relates to (closeness Gestalt principle)

  18. Ask yourself… • Are items grouped logically? • Is the language appropriate for the user? • Does the text provide the right amount of information? • What is the dog doing here?

  19. Is the text helpful?

  20. Example – What’s wrong here?

  21. UI Text Some practical suggestions

  22. Avoid redundancy

  23. Cut out extraneous text….

  24. Make the most of limited spaceEvery letter counts…. • This will result in… • Whether … • In order to… • Alternately, …. • As a result… • If… • To… • Or, … • In other words…. • Please…

  25. PM Text – avoid marketing text • “When you use this feature ….” (wonderful things will happen)

  26. Work with the developer • Terms that devs like to use: • “Abort” • “Terminate” • “Machine” • “Failed” (especially the product failed) • Formatting • Indentation (coding) • Enable this option With this option enabled you can…. • Spacing • Remember the Gestalt principle

  27. Notice the indentation

  28. Things to remember… • Users DO read the text • Need to find balance (can’t document the product in the UI) • Create a UI text process and get buyoff from stakeholders • PMs like to sell their feature • Developers are not writers • Guidelines make our lives easier • Don’t forget to evaluate! What seems clear to you, may not be to the reader

  29. Content Model

  30. Research: CustomersIdentify typical users

  31. Research Product • Customer need: I want to drink cold water • Business goal: Find a solution that fits my needs • Choose a solution: Ice; cooler; refrigerator • Requirements: Both hot and cold water • Limitations: Provide cold water for 100 people all day • Consider the options: Evaluate fridges • Buy: The product that best meets all my needs x x

  32. Research Content • Identify state of content • Current content set • Customer feedback • Content metrics • Third-party content • Evaluate competitive content • It was probably considered by your customers • Identify the case for content value • Increase revenue • Reduce costs • Aid deployment • Increase sales • Increase community

  33. PlanningDesign the structure of the content space On-box Online Wiki Blog Video Publicize strategy Blog strategy Forum strategy Web cast strategy Hierarchal Distributed Duplication strategy Link out strategy Off line reading strategy Loc strategy

  34. Implementation • Content types • Map to personas • Guide design: • Layout • Tone • Writing style • Guide review process • Review owners • Review criteria

  35. Evaluation and Maintenance

  36. Thank You To create a great information experience: • Know your customer • Map your content to user tasks, scenarios, and business needs (not to the features) • Use language your users understand • Use the right vehicles (what belongs in the UI, what belongs in docs) • Evaluate! QUESTIONS?

More Related