Ttyjfyk

Ask your manager what he or she wants you to do.

Obviously helping out another team is going to take time, particularly if they have an ongoing set of problems. It's going to cut into whatever else you are working on. It's your manager's job to decide whether you should take that time or not.

Talk to your manager, without bringing up the attitude of the other team or the other manager. Just lay it out... you've spent this amount of time so far, you think it will take this much more time, and likely there will be additional issues that will require more time. Should you break off what you are working on and help out the other team?

Your manager gets to decide, and is also up to date on how the schedule is impacted. And if the answer is "no", your manager is the one who talks to the other team's manager and lets them know you aren't available.

"Sorry, I'm busy with task X"

Don't elaborate. You want to keep the conversation firmly grounded in the current reality and avoid any comments that give credence to the idea that you might be in some way involved in their project (e.g. "I don't want to help this person who could use google" implies that you could or should help them).

If you are later accused of being unhelpful then stick to this line. Don't refuse to help, just say that you tried to help but felt obliged to prioritise your own work. i.e. to do the thing you were told to do.

Ultimately you might be tasked with babysitting the person but you can and should make them go through formal channels to request the babysitting.

I would take a couple approaches at the same time:

1. First, teach her to find her own answers. This may seem odd and "not my job" but it's a way to help others help themselves and take some of the burden off of you to fix all their problems. Ask questions like, "What did you find when you googled that error message?", "Have you googled how to configure X?", etc. Given time, that will train others that you expect that before they ask you a question, they will do at least some initial research and won't receive help from you until they do.


2. 
   

   Second, put the responsibility back on her and explain (briefly) why.

   
   
   

   
   

   When I helped you before, I had hoped to offer a few quick tips to get you unstuck. I'm sorry I can't be more help but I haven't been tasked by my manager to help with your project and don't have more time to spend on it without my manager's approval.

   
   

   
   

At this point I think you can go a few ways, you can 1. approach your manager to ask for time to help, 2. put it back on her to ask your manager if you can help her, or 3. just leave it there.

If she persists, talk to your manager. Explain your initial attempts to help but that you don't have the kind of time to spend on a regular, ongoing basis to help her. That said... be prepared for your manager to say to help her. In that case I would stick to #1 but help after a reasonable effort has been put into finding a solution.

This is a case where corporate bureaucracy can be your friend.

Them: How do I check if a file exists?

You: Great question. If you need our team's input, create a Task in Company Task App so my manager can put it in my queue. Thanks!

At the end she says "I'm going to bug you again tomorrow".

Response:

Actually I'm going to be pretty busy tomorrow. I've been happy to help out so far but maybe you should talk to $Boss about getting some more assistance? I kinda need to focus on my own work now! Sorry…

This is deliberately tailored for the scenario you describe, and I wouldn't use it except that they've started bugging you frequently, with evidence that they've stopped really bothering to try to solve things on their own (right down to the declarative, and frankly entitled nature of their parting line). It's fine to be firm and to push back. And if that feels unfair, just remind yourself that you're also helping them in the long run.

I'd also casually mention what's been going on to your own manager, not by way of complaining, but by way of laying the groundwork in case the colleague doesn't stop and you have to bring in the heavy guns later on. Though this suggestion depends: if my manager were trigger-happy and I got the impression this might get the colleague into trouble or otherwise cause more of a reaction than necessary, I'd consider just keeping it to myself for the time being. After all, you don't have to report every workplace conversation to your manager, until it's genuinely become a problem.

I faced the quite same situation, and I'd like to share how I get out of it.

At first, I got asked for questions from time to time. Later, I became the "automatic" question solver man. Since this situation installed gradually, I started gradually pushing it back:

Step 1: Delay my (too many) answers

• "I can't check with you now, but you can get back later. Can you please come back at ...?"


• "I may have a solution... I'll get back to you later."


• "Can you please send me an email with details X and Y. I'll reply back."

Step 2: Re-orient towards another problem solver

• "The document 'XXX' has exactly your answer. Check page 7..."


• "Let's check together. This web search engine spits out quite interesting links. What about you checking this result or this other one?"


• "I'm sorry. Please see with person Z (or service Z). They know this subject better than me."

Step 3: Give a clear push back (to the insisting askers)

• "I don't know."


• "I don't have a clue."


• Check your head quickly from left to right as "no-no".

This last action gets the last insisting askers out.

You have indicated that multiple people on another team have been floundering for days on a problem and that you could, in a day, resolve their setup issue.

The right thing to do is to help them. It will, eventually, unlock their productivity and help your organization as a whole.

That said, yes, I agree it was not right for them to take an entitled attitude with you, and they should NOT expect unlimited ad-hoc help from you whenever they request it.

I totally disagree, however, with some other other answers and comments that each team has their work and that you should "cut them off". The proper thing to do, is to put a structure and limits on your labor to help them. This may mean management needs to be involved and that both you and the other team need to formalize the arrangement.

I know folks on Stack Exchange sites like the Stack Overflow philosophy that dismisses questioning and knowledge-seeking without some very high standard of prior-proof-of-work demanded of the asker. But that's not how workplaces actually function.

You're paid, they're paid, and the organization needs work done. If you refuse helping them and it is later discovered that they burned months of time doing something that you could have helped clear up in hours, that will reflect badly upon you more than them.

All of the above answers have been a "hold the high ground," but for someone who demands your help and gives nothing back, they will have a higher chance of eventually taking credit for your work too. The best outcome is for them to leave the company or group.

Approach 1 - Their Boss Gets Mad

The passive aggressive, highly competitive response is to provide answers that are wrong, unproductive, or will make them look stupid. If they are thinking about the problem and call you out on it right there, then treat them to an overpriced coffee^[1] and talk about help being a two-way street.

If they blindly take your deliberately bad advice, because they are in over their head only to fail, they will cast the blame on you for sabotaging them. If it's known that you have helped in the past, they will still blame you for their failure. If possible, you need to deny ever providing any substantial help at all, because you have clear direction to focus on your task, even though this may be a lie.

Approach 2 - Your Boss Gets Mad

Alternatively, you can start to tell your boss that they have been trying to sabotage your work because you refuse to sacrifice your project schedule. This is lying, but moves the focus back to the other employee. It also gives you a chance to be creative at work.

Discussion

Both cases assume that management on both sides lacks the backbone to resolve this problem, a situation I see frequently.

I don't personally have the stomach for either approach as it goes against my ethos, but book and TV script authors^[2] seem to think that these things work. I would probably end up complaining to HR that this individual is creating a hostile work environment. A competent HR manager should recognize as a threat of lawsuit brewing and work down through senior management.

But narcissistic and belligerent people can be unwilling to change and must ultimately be evicted; make them cost the company money or embarrassment if management lacks the courage to do the right thing early.

Or, you can read Dale Carnegie's "How to Win Friends and Influence People". Learn. Apply.

_{[1.] This is a psychology trick to incur a social debt which can simply be repaid by the individual learning to be grateful. When they learn to show gratitude, another psychology trick kicks in and they will learn to respect your time.
[2.] The TV show Billions comes to mind.}