Thursday, January 24, 2008

User Requirements for User Interface Design

User interface is the face of your application & unless it thrills all the stakeholders, your Project is never going to be successful.

I often notice the same mistakes committed in User Interface Design at the early stages of a Project. Here are some of those "evils" :-

1. Scope : The Scope of the Project is usually not defined clearly & as a result, a lot of unwanted action items creep into the scope.

2. Ambiguity : Often, the lack of clarity in defining a particular requirement leads to multiple interpretations.

3. Assumptions : Often, the Developers assume things on the behalf of the Users. Again, this may lead to multiple interpretations.

4. StakeHolders : it's very important to involve all the Stakeholders in the Project ( Users, Managers, Developers, etc. ) early. Else, UI redesign might become the main focus of the Project !

Here are some thing that I do to capture the User Requirements ( on a Page/Page basis ) :-

1. Description
2. Trigger
3. Success & Failure Criteria.
4. Items on the page
5. Clairifications.

No comments: