There is a lot of advice out there for how to write requirements. There is not as much discussion about why to write requirements. Spend some time thinking about why you write requirements before you make decisions about how to write your requirements.
Whether you communicate requirements through conversation, user stories with acceptance criteria, or traditional structured requirements and use cases, or diagrams and commentary, you are sharing them as a means to an end – creating the right product. Don’t just follow some prescription and go through the motions of documenting requirements. Take a step back and consider the following goals for your requirements-writing.