Structured Content and Content Reuse

I just finished a two-day training class on managing structured content. The main ideas in the class were around how to analyze your content and create a content model, then identify where text can be reused. Single-sourcing (creating content once and using that as the source of all of your content types) and reuse were the underlying themes.
Our division already follows these guidelines pretty closely, so I probably won't be able to apply the information immediately in a practical way; say, by creating a new content model and content management system (since those things are pretty well established in developer division user education). But it did help me understand the ideas behind what we are doing, and why our tools work the way they do. If I ever move to another division that doesn't have these tools and processes in place, at least I'll have an idea of where to start.
We are not doing much about content reuse. In the documentation, we try not to duplicate information—we link to the information in another topic instead. We do reuse in the sense that the documentation is also available on the Web at https://msdn.microsoft.com, but the documentation is not changed in any way. I think of the Web as being another delivery mechanism, rather than another information product. I think that reuse would be more along the lines of taking pieces of our content and constructing another type of information product, such as a brochure or a quick reference card.
It seems that we could reuse some content in marketing materials, but marketers generally use a slightly different language than we do in the documentation. I think a marketer would not be very excited about taking the simple, direct language we use and putting it on the outside of the product package or on a poster, just as we would be careful about putting marketing language in the docs. Although we are looking at what it would mean to sort of bring the two together in some cases.