23rd September 2008

In producing web sites there are a range of pressures and expectations that need to be balanced at every stage.

Our ultimate goal is always to deliver on expectation and ensure that clients are happy with the web site that is being produced for them, even when they are not clear as to what it is they want at the outset.

There are multiple ways to deliver just about any piece of functionality, often with considerable differences in complexity and time taken to build.

The way we tend to deal with this is to spend time at the outset detailing what we are planning to deliver as part of the project proposal which combines scope and cost.

Be honest with yourself how long things take.

We find that this process helps us to be clear about what we are planning to deliver alongside the the cost for each component. It may not seem like rocket science but there are many agencies that will give a cost based upon what they think a client will pay; and then reverse engineer a specification to fit.

Given that the one thing any client will want to do is to pay less for what they perceive as being the same thing, this often leads to either delivery of patchy web software or projects going off the rails when it becomes clear that what is expected cannot be delivered for the budget and/or timescale.

Far better to bite the bullet and specify a project that you are confident will satisfy the client, even if you don't think they can afford it.

And avoid the death march...

Ultimately the budget is theirs and the responsibility to deliver a good quality project is yours.

If the project goes ahead you get to build something you'll be happy with, if not you avoid getting involved in a death march project.

Either way you win!