PROCESS2020-06-25T16:02:38+01:00

Process

1. Discovery

It starts with the Discovery phase by creating user personas, journey maps, understanding a user’s pain points and competitor market research. As this will be a fundamental foundation for a successful solution.

2. User Flows

By creating user-flows, we illustrate the path a user follows through your website/app interface to complete single or multiple tasks, is a great way to map the products journey and interaction features.

3. Wireframing

Low & mid fidelity wireframes created as part of an initial skeletal framework of the site/app which will be used to visualise components, layout & hierarchy to perform a specific purpose and focus on functionality and validation of approaches.

4. Visual Design

We start High fidelity visuals by creating a visual language, Introducing detailed design specs like typography, colours, theme, styles, guidelines & Icons. A pattern library is created using an atomic design approach with, functionality, scalability & accessibility in mind.

5. Prototyping

With a visual at hand, the prototyping process takes it one step further. It will allow me to show the stakeholder’s an interactive product journey and communicate the design with more clarity. These prototypes are also used in the user testing lab.

6. User Testing

Sitting in user test sessions is a great way to understand how users are interacting with the proposed design allowing for a better judgment of the required iterations design improvements in the iteration phase.

7. Design Iteration

When visuals have been tested in lab feedback is provided on the bases of the results these are then implemented into the visuals and tested further to measure if its adaption was successful this is a refinement process until the results are improved & confirmed.

8. Build & Release

On confirmation of successful design validation. The build is initiated using code UI partial libraries with both front-end and back-end developers working in situ to ensure that logic is working correctly when the code is committed when using Handlebars.js. This then gets through QA & end to end testing before placed on our weekly release.

9. Measure & Learn

The MVP or features are then measured using split tests, analytics, client feedback. The Leanings allow us to analyse the user behaviours and will influence design decisions for better user experience.