Hopefully if the user needs are not met as @hc255 mentions above, they would go back to the spec and make sure the output meets the user needs and intended use. I really don’t think there is any room for compromising during Design Validation, because if you end up releasing the product without addressing all these user needs, then that may cause issues with sales and customer complaints. Although going back and re-validating could be time consuming or costly, making compromises and releasing a product that isn’t meeting all the user needs and intended use will ultimately become more time consuming, costly and detrimental for sales down the line.