Describe how you would run a requirements playback session and why it matters.

1. The purpose is to confirm that what I documented matches what the business meant — and misunderstandings are far cheaper to fix at this point than after a build.
2. I send the material in advance so people arrive having read it, and open by restating the business objective, so the session is anchored to outcomes rather than field lists.
3. I walk through the current-state map, the pain points, and the requirements in business language, avoiding Salesforce terminology with a non-technical audience.
4. I actively invite disagreement. Silence in a playback usually means people have not engaged rather than that they agree, so I ask direct questions of specific people about the areas they own.
5. I close with explicit confirmation, open items with named owners and dates, and a written summary. Verbal agreement in a room is not a baseline; the written confirmation afterwards is.