The question
Teams can agree on a solution name while holding very different expectations of what it should do. Explore the underlying process and the outcomes expected before treating the feature list as a complete brief.
The approach
Follow the work across team boundaries, gather concrete examples and define the rules that govern important decisions. Use these conversations to expose ambiguity while it can still be resolved without changing a built solution.
The decision
Agree a requirements baseline that connects the business need to design and evaluation. Record assumptions, maintain a change path and give the people delivering the work a common reference.