[removed] and other unrewarding translation projects

6件のコメント

• 1
  
  Lara Fernandez 2020年09月23日 00:36

  Hi AlexF,

  Thanks for sharing your thoughts! :) 

  Before I go into responding to your post, please note that I have removed certain bits of the title and body of your thread that could be considered disrespectful to our customers. I'd like to take this opportunity to remind everybody here that the Gengo forums are a public space (except for the ones marked with a star, which require signing in to a translator account) and therefore searchable and accessible by anyone online. We understand that our translators are free to have their opinions about the orders that come through into the system, but we'd also appreciate your understanding regarding a need to be professional and respectful towards the customers who choose to order said content with us. Feedback is always welcome, as long as it's in a constructive manner (which I do appreciate the latter part of your post is, as you do offer suggestions that you feel would improve the situation for you.)

  Now with regards to the actual jobs, there are 2 points that I would like to clarify:

  • Much has been said over the last few months about a huge project for which we initially onboarded a lot of translators in the spring, which ended up not coming to fruition. As it so happens, this large volume of work that has started flowing into certain language pairs over the last week is actually part of said project :) Now, of course, it's up to you to decide whether it's worth your time and effort, but it's worth mentioning that this is actually the project that we had been waiting so long for (and the amounts of work that are coming in now, at an unpredictable pace, are actually only a fraction of what we were originally expecting.)
  • The workbench is designed in such a way that only 10 jobs are displayed per customer. So even if the customer orders 200 jobs in your language pair, you will only see 10 at a time, while the other 190 remain hidden and only appear on the dashboard as the previous ones are taken. There's no scenario where more than 10 jobs from the same customer will be displayed at the same time, so your dashboard shouldn't be really "flooded". If there are more than 10 jobs at any given point, they can't all belong to the same customer. If there are 11 jobs on your dashboard, at least 1 will be from a different customer :)

  Now, your suggestion for an "Opt out" button is interesting, and I will certainly share that with the team :) However, one thing that I would maybe like to explore (please share your feedback and thoughts!) is that, in a case like this, you'd likely have to "Opt out" from all jobs from that customer -- even if there's the possibility that they may order different content from other projects in the future, as I don't think you'd be able to Opt out for one specific project. What would be your thoughts on this? 

  Thanks,

  Lara

• 4
  
  AlexF 2020年09月23日 08:32

  I'm sorry that my twisting of the GIGO acronym caused some distress. It was not my intention. Apologies to all.

  On the Dashboard, only five jobs appear so yes, I don't see any other jobs except those from this customer (and moreover, these are all "Edit" jobs). Then when I go to the "Jobs" menu, I see 10 or more jobs, with the "other" jobs always needing me to scroll down the page. So yes, annoying too. And finally my RSS feed (rmpl) pings me every 10 minutes or so with the latest 10th available "Edit" job which usually appears first because they are larger than the usual "standard" jobs. So yes, considering all this, I am pretty annoyed by the whole thing.

  For the "Opt out" option, I would link it to a "Project" as this is clearly a collection of similar jobs, with the same set of instructions over a given period of time. If this is not possible, jobs from "opted-out" customers can also be put in a separate subsection "Opt outs" that we can go reevaluate from time to time, or in case of dire need, etc...

  I also think that this will help Gengo communicate with the customer. If Gengo has the information that 20, 50 or 80% of the translators are opting out of a given project, it means something about the job itself (unreasonable demands, low compensation, high risk on GoCheck score, unexplained delays on job approvals, etc). So I would definitely add a field where the translator gives a reason for opting out. 

   

  AlexF

   

   

   

• 0
  
  Lara Fernandez 2020年09月23日 08:34

  Thanks for elaborating your point, @AlexF -- this is much better feedback, and will be more useful in helping the team understand why the situation is not ideal :) Passing it along!

• 4
  
  Rup75 2020年09月23日 22:36

  Probably you guys are doing this already... but I think it would be good analyze pickup times, completion times, quality stats and other data between (a) "normal" jobs that consist in a single, coherent piece of text of a certain minimum length and (b) collections of small unrelated chunks, each taken from a different context. 

  What AlexF is referring to is (b) and my impression is that the statistics must be clearly different to (a) even if we ignore this specific big project, so you might draw the conclusion that these collections require a different handling altogether, e.g. with a specific training and/or qualification test, different rates, maybe some kind of a bonus scheme? And what about the GoChecks - is it really always possible to nail a "correct" translation when the original is ambiguous, so does this kind of scoring still make sense in this case? If GoCheck is used anyway on these collections, shouldn't they have a different, more lenient impact on the overall score, or maybe none at all?

  As a first step, it would be very good to have a different flag for these collections, as in TM or Edit jobs where you immediately know what to expect even without looking at the actual contents.

   

• 4
  
  Lara Fernandez 2020年09月24日 07:12

  Thanks for chiming in, Rup75! I'm passing your comment to our Product team too :) Additionally, I've gotten a request from our Product team to get a better idea of the need for this "Opt out" option, so I may run a simple survey in the coming days so I can actually provide some data. 

  On another note, regarding your comments about GoCheck, I've also forwarded to our Quality team so the LSs can take this into account. 

  Please also do note that an option to "Opt out" or a similar solution makes it into the roadmap, implementation won't be necessarily immediate :)

• 0
  
  Chris 2020年10月09日 10:19

  An alternative to an opt-out option might be the ability to group and collapse tasks per customer so there's only one entry or a group name left (ideally with the ability to open those in second browser tab).