A Mandate to Be Cheap
-
@Dashrender 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:
@scottalanmiller said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
I would immediately assume that the word "cheap" is simply used incorrectly, whereas he means, to find the most business cost appropriate solution available.
But that's the inherent mandate that is being overridden by the "cheap" mandate. So you would never state that in a business as it explicitly makes the former no longer the goal.
But the word cheap can be used as "Hey we can buy the proposed system with XY and Z, but this will work for the next two years and saves the company money"
That is taking the smart approach but also "being cheap".
There is no "smart approach" to being "cheap" when "cheap" is an override to "doing what's best." No matter how you couch it, it's still - not doing what is best for the company.
XenServer with Support from a Third party is "cheap" compared to support from Citrix. So are you saying anyone that uses NTG for XenServer support is sabotaging their employer?
Of course he's not saying that - the question is... Does NTG have the tools and know how to provide the level of support that the company needs? If yes, then the savings in this case are worthwhile, but if NTG doesn't, then the savings is detrimental because the solution of picking NTG does not solve the problem.
But it's cheaper, and @scottalanmiller will agree that 99% or more of businesses don't need developer level support for their hypervisor fleet.
So he's essentially said using the cheapest option (free xenserver and support from NTG) is detrimental to the business.
-
@Dashrender 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:
@scottalanmiller said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
I would immediately assume that the word "cheap" is simply used incorrectly, whereas he means, to find the most business cost appropriate solution available.
But that's the inherent mandate that is being overridden by the "cheap" mandate. So you would never state that in a business as it explicitly makes the former no longer the goal.
But the word cheap can be used as "Hey we can buy the proposed system with XY and Z, but this will work for the next two years and saves the company money"
That is taking the smart approach but also "being cheap".
There is no "smart approach" to being "cheap" when "cheap" is an override to "doing what's best." No matter how you couch it, it's still - not doing what is best for the company.
XenServer with Support from a Third party is "cheap" compared to support from Citrix. So are you saying anyone that uses NTG for XenServer support is sabotaging their employer?
Of course he's not saying that - the question is... Does NTG have the tools and know how to provide the level of support that the company needs? If yes, then the savings in this case are worthwhile, but if NTG doesn't, then the savings is detrimental because the solution of picking NTG does not solve the problem.
It's bigger than that... do they even need support? Is the cost/value of NTG's support better for the business in question than that from Citrix? We try to make that true as often as possible, but there are certainly times that Citrix is better overall for the customer in question and certainly times that having someone else and other times that having no support is best.
-
@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:
@scottalanmiller said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
I would immediately assume that the word "cheap" is simply used incorrectly, whereas he means, to find the most business cost appropriate solution available.
But that's the inherent mandate that is being overridden by the "cheap" mandate. So you would never state that in a business as it explicitly makes the former no longer the goal.
But the word cheap can be used as "Hey we can buy the proposed system with XY and Z, but this will work for the next two years and saves the company money"
That is taking the smart approach but also "being cheap".
There is no "smart approach" to being "cheap" when "cheap" is an override to "doing what's best." No matter how you couch it, it's still - not doing what is best for the company.
XenServer with Support from a Third party is "cheap" compared to support from Citrix. So are you saying anyone that uses NTG for XenServer support is sabotaging their employer?
Anyone that chooses NTG intentionally when they aren't believed to be the best option for the company is certainly sabotaging the company. That's just another way of saying "hurting them intentionally."
Don't confuse the potential overlap of cheap and best with the goal of being cheap instead of best.
And if cheap is the driver, you'd never choose NTG, you'd choose nothing at all.
You've said cheap should never be the business goal, the business goal is to be profitable.
A cheap alternative to Citrix Support would be NTG support.
So being cheap in this case, and by your defined argument means, the decision to be "cheap" is detrimental as they should choose Citrix for support every time.
-
@DustinB3403 said in A Mandate to Be Cheap:
So he's essentially said using the cheapest option (free xenserver and support from NTG) is detrimental to the business.
Cheapest option is always no support at all. When cheap is the driver, support is out of the question completely.
-
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
I know my boss "wants the cheapest option" but I also know that she wants what I believe to be a viable good, even if not best, solution. I think most SMB probably uses the term cheap incorrectly. They, like many of us, just don't communicate well.
Everyone wants cheap.... when it is also what is best. But what is best is what is important. In the OP's case... he feels that they want cheap instead of what is best. Sure they might overlap from time to time, or even often, but the decision criteria is that what is best is not the driving factor.
Whether an SMB uses cheap correctly or incorrectly isn't the problem, the issue is that there is an inherent mandate to do what is best that we all are supposed to follow (that's the job of IT) until politics of the organization mandate that we do something else.
In the OP's case, they've made him feel that his goals are not to do what is best for the company.
So there's a few things there - Why does the OP feel that way? It is because it's true? i.e. he proposes X and they always hack it down to Y which doesn't really meet the goals of the purchase, but it works, and they've been doing that so long that they think they will forever continue to be lucky (but really they just always think the IT person is shooting for the moon, so they assume they can always just hack and slash the IT suggestion since they've never been bit before)?
-
And I know of very few businesses that would say it must be Free
Free is just dangerous, as it's all on "you" to maintain. Sure you save 100% of the cost.
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.
-
A better example than support would be say Access Points (APs).
The solution calls for 10 APs, but management wants to be cheep, so they only install 5. A year goes by and 99% of the time WiFi works just fine (and from a management perspective it's 100% because they personally haven't been affected) so now management looks at IT and says why did you want 10, clearly 5 have done the job. Now management doesn't trust that IT is doing their job as efficiently as they could have, and questions everything going forward.
-
Cheap is one of those subjective words as well... What @DustinB3403 thinks is cheap, what I think is cheap, and what @scottalanmiller thinks is cheap can all be different things.
-
@Dashrender said in A Mandate to Be Cheap:
A better example than support would be say Access Points (APs).
The solution calls for 10 APs, but management wants to be cheep, so they only install 5. A year goes by and 99% of the time WiFi works just fine (and from a management perspective it's 100% because they personally haven't been affected) so now management looks at IT and says why did you want 10, clearly 5 have done the job. Now management doesn't trust that IT is doing their job as efficiently as they could have, and questions everything going forward.
I've been in this specific scenario, except for 1 or 2 APs vs 5 or 10... Initially things worked well...but as the APs aged, the device radios got weaker and weaker. So we got to explain to the president of the campus why we suggested 2 APs to start with.
-
@DustinB3403 said in A Mandate to Be Cheap:
And I know of very few businesses that would say it must be Free
Free is just dangerous, as it's all on "you" to maintain. Sure you save 100% of the cost.
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.
But if it doesn't solve the problem you're trying to solve, then what difference does the cost make? So to use your example, if you buy the 'cheaper' NTG option, yet they can't fix your problems, did you really get the cheaper option? I'd say no, instead you just wasted money.
-
@Dashrender said in A Mandate to Be Cheap:
A better example than support would be say Access Points (APs).
The solution calls for 10 APs, but management wants to be cheep, so they only install 5. A year goes by and 99% of the time WiFi works just fine (and from a management perspective it's 100% because they personally haven't been affected) so now management looks at IT and says why did you want 10, clearly 5 have done the job. Now management doesn't trust that IT is doing their job as efficiently as they could have, and questions everything going forward.
This is a good example, and it could be proven that "well do you need 10 AP's here is the documentation to prove it"
Which you could run a heat map, and check the coverage of the AP's and performance monitoring etc.
-
Additionally, in the case of support, you can generally buy time and materials support. So that might be the best solution of all.
If you never use it, it costs you nothing. If you do use it, it MIGHT cost more than it did with a maintenance contract, but considering the time value of money, etc you still might be ahead.
-
@Dashrender said in A Mandate to Be Cheap:
@scottalanmiller said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
I know my boss "wants the cheapest option" but I also know that she wants what I believe to be a viable good, even if not best, solution. I think most SMB probably uses the term cheap incorrectly. They, like many of us, just don't communicate well.
Everyone wants cheap.... when it is also what is best. But what is best is what is important. In the OP's case... he feels that they want cheap instead of what is best. Sure they might overlap from time to time, or even often, but the decision criteria is that what is best is not the driving factor.
Whether an SMB uses cheap correctly or incorrectly isn't the problem, the issue is that there is an inherent mandate to do what is best that we all are supposed to follow (that's the job of IT) until politics of the organization mandate that we do something else.
In the OP's case, they've made him feel that his goals are not to do what is best for the company.
So there's a few things there - Why does the OP feel that way? It is because it's true? i.e. he proposes X and they always hack it down to Y which doesn't really meet the goals of the purchase, but it works, and they've been doing that so long that they think they will forever continue to be lucky (but really they just always think the IT person is shooting for the moon, so they assume they can always just hack and slash the IT suggestion since they've never been bit before)?
I asked about the "is it true" part. He only said that he felt it, not that it was stated. So that's certainly an issue. He needs to find out if doing things not in the interest of the business' bottom line is really what he is supposed to do.
Understanding that prioritizing cheap means deprioritizing the overall value to the business is the first step. Then you are ready for a conversation: "Do you REALLY mean to imply that I should sacrifice business success in exchange for this different priority? Or did I get that wrong?"
-
@Dashrender said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
And I know of very few businesses that would say it must be Free
Free is just dangerous, as it's all on "you" to maintain. Sure you save 100% of the cost.
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.
But if it doesn't solve the problem you're trying to solve, then what difference does the cost make? So to use your example, if you buy the 'cheaper' NTG option, yet they can't fix your problems, did you really get the cheaper option? I'd say no, instead you just wasted money.
The goal of most businesses is to support the infrastructure, not troubleshoot the source code.
So 99.999999% of the time the solution works perfectly.
-
@DustinB3403 said in A Mandate to Be Cheap:
And I know of very few businesses that would say it must be Free
Really no different than prioritizing cheap. Once cheap is the priority, essentially everything in IT can be free. So that's the obvious result of that priority.
-
@DustinB3403 said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
A better example than support would be say Access Points (APs).
The solution calls for 10 APs, but management wants to be cheep, so they only install 5. A year goes by and 99% of the time WiFi works just fine (and from a management perspective it's 100% because they personally haven't been affected) so now management looks at IT and says why did you want 10, clearly 5 have done the job. Now management doesn't trust that IT is doing their job as efficiently as they could have, and questions everything going forward.
This is a good example, and it could be proven that "well do you need 10 AP's here is the documentation to prove it"
Which you could run a heat map, and check the coverage of the AP's and performance monitoring etc.
we're talking about management here, documentation, smockumentation - they don't need no documentation.. they look around and say.. see, we've been running for 1 year - I know of no problems.. you're just an over spender. It's the difference between being a business person and being and 'owner'.
-
@Dashrender said in A Mandate to Be Cheap:
@DustinB3403 said in A Mandate to Be Cheap:
@Dashrender said in A Mandate to Be Cheap:
A better example than support would be say Access Points (APs).
The solution calls for 10 APs, but management wants to be cheep, so they only install 5. A year goes by and 99% of the time WiFi works just fine (and from a management perspective it's 100% because they personally haven't been affected) so now management looks at IT and says why did you want 10, clearly 5 have done the job. Now management doesn't trust that IT is doing their job as efficiently as they could have, and questions everything going forward.
This is a good example, and it could be proven that "well do you need 10 AP's here is the documentation to prove it"
Which you could run a heat map, and check the coverage of the AP's and performance monitoring etc.
we're talking about management here, documentation, smockumentation - they don't need no documentation.. they look around and say.. see, we've been running for 1 year - I know of no problems.. you're just an over spender. It's the difference between being a business person and being and 'owner'.
A business owner should understand the value of the people they have employed. Without understanding that, the owner would look around and immediately think everyone employed by them is there to rob from them.
-
@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?
-
@DustinB3403 said in A Mandate to Be Cheap:
A business owner should understand the value of the people they have employed. Without understanding that, the owner would look around and immediately think everyone employed by them is there to rob from them.
Of course they should but you can read countless encounters where they don't. Hell, I think you've given some of those points from time to time.... i.e. you're dealing with learning XO instead of just purchasing a know good working backup product. Of the fact that your company won't shell out the $900/yr for XOA which would keep you from having to jump through hoops to keep XO updated manually, etc.
-
@dafyre said in A Mandate to Be Cheap:
Cheap is one of those subjective words as well... What @DustinB3403 thinks is cheap, what I think is cheap, and what @scottalanmiller thinks is cheap can all be different things.
Not really. Cheap means "cost less to acquire". Or "you spend less". Cheaper means that one is less than another. Cheapest is free or as close to free as possible. Saying something "is cheap" is subjective, but that's not involved here. Prioritizing cheap means that "spending less up front" is more important than everything else, like "value to the business".
