Others
There are plenty of other time-wasting activities that we can all manage much better. Hopefully the previous list has included a good sampling of work-related and personal time wasters to jog your memory and help you start thinking about the time wasters in your life that you can either manage better or eliminate completely. Of course, what's a waste of time for one person is an important part of life to someone else. Everyone is different.
Strategic Versus Tactical
For a system administrator, the ultimate time waster is any task that could be eliminated if only we had time to build the infrastructure to make such busywork go away. In other words, the ultimate time management technique for a system administrator is a good IT infrastructure.
Strategic tasks are those dealing with long-term planning, like constructing a security policy, getting buy-in from management, and deploying the policy. Tactical tasks are specific tasks related to a particular process, such as formatting a hard drive or installing a new PC.
The problem is that we get so caught up with tactical tasks that we never feel that we have time for strategic work. We're so busy mopping the floor that we don't have time to fix the leaking faucet.
You won't need to spend time handing out IP addresses if you deploy a DHCP server. You won't find yourself spending days fixing security problems if you have a modern and pervasive security program with things like automatically updating virus/malware/spam detection, self-defending networks, and policies that are supported by the highest levels of management. You won't spend afternoons debugging oddball Windows problems that turn out to be slight misconfigurations if you have an infrastructure that automates operating system installation so that every new machine starts out right. You won't spend nights restoring data from backup tapes if you have a server infrastructure that includes proper power, cooling, and redundant storage (RAID). (Not that RAID replaces the need for disaster recovery backups.)
The key is to make time for the strategic projects. Get them onto your calendar and schedule time for the individual steps in your to do list. My rule is to always have one strategic project going on. I'd like to have 50, but if I spread myself too thin, I won't get any of them done. It's better to pick one good project that gets done than to start 50 that never get finished. The advice in the section "Prioritization for Impact" in Chapter 8 will help you narrow down the project. Get consensus on which project will have the biggest impact, and get the whole team working on it until it's complete.
If you are looking for a good book on this topic, I recommend The Practice of System and Network Administration. It's more than 700 pages and very complete. I am, however, a little biased.
Summary
A time waster is any activity that has a low ratio of benefit to time spent. Rather than trying to do these activities more efficiently, it is better to try to eliminate them.
Certain activities can expand to fill all your time. You can snap out of it by setting a time limit. Make self-imposed rules such as, "When I start to do [insert activity], I will set an alarm to remind me to stop 10 minutes from now."
Nothing makes it easier to resist temptation than a witness. Sharing an office with a coworker can eliminate any inclination to do nonwork activities while you're at work.
There are many time wasters in modern life: junk items on the to do list, email lists, chatrooms, nonwork discussions at work, unwanted salespeople and recruiters, manual processes that could be automated, and so on. Once identified, they can be eliminated.
At home, you can manage time wasters better by using a digital video recorder to manage your TV, "videos to rent" lists and Netflix so you spend less time wandering around video stores, and laundry and housecleaning services so you have more free time for fun.
Learning to install something that will only be installed once has limited payback. For complicated installations like centralized backup/restore systems, budgeting to have installation done by the vendor or VAR can be a significant win.
For a system administrator, the ultimate time waster is any task that could be eliminated if only you had time to build the infrastructure to make such busywork go away. In other words, the ultimate time management technique for a system administrator is a good IT infrastructure. By thinking strategically, you can eliminate tactical tasks over the long term. In other words, you can stop mopping the floor and fix the leaking faucet.
Chapter 12. Documentation
This chapter is about how a good documentation repository can help us as system administrators, especially in our effort to manage our time better.
But first, let's talk about why we dislike, fear, and generally avoid writing documentation.
We're suspicious of anyone who asks us to document what we do because it sounds like the precursor to being fired. If we document what we do, we can be replaced. Alternatively, the request to have everything documented comes from outside our group, usually from someone who has gotten "ISO 9001 fever" and doesn't realize that documenting processes is a means to an end, not the other way around.
It can be very difficult to start writing a document. "Documentation" summons an intimidating image of a 1,000-page book describing everything we do, how it's done, and how things work. Where the heck would we start if we had to write that?
System administrators are often perfectionists. We could never document everything. Why start a project if it can't be finished? Because of the time it takes to write, documentation often becomes outdated during the writing. Why write something that will be useless the day it is completed?
Besides, there is always a line of people outside our offices requesting that we do urgent things. That's always going to trump documenting. Writing requires long stretches of uninterrupted time. No system administrator has that, right?
Lastly, geeks hate printed documents. Why kill a tree?
This chapter proposes something so different that I hate to call it documentation. Instead, we're going to make an information repository that is accessible, updatable, and useful. Best of all, it will serve our time management needs.
Figure 12-1.
Document What Matters to You
In place of big ol' scary documentation , what do system administrators need? You need repositories to store the information that will help you from a time management perspective. Your boss may have her reasons for wanting you to maintain documentation, but I recommend that your inspiration be something different—selfish. Build documentation repositories that serve you and your time management needs, not the seemingly irrelevant needs of your boss or quality department. Specifically, SAs need two repositories:
Customer-facing repository . Documents that you want users of your network to have access to, such as the policies and procedures they should follow to get service.
Internal IT repository. The info you need internally to help you do your job, such as contact info for vendors, written instructions for tasks, and so on.