What Does Calling an Application Mission Critical Mean
-
@Dashrender said in What Does Calling an Application Mission Critical Mean:
If you open the statement after someone posts about their setup with - huh, that's less than the home line, then you are snobbish and arrogant.
Of course I haven't read the post, so I don't know how you opened it.Another way to think of it is that their embarrassment is not a result of my arrogance.
They had emotional baggage because their scenario was, honestly, embarrassing. Instead of embracing that, they tried to raise the stakes by trying to sound extra important rather than just admitting failure and mistakes. Saying something needs to be mission critical but they screwed something up is one thing and results in direct help. Saying something needs to be mission critical and using that to excuse treating it exactly the opposite... well the only useful help there is helping them to determine if they understand the terms that they are using. Since their words and actions are in conflict, we have to help them work through determining what is "true". And in this case, it does not appear to be just the IT guy, but the company itself. The company seems to put no priority on the application and/or the IT guy is failing to do his job in explaining the risks and costs.
-
@scottalanmiller said in What Does Calling an Application Mission Critical Mean:
@Dashrender said in What Does Calling an Application Mission Critical Mean:
If you open the statement after someone posts about their setup with - huh, that's less than the home line, then you are snobbish and arrogant.
Of course I haven't read the post, so I don't know how you opened it.Another way to think of it is that their embarrassment is not a result of my arrogance.
They had emotional baggage because their scenario was, honestly, embarrassing. Instead of embracing that, they tried to raise the stakes by trying to sound extra important rather than just admitting failure and mistakes. Saying something needs to be mission critical but they screwed something up is one thing and results in direct help. Saying something needs to be mission critical and using that to excuse treating it exactly the opposite... well the only useful help there is helping them to determine if they understand the terms that they are using. Since their words and actions are in conflict, we have to help them work through determining what is "true". And in this case, it does not appear to be just the IT guy, but the company itself. The company seems to put no priority on the application and/or the IT guy is failing to do his job in explaining the risks and costs.
That's all well and good - but you know you're dealing with human beings, right? Most aren't as purely analytical as you.
At the same time, I agree that we (IT people in general) need to put our egos aside and solve a problem.
-
@Dashrender said in What Does Calling an Application Mission Critical Mean:
@scottalanmiller said in What Does Calling an Application Mission Critical Mean:
@Dashrender said in What Does Calling an Application Mission Critical Mean:
If you open the statement after someone posts about their setup with - huh, that's less than the home line, then you are snobbish and arrogant.
Of course I haven't read the post, so I don't know how you opened it.Another way to think of it is that their embarrassment is not a result of my arrogance.
They had emotional baggage because their scenario was, honestly, embarrassing. Instead of embracing that, they tried to raise the stakes by trying to sound extra important rather than just admitting failure and mistakes. Saying something needs to be mission critical but they screwed something up is one thing and results in direct help. Saying something needs to be mission critical and using that to excuse treating it exactly the opposite... well the only useful help there is helping them to determine if they understand the terms that they are using. Since their words and actions are in conflict, we have to help them work through determining what is "true". And in this case, it does not appear to be just the IT guy, but the company itself. The company seems to put no priority on the application and/or the IT guy is failing to do his job in explaining the risks and costs.
That's all well and good - but you know you're dealing with human beings, right? Most aren't as purely analytical as you.
Right, but that's his job. Condescending to him isn't the right response.
-
@scottalanmiller said in What Does Calling an Application Mission Critical Mean:
@Dashrender said in What Does Calling an Application Mission Critical Mean:
@scottalanmiller said in What Does Calling an Application Mission Critical Mean:
@Dashrender said in What Does Calling an Application Mission Critical Mean:
If you open the statement after someone posts about their setup with - huh, that's less than the home line, then you are snobbish and arrogant.
Of course I haven't read the post, so I don't know how you opened it.Another way to think of it is that their embarrassment is not a result of my arrogance.
They had emotional baggage because their scenario was, honestly, embarrassing. Instead of embracing that, they tried to raise the stakes by trying to sound extra important rather than just admitting failure and mistakes. Saying something needs to be mission critical but they screwed something up is one thing and results in direct help. Saying something needs to be mission critical and using that to excuse treating it exactly the opposite... well the only useful help there is helping them to determine if they understand the terms that they are using. Since their words and actions are in conflict, we have to help them work through determining what is "true". And in this case, it does not appear to be just the IT guy, but the company itself. The company seems to put no priority on the application and/or the IT guy is failing to do his job in explaining the risks and costs.
That's all well and good - but you know you're dealing with human beings, right? Most aren't as purely analytical as you.
Right, but that's his job. Condescending to him isn't the right response.
Where did I or anyone ask you to condescend to him? Tim didn't call his setup names, he simply pointed out how not patching wasn't a mission critical setup. He got the same points across that you did without insulting him.
-
@Dashrender said in What Does Calling an Application Mission Critical Mean:
@scottalanmiller said in What Does Calling an Application Mission Critical Mean:
@Dashrender said in What Does Calling an Application Mission Critical Mean:
@scottalanmiller said in What Does Calling an Application Mission Critical Mean:
@Dashrender said in What Does Calling an Application Mission Critical Mean:
If you open the statement after someone posts about their setup with - huh, that's less than the home line, then you are snobbish and arrogant.
Of course I haven't read the post, so I don't know how you opened it.Another way to think of it is that their embarrassment is not a result of my arrogance.
They had emotional baggage because their scenario was, honestly, embarrassing. Instead of embracing that, they tried to raise the stakes by trying to sound extra important rather than just admitting failure and mistakes. Saying something needs to be mission critical but they screwed something up is one thing and results in direct help. Saying something needs to be mission critical and using that to excuse treating it exactly the opposite... well the only useful help there is helping them to determine if they understand the terms that they are using. Since their words and actions are in conflict, we have to help them work through determining what is "true". And in this case, it does not appear to be just the IT guy, but the company itself. The company seems to put no priority on the application and/or the IT guy is failing to do his job in explaining the risks and costs.
That's all well and good - but you know you're dealing with human beings, right? Most aren't as purely analytical as you.
Right, but that's his job. Condescending to him isn't the right response.
Where did I or anyone ask you to condescend to him? Tim didn't call his setup names, he simply pointed out how not patching wasn't a mission critical setup. He got the same points across that you did without insulting him.
Where do you get the impression that I insulted him?
-
If telling someone that their setup is not mission critical when they say that it is is itself considered to be insulting, then how was Tim informing of him not also insulting? By that logic, both your and Tim's posts informing him that that is not MC would have been equally insulting.
-
Here is my quote: "You cant say that AND say mission critical. This makes the business see this server as a hobby, no words that they say match the actions that tell the real story of the priority that they have given the system. Important to patch now, yes, of course. But mission critical? That's only possible if the mission itself is seen as being unimportant - below the home line."
Nothing insulting here. Only pointed it out first. The server is below the home line, which is an important distinction that this cannot be classified as a well maintained hobby. None of this was about him, other than him repeating false information from the business, which is absolutely critical, as we know, that honesty, accuracy and semantics are the core of IT. You can play around with terms, that's how bad things happen. If this is their mission critical, how could they ever discuss something if it really mattered?
I pointed out that the business' actions, not his, told a different story than the words used.
If he felt that this was insulting, it could only have happened if he was carrying guilt about this or other emotional baggage that was not included in his or my posts.
-
I was quite clear in explaining that the business saw the system as a hobby and that he could not use terms like mission critical about a system that was being treated as it was. Businesses are not subject to emotional needs or being offended. The business is what it is, apparently a hobby.
-
If you go further in the thread, you'll notice that my next post, which is actually the OP of this post, was not "things you did wrong" or anything of the sort. We had already sorted him as far as what to do about his patches. This post was "things to discuss with your management that THEY are getting wrong and need to understand." Nowhere was HE at fault or blamed (other than repeating the false classification of the server) but he was empowered to go to the business and explain to them that they either need to act like a business or accept that they are not mission critical.
-
You definitely provided the requested assistance, but you seemed to go out of your way first to tell him how wrong the thinking is.
I'm fine with giving your opinion on the wrongness of the setup, but why not wait to have a conversation after the problem is resolved, not beforehand?
-
@Dashrender said in What Does Calling an Application Mission Critical Mean:
I'm fine with giving your opinion on the wrongness of the setup, but why not wait to have a conversation after the problem is resolved, not beforehand?
Why wait, it only takes a second and is more efficient to do things in order. I still had that post AND the one that had the answer of what to do before anyone else had even responded.
But it might be important. What if he only reads the first one before some disaster happens? Knowing that the business was not taking their systems seriously might be the most important thing that he gleaned from this. That might be what is needed to take someone from panic to reality. It might be what they need to march up to management and demand that people rethink blowing off good IT needs.
-
@DustinB3403 said in What Does Calling an Application Mission Critical Mean:
@Tim_G said in What Does Calling an Application Mission Critical Mean:
Mission Critical Application = Company literally making money while running, company literally losing money while down.
Imo anyways.
No such application should exist in the world today, besides the stock market. . .
I mean, that's literally a bit miner
-
@scottalanmiller said in What Does Calling an Application Mission Critical Mean:
Knowing that the business was not taking their systems seriously might be the most important thing that he gleaned from this.
While I see what you're saying... I just don't buy it. the chances that a person would read your post and turn around and return to management and instead of being in a panic over patching say - hey, this is your bloody fault.. now what are you going to do about making sure this doesn't happen again? the answer is only SAM would do that, not another person I know personally.
-
@Dashrender said in What Does Calling an Application Mission Critical Mean:
@scottalanmiller said in What Does Calling an Application Mission Critical Mean:
Knowing that the business was not taking their systems seriously might be the most important thing that he gleaned from this.
While I see what you're saying... I just don't buy it. the chances that a person would read your post and turn around and return to management and instead of being in a panic over patching say - hey, this is your bloody fault.. now what are you going to do about making sure this doesn't happen again? the answer is only SAM would do that, not another person I know personally.
You base the value on what you see as people likely doing, and there is rational to that. I'm basing it off what they are empowered to do. I like to give more options, faster. How they choose to leverage that is then up to them, but the info that they need is in their hands.
