Procedures

Writing a procedure is an art. Why? A procedure must be written in such a way that a junior-level analyst can understand how to configure a piece of technology without prior knowledge. Many times when a procedure is written, it leaves out key pieces of information that are needed to configure an IT resource. This can become frustrating to the employee who is required to configure something or fix a problem.

Would your team know how to resolve an issue if you or a senior employee left to go on vacation? The point of writing a procedure is to write it with so much detail that it does not leave anything to question. A procedure should have each and every step discussed to the point that what to do and how to do it is completely unambiguous.

I used to teach Linux classes at a community college, and I thought I had it all planned out. You see, we allowed our students to check out external hard drives for use during the semester. These hard drives were used to install a...