it gets back to the basics of "is the aircraft a dud because it doesn't do what it was designed to do" as opposed to "is the aircraft a dud because it doesn't do what we want it to do" which unhappily usually means that the engineering and design brief never considered the "new" requirements
unless the plane is a complete dud at the design level (ie inherent design flaws) they're all a legacy of being developed to meet the demands of the conops used to inform the engineers
its rarely the plane which is a dud - its usually an expectation centric issue wrapped around "additional requirements" which should have been factored in from the beginning if the development cycle had been done at qualified and considered pace
garbage in - garbage out across design, development, engineering, force and platform modelling, user input, service intent stages.....