The more time product teams and individual reviewers spend trying to understand an ECO, the longer the process takes.

Include only the information that is changing in the ECO. If you are asking for approval on a simple sourcing change, there’s no need to put the entire product specification in the ECO. Extraneous unchanging information just slows down the review process.

Attach relevant documentation to the ECO. Consider what information will help the team understand the nature and reason for the change. Do you have customer input? CAPA-driven resolutions? You can share information to give the reviewers the reason and impact for your changes.

Include redlined BOMs. Specifically, a redlined BOM that clearly indicates modified quantities, part numbers, reference designators, and makes it easy to see exactly what is changing. See an example below.

FIX #3: Route Electronic ECOs to All Internal Team Members and Partners

Once your engineering changes are managed online, it’s easier to track, review, and release changes to drive immediate product updates, especially with dispersed teams.

• Notify reviewers automatically. You can configure changes to automatically notify your change control board (CCB) or external reviewers via email with links to the related changes.
• Don’t limit visibility to the CCB. The change control board is not necessarily the only group that needs to know about pending ECOs. Let other people view and subscribe to product lines and related changes so that they are notified whenever ECOs have been submitted, modified, rejected, or approved.
• Create electronic approval traceability. Enable reviewers to approve or reject ECOs immediately, and let others see their decisions.
• Add additional reviewers on the fly. Your change boards likely comprise the same departments and players in most cases. However, you need the flexibility to add other reviewers or participants that may have additional responsibility or insights regarding certain product lines, types of changes, or unique situations. Your change management software should allow for adding ad hoc or additional reviewers as
  needed.

FIX #4: Route Your Changes to the Right People at Specific Stages Throughout the Product Lifecycle

New product development (NPD) and new product introduction (NPI) is continually evolving. Your company’s business processes change to meet new customer demands, technological advances, and specific innovations to your products. Having a dynamic and flexible change process that allows you to get changes to the affected teams and partners will ensure you can grow and scale as needed.

• Adjust the level of change control for each stage of development. Set up simpler revision controls for prototype parts and products. Introduce more controls with ECOs and change boards during limited production or volume production to ensure you can plan, build, and deliver high-quality products on time.
• Route different kinds of changes to specific people. Consider using different change board teams for various types of parts or product lines. This will ensure that those who know the most about any given product are the ones making the approval decisions.

FIX #5: Get Real-Time Access Online to Any ECO

Your ECOs contain critical information about your products and your process, so make it easy to access, review, and approve anytime and anywhere.

• Manage your ECOs in a single system or “source of truth.” This ensures everyone is always looking at the latest information.
• Send reminders to reviewers. Your teams are always busy, so send email reminders with a link to the ECO when they need to take action.
• Track ECOs from creation to release. Your ECO history will help your teams trace decisions and product changes. If issues arise (and they will) in the field or with customers, you can use your change history to identify why decisions were made, by whom, and drive faster resolution.
• Track all reviewers and status. When it’s easy to monitor who has reviewed ECOs, it’s easier to follow up when approval delays hit.