How can I constructively request well scoped project requirements?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
6
down vote
favorite
Are there good ways to ask the management to improve the clarity and detail level of work requests and be more specific rather than just throwing you into a war zone and expecting you to figure out on your own how to be useful to the team, being kind of like an individual shop within a shop. Or if the culture is like that already, and I don't find myself functioning well in such an environment of undefined roles and expectations, is it better to just look for a more structured place rather than try to change it. Or am I expecting too much? Is it bad to ask a manager to be more specific and clearly define what the expected work results should be if he seems to be vague as a matter of general habit.
workplace-rhythm project-management micro-management
add a comment |Â
up vote
6
down vote
favorite
Are there good ways to ask the management to improve the clarity and detail level of work requests and be more specific rather than just throwing you into a war zone and expecting you to figure out on your own how to be useful to the team, being kind of like an individual shop within a shop. Or if the culture is like that already, and I don't find myself functioning well in such an environment of undefined roles and expectations, is it better to just look for a more structured place rather than try to change it. Or am I expecting too much? Is it bad to ask a manager to be more specific and clearly define what the expected work results should be if he seems to be vague as a matter of general habit.
workplace-rhythm project-management micro-management
add a comment |Â
up vote
6
down vote
favorite
up vote
6
down vote
favorite
Are there good ways to ask the management to improve the clarity and detail level of work requests and be more specific rather than just throwing you into a war zone and expecting you to figure out on your own how to be useful to the team, being kind of like an individual shop within a shop. Or if the culture is like that already, and I don't find myself functioning well in such an environment of undefined roles and expectations, is it better to just look for a more structured place rather than try to change it. Or am I expecting too much? Is it bad to ask a manager to be more specific and clearly define what the expected work results should be if he seems to be vague as a matter of general habit.
workplace-rhythm project-management micro-management
Are there good ways to ask the management to improve the clarity and detail level of work requests and be more specific rather than just throwing you into a war zone and expecting you to figure out on your own how to be useful to the team, being kind of like an individual shop within a shop. Or if the culture is like that already, and I don't find myself functioning well in such an environment of undefined roles and expectations, is it better to just look for a more structured place rather than try to change it. Or am I expecting too much? Is it bad to ask a manager to be more specific and clearly define what the expected work results should be if he seems to be vague as a matter of general habit.
workplace-rhythm project-management micro-management
edited Sep 25 '12 at 20:49


IDrinkandIKnowThings
43.9k1398188
43.9k1398188
asked Sep 25 '12 at 19:01


