Editor’s note: this is the third post in a multi-part series from Stewart Mader, author of Wikipatterns. You can check out some of his other work at Grow Your WIki, and the first two parts of the series can be found here and here.
When an organization has a wiki at the center of its operations, people can gather and share the kind of information that others need - including everything from projects, products, initiatives, strategies, and other pieces of the big picture, to the everyday: how to process an expense report, access an office’s network, get business cards printed, or reserve a meeting room. On a wiki, this information can be gathered by the small efforts of many.
Let’s look at an example - the expense report. It’s a standard process, with a common form that people need to access, complete, include receipts, and submit for approval.
If the organization’s accounting office uses a wiki, a staff member can add a page, explain the process for filling out an expense report, attach the blank report template, and make sure the page can be viewed by employees logged into the wiki. That staff member might also decide to make the page editable, so that others can refine the instructions based on their experience. Another option is to restrict direct editing of the page, but enable comments so that people can leave feedback and notes in addition to the instructions. The accounting staff can then update the instructions and procedure based on comments, and leave reply comments to let people know that their feedback has been incorporated.
Either option is more participatory than a static page, and more efficient because people throughout the organization can add useful knowledge where it makes the most sense - on the wiki page, in context, instead of cluttering email inboxes with messages that will be mostly ignored.
But what’s really important about the wiki is not just that one example of the expense report, or even that the report itself is available on the wiki. It’s the idea that employees are working together to put the information they’re carrying around in their heads on the wiki, where others can more easily access it, use it, edit it, and improve it. That builds a culture where all employees can become contributors - both to the goals of the organization, and the evolving knowledge about how to reach those goals.
Comments RSS
| TrackBack URI
[...] where a wiki can help, and it’s the subject of the latest article in my series on the Wikinomics Blog: A wiki is more participatory than a static site, and more [...]
Pingback by Wiki ROI #2: Tacit Knowledge is Key to Improving Efficiency - July 11, 2008 5:55 pm
[...] לפוסט הקודם, סטיוארט מיידר שוב מתייחס ל-ROI בוויקי במאמר וסף ומדבר על מיצוי הידע הסמוי של [...]
Pingback by ROI לוויקי, חלק 2: ידע סמוי הוא המפתח לשיפור האפקטיביות - TheMarker Cafe - July 13, 2008 3:25 pm
[...] On July 11, 2008… Stewart Mader talked about the benefits of the Wiki: Guest blogger Stewart Mader on Wiki ROI #2: Collect and Refine Tacit Knowledge to Improve Efficiency [...]
Pingback by Wikinomics » Blog Archive » The Wikinomics Roundup: Week in Review - July 14, 2008 12:33 am
[...] Mader from Grow Your Wiki is guest posting on Wikinomics and his lastest post is on the effectiveness of wikis enabling tacit [...]
Pingback by Library clips :: The tacitness of wikis :: July :: 2008 - July 16, 2008 2:13 am
[...] Oscar Berg over at the Content Economy blog, shares a few of his readings from across the blogosphere. Included is Stewart Mader’s Wikinomics guest post on Wikis. [...]
Pingback by Wikinomics » Blog Archive » Wikinomics in the Blogosphere - August 1, 2008 10:24 am
[...] Z0rk The tacitness of wikis: [Via Library clips] Stewart Mader from Grow Your Wiki is guest posting on Wikinomics and his lastest post is on the effectiveness of wikis enabling tacit [...]
Pingback by Wikis - Tacit becomes explicit - August 18, 2008 12:42 pm