How would you coach a junior business analyst whose requirements are too vague?

Sample answer preview

I would show them how to move from vague language to observable outcomes. We would take one requirement and ask: what business need does it support, who uses it, what decision or action changes, what acceptance criteria make it testable, and what assumptions need confirmation.