The Measures of Success

At the start of your proposal or agreement you are stating the business goals — what the product is expected to achieve. If you want repeat work from the project owner then you’ll need to prove than any previous work has indeed achieved its intended goals. Therefore towards the end of the proposal you should outline what the success measures are, or how you will have determined if goals have been achieved.

As with gathering any feedback, these measures should be specific and carefully considered to measure the explicitly stated goals. Most important of all, they should be measurable! It’s like setting up a scientific experiment — your hypothesis is that the project will be successful so what conditions can you establish to test the hypothesis. This is of course easier if you have specific goals to start off with.

You could gather statistics about the website’s usage based on its functionality, e.g. sales data, contact forms, or user-submitted content, or even by conducting user surveys from the product itself. The most common way to measure a website or app’s success though is through the use of website analytics. There are various tools for doing this, most notably Google Analytics, but all of them require someone to set-up what user behaviour should be tracked and then be able to interpret the data. You should arrange with the project owner who should cover this role, and it may be a chance to up-sell more work in the form of ongoing support.