amphibient
3,20772441
3,20772441
add a comment |Â
add a comment |Â
3 Answers
3
active
oldest
votes
up vote
5
down vote
accepted
It's reasonable to ask for clarification of vague directives, but if you find that you are asking for more specificity than those around you of comparable experience/grade level, then the change will need to come on your end, not your manager's. If a manager has ten people with comparable experience and skills and nine of them are handling his directives just fine, then he's not going to be very receptive to requests from #10 to do things differently.
Here are some ways that you can try to address the problem at your end:
Get a mentor or buddy (a fellow developer). Obviously this person needs to be willing. If your company doesn't have a mentor culture, you (plural) may want to try to change that. You can point out to management that all new employees need some help to get settled in any company, and by investing a little mentor time they'll get to productive new hires more quickly.
When your manager gives you a vague directive, if you're talking you can immediately ask for clarification. if the directive came in some other way (email, line-item on a project plan, bug report, whatever), then before going to your manager, try a sanity-check with your mentor or a peer. The question is "is there enough information here?", not "is this reasonable?" or "how does he expect me to do that?".
If you're still confused and need to go to your manager for help, show him that you've spent some time thinking about it first. Don't ask "what do you mean by performance problem?" but "are you concerned with response time, or bandwidth usage, or delays in updating the back-end database, or...?".
Some industries, and some companies, are fundamentally uncertain. To succeed in those environments you need to be flexible and adapatable. If that turns out to be beyond your current abilities, it might be better to seek out a more structured environment.
add a comment |Â
up vote
10
down vote
Managers don't want to spend tons of time creating detailed plans for what their employees do.
However, a really easy way you can make this happen in effect is to take the vague work requests/instructions you receive and translate them into a much more detailed document (of the type you want from them). After doing this, run this document by your manager and project leads to ensure you have correctly understood what they are looking for in their vague request.
Another way to make it happen is to interpret the instructions as literally as possible. :)
– Amy Blankenship
Sep 26 '12 at 1:59
add a comment |Â
up vote
1
down vote
Impress on your manager that the accuracy of the requirements proportionally affect the accuracy of the cost- and time-estimates. No requirements or unclear expectations means that you will not be able to predict when it will be done or how much it's going to cost.
add a comment |Â
StackExchange.ready(function ()
$("#show-editor-button input, #show-editor-button button").click(function ()
var showEditor = function()
$("#show-editor-button").hide();
$("#post-form").removeClass("dno");
StackExchange.editor.finallyInit();
;
var useFancy = $(this).data('confirm-use-fancy');
if(useFancy == 'True')
var popupTitle = $(this).data('confirm-fancy-title');
var popupBody = $(this).data('confirm-fancy-body');
var popupAccept = $(this).data('confirm-fancy-accept-button');
$(this).loadPopup(
url: '/post/self-answer-popup',
loaded: function(popup)
var pTitle = $(popup).find('h2');
var pBody = $(popup).find('.popup-body');
var pSubmit = $(popup).find('.popup-submit');
pTitle.text(popupTitle);
pBody.html(popupBody);
pSubmit.val(popupAccept).click(showEditor);
)
else
var confirmText = $(this).data('confirm-text');
if (confirmText ? confirm(confirmText) : true)
showEditor();
);
);
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
5
down vote
accepted
It's reasonable to ask for clarification of vague directives, but if you find that you are asking for more specificity than those around you of comparable experience/grade level, then the change will need to come on your end, not your manager's. If a manager has ten people with comparable experience and skills and nine of them are handling his directives just fine, then he's not going to be very receptive to requests from #10 to do things differently.
Here are some ways that you can try to address the problem at your end:
Get a mentor or buddy (a fellow developer). Obviously this person needs to be willing. If your company doesn't have a mentor culture, you (plural) may want to try to change that. You can point out to management that all new employees need some help to get settled in any company, and by investing a little mentor time they'll get to productive new hires more quickly.
When your manager gives you a vague directive, if you're talking you can immediately ask for clarification. if the directive came in some other way (email, line-item on a project plan, bug report, whatever), then before going to your manager, try a sanity-check with your mentor or a peer. The question is "is there enough information here?", not "is this reasonable?" or "how does he expect me to do that?".
If you're still confused and need to go to your manager for help, show him that you've spent some time thinking about it first. Don't ask "what do you mean by performance problem?" but "are you concerned with response time, or bandwidth usage, or delays in updating the back-end database, or...?".
Some industries, and some companies, are fundamentally uncertain. To succeed in those environments you need to be flexible and adapatable. If that turns out to be beyond your current abilities, it might be better to seek out a more structured environment.
add a comment |Â
up vote
5
down vote
accepted
It's reasonable to ask for clarification of vague directives, but if you find that you are asking for more specificity than those around you of comparable experience/grade level, then the change will need to come on your end, not your manager's. If a manager has ten people with comparable experience and skills and nine of them are handling his directives just fine, then he's not going to be very receptive to requests from #10 to do things differently.
Here are some ways that you can try to address the problem at your end:
Get a mentor or buddy (a fellow developer). Obviously this person needs to be willing. If your company doesn't have a mentor culture, you (plural) may want to try to change that. You can point out to management that all new employees need some help to get settled in any company, and by investing a little mentor time they'll get to productive new hires more quickly.
When your manager gives you a vague directive, if you're talking you can immediately ask for clarification. if the directive came in some other way (email, line-item on a project plan, bug report, whatever), then before going to your manager, try a sanity-check with your mentor or a peer. The question is "is there enough information here?", not "is this reasonable?" or "how does he expect me to do that?".
If you're still confused and need to go to your manager for help, show him that you've spent some time thinking about it first. Don't ask "what do you mean by performance problem?" but "are you concerned with response time, or bandwidth usage, or delays in updating the back-end database, or...?".
Some industries, and some companies, are fundamentally uncertain. To succeed in those environments you need to be flexible and adapatable. If that turns out to be beyond your current abilities, it might be better to seek out a more structured environment.
add a comment |Â
up vote
5
down vote
accepted
up vote
5
down vote
accepted
It's reasonable to ask for clarification of vague directives, but if you find that you are asking for more specificity than those around you of comparable experience/grade level, then the change will need to come on your end, not your manager's. If a manager has ten people with comparable experience and skills and nine of them are handling his directives just fine, then he's not going to be very receptive to requests from #10 to do things differently.
Here are some ways that you can try to address the problem at your end:
Get a mentor or buddy (a fellow developer). Obviously this person needs to be willing. If your company doesn't have a mentor culture, you (plural) may want to try to change that. You can point out to management that all new employees need some help to get settled in any company, and by investing a little mentor time they'll get to productive new hires more quickly.
When your manager gives you a vague directive, if you're talking you can immediately ask for clarification. if the directive came in some other way (email, line-item on a project plan, bug report, whatever), then before going to your manager, try a sanity-check with your mentor or a peer. The question is "is there enough information here?", not "is this reasonable?" or "how does he expect me to do that?".
If you're still confused and need to go to your manager for help, show him that you've spent some time thinking about it first. Don't ask "what do you mean by performance problem?" but "are you concerned with response time, or bandwidth usage, or delays in updating the back-end database, or...?".
Some industries, and some companies, are fundamentally uncertain. To succeed in those environments you need to be flexible and adapatable. If that turns out to be beyond your current abilities, it might be better to seek out a more structured environment.
It's reasonable to ask for clarification of vague directives, but if you find that you are asking for more specificity than those around you of comparable experience/grade level, then the change will need to come on your end, not your manager's. If a manager has ten people with comparable experience and skills and nine of them are handling his directives just fine, then he's not going to be very receptive to requests from #10 to do things differently.
Here are some ways that you can try to address the problem at your end:
Get a mentor or buddy (a fellow developer). Obviously this person needs to be willing. If your company doesn't have a mentor culture, you (plural) may want to try to change that. You can point out to management that all new employees need some help to get settled in any company, and by investing a little mentor time they'll get to productive new hires more quickly.
When your manager gives you a vague directive, if you're talking you can immediately ask for clarification. if the directive came in some other way (email, line-item on a project plan, bug report, whatever), then before going to your manager, try a sanity-check with your mentor or a peer. The question is "is there enough information here?", not "is this reasonable?" or "how does he expect me to do that?".
If you're still confused and need to go to your manager for help, show him that you've spent some time thinking about it first. Don't ask "what do you mean by performance problem?" but "are you concerned with response time, or bandwidth usage, or delays in updating the back-end database, or...?".
Some industries, and some companies, are fundamentally uncertain. To succeed in those environments you need to be flexible and adapatable. If that turns out to be beyond your current abilities, it might be better to seek out a more structured environment.
answered Sep 25 '12 at 19:16
Monica Cellio♦
43.7k17114191
43.7k17114191
add a comment |Â
add a comment |Â
up vote
10
down vote
Managers don't want to spend tons of time creating detailed plans for what their employees do.
However, a really easy way you can make this happen in effect is to take the vague work requests/instructions you receive and translate them into a much more detailed document (of the type you want from them). After doing this, run this document by your manager and project leads to ensure you have correctly understood what they are looking for in their vague request.
Another way to make it happen is to interpret the instructions as literally as possible. :)
– Amy Blankenship
Sep 26 '12 at 1:59
add a comment |Â
up vote
10
down vote
Managers don't want to spend tons of time creating detailed plans for what their employees do.
However, a really easy way you can make this happen in effect is to take the vague work requests/instructions you receive and translate them into a much more detailed document (of the type you want from them). After doing this, run this document by your manager and project leads to ensure you have correctly understood what they are looking for in their vague request.
Another way to make it happen is to interpret the instructions as literally as possible. :)
– Amy Blankenship
Sep 26 '12 at 1:59
add a comment |Â
up vote
10
down vote
up vote
10
down vote
Managers don't want to spend tons of time creating detailed plans for what their employees do.
However, a really easy way you can make this happen in effect is to take the vague work requests/instructions you receive and translate them into a much more detailed document (of the type you want from them). After doing this, run this document by your manager and project leads to ensure you have correctly understood what they are looking for in their vague request.
Managers don't want to spend tons of time creating detailed plans for what their employees do.
However, a really easy way you can make this happen in effect is to take the vague work requests/instructions you receive and translate them into a much more detailed document (of the type you want from them). After doing this, run this document by your manager and project leads to ensure you have correctly understood what they are looking for in their vague request.
answered Sep 25 '12 at 19:17


