Discussion Locked

DOCUMENTATION & JOB SECURITY..WHERE DOES ONE DRAW THE LINE?

0 helpful
25 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I'm sure we can all relate to our bosses standing over our shoulders or scolding us for not providing enough documentation or training materials for lower level support staff. The problem is not that we are not capable of writing excellent documentation, as I know I have excellent technical writing skills, but if we make it so understandable to the average person that even a chimp can do our jobs, won't that put our own jobs in jeopardy? I can understand the business needs of having good documentation and training materials, but where does one draw the line when it threatens his/her own job security? Many times have I seen people who give 2 weeks notice and in those last 2 weeks are forced to train and bring up to speed the new employee who will replace the person leaving. I've been in such a situation and my attitude was more like "they can go f**k themselves, they are not paying me to train anyone and training anyone was not part of my job description". If the new guy/gal they are hiring needs to be trained to take over my job, then they are not the right person for the job. Am I being too harsh and unfair because I value my knowledge and am not there to lecture people or new employees at my own expense? I've seen people who documented until they were blue in the face and then replaced by cheaper employees who used the "documentation" written by the former employee to do the same work. Our knowledge is power, and our knowledge cost us a good chunk of change and our valuable time. In no way am I going to give freebee training lessons to anyone. They can all go the same route I did and put down a few grand to send themselves through IT school. There is no such thing as a free lunch and no boss or manager can force you to offer other a free lunch.

25 replies

by tuffalan

The trick is to document at a level where some one who has done the schooling/training can use the documents and those who have not cannot.
I have no problems helping people learn new things, I believe should have a fair go, but that means they have to put in the hard yards.

by why me worry?

what if your boss/manager is still not satisfied and wants you to pretty much rewrite history with your documentation, explaining every technical term from the ground up? Imagine writing documentation on your Active Directory Implementation and also needing to devote 3 chapters on what Active Directory is and what are domain controllers and such.

by tony hopkinson

ADS -> Networking -> TCP/IP -> subnet mask -> binary representation -> solid state transitor theory. You can branch off there into sub atomic physics, quantum mechanics, string theory and the big bang if you want.
Should sort him out.

I love people like that you can get paid for p1ssing them off.

by diablo4555

This is a reoccuring problem, I am the only IT qualified person on site, my boss is a finance manager, she wants me to document everything in case I am off !!
Her level of IT knowledge is poor for eg. I am currently specifying a large PC rollout she asked me why we need Microsoft office if the Pc,s come with Windows XP ( she thought they were the same !!)
I am not adverse to sharing knowledge as this is how we all learn but there comes a time when you just cant share everything, I used the anology with my my boss and told her that there are things in her job that are second nature to anybody who works in accounts and they should know, it is the same for IT..

by leoxx037

If you are at a point in your employment where you are concern about your supervisor/manager replacing you, then it?s time to move on. The TRUST is gone, paranoia and anxiety is setting in, and the fear of ?possibly? losing your job is not worth the time.

by drmweaver

I've been in similar situations. On the other hand I've also been on the other side. I only expected a high level of documentation from my employees. This way, some newbie that had no training or hands on, would simply be lost. However, a person with skills would understand the documentation.

I am also in the situation right now, where I"m resigning from my position. My delima to give two weeks or one week. One week, there would be no time to train another person. Two, and they would abuse my knowledge and skills, keep me late into the evening, etc..

I've decided on the one week and be strong on the hours I'll put in. I'm also making sure that I NOT offer any answers, but let them ask them. If they don't ask, they don't get.

I had no training when I came in. They have since put a person above me that has NO IT SKILLS. and this person will fail. Not because I didn't help, but because he choose to take on a position which he has no knowledge of.

Hope that helps some.

by jamesrl

As a manager, I expect that there should be a "reasonable" level of documentation.

Training should be ongoing, there should be no position where only one person knows everything. Documentation is not a subsitute for training.

Having said that, technical specialists should be teaching, training, or documenting generalist knowledge. There are generalist books, courses etc out there, and its a waste of your time and effort to duplicate them.

What you should focus on is how things work in your organization. Another poster mentioned active directory - there are plenty of resources on active directory, no use rewriting the book, just document how and why active directory is set up and works in your organization.

There are technical specialists in my group, and I recognise their time is better spent on doing than writing, so I use some of our technical writing resources to polish their work.

I thinks frankly its selfish and counter productive to horde knowledge - presumably you learned or someone trained you - you will find the more you give the more you get. If you give training, you should be able to ask for training in return.

James

by jkaras

