Job Documentation

This morning I started jotting down some notes about part of my job. This lead me to creating a more detailed list of different things that i do for example:
Linux Servers
– Samba
– Webmin
– etc

From each of the topics, my plan was to document what it does and how we utilize it. What do I do to keep it up to date and running. Then i hit me, why should i go through all this trouble? I’ve spent my must of my life learning about computers. Through books and hands on. Most of this stuff was not learned between 8 to 5 on the company dime, or on the company equipment. They have never even reimbursed a book expense. So why should I document how todo my job, just because I’m leaving and they won’t replace me?

If you were leaving your job, and you had a few months to go, would you document every detail for your company? I’ve got mixed feelings about this. I think my job needs to be documented so that someone else has an idea of what needs to be done, but I think thats as far as I’ll go. If they want to learn about NFS, samba, fixing network printers, hooking stuff up the AS400, working on CNC machines out in the shop, or whatever it will be up to them to figure that part out. What would you do?

5 thoughts on “Job Documentation

  1. I would say that a listing of responsibilities would be within reason. But a description of what’s required to complete those responsibilities is asking too much, unless it’s some proprietary technique specific to a system.

    Any employer should be able to lay that list out to a potential employee, and if that employee says that he/she can handle it, but can’t, it should be up to them to figure it out, not the company.

    My 2 cents…

  2. Chad is right.

    My two cents more…

    1. Create your consulting web site.

    2. Define your duties and perhaps measures of success.

    3. Create an internal site for your successor and her supervisor that bridges the two, through consulting you can offer, for training or mentoring you can provide, for packages of books selected and offered at a stiff premium (for example, “The 10500bc AS400 Bookshelf, what you should have at hand”).

    If you do much more, nobody will read it anyway.

  3. It’s the company’s responsibility. It’s one thing to be nice and lay it all out, but it’s quite another to bend over backwards for something they should have already done. Sorry, but I’m having a little job bitterness right now…

  4. I agree with Merrin. Its stupid to ask someone who is leaving to be “responsible” for that type of thing. Reminds me of when I quit my last job. I was responsible for documenting how to do stuff. Like I cared by that point!

  5. Don’t forget to document all the duties that fall under the catagory of WTF!

Comments are closed.