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:
@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.
Seriously? You've never has a solution that went sideways - for whatever reason? You're a lucky man!
I wouldn't say I've never had a solution that has gone sideways, but I've only ever supplied solutions that are acceptable and proven to work.
Rather than going with an off-the wall solutions like using FreeNAS for a file server.
Sure it could work, but honestly why would any business or IT person consider or do this.
I think that's the issue. You provide 2 good choices, and then flippantly say something like... "I guess you could do stupid option C, but that would be retarded." Boss chooses option C, obviously, and the subsequent failure is on you.
Yup, VERY important that you control this.
-
@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."
-
@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:
@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.
So the fault is that the IT department presented the solution that wasn't a good solution at all, and should have never been presented in the first place.
If management brings up the non-solution, it is again on IT to say that the solution doesn't work for business reasons x,y and z.
So yes, that is a fault on IT for not providing accurate business reasons to avoid a particular configuration, even if management brings it up.
It is also managements fault (if they accept the blame or not) for not listening to the IT department in their explaination as to why the solution doesn't work.
I believe you are missing the point. Remove logic. It has no place here. The boss decides on a solution regardless of anything you suggest. The solution is something related to IT. That means it belongs to you, and so does its failure. Who cares if you did or did not suggest it? Who cares if you had any share in the decision-making process? It's IT. You are IT. Your fault. Done.
And that is where the CYA process comes in.
If management is blindly throwing darts at a board to pick a solution, let them. Just document that process used, and always redirect that blame back, until you find a new position.
-
@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.
-
@DustinB3403 said in A Mandate to Be Cheap:
It is also managements fault (if they accept the blame or not) for not listening to the IT department in their explaination as to why the solution doesn't work.
More important than that.... whoever makes this decision IS IT. Period. End of story. Business managers tell IT managers the business needs. Whoever makes technical decisions is IT. No grey area at all. It's that simple.
Never let the IT decision makers get away claiming not to be IT.
-
@DustinB3403 said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
So the term cheap (generally) means, Find a solution that meets our needs, and boost profits as much as possible.
Cheap never means that, as I explained. Never.
I may have missed your explanation, was it something along the lines of "cheap means risking business profits?"
If so I'd disagree, and you already agreed with that sentiment when I mentioned XO from source versus XOA.
Cheaper means "less cost to acquire." Nothing further. No implications of good or bad.
You said cheap, not cheaper. I see where the mix up was. I agree cheaper means lower cost to acquire.
I said originally that we were prioritizing cheap. Once it is prioritized, cheapest is the only possible outcome. I stated that before. And I asked how "cheap" could mean anything else.
-
@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:
@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.
So the fault is that the IT department presented the solution that wasn't a good solution at all, and should have never been presented in the first place.
If management brings up the non-solution, it is again on IT to say that the solution doesn't work for business reasons x,y and z.
So yes, that is a fault on IT for not providing accurate business reasons to avoid a particular configuration, even if management brings it up.
It is also managements fault (if they accept the blame or not) for not listening to the IT department in their explaination as to why the solution doesn't work.
I believe you are missing the point. Remove logic. It has no place here. The boss decides on a solution regardless of anything you suggest. The solution is something related to IT. That means it belongs to you, and so does its failure. Who cares if you did or did not suggest it? Who cares if you had any share in the decision-making process? It's IT. You are IT. Your fault. Done.
And that is where the CYA process comes in.
If management is blindly throwing darts at a board to pick a solution, let them. Just document that process used, and always redirect that blame back, until you find a new position.
And point out across the board that the person throwing the darts is the IT manager, regardless of title.
-
@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.
-
@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:
@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.
So the fault is that the IT department presented the solution that wasn't a good solution at all, and should have never been presented in the first place.
If management brings up the non-solution, it is again on IT to say that the solution doesn't work for business reasons x,y and z.
So yes, that is a fault on IT for not providing accurate business reasons to avoid a particular configuration, even if management brings it up.
It is also managements fault (if they accept the blame or not) for not listening to the IT department in their explaination as to why the solution doesn't work.
I believe you are missing the point. Remove logic. It has no place here. The boss decides on a solution regardless of anything you suggest. The solution is something related to IT. That means it belongs to you, and so does its failure. Who cares if you did or did not suggest it? Who cares if you had any share in the decision-making process? It's IT. You are IT. Your fault. Done.
And that is where the CYA process comes in.
If management is blindly throwing darts at a board to pick a solution, let them. Just document that process used, and always redirect that blame back, until you find a new position.
And point out across the board that the person throwing the darts is the IT manager, regardless of title.
Yep.
-
@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.
-
@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.
-
@scottalanmiller said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
So the term cheap (generally) means, Find a solution that meets our needs, and boost profits as much as possible.
Cheap never means that, as I explained. Never.
I may have missed your explanation, was it something along the lines of "cheap means risking business profits?"
If so I'd disagree, and you already agreed with that sentiment when I mentioned XO from source versus XOA.
Cheaper means "less cost to acquire." Nothing further. No implications of good or bad.
Then the situation already failed, because it didn't take the whole picture into account.
-
@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.
-
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
So the term cheap (generally) means, Find a solution that meets our needs, and boost profits as much as possible.
Cheap never means that, as I explained. Never.
I may have missed your explanation, was it something along the lines of "cheap means risking business profits?"
If so I'd disagree, and you already agreed with that sentiment when I mentioned XO from source versus XOA.
Cheaper means "less cost to acquire." Nothing further. No implications of good or bad.
Then the situation already failed, because it didn't take the whole picture into account.
So you've grasped my point
-
@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.
