Defining the Problem is Half the Battle

Over the last few years after seeing hundreds of projects come through my company – if I have learned one thing – it is that defining the problem is half the battle.

So many times people will send over “documentation” which can sometimes be in the form of a mockup, an email, or a full blown specifications document. Most of the time the most difficult part of the project is extracting exactly what the client is looking for and not how to properly implement it. The client might even write one thing and actually mean something else so I always make sure to have the client clearly define what it is that they want. If they cannot clearly define something – how can you define the project or even the project’s success?

All I can recommend is that before getting into a project – make sure the client can clearly (in writing) state what they want as well as how to test it (you may need to help them a little). By having both the client define what it is that they want and how we can test it (to meet the end goal) – you can then reference the what and show them the how – using their own words thus showing them they got exactly what they originally wanted.

Above all…documentation is king.

About the Author...

Jennifer Zelazny

My name is Jennifer Zelazny and this site is a collection of my random thoughts and opinions. I am Penn Stater, WordPress developer, and a modern day explorer. I love exploring data, trends, and things that make the world a better place and sharing them here.

Leave a Reply

Your email address will not be published.
You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>
*
*