??? 12/04/10 18:53 Read: times |
#179874 - Well, the world's going mad ... but I'm not on board Responding to: ???'s previous message |
I just don't take work that's not clearly defined. In cases, many years ago, when I was "working for the man" from time to time, I just didn't take undefined tasks. If a guy tried to get me to do something undefined, I just encouraged him to do the analysis of his requirements before choosing a course.
If they couldn't do that, I just didn't do anything. After all, if I created something he couldn't use, it absolved him of responsibility for it, which was what he wanted, since he knew he wasn't smart enough to specify the job. Once he set about to write a statement of work (assignment) that included test criteria, I was safe in that he'd not be able to specify the acceptance test qualifiers unless he'd done the necessary analysis. A few guys who thought they could shirk their work ended up getting fired for incompetence. I have credentials and a track record that qualifies me for my work. Often enough my manager's boss would ask me what the trouble was, and I'd tell him that I didn't have a specification, so I couldn't just guess at the work to be done. In such circumstances, if my "boss" asked me to do his analysis for him, I'd do it, but it was tantamount to an admission that he was not competent to do his work. RE |