It takes, at a minimum, twice as long to fix an mistake than just slowing down and avoiding it. Example - functionality check, condition is accidentally selected as "good-cannot restore to factory" instead of "good" and a service LP prints...the process next is for someone with Nova access to create a "None Quit" service order...then you need to create a new open box LP in RSS, then someone with Nova access will need to create the open item service order off new LP...these systems do not talk to each other right away, this mistake could be spread out over many days. It may easily lead to inventory issue or a no pick...Even after all that it may take help desk ticket to fix (cannot create LP for sku in func check, even though func check is closed)...so as long as you are a role model, and have made expectations clear, formal accountability (write up) is appropriate when such mistakes are made.