Are you paying him based on the project or by the hour?
It gets really frustrating when you initially think that a project will take x hours, but because the client doesn't have a clear idea of what they want, it ends up taking 3x hours.
It can be especially frustrating when the client has a little experience in your field, but thinks that they are an expert. When this happens, then you begin to think "if you are such an expert, then why don't you do it yourself?"
If you actually know what you want, then you should create what is called a requirements document. It out lines exactly how things should look like, what they should do, and what they intereact with. If you don't know exactly what you want, then you should have him write one. If you don't agree with a part of what he writes, have him explain why he chose to do it his way, rather than how you propose.
Once you have the requirements document down, then all he has to do is go through it. Remember that you sought him, so you should respect his advice. If not, then you should get rid of him and get someone else.
|