A Mistake Not Worth Repeating For The New Freelancer
By Johnny Spence
Many new freelancers who start out in their first projects have the unfortunate tendency to go in over their heads. I know for sure since it happened to… yours truly. I'm sure most freelancers can agree that when first starting out, they worry more about how you will find your next projects instead of focusing on the one they already have.
Well, I happened to have found a quick project and upon looking at my qualifications, my employer thought it would be good to hire me for a different, longer term project. A freelancer's dream, right? At least I thought so. It was my very first project and I thought I hit a home run at my very first at bat.
Now, I'm a computer programmer/web developer, but I'll spare the gory techie details for those of you not in this field. I started out being given usernames, passwords and my project assignment, uploading and installing certain website components. There were no other instructions and only the expectation of me to have them installed within a week.
I didn't ask too many questions nor were many asked of me when I went to work. After all, it seemed straightforward. Plus, I had the best working situation: I was told to keep track of my hours and record them since I was being paid by my own rate. I have to admit, it did cross my mind to "pad" the hours a little, however, I was more interested in making a good impression, so I kept track of it to the exact minute.
The week passed and I had worked approximately thirty hours on this very project. It turned out to be quite a challenge from what I had expected until my project manager had a look at the work that I had done over the course of the week.
Then came the unexpected. Not only had I installed the wrong components, but I deleted existing components that were needed. To make matters worse, I took too much time to finish and it should have been done in a third of the time (especially given that I was charging a fairly high rate).
I wasn't given much of a notice, but I had been terminated from the project and had been told to submit my hours and I would be paid for the time worked. I never heard from them again nor received the payment I was told I would get. Worse yet, I never had seen this employer face to face and I was working thousands of miles from where they were based.
Eventually I decided I would just move on since I couldn't afford the time to keep fighting for a payment I might never see. I had to work, especially after losing a week's wages to this disaster.
In all fairness, I can understand this employer not having any intention of paying for my work which had actually worsened and delayed the project at hand. From this perspective, I learned the hard way the most important lesson that every freelance newbie should follow:
Always know exactly what you are getting into before you take on any project.
Unfortunately, most new freelancers are to eager to get a project under their belt that they will take any that comes their way… and without checking out the requirements or paying attention to how it will b done. The simple solution is to first take on simple projects that are manageable and without surprises and ASK QUESTIONS if you are not sure about anything.
Remember, once you are in over your head on a project, you also risk being short in your bank account later. I could honestly care less now about that lost paycheck, but this hard-learned lesson has helped me approach every project in a professional manner.
About the Author
By Johnny Spence
Author of The Rookie Freelance Job Guide
Article Source: http://www.simplysearch4it.com/article/40229.html
|If you wish to add the above article to your website or newsletters then please include the "Article Source: http://www.simplysearch4it.com/article/40229.html" as shown above and make it hyperlinked.|
| Some other articles by Johnny Spence|