methods
consensus building
To create a clear shared vision for the purpose of your software project, a meeting is held with all the development, product management and other professionals relevant to the project.
Your product/project vision, required functionality, the different user groups and the development platform are explored. This also raises the awareness of how these factors influence the user interface. A consensus is built around in what way the UI architecture can realise your product/project vision.
user scenarios
User scenarios form the foundation for user interaction architecture. After exploring the variety of ways in which the software is used by the different user groups, a concise set of user scenarios is constructed.
This set is useful throughout the whole design process to highlight the needs of the users, to prioritise functionality and, most importantly, to eliminate the risk of feature‐driven design.
evaluation
Software, prototypes, designs, photoshop mock‑ups and/or design ideas are evaluated against human computer interaction metrics, related to structure, logic, dynamics and communication. Together with your team, the rationale behind the current UI design is uncovered.
With a thorough evaluation, usability problems can be identified and solved before development is completed.
analysis
user requirements analysis
The user requirements analysis is essential for finding the right user interaction for the target user group.
Our user scenarios are used to develop primary user concepts, which in turn define how straightforward the UI should be. The user concepts are then converted into requirements for the UI.
functionality priority analysis and optimisation
Prioritised functionality is fundamental to creating the UI architecture. Taking into consideration our analysis of project goals and user requirements, the priority is extracted.
According to this priority, we structure the functionality into different levels to stop them interfering with each other in the UI. We optimise the functionality by re‑organising and reducing the number of UI metaphors that represent it.
look + feel compliance analysis
The look + feel of a software application is a major factor in user‑acceptance and determines the productivity that can be achieved with this application.
Considering the complex web of related decisions and also on a rule–by–rule basis, an in‑depth analysis measures if the UI of the software is built according to the letter of the guidelines and the spirit of the platform’s look + feel.
3E’s analysis
ease of use, ease of learning, ease of remembering
In any software application there is always a trade‑off between the 3E’s:
- Ease of use:
- how efficient is the software when used 40 hours a week.
- Ease of learning:
- how quickly can the user build an overview and feel in control of the software, when used for the first time.
- Ease of remembering:
- how familiar and reassuring is the software for the user, when it is used only occasionally.
To achieve an optimum balance of the 3E’s we take into account the evaluation results of the software or prototypes and the analysis of project goals and user requirements.