I'm an engineer who runs a business. I know the tradeoff between technology and costs. And figuring out how and where something should be validated is not a "business decision". It might be a business process decision, but unless it affect the bottom line (for example, the validation costs $50 so we only do it when a customer is just about to purchase) it's not a business decision.
There's a real problem with engineers not understanding business just as much as there's a problem with business types not understanding engineering. I had one of my engineers say to me once "I don't understand why we have sales people" (hint for those of you nodding along with him - it's so we get income so the engineers and everyone else can get paid). I've seen companies where engineering gold-plated the systems architecture to the point where the company couldn't make money with the deployed hardware.
Business isn't all that complicated and anyone competent as an engineer should be able to understand it (you may not like it but that's another issue entirely). Figuring out how the costs of a system affect the business, how the features in a product affect its salability, these are things that a good engineer will understand, and will probably wind up explaining to the business people.