The Fundamental Distinction Between Problems and Solutions
User research in the Discovery phase aims to understand the broader problem space and user context. Research in the Delivery phase focuses on evaluating the usability and functional effectiveness of a specific proposed solution. In Discovery, a primary goal is to reduce uncertainty about what to build by observing behaviors and identifying latent needs. In Delivery, the focus shifts toward ensuring decided concepts are executed comprehensibly. Researchers often distinguish between what users state they desire and their actual observed behaviors, as these can differ. This is a general guideline, not an absolute rule, as user feedback can still provide valuable direct insights during transitions between phases.
Discovery Questions: Mapping the Unknown
During the Discovery phase, researchers employ open-ended and exploratory questions. A suggested procedure is to avoid leading prompts and instead focus on how individuals currently navigate their routines or tasks. Hypothetical examples of Discovery questions include: "How do you currently organize your financial tasks?", "What main obstacles prevent you from completing this goal?", or "In what hypothetical context might you need to look for this specific information?". The objective is to identify behavioral patterns and mental models rather than to validate a specific interface. It is less about asking if a user would like a hypothetical feature, and more about understanding if the underlying problem it aims to solve is genuinely relevant to their routine.
Delivery Questions: Refining the Tangible
When a project enters the Delivery phase, research questions become more specific, focusing on a tangible artifact or prototype. Teams test their solution hypotheses. Hypothetical examples of typical Delivery questions are: "What do you expect to happen when you click this button?", "Did you feel confused during this hypothetical flow?", or "How would you describe what this screen does?". Usability testing rarely proves strict causality; observations help indicate whether the design supports the intended user journey. While Delivery research is not intended to uncover new structural problems, researchers should remain open to unexpected findings, as late-stage testing can reveal fundamental misunderstandings in the product's architecture.
Boundaries and Transitions: When to Shift Focus
The transition between Discovery and Delivery is rarely linear. It requires methodological rigor to avoid extrapolating findings beyond their appropriate context. For instance, if during a hypothetical usability test a participant's feedback suggests the core issue is a lack of perceived value in the service, rather than an interface flaw, the team might return to Discovery to reassess foundational assumptions. While it is often inefficient to resolve value proposition gaps solely with interface improvements, reasonable exceptions exist, such as when strict project constraints require iterative compromises before a full redesign. Research should be planned in iterative rounds, ensuring appropriate questions are asked when the team can act on the resulting insights.
Sources
Plan user research for your service — GOV.UK
Plan a round of user research — GOV.UK
Related reading
Your next discovery begins with a question.
Test an idea, observe the experience and bring evidence to your team.
Create my first studyFree · 1 study · 50 responses/month · no card
