When talking to the user or subject-matter expert about an application’s requirements, write the requirements in the form of scenarios. A scenario both defines the requirement and provides a list of steps detailing how the resulting feature will be used. For example, instead of writing a requirement to “process payroll,” your scenario might be to select an employee from a list of existing employees, to enter the time allocated to the project for each employee, and so on. This clarifies requirements and helps you better visualize how users will use the feature. Once you understand the reasoning behind the request, you might even find a better way to meet the requirement. You can then use these scenarios as the test plan for the feature.