When I work on any online project, I always try and apply the same process to it, whatever the size of the undertaking. This process is based largely on one I used at Yahoo! In my experience, the trick to being able to use this successfully is to apply it in such a way that you don’t get bogged down or overwhelmed by process. For example, in some projects one of the stages detailed below could be a conversation, in another, it might be a 50 page document.

Stages of the Process

In most instances, we’d expect prospective clients to come to us with 1 and 2 below:-

1 Ideate

What’s the core creative idea for the site?

2 Define Market Requirements

What are the requirements of the website? (in essence this is similar to what is covered in the miggle.co.uk client briefing form) What’s the market? Who are the competitors? On what criteria will the website be judged a success? What do budgets and timescales look like?

You can find more information on writing your brief here.

Stage 3 and 4 depends on the size of the project. If it’s a straightforward build in a content management system (CMS) and we’ve got a clear idea of content and hierarchy then often 3 and 4 is no more than us knowing the CMS tools comprehensively and squaring off that your requirements are met by the functionalities of the tools.

However, in larger, or bespoke projects, 3 and 4 can each also be extensive pieces of documentation. In my opinion the client should aim to be leading on as much of point 3 as possible – or calling in experts to help.

Point 4 is then the role of the company you choose to do your work. The bit in-between is the process you go through to select your supplier.

3 Define Product Requirements

Scope the product features that deliver on the concept and the market requirements.

4 Define Functional Specification

Detail how the product will work, detailing how and by what technologies the project would be delivered.

5-8 will be lead by your development team – with appropriate sign-off for clients happening during 5-7

5 Define Development Plan

Build this into a plan, which includes full costs and timescales.

6 Build

Execute on the plan.

7 Test

Test the solution.

8 Deploy

Deploy solution on production servers.

Finally, as the client, you need to work out if the project achieved on its objectives. So, there’s often going to be either between stages 8-9, or after stage 9, the plan by which you market your new development.

9 Evaluate

Measure the site’s performance against the criteria laid out in market requirements and get ready to ideate again.

How similar/dissimilar is this to processes you might use. I’d be interested to find out. Also, if you were looking at this from a client perspective, what do you think are the relative strengths and weaknesses of the process – and what would you change? I’d be interested to hear.

Based in Brighton and Hove, East Sussex, contact miggle.co.uk for website development, content management and online media services in the UK and worldwide.