Our Process

Requirements

The first step is for us to understand the who, what, why, when and how of the task in hand to formulate a strategy and get a clear understanding of the project.

Competitor Analysis/Qualitative and Quantitative Research

The next step is to analyse any competitors and assess the strengths and weaknesses of these against the user's needs. We also conduct qualitative and quantitative research dependending on the project requirements.

Low Fidelity Wireframes

We will then visually communicate hypothetical concepts with users and team members for feedback and iterate designs as needed until a suitable solution is established. This will usually define the navigation and basic structure with mapping of the user journey. This will also help expose any potential usability issues at the earliest stage of prototyping.

High Fidelity Design

Taking the low fidelity wireframes, user flows and user/team feedback into consideration, We start to create the designs and apply any product branding, typography, colour scheme and icons as needed.

High Fidelity Prototypes

After the design stage is approved, We will quickly develop interactive prototypes either using HTML/CSS, Axure or inVision depending on the product and client requirements. This lets the team easily interact with the product and explore how well the product will be received before the product is developed.

Development

Depending on requirements we can develop the front end of the product with the use of HTML, CSS and JS libraries.

Testing

The final piece of the puzzle. We can play a part in the testing and ironing out of bugs along with recommendations of fixes before the launch of the product. At this stage it is not too late to remove/add certain features easily before launch. This can be the case with some products and due to our agile and iterative approach from the start of design this should always be an easy task.

Launch

Notice*

Please note: This is our process from the start to end of certain projects. This is not a fixed method and can be rearranged as required. For example in some cases a low fidelity prototype is required before high fidelity designs and a high fidelity prototype may not be required.