Blog Post

Building a Team With Inexperienced Online Freelancers

Stay on Top of Emerging Technology Trends

Get updates impacting your industry from our GigaOm Research Community
Join the Community!


I was recently asked to manage a team of graphic designers, all of them fresh graduates with hardly any professional experience. Always eager to help, I accepted the opportunity, knowing that it would be challenging and educational, for both myself and the team.

I soon discovered that working with new freelancers is very different from working with my more accomplished peers. It required me to get back to basics and deal with issues that I hadn’t encountered before. Just as I had expected, there’s a whole new set of opportunities and problems that come from working with “newbies”.

The Benefits

One observable benefit to working with new freelancers is that you’ll be forced to keep things as simple as possible. It’s not a good idea to overwhelm them at the start with new tools and complex work processes. Introduce these things gradually. This will give you the opportunity to keep the work process streamlined.

Another advantage is the fresh perspective they have. This allows them to bring more innovative ideas to the table. Sometimes, getting too used to a certain process can leave us less likely to see the flaws in the way we work. If your team of newbies is perceptive enough, they can spot these flaws for you.

While there may be some benefits to working with new online freelancers, there are also many challenges. These challenges seem daunting, but fortunately there are ways to work around them.

Underdeveloped Work Habits

Usually, new web workers haven’t established efficient solo working habits. It might take a while before they get the hang of setting deadlines, boosting productivity, and motivating themselves to work well without someone looking over their shoulder all the time.

For this particular problem, writer/editor Ruth Thaler-Carter recommends setting official working guidelines. “Anytime you deal with people new to a given arena, you have to provide guidelines. Even experienced pros might need some direction to deal with a new topic or genre,” she says. Prepare a document showing the ideal work process, including the roles of each team member. This gives everyone a better idea of the scope of their own work.

It also helps to discuss all expectations from the start. This helps to get any misconceptions out in the open, allowing you to correct them early on.

Familiarity With Tools

If some members of your team aren’t tech-savvy, they might not be familiar with the communication and project management tools you use. Even if they are used to social networking tools, like Facebook and Twitter, they might be unaware of how the web is used for business.

To fix this problem, provide a list of required tools, including the reasons why they’re needed, as well as video tutorials on how to use them. Leading by example and sharing your expectations also works, as suggested by Mary Ellen Schutz, an editor. According to her, “If [they] are very skilled at what they do, just very informal in their communications, show them a better way. Be very clear in your expectations.”

Need For a Physical Office

Although this might be less common in the future, there’s also a chance that your team of new web workers will see the virtual office as “less professional” or “less real” than physical offices. This perspective can be detrimental to the team if it means they’ll take their work less seriously.

When I was leading a local group of freelance designers, many of them brought up the idea of moving to a “brick and mortar” office in order to boost their professional image. It was unnecessary at that time, because they had minimal capital and all their clients were offshore. If your team feels this way, shift their focus to the things that really will make them look more professional instead — whether it’s their quality of service or skill levels.

Sometimes, they might be looking for a physical office because of the interaction and collaboration with colleagues that physical proximity brings. If this is the case with your team, encourage them to interact with each other while brainstorming over Skype. Or, if you work with a local team, you could schedule coworking sessions at least once a month.

It may take a lot of initial hard work to turn fresh, inexperienced students into reliable professionals, but investing the time and energy to do it is worthwhile. After all, it was only a few years ago that I, too, started out just as green as they did.

Have you worked with new or inexperienced freelancers? What was your experience like?

Image by eocs from

4 Responses to “Building a Team With Inexperienced Online Freelancers”

  1. Thank you for the tips celine. I think the article is very informative regarding communication and exchanging information. You have mentioned many issues that i had been facing.

  2. Celine, thanks for the tips.

    Even when working with more experienced freelancers, I think many of your tips apply – setting clear expectations and discussing how you like to communicate and exchange information (e.g. through a project management tool, IM, email, etc.).

    We use our own collaboration software to work with freelancers, and the fresh perspective they bring when interacting with our software has definitely been a nice side benefit.

  3. I’m actually working as freelance because of no technology adopters in my country, I’d like in the future to build a team like this offshore and using the technology to work and communicate, I really believe is counter-productive, more expensive and without a real foundation having a physical office on an IT enterprise, it’s obsolete and more stressing, the future is the home office not only on IT but in some other areas, thanks to messaging and logistics technologies, nice tips it this article :) regards

  4. Hi Celine,
    This is a really interesting and useful article and something many micro ISVs face every day. In our case, we don’t have our own team of on-site developers, but instead work with distributed teams, using Agile software development methods. In particular, you raise a number of issues that I certainly empathise with; strong and regular communications are key, easy to use tools and simple processes are important and keeping it simple in the early days. I’ve written a few blogs in a similar vein; here’s one that I’d like to share which I hope will add to the debate:

    Thanks for sharing your experiences.