Your question is Clarify Ambiguous Project Requirements. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
You are starting a new cross-functional initiative where the business goal is clear, but the requirements are still vague and different stakeholders are using the same terms to mean different things. Before the team commits to delivery dates or starts detailed analysis, you need a way to reduce ambiguity, align on scope, and make sure the team is working from the same understanding.
How do you handle ambiguity in project requirements and ensure clarity for your team?