Mixing
When is it okay to consult others on work I'm doing (after being told I take up too much of their time)?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
3
down vote
favorite
When I was working for a very large company, we had an intranet site where any employee could document any procedure (for those of you who know IBM I'm referring to Connections). With 400,000+ employees around the world, this could be very hard to use.
I had been reprimanded for asking too many questions so I tried only using the documentation without consulting anyone.
I had to install MS Office on one computer and get the licensing for it, but I messed things up because the documentation I was following was for a different country. There was nothing indicating it was for a different country and to this day I'm not sure what I could have done differently.
What can I do to make sure that my questions are appropriate and not to frequent?
management productivity documentation
edited Nov 25 '13 at 23:47
Elysian Fields♦
96.9k46292449
asked Nov 24 '13 at 1:49
Arnakester
3871615
add a comment |Â
up vote
3
down vote
favorite
When I was working for a very large company, we had an intranet site where any employee could document any procedure (for those of you who know IBM I'm referring to Connections). With 400,000+ employees around the world, this could be very hard to use.
I had been reprimanded for asking too many questions so I tried only using the documentation without consulting anyone.
I had to install MS Office on one computer and get the licensing for it, but I messed things up because the documentation I was following was for a different country. There was nothing indicating it was for a different country and to this day I'm not sure what I could have done differently.
What can I do to make sure that my questions are appropriate and not to frequent?
management productivity documentation
edited Nov 25 '13 at 23:47
Elysian Fields♦
96.9k46292449
asked Nov 24 '13 at 1:49
Arnakester
3871615
1
These answers might help: Boss does not answer questions and When I ask my boss a question he says he's already answered but he hasn't. Not duplicates, but perhaps useful.
– jmac
Nov 25 '13 at 0:17
1
The edits help focus this post on a single, solvable question; thus, I've reopened.
– jmort253♦
Nov 30 '13 at 19:50
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
When I was working for a very large company, we had an intranet site where any employee could document any procedure (for those of you who know IBM I'm referring to Connections). With 400,000+ employees around the world, this could be very hard to use.
I had been reprimanded for asking too many questions so I tried only using the documentation without consulting anyone.
I had to install MS Office on one computer and get the licensing for it, but I messed things up because the documentation I was following was for a different country. There was nothing indicating it was for a different country and to this day I'm not sure what I could have done differently.
What can I do to make sure that my questions are appropriate and not to frequent?
management productivity documentation
edited Nov 25 '13 at 23:47
Elysian Fields♦
96.9k46292449
asked Nov 24 '13 at 1:49
Arnakester
3871615
When I was working for a very large company, we had an intranet site where any employee could document any procedure (for those of you who know IBM I'm referring to Connections). With 400,000+ employees around the world, this could be very hard to use.
I had been reprimanded for asking too many questions so I tried only using the documentation without consulting anyone.
I had to install MS Office on one computer and get the licensing for it, but I messed things up because the documentation I was following was for a different country. There was nothing indicating it was for a different country and to this day I'm not sure what I could have done differently.
What can I do to make sure that my questions are appropriate and not to frequent?
management productivity documentation
edited Nov 25 '13 at 23:47
Elysian Fields♦
96.9k46292449
asked Nov 24 '13 at 1:49
Arnakester
3871615
edited Nov 25 '13 at 23:47
Elysian Fields♦
96.9k46292449
edited Nov 25 '13 at 23:47
Elysian Fields♦
96.9k46292449
edited Nov 25 '13 at 23:47
Elysian Fields♦
96.9k46292449
96.9k46292449
asked Nov 24 '13 at 1:49
Arnakester
3871615
asked Nov 24 '13 at 1:49
Arnakester
3871615
asked Nov 24 '13 at 1:49
Arnakester
3871615
3871615
1
These answers might help: Boss does not answer questions and When I ask my boss a question he says he's already answered but he hasn't. Not duplicates, but perhaps useful.
– jmac
Nov 25 '13 at 0:17
1
The edits help focus this post on a single, solvable question; thus, I've reopened.
– jmort253♦
Nov 30 '13 at 19:50
add a comment |Â
1
These answers might help: Boss does not answer questions and When I ask my boss a question he says he's already answered but he hasn't. Not duplicates, but perhaps useful.
– jmac
Nov 25 '13 at 0:17
1
The edits help focus this post on a single, solvable question; thus, I've reopened.
– jmort253♦
Nov 30 '13 at 19:50
1
1
These answers might help: Boss does not answer questions and When I ask my boss a question he says he's already answered but he hasn't. Not duplicates, but perhaps useful.
– jmac
Nov 25 '13 at 0:17
These answers might help: Boss does not answer questions and When I ask my boss a question he says he's already answered but he hasn't. Not duplicates, but perhaps useful.
– jmac
Nov 25 '13 at 0:17
1
1
The edits help focus this post on a single, solvable question; thus, I've reopened.
– jmort253♦
Nov 30 '13 at 19:50
The edits help focus this post on a single, solvable question; thus, I've reopened.
– jmort253♦
Nov 30 '13 at 19:50
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
6
down vote
I suggest you start by using a technique called Rubber Duck Problem Solving. The idea is that you ask yourself the question you are going to ask someone else first. You try and answer your question, usually by asking yourself the important questions about the details. Then try to find the answer to the questions you asked and did not know. This process helps you solve your own problems many times, and reduces the amount of time you need to take from others when you do have to consult them.
Jeff Atwood wrote about this topic on Coding Horror in 2012
The critical part of rubber duck problem solving is to totally commit
to asking a thorough, detailed question of this imaginary person or
inanimate object. Yes, even if you end up throwing the question away
because you eventually realize that you made some dumb mistake. The
effort of walking an imaginary someone through your problem, step by
step and in some detail, is what will often lead you to your answer.
But if you aren't willing to put the effort into fully explaining the
problem and how you've attacked it, you can't reap the benefits of
thinking deeply about your own problem before you ask others to.
And then when asking the question provide the following information:
- Describe what's happening in sufficient detail that we can follow along. Provide the necessary background for us to understand what's going on, even if we aren't experts in your particular area.
- Tell us why you need to know the answer. What led you here? Is it idle curiosity or somehow blocking you on a project? We don't require your whole life story, just give us some basic context for the problem.
- Share any research you did towards solving your problem, and what you found, if anything. And if you didn't do any research – should you even be asking?
- Ultimately, this is about fairness: if you're going to ask us to spend our valuable time helping you, it's only fair that you put in a reasonable amount of your valuable time into crafting a decent question. Help us help you!
answered Nov 24 '13 at 17:00
IDrinkandIKnowThings
43.9k1398188
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
6
down vote
I suggest you start by using a technique called Rubber Duck Problem Solving. The idea is that you ask yourself the question you are going to ask someone else first. You try and answer your question, usually by asking yourself the important questions about the details. Then try to find the answer to the questions you asked and did not know. This process helps you solve your own problems many times, and reduces the amount of time you need to take from others when you do have to consult them.
Jeff Atwood wrote about this topic on Coding Horror in 2012
The critical part of rubber duck problem solving is to totally commit
to asking a thorough, detailed question of this imaginary person or
inanimate object. Yes, even if you end up throwing the question away
because you eventually realize that you made some dumb mistake. The
effort of walking an imaginary someone through your problem, step by
step and in some detail, is what will often lead you to your answer.
But if you aren't willing to put the effort into fully explaining the
problem and how you've attacked it, you can't reap the benefits of
thinking deeply about your own problem before you ask others to.
And then when asking the question provide the following information:
- Describe what's happening in sufficient detail that we can follow along. Provide the necessary background for us to understand what's going on, even if we aren't experts in your particular area.
- Tell us why you need to know the answer. What led you here? Is it idle curiosity or somehow blocking you on a project? We don't require your whole life story, just give us some basic context for the problem.
- Share any research you did towards solving your problem, and what you found, if anything. And if you didn't do any research – should you even be asking?
- Ultimately, this is about fairness: if you're going to ask us to spend our valuable time helping you, it's only fair that you put in a reasonable amount of your valuable time into crafting a decent question. Help us help you!
answered Nov 24 '13 at 17:00
IDrinkandIKnowThings
43.9k1398188
add a comment |Â
up vote
6
down vote
I suggest you start by using a technique called Rubber Duck Problem Solving. The idea is that you ask yourself the question you are going to ask someone else first. You try and answer your question, usually by asking yourself the important questions about the details. Then try to find the answer to the questions you asked and did not know. This process helps you solve your own problems many times, and reduces the amount of time you need to take from others when you do have to consult them.
Jeff Atwood wrote about this topic on Coding Horror in 2012
The critical part of rubber duck problem solving is to totally commit
to asking a thorough, detailed question of this imaginary person or
inanimate object. Yes, even if you end up throwing the question away
because you eventually realize that you made some dumb mistake. The
effort of walking an imaginary someone through your problem, step by
step and in some detail, is what will often lead you to your answer.
But if you aren't willing to put the effort into fully explaining the
problem and how you've attacked it, you can't reap the benefits of
thinking deeply about your own problem before you ask others to.
And then when asking the question provide the following information:
- Describe what's happening in sufficient detail that we can follow along. Provide the necessary background for us to understand what's going on, even if we aren't experts in your particular area.
- Tell us why you need to know the answer. What led you here? Is it idle curiosity or somehow blocking you on a project? We don't require your whole life story, just give us some basic context for the problem.
- Share any research you did towards solving your problem, and what you found, if anything. And if you didn't do any research – should you even be asking?
- Ultimately, this is about fairness: if you're going to ask us to spend our valuable time helping you, it's only fair that you put in a reasonable amount of your valuable time into crafting a decent question. Help us help you!
answered Nov 24 '13 at 17:00
IDrinkandIKnowThings
43.9k1398188
add a comment |Â
up vote
6
down vote
up vote
6
down vote
I suggest you start by using a technique called Rubber Duck Problem Solving. The idea is that you ask yourself the question you are going to ask someone else first. You try and answer your question, usually by asking yourself the important questions about the details. Then try to find the answer to the questions you asked and did not know. This process helps you solve your own problems many times, and reduces the amount of time you need to take from others when you do have to consult them.
Jeff Atwood wrote about this topic on Coding Horror in 2012
The critical part of rubber duck problem solving is to totally commit
to asking a thorough, detailed question of this imaginary person or
inanimate object. Yes, even if you end up throwing the question away
because you eventually realize that you made some dumb mistake. The
effort of walking an imaginary someone through your problem, step by
step and in some detail, is what will often lead you to your answer.
But if you aren't willing to put the effort into fully explaining the
problem and how you've attacked it, you can't reap the benefits of
thinking deeply about your own problem before you ask others to.
And then when asking the question provide the following information:
- Describe what's happening in sufficient detail that we can follow along. Provide the necessary background for us to understand what's going on, even if we aren't experts in your particular area.
- Tell us why you need to know the answer. What led you here? Is it idle curiosity or somehow blocking you on a project? We don't require your whole life story, just give us some basic context for the problem.
- Share any research you did towards solving your problem, and what you found, if anything. And if you didn't do any research – should you even be asking?
- Ultimately, this is about fairness: if you're going to ask us to spend our valuable time helping you, it's only fair that you put in a reasonable amount of your valuable time into crafting a decent question. Help us help you!
answered Nov 24 '13 at 17:00
IDrinkandIKnowThings
43.9k1398188
I suggest you start by using a technique called Rubber Duck Problem Solving. The idea is that you ask yourself the question you are going to ask someone else first. You try and answer your question, usually by asking yourself the important questions about the details. Then try to find the answer to the questions you asked and did not know. This process helps you solve your own problems many times, and reduces the amount of time you need to take from others when you do have to consult them.
Jeff Atwood wrote about this topic on Coding Horror in 2012
The critical part of rubber duck problem solving is to totally commit
to asking a thorough, detailed question of this imaginary person or
inanimate object. Yes, even if you end up throwing the question away
because you eventually realize that you made some dumb mistake. The
effort of walking an imaginary someone through your problem, step by
step and in some detail, is what will often lead you to your answer.
But if you aren't willing to put the effort into fully explaining the
problem and how you've attacked it, you can't reap the benefits of
thinking deeply about your own problem before you ask others to.
And then when asking the question provide the following information:
- Describe what's happening in sufficient detail that we can follow along. Provide the necessary background for us to understand what's going on, even if we aren't experts in your particular area.
- Tell us why you need to know the answer. What led you here? Is it idle curiosity or somehow blocking you on a project? We don't require your whole life story, just give us some basic context for the problem.
- Share any research you did towards solving your problem, and what you found, if anything. And if you didn't do any research – should you even be asking?
- Ultimately, this is about fairness: if you're going to ask us to spend our valuable time helping you, it's only fair that you put in a reasonable amount of your valuable time into crafting a decent question. Help us help you!
answered Nov 24 '13 at 17:00
IDrinkandIKnowThings
43.9k1398188
edited Nov 24 '13 at 23:28
answered Nov 24 '13 at 17:00
IDrinkandIKnowThings
43.9k1398188
answered Nov 24 '13 at 17:00
IDrinkandIKnowThings
43.9k1398188
answered Nov 24 '13 at 17:00
IDrinkandIKnowThings
43.9k1398188
43.9k1398188
add a comment |Â
add a comment |Â
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%2f16897%2fwhen-is-it-okay-to-consult-others-on-work-im-doing-after-being-told-i-take-up%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
1
These answers might help: Boss does not answer questions and When I ask my boss a question he says he's already answered but he hasn't. Not duplicates, but perhaps useful.
– jmac
Nov 25 '13 at 0:17
1
The edits help focus this post on a single, solvable question; thus, I've reopened.
– jmort253♦
Nov 30 '13 at 19:50