<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Ideas for greater wiki participation</title>
	<atom:link href="http://www.providentpartners.net/blog/index.php/2008/03/19/ideas-for-greater-wiki-participation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.providentpartners.net/blog/index.php/2008/03/19/ideas-for-greater-wiki-participation/</link>
	<description>The Marketing Edge, one of the longest running marketing and public relations podcasts.</description>
	<lastBuildDate>Tue, 27 Jul 2010 21:00:43 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Albert Maruggi</title>
		<link>http://www.providentpartners.net/blog/index.php/2008/03/19/ideas-for-greater-wiki-participation/comment-page-1/#comment-60720</link>
		<dc:creator>Albert Maruggi</dc:creator>
		<pubDate>Thu, 20 Mar 2008 10:20:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.providentpartners.net/blog/index.php/2008/03/19/ideas-for-greater-wiki-participation/#comment-60720</guid>
		<description>Miles, this is great and I trust helps others considering a similar project.  The one item I particularly liked is this

&quot;Spend another month just adding content from emails (now that you are familiar with the wiki it will be much easier) and when you get an email asking a question, make a wiki page, and reply back with a link to the wiki page that answers their question. Next email you get with the same question, give them the same link.&quot;

That is just so efficient.  Nice work and remember your comment on this blog will result in Provident Partners donating a food item to a St. Paul food shelter.  

All the best,</description>
		<content:encoded><![CDATA[<p>Miles, this is great and I trust helps others considering a similar project.  The one item I particularly liked is this</p>
<p>&#8220;Spend another month just adding content from emails (now that you are familiar with the wiki it will be much easier) and when you get an email asking a question, make a wiki page, and reply back with a link to the wiki page that answers their question. Next email you get with the same question, give them the same link.&#8221;</p>
<p>That is just so efficient.  Nice work and remember your comment on this blog will result in Provident Partners donating a food item to a St. Paul food shelter.  </p>
<p>All the best,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tankilo</title>
		<link>http://www.providentpartners.net/blog/index.php/2008/03/19/ideas-for-greater-wiki-participation/comment-page-1/#comment-60698</link>
		<dc:creator>tankilo</dc:creator>
		<pubDate>Thu, 20 Mar 2008 06:15:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.providentpartners.net/blog/index.php/2008/03/19/ideas-for-greater-wiki-participation/#comment-60698</guid>
		<description>When faced with a wiki without content relative to you or your department (be sure to search first, no need to duplicate work). Here was the &quot;nuts and bolts&quot; of what I have been doing so far.

Go to the wiki, and make one page, announcing it is for your department, with child pages to appear beneath. Then make a second page describing how to edit the wiki.
If you are like me, you already have a stack of notes, bookmarks of websites, a collection of text files, word documents, excel spread sheets, address books, and saved emails you go to every day to reference things like &quot;What is the code for stores in the West?&quot; &quot;Who is the contact in sales that knows about blackberries?&quot; &quot;What is the phone number of the fax machine for the biggest store?&quot; &quot;What is the team that handles issues with email?&quot; and even the simple &quot;What is the website where we time punch?&quot;

You might be thinking &quot;I should just convert all of this&quot;. But you are looking at a monumental task if you were to try and do it all at once.  Instead, keep the wiki webpage open. And when you have to reach into your notes to check something (and someone isn&#039;t tapping their foot needing it yesterday), add a child page to the wiki and put in nothing more than the info.

Anytime you receive an email and think &quot;Oh I should bookmark the site they link to&quot; or &quot;I should add this to my notes&quot;, add it to the wiki instead. If you archive all your old email anyway, you can still search it in case the wiki ever goes down.

Keep this up for about a month, adding a page with about a paragraph of text every day or every other day, and within a month, you&#039;ll have 15+ pages of relevant information on things you have been concerned with in the past 30 days. Go ahead and take an afternoon to observe what&#039;s there, do a little editing, link some things, consolidate some pages, realize that some new pages should really be added, and add them.

Spend another month just adding content from emails (now that you are familiar with the wiki it will be much easier) and when you get an email asking a question, make a wiki page, and reply back with a link to the wiki page that answers their question. Next email you get with the same question, give them the same link.
Finally your next project that requires collaboration with another employee, make a new page, and keep track of notes with the wiki, and at the bottom of the page, put in a link to the &quot;How to edit the wiki&quot; page, send the link to the new page you made to your coworkers.

And when they ask, try not to evangelize to much. Focus on how easy it is to add new content and how nothing gets deleted. And how anyone in the company is able to access the information, and how if all departments had a presence, we could share information so much easier.</description>
		<content:encoded><![CDATA[<p>When faced with a wiki without content relative to you or your department (be sure to search first, no need to duplicate work). Here was the &#8220;nuts and bolts&#8221; of what I have been doing so far.</p>
<p>Go to the wiki, and make one page, announcing it is for your department, with child pages to appear beneath. Then make a second page describing how to edit the wiki.<br />
If you are like me, you already have a stack of notes, bookmarks of websites, a collection of text files, word documents, excel spread sheets, address books, and saved emails you go to every day to reference things like &#8220;What is the code for stores in the West?&#8221; &#8220;Who is the contact in sales that knows about blackberries?&#8221; &#8220;What is the phone number of the fax machine for the biggest store?&#8221; &#8220;What is the team that handles issues with email?&#8221; and even the simple &#8220;What is the website where we time punch?&#8221;</p>
<p>You might be thinking &#8220;I should just convert all of this&#8221;. But you are looking at a monumental task if you were to try and do it all at once.  Instead, keep the wiki webpage open. And when you have to reach into your notes to check something (and someone isn&#8217;t tapping their foot needing it yesterday), add a child page to the wiki and put in nothing more than the info.</p>
<p>Anytime you receive an email and think &#8220;Oh I should bookmark the site they link to&#8221; or &#8220;I should add this to my notes&#8221;, add it to the wiki instead. If you archive all your old email anyway, you can still search it in case the wiki ever goes down.</p>
<p>Keep this up for about a month, adding a page with about a paragraph of text every day or every other day, and within a month, you&#8217;ll have 15+ pages of relevant information on things you have been concerned with in the past 30 days. Go ahead and take an afternoon to observe what&#8217;s there, do a little editing, link some things, consolidate some pages, realize that some new pages should really be added, and add them.</p>
<p>Spend another month just adding content from emails (now that you are familiar with the wiki it will be much easier) and when you get an email asking a question, make a wiki page, and reply back with a link to the wiki page that answers their question. Next email you get with the same question, give them the same link.<br />
Finally your next project that requires collaboration with another employee, make a new page, and keep track of notes with the wiki, and at the bottom of the page, put in a link to the &#8220;How to edit the wiki&#8221; page, send the link to the new page you made to your coworkers.</p>
<p>And when they ask, try not to evangelize to much. Focus on how easy it is to add new content and how nothing gets deleted. And how anyone in the company is able to access the information, and how if all departments had a presence, we could share information so much easier.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
