Exploring the possibilities

Have you ever been involved in an experimental project, one where the client wants to explore the possibilities?

These can be dangerous, just because of the word “experimental”.

You can end up out of hours, the client out of budget and unhappy - just because no proper goals, no outcomes were defined.

And then you have an unhappy client blaming you for the failure of something that was too nebulous to get a grip on.

Instead you need to define objectives for the project. What does success look like? What does failure look like? What happens if we get somewhere in-between? And, most importantly, for an experiment how many times do we refine and retry?

Objectives and outcomes are vital if you want your project to be a success. It doesn’t matter if it’s something you can do in your sleep or something that’s brand new to both of you.

Those objectives keep you both on the same page.

Rahoul Baruah

Rahoul Baruah

Rubyist since 1.8.6. Freelancer since 2007, dedicated to building incredible, low-cost, bespoke software for tiny businesses. Also CTO at Collabor8Online.
Leeds, England