For the last week or two, I happened to see several questionnaires that torture their clients with all sorts of different studios before creating simple sample sites. This made me extremely upset and encouraged me to propose a much more efficient and customer-oriented approach to setting the task and writing the TOR for simple websites with
limited time and budget.I remember, by the way, that in the comments to the articles on design I was asked such questions as “What to do when there is no time and money for design?”. The answer is below.
Just in case, I’ll clarify that I have no reason to call simple sites
template . Of course, I don’t have exact figures, but I’m pretty sure that 90% of simple sites on the Runet are built on the basis of designers and ready-made templates with repainting and pasting the client’s logo. And those who do not use ready-made design templates take ready-made templates from their heads: news on the right, top image image and menu, text in the center. Because time and budget do not allow to make a site for a specific client.
As usual, the task is set in Russian studios.
The most common are two options:
- Ask the client to write the TK,
- Ask the customer to complete a standard questionnaire.
As for the first point, I have already spoken in the article
“How to evaluate the task before starting the development of the site” and I will not repeat. This is just nonsense.
')
As for the second point, I will speak in some detail, because the questionnaires are used in very respected large studios, which fills my heart with sadness.
Questionnaires are evil
The first problem of the questionnaire lies in its nature: it requires you
to choose from the proposed answers . Given the qualifications of the compilers of questionnaires, the proposed options often do not allow you to choose the right option or simply do not understand the client. For example, here are the answers to the question “Choose a type of design”:
- presentation promotional site (not enough text, a lot of graphics),
- information representation (a lot of graphics and information, information in a very short form, but approximately 50% of the total content of the main page),
- informational (little graphics, a lot of text, information in detail).
Is that what? How can you choose something from this, and why should the client do it? Isn’t he hired a developer to make the right decisions, including those concerning design?
Or it is proposed to tick this requirement: "The website should be presented with a simple and easy navigation through the pages." What should the client answer? "Not! Just not convenient site navigation, I beg you! ”
And what should the client choose in response to the question “Choose browsers”? I, please, Mozilla and IE, but Opera and Chrome, probably, is not necessary. So should the customer respond?
The second problem is that the questionnaires are immediately aimed at determining the site specification and requirements, and
not on clarifying the client’s business objectives . The proposed answers actually constitute the task on the site, which
removes the responsibility for the result
from the developer . Say, you yourself, dear customer, so answered. What do you want from us now?
I will give some examples of such questions:
- Do you need a screensaver: Yes / No?
- Select a design pattern: Two columns / Three columns.
- Where the information field should be located: Left / Center / Right / Pop up.
- Determine the structure of the main page - this is an open question with no answers.
By the way, all these questions are taken by me from real questionnaires. I was killed on the spot number 3, where there is an answer “Pop up”. A curtain.
The third problem of the questionnaire is that it is often in its pure form, as the client has filled it, without any processing by a specialist, subscribes and starts up. That is, the developer not only disclaims responsibility, but also
forces the client to do not his work . Both the client and you yourself will suffer.
How we recommend setting a task
Conduct a personal interview
We believe that it is best to conduct a personal interview with the client, about the benefits of which I have already spoken in the above-mentioned article on setting the task. Let me remind you the key points:
- The interview demonstrates your reverent attitude to the client : you are ready to listen to him, and not to get back with the questionnaire; you are ready for personal contact; the client is an individuality for you, questionnaires are not applicable to him. This is true. And if you think that this is not the case, then you have no place in this business.
- The interview allows you to get much more useful information due to the fact that you can clarify them or ask additional questions, and also receive information not only in text, but also paraverbally - see the article “Three Frequent Errors in Communication with a Client” .
- The client can tell you about something unexpected that you would not even have thought to ask.
- An interview allows you to get first-hand information . Questioning does not give such a guarantee, because the questionnaire can be commissioned to fill in the secretary, who does not understand the belmes in this.
I foresee a question about how to conduct an interview if there is no access to the client’s body. For this there is Skype and cheap IP-telephony.
Interview plan
What, in fact, you need to ask. We propose to consider an interview plan for the most common type of site - corporate representation. Tasks of this interview:
- Clearly state what tasks the site should solve.
- Learn more about the client.
- Understand what information should be on the site: in what form and volume it should / can be presented.
- Understand how we will personalize * the site - adjust it to the client.
* I’ll clarify that by personalization I understand all the actions that the developer performs, so that the website from the designer and the set of templates is uniquely identified with the client - that is, not only the functionality change, but also the work with the style and content.
What you need to know | Questions |
---|
What tasks the site should solve | Let's define why you need a website, what tasks it should solve. |
About client / business |
Customer information | 1. Tell us about what you / your company is doing: what services or products you offer. |
2. Tell about your clients: about her needs, behavioral peculiarities, how they rate you. |
3. How do you sell your services / products to your customers? Describe the sales process: what you focus on, what are your advantages over competitors. |
4. Who are your competitors? |
About the site |
What information should be on the site; in what form and volume it should / can be represented | 1. What information - about you, your products / services - in your opinion should be on the site? (just information, not structure!). |
2. How and in what detail will we describe the goods / services? Provide examples describing your products / services. |
3. What do you have of this, and what will you need to create? Can you provide us with sample content? |
Refine personalization character | 1. Do you have a corporate identity? |
2. If not, what are the wishes for registration? |
3. Show examples of sites that you like. |
So, the main
task of such an interview is to find out the client’s tasks, understand his business and, as a result, suggest the best way to present information about him on the site for his target audience.
Make a technical assignment
The terms of reference based on this interview should contain the following information:
- Site tasks
- Business Description
- Description of CA,
- Competitor information
- Site style requirements
- Site content requirements
- Site Specification.
For convenience, we post
an example of a real Technical Specification (PDF, 170 KB), filled in according to this template.
You make the first 6 points of the list on the basis of an interview with a client and let him approve this document. After he approves these points, you proceed to the creation of a site specification - a detailed description of the functions and structure:
- Feature list;
- Information structure of the site, the composition of the main menu;
- What information is in each section / page and how it is presented;
- The presence and composition of contextual blocks on different pages.
This specification must be approved once again with the client and you can begin to create the site.
Summary
Never ask a client to fill out a questionnaire and, even more so, to draw up TK independently. This is a felony.
Independently determine the needs and tasks of the client, design the structure of the site - functional and informational. You are a professional developer. You must take responsibility for the result, and not transfer it to the client.