<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.2" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Putting Wikis to Work for Your PR Program</title>
	<link>http://www.globalprblogweek.com/2005/09/20/manuel-wikis-for-pr/</link>
	<description>September 19-23, 2005 :: Public Relations and Business Communications in the Age of Blogs</description>
	<pubDate>Mon, 01 Dec 2008 22:43:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.2</generator>
		<item>
		<title>By: Mike Manuel</title>
		<link>http://www.globalprblogweek.com/2005/09/20/manuel-wikis-for-pr/#comment-185</link>
		<dc:creator>Mike Manuel</dc:creator>
		<pubDate>Fri, 23 Sep 2005 18:26:27 +0000</pubDate>
		<guid>http://www.globalprblogweek.com/2005/09/20/manuel-wikis-for-pr/#comment-185</guid>
		<description>Wikipedia clearly takes the cake, but yeah, there are other projects worth noting -- mostly books it seems.  Larry Lessig's book rev for "Code" is being done via wiki (&lt;a href="http://codebook.jot.com/WikiHome" rel="nofollow"&gt;here&lt;/a&gt;).  Likewise, &lt;a href="http://wethemedia.oreilly.com/" rel="nofollow"&gt;Dan Gillmor&lt;/a&gt; and &lt;a href="http://www.darknet.com/" rel="nofollow"&gt;JD Lasica&lt;/a&gt; also relied on wikis (in some capacitiy) for thier book projects.  There's a longer list of wiki projects &lt;a href="http://en.wikipedia.org/wiki/List_of_wikis" rel="nofollow"&gt;here&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Wikipedia clearly takes the cake, but yeah, there are other projects worth noting &#8212; mostly books it seems.  Larry Lessig&#8217;s book rev for &#8220;Code&#8221; is being done via wiki (<a href="http://codebook.jot.com/WikiHome" rel="nofollow">here</a>).  Likewise, <a href="http://wethemedia.oreilly.com/" rel="nofollow">Dan Gillmor</a> and <a href="http://www.darknet.com/" rel="nofollow">JD Lasica</a> also relied on wikis (in some capacitiy) for thier book projects.  There&#8217;s a longer list of wiki projects <a href="http://en.wikipedia.org/wiki/List_of_wikis" rel="nofollow">here</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Forbush</title>
		<link>http://www.globalprblogweek.com/2005/09/20/manuel-wikis-for-pr/#comment-184</link>
		<dc:creator>Dan Forbush</dc:creator>
		<pubDate>Fri, 23 Sep 2005 18:11:21 +0000</pubDate>
		<guid>http://www.globalprblogweek.com/2005/09/20/manuel-wikis-for-pr/#comment-184</guid>
		<description>Mike -- 

Nicely said about "pain points." Other than Wikipedia, have you seen ANY outstanding example of a public wiki that's supporting true, self-generative collaboration? Just curious ... 

