bmad-agent-pm

To turn user interviews into a product requirements document (PRD), you need structured requirements discovery to identify the underlying problem, followed by lean prioritization to define the smallest valuable solution. This ensures the resulting PRD is grounded in actual user value and stakeholder alignment.

Breaking down epics from a vague feature request requires user-centered analysis and stakeholder alignment to validate assumptions. By focusing on the smallest valuable solution, you can translate fuzzy ideas into actionable implementation readiness steps and clear next steps for your product team.

To validate product requirements before implementation, you must check implementation readiness and ensure lean prioritization defines the smallest valuable solution. This involves reviewing the PRD against uncovered user needs and aligning stakeholders to confirm the requirements solve the actual problem.

Yes, you can use requirements discovery and stakeholder alignment for midstream course correction on an existing PRD. This involves re-evaluating user needs and adjusting the product requirements to ensure the project remains focused on the smallest valuable solution.

Aligning stakeholders when defining product requirements requires user-centered analysis and structured questioning to uncover real user needs. By grounding product decisions in user value and lean prioritization, you ensure all stakeholders agree on the smallest valuable solution before implementation.

Requirements discovery is the process of guiding structured questioning to identify the underlying problem before solutioning. You need it for product management when you have fuzzy ideas or vague feature requests and must turn them into clear, actionable product requirements backed by user interviews.