That's the motivation behind a tightly defined set of tasks in CorpWorld. Sure, in a larger sense, if you don't do your daily work - you probably shouldn't get paid. But in actual fact, the only tasks where inaction could have immediate financial consequences involve documenting exactly how many hours you worked since the last time you got a paycheck.
When I used to work for the state, we had a timecard. We walked in the door, pulled the card with our name on it and stuck it into the clock. There was a satisfying *ka-chunk!* and our card went back in its holder. When you left work, you did the same thing.
And some poor schlub would collect the cards at end of two weeks, do the math, and print up everybody's checks.
Certainly not the most efficient process. With a lot of cards and manual math, it took time and was error prone. Additional time was required to audit the numbers and make sure there were no mistakes.
-But the effect on each worker was pretty modest. A few seconds each day on the way in or out
In CorpWorld, my time tracking has been brought into the modern age. Here's what I do to get paid:
At the end of each week, I:
- Log into a secure website
- Create a new timecard
- Type in an amount of time for each day of the week.
- Save the resulting timesheet to PDF
- Print the PDF
- Sign the timesheet
- Walk the timesheet down to my manager's office (3 floors down)
- Get my manager to sign it
- Fax a copy to an 800 number at headquarters
- Fax another copy to a local office
- Scan a copy of the signed timesheet to PDF
- Email the scanned timesheet to my manager
I know, you're asking - why fax and email? Because the recipients at those locations do not accept other methods. And if any of these recipients don't get what they want when they want it - my direct deposit will be delayed. I know this because one time my manager and I were out on successive days and I missed the window. Instead of a deposit in my bank accost, I received a stored value card via express mail (for the record, SVCs = sucky way to move money).
Then there's the matter of my employer knowing what I'm working on. Yes, I was here for 40 hours last week, but what did I actually do?. We have a typical (read: user-vicious) timekeeping system where I log in, and enter a breakdown of what categories of tasks I worked on each day.
Right now, I am working on a colossus of a project - so virtually all of my time goes to one of two categories: Big Project-Specific Tasks and Big Project-Administrative Tasks. The amounts I put in these categories almost never change.
Aside from those, I have two other categories Non-Big Project-Administrative Tasks and Ad hoc stuff - the amounts I can put in either of these are strictly enforced. If I go over, I will hear about it.
If I don't enter all of my time by the end of the week, I will hear about it - from multiple people. The level of granularity allows interested managerial types to look at a report and say, "this guy logs a lot of hours to the Big Project," but not a whole lot else.
Enter time tracking system number three - which I'll call Racer. Racer supports a more granular analysis of what I'm doing on the Big Project. At some point, I'm given a set of tasks - and I estimate how long each will take. At the end of each day, I'm supposed to log into Racer (which helpfully does not support single sign on- and bars the ability to remember its log in credentials. Oh, and it throws a Certificate Error because of how it's installed.). After logging in I decrease the number of hours left for each task I worked on.
So, one of my tasks is estimated at 10 hours. That day, I work on it for two hours. End of the day I log into Racer and drop the task's remaining hours to 8.
The next day, something blows up and I spend four hours working on it. Consensus is reached, but there is not a lot of progress towards the ultimate completion. I log in, and leave the number at 8. I am not allowed to update the original estimate of 10. I strongly suspect that this is not how Racer is intended to be used, but it's irrelevant in any case. The task sits at 8 because that's what is left to do.
At some point, I will be asked by a colleague on Big Project to help them with something. Were I a mindless process monkey, I would say "Give me a task in Racer, and I can help you." That is what is expected, but at the point where they are asking, it's unclear how long helping them will take. I say "Sure, I'll help." And three hours later, I've lost a good part of my day, but they have what they needed and we both feel good. But now I have to account for those hours. I have no specific task in Racer, and if I follow the rules I should ask my team leader for one.
Being me, I do. They spend ten minutes explaining how involved it would be to add another task. Technically, it will not take long, but they need approval to create a new task for me - and they're not sure they'll be able to get it approved. They say, for three hours you can probably just roll it into your existing tasks. If it's recurring work, I should get a new task. As I'm pretty sure this was a one off thing - I leave it at that.
Racer is tracking progress on three tasks for me, so I consider logging into Racer to say "nothing happened" but it will do that automatically. So I don't log in.
At the end of the week - I have worked 40 hours, and spent a little more than 2 hours logging, printing, faxing, scanning, emailing, authenticating, re-logging with greater detail, re-authenticating, re-re-logging with still greater detail.
And while I'm not at all confident that the resulting muddle of data will be an accurate reflection of what happened in the past week, I am certain of one thing:
I will get paid on time.