Second Post

Don't worry, I'm not naming each post consecutively. The more I think about blogs and blogging, the more I realize that "good" blogs are really hard to come by and that finding "favorite" blogs are really based on personality types and interests and good content. Kind of like comic strips. I read the comics in the Philadelphia Inquirer everyday. I have definite daily favorites and some that I just don't get. I am sure that writing daily comics if very difficult and it shows sometimes in the strip. I applaud Fox Trot's creator for cutting back to weekly rather than let the strip go down hill due to lack of inspiration etc.

Anyway, I've decided to post less frequently than other blogs - but try to have good content, written in a style that I hope will suit your taste. I hope that the analogy above translates into tech issues. We'll see.

OK now onto the post:
I should have named this one "A watched Outbox never boils" or "A penny saved is a dollar spent later". Non profit budgets are really interesting. Rarely is there a line item for IT expenses. Rarely does a non profit org budget for maintenance. It's just not something that we can approach funders about. All of the money goes to programs, programs, programs. Very little for operating or general budget. Of the operating budget, very little is set aside for IT maintenance if any at all. This is nothing new to you. It's nothing new to us either.

Because of this budget dilemma, it seems that non profit staff are quick to shoo our techs out the door in order to try to save a few dollars. Our techs are keenly aware of this and try to be as efficient as possible.

Take this story for instance. A non profit asks our tech to fix an Outlook email issue during his regular visit. The tech is conscious that he is just about out of time for the appointment and wants to get this last issue taken care of so he doesn't have to charge the organization more money for an additional visit later. He makes some changes in Outlook to fix the issue. To test the fix, he sends a test message from the user's Outlook to himself.

The message sits in the Outbox, and sits, and sits, and sits, and sits, and sits, and sits, and sits, and sits, and sits, and sits, and sits, and sits, and sits, and sits, and sits, and sits, and sits, and sits, and sits, and sits, and sits, and sits.

What seems like forever turns out to be 3 seconds. 3. Do you know how many times the user can say "OK, see you next week" in 3 seconds? Plenty. The user was so worried about time that she wasn't concerned whether the fix actually fixed her issue. Once the email left the Outbox, the tech felt better about leaving and the user went back to using her computer for important non profit work:

Good thing she's budget conscious.