If you are like me, you’ve gone through several different computers over the course of a decade. I’ve had Dell, Toshiba and HP laptops all that provided (at the time) the needed processing punch. Eventually my software demanded more memory and computational power. Now I reached the age of my MacBook Pro and…….”Wham”! It feels as if there is enough horsepower under the hood to last me a lifetime. Or so I think for the time being.
My feelings of laptop longevity, albeit easily susceptible to change, raises a question. Besides the fame and glory of trying to fabricate smaller and smaller chips, is it really necessary to continue the march down the nanoscale for the average home/business PC?
Don’t get me wrong! I’ll be the first one to ogle at the latest and greatest technology. Also if it wasn’t for chip makers getting smaller, conserving power, we wouldn’t have marvels like the Macbook Air. However, as chip fabricators are currently in the 45 nanometer range shooting to get even smaller, I wonder if Moore’s Law will stop for general consumers sooner than we think.

For some small business, IT procurement can be a challenge. Budgets are tight and figuring out hardware requirements could be daunting. How is it possible to ensure that you get the most out of your computing so your life-cycle isn’t shorter than it needs to be AND you satisfy your employees within reason? One simple key is to address the usage pattern of your employees.

What is the benefit of looking at it this way? 
My eureka story covers this best. I took my car for a routine service and was surprised when the mechanic said I needed new brake pads. They were changed not too long ago and the math wasn’t working out in my head. Skeptical, I ignored his comment. If it wasn’t for the insurance requirements of his company he would have pulled me under the car to see how bad it was for myself. After he told me how many millimeters I had left before I would hear screeching I grudgingly had them changed. Later that week (still doubting my decision) I noticed something while a certain family member was driving the car (Identity withheld to protect my life).  This unidentified individual habitually stopped hard at red lights. AH HA! That was the usage pattern that led to the breaks needing changing earlier than my projected life-cycle. Unfortunately for me I had to fork out the money and reacted to the usage pattern after the fact. It doesn’t need to be that way for IT Procurement. 
For most users they would like a computer to function like their mind. They want to multitask on several different things and they want to do it quickly. Even with most up-to-date system, there is a threshold where it will seem unresponsive because of the multitasking being imposed by the user. So if someone has, say Adobe Photoshop CS3, open with 15 different images, is checking email, listing to a Pandora stream and browsing the web, the usage pattern can change. The goal is to help users understand how they need to think a little differently to maximize their computing productivity. When that message is properly conveyed, the life-cycle will be extended. The trick is to convey that message without inflicting pain.
To avoid any toe to toe confrontations, a simple yet proactive approach can be taken, here are a few options:
  • Every so often, provide employees with reminders and tips on good computing. These can be gathered from the same companies who provide your hardware and software. Sometimes these companies send monthly emails and webinars on useful computing topics. Recycle those in summary to employees in an official company message.
  • Provide a checklist of monthly maintenance tasks to perform (folder organization, file clean up, desktop cleanup, etc)
  • Establish a system to share tips and tricks among employees (wiki page, whiteboard sessions). 
(Reader Beware – Oncoming Rant)

With a snowy afternoon and a hot cup of tea I decided to make good use of my time and start a document I’ve put on hold for long enough. In an attempt to open my eyes to more than the Microsoft Office Suite, I started learning/using Pages (Part of the iWork ’08). 

The initial keystrokes were hard enough just to get the thoughts flowing. I was able to get out of the mental rut and put down a few good paragraphs. Unexpectedly Pages crashed. No issue there, it should just restore my document…Right? 

Lets pause there for a moment to note a few things:
1. In the time that I’ve started this blog the automatic autosave in blogger.com has protected my work every minute, autosaving some 15 times.

2. TextEdit, a very basic word processing program has an autosave feature backing up SQL code I was messing with.
3. Time Machine on my MacBook Pro has backed up my system 12 times since the start of today.
In our world of computing backups, redundancy and autosaving, being able to recover has become common-law! So it was in disbelief that I re-opened my Pages file to find that NOTHING was recovered. There wasn’t even an indication that it tried! Thats right…no autosave in Pages!
I won’t drag on with any more rhetoric on the subject. This isn’t a bash on Pages. Just a rant that the simple programmable things in life should never be forgotten. Autosave is one of them!
Command – S

“If you don’t measure it, you can’t manage it!”

All too often we encounter small business clients who feel their IT infrastructure is operating just fine. When asked, “how is your IT infrastructure working”, they roll their eyes to the sky and think back to their personal computing issues over the past week. The answer is often, “things are okay…I guess”.
Then it happens…
“My computer crashed!” 
“Are you able to get e-mail?”
“I can’t print, can you print?”
“Why is the internet so slow?”
“My home computer is faster than this.”
With almost inborn instinct the victims hit the power button and pray for normalcy. If the situation is not resolved with a reset and the frustration level is high enough, a call for support is made. Since these issues typically happen sporadically they are often swept under the mental rug.
But lets examine this with business basics – Time Is Money! If we chalk down the lost time of the underrated comments above into dollars, the loss would be startling. This is where a small business owner with limited IT support needs insight into their infrastructure with simple “Key Metrics”.
Key Metric 1: “How many times a week, month or quarter have I experienced an outage, failure or issue?”
Key Metric 2: “How long was each outage, failure or issue?”
Key Metric 3: “How much did this on average cost me in dollars and cents?
The metrics are no more complicated than 5th grade math class, but pack the same power as E=mc
If the financial loss because of the issues approaches 40% (for arguments sake) of the cost of the hardware, software, or service being used its time to take action. Setting aside a little effort measuring IT outages (among other things) can save a bundle. A small business owner can use the information to target potential system failure, plan for hardware upgrades and more important have peace of mind.