My colleague always ask for help. Should I help him always?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
2
down vote
favorite
So my colleague always or at least most of the times ask for my help like he expects me to explain everything from scratch for every project. He wants to learn but doesn't quite catch up everything that I explain him. I would feel bad if I don't help him also at the same time I can't afford to lose too much time behind this.
What should I do ?
management communication work-experience project-management teamwork
suggest improvements |Â
up vote
2
down vote
favorite
So my colleague always or at least most of the times ask for my help like he expects me to explain everything from scratch for every project. He wants to learn but doesn't quite catch up everything that I explain him. I would feel bad if I don't help him also at the same time I can't afford to lose too much time behind this.
What should I do ?
management communication work-experience project-management teamwork
Always - No. As much as feasible - Yes.
– PM 77-1
Nov 1 '15 at 5:13
Related: workplace.stackexchange.com/questions/9623/…, workplace.stackexchange.com/questions/5769/….
– Monica Cellio♦
Nov 1 '15 at 18:59
suggest improvements |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
So my colleague always or at least most of the times ask for my help like he expects me to explain everything from scratch for every project. He wants to learn but doesn't quite catch up everything that I explain him. I would feel bad if I don't help him also at the same time I can't afford to lose too much time behind this.
What should I do ?
management communication work-experience project-management teamwork
So my colleague always or at least most of the times ask for my help like he expects me to explain everything from scratch for every project. He wants to learn but doesn't quite catch up everything that I explain him. I would feel bad if I don't help him also at the same time I can't afford to lose too much time behind this.
What should I do ?
management communication work-experience project-management teamwork
edited Nov 1 '15 at 13:37


