Personally, I always used auditing
teams including a cross-functional group of members.
I don't get quite as vehement as some about
"shall not" audit own work as long as it is an open process in the presence of team members whose work is not under scrutiny. In small organizations, many folks wear so many hats, it is impossible for there to be anything for them to audit if we adhere to such a proscription.
I agree, also, that any audit is not a license to play gotcha or policeman. Unfortunately, we still see posts from folks who retain the idea the auditor is a cop with extraordinary powers of police, judge, jury, and executioner.
In my ideal world, the auditing team familiarizes itself with the plan for the process being examined by reading through procedures or work instructions. They then observe the PROCESS in operation (note - the
process, not the individual worker.)
If necessary, they ask clarification questions. Then they match what the plan says should be happening with the actual process and note one of three things:
- everything proceeds according to plan - the process conforms
- there is a glitch between plan and activity - this may be referred to process owner or a special team for confirmation and possible Corrective Action or Preventive Action
- the process conforms, but there is an opportunity for improvement
Note in number 2, I do not consider the audit team responsible for staying in business to monitor and approve a CA/PA, similarly to the process in Management Review, where the reports are given to management to decide on action or no action. This takes away the "unlimited police power" aspect of an audit and removes many situations from a personal ego slant where an auditor feels pressure to prove he is right and process owner is wrong.