Forum Moderators: phranque
You get the go ahead to do a large Web project, but the client will more often than not hold up the production process because of the content not available.
And, once you get the content, sometimes - you have to do a lot of leg work to get it into a useable format for Web work.
Any of you have a checksheet or procedure implemented to help speed up the process??
Looking for ideas.
-=bina
This is a constant issue with me as well. One thing that I try to do is always have a single project manager at the client company -- one person whose job is driving the content collection process.
A few years back I worked with a company who asked me to chase each department head for their individual contributions to a site. Foolishly I agreed, and I had to deal personally with 10 procrastinators, people who saw my requests as an intrusion into their daily work and just wanted me to go away.
So I learned that one contact person in the client company MUST assume responsibility. Even then, the delays pile up and usually require me to do some creative scheduling of our team's time. But at least we don't look like the guys making the problem.
Data collection problems are my biggest pet peeve. I would be willing to bet it's one of the top reasons websites are delayed.
My business model generally works that I start charging hosting fees once the site is done. If the client is holding up the process I simply start charging them hosting and they figure they should actually have something up since they are paying for the space.
Also, I tell them that they are moving down my priority list and I am taking on other work and they will now get my left over time.
-=bina
1. Who is the contact person?
2. Who is the content person?
3. Who is the approval person?
If they can't answer all three questions, don't take the project.
I learned this from a producer of corporate videos. Amazing how many of the 'video/movie rules' apply to web projects.