Time Tracking

My course is done. I thought it was spread out over four weeks because that's how our materials were laid out, but really it was one hour for four days spread across two weeks. I would've like a longer course because each course seemed to skip over material that would've been followed up on, on the next course.

That's not to say that I didn't get anything out of it. Because I started as a Jr. Tech, my habit is to go in and solve problems. Technically, I am still solving problems, but it's not in my best interest to be a part of the day-to-day work. My focus is on enabling others to solve problems in a systematic way. One thing I've appreciated was the recommendation to read The E-Myth Revisited by Michael Gerber. I'm about a hundred pages in and I see Without documentation, all routinized work turns into exceptions. At various stages of my career, I've wanted to get into documentation. And now that I'm here, I'm like, "how does one write words??".

As I figure that out, my top priority is time tracking. Throughout the course, there's mention of a rouge employee who is great at what they do, but they don't follow the standards. The more they described this person, the more I realized I was them. I am the rouge. It's not even in a malicious way, but more a development over the lack of structure that I've had. Well, now that I'm aware of it, I've challenged myself to fix my worst habit - Time Tracking. I just hate it. Even clocking in and clocking out is a chore. In an ideal world, I show up, something identifies how long I've been in a place, and then I leave and it updates itself. I'll have to work on that myself it seems. Anyway, I've roped my dispatcher in to looking at my time throughout the day to hold me accountable. If I know someone is watching, then instead of jumping from task to task, I'll take the time to log my day as I go versus relying on my memory at the end of the week. It's easier for everyone all around and won't keep me up late on Fridays in front of my computer.