Head London

About us

We have a clear, transparent way of working.
Vision, Scope, Build.

Vision Image

Vision

A collaborative discovery phase, producing a conceptual visualisation of what the project should be.

This is where we take the brief and start to make it concrete. We’ll have workshops with you to flesh out the thinking and thrash out the issues. We’ll look at your existing research and institute new research if necessary. This is where we look at business objectives and consumer needs, where we produce high level wireframes and discuss requirements. We’ll involve a multi-disciplinary team from our staff and as much collaboration with you as possible.

By the end of this process we’ll have a clear and concrete sense of short term and long term strategy.

Scope Image

Scope

This is where we turn vision sketches into blueprints and working prototypes.

In collaboration with our clients and partners, we’ll write use cases (short, clear text descriptions of software functionality) and make detailed wireframes so that everyone understands how a site works rather than just how it looks.

We’ll work through and finalise design decisions, information architecture and ensure consumer needs are being fulfilled. We’ll expose all of this work to users to see if it’s working, refining and redesigning to ensure it’s optimized to create a great user experience.

Again, we have the advantage of calling on multiple disciplines under one roof. The rapid back and forth and frequent communication between different people and skills means that we know the site will look and feel the way you want it to, and the technology will work the way it’s supposed to.

Scope Build

Build

This is where we execute. Easy to underestimate, but if you don’t do this flawlessly, you’ve wasted your money.

So we’re particularly focused on methodologies that let us get this right every time.

This is where we determine the technical architecture, where we make sure everything’s robust, scalable and deployable, and we create whatever custom software might be necessary.

We do this in a highly agile development routine, in rapid iterative cycles.
We test everything as we go, so there are no failures and surprises at the end.