Most specifications and requirements documents always talk about “what it does” and rarely does it ever talk about “what it doesn’t”. People create to do lists, and everyday we think about what we need to do, but how often do we think about what not to do?
Talking about what not to do is just as important as talking about what to do. Sometimes you can have so much to do’s that you just don’t know where to begin.
E.g., To be a good leader you must lead by example, and not be violent.
Knowing what not to do provides a more defined set of boundaries. There is nothing wrong with to do’s, but the to do’s can be made clearer when combined with not to do’s.