Yeah, QA is a popular destination for any hot potato that nobody else wants. To a point it is appropriate, perhaps initially acting as the analyst for who should really own any one potato.As a start up also QA does usually end up with the lions share of new customer requirements. GDPR? QA. Cybersecurity? QA Translations? QA
Don't get the idea that it's because you're a woman. This man has had the same issues for around 30 years across several different companies.I think this more accurately speaks to my frustration. I've done everything I can to facilitate communication and get people to value ownership, as have previous women in my position.
Don't get the idea that it's because you're a woman. This man has had the same issues for around 30 years across several different companies.
Did i mentioned, my team support a few companies, local and overseas.
There are other licenses I`m managing, which i think should not be under QA/RA, but felt that no one wants to do it / want to learn to do it (although to me it is a simple process with a lot of confidential documents involved = time consuming).
I am happy to these at this age, but i don`t think its good for my health in long run.
Personally, i think some of these "task" should be put on other head, if manpower is not an issue.
Building safety / Hoist lifts / Fire safety/ OSHA - building maintenance
Legal - paralegal or company secretary / maybe a PA
Antibribery - Finance dept to lead
Cybersecurity - IT dept to lead
Data Protection - Human resource or IT to lead
Finance license - Finance dept to lead
Import export - Operations / Supply chain
Have i or my team crossing the line doing all these task? I`m not sure myself.
But we hope we are helping company to fulfill all the customer needs (users, authorities and suppliers), as we are known to be a "non-revenue department".
In small company where there is limited staff, employees may wear double hats. E.g. QA/QC cum Engineering. That is ok, provided 1) you have the knowledge and 2) you are not doing someone else's job, i.e. there isn't an engineering function in the company.In my early training in the Quality field, one of my instructors stressed that we should always do QA/QC, and only QA/QC, else we find ourselves going down a path that ends to failing in your Quality duties.
His theory was once you go down the road of doing something that another department rightfully owns, then there will never be an end to the non Q duties you will be assigned. Inevitably you will fail at something, and it's only a question of whether you fail at your Q duties or the non-Q duties.
I just crossed the line ( I was pushed! )and now have some non Q responsibility. Traditionally I'd view the tasks as the responsibilities of Design Engineering and Technical Writer.
I know we all work in a "many hats" world, but I'd be interested in your opinions regarding this outlook.