·         Do you rely on any vendor documentation for products/tools you use? 

I try to. Sometimes our particular practices require supplemental info. 

·         What ways do you make your documentation available for people to use?  (file share, wiki, intranet, etc.)

File share on a network drive. Another unit I worked with was big on using the intranet. What I liked about the intranet was that you could read descriptions of what was behind a link, instead of trying to decipher file names. My staff at Berkeley are using file shares. Since we don't have an intranet, we won't be going that route. We're a Google customer--gmail, Drive, etc, but we aren't using, don't have? Google Sites or I might try to use that. 

·         What are some things you’d wished were documented when you first started your position?

I've always asked my staff to train me on how to use their systems. :-)  I try to get staff from different units (catalogers, in addition to acquisitions staff, for example) to show me things. This way I get multiple perspectives. I try to refer to the manual only when people don't know how to use a system. 

Probably the thing I most wish to find documentation on are the complicated things, the medium to big picture things--how does this affect that. We have someone here who has spent more than a year getting a handle on how we manage our 745 funds, more than half of which are endowments. There was some documentation, but there were gaps, some inner working type things missing and perhaps some big relationship/impact if you don't do X things missing. She's written a lot of clear documentation. And has "forced" me to document various process changes I've made that are very complex and mostly in my head. I think it's the hard stuff that's in your head that people will wish they had on paper.