"The PM used Stitch by Google to create designs after our Miro session. To the untrained eye, it looks like a finished design. But when you look closer, it's not quite right and a little bit broken in places."
"For years, we've followed one cardinal rule when talking about UX: never show high-fidelity mockups until they've been validated. I've said similar things in the past, for good reason. One of the biggest? It set unrealistic stakeholder expectations. Show something that looks finished, and people think it is finished."
"Then, when user research reveals problems, you're stuck explaining why that "done" feature needs to change."
AI tools can generate polished-seeming interfaces quickly, producing artifacts that look finished but contain subtle flaws and incorrect assumptions. Showing high-fidelity mockups prematurely can create unrealistic stakeholder expectations and make later research-driven changes harder to justify. Traditional UX guidance to avoid high-fidelity deliverables before validation must be reevaluated in light of AI's ability to simulate completion. Design teams should explicitly signal provisional status, prioritize early validation, and adapt workflows to separate visual polish from validated functionality. Clear communication, labeled artifacts, and rapid testing practices can preserve research-driven iteration while leveraging AI for speed and ideation.
Read at Medium
Unable to calculate read time
Collection
[
|
...
]