In regulated industries like medical, aerospace, or automotive, rigorous development processes are essential. Risk assessments, validation plans, documentation - they’re required, and for good reason.

But what if your product isn’t regulated? Do structured engineering processes still matter?

I believe the answer is YES - but not always in the same way. The key is 𝘤𝘶𝘴𝘵𝘰𝘮𝘪𝘻𝘢𝘵𝘪𝘰𝘯.

𝗧𝗵𝗲 𝗣𝗿𝗼𝗰𝗲𝘀𝘀 𝗧𝗼𝗼𝗹𝗯𝗼𝘅 𝗜𝘀𝗻’𝘁 𝗢𝗻𝗲-𝗦𝗶𝘇𝗲-𝗙𝗶𝘁𝘀-𝗔𝗹𝗹

Checklists of required engineering processes, like code reviews, traceability, CI/CD, and risk management, are often defined at the industry level, especially in safety-critical fields.

But these frameworks are usually “one-size-fits-many,” and they often assume that every process must be executed in a rigid, predefined way.

If you are working in a regulated field, required processes are part of the cost of doing business.

However, if you are in an unregulated field, where certain processes aren’t required, that doesn’t always mean it’s wise to skip them.

𝗔𝗱𝗮𝗽𝘁 𝗣𝗿𝗼𝗰𝗲𝘀𝘀 𝗮𝗻𝗱 𝗘𝗹𝗲𝗺𝗲𝗻𝘁𝘀 𝘁𝗼 𝗙𝗶𝘁 𝘁𝗵𝗲 𝗣𝗿𝗼𝗷𝗲𝗰𝘁

When planning your project, it’s important to understand the purpose of each process element, weigh the costs and benefits, and include only what makes sense for your project’s goals and risks.

Take risk management. Its purpose is to identify hazards, estimate severity and likelihood, and identify potential mitigations prior to starting the design. You don’t necessarily need a formal report to be submitted to a regulatory agency, but a quick whiteboard session might be enough to surface key risks and avoid surprises down the line.

The key to customizing the process and its individual elements is recognizing that without risk management, its perspective is likely to be forgotten or underemphasized, and that even a lightweight approach can significantly improve project outcomes.

𝗣𝗿𝗼𝗰𝗲𝘀𝘀 𝗗𝗲𝘀𝗶𝗴𝗻 𝙞𝙨 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴

Engineers love solving problems - but we sometimes forget that the process we use to build a product is itself a design problem.

A great process:

• Supports quality where it matters
• Eliminates waste where it doesn’t
• Fits the team’s working style
• Aligns with the product’s goals

At Wolff Electronic Design, we propose customized processes that reflect this thinking: just enough, not too heavy, not too light.

𝗟𝗲𝘁’𝘀 𝗦𝗵𝗮𝗿𝗲 𝗡𝗼𝘁𝗲𝘀

What’s your experience been with customizing (or not customizing) engineering processes? Where has it helped or backfired?

By @Greg Burk originally posted to LinkedIn

#EngineeringLeadership #ProcessOptimization #WolffElectronicDesign