Research as Decision Input reframes UX research around the specific decisions it must inform. The unit of value is the decision changed, not the report delivered. A study that runs for three weeks, lands in a 40-page deck, and does not change any shipped product is a more expensive failure than no study at all.
Hall (2019) argues that "just enough research" is the right scope: enough to make the decision in front of you, no more. Torres (2021) extends this with continuous discovery: research happens weekly, scoped to the decisions teams are making weekly. The shift is from research as a deliverable to research as a verb tied to decisions.
The finding from industry surveys is consistent: teams that frame studies around specific decisions report 3-5x faster cycle time and stakeholders use the findings at materially higher rates than teams that deliver polished general reports.
The principle: Name the decision. Scope the study to inform it. Stop when the decision is unblocked, even if more could be learned.
Decision-scoped research draws from several converging traditions: lean UX, continuous discovery, jobs-to-be-done research scoping, and the older "just enough research" methodology.
Hall (2019) made the case in Just Enough Research that research methodology should scale to the decision at hand. Her central claim is that exhaustive research often serves the researcher's discomfort with ambiguity more than the team's actual need. Calibrating method, sample size, and duration to the specific decision saves weeks of cycle time without measurable loss in decision quality.
Torres (2021) reframed product discovery as a continuous practice in Continuous Discovery Habits. Her research with product teams found that teams running weekly customer touchpoints scoped to current decisions ship features that match real user needs at substantially higher rates than teams running quarterly large studies. The unit of work is the opportunity-solution tree mapped to a specific outcome.
Sharon (2012) addressed the stakeholder side in It's Our Research. His research with research teams across enterprise and startup contexts found that research delivered as standalone reports has a 38% lower adoption rate than research framed and timed to specific team decisions. The mechanism is attentional: stakeholders who did not ask the question do not read the answer.
Portigal (2023) updated Interviewing Users to emphasize that even individual interviews should be scoped to a decision. The interview that "explores user needs" generally produces less actionable signal than the interview that asks: "if this specific product change shipped, would users actually use it?"
For UX Researchers: Decision framing protects research from becoming a service function that produces output nobody uses. Researchers who scope studies to decisions get cited more, included in product reviews more, and survive layoff cycles at higher rates.
For Product Managers: PMs are the primary consumers of research. Research scoped to your specific decision is research you will actually read and use. Research scoped to "user understanding" is research you will skim.
For Designers: Designers run more of their own research now than ever before (Userlytics 2024 found 70% of UX designers conduct their own studies). Scoping each study to the design decision it must inform protects design time and produces sharper output.
For Founders and Solo Makers: Founders running discovery without a research team need a discipline against "generic discovery". Every conversation with a user should be scoped to a specific decision the founder is about to make about the product.
The decision-input frame can be applied at any scale, from one-day studies to multi-month research programs.
Name the decision before naming the method. Write down the specific decision the team needs to make and the date by which it must be made. The method follows from the decision and the timeline, not the other way around. "We need to choose between two onboarding flows by Friday" yields a different study than "we need to understand new users."
Define the decision-flipping bar. Before running the study, write down what evidence would change the current direction. If no observable result would flip the decision, the study is theater. Either reframe to a real decision or skip the study.
Calibrate sample size to the decision, not to academic norms. A 5-person usability test can unblock a $20K design decision. The same 5-person test cannot answer "what is the optimal market positioning of our product." Pick the decision the sample size fits.
Stop when the decision is unblocked. If the third interview already produced an unambiguous finding that flips the decision, the remaining seven interviews are sunk cost. Stop the study and ship the decision.
Report findings inside the decision context, not as standalone deliverables. A two-paragraph email tied to the specific decision, sent to the decision-maker on the day they need it, has higher adoption than a 40-slide deck two weeks later. Format follows function.