One such weakness is an author's natural tendency to overlook one's own mistakes. This makes an auditor's input more like an opportunity/continual improvement.
No just overlook them, but to also not learn from them.
In my opinion, many of us in this field are 'fixers.' We wish to point out those opportunities within the system and/or to be a part of the solution to those opportunities. Where we fail is in taking that long, hard look in the mirror and the opportunities within ourselves.
Case in point, the cap on the 'N' key on my laptop has popped off. This started a joke within the team - I mean, the 'N' key?!?! Why not the 'F' key? LOL! Someone suggested that I say 'no' too quickly. New approach to something in my portfolio? No. Revisions to my system/process? No. We all had a good laugh...but then I took some time to reflect on that.
Now, I ask people to explain their ideas and questions more fully. Rather than give an immediate, knee-jerk answer, I want to know more about what prompted the question or idea. It's easy to say 'no.' It's not so easy to listen (or read) and understand. It's faster to say 'no.' It takes time to listen (or read) and understand.
We see these fast responses here in the Cove far too often. We (myself included) jump in with solutions from the get-go instead of first trying to understand the 'why' behind the question/scenario.
Okay, so I was a tad philosophical and off topic, yet I think this was an excellent segue for many of us to pause, take a breath, and expand our listening/reading skills.
...and for those wondering about my 'N' key, I have not fixed nor replaced it. Makes for some difficult typing if I'm using my laptop keyboard instead of larger one plugged into the USB port, but it's a wonderful reminder of this shift in my approach to discussions.