This sounds like the opening of a joke so I apologize to those who are reading this expecting a laugh or two 🙂 This is actually your chance to help out an analyst, namely, me.
In my recent research on business relevant use cases for social software I have assembled a set of general use case categories (set not yet ready to expose). One of the general use cases involves the movement from single author (or constrained authorship), point-in-time, sequentially constructed, bounded documentation to multi-author (or less constrained authorship), dynamic, simultaneously constructed, long-lived documentation.
To simplify this with a general usage example, the first is me, creating a document, sending it to a few others for co-authorship, using it for a relatively short period of time, and storing it somewhere (in a folder structure maybe) for possible resurrection at some point in the future for a new revision (thus again kicking off the loose “workflow”). Second is us simultaneously creating, expanding, and continuously maintaining documentation for a long lived purpose.
To simplify with a technology example this is a Word document v. a wiki.
Using a “publishing” example this is Encyclopedia Britannica v. Wikipedia.
So here is my challenge where you can help. I need a good name for this use case category. Although, “multi-author (or less constrained authorship), dynamic, simultaneously constructed, long-lived documentation” is quite descriptive, you might agree that it is a bit cumbersome 🙂
This is a “call for a better term.” What term do you use (something descriptive rather than wiki or collaborative documentation)?
View Free, Relevant Gartner Research
Gartner's research helps you cut through the complexity and deliver the knowledge you need to make the right decisions quickly, and with confidence.Read Free Gartner Research
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.