Start with the system boundary, not the feature list
Teams often jump to screens and tickets. A clearer first move is naming the system boundary: who interacts, what data crosses the edge, and which decisions sit outside your control. That single diagram keeps requirements from sprawling.
In our systems analysis studio we ask every cohort to draw the boundary before listing features. Disagreements show up immediately—and that is useful. Document them as open questions with owners instead of forcing a premature answer.
If your group is preparing a rebuild or integration in Ho Chi Minh City, bring the messy notes you already have. The training is built around your case, not a canned retail demo.