• consulting
• profiling
• architecture
• design
• build
• testing
• launch

It is our experience that once a specification document is written at the outset of a project it does not see the light of day until acceptance testing, by which time it is too late to properly rectify any errors or omissions. A specification should be a live document subject to change as better ideas will undoubtedly emerge through the design and development process. As such, website specifications developed by >large are accompanied by a series of easily-referenced-schematics consisting of the sitemap, wireframes and flow diagrams of key functionality. Furthermore, it is at this point that we determine the success criteria that will accurately measure ‘Return On Investment’ post-launch.

The Large specification process is progressive, building on the audience profiles, which in turn build on a thorough brand understanding. The entire process is rigorous, logical and builds on previous steps, minimising delays and facilitating a transparent and logical sign-off process. The result is projects running on time without any misunderstandings and a website that informs, motivates and leaves a lasting positive impression on its audience.

Only once we have a thorough understanding of the brand and audience can we specify a site structure and associated set of templates, wizards and other tools that will result in an engaging and compelling website for customers. 

Sitemap
From the sitemap we identify the templates we need to create, the content we will need to populate them and the user journeys that are likely to result.




Wireframes
Wireframes specify how information is managed on a page and form a visual check list for template development, ensuring consistency and decisions based on objective facts and research rather than the emotion and politics – we can leave these for the design phase! Furthermore, as they are visual, they are unambiguous to designers, developers and strategists on both the agency and client side.




User Journeys
Once the templates have been defined we tie them back to the personas created during the audience profiling stage to create a series of user journeys. These user journeys can be assessed by a neutral third-party or used post-launch to see if anticipated behaviour matches actual behaviour.