Strong BAs do not begin with a feature list. They begin by understanding why the initiative exists, who is affected, what evidence already exists, and which uncertainties must be reduced first. Preparation turns discovery from a collection of meetings into a decision-making process.
Create the conditions for useful discovery before asking for detailed requirements.
Clarify the problem, business drivers, desired outcomes, boundaries, and constraints. A project can deliver every requested feature and still fail if the team has not agreed what success means.
Each step reduces a different kind of uncertainty before delivery begins.
A retailer asks for a redesigned checkout because mobile conversion is falling.
Clarify the target segment and expected conversion improvement.
Review funnel analytics, support tickets, existing flows, and payment failures.
Interview support and product, then observe five mobile users completing checkout.
Prioritize the highest-risk assumptions for prototype testing.
The team learns that address validation—not visual design—is the largest failure point and redirects the first release toward measurable impact.
Open each answer, then practice saying it naturally in your own words.
Use a clear sequence: purpose, stakeholders, evidence, discovery plan, collaboration setup, risks, and milestones. Explain what each step prevents.
A condition or goal motivating the initiative.
A fixed limit such as time, budget, regulation, or technology.
A belief treated as true until it is validated.
Work or an external condition another outcome relies on.
Answer all three questions. Score 2 out of 3 to pass this section and update your course progress.
Choose one answer for every question, then submit your quiz.