D
How important is the audience when wrtiting a design verification/validation report?
My responsibility is to review reports from a regulatory compliance perspective and I get alot of push back when I request a change specifically if the change will make the document read easier and the flow more logical. Some of it is simply poor grammer, some of it is overuse of engineering terminology and some of it is them thinking that everyone thnks the same way they do or that the information is implied/assumed. i.e. For each acceptance criterian I expect a corresponding result.
They are not very happy with me at the moment. How can I help them to at least appreciate, at some level, the audience without further frustration on all our parts? Thanks
My responsibility is to review reports from a regulatory compliance perspective and I get alot of push back when I request a change specifically if the change will make the document read easier and the flow more logical. Some of it is simply poor grammer, some of it is overuse of engineering terminology and some of it is them thinking that everyone thnks the same way they do or that the information is implied/assumed. i.e. For each acceptance criterian I expect a corresponding result.
They are not very happy with me at the moment. How can I help them to at least appreciate, at some level, the audience without further frustration on all our parts? Thanks