It is a balancing act. I'll give a personal experience with a RA saying "no" to innovation.
As a Navy officer, I was assigned to a Torpedo Maintenance Facility. A new type of torpedo had come out. We had a lot of problems with the maintenance procedures not being very specific, full of "if applicable" clauses, and changes affecting previous changes in some procedures not others. And the Navy shipping us faulty parts and incomplete torpedoes. But if a mistake was made, the RA (in this case "NUSC") said the enlisted sailors "knew what to do" and every failure was the sailor's faults. Another officer and I started documenting issues, and even circulated a sarcastic cartoon about the parts and incomplete issues. We submitted many procedure changes. But the very same NUSC that inspected us was the procedure writers. They claimed they got dinged for "making too many procedure changes" so refused to allow ours.
In the end, the other officer and I prevailed, I even got an award from the Navy, but it was an uphill battle the whole way.
By the way, for those familiar with military history, consider we went into World War II with faulty torpedoes that would not work, but the Navy RA accepted them, would not listen to the users who fired dud after dud, and inadequately tested them