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.
-
@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!
-
@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:
@coliver said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
The term cheap to me (and I think others) means it needs to perform to the level that we can still run production (or whatever the use case is) and save more money than what we may have been proposed before.
That's an undefinable definition. Cheap but not the cheapest, good but not the best for us. So not the best option for the business, but not recklessly cheap. How do you make decisions around that? How do you decide what is "cheap enough" while being "not so bad" but not just choosing "what is best for the financial interest of the business?"
I'm seriously, without a clear definition but also without the goal of doing what is right for the business... what's the motivator for this? What makes something the lesser choice, but good enough?
Isn't part of being the best solution also having the lowest cost while still getting all of the needed items from that solution?
Right, but cheap denotes that you are making sacrifices that would stop you from getting the best solution for you business. At least to me it does.
Exactly. "Best" is no longer the decision factor... something else is. Anything else, is bad. Cheap is just one of many bad options.
I think it's important to make the distinction that "best" is not a factor. It is a matrix, unlike "cheap", which is tied to a single factor.
Best remains a factor... that factor being "the most value to the business goal of profits".
Value is not a single factor. It's based on multiple factors, ergo it is a matrix.
-
@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.
-
@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.
-
@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.
-
@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.
-
Now as an example.
We need a new file server to host 16TB of space.
What are the business needs above in the most general sense?
-
@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.
-
@DustinB3403 said in A Mandate to Be Cheap:
Now as an example.
We need a new file server to host 16TB of space.
What are the business needs above in the most general sense?
It doesn't matter, because the options that satisfy those criteria will cost too much. You will be forced to stretch and bend until you come back with something that won't work, but will meet the artificial price point. And... then it's your failure.
-
@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.
-
@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.
-
@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.
Part of the issue is likely "letting them call you IT." It's fine, because you ARE IT. But you are not "in charge of IT". Always force the discussion to be that they are YOUR "IT Managers" and never let them state otherwise. Never let them repeat it to other people. Point out, always, to everyone, that you are the in the trenches IT guy, but the IT decisions are those of the IT manager ultimately and you just action them. It's only words, but it goes a long way. Hard to blame IT when everyone realizes who the IT decision maker is.
Of course, don't present any solution that isn't going to make them ultimately happy. Rule those out. That's important, too.
-
@art_of_shred 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:
@coliver said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
The term cheap to me (and I think others) means it needs to perform to the level that we can still run production (or whatever the use case is) and save more money than what we may have been proposed before.
That's an undefinable definition. Cheap but not the cheapest, good but not the best for us. So not the best option for the business, but not recklessly cheap. How do you make decisions around that? How do you decide what is "cheap enough" while being "not so bad" but not just choosing "what is best for the financial interest of the business?"
I'm seriously, without a clear definition but also without the goal of doing what is right for the business... what's the motivator for this? What makes something the lesser choice, but good enough?
Isn't part of being the best solution also having the lowest cost while still getting all of the needed items from that solution?
Right, but cheap denotes that you are making sacrifices that would stop you from getting the best solution for you business. At least to me it does.
Exactly. "Best" is no longer the decision factor... something else is. Anything else, is bad. Cheap is just one of many bad options.
I think it's important to make the distinction that "best" is not a factor. It is a matrix, unlike "cheap", which is tied to a single factor.
Best remains a factor... that factor being "the most value to the business goal of profits".
Value is not a single factor. It's based on multiple factors, ergo it is a matrix.
I disagree. Only if you leave room for flexible ethics or legality do you really have anything more than one value in a normal business. NTG aside, which does not operate for normal reasons, businesses have one single measurement of success - profits. Everything else is a red herring.
-
@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.
-
@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.
-
@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.