The requirements "sweet spot" is the balance point of the greatest amount of understandability and the least amount of ambiguity.
A learned skill, finding the sweet spot will depend on the team members ' abilities , the application context, and the level of certainty you must provide so that your system works as intended.
If the risk of misunderstanding is unacceptable, more formal requirements techniques may need to be applied.
![Managing Software Requirements[c] A Use Case Approach](/icons/blank_book.jpg "Managing Software Requirements[c] A Use Case Approach"){kind=icon}