I use a cascading "knowledge" system myself: - A pocket Moleskin notebook keeps track of random thoughts, notes, scratches, diagrams, and more. - This eventua

I use a cascading "knowledge" system myself: - A pocket Moleskin notebook keeps track of random thoughts, notes, scratches, diagrams, and more. - This eventually becomes either "tickets" in my issue tracker, or becomes "wikis" or "wiki updates" on my wiki server. - This eventually leads to things like: snippets, configuration notes, historical documents, record keeping, runbooks, and more. Eventually it just became "natural" to keep my documents up-to-date, or as issues are discovered get them thrown into the correct backlog.