1 / 28

Management Bloopers

Management Bloopers. Counterproductive Attitude. Counterproductive Attitude. Misunderstanding what user interface professionals do Treating user interface as low priority Discounting the value of testing and iterative design. Designer versus programmer distinction Variations

vanna-petty
Download Presentation

Management Bloopers

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. Management Bloopers Counterproductive Attitude

  2. Counterproductive Attitude • Misunderstanding what user interface professionals do • Treating user interface as low priority • Discounting the value of testing and iterative design Management BloopersChapter 8

  3. Designer versus programmer distinction Variations Assuming GUI programmer = GUI designer Assuming graphic designer = GUI designer Blooper 76Misunderstanding what UI professionals do Management BloopersChapter 8

  4. Blooper 76 • Assuming GUI programmer = GUI designer • Profound misunderstanding • Disregards value of good UI • Top-notch UI programmers • Poor user interfaces • Lack of UI design experience • Toolkit influences programmer • Lack of compromise Management BloopersChapter 8

  5. Blooper 76 • Assuming graphic designer = GUI designer • Beautiful versus usable • World wide web • Graphic design • Detailed component appearance • UI design • Choice of components / labels • Easy to learn • Helpful toward user goals Management BloopersChapter 8

  6. Management Understands distinction between UI programmers / UI designers UI designers / Graphic designers Chooses well-rounded teams UI designer Prepares UI specification Analyzes user requirements Devises usability testsPage 419, Table 8.1 Avoiding Blooper 76 Management BloopersChapter 8

  7. Blooper 77Treating UI as low priority • Assuming that usability has low impact on market success • Initial expense, later revenue • Usability speeds market acceptance • Assuming that the user interface is only “fonts and colors” • Narrow view • Interaction Management BloopersChapter 8

  8. Blooper 77 • Assuming that users can adapt to anything • Functionality isn’t everything • Competition • Rationalizing • Budget cuts • UI affects entire product • Assigning the GUI to less experienced programmers Management BloopersChapter 8

  9. Management High priority Usability impact Early discovery Competitive marketplace Bad UI = Bad product Experience matters Avoiding Blooper 77 Management BloopersChapter 8

  10. Blooper 78Discounting the value of testing and iterative design • Good designers do not need iteration • “We do not have the luxury of usability testing” • Allowing no time to fix usability problems Management BloopersChapter 8

  11. Blooper 78 • Good designers do not need iteration • Engineering discipline • Scientific basis • Clear requirements • Generation / Alternatives • Constraints / Trade-offs • Testing / Evaluation / Revision • Revisions equal failures? • Business risk Management BloopersChapter 8

  12. Blooper 78 • “We do not have the luxury of usability testing” • Shorten development schedule • Testing helps navigate • Need not be expensive • Skipping does not save money • Marketplace testing Management BloopersChapter 8

  13. Blooper 78 • Allowing no time to fix usability problems • Testing occurs without correction • Tests as proof • Tests as required step Management BloopersChapter 8

  14. Avoiding Blooper 78 • Test at every stage • Simple testing • Valued feedback • Predevelopment tests • Page 431, Table 8.2 • Testing participants • Flexibility • Use results! Management BloopersChapter 8

  15. / Bloopers 8.2 / 8.2.1 – Poor Tools and Building Blocks 8.2.2 – Anarchic Development 8.2.3 – No Task Domain Expertise on Team 8.2.4 – Giving Programmers Faster Computers

  16. Poor Tools and Building Blocks – 8.2.1 / Blooper 79 / • Developers want to choose the best tools for their development efforts, but many times base their selection on the wrong criteria like: • While these are important issues, they have very little to do with the usability and/or usefulness of the applications that will be built using them. Management BloopersChapter 8

  17. Poor Tools and Building Blocks – 8.2.1 / Blooper 79 / • What GUI Developers should be looking for in a development suite are things like: • Developers and managers typically look at what benefits a tool will provide for them, not the benefits it will provide to the people who will be using the interface designed with that tool. • Consultant recommendations on alternative development tools are regularly met with much gloom and doom. Management BloopersChapter 8

  18. Poor Tools and Building Blocks – 8.2.1 / Blooper 79 / • 5 Examples of Tools Hampering Usability • Menus that Violate Users’ Muscle Memory • Unresponsive Components • Inadequate Navigation Feedback • Missing Important Visual Distinctions • Focus on appearance and layout, rather than function Management BloopersChapter 8

  19. Poor Tools and Building Blocks – 8.2.1 / Blooper 79 / • Avoiding Blooper 79 • The author does not provide a specific solution to avoid this blooper, rather he restates the importance of these development tool features: Management BloopersChapter 8

  20. Anarchic Development– 8.2.2 / Blooper 80 / • Uncontrolled, non-repeatablecrisis-of-the-moment based Development. vs. • Proven, repeatable, company goalsand user requirement based Development. • Examples p.442 • Programmers making business decisions • Basically a total melt-down scenario Management BloopersChapter 8

  21. Anarchic Development– 8.2.2 / Blooper 80 / • Avoiding Blooper 80 • Implement a professional development process and make sure to stick to it. • Don’t Hack … Design • Developers are Publishers and should act like it! • Give GUI experts more clout • Take Responsibility Management BloopersChapter 8

  22. No Task Domain Expertise on Team - 8.2.3 / Blooper 81 / • Examples of task domain experience on p.462 • No in-house UI Designers for complex domains • UI designers have no contact with experts • Designing “in the dark” • The burden of task domain identification and locating professionals in that domain falls upon the development organization Management BloopersChapter 8

  23. No Task Domain Expertise on Team - 8.2.3 / Blooper 81 / • Avoiding Blooper 81 • User-Centered design process • User’s task domain expertise is a must • Learn about the user’s work method • Use testing to guide design, not grade designers • When all else fails … hire outside experts Management BloopersChapter 8

  24. Giving Programmers Faster Computers - 8.2.4 / Blooper 82 / • Some justifications • Some Costs • Users can’t afford nor do they need an upgrade • Not everyone has T1 access speeds, or can even get them • Programs may end up being poorly designed and simply rely on pure processing power to make up the difference. Management BloopersChapter 8

  25. Giving Programmers Faster Computers - 8.2.4 / Blooper 82 / • Avoiding Blooper 82 • Compile on fast servers • Use mid-range systems to test product on • Try to design to the lowest common trait • Keep bandwidth limitations in mind • Put yourself in the users shoes (pocketbook) Management BloopersChapter 8

  26. / THE END / NO MORE BLOOPERS!!! Management BloopersChapter 8

  27. Final Exam Review • 40% Johnson chapter 5-8. • What are Interaction Bloopers? • What are Web Bloopers? • What are Responsiveness Bloopers? • What are Management Bloopers? • 40% Project (sliders, radio buttons, combo box plus painting and Timers) • 50% commenting code • 20% Comprehensive: broad questions asking informed comments on GUI design, GUI toolkits and the building of GUI applications in Java. Management BloopersChapter 8

  28. Course Review • Project due Monday, midnight • I will write the exam Tuesday night and base it on code received. • Course evaluation forms can be supplemented with direct communication. • I thought presentations were very well done and will post grades this weekend (all A’s and B’s as of today). Management BloopersChapter 8

More Related