Mixing
Handling rumors about project priorities
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
0
down vote
favorite
We are working on the firmware our company's new device. Yesterday we heard some rumors from the head of hardware department about a trade show next week where our CEO wants to show the hardware to a few clients.
It is not official since the software department has its own boss and he didn't say anything about it. Unfortunately he is very busy/unavailable/offsite these days.
The second misfortunate thing that we are working on testing features (testing that the device was assembled properly and there is not any hardware design mistakes) as we have planned with our boss. These features are not too valuable for an end-user directly, you can not press buttons and see the result on the device etc. We do not know how much the CEO knows about this.
How should we handle this situation? We would like to avoid last-minute firefighting due to changing priorities nor spend a lot of time with meetings/catching people to figure out what we should do and what are the real priorities.
communication
asked Apr 21 '14 at 22:38
user18933
31
add a comment |Â
up vote
0
down vote
favorite
We are working on the firmware our company's new device. Yesterday we heard some rumors from the head of hardware department about a trade show next week where our CEO wants to show the hardware to a few clients.
It is not official since the software department has its own boss and he didn't say anything about it. Unfortunately he is very busy/unavailable/offsite these days.
The second misfortunate thing that we are working on testing features (testing that the device was assembled properly and there is not any hardware design mistakes) as we have planned with our boss. These features are not too valuable for an end-user directly, you can not press buttons and see the result on the device etc. We do not know how much the CEO knows about this.
How should we handle this situation? We would like to avoid last-minute firefighting due to changing priorities nor spend a lot of time with meetings/catching people to figure out what we should do and what are the real priorities.
communication
asked Apr 21 '14 at 22:38
user18933
31
2
Don't tell me that the boss of the software engineering department is too busy to read his own emails. Send him an email, lay out what you know about the situation and the concerns that you have as a group and cc: the CEO. And you own boss. Actually, it's better that your own boss send the email on behalf of the firmware department and cc: the CEO. What's up with your company that people are so hesitant about communicating with each other?
– Vietnhi Phuvan
Apr 22 '14 at 2:31
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
We are working on the firmware our company's new device. Yesterday we heard some rumors from the head of hardware department about a trade show next week where our CEO wants to show the hardware to a few clients.
It is not official since the software department has its own boss and he didn't say anything about it. Unfortunately he is very busy/unavailable/offsite these days.
The second misfortunate thing that we are working on testing features (testing that the device was assembled properly and there is not any hardware design mistakes) as we have planned with our boss. These features are not too valuable for an end-user directly, you can not press buttons and see the result on the device etc. We do not know how much the CEO knows about this.
How should we handle this situation? We would like to avoid last-minute firefighting due to changing priorities nor spend a lot of time with meetings/catching people to figure out what we should do and what are the real priorities.
communication
asked Apr 21 '14 at 22:38
user18933
31
We are working on the firmware our company's new device. Yesterday we heard some rumors from the head of hardware department about a trade show next week where our CEO wants to show the hardware to a few clients.
It is not official since the software department has its own boss and he didn't say anything about it. Unfortunately he is very busy/unavailable/offsite these days.
The second misfortunate thing that we are working on testing features (testing that the device was assembled properly and there is not any hardware design mistakes) as we have planned with our boss. These features are not too valuable for an end-user directly, you can not press buttons and see the result on the device etc. We do not know how much the CEO knows about this.
How should we handle this situation? We would like to avoid last-minute firefighting due to changing priorities nor spend a lot of time with meetings/catching people to figure out what we should do and what are the real priorities.
communication
asked Apr 21 '14 at 22:38
user18933
31
asked Apr 21 '14 at 22:38
user18933
31
asked Apr 21 '14 at 22:38
user18933
31
asked Apr 21 '14 at 22:38
user18933
31
31
2
Don't tell me that the boss of the software engineering department is too busy to read his own emails. Send him an email, lay out what you know about the situation and the concerns that you have as a group and cc: the CEO. And you own boss. Actually, it's better that your own boss send the email on behalf of the firmware department and cc: the CEO. What's up with your company that people are so hesitant about communicating with each other?
– Vietnhi Phuvan
Apr 22 '14 at 2:31
add a comment |Â
2
Don't tell me that the boss of the software engineering department is too busy to read his own emails. Send him an email, lay out what you know about the situation and the concerns that you have as a group and cc: the CEO. And you own boss. Actually, it's better that your own boss send the email on behalf of the firmware department and cc: the CEO. What's up with your company that people are so hesitant about communicating with each other?
– Vietnhi Phuvan
Apr 22 '14 at 2:31
2
2
Don't tell me that the boss of the software engineering department is too busy to read his own emails. Send him an email, lay out what you know about the situation and the concerns that you have as a group and cc: the CEO. And you own boss. Actually, it's better that your own boss send the email on behalf of the firmware department and cc: the CEO. What's up with your company that people are so hesitant about communicating with each other?
– Vietnhi Phuvan
Apr 22 '14 at 2:31
Don't tell me that the boss of the software engineering department is too busy to read his own emails. Send him an email, lay out what you know about the situation and the concerns that you have as a group and cc: the CEO. And you own boss. Actually, it's better that your own boss send the email on behalf of the firmware department and cc: the CEO. What's up with your company that people are so hesitant about communicating with each other?
– Vietnhi Phuvan
Apr 22 '14 at 2:31
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
8
down vote
accepted
In general, it isn't your responsibility to make sure that what you've been tasked to do is the most important thing you should be doing.
Although taking some initiative tends to be a good thing, and you may occasionally find yourself getting punished for doing what you've been told rather than something else.
In this case, I don't see much harm in asking your boss about it:
Hey boss
There are some rumours going around that the product will be demo'd next week.
As you know, we're currently working on software to validate the hardware design.
I'd just like to clarify whether we should continue on the hardware validation, or whether we should shift our priorities to focus on functionality instead, as to make the product seem more impressive to users for the purposes of the demo.
Or aren't there truth to these rumours, or is it perhaps purely focussed around the hardware?
(Customized to how you'd write it and what makes sense for your situation, of course)
This is the extent of what you should do. You only report to your boss - any clarification about what you should be doing should be addressed with him/her and him/her alone.
If you've been working on the wrong things, this will be because of someone else having messed up (unless you haven't been doing enough work). If you feel it sufficiently probable that someone may end up trying to throw you under the bus, it's best to get the above communication in writing (and perhaps make it clearer exactly how little you think there will be to demo from a software point of view). "Last-minute firefighting" may happen if someone messes up - it's just something you'll have to accept.
If you can't get hold of your boss for a sufficient period of time (days...), you could consider approaching someone higher up, perhaps even the CEO, if you deem that appropriate. Do make it clear that you haven't been able to get hold of your boss, as you don't want to make it seem like you're trying to go over his/her head.
answered Apr 21 '14 at 23:36
Dukeling
8,70132447
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
8
down vote
accepted
In general, it isn't your responsibility to make sure that what you've been tasked to do is the most important thing you should be doing.
Although taking some initiative tends to be a good thing, and you may occasionally find yourself getting punished for doing what you've been told rather than something else.
In this case, I don't see much harm in asking your boss about it:
Hey boss
There are some rumours going around that the product will be demo'd next week.
As you know, we're currently working on software to validate the hardware design.
I'd just like to clarify whether we should continue on the hardware validation, or whether we should shift our priorities to focus on functionality instead, as to make the product seem more impressive to users for the purposes of the demo.
Or aren't there truth to these rumours, or is it perhaps purely focussed around the hardware?
(Customized to how you'd write it and what makes sense for your situation, of course)
This is the extent of what you should do. You only report to your boss - any clarification about what you should be doing should be addressed with him/her and him/her alone.
If you've been working on the wrong things, this will be because of someone else having messed up (unless you haven't been doing enough work). If you feel it sufficiently probable that someone may end up trying to throw you under the bus, it's best to get the above communication in writing (and perhaps make it clearer exactly how little you think there will be to demo from a software point of view). "Last-minute firefighting" may happen if someone messes up - it's just something you'll have to accept.
If you can't get hold of your boss for a sufficient period of time (days...), you could consider approaching someone higher up, perhaps even the CEO, if you deem that appropriate. Do make it clear that you haven't been able to get hold of your boss, as you don't want to make it seem like you're trying to go over his/her head.
answered Apr 21 '14 at 23:36
Dukeling
8,70132447
add a comment |Â
up vote
8
down vote
accepted
In general, it isn't your responsibility to make sure that what you've been tasked to do is the most important thing you should be doing.
Although taking some initiative tends to be a good thing, and you may occasionally find yourself getting punished for doing what you've been told rather than something else.
In this case, I don't see much harm in asking your boss about it:
Hey boss
There are some rumours going around that the product will be demo'd next week.
As you know, we're currently working on software to validate the hardware design.
I'd just like to clarify whether we should continue on the hardware validation, or whether we should shift our priorities to focus on functionality instead, as to make the product seem more impressive to users for the purposes of the demo.
Or aren't there truth to these rumours, or is it perhaps purely focussed around the hardware?
(Customized to how you'd write it and what makes sense for your situation, of course)
This is the extent of what you should do. You only report to your boss - any clarification about what you should be doing should be addressed with him/her and him/her alone.
If you've been working on the wrong things, this will be because of someone else having messed up (unless you haven't been doing enough work). If you feel it sufficiently probable that someone may end up trying to throw you under the bus, it's best to get the above communication in writing (and perhaps make it clearer exactly how little you think there will be to demo from a software point of view). "Last-minute firefighting" may happen if someone messes up - it's just something you'll have to accept.
If you can't get hold of your boss for a sufficient period of time (days...), you could consider approaching someone higher up, perhaps even the CEO, if you deem that appropriate. Do make it clear that you haven't been able to get hold of your boss, as you don't want to make it seem like you're trying to go over his/her head.
answered Apr 21 '14 at 23:36
Dukeling
8,70132447
add a comment |Â
up vote
8
down vote
accepted
up vote
8
down vote
accepted
In general, it isn't your responsibility to make sure that what you've been tasked to do is the most important thing you should be doing.
Although taking some initiative tends to be a good thing, and you may occasionally find yourself getting punished for doing what you've been told rather than something else.
In this case, I don't see much harm in asking your boss about it:
Hey boss
There are some rumours going around that the product will be demo'd next week.
As you know, we're currently working on software to validate the hardware design.
I'd just like to clarify whether we should continue on the hardware validation, or whether we should shift our priorities to focus on functionality instead, as to make the product seem more impressive to users for the purposes of the demo.
Or aren't there truth to these rumours, or is it perhaps purely focussed around the hardware?
(Customized to how you'd write it and what makes sense for your situation, of course)
This is the extent of what you should do. You only report to your boss - any clarification about what you should be doing should be addressed with him/her and him/her alone.
If you've been working on the wrong things, this will be because of someone else having messed up (unless you haven't been doing enough work). If you feel it sufficiently probable that someone may end up trying to throw you under the bus, it's best to get the above communication in writing (and perhaps make it clearer exactly how little you think there will be to demo from a software point of view). "Last-minute firefighting" may happen if someone messes up - it's just something you'll have to accept.
If you can't get hold of your boss for a sufficient period of time (days...), you could consider approaching someone higher up, perhaps even the CEO, if you deem that appropriate. Do make it clear that you haven't been able to get hold of your boss, as you don't want to make it seem like you're trying to go over his/her head.
answered Apr 21 '14 at 23:36
Dukeling
8,70132447
In general, it isn't your responsibility to make sure that what you've been tasked to do is the most important thing you should be doing.
Although taking some initiative tends to be a good thing, and you may occasionally find yourself getting punished for doing what you've been told rather than something else.
In this case, I don't see much harm in asking your boss about it:
Hey boss
There are some rumours going around that the product will be demo'd next week.
As you know, we're currently working on software to validate the hardware design.
I'd just like to clarify whether we should continue on the hardware validation, or whether we should shift our priorities to focus on functionality instead, as to make the product seem more impressive to users for the purposes of the demo.
Or aren't there truth to these rumours, or is it perhaps purely focussed around the hardware?
(Customized to how you'd write it and what makes sense for your situation, of course)
This is the extent of what you should do. You only report to your boss - any clarification about what you should be doing should be addressed with him/her and him/her alone.
If you've been working on the wrong things, this will be because of someone else having messed up (unless you haven't been doing enough work). If you feel it sufficiently probable that someone may end up trying to throw you under the bus, it's best to get the above communication in writing (and perhaps make it clearer exactly how little you think there will be to demo from a software point of view). "Last-minute firefighting" may happen if someone messes up - it's just something you'll have to accept.
If you can't get hold of your boss for a sufficient period of time (days...), you could consider approaching someone higher up, perhaps even the CEO, if you deem that appropriate. Do make it clear that you haven't been able to get hold of your boss, as you don't want to make it seem like you're trying to go over his/her head.
answered Apr 21 '14 at 23:36
Dukeling
8,70132447
answered Apr 21 '14 at 23:36
Dukeling
8,70132447
answered Apr 21 '14 at 23:36
Dukeling
8,70132447
answered Apr 21 '14 at 23:36
Dukeling
8,70132447
8,70132447
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%2f23034%2fhandling-rumors-about-project-priorities%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
2
Don't tell me that the boss of the software engineering department is too busy to read his own emails. Send him an email, lay out what you know about the situation and the concerns that you have as a group and cc: the CEO. And you own boss. Actually, it's better that your own boss send the email on behalf of the firmware department and cc: the CEO. What's up with your company that people are so hesitant about communicating with each other?
– Vietnhi Phuvan
Apr 22 '14 at 2:31