IT Employment

General discussion


Problems with the boss

By broncodriver23 ·
i am having problems with my boss and i am looking for suggestions on how to deal with it. my problem is that my boss has priority issues. he keeps switching around what he wants done first so often that i cant get things done. he puts projects on hold till he decides they are ready, and expects the project to be done in less time then it was planned. we have already had several problems where he has forced me to put things live without proper testing, and when it dosent work he blames me to his boss. his boss has asked me what happened, and when i explain it to them they seem to listen to me. he is extreemly disorganized and he cant remember what he changes. in addition he "plays" with systems and software we cant support. we are a microsoft shop, and all of a sudden he wants a program thats on unix to be in the environment and tells me to build a server (that we dont have) to use the program. if i tell him we don have a server he tells me to pull one from our live site.

i know this sounds like a rant, but i'm really curious if anyone has to deal with this sort of stuff with there boss.


This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

Document, Document, Document

by BFilmFan In reply to Problems with the boss

If you are going to keep working for this manager, then I would document in email every time a project changes, is rescheduled, is time shortened.

If you just have had all you can stand, I'd start the new employment search. I can never advise anyone to stay where they are miserable. You aren't providing yourself, your co-workers or clients the level of service and attention they deserve when the majority of your day is spent dealing with conflict issues.

If all else fails and you can't quit, you could always wait for a talk show to host a segment on Bosses that Drive Me Crazy. Frankly, I'd like to see that on a Springer episode myself....

Collapse -


by mattbakeruk In reply to Document, Document, Docum ...

Good idea and start copying people on emails where you're instructed to pull machines from live environments.

You'll soon find out who your supporters are if the live money making environment is under threat.

Also what policies do you have in place on security on introducing new software - check you're not breaching them. If you are you're likely to be the one to hang.

Collapse -

You boss is a Nut!

by sgott In reply to Problems with the boss

Being a boss does NOT = good manager or even "rational human being"

Wise up! Get that resume out there and get another job

You'll be glad you did

Collapse -

BoZ ?

by indra.gunawan In reply to You boss is a Nut!

Quit and goo... :)

Collapse -

Happiness is a need too

by jdclyde In reply to Problems with the boss

If your job drives you nuts, find a new job. Life is much too short to spend it where every morning you wake up dreading to go into work.

If you like the job, just want something to happen with the aledged manager then try to work something out.

Have you talked to him about how you feel when he MAKES you compromise your work ethics? How does this compromise benefit the company?

I would ask this personally, not in an e-mail. Be direct without attacking or he will just get defensive and you will get no where. Just explain that you are trying to understand your position in the company to make sure your goals are in line with what the company expects and needs.

good luck.

Collapse -

For every action, there is a reaction

by erich1010 In reply to Problems with the boss

You should do everything that your boss tells you do to, BUT you should also advise him about all of the consequences of any action.

Any action you do can be quanticized in cost of 1) Time 2)Money 3) Resources

When he asks you to switch focus, give him a new project plan for each project involved, showing added delays in the previous project and added cost in the new project. Make sure you let him know that if you switch to project X, then project Y's deadline will not be met.

Most projects affect more than just your boss. Any time your boss's decision potentially affects a project adversely, let all parties involved with that project know immediately. (CC your boss, of course)

Hopefully, your boss will start getting feedback, not just from you, but everybody involved, and will start assessing the impact of his decisions before making them. Also, when **** does start hitting the fan, your *** will be covered.

Collapse -

Boss is Boss

by mjd420nova In reply to Problems with the boss

I use a large bulletin board divided into two sections, one software the other hardware. Each
project gets a rating (FLAP STATE) as to their
urgency and another for their status.

Collapse -

Wrong Fit for Your Boss and His Boss Suspects It

by A_dangerous_mind In reply to Problems with the boss

Your boss's boss doesn't sound like it's clueless about him. It may be someone that he was forced to hire by his boss, but he has doubts about his competence. It sounds like they suspect most of what you've written.

Unfortunately, my experience is that this kind of boss usually has to cause a disaster that can't be ignored before he is shown the exit or transferred to something that he is more competent at doing. That disaster is usually something on the order of the failure of a prominent project or tremendous employee turnover.

Collapse -

Implement a change process

by awfernald In reply to Problems with the boss

One of the ways to avoid most of the things that you mention is to have a valid change management process in place.

Basically, prior to any changes being moved into the production environment (hardware, software, applications, patches, etc...), changes being made in the configuration of the production environment, or production systems (hardware, software, applications, etc...) being removed from the production environment must be follow the process and be APPROVED before the change can occur.

If your boss is the one who would be doing the "APPROVE" on these changes, more is the better, as then he will have to explain why he approved the change, if it was still buffy, untested, faulty, etc... He can still blame you, however, his signature is now on the form saying that it was HIS decision, and thus HIS responsibility. Only if you lie or falsify information can he blame you.

Also, having some type of formal testing requirements in place would help as well. This way, if he wants to move something into production that is not ready, then you can place it into the testing environment, and see how bad it is going to muck everything up.

Hope this helps.

Related Discussions

Related Forums