Unknown

Photo by Pedro Figueras on Pexels.com

People at work are angry with you. Well, not really angry so much as irritated because you didn’t do a part of what you were supposed to.

I just learned that I was supposed to do part of a software configuration in the new software for a school district that just converted. It’s not a life or death issue and, yes, it is inconvenient but it isn’t something that keeps the district from doing what it is supposed to do.

The only problem is that I didn’t know I was supposed to do it.

The process is still pretty new and there are no manuals from the software company that says “Do this in this order to set up the software for district use after conversion…” so we are kind of feeling our way through the process. Stuff gets missed or falls through the cracks since we don’t know completely what needs to be done.

There are known knowns. These are things we know that we know. There are known unknowns. That is to say, there are things that we know we don’t know. But there are also unknown unknowns. There are things we don’t know we don’t know.

Donald Rumsfeld

So why the heck are you irritated with me if I didn’t know I was responsible? And why the heck are you irritated with me if I didn’t know what the heck I was supposed to do if I didn’t know I was supposed to do it?

Now that I know, I am aware of it and can take care of the next time, but for now:

BITE ME.

Teams

top view photo of people near wooden table

Photo by fauxels on Pexels.com

Transition is hard. Lots of people hate change and resist it when it happens. I am not really one for change for change’s sake and I don’t really fear it, but sometimes change just isn’t necessary. – especially when you have something that serves the purpose fine the way it is.

Software changes should make your life better (either more convenient, streamlined, or all encompassing). At the very least, it should make your life less complicated right off the top. At work, we are going in the wrong direction for ease and internal communication.

We are switching from Skype for Business to Microsoft Teams. Never heard of it? Yeah, me neither until now.

I am just learning about this new software and how to use it, but so far I am not all that impressed. It seems to have taken the social media approach to business communication. Teams doesn’t integrate Outlook with it, so not only do I have to have Teams open but I also have to have a separate program open for my calendar and email. How is that really streamlining things? It’s not. At least not yet.

Guess you could say I am not feeling much like a Teams player…

**Thank you, thank you…I’ll be here all week…**

Do your job

man sitting on black leather padded chair

Photo by Jason Appleton on Pexels.com

The job I have is to help people with the software they use every day. I help them extract data from the software and help then fix issues when it doesn’t work correctly.

What I don’t like doing is their jobs for them.

We often get requests that are a are a regular function of their job, something they should know how to do after years of working at the job. Yes, there are those who are new to the position so I can understand asking for help at that point.

However, there are lots of people who call us on a regular basis to help them get data from the system they should have learned how to do by now. They just refuse to figure it out.

“Oh, it’s just easier if you do it.” 

“I know it is accurate when you do it.” Um, no, not necessarily. It’s your data. We don’t know if it is accurate. We just tell you what we see.

“It takes too much time to learn this stuff.”

Good grief…just freaking do your job.


Anyone else out there tired of doing someone else’s job? What is it and why do you do it?