Lack of clarity
Posted: Sun Feb 02, 2025 6:21 am
Stick to the principle "it is better to see once than to hear a hundred times". The client and the contractor often think about the same things differently.
This is generally the most common situation.
For example, the customer wants the result to be an abstraction (picture below).
As a result, the performer gives the client something similar.
It is very difficult in this case to prove journalist email list whose abstraction is more real. Both are right, and there is no one to blame.
And it is unclear who should pay for the reworking of the project. But if the client had attached an image of the final result to the technical specifications, it would have been possible to avoid a controversial situation.
Describing development stages using quality adjectives
Remember the adjective categories you were taught in school?
If an adjective characterizes a quality that can be expressed more or less strongly, then it is better not to use it in the technical specifications for website development.
Read also!
"Online payment on the website: how to choose a service and set it up"
Read more
For example, the word "beautiful". This adjective can be used to compare objects: more beautiful, scarier. The same with the words "smart", "fashionable", etc.
They cannot be interpreted unambiguously, since each of us has our own idea of fashion and beauty.
It's important to be specific. For example, specify that you want it two shades darker, or that the corners of the button should be sharp, and that the object needs to be shifted by 5 centimeters.
"At the discretion of the developer"
This is a serious mistake many clients make. Never make it by leaving some items of the technical specifications blank.
Download a useful document on the topic:
Checklist: How to Achieve Your Goals in Negotiations with Clients
Naturally, it can be different. If a professional works on the project, then the result will be appropriate. But even if he does everything correctly, there is always a risk that you personally will not like the result.
This is generally the most common situation.
For example, the customer wants the result to be an abstraction (picture below).
As a result, the performer gives the client something similar.
It is very difficult in this case to prove journalist email list whose abstraction is more real. Both are right, and there is no one to blame.
And it is unclear who should pay for the reworking of the project. But if the client had attached an image of the final result to the technical specifications, it would have been possible to avoid a controversial situation.
Describing development stages using quality adjectives
Remember the adjective categories you were taught in school?
If an adjective characterizes a quality that can be expressed more or less strongly, then it is better not to use it in the technical specifications for website development.
Read also!
"Online payment on the website: how to choose a service and set it up"
Read more
For example, the word "beautiful". This adjective can be used to compare objects: more beautiful, scarier. The same with the words "smart", "fashionable", etc.
They cannot be interpreted unambiguously, since each of us has our own idea of fashion and beauty.
It's important to be specific. For example, specify that you want it two shades darker, or that the corners of the button should be sharp, and that the object needs to be shifted by 5 centimeters.
"At the discretion of the developer"
This is a serious mistake many clients make. Never make it by leaving some items of the technical specifications blank.
Download a useful document on the topic:
Checklist: How to Achieve Your Goals in Negotiations with Clients
Naturally, it can be different. If a professional works on the project, then the result will be appropriate. But even if he does everything correctly, there is always a risk that you personally will not like the result.