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.

We’ll often get calls from businesses looking for quotes for a website. While they’ll have a good idea of what they want, to define a price and timescale, the devil is always in the detail. That’s why we’ll always ask for a brief. However, often the response we’ll get is, “We don’t have one” or “We don’t know where to start in writing one” – so if that sounds like you, maybe this post will be of some use.

Focus on your objectives

A good web design company will just want to know about your business objectives. From this, they can recommend solutions.

Our briefing form, which is based on one used by Clearleft, with a few other objective based questions thrown in, is all about trying to find out about your requirements, as well as who your audience and customers are, who you compete with and what kind of image you want to create online. Beyond the actual brief, we’re also aiming here for you to tell us all about your business. You know your company best, so that should be an easy thing to do shouldn’t it? Aim to talk to us in your language, not ours, and let us come back to you for points of clarity if we don’t understand some of your objectives.

And really, that’s it…

Is it? Yes, pretty much.

However… listing your objectives alone won’t get your website built. There may be other important stages that need to be covered too – such as user research for example. In any case, your site will only get built once you’ve agreed that the solutions proposed back to you in the web company’s response make sense and deliver on your objectives.

That can be a difficult thing to ascertain, because it may not be obvious to you initially, as the client, how the solution that’s been proposed delivers on your business needs. But the extent to how well your prospective development partner assists you with that stage will be one of the key criteria you use in trusting whether or not they are the company to work with. Then, beyond that, even with the solutions agreed, depending on the scope of the site, more detailed work may need to be done on specifying exactly how your site is built.

So the brief is just the first stage then?

Yes, it is. And its worth is weight in gold.

A good brief is a uniform document you can take to a number of potential providers, meaning the proposals you get back will be something you can compare like for like. Many companies will give you that initial response for free. However, if more detailed planning needs to be done to specify exactly what the solution might look like, then it may be that this in itself becomes a chargeable stage of the project. It really depends on the size of the project overall, but a good prospective provider will always let you know to what extent the planning you’ve done in the brief gives them the info they need. You can read more on planning your web design project here too.

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.