If I understand juped correctly, the SIAI hands projects to editors, who go off for a while then come back with a finished product. Nobody is monitoring editors to know how many hours they do in fact work. And it’s not very relevant, since someone who works half as much but twice as fast will take the same time. So paying by the hour doesn’t seem to make much sense, even assuming trustworthy reporting.
I’m not sure how things have been done in the past, but as of last week I’m in charge of the document production team and have access to editors timesheets.
I’d also suggest that you are overestimating the variance of speed (holding quality of the product constant) of workers who stick with the team.
Finally, tasks aren’t always as clearcut as I think you imagine (not every task is, go convert this document and get it back to me) so that would complicate paying in a non-hourly fashion. Additionally clear cut tasks might vary in difficulty—converting one document might be easier then another—which means assigning a dollar figure isn’t a trivial task and comes with it’s own costs.
There may be other (notably legal) reasons to prefer to offer hourly wages rather than piece work. And if you’re expecting your workers will misreport their hours, you have other problems!
Each employee has a timesheet (on Google Docs) where they report their hours along with a description of what they spent those hours on. This doesn’t allow for fine grained analysis of how effective each worker is (or if they are embellishing slightly), but it’s enough to ensure that any substantial miss reporting does not occur.
I am curious, how does it work out as an hourly-rate thing?
Sorry, I don’t understand the question. Could you elaborate?
If I understand juped correctly, the SIAI hands projects to editors, who go off for a while then come back with a finished product. Nobody is monitoring editors to know how many hours they do in fact work. And it’s not very relevant, since someone who works half as much but twice as fast will take the same time. So paying by the hour doesn’t seem to make much sense, even assuming trustworthy reporting.
I’m not sure how things have been done in the past, but as of last week I’m in charge of the document production team and have access to editors timesheets.
I’d also suggest that you are overestimating the variance of speed (holding quality of the product constant) of workers who stick with the team.
Finally, tasks aren’t always as clearcut as I think you imagine (not every task is, go convert this document and get it back to me) so that would complicate paying in a non-hourly fashion. Additionally clear cut tasks might vary in difficulty—converting one document might be easier then another—which means assigning a dollar figure isn’t a trivial task and comes with it’s own costs.
There may be other (notably legal) reasons to prefer to offer hourly wages rather than piece work. And if you’re expecting your workers will misreport their hours, you have other problems!
Basically, how do you count the hours?
Each employee has a timesheet (on Google Docs) where they report their hours along with a description of what they spent those hours on. This doesn’t allow for fine grained analysis of how effective each worker is (or if they are embellishing slightly), but it’s enough to ensure that any substantial miss reporting does not occur.
I see. As an EVE player, I know all about Google Docs timesheets...