You can follow the advice in the first six points to the letter and still have a project that fails. Probably the second most common reason I’ve seen projects fail is because the client fails to live up to their commitments. No I’m not talking about hitting your payment milestones, I’m talking about delivering your content. Your developer can only go so far on their own, at some point in the project you are going to have to deliver some content to go into the application. Your developer should have made sure that you have milestones in the project just as they do, don’t ignore these. Your participation and dedication to these milestones is every bit as important as your developers. If you reach a milestone in which you are supposed to deliver a document (say, the history of the company) and you miss that, then they can’t continue to work on that portion of the application until you do. Don’t be surprised if the schedule slips because of your non-participation.
This is your application that they are building, you have money on the line. Don’t be the reason that it misses its delivery date. Also, don’t expect your developer to work extra hours to get the project back on schedule just because you failed to meet your obligations. As soon as that milestone goes by, expect all other milestones to move and the final delivery date to move the same number of days you are late. As the old saying goes:
Failure to plan on your part does NOT constitute an emergency on my part.
When you are ready, move on to part 8 of 8 and read “How to Plan a Website – Own it.“
Want more helpful advice?
Are you looking for more helpful advice? Check out our book, Avoiding a Goat Rodeo. It was written to help non-programmers understand website development. It shows you how to get the website you want.