Requirements are the foundation of business analysis. Good requirements save projects from costly mistakes. Poor ones cause confusion, rework and frustration.
“The system should be fast” is vague. “Search results should load within two seconds” is testable.
User stories such as “As a customer, I want to reset my password so I can access my account” keep the focus on real needs.
State how you will know the requirement has been met.
Describe what is needed, not how to build it.
Review requirements with the people who asked for them before work begins.