Maintaining useful business documentation
patio11: At my day job, we put everything permanent in a wiki and everything temporary in Trac (our issue tracking software).  It turns out that engineers spent most of their time in trac rather than the Wiki, so that gradually is becoming the authoritative option.For my business, I have three things: I have a succession of paper notebooks for any idea that can get garbage collected in less than a week.  This is good for, e.g., A/B tests.  (Why am I doing an A/B test with the Dropbox style invites?  Flips open notebook to last page.  Oh, that's why.)You're going to laugh at me for this, but for long-term, searchable business documentation... I use my blog.  What the effity was I thinking when I launched this feature two years ago?  Search for my blog post about it.  (Issues too minor for the blog have commit notes in subversion.)If I were more worried about exposing my ideas to the world, I'd use an internal wiki-style software instead of the blog.The third thing, which is perhaps less useful as an answer but still true, is that I have very, very good memory for the written word.  (This is one reason I write so darn much.  Anything I write and almost everything I read, I get to keep.)