UX Teams Need Shared Goals Before Detailed Screens

Designers often feel pressure to show their value by producing work faster. They may shorten research and move quickly to detailed screen designs. But the article argues that speed can hide a more important problem. A team may already have chosen its direction before learning about users. Making screens faster does not fix that decision process.

The author compares this problem with the advantage of an early answer online. On Stack Overflow, an early answer can collect attention before a better answer appears. In a product team, an early idea can also shape later decisions. People may agree on a plan before checking whether its assumptions are sound. User research can then seem like a delay instead of useful evidence.

Detailed mockups can make an uncertain idea look complete and ready to build. A mockup is a picture of how a screen might look. It can show a possible solution, but it cannot prove the problem matters. The article warns that teams may fill research templates with guesses rather than evidence. Polished screens can make those guesses harder to question.

This also explains why releasing a product does not always lead to learning. The delivery team may receive new information from users after launch. But that information has little effect if the people setting priorities ignore it. Designers can then receive blame for poor results, even when the original idea was weak. The author says designers should help shape decisions earlier instead of simply speeding up delivery.

Simple tools can support those earlier conversations without making a solution look finished. A storyboard shows a customer's situation and the change a team hopes to make. A PRFAQ uses a proposed press release and questions to discuss an idea. These tools can help decision-makers agree on customer needs and business goals. They also make it easier to reject an idea before detailed design begins.