This is why design takes calendar time rather than simply clock time. You can't just schedule a block of time in which to review the Data Driven Insights and make the Design Decisions. The wastewater needs time to slosh around and clear out before the good stuff can get flowing.
It's hard to explain this to colleagues. Not only is it embarrassing to share the bad stuff, but many of the "try it" cycles happen entirely in the designer's head or as incomprehensible sketches. And they don't have the context to recognize the hi-fi bad stuff as bad.
"Let's just build that and see if users like it" extends the feedback cycle unnecessarily. You don't need to spend resources on the wastewater to know that it's bad. Until there's a kernel of quality, throwing build resources at an idea is a waste.
(this is not to say that we can truly judge the quality of a designed user experience until users are experiencing it, but it should at least have the faith of the designer before being put to that test)