Our Process

Every project needs a plan, whether it is has a value of $500 or $100,000.
It needs to be managed in a structured way to ensure you get the results you expect.

As with all projects we know that they are movable beasts. In our experience it is very difficult to predict every possible hurdle that may occur, so we like to employ a flexible approach that allows room for change where necessary.

This allows creative input at every stage during a project from both us and yourselves, which can be managed efficiently and effectively. This is why we use this process and we know it works.

Project kick off

We sit down with you to get to the real guts of the project. This is where we define exactly what the aims of the project are and what will be delivered at end.

Then, dependent on the project, we use a number of tools to flesh out the requirements such as workshops or user research. This allows us to make educated assumptions about the types of people visiting your website, and the way that they will use it, ensuring your customers needs are always at the heart of what we design and create.

From this we develop the design concepts and information architecture (IA) and all other project documentation.

Design & development

We like to break each project down into a series of easy to manage releases, the first of which combines the design concepts and the information architecture into a working prototype. This allows you to start playing with the site as early as possible in the project and test how it all fits together.

Whilst this is happening, we can start working on the main technical areas of the site such as the set-up of any content management systems and the interactive areas of the site, documenting as we go.

Release cycles

Working in release cycles allows testing to be carried out at regular points during the project. When you have finished testing the initial release and all the findings have been documented, we create a plan for the next release including the schedule of work and expected timescale impacts of any major changes.

When the release is ready, its back to testing again, then another release and so on and so forth until the project is ready for the final release and all parties are happy.

We find this process an excellent way of working as you get to work on the project throughout, testing at every stage so you are not surprised by what is produced at the end. You can make as many changes and suggestions as necessary throughout until you are happy with the final product.