<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The GITS Blog &#187; agencies</title>
	<atom:link href="http://ginstrom.com/scribbles/tag/agencies/feed/" rel="self" type="application/rss+xml" />
	<link>http://ginstrom.com/scribbles</link>
	<description>Random scribbling about programming, translation, and Japan</description>
	<lastBuildDate>Fri, 11 May 2012 05:10:41 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>The problem with &#8220;screening&#8221; translators</title>
		<link>http://ginstrom.com/scribbles/2009/04/29/the-problem-with-screening-translators/</link>
		<comments>http://ginstrom.com/scribbles/2009/04/29/the-problem-with-screening-translators/#comments</comments>
		<pubDate>Wed, 29 Apr 2009 11:32:51 +0000</pubDate>
		<dc:creator>Ryan Ginstrom</dc:creator>
				<category><![CDATA[freelancing]]></category>
		<category><![CDATA[translation]]></category>
		<category><![CDATA[agencies]]></category>
		<category><![CDATA[freelance]]></category>

		<guid isPermaLink="false">http://www.ginstrom.com/scribbles/?p=72</guid>
		<description><![CDATA[An acquaintance who owns a translation agency was complaining to me the other day about the pool of freelancers who send him applications. He claims that he wants top-quality translators, but so many mediocre ones apply that he can't sift through all the noise. He keeps creating stricter screening procedures in the hopes of filtering [...]]]></description>
			<content:encoded><![CDATA[<p>An acquaintance who owns a translation agency was complaining to me the other day about the pool of freelancers who send him applications. He claims that he wants top-quality translators, but so many mediocre ones apply that he can't sift through all the noise. He keeps creating stricter screening procedures in the hopes of filtering out the riffraff, but it doesn't help.</p>
<p>I had a look at this agency's requirements for application:</p>
<ul>
<li>Email lengthy resume, with lots of required information</li>
<li>Email statement of motivation for applying</li>
<li>Email several sample translations</li>
<li>Send above documents via postal mail</li>
</ul>
<p>Motivation for applying? Is this a freelancer application or an essay contest? And why require the same documents to be both emailed and posted?</p>
<p>I think the problem is clear: the agency's screening process is screening out the top applicants, not the bottom ones. I don't think many established translators would go through this kind of rigmarole just for the chance of getting work from this agency; established translators already have a good stream of work.</p>
<p>In other words, when you hire an established translator, you're competing with other translation buyers for this person's time. Why make it a hassle to switch?</p>
<p>It's pretty obvious to me that this agency thinks too highly of itself. You might even take the cynical view that the agency is screening for exactly what it wants: the timid and easily controlled. That's fine. But then don't come complaining to me that you can't get any decent talent.</p>
<h3>How to get good translators</h3>
<p>The big problem with this agency's approach is that it's passive. The agency puts up an "employment opportunities" page, and waits for the applications to roll in. This kind of approach is obviously going to be biased toward people who don't have enough work for whatever reason &#8212; in at least some cases because they're beginners or not good translators.</p>
<p>In my book, the best way to find good translators actually involves doing some work. Instead of passively waiting for applications, go to where translators hang out &#8212; mailing lists, forums, what have you. Find the ones who look competent, and contact them. Then if rates, specializations, and other factors match up, send them a small, paid job. If they do well, send increasingly large jobs. I've had several clients approach me this way, and these have turned into some of my best customers.</p>
<p>Sure, this is more work than casting your nets and seeing what turns up in them. But if you truly want good translators, and aren't just paying lip service to quality, can you afford not to?</p>
]]></content:encoded>
			<wfw:commentRss>http://ginstrom.com/scribbles/2009/04/29/the-problem-with-screening-translators/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Volume discounts</title>
		<link>http://ginstrom.com/scribbles/2008/11/24/volume-discounts/</link>
		<comments>http://ginstrom.com/scribbles/2008/11/24/volume-discounts/#comments</comments>
		<pubDate>Mon, 24 Nov 2008 03:22:33 +0000</pubDate>
		<dc:creator>Ryan Ginstrom</dc:creator>
				<category><![CDATA[freelancing]]></category>
		<category><![CDATA[translation]]></category>
		<category><![CDATA[agencies]]></category>
		<category><![CDATA[business]]></category>
		<category><![CDATA[discounts]]></category>
		<category><![CDATA[freelance]]></category>
		<category><![CDATA[volume]]></category>

		<guid isPermaLink="false">http://ginstrom.com/scribbles/?p=654</guid>
		<description><![CDATA[One question that often comes up among freelance translators is whether we should give volume discounts. I'm not against giving them in principle, but I think that we need to weigh the pros and cons of doing so. Crossed purposes Often agencies will ask for rather large volume discounts &#8212; larger than translators are willing [...]]]></description>
			<content:encoded><![CDATA[<p>One question that often comes up among freelance translators is whether we should give volume discounts. I'm not against giving them in principle, but I think that we need to weigh the pros and cons of doing so.</p>
<h3>Crossed purposes</h3>
<p>Often agencies will ask for rather large volume discounts &#8212; larger than translators are willing to give. A big reason for this is that the interests of translators and translation agencies aren't aligned. The marginal cost of production falls much more rapidly for the agency than for the translator. Although they do have to proof, edit, and (in some cases) DTP your work, a large proportion of the agency's costs are fixed: salaries, sales, marketing, rent, &#8230; Selling 200 pages of translation isn't much more costly to the agency than selling 100 pages.</p>
<p>Big jobs greatly increase the profit margin of the agency, and thus they're often willing to offer a hefty discount to get them. The agency has then got to turn around and convince the translator to accept this discount.</p>
<h3>Ramp-up time and familiarization</h3>
<p>The marginal costs for the translator also decrease with volume. I think most translators will agree that doing five 1,000-word jobs will take more time, on average, than one 5,000-word job. For me, it's because it takes me a little time to get my head into a particular job, and with five different jobs I've got to switch gears five times. There's also the terminology issue: I usually have fewer and fewer terms to research/come up with good translations for as the job goes on.</p>
<p>On the longer job, my translation will also tend to be better. This is because I get a better picture of what the document is saying; when terms are used more often, or the technology is described in more detail, I have a better chance of being accurate with my translation.</p>
<p>But although my output does increase with larger jobs, it still takes more time (i.e. costs more) to do 200 pages than 100. This might be worth a discount, but generally not the really steep ones that some agencies ask for.</p>
<h3>Discount or surcharge</h3>
<p>Because of the benefits of longer jobs, I'd prefer getting more large jobs and fewer small ones. As a translator, I'd prefer doing this by charging a surcharge for smaller jobs. But of course, clients never like to pay surcharges, and love to get discounts. So why not turn it around: charge what you consider a decent rate for large jobs, and a commensurately higher rate for small ones &#8212; but tell the client that the small-job rate is your normal rate, and the volume rate is your discounted rate.</p>
<p>On the other hand, if the client wants discounts for matches in a TM, then in my view the volume discount goes out the window. It's either one or the other.</p>
<h3>What you can get away with</h3>
<p>As is almost always the case with business (and as freelance translators, we <em>are</em> in business), it's not a matter of what's fair, but a matter of what you can get away with. If an agency can squeeze a big volume discount out of a translator, it will. And if the translator can get away with not giving a volume discount, she won't. The need to hire and retain good translators, and the need to attract and keep clients, are what balance the equation.</p>
<p>In the end, I take a request for a volume discount as a bargaining position. I weigh that request against how attractive the client's work is, relative to other sources of work that I have. If the numbers don't match up, and the client won't accept my counter offer, then I won't take the work. If they do add up, then I will.</p>
]]></content:encoded>
			<wfw:commentRss>http://ginstrom.com/scribbles/2008/11/24/volume-discounts/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>Ministry of Kitchen Sinks</title>
		<link>http://ginstrom.com/scribbles/2008/10/21/ministry-of-kitchen-sinks/</link>
		<comments>http://ginstrom.com/scribbles/2008/10/21/ministry-of-kitchen-sinks/#comments</comments>
		<pubDate>Mon, 20 Oct 2008 15:22:02 +0000</pubDate>
		<dc:creator>Ryan Ginstrom</dc:creator>
				<category><![CDATA[translation]]></category>
		<category><![CDATA[agencies]]></category>
		<category><![CDATA[english]]></category>
		<category><![CDATA[government]]></category>
		<category><![CDATA[Japanese]]></category>
		<category><![CDATA[ministries]]></category>

		<guid isPermaLink="false">http://ginstrom.com/scribbles/?p=469</guid>
		<description><![CDATA[A lot of Japanese government agencies have English names that are more &#8230; descriptive &#8230; than the Japanese. Probably the worst offender is the 文部科学省, which has the quite unwieldy official translation of Ministry of Education, Culture, Sports, Science and Technology. This is a real pain when you're constrained for space, such as when translating [...]]]></description>
			<content:encoded><![CDATA[<p>A lot of Japanese government agencies have English names that are more &#8230; <em>descriptive</em> &#8230; than the Japanese.</p>
<p>Probably the worst offender is the <a href="http://www.mext.go.jp/">文部科学省</a>, which has the quite unwieldy official translation of <a href="http://www.mext.go.jp/english/index.htm">Ministry of Education, Culture, Sports, Science and Technology</a>. This is a real pain when you're constrained for space, such as when translating a table or PowerPoint presentation. At least the abbreviation is a tidy four-letter "MEXT."</p>
<p>Perhaps a bit less drastic is the 郵政研究所, literally the "postal policy research institute." They slipped a trendy "telecommunications" into the English translation: "Institute for Posts and <em>Telecommunications</em> Policy."</p>
<p>Another example is the <a href="http://www.mlit.go.jp/">国土交通省</a>. Literally, it's the "ministry of land and transport," but the English translation is "Ministry of Land, <em>Infrastructure</em> and Transport." The MLIT was created by merging the old Ministry of Transport and Ministry of Construction; my guess is that the MOC people were upset about losing any mention of "construction" in the Japanese name, so stuck the far more trendy "infrastructure" into the English translation as a face-saving measure.</p>
<h3>Land grab?</h3>
<p>The MEXT started life as the 文部省, with a nice, pithy English translation of "Ministry of Education." One can only imagine the backroom deals and lavish <del datetime="2008-10-18T11:52:12+00:00">foreign junkets</del> overseas fact-finding missions that went into getting a 科学 (Science) tacked onto them.</p>
<p>Since the ministry pretty much controls its own English translation, it looks like the MEXT really let their territory-coveting hair down when coming up with the English name. I'm actually surprised that they didn't simply call themselves the Ministry of Life, the Universe, and Everything.</p>
<h3>Example of restraint</h3>
<p>A good example of restraint is the <a href="http://www.soumu.go.jp/">総務省</a>, literally the "general affairs ministry." In 2001, it changed its official translation from <em>Ministry of Public Management, Home Affairs, Posts and Telecommunications</em> to <a href="http://www.soumu.go.jp/english/index.html">Ministry of Internal Affairs and Communications</a>. Still more of a mouthful than the Japanese, but it's heading in the right direction.</p>
<h3>At least some agencies get it</h3>
<p>Of course, not all English translations of Japanese government agency names are tales of woe. A good example is the 海上保安庁, which recently changed its official translation from the somewhat cryptic Maritime Safety Agency to the much more understandable <a href="http://www.kaiho.mlit.go.jp/e/index_e.htm">Japan Coast Guard</a>. In this case I suspect they simply gave in to pressure, since most English-speaking media referred to them as the Coast Guard anyway, and even 海上保安庁 people usually called themselves the Japanese Coast Guard when dealing with foreign entities.</p>
<h3>And now for something completely different</h3>
<p>While researching this post, I noticed that <a href="http://www.kenkyusha.co.jp/">Kenkyusha</a>'s Reader's Plus dictionary has a translation for "Ministry of Silly Walks": ばかあるき省.</p>
]]></content:encoded>
			<wfw:commentRss>http://ginstrom.com/scribbles/2008/10/21/ministry-of-kitchen-sinks/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

