Outsourcing vs. offshoring, and how U.S.-based technical writers can stay competitive
Jun6
By Ron Creel
I have recently heard people confuse the distinction between “outsourcing” and “offshoring.” To clarify, outsourcing is when a company hires another business, such as Your Writing Dept, to do a specific task for them either because they do not have that talent in their existing labor pool, or they need to temporarily add skilled members to their existing team, but cannot justify hiring them as permanent staff.
I have seen many cases where outsourcing is a cost effective method for a company to produce high quality written material for a fraction of the cost of having a full-time technical writer. And writers who work on outsourced projects have the ability to learn how to work quickly and can expand the breadth of their knowledge and portfolios. To fully appreciate the benefits outsourcing a writing project can bring to a business, one needs to look at the overall costs associated with maintaining a full-time writing team that might sit idle periodically for no fault of their own. Look at it this way, if you owned a medium-size manufacturing company that periodically needs new user guides to support new product, would you rather pay a technical writer $60,000 to $80,000 a year, or pay a U.S.-based outsourcing business $3,000 to $10,000 for several product manuals?
Offshoring, while similar to outsourcing, is the hiring of a company, or an individual, outside of the home country where the business operates. For example, if a company is based in the U.S. and hires a company in India to develop software user manuals, they would be offshoring this work. Sure, it’s also outsourcing the work, but careful use of the two terms helps define the specific benefits and downsides of these types of arrangements.
Frankly, from an American viewpoint, we do not want to see jobs taken away from people living in the U.S. So, aside from the emotional aspects of offshoring technical writing projects, there are several negative aspects to offshoring. One would be that native English speakers make better writers for an American audience. But, this is not to say that all Americans can write at an expert level. While labor costs can be much lower with offshoring, I have seen that costs can actually increase with the need to redo some of the work produced by offshore writers. Of course, communication differences and timezones can be a barrier to effectively working with an offshoring company.
Your Writing Dept is a Sacramento-based writing firm that specializes in developing technical manuals and user guides. We’re the leaders in technical communications in Northern California. Note: We outsource, rather than offshore. Email us for more information about our services at info@yourwritingdept.com.
Additional Posts from Your Writing Dept
- Laid off technical writer? We want to hear from you.
- InfoPorn: Presenting raw data with visually stimulating graphs
- How many spaces after a period? One or two?
- Will Bing become the new Google?
- Tips for hiring an outsourced technical writing team to document your product or process
- MS Office 2007 Hidden Treasure
Enjoy this article?
Consider subscribing to our RSS feed!
6 Comments
Leave a comment
You must be logged in to post a comment.
5:36 am on June 25th, 2009
Glad to see an article discussing the two. Another variation in this equation - when techwriting jobs move overseas, but to a branch of the same company. Perhaps a flavor of offshoring? This is a trend I’ve seen where departments cut costs by laying off US-based writers and rehire in a branch office of the company in another country.
It is a reality of our field. As is the fact that companies who do hire in the US are looking for that ‘expert’ in a certain tool or technology. So get as much as you can out of your current position and look for those opportunities to expand your experience. It may not save your current job, but it will help find the next one.
7:17 am on June 26th, 2009
A few years ago, when I noticed that a lot of vacancies were asking for Framemaker knowledge (which I didn’t have) I downloaded an evaluation copy, studied furiously, and passed the Adobe Certified Expert exam. I still didn’t have real-world experience of FM, but that ACE certification on my CV got me into interviews where I had a chance to make a personal impression. Added bonus: even when being interviewed for jobs that didn’t need FM, I still got credit for being willing to update my skills.
11:54 am on July 2nd, 2009
Unfortunately, neither the person at LinkedIn being quoted nor the author of this blog offers much insight as to what might be the root cause for the changes in employment of technical writers.
There is likely stagnation at the pace of improvements in the productivity of tech writers. Causes for this? Answers: Same Help technology provided by Microsoft for 15 years, disconnect between sw engineering cycles and documentation cycle (management issue), decreasing profit margins in many software sectors resulting in unreflective management responses in cutting costs, design of applications don’t incorporate intelligent user assistance technology so UA looks to mgmt like “overhead” rather than as part of product. So my point is that both product-development technology considerations and management misunderstandings both play a role.
9:13 pm on August 25th, 2009
Jenna,
This post has been edited to remove the text from your post. My apologies if I offended you.
Ron