Plan a Website Project

Contents > Plan >

PLANNING A WEBSITE

PROJECT OBJECTIVES

Objectives of client

Sometimes it takes much discussion before the client can reflect on what is specifically required. It helps if the results of these deliberations are recorded. The following may be involved:

• What is the aim of the website? Are there measureable objectives? Will the website result in a major change in the way the enterprise conducts its business? How can we do better than our competitors? How can it be used to improve our image and branding?
• Budget available? New costs to the business will arise.
• Timing? What is a reasonable estimate of how long it will take? Are there timing imperatives? Agree deadline and milestone dates and feedback about the development process.
• Sustainability? Site maintenance must be planned in terms of timing, personnel and training. What are the life expectancies of the software technologies? How long before a complete revision may be required? How to avoid getting locked into proprietary solutions?
• Does it 'live the image'? The website is a representation of the company on the Web, so it should incorporate the values of the company in its makeup.

Objectives of provider

The provider clearly seeks to satisfy the client's objectives, but has further concerns which must be satisfied for the project to be an overall success.

• Consistent client objectives which are clear and mutually attainable. This may require a degree of client education about how objectives may clash. When objectives are changed then the impact must be explained.
• Make a profit. This must be of the order of competitors' yet provide a value-for-money site.
• Enhance the reputation. The site must conform to good practice and use up-to-date techniques.

ASSESS

Strategic decisions need to be taken at a high level involving the client looking at the present marketing and deciding what is to be retained and what needs to be changed.

• - what are the overall aims of the business? Where can the website make a contribution?
• - what branding with legacy colour schemes, logo etc MUST be incorporated?
• - what should be the extent of the website? It could range from a few pages advertising products (a presence on the web), to a completely new way to sell goods on the Internet.

CONSTRUCT A TIMETABLE

Be realistic

It will take longer than the initial estimate! Recognise that this is a very time consuming activity. Allocate sufficient time for the process and allow a generous amount of time for the design phase, where well thought through decisions will show and be appreciated by users.

Set milestones

Target dates for the phases can be estimated and these act as indicators for timely delivery.
Educates the client, and helps them to realise that it is not just a coding exercise.

CLIENT

At a lower level, decisions must be made to establish:

• are there are any knock-on effects for staffing?
• who is to maintain the site? will training be required? A static website is unattractive, so a systematic dataflow must be established with regular updates, maintenance and checks.
• how to incorporate the website as part of the branding? - use the URL and e-mail throughout the enterprise on letterheads, stationery, adverts, transport livery, etc.

CUSTOMERS

Initially, certain assumptions are made, but patterns of usage will indicate where changes can be made. The aims must be to:

• meet user needs (can information be accessed quickly and easily? is it easy to place an order? if there are queries - who can provide an answer?)
• enhance user experience (to encourage them to return to the site and to get a positive impression of the enterprise)

Requirements (content)

Website content is one of the first inputs. Development should concentrate on the areas of most interest to the customer.

Usability (navigation)

Navigation must be made as user-friendly as possible. Actual usage may point to improvements, as users rarely use the site in the way envisaged by the designer.

Profile

The customer and client profiles must be defined, as these will affect the overall design, especially in terms of colours and 'voice'. As time elapses, changes in customer base or product range may dictate a change of design to suit the new circumstances.

HOSTING

An ISP must be approached and hosting facilities set-up to include:

• the availability of suitable software - do you need SSIs? cgi-bin? shopping trolley?
• space and bandwidth restrictions
• a number of e-mail accounts
• archiving policies particularly in regard to system logs, and reporting software for feedback on usage
• good server availability statistics
• set-up costs of domain name?

RESOURCES

There are many resource issues to consider including the availability of :

• development hardware & software. Diligent searching (see resources page) can unearth some excellent, free software tools.
• personnel number (often wildly underestimated) and skills required (artistic appreciation, creativity, communication skills, good command of the language, coding ability, knowledge of software packages).
• funding constraints and opportunities.

ACCEPTABILITY

How will the final product (website) be rated against the requirements?
Factors involved in the evaluation of a website.