Dan</description>
		<content:encoded><![CDATA[<p>Mike &#8212; </p>
<p>Nicely said about &#8220;pain points.&#8221; Other than Wikipedia, have you seen ANY outstanding example of a public wiki that&#8217;s supporting true, self-generative collaboration? Just curious &#8230; </p>
<p>Dan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Schwartzman</title>
		<link>http://www.globalprblogweek.com/2005/09/20/manuel-wikis-for-pr/#comment-181</link>
		<dc:creator>Eric Schwartzman</dc:creator>
		<pubDate>Fri, 23 Sep 2005 17:15:35 +0000</pubDate>
		<guid>http://www.globalprblogweek.com/2005/09/20/manuel-wikis-for-pr/#comment-181</guid>
		<description>Versionitis.  I know it all too well.  Excellent job articulating to benefits of Wikis.</description>
		<content:encoded><![CDATA[<p>Versionitis.  I know it all too well.  Excellent job articulating to benefits of Wikis.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Phillips</title>
		<link>http://www.globalprblogweek.com/2005/09/20/manuel-wikis-for-pr/#comment-135</link>
		<dc:creator>David Phillips</dc:creator>
		<pubDate>Thu, 22 Sep 2005 11:06:42 +0000</pubDate>
		<guid>http://www.globalprblogweek.com/2005/09/20/manuel-wikis-for-pr/#comment-135</guid>
		<description>Hmmm.. I agree about document sharing having some value but the joy of a Wiki is that it can be widely shared. An amendment by a CEO may give a product manager the shivers and, in a networked organisation the CEO is not the only boss. Of course educating some CEO's may take a while but those who dont understand the Internet paradigm will be doing a lot of gardening soon anyway.

Its a culture thing as well.</description>
		<content:encoded><![CDATA[<p>Hmmm.. I agree about document sharing having some value but the joy of a Wiki is that it can be widely shared. An amendment by a CEO may give a product manager the shivers and, in a networked organisation the CEO is not the only boss. Of course educating some CEO&#8217;s may take a while but those who dont understand the Internet paradigm will be doing a lot of gardening soon anyway.</p>
<p>Its a culture thing as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Manuel</title>
		<link>http://www.globalprblogweek.com/2005/09/20/manuel-wikis-for-pr/#comment-94</link>
		<dc:creator>Mike Manuel</dc:creator>
		<pubDate>Wed, 21 Sep 2005 17:41:10 +0000</pubDate>
		<guid>http://www.globalprblogweek.com/2005/09/20/manuel-wikis-for-pr/#comment-94</guid>
		<description>Agreed, although in the case of approvals, it'll be interesting to see what shakes out as the best solution. For some, wikis will do the trick.  For others, new services like &lt;a href="http://www.writely.com/" rel="nofollow"&gt;Writely &lt;/a&gt;could be the ticket.  And I wouldn't rule MSFT out from baking better lightweight collaboration (ugh, I said it) features into Office and other applications either.</description>
		<content:encoded><![CDATA[<p>Agreed, although in the case of approvals, it&#8217;ll be interesting to see what shakes out as the best solution. For some, wikis will do the trick.  For others, new services like <a href="http://www.writely.com/" rel="nofollow">Writely </a>could be the ticket.  And I wouldn&#8217;t rule MSFT out from baking better lightweight collaboration (ugh, I said it) features into Office and other applications either.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Phillips</title>
		<link>http://www.globalprblogweek.com/2005/09/20/manuel-wikis-for-pr/#comment-87</link>
		<dc:creator>David Phillips</dc:creator>
		<pubDate>Wed, 21 Sep 2005 16:35:39 +0000</pubDate>
		<guid>http://www.globalprblogweek.com/2005/09/20/manuel-wikis-for-pr/#comment-87</guid>
		<description>One wonderful application is the ankle-bitter-like problem of approvals. First there is the brief. Everyone wants a say, then there is the first draft and first approval hurdle, then the next, then the lawyers and then the Deputy CEO and then – the deadline left the station without you. Enter Wiki.

As a productivity enhancer, this has to be the toy.

And, what happens to all that background briefing stuff. Great for journalists but also for sales staff, product designers, brand managers – the list goes on. Wiki's have a big future in PR.</description>
		<content:encoded><![CDATA[<p>One wonderful application is the ankle-bitter-like problem of approvals. First there is the brief. Everyone wants a say, then there is the first draft and first approval hurdle, then the next, then the lawyers and then the Deputy CEO and then – the deadline left the station without you. Enter Wiki.</p>
<p>As a productivity enhancer, this has to be the toy.</p>
<p>And, what happens to all that background briefing stuff. Great for journalists but also for sales staff, product designers, brand managers – the list goes on. Wiki&#8217;s have a big future in PR.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Manuel</title>
		<link>http://www.globalprblogweek.com/2005/09/20/manuel-wikis-for-pr/#comment-66</link>
		<dc:creator>Mike Manuel</dc:creator>
		<pubDate>Wed, 21 Sep 2005 04:13:31 +0000</pubDate>
		<guid>http://www.globalprblogweek.com/2005/09/20/manuel-wikis-for-pr/#comment-66</guid>
		<description>You probably don't want to hear this, but I think the answer to your question is "it depends...." 

Again, I default to the belief that you need to really understand what the pain points are in your existing work process before you can throw new technology at the problem.  And let the problems you identify dictate which technology you ultimately turn to.

I think wikis and blogs each lends themselves nicely to certain common problems, especially in PR.  Not knowing your's, its hard to say, but generally speaking, your program will likely benefit from the application of either technology.</description>
		<content:encoded><![CDATA[<p>You probably don&#8217;t want to hear this, but I think the answer to your question is &#8220;it depends&#8230;.&#8221; </p>
<p>Again, I default to the belief that you need to really understand what the pain points are in your existing work process before you can throw new technology at the problem.  And let the problems you identify dictate which technology you ultimately turn to.</p>
<p>I think wikis and blogs each lends themselves nicely to certain common problems, especially in PR.  Not knowing your&#8217;s, its hard to say, but generally speaking, your program will likely benefit from the application of either technology.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Pipper</title>
		<link>http://www.globalprblogweek.com/2005/09/20/manuel-wikis-for-pr/#comment-60</link>
		<dc:creator>David Pipper</dc:creator>
		<pubDate>Wed, 21 Sep 2005 00:28:50 +0000</pubDate>
		<guid>http://www.globalprblogweek.com/2005/09/20/manuel-wikis-for-pr/#comment-60</guid>
		<description>Mike, any advice on whether or not a small group that's just now experimenting with new technology (particularly blogs and wikis) should take one platform over the other?  Is a blog better than a wiki?</description>
		<content:encoded><![CDATA[<p>Mike, any advice on whether or not a small group that&#8217;s just now experimenting with new technology (particularly blogs and wikis) should take one platform over the other?  Is a blog better than a wiki?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
