Timesheets/time tracking - does it ever not suck?
Curious to hear the opinions of this sub on timesheeting/time tracking.
It’s a necessary evil, but the process at my current employer involves filling out a spreadsheet every week with a seperate spreadsheet for oncall rotations then uploading it into SAP.
Surely there must be a better way.
Edit: lots of great comments and experiences in this thread.
While I really would like to improve our systems, I should have stated that I am a salaried employee on an internal IT team and I work for a large national company, and all my time is billed to capital projects.
Our current SAP CATS spreadsheet system caters for a lot of the “businesses within a business” that we have and all the different requirements those of “businesses”.
Maybe one day I will find the time and the money to fix this.
Posted Nov 15, 2020, 10:28 PM UTC · edited
Internal IT is great as we don't track time. Just keep everything running and you get paid the same every two weeks.
I'm internal IT and expected to track time against internal projects.
That's usually a sign of bad management, IMO. I've never had people track time. I either see progress, or I don't. I either see people goofing off and not being productive, or I don't. IMO a manager should be able to tell work is being done without micromanaging. If you can't trust someone to do their job, they shouldn't have it. You manage them up or you let them go.
I want reports on progress, not punchcards. Telling me you spent 4 hours doesn't tell me what you DID. Punchcard managing doesn't reward hard work, it encourages the required minimum.
Edit: I said USUALLY. yes, there are cases where it's useful, but it should not be the primary metric. Output is the primary metric.
Or fed gov contract reporting requirements. I'm required to report time because the servers I work on are used for gov projects.
Bad management. Government is the poster child of bureaucracy and fucking shit up.
I'm sure that makes sense in a smaller shop, but at my Fortune <50 company, it's less about my time and more about project OPEX and staffing data.
Yeah, we try to operate as informally as we can on a day-to-day basis but larger orgs come with a certain amount of complexity and paperwork/legal expectations. Initiatives flow up and down the command chain and it can be very nice to point to hard data when asked for an accounting of your work. It also helps you build a reputation for competence and responsiveness.
I track: ticket number, application/tool, category of work, time (15 minute increments), and a brief description.
It's not used by the team for daily operations, but I've drawn on it for various things:
How much time am I spending on a new application vs time spent on the 2 applications it replaced?
Senior admin says: "upper management wants a detailed justification of how we use our time, with estimated costs & business value."
Analyze top 10 tickets for the past quarter in terms of time spent -- how can we avoid these time sucks in the future?
Contract manager says: "we're going to start reporting our top contributions quarterly to the client, starting with the current almost-completed quarter"
Based on these experiences, I'd track all this stuff for my own use (and for defensive purposes when needed) even if I hadn't been asked to set it up.
The problem I'm having at my (internal) work is that we spend far more time on maintenance than is budgeted and I'm having a hard time getting that information relayed back up the management chain because there's no time tracking to quantify it.
I've spoken with my direct manager about it with my intention simply being to increase visibility into the amount of work preventing us from making meaningful forward progress - but I think they struggle without the data to back it up. All I'd like is for it to be known so that they can properly rebalance the budget to either mitigate then correct the issue or accept it knowing that the output ratio is going to be low.
Really don't know how accomplish this without them tracking. We do track stories, but even when I show an 80/20 breakdown of toil to feature it's seemingly not sufficient to sound alarms.
For me it's a sign of bad management if they don't track time.
Being in an organisation where the IT director abandoned timesheets decades ago, I clearly see that IT is now unable to proof that they are understaffed.
The business is complaining about IT unable to deliver, and a lot of shadow-IT due to that. As the IT director is unable to show that everyone in IT is working more hours than they are hired for, it's impossible to get more IT staff.
I track my own time in Clockify as a CYA, as I wouldn't be surprised if the ball will drop somewhere in the next year and I want to be able to show management my (own) metrics.
I can prove that with how long things take and the backlog of to-dos. If I need additional proof beyond that, I can ask for time tracking.
Where I'm at it's more about giving our manager the data he needs to show upper management where his resources are going and justifying staffing levels and things like that.
Same at my place. Biggest waste.
But when we log 20 extra hours of night/weekend/holiday on-call, it goes in a general break-fix bucket that no one ever questions.
I just wish for once management would ask us why every week someone’s logging 60+ hours, and maybe we should be evaluating those events to try to reduce the need to engage on-call for predictable work that could’ve been handled during normal hours.
Yeah, I used to have to do that and there was no 'admin' bucket. 100% of my time had to be billed to a project and and project managers would constantly bitch about how much time people were billing to their projects. Usually lead to people adding so many projects to their docket that over half their effective time would be tied up in status meetings.
I really don't need to hear this as I procrastinate on filling out my timesheet for last week...
I love how that interacts with the fiction of "vacation hours". Like, "yes, I will spend '16 hours' of vacation time to take Thursday and Friday off, despite the fact that I would be hypothetically working between 6 and 10 hours on those days".
Yes, I realize that it's really "days" and the software handles that by doing the division and allocating you 6.154 hours on your paycheck... but it's still an amusing extrapolation to apply to a "meh keep it working" job type.
We switched to unlimited vacation for higher level IT. While some companies use that as a way to discourage vacation use, my company has been very flexible with it (everyone on my team has taken multiple weeks off this year so far) and just considers it a win to no longer have to spend any time tracking it for salaried IT employees. Takes the “I took Thursday off but something broke Thursday night and I still had to work” out of the equation as well.
Except the reason they stopped doing accrual is to avoid paying it out when you leave (if the state you're in mandates that). Companies love to say it's to help the employee, bullshit, it's solely to help themselves. A few unicorn companies exist where you can get more time off out of the deal, but it's unlikely.
The state we’re in does not mandate that. Not everything is a trick. Some things can be win-win.
Same with my place, it's been pretty good. Just two weeks notice you want off and it's normally cool. Just need to not go pto when a bunch others are off.
Yeah, just make sure issues/tickets are updated and give some update on what is everyone working on during team meeting. Int/Ext IT here
[deleted]
my dream job
damn man, I wish I was you right now haha.