Talk to engineers or search the Web about Engineering Change Orders (ECO) and you will quickly realize you have stumbled into dreaded territory. People who engineer either the design or the manufacturing processes generally love their jobs, but universally cringe at the thought of having to request, document, and implement changes to their work after the fact.
One reason engineering team members cringe in reaction to ECOs is because they instinctively recognize inefficiency when they see it. In this era of computer-based automation and efficiency, ECOs seem to have been left behind. They are usually created on spreadsheets then processed manually and informally using nothing more sophisticated than Windows Explorer and email. It is a process offering no chance for department-wide visibility, no way to automate the surrounding information flow of alerts, status, and approvals, and no way to create a useful audit trail for future reference.