Over time, I have been involved in some of the worst projects ever as a freelancer, consultant, or some other “non-employee” relationship. When you are a direct hire to a company, you do not have the freedom to pick and choose what you work on. But as an outside person being paid to work specifically on one project, you do have the choice. I have been burned so many times it isn’t funny, but I have learned a lot from my mistakes. 

With that distinctly unsweet scenario in mind, TechRepublic Premium presents 10 of the biggest red flags to be wary of. 

• Featured text from the download:

  1: No clear spec or goals

  All too often, I’ve been approached to work on a project, but the person trying to arrange the deal can’t tell me what they really need done. It’s not that they are under some strange code of silence. They really have no clue what they want. They have a general idea of what the finished product should look like and a superb understanding of its differentiating factors or killer features, but outside that they have not thought it through. 

  This is one of the most common and most significant danger signs! How many hours’ worth of work do you want to throw away on a regular basis because the client realized after you built it that what they asked for wasn’t what they needed? At the very least, these kinds of projects should be contracted only at a per-hour rate.

Boost your project work with our seven-page PDF. This is available to download for FREE. Get access to more content with a Premium annual subscription. Use the code 25off-trp to get a 25% discount.

TIME SAVED: Crafting this content required 14 hours of dedicated writing, editing, research, and design.