When Technical Meets Non-Technical
-
@scottalanmiller said:
Do you have any ability to select which coworkers you consult with? Are you limited to that one? What is their job that they are a non-technical coworker that you are being asked to talk to?
No, I don't have to consult with this one co-worker, but the point is that there is no policy stating we have to consult with each other or this client for performing this action. My co-worker, I feel, is probably misinterpreting something they heard about something else due to their non-technical nature and background.
-
Do I understand that you approached this co-worker for feedback, and that's when they disagreed with your lack of confirmation with other co-workers before acting?
Does you MSP run solutions by committee? The few I've worked with don't. The tech assigned generally makes all the calls as needed, when they don't know they escalate.
-
@Dashrender said:
Do I understand that you approached this co-worker for feedback, and that's when they disagreed with your lack of confirmation with other co-workers before acting?
Does you MSP run solutions by committee? The few I've worked with don't. The tech assigned generally makes all the calls as needed, when they don't know they escalate.
Remember that not all MSP's operate like NTG does working as a TEAM to cover for each other.
-
@Dashrender said:
Do I understand that you approached this co-worker for feedback, and that's when they disagreed with your lack of confirmation with other co-workers before acting?
Does you MSP run solutions by committee? The few I've worked with don't. The tech assigned generally makes all the calls as needed, when they don't know they escalate.
A case I was working yesterday (when it first opened) was handed off to them today from the previous shift. An email was sent to our distro list by the provider recommending we clear the counters. I just asked them if they'd seen the email with the request by the provider, and that's when they went off on me about this and how I do this totally wrong. I kept saying how I just wanted to make sure they'd seen the email and I wasn't there to argue and kept trying to leave it at that, but they wouldn't drop it.
We don't really run solutions by a committee. If it's something we don't know how to handle, we ask co-workers and escalate as necessary. We can also have duty managers take over cases, etc. But as a rule, whoever has the case makes the call if it's not a specified policy on what to do.
-
@Minion-Queen said:
@Dashrender said:
Do I understand that you approached this co-worker for feedback, and that's when they disagreed with your lack of confirmation with other co-workers before acting?
Does you MSP run solutions by committee? The few I've worked with don't. The tech assigned generally makes all the calls as needed, when they don't know they escalate.
Remember that not all MSP's operate like NTG does working as a TEAM to cover for each other.
Yeah, I miss that.
-
@Minion-Queen said:
@Dashrender said:
Do I understand that you approached this co-worker for feedback, and that's when they disagreed with your lack of confirmation with other co-workers before acting?
Does you MSP run solutions by committee? The few I've worked with don't. The tech assigned generally makes all the calls as needed, when they don't know they escalate.
Remember that not all MSP's operate like NTG does working as a TEAM to cover for each other.
Same for internal IT. Some teams, like where I am now, take team ownership of projects and everything is done while consulting each other. Others, like the large bank I was at, had projects and systems with individual owners who took individual responsibility for systems.
-
@handsofqwerty said:
@Dashrender said:
Do I understand that you approached this co-worker for feedback, and that's when they disagreed with your lack of confirmation with other co-workers before acting?
Does you MSP run solutions by committee? The few I've worked with don't. The tech assigned generally makes all the calls as needed, when they don't know they escalate.
A case I was working yesterday (when it first opened) was handed off to them today from the previous shift. An email was sent to our distro list by the provider recommending we clear the counters. I just asked them if they'd seen the email with the request by the provider, and that's when they went off on me about this and how I do this totally wrong. I kept saying how I just wanted to make sure they'd seen the email and I wasn't there to argue and kept trying to leave it at that, but they wouldn't drop it.
We don't really run solutions by a committee. If it's something we don't know how to handle, we ask co-workers and escalate as necessary. We can also have duty managers take over cases, etc. But as a rule, whoever has the case makes the call if it's not a specified policy on what to do.
Did a manager say you were doing things wrong? Or just someone non-technical outside of your job?
-
@Minion-Queen said:
@Dashrender said:
Do I understand that you approached this co-worker for feedback, and that's when they disagreed with your lack of confirmation with other co-workers before acting?
Does you MSP run solutions by committee? The few I've worked with don't. The tech assigned generally makes all the calls as needed, when they don't know they escalate.
Remember that not all MSP's operate like NTG does working as a TEAM to cover for each other.
Not sure what you mean? If I hire and MSP I fully EXPECT them to work as a team to cover for each other, otherwise why am I with you? Only exception is a one man shop.
-
Most MSP's really do work based on an Account Manager being fully responsible for the client. And honestly most of them are such small shops they really don't have a team to rely on.
-
@scottalanmiller said:
@handsofqwerty said:
@Dashrender said:
Do I understand that you approached this co-worker for feedback, and that's when they disagreed with your lack of confirmation with other co-workers before acting?
Does you MSP run solutions by committee? The few I've worked with don't. The tech assigned generally makes all the calls as needed, when they don't know they escalate.
A case I was working yesterday (when it first opened) was handed off to them today from the previous shift. An email was sent to our distro list by the provider recommending we clear the counters. I just asked them if they'd seen the email with the request by the provider, and that's when they went off on me about this and how I do this totally wrong. I kept saying how I just wanted to make sure they'd seen the email and I wasn't there to argue and kept trying to leave it at that, but they wouldn't drop it.
We don't really run solutions by a committee. If it's something we don't know how to handle, we ask co-workers and escalate as necessary. We can also have duty managers take over cases, etc. But as a rule, whoever has the case makes the call if it's not a specified policy on what to do.
Did a manager say you were doing things wrong? Or just someone non-technical outside of your job?
A peer who works the same client. I've never had a manager approach me saying anything in regards to anything I've done wrong with this client and my technical work has never been scrutinized. I've just had them (my managers) update me on policy stuff, such as who I should have reached out to instead, or in addition to, etc.
-
@Dashrender said:
@Minion-Queen said:
@Dashrender said:
Do I understand that you approached this co-worker for feedback, and that's when they disagreed with your lack of confirmation with other co-workers before acting?
Does you MSP run solutions by committee? The few I've worked with don't. The tech assigned generally makes all the calls as needed, when they don't know they escalate.
Remember that not all MSP's operate like NTG does working as a TEAM to cover for each other.
Not sure what you mean? If I hire and MSP I fully EXPECT them to work as a team to cover for each other, otherwise why am I with you? Only exception is a one man shop.
That's definitely not the norm. But you also have to realize that lots of clients don't want team work, they want accountability. It is very common in IT to "expect" a certain behaviour without it being stated but rarely does that match what many customers want.
The idea behind an MSP is not to make the work be a team. That's a benefit that some MSPs, like NTG, provide for you. But remember that the average MSP is only one or two people and so conceptually getting a team rather than a person isn't even possible. Often an MSP is a one man shop too and has to do all the business stuff AND the IT stuff so you are only getting a part time IT resource.
-
@Minion-Queen said:
Most MSP's really do work based on an Account Manager being fully responsible for the client. And honestly most of them are such small shops they really don't have a team to rely on.
My guess would be that 90% of MSPs don't have more than a single full time IT person (but many might have one full and one part.)
-
@handsofqwerty said:
A peer who works the same client.
A peer would imply that they are an IT resource.
-
@scottalanmiller said:
@handsofqwerty said:
A peer who works the same client.
A peer would imply that they are an IT resource.
They do the same kind of work I do, but they do it from a procedural standpoint. They know if they get alert A, they do X, Y and Z. They don't really understand what they're looking at, and honestly, they don't have to for the position they're in. They just have to know what to look for, and if it is what it's supposed to be, do this. Otherwise, do that.
-
I want a part timer
-
@handsofqwerty said:
@scottalanmiller said:
@handsofqwerty said:
A peer who works the same client.
A peer would imply that they are an IT resource.
They do the same kind of work I do, but they do it from a procedural standpoint. They know if they get alert A, they do X, Y and Z. They don't really understand what they're looking at, and honestly, they don't have to for the position they're in. They just have to know what to look for, and if it is what it's supposed to be, do this. Otherwise, do that.
They don't seem to be a good candidate for bouncing ideas off of then.
-
@scottalanmiller said:
@handsofqwerty said:
@scottalanmiller said:
@handsofqwerty said:
A peer who works the same client.
A peer would imply that they are an IT resource.
They do the same kind of work I do, but they do it from a procedural standpoint. They know if they get alert A, they do X, Y and Z. They don't really understand what they're looking at, and honestly, they don't have to for the position they're in. They just have to know what to look for, and if it is what it's supposed to be, do this. Otherwise, do that.
They don't seem to be a good candidate for bouncing ideas off of then.
I don't. If I have a question, I never go to this person. They had a case assigned to them this morning. An email came in regarding taking an action on the case, and all I did was ask if they'd seen the email. Then all this started.
-
So they don't even know if you are consulting with other people or not?
-
@scottalanmiller said:
So they don't even know if you are consulting with other people or not?
This co-worker sits about 12 feet from me. They are in their own little world most of the time, because I know it takes many times the concentration for them to do what I can do practically in my sleep. I've spent a great deal of time making myself more efficient, writing macros to do common tasks to improve speed and efficiency, etc. But they don't monitor everything I do, AFAIK. Technically there is no way they could know if I did consult or not, because I could have emailed or chatted with someone directly, and they wouldn't know.
-
So I guess the question is... what is the question? Sounds like a random person spouting off about something they have not observed, have nothing to do with and aren't your manager in any way?
