Basically, I don’t call shots in my organization, I’m a worker bee (best I could call myself is a "specialist worker bee hehehe) I can only work on what is assigned to me and our people are strict on that. Sometimes I get called into meetings as a technical advisor just to let people know if what they are dreaming sounds feasible but even those, if they start to take off, my bosses intervene and demand a project is actually created and put through the paces before it can be assigned to someone.
With that in mind, if I deem a project, task, inquire BS and do not work on it but I am wrong, the interested party (usually my boss) would come back to me to get status updates, ETAs, etc. Therefore, if I deem a project BS and it is not, I would eventually get in trouble.
What usually happens is that my boss would come and instead of asking about the status on the BS project, they would tell me to hold on or provide me new specs which may not be BS or simply to tell me the project sponsors dropped it.
Totally fair question.
Basically, I don’t call shots in my organization, I’m a worker bee (best I could call myself is a "specialist worker bee hehehe) I can only work on what is assigned to me and our people are strict on that. Sometimes I get called into meetings as a technical advisor just to let people know if what they are dreaming sounds feasible but even those, if they start to take off, my bosses intervene and demand a project is actually created and put through the paces before it can be assigned to someone.
With that in mind, if I deem a project, task, inquire BS and do not work on it but I am wrong, the interested party (usually my boss) would come back to me to get status updates, ETAs, etc. Therefore, if I deem a project BS and it is not, I would eventually get in trouble.
What usually happens is that my boss would come and instead of asking about the status on the BS project, they would tell me to hold on or provide me new specs which may not be BS or simply to tell me the project sponsors dropped it.