It might be now? Honestly, it probably is, given the reworks.

But the problem with the Eight, at least initially, was the way the suppliers were organized. Or, more specifically, how they weren't organized. Boeing had flushed through a half dozen generation of Systems Engineers in the aughties, and no one really had a half chance to get familiar with anything that was laid down before. Suppliers generally took their best guess and went with it - that's where we were, at the time, because it proved completely impossible to make any contact with a person at Boeing who knew what the FMS data bus was . . or, on most days, even what a FMS data bus was. So we guessed either ARINC429 or ARINC664 and got (mostly!!) lucky.

There were also some . . ah, I don't want to say "bad" . . so let's say, "non-technical" SEs . . who advocated for their own vision vis a vis SE and supplier management. In short, this was a giant mish mish, and, speaking for myself, it colored my personal perception of Systems Engineering as a discipline to this day. While you get some real SE rockstars, you also get an epidemic of shysters with mild sociopathy, and it takes good, technical leadership to tell one from the other.

Keep in mind this was . . sheesh . . almost two decades ago, so take it all with a grain of salt.

System Engineering is a technical profession. I honestly don't think is does anyone any good to avoid calling nontechnical SEs bad at the job. The truth is important especially when it leads to the development of metal tubes that fly 150+ people through the air at hundred of miles per hour.

With that said, a nontechnical SE is a sign of a fundamentally broken system and org. Someone had to hire them for the role. Meaning they were interviewed and deemed fit for the role, likely with room to grow given more experience and opportunities to learn from. While I would say a nontechnical SE is bad st their job, stopping there doesn't fix the problem at all and its important that the context of why they had that job isn't lost.