I liked this a lot. Wachter-Boettcher walks you through some basic steps about analyzing the mass of your content and trying to find that "just right" level of detail (although in many cases we have to do this before we know what all we are going to need in terms of content). She encourages building bridges between the technical team and the CME's. And then she also argues for building some structure into our content with the hope that we can then use it in API's. (All the more reason to use LibraryThing!)

The weakness here is that it can be difficult to apply... in my situation, we have a ton of content, very disparate (university), and some amount of system lock-in (resource constrained, like all organizations). But contemplation is the first step, and this little book will be one more nudge in that direction.

My list of links and notes and related items is at http://chellerystick.com/lists/content-everywhere-home-companion ( )