Unfortunately in the rush to get products to market, testing and refactoring of the user experience is often one of the first things to be neglected. I am currently working on an internal application for one of my clients in the capacity of product owner - specifying the detail of the system functionality. With very aggressive deadlines, and a long list of functionality to be delivered, we have had to be fairly savage about cutting the number of iterations of design and development to get the system up and running in time. Sadly this has meant that the current user experience is patchy and in places unintuitive. For the second version of the software, I hope to devote one or more development sprints to refactoring usability, and hope to apply some of the skills I learnt his week during our user pilot next month.
- People's success in carrying out a particular task, and their satisfaction levels do not necessarily correlate
- 10% of your project budget should be dedicated to usability. This can improve a website sales conversion rate by 87%
- I am not the user - it is imperative to carry out studies with real users and use the feedback to drive the direction of the design
- You only need 5 users in a test to detect 85% of the problems
- Try to integrate features for both novice and expert users so you are providing a good user experience to different types of users
- You don't have to reinvent the wheel - you can/should use pattern libraries and platform conventions to make design and workflows more intuitive
More information about usability week can be found on the NN/g website: