The "Why" Statement

Why do I do what I do? 

• Is it to collect a paycheck? No, but that is a benefit of what I do.
• Is it because I'm a total UM fan girl? No, but that helps.
• Is it due to the experience that I had? That others had? Now we're getting somewhere.

The reason that I do what I do for a living is to change peoples lives for the better through education. Whether I'm wearing my fundraiser hat or my librarian hat, my goal is to empower and transform people through education.

This might seem broad, but it's actually the very core of why I do what I do. I have been changed and transformed by the experiences and knowledge gained at UM-Dearborn. Many have. It is critical to me that others are able to unlock their own potential. In my heart and soul, I believe that UM-Dearborn and the library are where that can happen.

I came back to this today because I returned to work after a LONG vacation and I just needed to get myself pumped up. My break was wonderful and even though I love my work, there's always a pinch of dread having to again wake up again at an early hour and get back to the grind. I am in a class right now and one of the instructors suggested to go back to your why statement for this and other reasons, such as:

• Addressing something at work frustrates you
• The need to prioritize your to-do list
• Having a low-energy day

What is your why statement? I recommend trying to write it out. My first draft was full of drivel and tangents, but after refining and being true to myself and my goals, that's at the core of what kind of work I choose to do in this short life.

Year of Gratitude - Day 144 - A good pen

I love good pens. I never turn down the chance to get a new one.

How was your meeting?

One day I asked a colleague: "How was your meeting?" A shrug was followed by a single word: "Routine." We chatted a moment longer and then I headed home, but that word, "routine," really stuck in my mind. Meeting for meeting's sake is one of my ultimate pet peeves. If there's a hell, it's a long meeting with no agenda, time frame, or purpose. On the drive home I thought about when I call meetings. Here's what I came up:

• A decision needed to be made, especially a decision that effected the entire team and their workload. I heard this first on the Manager Tools podcast, which is absolutely first rate and should be MANDATORY LISTENING for managers at all levels. The Manager Tools blog is totally sweet also.
  
• Complex projects. Sometimes all the detail in an email can't stand up to a good ol' conversation with colleagues armed with paper, pencils, dry erase boards, drawings and ideas. My team always has good, productive discussions that enable us to go into a big project with the right approach.
  
• Collaboration with other departments. Though I supplement all of my meetings with other departments with heavy notes and agendas, sometimes this is another case in which verbal communication is better than digital communication. However, I'm really trying to follow up after meetings at least by writing the minutes in my work journal - but GEEZ that's a whole ton of work! In the end it's worth it, but still.
• One-on-one meetings. This is another awesome tip from the Manager Tools folks. It's great to sit down and just hear what the employees need to talk about. I haven't done that in a while, but look forward to scheduling some of those throughout summer.

Don't let your meetings be routine. Make them count. Make them important. Make them something we CAN'T do without. Make them so that people are excited or intrigued by what's happening at them.

And if we can do without a meeting, than by all means cancel it!