Elysian Fields♦
96.9k46292449
96.9k46292449
Another way to make it happen is to interpret the instructions as literally as possible. :)
– Amy Blankenship
Sep 26 '12 at 1:59
add a comment |Â
Another way to make it happen is to interpret the instructions as literally as possible. :)
– Amy Blankenship
Sep 26 '12 at 1:59
Another way to make it happen is to interpret the instructions as literally as possible. :)
– Amy Blankenship
Sep 26 '12 at 1:59
Another way to make it happen is to interpret the instructions as literally as possible. :)
– Amy Blankenship
Sep 26 '12 at 1:59
add a comment |Â
up vote
1
down vote
Impress on your manager that the accuracy of the requirements proportionally affect the accuracy of the cost- and time-estimates. No requirements or unclear expectations means that you will not be able to predict when it will be done or how much it's going to cost.
add a comment |Â
up vote
1
down vote
Impress on your manager that the accuracy of the requirements proportionally affect the accuracy of the cost- and time-estimates. No requirements or unclear expectations means that you will not be able to predict when it will be done or how much it's going to cost.
add a comment |Â
up vote
1
down vote
up vote
1
down vote
Impress on your manager that the accuracy of the requirements proportionally affect the accuracy of the cost- and time-estimates. No requirements or unclear expectations means that you will not be able to predict when it will be done or how much it's going to cost.
Impress on your manager that the accuracy of the requirements proportionally affect the accuracy of the cost- and time-estimates. No requirements or unclear expectations means that you will not be able to predict when it will be done or how much it's going to cost.
answered Sep 27 '12 at 11:07
pap
5,2561524
5,2561524
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%2f4177%2fhow-can-i-constructively-request-well-scoped-project-requirements%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