| Questions to ask your client before building their | | | | needs to be discussed since there may be SEO and |
| website. | | | | cost implications. |
| This article is most relevant to people who develop | | | | Another important subject is the intended audience of |
| standard websites (e.g. a business' web presence). If | | | | the website. Questions you could ask include; who is |
| your main focus is web-based applications, this paper | | | | your intended audience? what's their typical |
| may have limited appeal. | | | | occupation?, what is their age range?, is it mostly male |
| Client input is the foundation upon which successful | | | | or female?, how often do they use the Internet? |
| web sites are built. It's absolutely vital that you get your | | | | You can ask the client to show you some websites |
| client to articulate their goals in order for you to | | | | they like and have them explain what it is about each |
| successfully deliver their project . To help facilitate this | | | | site that appeals to them (e.g. client: "I like the clean |
| process, a number of questions can be asked relating | | | | layout of the site", "the animated banner is really cool", |
| to areas such as target audience, desired look and | | | | etc). If you know that your client likes a particular style |
| feel, and what interactive functionality is required. | | | | of navigation, it makes sense to use that style for their |
| A good way to tease out your client's requirements is | | | | website. |
| to use a Needs Analysis document. This is basically a | | | | Notice that none of these questions have to do with |
| 2-3 page fill in form, full of questions which prompt the | | | | layout or color schemes (e.g. where the navigation |
| client to think about not just the visual elements of their | | | | should be, what font should be use, etc). These |
| site, but what they are trying to achieve in concrete | | | | considerations should be left to the graphic designer, |
| business terms. | | | | after-all, they are the expert. |
| Using a Needs Analysis form provides many benefits. | | | | Business Related - these questions aren't directly |
| It often acts as the basis for developing a fee | | | | connected to the visual appearance or functionality of |
| proposal or tender. Unless you know what it is your | | | | the website, but they may have an impact on the |
| client wants, you wont be able to cost it with any | | | | project itself. For instance, you would want to ask |
| degree of accuracy. Another advantage of a Needs | | | | questions like: is your content ready?, how are you |
| Analysis form is it can present ideas to the client which | | | | planning to market your website once it launches?, are |
| they hadn't previously thought of. This isn't just a boon | | | | you open to developing in stages to manage costs?, |
| in terms of up-selling, it also means features aren't | | | | do you require an SEO strategy?, are there time |
| added mid-way or at the end of a project (e.g. client: "I | | | | constraints (e.g. client: "we need it ready before we go |
| know you've finished my website, but can you just | | | | to a trade show in November", or "we are printing a |
| quickly add a photo gallery page?"). | | | | brochure next month and want to refer to the |
| The Needs Analysis form I use is broken up into five | | | | website")? |
| sections; Company Details, Graphic Design, Business | | | | You may wish to ask a few questions about the |
| Related, Technical Requirements, and Programmed | | | | client's competitors, such as; do your competitors have |
| Features. I will cover some of the questions contained | | | | websites? what do you like about your competitor's |
| in each section along with the over-all structure of the | | | | websites?, what do you dislike about your competitor's |
| form. | | | | website? Sometimes finding out what someone |
| I always start documents with a short description of | | | | doesn't like can be a great help in determining what |
| what the document is. This is for the benefit of anyone | | | | they do want. |
| seeing it for the first time (e.g. Document Purpose: this | | | | Probably the most significant of the business related |
| form is used to gather client requirements...). | | | | questions is about content. Lack of content can be a |
| Company Details - this section is pretty | | | | real killer. A wonderful website may be developed, but |
| straight-forward, you record information such as the | | | | if the content isn't ready, the site is effectively in limbo. |
| company name, who the main contact is, address, | | | | One way to help reduce the risk of this happening is to |
| phone numbers, the client's position within the | | | | recommend early on that the client engage a content |
| organisation, etc. It's also a good idea to note down | | | | publisher. |
| any other stake-holders that will be involved in the | | | | Technical Requirements - these questions are mostly |
| project, and if the primary contact is able to give | | | | system administration related. For instance; you want |
| approval for the work to begin. | | | | to find out if the client already has a hosting provider |
| The information gathered in the Company Details | | | | organised. You also need to know if the client has |
| section will most likely be needed for producing a | | | | registered their domain name or if they want you to |
| quote. It will be especially useful if a sales consultant or | | | | register additional web addresses on their behalf. |
| business development manager is gathering | | | | Programmed Features - this section covers the |
| requirements to hand over to a project manager. From | | | | interactive elements of the website. Probably the most |
| this, the project manager will be able to figure out | | | | important goal of this section is to establish the |
| who's who on a project. | | | | information architecture of the site. This can be done |
| Graphic Design - this section is meant to capture | | | | by asking the client what sections their website should |
| details relating to the website's visual appearance. It is | | | | have (e.g. press releases, our work, testimonials, etc). |
| not so much concerned with layout and colour, but | | | | The client may also have a need for interactive pages |
| rather communication. The information gathered in this | | | | which require custom coding (e.g. sign-up form, news |
| section will be most useful to a graphic designer. Good | | | | articles, member's login, photo gallery, etc). |
| questions to ask the client include; 'what image are you | | | | Other significant questions would include; are you |
| trying to portray?' (e.g. friendly, corporate, innovative, | | | | planning to sell anything online?, do you require a CMS?, |
| etc), 'what phrase would best describe your website | | | | does your site need to work with an existing |
| once it's launched?' (e.g. 'these guys look really | | | | database? |
| professional'), 'what's the main goal of your website?' | | | | You'll generally find that only about 80% of the form's |
| (e.g. sell products online), 'what else are you trying to | | | | questions are relevant to any particular project. That |
| achieve with your website?' (e.g. promote skin cancer | | | | being the case, it makes sense to remove or |
| awareness amongst young people), 'what would you | | | | cross-out irrelevant questions before meeting with |
| like users to do at your website?' (e.g. register, buy | | | | your client (e.g. you would probably know before-hand |
| products, etc). | | | | if any e-commerce facilities are needed). |
| You also want to ask if the client's logo and branding | | | | Another idea is to pre-fill as much of the form as |
| material is ready. Your graphic designer will want to | | | | possible. Besides the obvious benefit of saving time in |
| get his hands on any digital files as soon as possible | | | | the face-to-face meeting, it demonstrates you've paid |
| (e.g. logos, product photographs, etc). Connected to | | | | attention to verbal requirements which may have |
| this, you may want to ask the client if they have a | | | | already been discussed. |
| style guide. The topic of Flash vs. static HTML also | | | | |