You make the right point. I hate all the its my information and they cant have it. Everything you know is given to you by professional people that made an investment in you to help their business. All relationships whether professional, personal, or what have establish a healthy give and take. It would be stupid to not have documentaion to protect the business, if you did something atrocious that got you fired then it had nothing to do with the documentaion.

I do conceed the point that documentation is aimed at removing the employee in counseling parameter. The boss expecting to define what the topic is in the documentation is wrong. It should be suitable for the basic understanding of what was done and why so assist others on the team to get up to speed. What the U.S. workforce is missing nowadays is trust between employer and employee with the what's in it for me mentality. We all want to be successful if we all make the investment it pays off for all.

by murr

Business Continuity is becoming more important and documentation for this purpose is needed. Documentation to comply with SOX and such is also needed. But it doesn't need to be that detailed, just enough for another Pro to take over....

But if your boss is going overboard on the matter, I don't have any good suggestions, but to maybe look for a better run company.

If they want to hire untrained people and expect them to survive with only your documentation, they will fail (as you said) -- let them reap what they sow.

by firefly1522

At my workplace, we have 2 types of documentation. The very detailed-so-that-a-trained-monkey-could-do-it type for very simple things that most people in the company have access to and then the type of documentation that requires that you have at least some working knowledge of our system and a security badge to get into it.

by paul.menefee

If your job is so simple that you can put it down in black and white and atriculate every step out, then perhaps, your goose is already cooked. A chimp could do it. I've run into this debate before but have found that real security comes with skill. Skills are learned details; things you can't put in text books. Your skill is that intangible part of your every day decisions at work. It's when you make a judgment call in a situation based on a gut feeling about something.

So identify your skills and improve them everything else you do can and will be eventually automated. (by programmers like me)

by sakuhara

Agree! Almost everything is documented already pertaining to AD, SUS, Exchange, etc. Don't get lulled into a false sense of security. Managers will fund an application or outsource to rid themselves of the attitude. Most is done today via GUI....The ones that build the GUI win! Learn or be left behind. Most importantly be able to pass those tricks on.

by onwynn

I am one of the lesser formally trained people being given an opportunity in the IT world by my company - an opportunity I might point out that I would not have gotten outside of the company as I carry no certifications, but do have 15 years+ hands-on experience with computers at a Technician's level. What I understand from the original statement from "rzan" is that my 15 years of hands-on is somehow inferior to the couple of years in school that someone else may have. How many of us have seen certified contractors or newly hired employees turn out to be nothing more than paper carrying idiots when it comes to the world of computers. I have worked in security, military, and factory and they all carry that same, outdated mentality that someone without credentials hasn't paid their dues - the simple fact is we've simply paid different dues, and we are no less worthy than someone who had the circumstances and money and time to fork out for a formal education. Can you see how it balances - it's taken me 15 years to get an opportunity, I wonder how long after schooling "rzan" began work in the field?
As to the documentation. I currently work in the automotive industry supporting computers for a multi-site computer network that crosses borders. Our requirements for documentation are clearly defined in our Quality Standards that all processes and functions must be clearly documented in such a manner that the work can be audited, quantified and tracked for improvement. It is also to be prepared with the intention of its as a training aid for newly hired employees as it spells out the standards we expect from our employees. Whereas I can understand the survival instinct to deny someone your "power/knowledge" in order to preserve what you've got, I personally would not want to work for a company that put me in that position. Loyalty only goes so far and my company will get from me the same in kind. Besides, anyone with the right skills, attitude, and drive will not want for a job for long.

by dggraham

Having worked in knowledge management, I have seen first hand how management can misuse the works of subject matter experts to enable the under qualified. However, there is another side to this that I am personnally now facing. My current employer has me performing tasks that are well below my knowledge, skills, and abilities. My efforts to advance are being blocked because "no one else can do" the tasks. Of course this is flattering, but it is also inaccurate. The only way I'm going to free myself from these mundane tasks is to train a successor which will include thorough documentation.

by jkowolf

How do you expect to get promoted if there isn't anyone who can do your existing job? Is it fair to your employer to pay you to work on a project only to have you leave or get hit by a bus and they have to start all over again?

I'll admit, I'm in a different situation. I'm the only IT person in my area, so there is no threat to take over my development chores. However, I am very quick to create programs for non-technical users to use so I don't have to spend a portion of my day running them (Reports, data imports, etc.). I get to move on to bigger and more challenging things.

by odongojuliuspeter

You sound young in your profession. This could be a test of integrity and an opportunity for your promotion.Better watch out.

