Below is something I am working on at my job. It is a set of recommendations designed to suggest a system in which people in the company are encouraged to publish information to each other and collaborate with and through that information.

I think these recommendations are worth posting here as they suggests a set of requirements that microcontent oriented systems (like the iCite net, wikis, blogs, etc.) might best match. (note: you also might notice that I imitated some of the W3C's Recommendation Track Process Maturity Levels.)

***

Note: the word "public" is used to indicate that information should be made as widely available as possible. In general, "public" in this context, at this time, means the whole enterprise of company employees, and not customers, partners, vendors, or competitors of the company, or the "public at large".

With any specific information, there may be process, security, regulatory, etc., requirements for privacy of information, and these must be adhered to. But, except for such requirements, information should be made "public", and enterprise processes should encourage information being as public as possible.

Meetings

1. Meetings published (by meeting caller) to a public calendar. Meeting information should include at least a descriptive title and list of participants with their contact information

2. Meeting agendas published (by meeting caller) to the public

3. Meeting agendas accessible through an annotation / editing mechanism through which meeting invitees can adjust the agenda

4. Meeting notes published (by each meeting attendant who takes notes) to the public

5. Meetings notes accessible through an annotation / editing mechanism through which meeting attendants can annotate and edit the meeting notes

6. Meeting notes are associated with a discussion mechanism through which the public can discuss the topics of the meeting

7. Meeting notes and meeting discussion are associated with a notification mechanism which the public can subscribe to in order to track developments around this topic

Documents (requirements, processes, and standards)

8. Documents representing requirements, processes, or standards are published (by document author) to the public, in a progression of releases to each solicit feedback. These releases are:

8a. Working Draft: A Working Draft is a document published (by the document author) for review by the public to solicit early contributions and to establish the participants in a Working Group to flesh out the document

8b. Candidate Recommendation: A Candidate Recommendation is a document that has been widely reviewed and satisfies the Working Group's requirements. A Candidate Recommendation is published to gather implementation experience

8c. Proposed Recommendation: A Proposed Recommendation is a mature report that, after wide review for soundness and implementability, is sent to relevant Governance organizations for endorsement

8d. Standard: A Standard is a specification or set of guidelines that, after extensive consensus-building, has received the endorsement of senior management and relevant Governance organizations

9. Documents are accessible through an annotation / editing mechanism through which working group members can annotate and edit the document

10. Documents are associated with a discussion mechanism through which the public can discuss the topics of the document

11. Documents are associated with a notification mechanism which the public can subscribe to in order to track developments around the document's topic

Metrics and Reports

12. Metrics and reports are published (by their authors, or by automated report generators) to the public

13. Metric and reports are associated with a discussion mechanism through which the public can discuss the topics of the metrics and reports

14. Metrics and reports are associated with a notification mechanism which the public can subscribe to in order to track the release of updated metrics and reports

Individuals

15. Each individual publishes (on a personal site) to the public a daily log representative of his or her activities and interests, including links to meetings attended and documents created

16. Each individual's personal site is associated with a discussion / feedback mechanism through which the public can offer feedback or enter dialog about the individual's activities and interests

17. Each individual's personal site is associated with a notification mechanism which the public can subscribe to in order to track developments with this individual

Groups (board, group, team, department, and division)

18. Each board, group, team, department, and division publishes to the public a daily log representative of their collective activities and interests, including links to meetings attended and documents created

19. Each board, group, team, department, and division site is associated with a discussion / feedback mechanism through which the public can offer feedback or enter dialog about the group's activities and interests

20. Each board, group, team, department, and division publishes site is associated with a notification mechanism which the public can subscribe to in order to track developments with this group