1. William H. Bowers – whb108@psu.edu Orchestration & Flow Cooper 9

2. William H. Bowers – whb108@psu.edu Topics Flow and Transparency Flow and Transparency UI Transparency Guidelines UI Transparency Guidelines Inducing and Maintaining Flow Inducing and Maintaining Flow Follow Mental Models Follow Mental Models Direct, Don’t Discuss Direct, Don’t Discuss

3. William H. Bowers – whb108@psu.edu Topics Keep Tools Close at Hand Keep Tools Close at Hand Modeless Feedback Modeless Feedback Orchestration Orchestration Possibility vs. Probability Possibility vs. Probability Quantitative Information Quantitative Information

4. William H. Bowers – whb108@psu.edu Topics Avoiding Unnecessary Reporting Avoiding Unnecessary Reporting Command Invocation vs. Configuration Command Invocation vs. Configuration Interrogation Mode Interrogation Mode Hiding Ejector Seat Levers Hiding Ejector Seat Levers

5. William H. Bowers – whb108@psu.edu Flow and Transparency “Condition of deep, nearly meditative involvement” “Condition of deep, nearly meditative involvement” “Gentle sense of euphoria” “Gentle sense of euphoria” Extremely productive Extremely productive The ultimate UI is no UI The ultimate UI is no UI

6. William H. Bowers – whb108@psu.edu UI Transparency Guidelines Follow mental models Follow mental models Direct, don’t discuss Direct, don’t discuss Keep tools close at hand Keep tools close at hand Provide modeless feedback Provide modeless feedback

7. William H. Bowers – whb108@psu.edu Follow Mental Models Users have different mental models Users have different mental models Patterns of cause and effect Patterns of cause and effect Race car gauges Race car gauges

8. William H. Bowers – whb108@psu.edu Direct, Don’t Discuss Developer’s idea of UI is two way communication Developer’s idea of UI is two way communication Users want UI to work like a car Users want UI to work like a car –Direct software’s actions –Receive direct feedback Software dialogs can be aggravating Software dialogs can be aggravating

9. William H. Bowers – whb108@psu.edu Keep Tools Close at Hand Use palettes or toolbars Use palettes or toolbars Make it easy to transition between tools Make it easy to transition between tools Heads up displays Heads up displays Display status information on screen edges Display status information on screen edges

10. William H. Bowers – whb108@psu.edu Modeless Feedback Modal dialogs stop program flow Modal dialogs stop program flow Feedback must be clear and easy to see Feedback must be clear and easy to see Cooper wants continuous MS Word count Cooper wants continuous MS Word count

11. William H. Bowers – whb108@psu.edu Orchestration Users would work without program, if possible Users would work without program, if possible User would work without UI, if possible User would work without UI, if possible The best UI is transparent The best UI is transparent All UI elements should work together All UI elements should work together

12. William H. Bowers – whb108@psu.edu Orchestration Finesse Finesse –Less is better - streamline –File open, save, rename, etc. Invisibility Invisibility –Good UI’s are invisible –Don’t get in the way of functionality

13. William H. Bowers – whb108@psu.edu Possibility vs. Probability Probability of discarding changes is remote Probability of discarding changes is remote Therefore option shouldn’t be in a dialog Therefore option shouldn’t be in a dialog Standard print dialog is unnecessary Standard print dialog is unnecessary

14. William H. Bowers – whb108@psu.edu Possibility vs. Probability We can’t design/code for every possibility We can’t design/code for every possibility Segregate possible from probable Segregate possible from probable Make edge cases unobtrusive Make edge cases unobtrusive

15. William H. Bowers – whb108@psu.edu Quantitative Information Raw numbers don’t always help Raw numbers don’t always help Tufte Tufte –Show data as ‘compared to what?’ –Show the data, don’t tell about it Use appropriate level of detail Use appropriate level of detail Use graphical representation Use graphical representation

16. William H. Bowers – whb108@psu.edu Quantitative Information Show status progression Show status progression Ask forgiveness, not permission Ask forgiveness, not permission Too much detail is confusing to users Too much detail is confusing to users Don’t stop to report normalcy Don’t stop to report normalcy Handle minor problems Handle minor problems

17. William H. Bowers – whb108@psu.edu Avoiding Unnecessary Reporting Users do not need all the details Users do not need all the details Issue reassuring clues of wellness Issue reassuring clues of wellness Do not burden the user with trivia Do not burden the user with trivia Do not use dialogs to report normalcy Do not use dialogs to report normalcy Do not stop for non-serious problems Do not stop for non-serious problems Continue to move towards the goal Continue to move towards the goal

18. William H. Bowers – whb108@psu.edu Command Invocation vs. Configuration Printing vs. printer configuration Printing vs. printer configuration Separate the commands Separate the commands Do not ask for configuration every time Do not ask for configuration every time Remember past usage to predict current use Remember past usage to predict current use

19. William H. Bowers – whb108@psu.edu Interrogation Mode Demands information from the user Demands information from the user Should present choices instead Should present choices instead Use sensible interaction Use sensible interaction Report failure properly Report failure properly Have a reason for everything Have a reason for everything

20. William H. Bowers – whb108@psu.edu Interrogation Mode Makes the program appear Makes the program appear –Ignorant –Forgetful –Weak, lacking initiative –Fretful –Overly demanding

21. William H. Bowers – whb108@psu.edu Hiding the Ejector Seat Levers One time or rare procedures One time or rare procedures Irreversible actions Irreversible actions Prevent accidental use Prevent accidental use

22. William H. Bowers – whb108@psu.edu Questions & Discussion