- Ask teams not to document requirements or describe everything in details. Instead of that ask them to document the decisions they made while coming to an agreement about requirements. It might sound the same, but writing down “why” is more important than “what” because it helps you better understand the product and learn.
- Documentation has two purposes: communication, and memory. From my (most people will share that i think) experience is that written documentation is a very poor way to communicate. It’s a pretty good way to remember things. And maybe sometimes code is the best way to “remember” things rather than creating a pile of documents which will be outdated in less than a month.