Knowledge Management

From crowdresearch
Revision as of 19:57, 6 August 2015 by Jamesgdamon2 (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

The goal of our Knowledge Management group is to maintain a cohesive and intuitive information resource that spans the wiki, Meteor, Trello, Slack, and GitHub. New members of the research group should be able to easily navigate the wiki to find their bearings and then go through old Meteor milestones and Slack conversations to get context when necessary. A well organized information system facilitates action by reducing friction associated with misunderstandings and redundant work.

The Knowledge Model

A pyramid showing the hierarchical structure of the Knowledge Model

Data -> Information -> Knowledge

The smallest bit of information is a datum. Numbers, objects, and individual items in a list are all examples of data. Data has minimal or no context.

When data is processed and combined with other data, it becomes information. Example: Liquid water can turn into ice.

Information is then contextualized and becomes knowledge. Knowledge informs action and decision making. Example: If I put ice in my drink it will stay cold.

More background on the knowledge model

How do we encourage this process in our own project?

Building the Wiki

A well managed wiki is a powerful research tool that provides access to processed information as well as raw sources. It is intuitive for new users and easily updated to share new information. Articles should be long enough to be worth reading but not so long that it becomes difficult to keep track of the content.


Articles that are too long to grasp should be shortened. They can be turned into lists with brief description of each item and links to each item's full article. They may also be split into two or more interlinked articles. If a subsection of an article grows continuously, at a certain point it might be best for it to become its own article.


We are constantly learning and adding our thoughts to the wiki. In addition to sharing the articles we read, it is essential for us to help others digest them without committing to reading the full article as well. The first step of this process can be seen in the work done by the reputation system group for their week 10 milestone. The next step would be to identify common themes like reputation inflation and split them off into their own articles with support from the relevant resources.


An article with no links in or out might as well exist in a vacuum. It is important to add links because they make the wiki as a whole more cohesive. Not all links have to be within the crowd research wiki either. To learn about linking etiquette followed on Wikipedia see here.

Page Content

Since some pages on the wiki are used as milestone submissions and others are for reference, it is important to be aware of the pages you are editing. Milestone submissions should all be appropriately titled and edited only by those who are submitting them.

While Meteor is the current venue for decision making, it might be beneficial to use wiki pages to emulate the process outlined in the deliberatorium

Finally, project subgroups (open-governance, reputation-systems, leadership-board) should have their own pages with descriptions and other useful information.