As I’m a Designer, it’s normally expected that I’d want to get straight into actually working on the visuals for any project, but as it turns out I’m the main advocate of creating a detailed Features Specification for the current project I’m working on.

It’s really important before a project goes ahead to know it’s full scope for a variety of reasons.

1. To make it clear to all involved in the project what the purpose and functionality is of each page, and the site as a whole. This clarity ensures that at the start of the project everyone knows what we are aiming to acheive. It documents our intentions and ensures we are going to create something that properly fits into the clients requirements and expectations.

2. To make the design more cohesive by defining components. When designing numerous pages there can end up being many different elements. Just a bit of thought into grouping these elements as similar components can make it easier on design and build.

3. To accurately plan and cost the project. If we are all aware at the beginning of a project of what the level of work will be required, especially in development, then the cost will be more accurate and the planning will be much easier.

4. To make it easier to actually design. If there is a clear set of content and functionality for each page, then when it comes to designing the site, there will be more time to concentrate on the look and feel, rather than what is actually going on each page.

Tags: design, process