Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Post History

50%
+0 −0
Q&A How can a new writer make a realistic estimate of his work rate?

Estimates of how long work like this will take are always guesswork. One can make some excellent guesses when one is experienced, but even then, it's advisable for one to take several factors into ...

posted 13y ago by Neil‭  ·  last activity 5y ago by System‭

Answer
#3: Attribution notice added by user avatar System‭ · 2019-12-08T02:15:02Z (about 5 years ago)
Source: https://writers.stackexchange.com/a/5214
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision by (deleted user) · 2019-12-08T02:15:02Z (about 5 years ago)
Estimates of how long work like this will take are always guesswork. One can make some excellent guesses when one is experienced, but even then, it's advisable for one to take several factors into account:

- **The difficulty of the material.** Have you seen any of the text you'll be translating? If you have, then you already have a rough guide as to how long this will take.   
  
I suggest _actually doing the cleanup work you'll be doing on a few pages of the material_ while timing yourself. You can then make an estimate of how much time the core project will take. This is an amazingly simple and useful technique that I do with every editing or rewrite job before _quoting_ a fee or setting any timelines, to avoid surprises for myself or for the client.   
  
While this is much simpler with straight text (where you will have a word or page count), I imagine similar techniques can be used with translating an app.   
  
(Perhaps another tech writer can chime in about this. How do you estimate the volume of application text? Is there a metric here that's useful?) 

- **Communication issues** can also add time to a project. In this case, I'm guessing the documentation team will be in the office where you'll be doing the work?   
  
If you come across problems while doing the rewrite that are prohibiting you from proceeding, timely responses to questions from your client will make your job easier. If your only contact is in Japan, you'll have to wait overnight for responses. 

- **Familiarity with the material** is also something that can add time to a project. In this case, you have a technical background, but are you familiar with Android's quirks? If not, add a little time to your estimate. 

If, after getting a time estimate together, you find that the client's timeline is truly unrealistic, I recommend going to them with this information and discussing the issue. If the two of you truly are at odds here, then this could easily turn into a difficult working situation that it'd be best to avoid. On the other hand, if your estimate is fairly close to what they're looking for, then you have no problems.

#1: Imported from external source by user avatar System‭ · 2012-03-12T07:46:33Z (almost 13 years ago)
Original score: 4