1. Practical Interface Guidelines
Things they did not teach us in programming class

2. Introduction What? Practical Interface Guidelines When? July 14, 2006
Where? SIC 2006 (Denver, CO)
Who? Gregg Seelhoff
Why? Improved user interface results in:
Better software
More sales
Fewer customer support issues
How?

3. Definitions Practical Interface Guidelines
Providing something immediately actionable
Interface
The way in which a program interacts with its users
Guidelines
Strong suggestions (i.e., not rules)

4. User Interface Considerations
Design
Implementation
Testing

5. User Interface Considerations
Design – Theoretical
Implementation – Functional
Testing – Practical

6. Interface Design
Audience
Narrative
Workflow
Metaphors

7. Audience Know your audience! Users have expectations.
Novice users need simpler interfaces.
Power users demand options.
Applications that have a critical job function can afford to have a more complex interface, but…
Ease of use is always the goal.

8. Narrative
When designing software, include a narrative description of a typical user session.
If the application replaces an existing solution, tend toward a similar, albeit streamlined, process.
Consider writing documentation first (or simultaneously); if the process is difficult to document clearly, the user interface may be too confusing.

9. Workflow Minimize actions Let user get right to the task
Use defaults for standard options
Omit advanced options from basic workflow
Reduce swapping between mouse and keyboard

10. Metaphors Metaphors are good; Similes are better.
Use a concept that is understood by the target audience.
Harness existing knowledge of the problem domain and methods.
Similes serve as a mental framework for getting started with the software.
Do not allow yourself to be restricted by metaphors (or take it too far).

11. Interface Implementation
Responsiveness
Consistency
Usability

12. Responsiveness React to user input immediately. Feedback is essential:
Visual
Audio
Tactile
Any action that is not immediate must indicate that work is happening.
If an action takes more than a few seconds, it must have a progress indicator.

13. Consistency Conform to user expectations.
Be consistent throughout program.
Never alter the normal behavior of a control.
Use standard controls for standard program behavior.
Use standard window controls and system menu options.
Do not remove menu options.
Avoid modes.

14. More Consistency Keyboard: Mouse: Clipboard:
Never disable system keys.
Use standard keyboard shortcuts.
Mouse:
Select on click (press).
Take action on release.
Clipboard:
Support standard behavior.
Only use after explicit user action.

15. Accessibility Wherever possible, support users with disabilities:
Blind - support screen readers.
Deaf - use visual notification.
Physically restricted - support alternative input devices.

16. Accessibility Wherever possible, support users with disabilities:
Blind - support screen readers.
Deaf - use visual notification.
Physically restricted - support alternative input devices.
Color Blind - avoid reliance on colors only.

17. Usability Use wizards or setup assistants.
Show quick start or tutorial on first run.
Make the most common functions easiest to access.
Support tool tips and other hints.
Have all actions available from the program menu.
Do not rely on double-clicking.

18. Interface Testing Alpha Testing Focus Groups Beta Testing
Customer Support

19. Alpha Testing Internal/private testing
Runs the full duration of development
Eat your own dog food:
Use the software as your users would.
If you find something annoying or problematic, chances are good that potential customers will feel the same way.
Start testing from scratch on a regular basis.

20. Focus Groups Testing with “real” users: Observe actual interactions.
Family and friends
User groups
Formal focus groups
Observe actual interactions.
Resist the temptation to lead or assist.
Never be defensive or apologetic.
Record the proceedings, if possible.
Review all feedback.

21. Beta Testing External testing: Review all feedback.
Open (public)
Closed (private)
Review all feedback.
Respond to let testers know that you are paying attention.
Every report is valuable, but…
Do not let beta testers design the software.

22. Customer Support “The customer is always right.”
Every customer question or complaint is an opportunity.
For each reported problem, there are likely hundreds or thousands of users who did not bother to contact you.
Never get defensive (or offensive) with customers or users.
All feedback is valuable.

23. Resources About Face by Alan Cooper (“Father of Visual Basic”)
Apple Human Interface Guidelines
Windows User Experience Guidelines
Association of Shareware Professionals
Gamecraft blog

24. Questions?
Answers.