48 replies
by cmiller5400
by redsgirl
Does the guy know what he's doing in his job. I've had plenty of sys admins who are, to be frank, incompetent.
They usually cover it by keeping everything to themselves so that everyone thinks that they are doing the best job possible.
Not an easy situation to deal with.
You may find to be fair that he just thinks that too much information may overload you and is doling it out piecemeal in an attempt to keep your learning curve at a reasonable level.
by sully
by jdclyde
He is feeling threatened by you, and there are many ignorant people in this field that will try to hord knowledge to either make themselves harder to replace or to make everyone see how grand they are because they can do what no one else can do.
"Wow, you did that good. Think you could show me that sometime?"
"Was wondering what I would have to do on the days that you are on vacation, could you give me a hand please?"
also, you can talk to him in neutral terms that change it from a blame game to a request that it is intended for.
"When you don't allow me to finish a project, it makes me feel like you don't trust me. Is there something I have done that would make you feel this way?"
I went through something like this, but it wasn't technical knowledge being with held because I knew more than the admin at the time. She still thought I was trying to take her job, not realizing that there was so much work to do that she was not able to do what she was doing well because she didn't have time. Everything was done poorly because of having too much on her plate. She eventually was able to hand off half of her responsbilities (she picked what she wanted and I got the rest) without a pay cut of any kind.
It did take a long time though.
by jdmercha
I just recently hired a new and capable person. He may look at me as hording information too.
From my perspective there is just too much information to give to him all at once. So I dole it out as it comes up. But then it is difficult to keep track of what I have told him and what I haven't. So basically, if he doesn't ask me for the information then he doesn't get it. Although he hesitates to ask questions sometime, because he'd like to figurte it out himself, he does ask questions when he feels he needs to.
by redsgirl
by pkr9
I have stepped in as sysadmin or operator as it was called a while back, and seen the same situation. Now I work with managing and consulting so I know this from both sides. No matter how competent you are, there's always special things to learn in every installation.
It's a good idea to meet on a regular basis, say 15 min.s in the morning and 15 mins at the end of the day, to sort things out. Also a weekly status will be a good thing. If you don't organise things, you'll be doing firefighting all the time. Curing the symphtoms but not curing the desease.
As he(?) obvioulsly has it all stored in his head, this would be a great opportunity to do the documentation that obviously is lacking, otherwise you would be able to read what you need to do. By doing this you will learn, and he will do the company the big favour of doing what should have been done long time ago - ensuring that the company will not go bankrupt in case he gets hit by a bus.
by davedxb
One of my clients who i was offering my services too hired me. He needed a IT Support guy for a small company, and i was fresh out of college, spent 10 months doing volantary work (free).
N ways...i had no knowledge what so ever of
routers
web servers
email servers
internal network servers
etc
He hired me...thing is i didnt have a senior IT member to take care of me...It was just me...
6 months later....i had ppl
yell at me
hate me
talk behind my back
was fired for 3 hours lol
An right now im currently managing
2 internal network servers
1. fax + file server
2. ISA 2004 firewall
wirless routers
and 1 internet web hosting linux server for 3 companies.
website
email
So....i think it was cool...i think u should stay strong and take it..in a proper manner that is. Be tough, one thing you need to show them is your learning...and your gradually taking a stance.
by drremer
As a manager of WatchBlog.com and president of Vote Out Incumbents Democracy, an all volunteer organization, and a psychology degree, I recommend a straight forward honest approach. SysAdmins tend to be results oriented people, appeal to that trait.
I would say something to the effect, "I am able and willing to learn much more, so that I can be more productive in my position. But, without guidance and direction from you, I don't feel I am maximizing my potential for your goals and objectives. Would it be possible for us to carve out 10 minutes of uninterrupted time once a week or, every two weeks for a short while, so that I can pick your brain and get your feedback and direction on how I can increase my abilities and skills toward our common objectives."
It is a straight forward approach. It is complimentary but efficient in seeking what you are looking forward. Most people find being asked to coach or teach one of the highest compliments they can be paid, provided it does not interfere with their own agendas.
David R. Remer
by sully
Mike unless you know this manager or this woman I suggest that you be more genuine and realistic with advice. We don't often mean to sound like we know everything but sometimes it slips out and craps all over a great argument. You were spot on with "Think in terms of HIS needs, wants, and desires and..." It's got to be about HIM and his agenda. When we become bosses we gain that perspective by default and we have to maintain it or we loose.
You should certainly not "confront" your boss, you should do what you are charged with doing, you should definitely use your off time to learn more (it's almost an unwritten rule to do so as the research $$$ would cripple any business that tried to pay for all that needs to be done).
Just keep being the best that you can be, vent when you need to and vent to the right people and don't worry about it, go there do the job, dive into the research, and win.
by jaco
Hi redsgirl,
A1. we as it pro's learn with our eyes.
A2. when youve reached his level of experience you can confront him.
A3. use your eyes.
redsgirl, for some unkown reason employers seem to think that Sys-Admins grow on trees, on your way in becomming a SA you will find that there is no help or gratitude, and on top of that you have to put up with stupid people that should actualy not be allowed near a PC. The nice thing is that whatever you achieve becomes your reward (its the best reward you will ever experience). My advice..
I am the SA to approx 60 Companies - at every single one there is always a problem that keeps on comming back - Find the solution, suggest and assist YOUR SA in solving this problem, and you will be the best thing since Linux....
Regards
by damian
Sorry this turned into a book...
When you find yourself as that 'that help' and not able to obtain the relevant information to perform your new duties - what can you do?
I think most of us have run into this situation at one time or other and when it's your senior who's not willing to make time for you, it makes it a little harder progress.
It is not uncommon that a Sys admin who's been running his own show for X number of years, screams to his boss that he needs help, which is why he keeps missing deadlines or making errors in his work (not always the case, some are just unbelievably organized and good at what they do).
There is no 'one' right way to approach this, but here are a few things that have worked for me in the past in a similar situation:
- 1st off sit with the guy and try to agree areas of specialism or ownership, after all he hire YOU for a reason. In the beginning this might be the dog's work, but start efficiently while you have time and begin to document processes and create mini road maps for changes upgrades etc that you can present.
- You have now demonstrated to him your competence, begun the tiresome task of documentation which he has obviously not done previously and more to the point started to learn the environment to a detailed level.
It's not exciting stuff, but calculated and reliable.
Things that I see fail:
- Sit and wait for it to come to you. It may never come
- Complain about the situation. You'll alienate the single person who you needs help - yourself.
- The Adhoc route. You want to work, help out and make a difference, but you have no idea how anything is setup= You are most likely going to break something that has not been setup in a text book manner and really annoy, well yourself amongst other people.
I hope this can give you some ideas how to move forward, Oh and congratulations on your new position by the way.!
by jamie
Your new in your job. Your a bit stressed because you've got a lot to learn. Possibly your stress is causing you to percieve the Sys Admins actions in a negative way. He might be unwilling to give you the vulcan mind meld and transfer all of his info in one hit because he doesn't want to fry your brain.
Who does the Sys Admin report to?
Can you organise a formal meeting with the Sys Admin and discuss with him what is gooing on?
Make a skills matrix for your position and work out what areas you need training in, possibly give yourself a rating out of 10
eg Disaster recovery 7
Database admin 5
Various other applications used by the organisation
etc
You then have a knowledge shopping list that you can use to bolster your skillset. The internet is a pretty good source of information. For the applications used within the organisation try to ferret out some user guides, or possibly chat with some of th end users.
Best of luck
Jamie
by reyoung3
Have you thought about asking for the help you need nicely via email? Thereby creating a documented trail for you, in the event you need proof you have asked for help. Just a thought.
Richard
by larry.gerlt
When he assigns a task
a. If you have not done it before, ask for complete insturctions and his assitance in performing. Explain you want to ensure you do exactly as he wants it done. If the task has been documented, print a copy to use and made copious notes about any item that you're not 1oo% clear on.
b. Ask him when he wants is done by. Immediately, by 2PM, the end of the day, etc.
c. If you have other tasks pending, discuss priority of new task - where does it rank for completion on you task list.
by careerdad
First of all I wanted to say that I really enjoyed reading this thread as it seems as if everyone here is genuinely trying to help. All of the answers have their merit and are all good advice.
The only think I didn't really see here is that you now have an opportunity to train yourself to become better at your job. It's obvious that your new boss isn't putting much pressure on you as far as accountability, so why not take the time to familiarize yourself with the technology? Go ahead, surf the web, look up and research the technology that's specific to your site and like one other gentleman said, rate yourself on your strenghts and weaknesses and bulk up on your weaknesses. This will make you a more well rounded tech and individual as well as make you more valuable in the future.
I've been in this situation, in fact I'm in it now! Everyone wants to feel wanted/needed but if you have this opportunity then I think you should sieze it. Trust me, the time will come when you too will be so busy you won't have time to train!
Sorry didn't mean to turn this into a lecture. Good luck.
by crousseau
by laduerksen
Being an IT manager since 86, I interview many candidates for hire.
My most favorite question to ask is:
Just a couple days after being hired, some one reports that a critical system is down. You're the only one available at the time and it must get back up and running. What do you do?
Best answer ever received: "Well there's got to be a manual, documentation or something somewhere."
Worst answer ever received: "Your gonna send me to training aren't you?"
The person with the first answer was hired and is now running his own business. The second person I never saw or heard from again.
by scottba
I am a Sys Admin and have hired a new assistant. While my assistant is very good there are still things he needs to learn. The problem that we have here and I am sure in most places is that there are more things to get done than is possible somedays. I would love to teach him everything I know, but there just never seems to be time to do those things. My advise to you - tag along and ask tons of questions. After you watch him do a task look it up on line and learn about it.
The other thing to keep in mind is that maybe he isn't teaching you everything he knows because sometimes we just don't realize everything we do as it becomes almost second nature.
Keep trying and best wishes
Barb
by vernonhorn
by scott
by uveses
hello... I think the roblem you have all boils down to a personality issue (the sys admin's that is). Some people are really like that, it may be due to a lack of confidence in themselves figuring that you may get better than them, or maybe the fact that you are new is causing the sys admin to give you that hard time.
A possible approach to this would be to calmly and in a diplomatic way mention that you are interested in learning more. You could also try to research the issues you may face (technical issues) on the web or in books to reduce the time it may take you to resolve them. Also if I'm reading correctly, the sys admin is a male and you r a female, if this is correct it shouldn't affect the professional relationship but it may be a possible cause.
My overall suggestion is try to do some reading on your own, this is usually common for persons with little experience, try a few things on your own and surely youwill soon become a force to recon with the the IT world.
by jack-m
I didn't read all the replies you got so if I'm repeating anything....sorry.
Some things you might consider, 1) he might be afraid that if he teaches you everything so you can take over when he's on vacation, off sick, etc. HIS boss might think he's superfluous and if you make less money he'll be replaced. 2)he might not be a good teacher. Often it's easier to do than to teach. 3)if you learn everything he knows about this job you become his peer rather than his assistant and just might outshine him. 4) finishing jobs you start might be his way of showing you how smart he is.
Some advice, learn on your own all you can. Take responsibility whenever you can. If you act like you know what you're doing you'll be treated that way. Take every opportunity to let his boss know you're eager for more responsibility and to learn more. DON'T badmouth your boss to anybody but it is OK to express concern that you aren't learning as fast as you would like, that you are ready to do more, take on more duties. The things your boss doesn't like or want to do you should make an area of your expertise. If you're in a small company you need to be careful and go slow. If it's a big company you have more room to expand and freedom to try and improve your situation.
If after a reasonable amount of time you might want to approach a higher up and ask for a revue of your performance to date and that would be the time to let them know you feel stymied and want to advance, there or elsewhere. Good luck.
by beoweolf
Not to be dismissive or characterize all new hires as self serving. But... you saw that coming... Out of the last new hires or recently promoted candidates, there seems to be a reluctance to get educated the old fashioned way - read up on the subject, practice on an unused server (at home if you have to).
Expecting "pre-digested" education is not the way to impress the current "Alpha" administrator.
Sure, if there is a lack of documentation, you have every right to ask for the run book, if there isn't one, the offer to create one, with the admin's help. By help, I mean suggest a format, document some of the simple stuff that has been turned over to you, then ask for a review of the document. As mentioned in an above post...schedule 15 - 20 minutes of time before the work day starts to get some uncommitted time for the review. When you show you are willing to get into the "trench work", it makes it a lot easier to hand over some of the "Glamour" jobs.
I've had new hires that wanted to Cherry pick what they wanted to learn as opposed to what I needed them to learn. They would rush through backups and restores, with scant attention to what was really being backed up (you need to review the reports to ensure errors are not occurring). Then complain when they want to learn how to rebuild or restore an Exchange server (cluster). The net result being that a job that takes an hour, ends up stretching into 3-while the users are complaining, whining and forming into the expected knots of angry villagers ready to storm the castle.
Want to ask questions, be afforded the respect that you "think" you deserve? Then Show up, shut up, listen more than you talk and keep the villagers out of the managers? hair. Every time a "simple" task, one that has been delegated to you is found "lacking" - whether or not the manager says anything about it - your "worth index" suffers. [Worth index: Bother vs. demonstrated Brains.]
No manager/administrator that I know of will hire someone just to keep them from learning how to do the job they were hired to do. Where the discrepancy occurs is when what you are/were hired to do, conflicts with what you want to do. If and when you are on solid ground for what you were hired to do...then its a lot easier to turn over more to the new hire. Just because the manager hasn't called you in on the carpet to highlight each and every mistake you have made, doesn't necessarily mean you have met and exceeded all goals.
There is something that is keeping the manager from raising your "worth index"...spend time to find out what it is; personal note: I've had new hires that complain about not being given enough to do. Much of what is needed to learn is imparted on the fly, it isn?t always marked by a pause and an announcement, and much of what is learned on the job comes from experiential observation rather than a formal declaration. Even when some new hires ask for help or to look over your shoulder while you work over a problem; they have no notebook. In the OP, I see no mention of whether or not manuals were read or review of notes taken? Nothing is worse than having to go over the same ground that was covered just days before. Agreed few remember everything, that?s why carrying a notebook - especially in the beginning stages of new position, shows a lot of respect. Then when you need a refresher, you can refer to your notes to find out where you went wrong or where you were given the wrong information. It?s a two way street, come prepared and it shows that you are serious about the job.
Hint: good notes are a perfect beginning for creating a "run book".
Maybe he just has a hard time 'letting go'. If he has become attached to these systems, or feels a strong personal reponsibility for them, he may just be finding it difficult to let go and move on.
Or maybe he is worried about dumping 'busy-work' on you, or giving you more than you are comfortable with.
I just throw those out as other possibilities, which would fit with your observation that he is nice. It could be he is a geek become manager, and is very much out of his element in trying to handle delegation and such.
As to what works in this situation... Patience. Look for opportunities to help, and keep soaking up the bits as he divulges them.
by pmshah9
by big ole jack
by ibanezoo
I finally got a new person to help me out and back me up, someone similar to you. I too give projects but I refuse to complete the projects for the new guy. I like to see not so much his specific knowledge of things, but more his work habbits and ability to gain the knowledge required to complete a task. I do try see both sides of the coin though, and I'm not sure about the specifics of your company. You need to learn, but the work also needs to be completed. Fortunately for me I can dictate timetables most of the time, your company might not be like that with deadlines.
One thing I do is narrate alot of what I am doing if it is something new to the other guy. I know every detail isn't going to be remembered, but hopefully the main points will stick. And when they are required to do it themselves I assume some things will be forgotten, which will require research and the possibilty for a better solution, or if nothing else a deeper understanding than I have the time to give. Maybe you can ask your sys admin to do something similar.
Ask for specific projects, and I hate to say it but be careful asking a million questions. Sometimes my mindset is that if I am just answering all their questions, that means I can't concentrate on my own work. I could quickly do their work and mine and be done with everything. When you are already understaffed it makes for a difficult situation.
Something he may be afraid of is that you are going to do something different and change something he thinks is perfect. I admit I am guilty of this myself but am learning to embrace it with the knowledge that if they do something better, I am still there to steer them in a way that works for everyone.
Dunno if this helps but hopefully you can see it from the other side a little bit. Careful with the word "confront". The last thing you want to be is confrontational.
by allreal2g
by server queen
Don't be afraid to ask him, "What did you have to do to fix that? What was actually wrong?" and keep notes. The #1 thing most of us who've been doing this for a million years are bad at is passing that knowledge on to others, whether through documentation or teaching. I'm guilty of it myself. I'm not a particularly good teacher (I'm not a people person), and I am slovenly about documenting things. So when my junior sys ads need to know things, they have to actually ask me. If they run around pretending they already know everything, then they won't learn until it bites them, because I'm not particularly good at going out of my way to teach them unless they ask.
Some sys ads are too arrogant to ever say the words "I don't know how to do that" or "I don't know what that means" and those sys ads tend to be the ones who are snotty when junior techs use those phrases too. You actually earn a lot of points with me by not being afraid to use them, because if you already think you know everything, your mind is closed to learning. The #1 thing I look for in a junior tech is curiosity about how I corrected a problem - FOLLOW UP.
His time is probably very limited - mine is - and training seems an imposition on an already overstressed schedule. Start by taking over the simplest tasks - backups, for example. Experiment with minor file backups and restores until you can take over that from him. Take over first-level troubleshooting on servers from him - volunteer to go out and look at a downed server so he doesn't have to, and fix the minor problems. Ask if you can take training classes, and keep your notes from the classes handy.
by beoweolf
Most Administrators are very aware of smoke and mirrors...you pick it up quick when taking to users who swear they have changed nothing, purged nothing or never opened their computer - until you show them the data trails listed in the system log or crack the case and see mysterious recent finger prints in the dust.
The best way to impress a manager is to do your job and step up to the line when you screw up. Coming from desktop support to LAN/Network operations is as different as playing video games is to designing them. Once you pull back the curtain, the whole world changes. Remember the Matrix - "red pill or blue pill" ... if you have or want to keep your illusions, don't take the (reality) pill! Obviously its the managers fault.
No matter what happens, the system admin is always going to catch the heat. If you can't convince him/her that you can be trusted, can follow directions and when necessary...think on your feet, then you are not giving off the right "vibes". Its the workers job to earn respect, not the managers to give something that hasn't been earned.
I still say, if you are not getting more responsibility, don't ask why the manager is holding back, ask why he doesn't trust you enough to do the job?
Some jobs are pretty easy to B.S. through, but there is an "Art", as well as processes and procedures, to successfully running a network or system. For example; you learn troubleshooting by going thru a series of logical steps and checks...but once you have experience, you can often skip a step or two - if you know where the likely bottlenecks occur. You don't get taught that...you learn it by doing or by being around those that already know how, when and where. If it were only about desire or strictly by recipe...we could just hire every college grad or certificate holder without regard to resume or demonstrated ability. But it isn't, you still need to prove to the manager than he will not be spending too much time explaining why an employee did or didn't do something they should or shouldn't have done. After all is said and done, it really is about trust. Smoke 'n mirrors only works when no one is watching closely.
by jmyers
Did you get hired as an intern? The last I heard, people get hired for what they can offer a company, not the other way around.
Despite SOX compliance regulations running rampant throughout many organizations, the true techies out there (including myself) don't like to teach others or document their work. If you've been around as long as I have then you remember what it was like to be the only one who had a clue. This was before the MCSE bootcamps came around so people actually had to learn by doing.
My suggestion to you; learn on your own time, confront him if you want but if it was me, I'd have to "let you go" and last but not least, find a job in the publishing or media industry.
Signed,
Old time geek
by tspevak
"My suggestion to you; learn on your own time, confront him if you want but if it was me, I'd have to "let you go" and last but not least, find a job in the publishing or media industry."
There are several layers of problem here. They don't automatically all point to the newer person here.
Under normal circumstances, employers hire people and train them to do a specific job. The candidate should bring a basic skill set match to the position, but most companies would try to build on that skill set to make that employee more effective at their position. Time is usually given to the employee to build that skill set, and probationary periods are established to catch the major problems. If this person is still an employee after a year and a half, I am assuming that the company acknowledges that person's value as a worker. Full-time, part-time, interns, and seasonal employees should all be shown how to do what is expected of them at the start of the job. If employers invest time and energy into getting new employees, they should probably invest time to keep employees, too.
I am not sure what the SOX compliance has to directly do with this employee. There isn't necessarily a problem with the Sys Admin doing the core stuff, but not every facet of network administration involves SOX. Besides, she's in IT; she will eventually have to be involved anyway with the data, especially if her skill set grows. If the Sys Admin doesn't want to share information, it sounds like it could be any number of obstacles. Fear of being replaced, inability to work with others, unrealistic expectations, passive-aggressive behavior against an employer he is trying to get back at for whatever reason, fear of being found out, lack of trust....take your pick, it could be ugly. It may not even be any of this, but the bottom line is that she isn't learning anything. It could be the Sys Admin agenda taking over for the company agenda. Something is not right here, though.
The solution isn't to target her. The solution lies in addressing the issue head-on. I think she still has a few options. I think she should politely confront the issue with the Sys Admin. Present things in a "Look, I really need to know exactly what my role is here. Can we go over/fine tune my job description?" talk. I wouldn't look to blame anyone or anything, just present things in a "let's get to the bottom of things so it can go smoother." Throw in a simple, short confession that you aren't after anyone's job. You just want to be ready, in case the Sys Admin is not around.
Unless the guy is completely closed off to working with her, things should improve. If not, I think she should set her sights on leaving the situation as soon as she can. Burn vacation time on interviews...and get out. Oh, and one unfriendly Sys Admin isn't necessarily a signal to change careers...well, at least not for her.
-Drewster
by big ole jack
by big ole jack
train for skills
I'm sure you would let him go...
Your attitude sucks
Signed
Old time geek
by mr_rc
I've been in my job now for just on 6 months, but my first few weeks were just as you described. I never got the chance to finish anything I was given.
I have no problem saying 'I dont know how to do that' if I dont, or 'I have a vague idea, I'll give it a try'. Which he seemed to respect, not criticise me for.
It was the Friday of my 3rd week (of pretty much doing nothing) that he came to me and told me that on Monday a new router was coming in. I had to upgrade it, configure it and get it sent to a new site.
Well, I'd never configured a router before and I told him so, but I asked what make and model it was and said I'd research it on the weekend. He gave me a funny look (which I assumed was because I didnt know how to configure a router).
Monday comes, he dumps it on my desk and walks away, doesnt say anything. I figured that I must have said something wrong, but went ahead with the configuration as best I could. There were 1 or 2 points that I needed his input (setting up a VPN) but otherwise I got it all done to his satisfaction.
It seems that rather than annoying him, I impressed him by 'going the extra mile' and using my own time to improve my skills. He deliberately stayed out of my way and left me to it as a 'test' to see how I dealt with unfamilar territory. I passed.
Since then he has been a lot more open and willing to explain things, sometimes in detail, sometimes not (research time for me) and I think a trust has developed between us.
You probably think I've gone off on some weird tangent here, but my advice is this:
1. Be honest about your abilities.
2. Demonstrate your willingness to learn what is needed by 'going the extra mile' and learning for yourself.
3. Dont be afraid to ask for help (BUT ask for help, not for them to do it for you).
4. If you know he has to do some crappy task, volunteer to do it 'so you (meaning him/her) can concentrate on more important things'.
5. Document all of your own work and put it forward to them for review, it not only shows them that you are learning but also helps you learn as well. (I documented domain profile migration, he didnt tell me he had it documented but he is now using mine as it is more 'user friendly' and stepped out clearly.)
Hope this helps...
Sometimes you run into people like that thinking if I keep this info to myself I will make my job more secure. I have worked in the same sitution for 19 years now. It's difficult but !!! eventually you will find someone in upper management that discovers what is going on. what he is trying to do is show others how smart he is a you are the studge. I have lived this out & as he had control of the budget he makes purchases of the wrong material to do a job and when it don't work he covers it up as the technology isn't quite ready for all this. My only conbat for this is to stay well informed, study your equiptment (PC's,Netword) & begin to show that you can see inside all this as well or better than he does. It's hard to beat a well informed, well studied person down & eventually you will find that that he don't know as much as you or he thinks he dose. I know you can do the job and you do as well. The trick is to show everyone else that you can do it.
DO THIS :
Know your network like the back of your hand.
Know the PC's and operating systems same way.
You will finally get to know the system you are working on as well or better than he does. Don't share anything that you do as well. Let him try to keep up. Look for slow downs with users. What do they need, Keep all up to date as well as you can.It will come to the day when he is wondering just how you have done what you did and how you corrected the problems.
Do this.
Make a list of your weakest users.
provide them with as much help as possible.
Help desk calls come from these people, how do I connect to this printer, how do I map to this drive. Where I work this is about the top two of problems we run into. People can't find files or can't print where they want to print. That is what I did. Write a script for each user that quickly connects each user to the printer and drives that they need. Place it on there desktop. tutor them how to use the scripts and soon that part of the problem will go away. Now you have time for other things.
hope this will help.
tom
by ree_ree27029
RedsGirl,
First, I will not hold it against you for being a Reds fan. I am an Astros's fan for life.
Second, after reading your post and all the replies, there is a lot if information here to sort through. IT would appear that your current predicament is a common one for newbies. Wether this is a sad trend in the IT world or a generational thing is yet to be determined. looking back at all the post, there are few common ideas that you should take from allof this.
1. Be honest - never lie about a skill or claim you know something you don't. That will lead to reprimand or worst.
2. Don not be afraid to stand up for yourself - ever.
- If you have an issue with someone, the first thing that needs to be done is to speak with this person privately about the problem, no matter what they have done to you. As hard as it may seem this can solve %90 of social issues with colleagues. If that does not solve anything, then go to your superior.
3. From a technical stand point. Do not hoard information.
- It is important to document and share information. No matter how trivial it may seem. This will radiate a "teamwork" attitude from you to the rest of the group or your superior.
by aa8vs
Since he hired you, see if you can get a meeting one on one and make some suggestions of what you want to be doing/ learning in six months, 1 year, 18 months, and 24 months.
See in his mind how does that track with what he has in mind for you. Get some input from him as far as your career plan and how you can best support the organization.
Offer suggestions, gather input from him and then plan out your next 'review' period, say a year and see how that goes...
by redsgirl
you all gave me some GREAT advice thus far. as a newbie in this industry i sometimes find it hard to 'find my footing' as to how to handle or do certain things. you all have given me a 'head start' on how to handle this situation and also on how to handle myself in future situations. also, a few of you gave advice on increasing MY OWN knowledge which is not only helpful in THIS situation , but helpful in siutations to come, no matter where I go from here. i know this sounds corny but i truly thank all of you for your advice! (because i (1)didn't think anyone would reply and (2)if they did i thought i was going to be told to figure it out for myself/ stop whining...etc)
thanks again everyone.
-redsgirl
by big ole jack
by lclaire
Dear Redsgirl:
First of all, I've read all of the posts; keep in mind that none of us has the "right" answer for you. All that we can offer are opinions - follow them at your own risk.
There are no perfect places, just perfect niches. Work at Disney World if you need warm fuzzies. No one is going to give you want you want - unless you're Paris Hilton. It is up to you to control your career path and your destiny.
As you gain experience, you will begin to develop your own unique way of dealing with specific situations. You will find that many of your assumptions about how a "good" manager "should" behave just doesn't fit what you may have envisioned. So here's a reality check: start acting like a professional and your boss might start treating you like one.
You are brand new...and you are whining already? Grow-up! If you don't like something, change it! Take charge of your situation. No one likes a whiner. Whining gets nothing accomplished, it annoys people and usually gets you fired. I'm sorry to say this, but you are also feeding into the stereotype that women can't do the job. Maybe you need to be doing something else.
I'm a female with 2 masters degrees and 25 years of experience. Sink or swim, it's up to you. I don't mean to sound unsympathetic, but you accepted this job, right? (That is, you weren't conscripted into indentured servitude.) So, what's the job description? What did you agree to do? What are your responsibilities? What are your goals and milestones and how will your performance be measured?
You said the Sys Admin hired you, so he must have had some idea about how your experience would fit in with the job. When you accepted the position, you should have had some understanding of what you would be expected to do, right? If you haven't already, figure out what is "reasonable and customary" for the position. What is your job title? If you haven't already, develop measureable goals for your first six months (i.e., document certain processes, organize something, reconfigure something, etc.) Don't bite off more than you can chew; be realistic.
Ask the Sys Admin for a sit-down. Present him with your ideas about what you think your goals should be and how you can best fulfill the requirements of the position. Identify your areas of concern, offer your solutions and then ask him what he thinks. Find out what he would like you to accomplish over the next 6-12 months. Produce a well thought out document as to how you see your job responsibilities unfolding; you both sign off on it and it goes into your file. At review time, you get judged against what you agreed to do. Establish Monday a.m. meetings to discuss priorities for the week; establish Friday p.m. meetings to determine if you have accomplished what needed to be done. The point is to help your boss help you.
You are too new/inexperienced to "get around" this situation by going to a higher-up; that's a recipe for getting fired. And you shouldn't be confronting your boss, either. Confront him...over what? That you don't know how to do your job? One confronts a bully on the playground. One confronts someone who is harassing you. You don't confront a boss over your lack of performance. You need to be a team player, not a trouble-maker. When you are asked to do something, respond by asking (in a respectful way) what the deadline is for that particular task. If you don't think you can do it, be honest and hope that you don't get let go because you can't do your job.
Regardless of how you feel about this guy, leave that at home - he is not supposed to be a buddy, he is your boss. Be a professional and only deal with him with respect. Whatever you do, don't complain about him to the end-users - you will only make yourself look unprofessional. Be warned: say negative things about your boss and you can be assured that it will eventually get back to him. Attitude is everything; if you go in to work every day with a positive demeanor, you'll thrive. If you go in with a bad attitude, you won't survive.
I see that you're located in Key West - great place to live, but not exactly teeming with IT opportunities. If I were you, I would certainly give it my best effort to make this job into something worth keeping.
Ultimately, you have to assess whether or not this position is right for you -- or if you are a good fit for the position. Good luck.
by benzesp
I had the same situation when I first started my current sys
admin job. The Director of IT (my boss) is so busy so it was
really hard to get him to help me out when I got stuck doing a
task. Luckily I always had a dozen or so tasks to do so I would
just work on something else until he could help me out. I would
insist on "driving" when he was showing me how to resolve an
issue. I'm a hands on learner. I think sometimes they forget that
you sometimes have absolutely no Idea what to do or where to
start.
My advise is this:
Ask questions right away when something goes over your head.
If your not sure about something ask before you act on it.
Be assertive yet friendly when asking for advise, it's a whole lot
easier when your boss considers you a friend. Get to know your
boss, that is so important. Go have a beer after work and BS with
him. Getting it on a personal level is key to a laid back work
atmosphere.
Be resourceful by talking to other people within the company on
issues. ( I'm always bothering our software engineer and asking
him about issues)
Ask for a "chore list" and insert yourself in to the everyday
routine.
Most important, Always have new book in your bag ( CCNA book
is in mine right now)
We all have to start somewhere, you might be a pain in
somebody's ass for a while but thats just the way it has to be.
keep pushing, dont get discouraged.
by pamelaknight
This discussion is closed to new replies.
Trending IT Employment posts
Sort by Trending