maintained by Lars Pind
|
- The Vision
We want our users to be happy. We can't make our users happy by only discussing where to place the buttons. It requires an understanding of our users and how their daily life with our software is going to be. That's what this is all about: Tackling the UI design problem at a higher level. (updated April 11, 2001)
This is what you need to learn and do to develop your own user interfaces.
- 1. Know your users and what they need
How to do user-centered requirements (updated June 5)
- 2. Design a user interface that gives them what they need.
ACS Human Interface Elements (NEW! Added August 28)
ACS Visual style guide for admin interfaces (updated July 3)
- 3. Find the problems that you overlooked.
How to do a heuristic evaluation (updated August 14)
How to do usability testing (updated June 19)
Personas (stable) updated June 22, 2001
If we want to design good user interfaces, we have to know who we're designing them for. The personas answer this question by presenting a cast of made-up people, presented with rigorous detail, believed to be representative. We only care about people that are hands-on, interacting with the software. The guy who writes the check and the general stakeholders will get their say through use-cases and other means. If they're not using the software themselves, we shouldn't desing the UI for them.
Master Wireframe (stable) updated July 11, 2001
This illustrates what the user experience is going to be like.