Design teams often need feedback on interface ideas before investing further in detailed design or in more extensive research. When development cycles accelerate — whether driven by AI tooling, automated pipelines, or simply competitive pressure — the temptation to skip early validation grows. Teams move fast, assumptions accumulate, and by the time research happens, too much has already been decided.
Lightweight unmoderated research
This talk explores how unmoderated UX research methods can be used to gather user feedback early in the design process and support design decisions with evidence rather than assumptions. Drawing on real product examples, Kamila will share practical approaches to using several lightweight, unmoderated methods:
- first-click testing,
- preference testing,
- card sorting and tree testing,
- anticipation testing.
These are presented not as a catalog of techniques but as a set of targeted interventions. Each method produces a specific kind of signal: where users expect to find something, which direction feels more intuitive, how well a structure matches a mental model. Used at the right moment, these signals can redirect a design before significant effort is invested in the wrong direction.
User signals for speed
The intended angle of the talk is not about AI tooling and AI-assisted workflows but rather about how teams can maintain good UX judgment when product and design iteration cycles become increasingly fast. The core argument is that speed itself is not the enemy of good UX — but speed without any user signal is. Unmoderated methods fit into fast cycles precisely because they are low-overhead. They are not a replacement for deep research; they are reality checks — moments where the team pauses, tests an assumption, and decides whether to keep going or course-correct.
Design-research collaboration
The talk will discuss how these fast-testing approaches affect collaboration between designers and researchers. When lightweight testing becomes a regular practice, researchers are no longer called in at the end, and teams validate ideas earlier and more frequently. The final design judgment remains with the designer. The researcher is a partner who makes sure that that judgment is informed by something real by bringing the users’ voices into the process.
Takeaways
Attendees will learn when these methods are useful, how they can be incorporated into existing workflows, and what kinds of insights they can provide for product and design teams. Attendees will also receive a clear framework for choosing when and how to apply each method, a set of examples from actual product work, and a way to talk about the value of fast testing with teams and stakeholders who see research as a slowdown rather than a safeguard.
Target audience
This talk sits at the intersection of research practice and design craft. It is relevant to:
- designers who want to validate ideas more confidently,
- researchers who work in fast-moving product environments, and
- anyone thinking about how to preserve UX quality when the pressure to ship is high.
