One of the most heated debates during Web sites or intranet designs are discussions were developers and designers discuss whether such a design or form or whatever is the best for the users. In most of these discussions everyone is just assuming that what makes sense to himself/herself is what will make sense to users. In most of the times, actual users’ answer is “none of the above”.
For example, a 60 years old person who rarely uses a computer has serious trouble figuring out that hovering over a menu item will cause the menu to expand into the second level. For most designers or developers this is a no brainer. Same for floating panels or drag and drop operations and so on.
Most requirements documents mention actual users just in term of numbers; something like: expected number of users is X and expected number of concurrent users is Y and it is all about performance measures and not about knowing the actual users who will be using the system. Many developers and designers have never met the customers and can not even imagine how they look like or what they are actually using the machines. As a result, with unknown users, geeks are developing what they see best –for themselves.
Not understanding the end users is one sure way the application will not be a success. On the other hand, making really simple applications that targets the end users needs is one the reasons the IPod and the IPhone were smashing successes.
One the popular methodologies used to design a user-centric interface is the use of personas. Personas are imaginary users that are targeted during the design. There can be one or more personas for any given application. This is a good antidote for the problem of designing application for self rather than for the actual users (called mirror personas) For example, when designing Visual studio, Microsoft came up with three personas : Mort, the opportunistic developer, likes to create quick-working solutions for immediate problems and focuses on productivity and learn as needed. Elvis, the pragmatic programmer, likes to create long-lasting solutions addressing the problem domain, and learn while working on the solution. Einstein, the paranoid programmer, likes to create the most efficient solution to a given problem, and typically learn in advance before working on the solution. (Reference: http://www.nikhilk.net/Personas.aspx )
The use of personas was introduced in the famous book “The inmates are running the asylum” ( http://www.amazon.com/Inmates-Are-Running-Asylum/dp/0672316498 )
Needless to mention, the success of this methodology depends on having personas that accurately represent the end users, otherwise it will be defeating the purpose.
This will help eliminate problems that are sure to come from discussions that go like this: For an application that is targeting people with very superficial knowledge of PCs:
- Developer1 : How will the user be able to change that setting?
- Developer2: Very simple, all they need to do is open this XML file and edit the corresponding node with the updated value.
- Developer1: Cool, That means our application is generic and configurable.
Of course you can imagine the users’ reaction when told to simply open the XML file, look for the node “xyz”, etc. Even worse are the problems that may come out of such users actually trying to edit this XML file.
Personas can be equally helpful when trying to figure out what features may be most useful to “users” and what features can be scoped out of the project or how to prioritize features or releases.
References:
