Comments on: If you can’t script it, use a checklist

By: Matt Simmons

Matt Simmons — Mon, 13 Jul 2009 10:59:21 +0000

Hey Michael, great comment. You’re very right in that we’re ALL the “current jerk”, and that we need to document for those people who come after us.

It sounds like the checklists really worked for you in that position. I’m hoping to get some more going here, too. They’re too handy to ignore.

By: Michael T

Michael T — Mon, 13 Jul 2009 10:55:32 +0000

I created (as opposed to caused) a check list to be created in a support environment where the one sheet checklist was completed and initialed by the next support character in a pager rotation and became part of the audit material available to customers. It had some of the dumbest little things on it such as "Have spare battery." It seems stupid but I can assure you that it made a HUGE difference to the person who had to initial it that they knew, without a doubt, that if they initialed it and didn't have the battery that everyone would know and no one could say I forgot. And you also knew that the customer, during a post-mortem, could ask for proof that we did the right things and hadn't screwed up and that this documentation would be produced with our names on it. Tweren't anway way of getting around it. On another note, I learned this about documentation. I always griped/wished/complained that the jerk before me thought of the next guy and provided documentation. It was then that I realized that while I was "the next guy" there would always be a next guy and I was the current jerk and it was my responsibility to document things for the person after me!

By: Steve

Steve — Fri, 10 Jul 2009 03:46:55 +0000

That’s really good. I like that, and I will gladly steal it Thanks!

‘Tis not theft, but a long term loan.

By: John McGrath

John McGrath — Thu, 09 Jul 2009 15:59:09 +0000

When I write a script/Setup Document/Instruction document, I will screenshot the step, and make notes about the step in our template.

In this way, who ever comes behind me can use the document to install and configure the software/hardware/OS the same, and if the process requires validation, we have a known good procedure.

By: Matt Simmons

Matt Simmons — Thu, 09 Jul 2009 14:54:57 +0000

@ToddT: That’s really good. I like that, and I will gladly steal it Thanks!

@Dusty: Yeah, that’s a problem with the blogspot redirect I’ve got going on. I need to spend some more time making it work, but I don’t have a ton to devote to the blog right now. In the meantime, please accept my apologies, and feel free to search at the top. Alternatively, the archives are fully browsable at the right, if you use the URL to determine the date. Sorry it’s so difficult right now.

By: dusty

dusty — Thu, 09 Jul 2009 14:21:25 +0000

Hi. I am browsing your “Redhat Clustering” write-ups — and notice a problem:

Whenever I click a link in your blog to take my browser to a story, such as this link, it then redirects me away from that page to the latest and greatest entry.

I would really love to read that link, but alas, cannot seem to get there and stay. Bugger.

By: ToddT

ToddT — Thu, 09 Jul 2009 14:16:35 +0000

First, I love your blog. Second, I have to add one more maxim to your arsenal.

” Document what you do.” and “Do what you Document.”

I learned this one when I transitioned from sysadmin to IT auditor. Many of the shops that I audit, maintain the documentation for the auditors only. No one else updates or reads it. Half of the issues I find are personnel not following the procedures outlined in the documentation.