Service - The Different Tutorials - Part 1: Converting a Client's Thoughts

The Different Tutorials - Part 1: Converting a Client's Thoughts

or how to analyse, plan and project.

I am often asked for support on different problems appearing in

projects people work on.

As I am a very curious person I always ask how this problem came

up and why. And for sure the answer is: "Because my client asked

for, but the system I use doesn't have the feature to do so".

Well, for sure that's right, but as I ask if this wasn't clear from the

beginning that this feature should be implemented I very often get

told: "Yes, but I thought ...."

And that's the point I really start thinking .. Did you ever think about

what you do or did you plan this project properly???

And the answer is NO for multiple reasons. So let's take a closer look on how to analyse, plan

and project a client's solution and what's important to do for successfull development.

Do you understand your Client?

First of all it's most important to understand, that your client is not a programmer, developer or

CMS specialist. If he would be, he would do the job by himself. So listen to your client's ideas

and explanations carefully and in a way you don't expect him to describe everything the way

you'd expect it from a professional. He will tell you his needs in a simple and very often "wrong"

way.

Let's make a small example.

You client tells you: "I want to have two versions of the website. One for selling clothes and one

for selling shoes".

Now it's your job to analyse if he really wants to have two separated websites (we assume he

does not) or if he just wants to change the style of the site to change according to the part o the

website where clothes or shoes are sold, which will just end up in the use of two different

templates or css styles.

Well, this is a very basic example, but you can imagine where this might end up if added some

more complexity.

Need an example? Well .. here we go:

"I need a facebook botton." you are told.

OK so far. But... what exactly is meant and wanted? Does your client want a global facebook

"share" button to share the website with the main URL? Or does he want a "like-it" button for

his facebook fan page?  Or, assumed it's our clothes and shoes seller, does he want to share

each product with individual "share" buttons for each product and do you want to insert any

of those buttons manually?

Got the idea behind what means to understand your client? It's important!

Do you have a concept?

As you now have a clue on what your client really wants you might develop the first ideas and

concepts.

But ... stop! We have the demand to be professional which means to analyse if things are

possible the way mentioned and discussed and to develop a solid product and solution.

This is where your plan comes up. So first write down and merge everything you discussed with

your client and sketch your first ideas each point on how you want to realize it.

This is your conceptual plan for the project. It ensures you don't forget anything later or run into

difficulties and builds the basis for the development process.

But this comes later ... and yes, professional development also means a lot of paper work.

For each point you don't know how to solve it or you are not sure on some details, start your

evaluation now. Note any dubiety and classify and sort code, components or extensions you

might want to use and review the possibilities on your doubts and requirements.

This gives you a good overview on what to use and how to connect everything to work seamless

integrated.

Based on this facts you now have collected and cleared you are able to write your final concept.

How about a Project?

For sure you want to tell your client now how much everything will cost and how long it will take

to be finished. So it's time to start to project everything.

You have collected all you need with your concept, so start with a timeline for your project.

For each phase your timeline has calculate three times of the time amount you might have in

mind.

As a small example:

You think the screen design will take two or three days. Plan  nine or ten days. It's a fact

everywhere additional effort will appear as new ideas or wishes will come up. So try to stay

on the safe side.

Also clear and note the responsibilities if you work with different people on that project.

Who does what and does he agree with the durations you set and what does this cost you

as well as what do you want to earn with this particular work.

Finished? Now you can calculate the project on time and money and create the offer.

Congratulations this is the first step taken on professional development.