Joe Strazzere
223k104652918
223k104652918
asked Nov 1 '15 at 5:06
Rohan
112
112
Always - No. As much as feasible - Yes.
– PM 77-1
Nov 1 '15 at 5:13
Related: workplace.stackexchange.com/questions/9623/…, workplace.stackexchange.com/questions/5769/….
– Monica Cellio♦
Nov 1 '15 at 18:59
suggest improvements |Â
Always - No. As much as feasible - Yes.
– PM 77-1
Nov 1 '15 at 5:13
Related: workplace.stackexchange.com/questions/9623/…, workplace.stackexchange.com/questions/5769/….
– Monica Cellio♦
Nov 1 '15 at 18:59
Always - No. As much as feasible - Yes.
– PM 77-1
Nov 1 '15 at 5:13
Always - No. As much as feasible - Yes.
– PM 77-1
Nov 1 '15 at 5:13
Related: workplace.stackexchange.com/questions/9623/…, workplace.stackexchange.com/questions/5769/….
– Monica Cellio♦
Nov 1 '15 at 18:59
Related: workplace.stackexchange.com/questions/9623/…, workplace.stackexchange.com/questions/5769/….
– Monica Cellio♦
Nov 1 '15 at 18:59
suggest improvements |Â
2 Answers
2
active
oldest
votes
up vote
4
down vote
Short answer: Teach your colleague to research and learn in the way that you do.
When you find you have a colleague who seems to rely on you as being the source of all information, then something you can do is to teach them how you learn new things. For example, if you colleague asks you about a certain technology or API, then you can say to them:
Have you tried searching for that? What search terms did you use? I would suggest x search term.
Repeat this, each time they have a question that is technology specific.
Now, if they are asking you project specific issues, when you explain something to them the first time, suggest they write it down. If they then ask you the same question again, say something like:
Did you have a look in your notes you took about this? Did it give you enough information?
If they answer, "No I didn't look" then you can point them to do so, but if they say that it didn't cover it, tell them to write the new information down to add to their notes.
Lastly, if they are onboarding to a new or existing project, direct them to the documentation. It can be tech specs, design documents or even function specifications. Answer something like:
Did you check the [insert relevant document here]? What did it say? Where do you find it unclear?
Sooner or later, they will get the message that most information they require is already available and that they need to spend some time doing their own research rather than using up your time to do it. If, however, they have checked the other sources and were unable to find the relevant information, then asking you is the correct action for them to take. But make them write it down! :)
suggest improvements |Â
up vote
0
down vote
Don't let your colleagues learning issues impact on your own work. Help when it's convenient and you feel like it, don't when it's not. Otherwise he/she may just lean on you all the time which it looks like is already happening.
Just be firm, they might get a bit upset, but that's life, you don't want to be someone else's crutch through their career. They'll get the picture eventually and find another crutch. The workplace can be a competitive environment, teaching others is not your task unless you're a teacher.
I'm pretty upfront when I keep getting pestered with issues that seem too simple and when they require long winded explanations... my response is "You need to work that out for yourself. Let me know if you get stuck and I'll see what I can do later." then by the time they've researched it for half an hour they've normally solved it themselves. All I did was take away the easy option of picking my brain for the answer.
If your colleague is incompetent it can work to your advantage by making you look better. If they get removed, that's life, and most people would prefer to work with colleagues who can handle their jobs, it makes everything go smoother and uplifts the whole team.
suggest improvements |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
4
down vote
Short answer: Teach your colleague to research and learn in the way that you do.
When you find you have a colleague who seems to rely on you as being the source of all information, then something you can do is to teach them how you learn new things. For example, if you colleague asks you about a certain technology or API, then you can say to them:
Have you tried searching for that? What search terms did you use? I would suggest x search term.
Repeat this, each time they have a question that is technology specific.
Now, if they are asking you project specific issues, when you explain something to them the first time, suggest they write it down. If they then ask you the same question again, say something like:
Did you have a look in your notes you took about this? Did it give you enough information?
If they answer, "No I didn't look" then you can point them to do so, but if they say that it didn't cover it, tell them to write the new information down to add to their notes.
Lastly, if they are onboarding to a new or existing project, direct them to the documentation. It can be tech specs, design documents or even function specifications. Answer something like:
Did you check the [insert relevant document here]? What did it say? Where do you find it unclear?
Sooner or later, they will get the message that most information they require is already available and that they need to spend some time doing their own research rather than using up your time to do it. If, however, they have checked the other sources and were unable to find the relevant information, then asking you is the correct action for them to take. But make them write it down! :)
suggest improvements |Â
up vote
4
down vote
Short answer: Teach your colleague to research and learn in the way that you do.
When you find you have a colleague who seems to rely on you as being the source of all information, then something you can do is to teach them how you learn new things. For example, if you colleague asks you about a certain technology or API, then you can say to them:
Have you tried searching for that? What search terms did you use? I would suggest x search term.
Repeat this, each time they have a question that is technology specific.
Now, if they are asking you project specific issues, when you explain something to them the first time, suggest they write it down. If they then ask you the same question again, say something like:
Did you have a look in your notes you took about this? Did it give you enough information?
If they answer, "No I didn't look" then you can point them to do so, but if they say that it didn't cover it, tell them to write the new information down to add to their notes.
Lastly, if they are onboarding to a new or existing project, direct them to the documentation. It can be tech specs, design documents or even function specifications. Answer something like:
Did you check the [insert relevant document here]? What did it say? Where do you find it unclear?
Sooner or later, they will get the message that most information they require is already available and that they need to spend some time doing their own research rather than using up your time to do it. If, however, they have checked the other sources and were unable to find the relevant information, then asking you is the correct action for them to take. But make them write it down! :)
suggest improvements |Â
up vote
4
down vote
up vote
4
down vote
Short answer: Teach your colleague to research and learn in the way that you do.
When you find you have a colleague who seems to rely on you as being the source of all information, then something you can do is to teach them how you learn new things. For example, if you colleague asks you about a certain technology or API, then you can say to them:
Have you tried searching for that? What search terms did you use? I would suggest x search term.
Repeat this, each time they have a question that is technology specific.
Now, if they are asking you project specific issues, when you explain something to them the first time, suggest they write it down. If they then ask you the same question again, say something like:
Did you have a look in your notes you took about this? Did it give you enough information?
If they answer, "No I didn't look" then you can point them to do so, but if they say that it didn't cover it, tell them to write the new information down to add to their notes.
Lastly, if they are onboarding to a new or existing project, direct them to the documentation. It can be tech specs, design documents or even function specifications. Answer something like:
Did you check the [insert relevant document here]? What did it say? Where do you find it unclear?
Sooner or later, they will get the message that most information they require is already available and that they need to spend some time doing their own research rather than using up your time to do it. If, however, they have checked the other sources and were unable to find the relevant information, then asking you is the correct action for them to take. But make them write it down! :)
Short answer: Teach your colleague to research and learn in the way that you do.
When you find you have a colleague who seems to rely on you as being the source of all information, then something you can do is to teach them how you learn new things. For example, if you colleague asks you about a certain technology or API, then you can say to them:
Have you tried searching for that? What search terms did you use? I would suggest x search term.
Repeat this, each time they have a question that is technology specific.
Now, if they are asking you project specific issues, when you explain something to them the first time, suggest they write it down. If they then ask you the same question again, say something like:
Did you have a look in your notes you took about this? Did it give you enough information?
If they answer, "No I didn't look" then you can point them to do so, but if they say that it didn't cover it, tell them to write the new information down to add to their notes.
Lastly, if they are onboarding to a new or existing project, direct them to the documentation. It can be tech specs, design documents or even function specifications. Answer something like:
Did you check the [insert relevant document here]? What did it say? Where do you find it unclear?
Sooner or later, they will get the message that most information they require is already available and that they need to spend some time doing their own research rather than using up your time to do it. If, however, they have checked the other sources and were unable to find the relevant information, then asking you is the correct action for them to take. But make them write it down! :)
answered Nov 1 '15 at 6:25


