PointConcept

I was recently helping a client who has an issue with their web developer. As usual a big chunk of the issue was caused by poor communication, which in turn was caused by shortage of time.  But this problem cuts both ways. The client did not take the time to fully think out what they wanted and get help to define this and the developer did not take time to fully understand what was needed and what was expected. This was compounded by no ongoing dialogue, no project tool and no updates supplied to the client or asked for. Then suddenly the deadline was close and the site was only partly done and did not look as the client expected. Now both parties have a problem. For the developer, they may loose the commission and receive bad press, or go over their budget fixing things. For the customer, the whole project has created stress and they are now faced with paying a second time to get what they wanted done.

All of this could be avoided by actually setting aside some time to sit down and get some agreement on expectations. This works for any project: draw up the process; explore the issues; draw some wireframes and create some lists. Set some milestones. But most importantly get to understand each other and what you need to provide. This is all basic stuff really and there are books galore written about it, but nearly always from the perceptive of the project manager. The trouble here is that small business owners are so busy project managing their business and don’t or wont take on the new project. They expect the developer/ supplier to do that. Only often they are a small business too and concentrated on doing what they do. They also have their way of doing it and often “know” best.

If both side have a check list before they sit down they can then easily see on which parts they agree, and then on which parts they need to spend time discussing. And that is were you need to spend your time, because these are the points which will eventually cause a falling out.

So if you are hiring, either get someone to help scope the project and spend time putting it together for you, or spend that time yourself and find examples and ask questions.

If you are the prospective developer, remember your client may not understand what you do and take time to explain it to them. Have a method and check list to reach an agreement. Then provide  a fairly detailed scope. Get this signed off and then ensure you spend 20 minutes a week updating the client. It will save you time in the long run.

I really am not saying anything new here, but it needs to be said again and again. It’s been talked about by plenty of people and will continue to be. In fact while I was writing this someone else was posting this check list for a Drupal Design Brief. I suggest you grab it and keep it, then use it both as a supplier and as a client.