Many people reason like you do but be reminded to follow the instructions from your boss or quit the job.

If it is the policy and organisational strategy to train and/or mentor junior staff in certain fields then you have no other option but to comply. Remember someone out there could equally do that job and very willingly.

Any resistance on your part may be interpreted as an indiscipline and/or a sabotage and that will definately not be taken lightly.

NB: Insubordination of your interest to organisational interest may not be tolerated.

Why not leave a legacy with the knowledge you have afterall this life is too short.

by xwarzbek

Even if you think you don't want to "advance" - what stops Sanjiv in Bangalore or Drago in Slovakia from documenting what they just wrote and selling that to the company? The company would then have an idea what they are getting for the money. If the only thing keeping you in the job is lack of documentation, there is a commercial company ready to sell your job out from under you. Your ability to document what you did demonstrates why you should be the one doing it.
Hey- Chimps don't document either. That's the reason not to hire chimps as programmers.

by jnoble9

It is standard practice for those of us that are experienced, to hire staff that we can teach, mold, and train to be our replacements.

If you think that information "starvation" is job security, you are myopic, and will have a hard time advancing in your career.

Knowledge that is not shared, is wasted.

by fshelpdesk

I work at a helpdesk and I strongly believe in documentation. I am happy to pass on knowledge, procedures and tips to others. (they can have my job!!!) Since so few people are willing to document I believe that it makes you more valuable to your employer and shows that you are willing to work as a team.

HOWEVER, I also think that if an employer hires someone with only enough knowledge to follow documentation, then they are getting what they deserve!

There are certain job skills and talents that can in no way be documented, passed on or taught to anyone in a short period of time. That is what makes a tech worthy.

by stephmeister

This is not about your job security. It's a requisite to document, not for junior level people to take over your job, but for business continuity, possible compliance with regulatory matters (SOX, SAS70 reviews, other audits, etc.), as well as good practice to see things are done right and consistently.

I'm an IT Manager and Disaster Recovery Coordinator. We have senior engineers that we have no intention of replacing... the good ones, DO create and maintain documentation. More importantly, they are key people we've come to rely on, and our "go to" people. If you're even slightly worried about your position, do the documentation and step up your performance a notch.

by frostbite

If there has been a study on the correlation between good documenters and job security.

In the organizations I have been, one of the things I have seen over time is the tendency for people who have been able to develop clear documentations to move faster in their careers. I think this can be attributed to (1) They can empower junior staff to do development the junior staff was hired to do
(2) They have more time to deal with the higher level needs of the business. There may be other factors as well.

I'm sure, for each success story there are also others who got stripped of their jobs after thoroughly documenting their work.

While I feel very bad for them, I think that developing documentation only plays a small part in it and bigger factors may have come into play.

by wtapp

It has been my firm belief and experience that if you can write documentation or better yet train a chimp to do your job then you are doing your job correctly. If you take the stance that this chimp will replace you then you are being a chump.
If you can find someone to do your job then you will have the opportunity to grow and add value to your organization, or someone elses. Think about this...Should your boss decide to hire the local college drop out for $20/hr less than you to do nothing more than use your documentation, you have something to write on your resume "...created process to save company nearly $50K a year with improved process..." You create your own opportunities at work. If you stick to your guns and refuse to write the document then you are of little or no value to your employer now, or even after he fires you and finds someone who will document the processes.

by humbletech99

If your job can be done by someone else, evertually it will be. Somebody cheaper, enter immigrants...

IF YOU ARE NOT A SCIENCE/MATHS PERSON, YOUR DAYS IN IT ARE NUMBERED, I GUARANTEE IT.

Now, I've just documented our network thoroughly, but that only tells people what is where etc. If your don't know the servers, security, networking, etc etc, you don't belong it IT and you won't find my documentation of much use (although it will save stacks of time deducing things which i what it's supposed to do).

I can understand the resentment to teach, because this allows inferior people to try to shortcut and cheat their way to higher knowledge - not earning knowledge leads to its abuse and degradation. This same goes for paper certs. However, worthy people should be mentored and I would mentor someone I deem to be good enough (but that already cuts out 90% of the people trying to do IT).

People who don't spend all their free time learning, buying (& reading!) expensive books and gear, practising, experimenting, qualifying etc. will not be able to compete with the hardcore guys out there who will chew them up. Problem is, IT doesn't pay enough any more to justify that, but it's still expected.

At the end of the day, we need more intelligence, more hard work and less average people trying to do this specialist field.

This discussion is closed to new replies.