Forum Moderators: not2easy
My practice is to ask them to provide draft content. I then act as the editor.
It's an interactive process - you'll have to get an idea of what is (or could be) available, think about the site architecture, and figure out what you need. The client should draft the content in most cases, but if you are a marketing pro you should organize, edit, and create as needed to make the site work.
Now I believe that was a mistake, at least when the customer is so slow about coming up w/ anything.
One thing we do in any proposal is have a "Provided by Client"
section - that makes it clear what we expect, and gives us
documentation if the project scope changes due to the client's
failure to provide something in a timely manner.
May I steal that idea? :)
I've lost web sites before because the customer didn't provide content, or never got around to approving the web site.
I had one that started with me. Then, their employee who was handling getting the content to me quit. Never got any more content, and the next thing I heard was when they were announcing at a meeting who was doing their web site, and it wasn't me!
If there is a bright side to it, it's that that was a couple years ago, and they still don't have a web site.
Gee, ya think maybe the new guy wasn't given any content either? ;)
May I steal that idea?
By all means use it, ccDan, WebmasterWorld has sharing knowledge at its core.
Accountants often talk about "shoebox jobs" - that's where a client comes in with a shoebox full of receipts and papers and says, "do my taxes".
We've seen our share of shoebox jobs in the website biz, and sometimes there's almost nothing in the shoebox. Set your client expectations early and things will go far more smoothly. :)
So, I came up with a list of topics for them and together we organized and categorized them. The exercise of working together caused them to mentally get on board with the project and gave me a good feel for the inner workings of the station. This way, we could effectively create content that was relevant for who they are and who they are trying to reach. This also helped me later when I took over writing the content for their site because we had been working on it together from the beginning. All the guesswork was gone.
Think about what you would want out of the website if you were a customer and design it with that mentality. After it's finished, open up for business. Customers will give you feedback, request information/features that aren't there, and offer opinions on what could be done differently to make it more efficient/easier to read/more relevant to their needs, etc.
Asking customers to proof your site in my opinion is not only unprofessional, but tells the customer you have no idea what you're doing and need their help. It's your business, you're supposed to be the expert, not them :)
You need not ask for customer opinions - you'll get it whether you want it or not. A simple "comments" area will do a good job of asking for feedback without really asking for it.