It sounds like you are trying to build in a workflow to a tool that does not have much workflow. But one or two ideas spring to mind that may spur some thought for you:
1) have a sub-space or separate group where the discussions are turned into documents. The members would just be your admins and maybe the occasional additional person needed as a subject matter expert. This way all docs are visible. Possibly add a manual standard to put in the doc title or first line of the body so everyone knows where things are at (Initial, draft, review, final). Once it is ready the Jive Move doc function is pretty easy to then place the final document in its final home.
2) similar to above but use the Idea module (assuming you own it). There are phases there that are more for ideation, but you could re-purpose them as to the phases of your discussion to doc transformation. The editor in the ideas is exactly the same as the document editor...once you are finalized you would probably need to cut and paste from the idea to a document. Maybe even some of the idea widgets will add value to this "working group or sub-space" to help manage the process a bit.
So good luck on this!
Andrew is right, Jive doesn't have a lot of workflow, but it does have a little. Are you using the approval feature available under the Collaboration options?
We are using the approval feature that Jive provides which is part of our problem. Since the Space Administrator role is shared between two people, they are struggling to see which discussions have documents created by their peer. It doesn't make sense for them to put each other on as an approver upon creation just so the other person can "see" the document was created, considering the document isn't really ready for approval. What they really want is the ability for the Space Administrator to see all documents in draft for their given space, regardless of who drafted it.
We have a "mining" space that fits what you are describing. Helpful discussions across all communities are converted to documents and placed into this mining community for editing by a group of technical writers, and then reviewed by SMEs. We've kept it simple and have been using tags as a means to move a document through workflow (draft, edit, review, publish).
I have been playing around using categories to implement the same, and using the categories widget to get a dashboard showing the number of docs in each workflow step.
Andrew - I love the idea of using the Ideation module!
Hi Christine --
I've debated the approach of a separate space for the activity of creating the official document, but go back and forth. How do you handle the approval aspect? The approvers for our documents vary from document to document. Are you using the comments on a document to @mention the necessary people as well as obtain feedback on the document or can anyone edit the document. How are you notifying approvers of changes once they've already approved a specific version?
I'm interest in how you are handling this as the management of the content continues to be a "hot topic".