Majestic Market Research MRSS firms based in India provides market research services in Automotive Industry, HealthCare & Eye Tracking. We are a member of the European Association of Opinion and Marketing Research Professionals ESOMAR.
Making computer-based products (and services) more usable is smart business. Usability increases customer satisfaction and productivity, leads to customer trust and loyalty, and inevitably results in tangible cost savings and profitability.
Because user-interface (UI) development is part of a product’s development cost anyway, it pays to do it right. Most software and Website development managers view usability costs as added effort and expense, but the reverse is more commonly true.
The first 10% of the design process, when key system-design decisions are made, can determine 90% of a product’s cost and performance, usability techniques help keep the product aligned with company goals
1. Quality in use requirements
Establish requirements for effectiveness, efficiency and satisfaction for the user groups and tasks identified in the context of use analysis and in the scenarios. Arrange a workshop attended by users developer's).
We provide a trained facilitator and a person to record the issues raised during the meeting.
Review each of the tasks in the context analysis report along with their associated task scenarios to confirm their relevance and importance.
Decide which task and user type needed usability criteria.
For each chosen task and user type estimate:
If there is an existing system, it can be evaluated by the selected users and tasks, and the results used to refine the usability requirements. Quality in use requirements should be evaluated by usability testing.
2. Detailed usability requirements
Decide which usability requirements are relevant. Examples of potential requirements are:
Interface elements (e.g. menus) should be easy to understand
For a walk up and purchase or use system, the purpose of the system should be easily understandable
The user documentation and help should be complete
The help should be context sensitive and explain how to achieve common tasks
The system should be easy to learn
The interface actions and elements should be consistent
Error messages should explain how to recover from the error
Undo should be available for most actions
Actions which cannot be undone should ask for confirmation
The system be customizable to meet specific user needs
A style guide should be used
The screen layout and color should be appealing
Arrange a workshop to review how to elaborate the requirements for the specific system being developed. The workshop should be attended by:developers, user's) if easily available
The objective of the design phase is to create and develop a user interface design that is based on the requirements specification, and that supports the users with their task at hand. Early designs will be simple and sketchy. These will mature into one final design through an iterative process of evaluation and redesign. Successful design will:
Create and develop design ideas using multidisciplinary input.
If necessary allocate tasks between humans and machines
Visualize design ideas using sketches, models and simulation/dynamic prototypes
Consider using parallel design
Evaluate design ideas with a few typical users. Get them to carry out typical simulated/real tasks, using methods that may include storyboarding or wizard of oz.
Expert or heuristic evaluation may also be used.
Ensure that the design takes account of design guidelines
Feed the results back into the design process quickly.
Iterate the process of design - evaluation until design objectives are fulfilled.
The objective of usability activities at the implementation stage are to ensure that detailed design takes account of usability principles.
This can be achieved by:
use of style guides and design guidelines
ensuring that rapid prototyping activities incorporate usability
The purpose of testing and measuring is to assess the degree to which user and organizational requirements have been achieved, and to provide feedback in a form that can be used by designers and developers to improve the user interface design. There are a number of different evaluation methods that vary in terms of formality, rigidity and the degree of user participation. The most suitable method will depend on the product being developed, the availability of representative users and financial/time restrictions. Evaluation can be user based or expert based. User based testing will provide information related to the task at hand - does this design support the user in their work. Expert inspections tend to identify lack of conformity to standards, interface design guidelines and expert comments based on experience. There are two objectives for testing and measuring
1. Diagnose usability problems
user-based methods such as participatory evaluation, diagnostic evaluation, and critical incident analysis should be used when possible, supported by questionnaires to assess attitudes
these can be supplemented by expert or heuristic evaluation. These methods should be used to improve early machine prototypes.
2. Evaluate whether usability objectives have been achieved
requirements for user performance and satisfaction can be evaluated by use of performance testing, cognitive workload and attitude questionnaires.
other usability objectives can be assessed by expert evaluation.
These methods should be used to test final prototypes. The methods will also provide diagnostic information that can be used to make last minute improvements, or provide requirements for the next release.
It is important to monitor the usability of the system after release to ensure that it meets user needs in the field. This should be used as an input to requirements for a new version or release.
Techniques for collecting user feedback include post release testing, use of questionnaires to survey user satisfaction, remote testing, analysis of help desk calls, and observing users.
AN ROI FRAMEWORK
Usability returns many benefits (return on investment, or ROI) to products developed for either internal use or sale
• Increased user productivity
• Decreased user errors
• Decreased training costs
• Savings gained from making changes earlier in design life cycle
• Decreased user support
• Increased sales
• Decreased customer support costs
• Savings gained from making changes earlier in the design life cycle
• Reduced cost of providing training (if training is offered through
the vendor company
MMRSS is a certified firm and complies with the following international standards