Recent research suggests that as much as 50% of explained sources of variation in software code inspections relates to people related issues and less than 30% relates to inspection processes. This paper examines the impact of two feedback mechanisms (process maturity and inspector proficiency) on inspection processes. Results of a survey of thirty-one experienced software developers and some follow-up interviews are presented. Variations appear to exist within organizations at the process level even within a relatively mature development organization. Process maturity and inspector proficiency constructs are difficult to measure. The findings should extend to other formal technical reviews and provide insights into managing different- place, different time inspections.