Kazanan
User research and product scope
Web Design and Development describes wider website delivery, while design research examines the people and decisions behind a particular journey. Collect the available material before choosing a method. Existing support questions, analytics and user access can answer different questions. A research plan should explain which uncertainty it addresses and what remains outside the available evidence.
Separate observed behavior, interview statements and assumptions about a persona. A support message may reveal confusing wording without establishing how frequently every user encounters it. An interview can explain expectations but does not automatically predict use of the redesigned flow. Name participant profiles, relevant tasks and access constraints. Do not present a hypothetical group or a planned session as completed research. The buyer needs to understand how a recommendation follows from the evidence actually available.
Prioritize flows through task importance and uncertainty rather than screen count alone. Decide which users can participate, what questions can be answered and who accepts the findings. Where access is missing, keep that limitation in the recommendation. A focused investigation may support a small correction rather than a whole-product redesign. Record unanswered questions so later teams can distinguish a design chosen under a constraint from one validated through direct observation.
