What usually causes more rework in your SaaS: bad UI or unresolved product decisions?
retained text
<!-- SC_OFF --><div class="md"><p>I have been reviewing a product flow where several screens had already been designed well.</p> <p>The problem was that important behaviour around those screens was still undecided.</p> <p>Who owns the next action?</p> <p>What happens if a payment stays pending?</p> <p>Can a user recover something they purchased after the product is removed?</p> <p>Which states should support handle manually, and which should the product resolve?</p> <p>Each unanswered question eventually looked like a UI issue because the screen was where the confusion became visible. But redesigning the screen alone would not have settled the underlying decision.</p> <p>It made me wonder how other SaaS teams recognise the difference.</p> <p>When a flow keeps getting redesigned, how do you determine whether the interface is genuinely weak or the team has not agreed on how the product should behave?</p> <p>Do you have a review process for this, or does it usually become clear only during development and support?</p> </div><!-- SC_ON -->   submitted by   <a href="https://www.reddit.com/user/T07NAD0"> /u/T07NAD0 </a> <br /> <span><a href="https://www.reddit.com/r/SaaS/comments/1vgsmp3/what_usually_causes_more_rework_in_your_saas_bad/">[link]</a></span>   <span><a href="https://www.reddit.com/r/SaaS/comments/1vgsmp3/what_usually_causes_more_rework_in_your_saas_bad/">[comments]</a></span>
document fetched 2026-08-06 08:32 · canonical https://reddit.com/r/SaaS/comments/1vgsmp3/what_usually_causes_more_rework_in_your_saas_bad