Since the subject of delivery problems is on my mind. I thought I’d mention that most delivery problems are actually a operating strategy problem.
For instance, at AFH, we often run into people who are completely frustrated with their website developers. Most of the time, it’s because the website developer set some expectation of when the site would be completed, and wasn’t able to deliver. For Instance, they may say they will have the site finished in 6 weeks but the client is required to provide the content for pages of the site. Problem is, that rarely does the client take only 6 weeks to provide all content, proof it, and get it to the developer on time. Next thing they know, their site is 4-6 months into development and still under construction. Web designers, often blame this problem on the client being slow, but really, the developer should head this issue off at the pass. You see, chances are, the client isn’t in a website development situation every day. If so, they’d have no reason to hire a developer. This means that the developer should know the potential problem and find a different way of operating through the process so that nobody is frustrated or waiting on the other.
At AFH, we have pretty good luck heading off this problem in the following way. We promise a site to be finished with design and build in 3-4 weeks. We do this by conducting building the framework, design and functionality of the site and then training the client to be able to type in their own content and load their own pictures or videos. This way, they receive their site on time (early in most cases) and then can take as long or short of a time as needed re-wording and changing their content. Another benefit for the client, is that they will then be trained how to edit the content of their site and not be forced to pay every time they desire to make a change.
Can a change in operating strategy prevent your delivery problems?
