The first phase is about information gathering, getting to know the client and research work. We conduct an interface audit too if it’s a redesign. The goal of this phase is to gain a better understanding of the client’s business, competitors and main goals of the project.
In this phase, we establish a set of design principles to follow and start working more closely on the overall concept, user stories and information architecture. We also review interface audit’s results with the client and plan the next steps.
Rather than jumping straight into high-fidelity designs, we start all projects with lo-fi sketches. By spending short periods of time sketching early on, we save ourself hours on the computer later. Sketching ideas down happens throughout the process.
Moving quicker to code helps us to put content over form, embrace the fluid nature of the web and focus on systems of components instead of pages. It also helps us to find user experience issues that previously only became visible once the implementation started.
This phase describes the feelings we get that are evoked by color, texture and typography. We do this in iterations before, after and during prototyping. Instead of designing static page comps, we try to work in a more modular manner and break our designs into smaller chunks.
Testing on actual devices and reviewing progress early will save us from having bigger problems later on. The goal is to encourage conversation and collaboration not only by designers, but by developers and shareholders as well.