Reply to Re: explaining web standards to clients

Your name:

Reply:


Posted by Tony Cooper on 10/19/05 17:25

On 19 Oct 2005 06:41:51 -0700, "Travis Newbury"
<TravisNewbury@hotmail.com> wrote:

>Tony Cooper wrote:
>> The problem the average purchaser has is that the average provider of
>> the product or service insists on going on at length about the
>> technical way that this is done or that is done. We - the average
>> purchasers - don't give a rat's ass how you get the windmill on the
>> page. We just want it there.
>
>But do you want to know if someone is going to have problems seeing it?
> Or do you just want them to make it reguardless of who (or how many)
>of your customers can't see it.

In the example used, yes I want a windmill there. From a practical
standpoint, as a person selling a service, you won't get very far
telling your clients that a windmill can't be done in a way that all
viewers will see in its full glory. You might offer to do a page
with a revolving purple windmill and wind noises in the background
over here, and a static windmill graphic over there for the people who
don't have system that displays revolving purple windmills.

The important thing, in my view, is that you don't drone on about the
reason that some viewers won't be able to see the blades turn. Just
give the client a simple alternate that presents what he wants and
also does what you know is right.

>I personally, would want the developer to explain to me why my windmill
>may not work for everyone. THEN (and only then) can I as the decision
>maker make a intelegent desision about the windmill.

I had the impression that you design/develop websites for clients.
Yet, you refer to intelligent decisions. Most products are not
purchased based on intelligent decisions. Watch television ads, look
at magazine ads, or look at websites. What intelligent seller is
appealing to the intelligence of the buyer? Ninety-some percent of
what you purchase will be the result of an emotional buying decision.
The windmill sold you.


>> People selling products - from computers to programming to website
>> development - seem to feel that it is important to impress the client
>> by using every technical term in the books....
>
>There is a HUGE difference between telling you some fancy key words,
>and telling you FACT about why your design may be flawed. Without this
>information YOU can not make an intellegent decision. Even WITH this
>information you may still make a bad decision. But at least you were
>informed.

Nah. The client wants his idea implemented. You just have to figure
out how to implement his idea in a way that works. If the client
wants a garden gnome on his page that jumps off the screen and spits
in the viewer's face, you don't tell the client the facts of why this
can't be done. You tell the client you can come up with a page that
gives the viewer the impression that the gnome is spitting in the
viewer's face.

Telling the client too many facts will probably result in the client
turning to the Yellow Pages for a different source. If you are in the
habit of telling clients that their design idea is flawed, you should
have a backup plan for putting groceries on the table. Better you
should tell the client that his plan is a good start, and that you'll
work on a concept that will incorporate his design in a format that
will work.




--


Tony Cooper
Orlando, FL

[Back to original message]


Удаленная работа для программистов  •  Как заработать на Google AdSense  •  England, UK  •  статьи на английском  •  PHP MySQL CMS Apache Oscommerce  •  Online Business Knowledge Base  •  DVD MP3 AVI MP4 players codecs conversion help
Home  •  Search  •  Site Map  •  Set as Homepage  •  Add to Favourites

Copyright © 2005-2006 Powered by Custom PHP Programming

Сайт изготовлен в Студии Валентина Петручека
изготовление и поддержка веб-сайтов, разработка программного обеспечения, поисковая оптимизация