A Mosaique website always starts with the user. It’s important to properly understand what a client needs the site to achieve for their business but how it looks and works is created around the needs of the customer.
Our starting point is analytics from the current site (where they exist) as well as evaluation of digital solutions created by competitors.With these statistics and background information, we brainstorm the issues so that we can create the skeletal structure of the site. Next we drill down on the objectives through journey mapping.
By doing so, we build a picture of the end product, define the demographics and understand what the client offers against what the user needs and expects from a digital interface. This forms the foundation of a well-pitched, interactive and functional user journey that inspires the design.
product enables user to achieve their goals – the tasks that it was designed to carry out and/or wants needs of user.
Effectiveness (ease of use)
quantitatively measured by speed of performance, or error rate, and is tied to a percentage of users.
user’s ability to navigate the interface to some defined level of competence after some predetermined period of learning. Also, refers to ability for infrequent users to relearn the system.
user’s perceptions, feelings and opinions of the product, usually captured through the testing process or an evaluation of the voice of the customer.
Design with knowledge
With all of our findings and research achieved, the design of the site will be a collaborative approach between the client, tech team and specialist UI designer.
The initial stages are to establish wireframes focused around user flow, navigation and functionality. Using all the data established through our research and the agreed wireframes, the design team can now gets creative with UI happy in the knowledge that the solution adheres to solid usability principles.
Prototyping is cheaper than retrofitting
When the first draft design has been agreed, we can test our research and design efforts through a prototyping system. This enables us to test the UI without actually coding anything. This is good for testing key, or complex, user functions that are possibly new to the user.
Being able to work with a prototype allows us to carry out interaction testing on our design assumptions, gather feedback, determine changes and apply improvements to our concept based on real people using with our solution before any expensive programming work is undertaken.
When we feel the product is ready to implement, we always take a breather at that stage.
We look closely at the solution and compare what we’ve got with the initial specification. Interactive and functional elements may have been added, edited or deleted based on the creative process so far and the solution may have changed considerably from the plans drawn up at the outset.
Talking this through with the client, together with any cost implications, are a necessity to manage the build process so that it fits in with allocated budgets and timelines.
The final outcome of the evaluation is releasing the solution for production. This is only done when we feel we have thoroughly completed the testing process. All this preparation means we create the best possible user experience, we gain a higher return on investment for the client and there are minimal changes to the planned programming thereby avoiding expensive development costs.