Jane S♦
40.8k17125159
40.8k17125159
suggest improvements |Â
suggest improvements |Â
up vote
0
down vote
Don't let your colleagues learning issues impact on your own work. Help when it's convenient and you feel like it, don't when it's not. Otherwise he/she may just lean on you all the time which it looks like is already happening.
Just be firm, they might get a bit upset, but that's life, you don't want to be someone else's crutch through their career. They'll get the picture eventually and find another crutch. The workplace can be a competitive environment, teaching others is not your task unless you're a teacher.
I'm pretty upfront when I keep getting pestered with issues that seem too simple and when they require long winded explanations... my response is "You need to work that out for yourself. Let me know if you get stuck and I'll see what I can do later." then by the time they've researched it for half an hour they've normally solved it themselves. All I did was take away the easy option of picking my brain for the answer.
If your colleague is incompetent it can work to your advantage by making you look better. If they get removed, that's life, and most people would prefer to work with colleagues who can handle their jobs, it makes everything go smoother and uplifts the whole team.
suggest improvements |Â
up vote
0
down vote
Don't let your colleagues learning issues impact on your own work. Help when it's convenient and you feel like it, don't when it's not. Otherwise he/she may just lean on you all the time which it looks like is already happening.
Just be firm, they might get a bit upset, but that's life, you don't want to be someone else's crutch through their career. They'll get the picture eventually and find another crutch. The workplace can be a competitive environment, teaching others is not your task unless you're a teacher.
I'm pretty upfront when I keep getting pestered with issues that seem too simple and when they require long winded explanations... my response is "You need to work that out for yourself. Let me know if you get stuck and I'll see what I can do later." then by the time they've researched it for half an hour they've normally solved it themselves. All I did was take away the easy option of picking my brain for the answer.
If your colleague is incompetent it can work to your advantage by making you look better. If they get removed, that's life, and most people would prefer to work with colleagues who can handle their jobs, it makes everything go smoother and uplifts the whole team.
suggest improvements |Â
up vote
0
down vote
up vote
0
down vote
Don't let your colleagues learning issues impact on your own work. Help when it's convenient and you feel like it, don't when it's not. Otherwise he/she may just lean on you all the time which it looks like is already happening.
Just be firm, they might get a bit upset, but that's life, you don't want to be someone else's crutch through their career. They'll get the picture eventually and find another crutch. The workplace can be a competitive environment, teaching others is not your task unless you're a teacher.
I'm pretty upfront when I keep getting pestered with issues that seem too simple and when they require long winded explanations... my response is "You need to work that out for yourself. Let me know if you get stuck and I'll see what I can do later." then by the time they've researched it for half an hour they've normally solved it themselves. All I did was take away the easy option of picking my brain for the answer.
If your colleague is incompetent it can work to your advantage by making you look better. If they get removed, that's life, and most people would prefer to work with colleagues who can handle their jobs, it makes everything go smoother and uplifts the whole team.
Don't let your colleagues learning issues impact on your own work. Help when it's convenient and you feel like it, don't when it's not. Otherwise he/she may just lean on you all the time which it looks like is already happening.
Just be firm, they might get a bit upset, but that's life, you don't want to be someone else's crutch through their career. They'll get the picture eventually and find another crutch. The workplace can be a competitive environment, teaching others is not your task unless you're a teacher.
I'm pretty upfront when I keep getting pestered with issues that seem too simple and when they require long winded explanations... my response is "You need to work that out for yourself. Let me know if you get stuck and I'll see what I can do later." then by the time they've researched it for half an hour they've normally solved it themselves. All I did was take away the easy option of picking my brain for the answer.
If your colleague is incompetent it can work to your advantage by making you look better. If they get removed, that's life, and most people would prefer to work with colleagues who can handle their jobs, it makes everything go smoother and uplifts the whole team.
answered Nov 1 '15 at 9:20


Kilisi
94.7k50216376
94.7k50216376
suggest improvements |Â
suggest improvements |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f56893%2fmy-colleague-always-ask-for-help-should-i-help-him-always%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Always - No. As much as feasible - Yes.
– PM 77-1
Nov 1 '15 at 5:13
Related: workplace.stackexchange.com/questions/9623/…, workplace.stackexchange.com/questions/5769/….
– Monica Cellio♦
Nov 1 '15 at 18:59