A Mandate to Be Cheap
-
@scottalanmiller said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@dafyre said in A Mandate to Be Cheap:
This was prevalent for a number of years at my job... As I was leaving, it did not seem to be quite as large of a problem.
Why is it a problem at all? As long as everyone knows who is the IT decision maker, that's all that matters. That's the person you (I dislike saying this) blame when things don't work because of some decision that was made.
I agree, I see no problem at all. Not even sure what the perceived one is. Maybe that the IT Managers were not admitting that htey were?
LOL - exactly - that is the real problem. For example, my boss (or the board) are the ones that make the decision, not me. Therefore the fault is really there's. But they don't see it that way, which of course is crazy... instead they say - hey Dash, that solution that I picked from the ones you provided was shit, this is your fault.
I would argue that you shouldn't ever propose a solution that could turn into shit.
Only provide options that will work, and then the business can't make the "wrong choice" and have wasted money.
What?!? You must be new at this. Management will seldom let you get away with only providing good options, especially when they dictate your parameters with inane boundaries.
So the onus of deciding what solutions management gets to "review" is on you to present to management. It's your responsibility to say "That isn't an option, here is why it doesn't meet the needs of the business here, here and here"
Or whatever reasons. But business reasons should be the reasons that a solution isn't an option.
Exactly, you are the filter. If you are making recommendations, they are YOUR recommendations. Otherwise, you are just being asked to list things regardless of viability... which if so, there is nothing whatsoever to blame you for.
I can't argue with that. However, having something legit to blame someone for doesn't have to be part of the equation when you just feel like passing blame. I'm not calling it legit, just saying that happens in the real world. I'm not saying you can't win in a court of law; I'm saying that it's not worth the effort to fight a battle you aren't going to win with a boss or owner in a SMB employment scenario.
Of course, BUT you can manage things better or worse. How options are presented, which ones are presented, how they are documented, how the decision is labeled... these things really matter, even to crazy, irrational owners.
This is where the topic always turns to, how well documented was this decision process? Was it clear to everyone involved that the solution doesn't meet the needs? What was the driving factor for the final decision, did ownership go out and purchase it and then say "make it work"?
If conversations like this occur and don't start with clear and simple understanding / explanations then the failure was on the filter (IT).
If the filter is working, but being bypassed (or removed entirely) then there was no care for the business use.
Just a desire to spend money.
-
@scottalanmiller said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@dafyre said in A Mandate to Be Cheap:
This was prevalent for a number of years at my job... As I was leaving, it did not seem to be quite as large of a problem.
Why is it a problem at all? As long as everyone knows who is the IT decision maker, that's all that matters. That's the person you (I dislike saying this) blame when things don't work because of some decision that was made.
I agree, I see no problem at all. Not even sure what the perceived one is. Maybe that the IT Managers were not admitting that htey were?
LOL - exactly - that is the real problem. For example, my boss (or the board) are the ones that make the decision, not me. Therefore the fault is really there's. But they don't see it that way, which of course is crazy... instead they say - hey Dash, that solution that I picked from the ones you provided was shit, this is your fault.
I would argue that you shouldn't ever propose a solution that could turn into shit.
Only provide options that will work, and then the business can't make the "wrong choice" and have wasted money.
What?!? You must be new at this. Management will seldom let you get away with only providing good options, especially when they dictate your parameters with inane boundaries.
You can always limit your responses to good ones. You can say "there are, of course, bad ideas but it's my job to not recommend them, obviously. But if you want to do things that are not safe, you can always make that decision yourself."
While I love the frankness of that statement - and love to pretend that I'm that frank in general - OK I am, but not to the one who signs my paycheck. It's rare that you could say that to your manager and not have them severely dislike you, possibly to the point of firing you. Why? because they are emotional and want to be hand held.
-
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@dafyre said in A Mandate to Be Cheap:
This was prevalent for a number of years at my job... As I was leaving, it did not seem to be quite as large of a problem.
Why is it a problem at all? As long as everyone knows who is the IT decision maker, that's all that matters. That's the person you (I dislike saying this) blame when things don't work because of some decision that was made.
I agree, I see no problem at all. Not even sure what the perceived one is. Maybe that the IT Managers were not admitting that htey were?
LOL - exactly - that is the real problem. For example, my boss (or the board) are the ones that make the decision, not me. Therefore the fault is really there's. But they don't see it that way, which of course is crazy... instead they say - hey Dash, that solution that I picked from the ones you provided was shit, this is your fault.
I would argue that you shouldn't ever propose a solution that could turn into shit.
Only provide options that will work, and then the business can't make the "wrong choice" and have wasted money.
What?!? You must be new at this. Management will seldom let you get away with only providing good options, especially when they dictate your parameters with inane boundaries.
You can always limit your responses to good ones. You can say "there are, of course, bad ideas but it's my job to not recommend them, obviously. But if you want to do things that are not safe, you can always make that decision yourself."
While I love the frankness of that statement - and love to pretend that I'm that frank in general - OK I am, but not to the one who signs my paycheck. It's rare that you could say that to your manager and not have them severely dislike you, possibly to the point of firing you. Why? because they are emotional and want to be
hand held[moderated] stroked.FTFY
-
@scottalanmiller said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@dafyre said in A Mandate to Be Cheap:
This was prevalent for a number of years at my job... As I was leaving, it did not seem to be quite as large of a problem.
Why is it a problem at all? As long as everyone knows who is the IT decision maker, that's all that matters. That's the person you (I dislike saying this) blame when things don't work because of some decision that was made.
I agree, I see no problem at all. Not even sure what the perceived one is. Maybe that the IT Managers were not admitting that htey were?
LOL - exactly - that is the real problem. For example, my boss (or the board) are the ones that make the decision, not me. Therefore the fault is really there's. But they don't see it that way, which of course is crazy... instead they say - hey Dash, that solution that I picked from the ones you provided was shit, this is your fault.
I would argue that you shouldn't ever propose a solution that could turn into shit.
Only provide options that will work, and then the business can't make the "wrong choice" and have wasted money.
What?!? You must be new at this. Management will seldom let you get away with only providing good options, especially when they dictate your parameters with inane boundaries.
So the onus of deciding what solutions management gets to "review" is on you to present to management. It's your responsibility to say "That isn't an option, here is why it doesn't meet the needs of the business here, here and here"
Or whatever reasons. But business reasons should be the reasons that a solution isn't an option.
Exactly, you are the filter. If you are making recommendations, they are YOUR recommendations. Otherwise, you are just being asked to list things regardless of viability... which if so, there is nothing whatsoever to blame you for.
I can't argue with that. However, having something legit to blame someone for doesn't have to be part of the equation when you just feel like passing blame. I'm not calling it legit, just saying that happens in the real world. I'm not saying you can't win in a court of law; I'm saying that it's not worth the effort to fight a battle you aren't going to win with a boss or owner in a SMB employment scenario.
Of course, BUT you can manage things better or worse. How options are presented, which ones are presented, how they are documented, how the decision is labeled... these things really matter, even to crazy, irrational owners.
You'd certainly like to think you can control these things, but the reality is you probably can't. I constantly have management asking - Why do the PCs we purchase cost more than the ones in Best Buy - it's just a computer right? They don't understand things like warranties, business class machines, Windows Pro vs Home editions, etc, etc... when you tell them those things.. they only hear words, rambling words.
What's worse is that they often have had their crappy BB computer at home for 5+ years, so all those things that you mention about business class being better - they don't don't believe it since they got the same 5+ out of their BB computer.
-
@coliver said in A Mandate to Be Cheap:
Inex
This is exactly my thinking. Most use them interchangeably but I say cheap is poor quality and inexpensive deals with the price. Not to be confused with cost, which I would say includes perceived or actual value. 'Round and 'round we go.
-
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@dafyre said in A Mandate to Be Cheap:
This was prevalent for a number of years at my job... As I was leaving, it did not seem to be quite as large of a problem.
Why is it a problem at all? As long as everyone knows who is the IT decision maker, that's all that matters. That's the person you (I dislike saying this) blame when things don't work because of some decision that was made.
I agree, I see no problem at all. Not even sure what the perceived one is. Maybe that the IT Managers were not admitting that htey were?
LOL - exactly - that is the real problem. For example, my boss (or the board) are the ones that make the decision, not me. Therefore the fault is really there's. But they don't see it that way, which of course is crazy... instead they say - hey Dash, that solution that I picked from the ones you provided was shit, this is your fault.
I would argue that you shouldn't ever propose a solution that could turn into shit.
Only provide options that will work, and then the business can't make the "wrong choice" and have wasted money.
What?!? You must be new at this. Management will seldom let you get away with only providing good options, especially when they dictate your parameters with inane boundaries.
So the onus of deciding what solutions management gets to "review" is on you to present to management. It's your responsibility to say "That isn't an option, here is why it doesn't meet the needs of the business here, here and here"
Or whatever reasons. But business reasons should be the reasons that a solution isn't an option.
Exactly, you are the filter. If you are making recommendations, they are YOUR recommendations. Otherwise, you are just being asked to list things regardless of viability... which if so, there is nothing whatsoever to blame you for.
I can't argue with that. However, having something legit to blame someone for doesn't have to be part of the equation when you just feel like passing blame. I'm not calling it legit, just saying that happens in the real world. I'm not saying you can't win in a court of law; I'm saying that it's not worth the effort to fight a battle you aren't going to win with a boss or owner in a SMB employment scenario.
Of course, BUT you can manage things better or worse. How options are presented, which ones are presented, how they are documented, how the decision is labeled... these things really matter, even to crazy, irrational owners.
You'd certainly like to think you can control these things, but the reality is you probably can't. I constantly have management asking - Why do the PCs we purchase cost more than the ones in Best Buy - it's just a computer right? They don't understand things like warranties, business class machines, Windows Pro vs Home editions, etc, etc... when you tell them those things.. they only hear words, rambling words.
What's worse is that they often have had their crappy BB computer at home for 5+ years, so all those things that you mention about business class being better - they don't don't believe it since they got the same 5+ out of their BB computer.
The solution to this is explain why their proposed solution doesn't work (and document the explanation). If they still choose to purchase BB computers for $200 bucks it's pure on them.
When it blows up, they lose credibility and trust of further up management.
-
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@dafyre said in A Mandate to Be Cheap:
This was prevalent for a number of years at my job... As I was leaving, it did not seem to be quite as large of a problem.
Why is it a problem at all? As long as everyone knows who is the IT decision maker, that's all that matters. That's the person you (I dislike saying this) blame when things don't work because of some decision that was made.
I agree, I see no problem at all. Not even sure what the perceived one is. Maybe that the IT Managers were not admitting that htey were?
LOL - exactly - that is the real problem. For example, my boss (or the board) are the ones that make the decision, not me. Therefore the fault is really there's. But they don't see it that way, which of course is crazy... instead they say - hey Dash, that solution that I picked from the ones you provided was shit, this is your fault.
I would argue that you shouldn't ever propose a solution that could turn into shit.
Only provide options that will work, and then the business can't make the "wrong choice" and have wasted money.
What?!? You must be new at this. Management will seldom let you get away with only providing good options, especially when they dictate your parameters with inane boundaries.
So the onus of deciding what solutions management gets to "review" is on you to present to management. It's your responsibility to say "That isn't an option, here is why it doesn't meet the needs of the business here, here and here"
Or whatever reasons. But business reasons should be the reasons that a solution isn't an option.
Sadly, they still have the authority to select the thing you said was not an option, and only recall that you mentioned it; thus it is your fault.
Here Here!
I suffer this problem - I present two options, say which one I really want, and they say - really, there is no other option? I know Bill down at BB can sell me xyz for half that price - then you do what Dustin explains, and they still pill Bill's solution and blame you when it doesn't work, and in my example, it was their mention.
Right, the issue here is defining "option".
Is there another option?
No, none that I know of that I could in good conscious recommend without knowing that I was setting you, the IT decision manager, up for failure.
Now I do like that sentence! I really truly wonder how it would really fly? I see several outcomes, so directly, yet pretty eloquently, of reminding them that they are the IT manager - 1) they will realize their but is on the line, and probably cave to your recommendation because they know they don't know, so they take your recommendation 2) they laugh at you because they don't agree that they are the IT decision manager, and because they are the owners they can do whatever they want, regardless of logic, 3) realize that this meeting was perhaps unnecessary and that they really should have you be the IT manager and trust you to do that job.
-
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@dafyre said in A Mandate to Be Cheap:
This was prevalent for a number of years at my job... As I was leaving, it did not seem to be quite as large of a problem.
Why is it a problem at all? As long as everyone knows who is the IT decision maker, that's all that matters. That's the person you (I dislike saying this) blame when things don't work because of some decision that was made.
I agree, I see no problem at all. Not even sure what the perceived one is. Maybe that the IT Managers were not admitting that htey were?
LOL - exactly - that is the real problem. For example, my boss (or the board) are the ones that make the decision, not me. Therefore the fault is really there's. But they don't see it that way, which of course is crazy... instead they say - hey Dash, that solution that I picked from the ones you provided was shit, this is your fault.
I would argue that you shouldn't ever propose a solution that could turn into shit.
Only provide options that will work, and then the business can't make the "wrong choice" and have wasted money.
What?!? You must be new at this. Management will seldom let you get away with only providing good options, especially when they dictate your parameters with inane boundaries.
You can always limit your responses to good ones. You can say "there are, of course, bad ideas but it's my job to not recommend them, obviously. But if you want to do things that are not safe, you can always make that decision yourself."
While I love the frankness of that statement - and love to pretend that I'm that frank in general - OK I am, but not to the one who signs my paycheck. It's rare that you could say that to your manager and not have them severely dislike you, possibly to the point of firing you. Why? because they are emotional and want to be hand held.
Do you REALLY believe that your manager would fire you for doing your job well AND that the owners of the business would feel that firing you was a good thing to do specifically to cover up the manager trying to be emotional and trying to sabotage the business?
I'm being serious... read that statement aloud and ask yourself... firing someone over refusing to be set up for blame aforethought when the intent was for your manager to hurt the business and didn't like that you were not going to assist?
-
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@dafyre said in A Mandate to Be Cheap:
This was prevalent for a number of years at my job... As I was leaving, it did not seem to be quite as large of a problem.
Why is it a problem at all? As long as everyone knows who is the IT decision maker, that's all that matters. That's the person you (I dislike saying this) blame when things don't work because of some decision that was made.
I agree, I see no problem at all. Not even sure what the perceived one is. Maybe that the IT Managers were not admitting that htey were?
LOL - exactly - that is the real problem. For example, my boss (or the board) are the ones that make the decision, not me. Therefore the fault is really there's. But they don't see it that way, which of course is crazy... instead they say - hey Dash, that solution that I picked from the ones you provided was shit, this is your fault.
I would argue that you shouldn't ever propose a solution that could turn into shit.
Only provide options that will work, and then the business can't make the "wrong choice" and have wasted money.
What?!? You must be new at this. Management will seldom let you get away with only providing good options, especially when they dictate your parameters with inane boundaries.
So the onus of deciding what solutions management gets to "review" is on you to present to management. It's your responsibility to say "That isn't an option, here is why it doesn't meet the needs of the business here, here and here"
Or whatever reasons. But business reasons should be the reasons that a solution isn't an option.
Exactly, you are the filter. If you are making recommendations, they are YOUR recommendations. Otherwise, you are just being asked to list things regardless of viability... which if so, there is nothing whatsoever to blame you for.
I can't argue with that. However, having something legit to blame someone for doesn't have to be part of the equation when you just feel like passing blame. I'm not calling it legit, just saying that happens in the real world. I'm not saying you can't win in a court of law; I'm saying that it's not worth the effort to fight a battle you aren't going to win with a boss or owner in a SMB employment scenario.
Of course, BUT you can manage things better or worse. How options are presented, which ones are presented, how they are documented, how the decision is labeled... these things really matter, even to crazy, irrational owners.
You'd certainly like to think you can control these things, but the reality is you probably can't. I constantly have management asking - Why do the PCs we purchase cost more than the ones in Best Buy - it's just a computer right? They don't understand things like warranties, business class machines, Windows Pro vs Home editions, etc, etc... when you tell them those things.. they only hear words, rambling words.
What's worse is that they often have had their crappy BB computer at home for 5+ years, so all those things that you mention about business class being better - they don't don't believe it since they got the same 5+ out of their BB computer.
The answer is simply... because the ones at BB don't meet our needs AND they don't cost less, that's a simple business mistake. Refer them to the CFO and ask him to provide a class on TCO versus purchase price.
Seriously, don't accept business failings. These questions are normally answered by... don't empower them to make these statements by agreeing in any fashion when they are patently untrue.
And if they don't believe it... just buy those. Seriously, don't agonize over their decisions. Say "I don't believe that the TCO is lower, but if you want them, sign this paper that you want to do this anyway." Done... move on. You did your job, they decided to do their own IT research, make their own decisions and be the IT managers. Don't try to override the IT Manager... just don't let them pretend that you are the IT decision maker.
-
@DustinB3403 said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@dafyre said in A Mandate to Be Cheap:
This was prevalent for a number of years at my job... As I was leaving, it did not seem to be quite as large of a problem.
Why is it a problem at all? As long as everyone knows who is the IT decision maker, that's all that matters. That's the person you (I dislike saying this) blame when things don't work because of some decision that was made.
I agree, I see no problem at all. Not even sure what the perceived one is. Maybe that the IT Managers were not admitting that htey were?
LOL - exactly - that is the real problem. For example, my boss (or the board) are the ones that make the decision, not me. Therefore the fault is really there's. But they don't see it that way, which of course is crazy... instead they say - hey Dash, that solution that I picked from the ones you provided was shit, this is your fault.
I would argue that you shouldn't ever propose a solution that could turn into shit.
Only provide options that will work, and then the business can't make the "wrong choice" and have wasted money.
What?!? You must be new at this. Management will seldom let you get away with only providing good options, especially when they dictate your parameters with inane boundaries.
So the onus of deciding what solutions management gets to "review" is on you to present to management. It's your responsibility to say "That isn't an option, here is why it doesn't meet the needs of the business here, here and here"
Or whatever reasons. But business reasons should be the reasons that a solution isn't an option.
Exactly, you are the filter. If you are making recommendations, they are YOUR recommendations. Otherwise, you are just being asked to list things regardless of viability... which if so, there is nothing whatsoever to blame you for.
I can't argue with that. However, having something legit to blame someone for doesn't have to be part of the equation when you just feel like passing blame. I'm not calling it legit, just saying that happens in the real world. I'm not saying you can't win in a court of law; I'm saying that it's not worth the effort to fight a battle you aren't going to win with a boss or owner in a SMB employment scenario.
Of course, BUT you can manage things better or worse. How options are presented, which ones are presented, how they are documented, how the decision is labeled... these things really matter, even to crazy, irrational owners.
You'd certainly like to think you can control these things, but the reality is you probably can't. I constantly have management asking - Why do the PCs we purchase cost more than the ones in Best Buy - it's just a computer right? They don't understand things like warranties, business class machines, Windows Pro vs Home editions, etc, etc... when you tell them those things.. they only hear words, rambling words.
What's worse is that they often have had their crappy BB computer at home for 5+ years, so all those things that you mention about business class being better - they don't don't believe it since they got the same 5+ out of their BB computer.
The solution to this is explain why their proposed solution doesn't work (and document the explanation). If they still choose to purchase BB computers for $200 bucks it's pure on them.
When it blows up, they lose credibility and trust of further up management.
I think you must be working in much larger medium sized business than I. There is at most 1 level between me and the owners of the company since I left a fortune 500 company. So if my boss is good buddies with the owner/CEO I'm sunk no matter what.
-
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@dafyre said in A Mandate to Be Cheap:
This was prevalent for a number of years at my job... As I was leaving, it did not seem to be quite as large of a problem.
Why is it a problem at all? As long as everyone knows who is the IT decision maker, that's all that matters. That's the person you (I dislike saying this) blame when things don't work because of some decision that was made.
I agree, I see no problem at all. Not even sure what the perceived one is. Maybe that the IT Managers were not admitting that htey were?
LOL - exactly - that is the real problem. For example, my boss (or the board) are the ones that make the decision, not me. Therefore the fault is really there's. But they don't see it that way, which of course is crazy... instead they say - hey Dash, that solution that I picked from the ones you provided was shit, this is your fault.
I would argue that you shouldn't ever propose a solution that could turn into shit.
Only provide options that will work, and then the business can't make the "wrong choice" and have wasted money.
What?!? You must be new at this. Management will seldom let you get away with only providing good options, especially when they dictate your parameters with inane boundaries.
So the onus of deciding what solutions management gets to "review" is on you to present to management. It's your responsibility to say "That isn't an option, here is why it doesn't meet the needs of the business here, here and here"
Or whatever reasons. But business reasons should be the reasons that a solution isn't an option.
Sadly, they still have the authority to select the thing you said was not an option, and only recall that you mentioned it; thus it is your fault.
Here Here!
I suffer this problem - I present two options, say which one I really want, and they say - really, there is no other option? I know Bill down at BB can sell me xyz for half that price - then you do what Dustin explains, and they still pill Bill's solution and blame you when it doesn't work, and in my example, it was their mention.
Right, the issue here is defining "option".
Is there another option?
No, none that I know of that I could in good conscious recommend without knowing that I was setting you, the IT decision manager, up for failure.
Now I do like that sentence! I really truly wonder how it would really fly? I see several outcomes, so directly, yet pretty eloquently, of reminding them that they are the IT manager - 1) they will realize their but is on the line, and probably cave to your recommendation because they know they don't know, so they take your recommendation 2) they laugh at you because they don't agree that they are the IT decision manager, and because they are the owners they can do whatever they want, regardless of logic, 3) realize that this meeting was perhaps unnecessary and that they really should have you be the IT manager and trust you to do that job.
Is 2) really the owner than often? If so, quit. Easy peasy. They are irrational, insane and going to hurt you for fun.
-
@Dashrender said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@dafyre said in A Mandate to Be Cheap:
This was prevalent for a number of years at my job... As I was leaving, it did not seem to be quite as large of a problem.
Why is it a problem at all? As long as everyone knows who is the IT decision maker, that's all that matters. That's the person you (I dislike saying this) blame when things don't work because of some decision that was made.
I agree, I see no problem at all. Not even sure what the perceived one is. Maybe that the IT Managers were not admitting that htey were?
LOL - exactly - that is the real problem. For example, my boss (or the board) are the ones that make the decision, not me. Therefore the fault is really there's. But they don't see it that way, which of course is crazy... instead they say - hey Dash, that solution that I picked from the ones you provided was shit, this is your fault.
I would argue that you shouldn't ever propose a solution that could turn into shit.
Only provide options that will work, and then the business can't make the "wrong choice" and have wasted money.
What?!? You must be new at this. Management will seldom let you get away with only providing good options, especially when they dictate your parameters with inane boundaries.
So the onus of deciding what solutions management gets to "review" is on you to present to management. It's your responsibility to say "That isn't an option, here is why it doesn't meet the needs of the business here, here and here"
Or whatever reasons. But business reasons should be the reasons that a solution isn't an option.
Exactly, you are the filter. If you are making recommendations, they are YOUR recommendations. Otherwise, you are just being asked to list things regardless of viability... which if so, there is nothing whatsoever to blame you for.
I can't argue with that. However, having something legit to blame someone for doesn't have to be part of the equation when you just feel like passing blame. I'm not calling it legit, just saying that happens in the real world. I'm not saying you can't win in a court of law; I'm saying that it's not worth the effort to fight a battle you aren't going to win with a boss or owner in a SMB employment scenario.
Of course, BUT you can manage things better or worse. How options are presented, which ones are presented, how they are documented, how the decision is labeled... these things really matter, even to crazy, irrational owners.
You'd certainly like to think you can control these things, but the reality is you probably can't. I constantly have management asking - Why do the PCs we purchase cost more than the ones in Best Buy - it's just a computer right? They don't understand things like warranties, business class machines, Windows Pro vs Home editions, etc, etc... when you tell them those things.. they only hear words, rambling words.
What's worse is that they often have had their crappy BB computer at home for 5+ years, so all those things that you mention about business class being better - they don't don't believe it since they got the same 5+ out of their BB computer.
The solution to this is explain why their proposed solution doesn't work (and document the explanation). If they still choose to purchase BB computers for $200 bucks it's pure on them.
When it blows up, they lose credibility and trust of further up management.
I think you must be working in much larger medium sized business than I. There is at most 1 level between me and the owners of the company since I left a fortune 500 company. So if my boss is good buddies with the owner/CEO I'm sunk no matter what.
And scott answered this issue in the post just above yours.
Have their signature on whatever solution was purchased, they are the [moderated]-ups that decided to purchase whatever it was.
-
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@dafyre said in A Mandate to Be Cheap:
This was prevalent for a number of years at my job... As I was leaving, it did not seem to be quite as large of a problem.
Why is it a problem at all? As long as everyone knows who is the IT decision maker, that's all that matters. That's the person you (I dislike saying this) blame when things don't work because of some decision that was made.
I agree, I see no problem at all. Not even sure what the perceived one is. Maybe that the IT Managers were not admitting that htey were?
LOL - exactly - that is the real problem. For example, my boss (or the board) are the ones that make the decision, not me. Therefore the fault is really there's. But they don't see it that way, which of course is crazy... instead they say - hey Dash, that solution that I picked from the ones you provided was shit, this is your fault.
I would argue that you shouldn't ever propose a solution that could turn into shit.
Only provide options that will work, and then the business can't make the "wrong choice" and have wasted money.
What?!? You must be new at this. Management will seldom let you get away with only providing good options, especially when they dictate your parameters with inane boundaries.
You can always limit your responses to good ones. You can say "there are, of course, bad ideas but it's my job to not recommend them, obviously. But if you want to do things that are not safe, you can always make that decision yourself."
While I love the frankness of that statement - and love to pretend that I'm that frank in general - OK I am, but not to the one who signs my paycheck. It's rare that you could say that to your manager and not have them severely dislike you, possibly to the point of firing you. Why? because they are emotional and want to be hand held.
Do you REALLY believe that your manager would fire you for doing your job well AND that the owners of the business would feel that firing you was a good thing to do specifically to cover up the manager trying to be emotional and trying to sabotage the business?
I'm being serious... read that statement aloud and ask yourself... firing someone over refusing to be set up for blame aforethought when the intent was for your manager to hurt the business and didn't like that you were not going to assist?
Absolutely, although that chain of rationalization doesn't happen in their minds. You're a PITA always nagging them about details they don't want to be bothered with. Eventually, you are weeded out.
-
@art_of_shred said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@dafyre said in A Mandate to Be Cheap:
This was prevalent for a number of years at my job... As I was leaving, it did not seem to be quite as large of a problem.
Why is it a problem at all? As long as everyone knows who is the IT decision maker, that's all that matters. That's the person you (I dislike saying this) blame when things don't work because of some decision that was made.
I agree, I see no problem at all. Not even sure what the perceived one is. Maybe that the IT Managers were not admitting that htey were?
LOL - exactly - that is the real problem. For example, my boss (or the board) are the ones that make the decision, not me. Therefore the fault is really there's. But they don't see it that way, which of course is crazy... instead they say - hey Dash, that solution that I picked from the ones you provided was shit, this is your fault.
I would argue that you shouldn't ever propose a solution that could turn into shit.
Only provide options that will work, and then the business can't make the "wrong choice" and have wasted money.
What?!? You must be new at this. Management will seldom let you get away with only providing good options, especially when they dictate your parameters with inane boundaries.
You can always limit your responses to good ones. You can say "there are, of course, bad ideas but it's my job to not recommend them, obviously. But if you want to do things that are not safe, you can always make that decision yourself."
While I love the frankness of that statement - and love to pretend that I'm that frank in general - OK I am, but not to the one who signs my paycheck. It's rare that you could say that to your manager and not have them severely dislike you, possibly to the point of firing you. Why? because they are emotional and want to be hand held.
Do you REALLY believe that your manager would fire you for doing your job well AND that the owners of the business would feel that firing you was a good thing to do specifically to cover up the manager trying to be emotional and trying to sabotage the business?
I'm being serious... read that statement aloud and ask yourself... firing someone over refusing to be set up for blame aforethought when the intent was for your manager to hurt the business and didn't like that you were not going to assist?
Absolutely, although that chain of rationalization doesn't happen in their minds. You're a PITA always nagging them about details they don't want to be bothered with. Eventually, you are weeded out.
It doesn't have to happen in their minds, it only has to be traceable via email communications.
Even if they do let you go, by the time that decision has been made, it would be painfully obvious that management is messing with the business more than the employee was.
-
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@dafyre said in A Mandate to Be Cheap:
This was prevalent for a number of years at my job... As I was leaving, it did not seem to be quite as large of a problem.
Why is it a problem at all? As long as everyone knows who is the IT decision maker, that's all that matters. That's the person you (I dislike saying this) blame when things don't work because of some decision that was made.
I agree, I see no problem at all. Not even sure what the perceived one is. Maybe that the IT Managers were not admitting that htey were?
LOL - exactly - that is the real problem. For example, my boss (or the board) are the ones that make the decision, not me. Therefore the fault is really there's. But they don't see it that way, which of course is crazy... instead they say - hey Dash, that solution that I picked from the ones you provided was shit, this is your fault.
I would argue that you shouldn't ever propose a solution that could turn into shit.
Only provide options that will work, and then the business can't make the "wrong choice" and have wasted money.
What?!? You must be new at this. Management will seldom let you get away with only providing good options, especially when they dictate your parameters with inane boundaries.
You can always limit your responses to good ones. You can say "there are, of course, bad ideas but it's my job to not recommend them, obviously. But if you want to do things that are not safe, you can always make that decision yourself."
While I love the frankness of that statement - and love to pretend that I'm that frank in general - OK I am, but not to the one who signs my paycheck. It's rare that you could say that to your manager and not have them severely dislike you, possibly to the point of firing you. Why? because they are emotional and want to be hand held.
Do you REALLY believe that your manager would fire you for doing your job well AND that the owners of the business would feel that firing you was a good thing to do specifically to cover up the manager trying to be emotional and trying to sabotage the business?
I'm being serious... read that statement aloud and ask yourself... firing someone over refusing to be set up for blame aforethought when the intent was for your manager to hurt the business and didn't like that you were not going to assist?
See though, you're back to the black and white thing - you assume that since the manager didn't take my recommendations, that they must be out to hurt the company.
Looking at my AP example way above - the proposal says 10 APs, they buy 5 - do you seriously think that the IT decision maker in this case was thinking.. hey I want to screw over my company, so today i'll do that buy only having them install 5 APs instead of 10. Damn, anyone who does think that should most definitely be fired, but no I don't think they ever think that.
Do I think they would seriously fire me, sadly, my lack of personal self confidence has me leaning that way at times. I know my skills are good, I'd say they are average around ML, and way above average at SW, but self confidence is an internal thing - I'm probably to old to really change it much.
-
@Dashrender said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@dafyre said in A Mandate to Be Cheap:
This was prevalent for a number of years at my job... As I was leaving, it did not seem to be quite as large of a problem.
Why is it a problem at all? As long as everyone knows who is the IT decision maker, that's all that matters. That's the person you (I dislike saying this) blame when things don't work because of some decision that was made.
I agree, I see no problem at all. Not even sure what the perceived one is. Maybe that the IT Managers were not admitting that htey were?
LOL - exactly - that is the real problem. For example, my boss (or the board) are the ones that make the decision, not me. Therefore the fault is really there's. But they don't see it that way, which of course is crazy... instead they say - hey Dash, that solution that I picked from the ones you provided was shit, this is your fault.
I would argue that you shouldn't ever propose a solution that could turn into shit.
Only provide options that will work, and then the business can't make the "wrong choice" and have wasted money.
What?!? You must be new at this. Management will seldom let you get away with only providing good options, especially when they dictate your parameters with inane boundaries.
So the onus of deciding what solutions management gets to "review" is on you to present to management. It's your responsibility to say "That isn't an option, here is why it doesn't meet the needs of the business here, here and here"
Or whatever reasons. But business reasons should be the reasons that a solution isn't an option.
Exactly, you are the filter. If you are making recommendations, they are YOUR recommendations. Otherwise, you are just being asked to list things regardless of viability... which if so, there is nothing whatsoever to blame you for.
I can't argue with that. However, having something legit to blame someone for doesn't have to be part of the equation when you just feel like passing blame. I'm not calling it legit, just saying that happens in the real world. I'm not saying you can't win in a court of law; I'm saying that it's not worth the effort to fight a battle you aren't going to win with a boss or owner in a SMB employment scenario.
Of course, BUT you can manage things better or worse. How options are presented, which ones are presented, how they are documented, how the decision is labeled... these things really matter, even to crazy, irrational owners.
You'd certainly like to think you can control these things, but the reality is you probably can't. I constantly have management asking - Why do the PCs we purchase cost more than the ones in Best Buy - it's just a computer right? They don't understand things like warranties, business class machines, Windows Pro vs Home editions, etc, etc... when you tell them those things.. they only hear words, rambling words.
What's worse is that they often have had their crappy BB computer at home for 5+ years, so all those things that you mention about business class being better - they don't don't believe it since they got the same 5+ out of their BB computer.
The solution to this is explain why their proposed solution doesn't work (and document the explanation). If they still choose to purchase BB computers for $200 bucks it's pure on them.
When it blows up, they lose credibility and trust of further up management.
I think you must be working in much larger medium sized business than I. There is at most 1 level between me and the owners of the company since I left a fortune 500 company. So if my boss is good buddies with the owner/CEO I'm sunk no matter what.
Correct, you are dealing with people who just don't care and, it sounds like, are kind of corrupt (if they will blame you for their own decisions, that's kind of just mean and vicious.) Scapegoating when there are no politics, just mean owners, is very bad.
-
@art_of_shred said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@dafyre said in A Mandate to Be Cheap:
This was prevalent for a number of years at my job... As I was leaving, it did not seem to be quite as large of a problem.
Why is it a problem at all? As long as everyone knows who is the IT decision maker, that's all that matters. That's the person you (I dislike saying this) blame when things don't work because of some decision that was made.
I agree, I see no problem at all. Not even sure what the perceived one is. Maybe that the IT Managers were not admitting that htey were?
LOL - exactly - that is the real problem. For example, my boss (or the board) are the ones that make the decision, not me. Therefore the fault is really there's. But they don't see it that way, which of course is crazy... instead they say - hey Dash, that solution that I picked from the ones you provided was shit, this is your fault.
I would argue that you shouldn't ever propose a solution that could turn into shit.
Only provide options that will work, and then the business can't make the "wrong choice" and have wasted money.
What?!? You must be new at this. Management will seldom let you get away with only providing good options, especially when they dictate your parameters with inane boundaries.
You can always limit your responses to good ones. You can say "there are, of course, bad ideas but it's my job to not recommend them, obviously. But if you want to do things that are not safe, you can always make that decision yourself."
While I love the frankness of that statement - and love to pretend that I'm that frank in general - OK I am, but not to the one who signs my paycheck. It's rare that you could say that to your manager and not have them severely dislike you, possibly to the point of firing you. Why? because they are emotional and want to be hand held.
Do you REALLY believe that your manager would fire you for doing your job well AND that the owners of the business would feel that firing you was a good thing to do specifically to cover up the manager trying to be emotional and trying to sabotage the business?
I'm being serious... read that statement aloud and ask yourself... firing someone over refusing to be set up for blame aforethought when the intent was for your manager to hurt the business and didn't like that you were not going to assist?
Absolutely, although that chain of rationalization doesn't happen in their minds. You're a PITA always nagging them about details they don't want to be bothered with. Eventually, you are weeded out.
THere is no winning in that scenario. Doing a good job gets your fired, doing a bad job gets your fired. It's a corrupt environment (even if the corruption is just one owner that isn't capable of logic or kind thinking who just hates you personally) and the only good answer is to leave it as leaving it is the assumed end result regardless.
-
@DustinB3403 said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@dafyre said in A Mandate to Be Cheap:
This was prevalent for a number of years at my job... As I was leaving, it did not seem to be quite as large of a problem.
Why is it a problem at all? As long as everyone knows who is the IT decision maker, that's all that matters. That's the person you (I dislike saying this) blame when things don't work because of some decision that was made.
I agree, I see no problem at all. Not even sure what the perceived one is. Maybe that the IT Managers were not admitting that htey were?
LOL - exactly - that is the real problem. For example, my boss (or the board) are the ones that make the decision, not me. Therefore the fault is really there's. But they don't see it that way, which of course is crazy... instead they say - hey Dash, that solution that I picked from the ones you provided was shit, this is your fault.
I would argue that you shouldn't ever propose a solution that could turn into shit.
Only provide options that will work, and then the business can't make the "wrong choice" and have wasted money.
What?!? You must be new at this. Management will seldom let you get away with only providing good options, especially when they dictate your parameters with inane boundaries.
You can always limit your responses to good ones. You can say "there are, of course, bad ideas but it's my job to not recommend them, obviously. But if you want to do things that are not safe, you can always make that decision yourself."
While I love the frankness of that statement - and love to pretend that I'm that frank in general - OK I am, but not to the one who signs my paycheck. It's rare that you could say that to your manager and not have them severely dislike you, possibly to the point of firing you. Why? because they are emotional and want to be hand held.
Do you REALLY believe that your manager would fire you for doing your job well AND that the owners of the business would feel that firing you was a good thing to do specifically to cover up the manager trying to be emotional and trying to sabotage the business?
I'm being serious... read that statement aloud and ask yourself... firing someone over refusing to be set up for blame aforethought when the intent was for your manager to hurt the business and didn't like that you were not going to assist?
Absolutely, although that chain of rationalization doesn't happen in their minds. You're a PITA always nagging them about details they don't want to be bothered with. Eventually, you are weeded out.
It doesn't have to happen in their minds, it only has to be traceable via email communications.
Even if they do let you go, by the time that decision has been made, it would be painfully obvious that management is messing with the business more than the employee was.
So what? You don't have a job. Is that a win for you?
-
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@dafyre said in A Mandate to Be Cheap:
This was prevalent for a number of years at my job... As I was leaving, it did not seem to be quite as large of a problem.
Why is it a problem at all? As long as everyone knows who is the IT decision maker, that's all that matters. That's the person you (I dislike saying this) blame when things don't work because of some decision that was made.
I agree, I see no problem at all. Not even sure what the perceived one is. Maybe that the IT Managers were not admitting that htey were?
LOL - exactly - that is the real problem. For example, my boss (or the board) are the ones that make the decision, not me. Therefore the fault is really there's. But they don't see it that way, which of course is crazy... instead they say - hey Dash, that solution that I picked from the ones you provided was shit, this is your fault.
I would argue that you shouldn't ever propose a solution that could turn into shit.
Only provide options that will work, and then the business can't make the "wrong choice" and have wasted money.
What?!? You must be new at this. Management will seldom let you get away with only providing good options, especially when they dictate your parameters with inane boundaries.
So the onus of deciding what solutions management gets to "review" is on you to present to management. It's your responsibility to say "That isn't an option, here is why it doesn't meet the needs of the business here, here and here"
Or whatever reasons. But business reasons should be the reasons that a solution isn't an option.
Sadly, they still have the authority to select the thing you said was not an option, and only recall that you mentioned it; thus it is your fault.
Here Here!
I suffer this problem - I present two options, say which one I really want, and they say - really, there is no other option? I know Bill down at BB can sell me xyz for half that price - then you do what Dustin explains, and they still pill Bill's solution and blame you when it doesn't work, and in my example, it was their mention.
Right, the issue here is defining "option".
Is there another option?
No, none that I know of that I could in good conscious recommend without knowing that I was setting you, the IT decision manager, up for failure.
Now I do like that sentence! I really truly wonder how it would really fly? I see several outcomes, so directly, yet pretty eloquently, of reminding them that they are the IT manager - 1) they will realize their but is on the line, and probably cave to your recommendation because they know they don't know, so they take your recommendation 2) they laugh at you because they don't agree that they are the IT decision manager, and because they are the owners they can do whatever they want, regardless of logic, 3) realize that this meeting was perhaps unnecessary and that they really should have you be the IT manager and trust you to do that job.
Is 2) really the owner than often? If so, quit. Easy peasy. They are irrational, insane and going to hurt you for fun.
In my case the owners are the board - and they can often be more seemingly irrational then the CEO, which if is true, then you're right, a person in this situation should move on.
-
@art_of_shred said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@art_of_shred said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@dafyre said in A Mandate to Be Cheap:
This was prevalent for a number of years at my job... As I was leaving, it did not seem to be quite as large of a problem.
Why is it a problem at all? As long as everyone knows who is the IT decision maker, that's all that matters. That's the person you (I dislike saying this) blame when things don't work because of some decision that was made.
I agree, I see no problem at all. Not even sure what the perceived one is. Maybe that the IT Managers were not admitting that htey were?
LOL - exactly - that is the real problem. For example, my boss (or the board) are the ones that make the decision, not me. Therefore the fault is really there's. But they don't see it that way, which of course is crazy... instead they say - hey Dash, that solution that I picked from the ones you provided was shit, this is your fault.
I would argue that you shouldn't ever propose a solution that could turn into shit.
Only provide options that will work, and then the business can't make the "wrong choice" and have wasted money.
What?!? You must be new at this. Management will seldom let you get away with only providing good options, especially when they dictate your parameters with inane boundaries.
You can always limit your responses to good ones. You can say "there are, of course, bad ideas but it's my job to not recommend them, obviously. But if you want to do things that are not safe, you can always make that decision yourself."
While I love the frankness of that statement - and love to pretend that I'm that frank in general - OK I am, but not to the one who signs my paycheck. It's rare that you could say that to your manager and not have them severely dislike you, possibly to the point of firing you. Why? because they are emotional and want to be hand held.
Do you REALLY believe that your manager would fire you for doing your job well AND that the owners of the business would feel that firing you was a good thing to do specifically to cover up the manager trying to be emotional and trying to sabotage the business?
I'm being serious... read that statement aloud and ask yourself... firing someone over refusing to be set up for blame aforethought when the intent was for your manager to hurt the business and didn't like that you were not going to assist?
Absolutely, although that chain of rationalization doesn't happen in their minds. You're a PITA always nagging them about details they don't want to be bothered with. Eventually, you are weeded out.
It doesn't have to happen in their minds, it only has to be traceable via email communications.
Even if they do let you go, by the time that decision has been made, it would be painfully obvious that management is messing with the business more than the employee was.
So what? You don't have a job. Is that a win for you?
I'd be out finding another position the same day, while applying for unemployment coverage. I'd not have a job at a toxic place any longer.
So no it's not a "win" but it would be a win in terms of being done with a poor employer.
