<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:series="http://unfoldingneurons.com/"
	>

<channel>
	<title>I&#039;d Rather Be Writing &#187; forums</title>
	<atom:link href="http://idratherbewriting.com/tag/forums/feed/" rel="self" type="application/rss+xml" />
	<link>http://idratherbewriting.com</link>
	<description>The Latest Trends in Technical Communication</description>
	<lastBuildDate>Fri, 10 Feb 2012 23:59:59 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Forum → Wiki → Blog Workflow</title>
		<link>http://idratherbewriting.com/2010/11/24/forum-wiki-blog-workflow/</link>
		<comments>http://idratherbewriting.com/2010/11/24/forum-wiki-blog-workflow/#comments</comments>
		<pubDate>Wed, 24 Nov 2010 15:23:38 +0000</pubDate>
		<dc:creator>Tom Johnson</dc:creator>
				<category><![CDATA[blog]]></category>
		<category><![CDATA[blogs]]></category>
		<category><![CDATA[forums]]></category>
		<category><![CDATA[participation]]></category>
		<category><![CDATA[Wikis]]></category>
		<category><![CDATA[workflows]]></category>

		<guid isPermaLink="false">http://idratherbewriting.com/?p=8089</guid>
		<description><![CDATA[One of the sites I&#8217;m working with lately at my job combines a forum (vBulletin), blog (Joomla), and wiki (Mediawiki) into one experience. Each of these tools does a great job at what it was designed to do. They&#8217;re three separate platforms skinned and linked together. I used to think the site was a hodgepodge of software platforms, but now I see that these three resources ... <a href="http://idratherbewriting.com/2010/11/24/forum-wiki-blog-workflow/">more &#187;</a>]]></description>
			<content:encoded><![CDATA[<p>One of the sites I&#8217;m working with lately at my job combines a forum (vBulletin), blog (Joomla), and wiki (Mediawiki) into one experience. Each of these tools does a great job at what it was designed to do. They&#8217;re three separate platforms skinned and linked together.</p>
<p>I used to think the site was a hodgepodge of software platforms, but now I see that these three resources can harmonize together in an amazing way.</p>
<div id="attachment_8197" class="wp-caption alignnone" style="width: 610px"><a href="http://idratherbewriting.com/wp-content/uploads/2010/11/blog-forum-wiki.jpg"><img class="size-full wp-image-8197" title="A possible workflow from forum to wiki to blog" src="http://idratherbewriting.com/wp-content/uploads/2010/11/blog-forum-wiki.jpg" alt="A possible workflow from forum to wiki to blog" width="600" height="362" /></a><p class="wp-caption-text">A possible workflow of information from forum to wiki to blog.</p></div>
<p>Here&#8217;s the interaction in a little more detail:</p>
<ul>
<li><strong>Forum:</strong> Users contribute openly and regularly to the forum, creating at least several new threads and probably 15 new responses a day. Users feel comfortable posting and responding to forum questions, because they aren&#8217;t making official remarks about any topic. They&#8217;re offering their thoughts, or asking questions. It&#8217;s an informal medium that is inviting and comfortable.</li>
<li><strong>Wiki:</strong> The conversations on the forum drive needs in the wiki. Answers and resolutions from the most popular forum threads should be transferred to the wiki as official articles.  Transferring this content requires you to organize and articulate the information, which isn&#8217;t always easy. So admittedly this transfer isn&#8217;t often done with the site I mentioned, but if someone were designated into this role, it could be powerful.</li>
<li><strong>Blog:</strong> The blog showcases the information recently added to the wiki. The blog can also serve as a voice to energize a community, to call attention to needs on the wiki, or to bring other news to users.</li>
</ul>
<p>I never considered how well these tools work together, but they do. The different mediums allow users to interact in ways that suit them. Of course it would be nice to have one tool that has an incredibly powerful blog, wiki, and forum wrapped up into one package. Some wiki platforms provide all three, such as Tiki Wiki. But swiss-army knife tools almost invariably perform much like an on/off road motorcycle.</p>
<p>The drawback of having three sources for content, however, is that content published on one source may never make it to the other sources. For example, if I write a blog article about a new application, shouldn&#8217;t that content also appear as an article on the wiki? If a forum thread clarifies a topic, shouldn&#8217;t that clarification be added to a wiki article? If I add a new wiki section, shouldn&#8217;t that section be announced and summarized, as well as explained, on the blog? Content overlap becomes a problem. So does search.</p>
<p>Regardless of the overlap problem, combining a forum with a wiki and blog has tangible benefits. It helps solve the participation problem with wikis. Users are more comfortable asking a question in a forum rather than changing the original content of an article. Wiki admins can harvest information from these forum threads to strengthen the information of the wiki. Significant new wiki information should be announced to users on the blog.<br />
<h2>Blog Sponsors</h2>
<ul>
<li><a href="http://webworks.com">Webworks ePublisher</a></li>
<li><a href="http://scriptorium.com">Scriptorium</a></li>
<li><a href="http://www.helpgenerator.com">Help Generator help authoring software</a></li>
<li><a href="http://idc.spsu.edu">Southern Polytechnic: Information Design and Communication</a></li>
<li><a href="http://simplifiedenglish.net">Simplified English</a></li>
<li><a href="http://info.mindtouch.com/irbw/tcs-custom-tour?persona=content">MindTouch</a></li>
<li><a href="http://www.madcapsoftware.com/products/madpak/overview.aspx?utm_source=IdRatherBeWriting&#038;utm_medium=Banner&#038;utm_campaign=MadPak"</a>Madcap Software</a></li>
<li><a href="http://www.drexplain.com/">Dr.Explain</a> </li>
<li><a href="http://www.adobe.com/products/technicalcommunicationsuite/try.html?sdid=ITRSO">Adobe Technical Communication Suite</a></li>
<li><a href="http://www.congree.com/en/download-congree-personal-edition.aspx">Congree</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://idratherbewriting.com/2010/11/24/forum-wiki-blog-workflow/feed/</wfw:commentRss>
		<slash:comments>18</slash:comments>
		</item>
		<item>
		<title>Is This Meeting Really Necessary?</title>
		<link>http://idratherbewriting.com/2009/07/15/is-this-meeting-really-necessary/</link>
		<comments>http://idratherbewriting.com/2009/07/15/is-this-meeting-really-necessary/#comments</comments>
		<pubDate>Thu, 16 Jul 2009 00:48:56 +0000</pubDate>
		<dc:creator>Tom Johnson</dc:creator>
				<category><![CDATA[chats]]></category>
		<category><![CDATA[forums]]></category>
		<category><![CDATA[meetings]]></category>
		<category><![CDATA[Notes]]></category>
		<category><![CDATA[STC]]></category>
		<category><![CDATA[time]]></category>
		<category><![CDATA[Wikis]]></category>

		<guid isPermaLink="false">http://www.idratherbewriting.com/?p=4046</guid>
		<description><![CDATA[After a recent conference call I had for an STC chapter meeting, we needed an online mechanism to keep the discussion going. Doc Guy set up a Google Groups discussion site (which includes a threaded forum and wiki) to facilitate the online discussion, and we started a few threads, but soon the discussion focused , unfortunately, only on scheduling dates for in-person meetings. In a ... <a href="http://idratherbewriting.com/2009/07/15/is-this-meeting-really-necessary/">more &#187;</a>]]></description>
			<content:encoded><![CDATA[<p>After a recent conference call I had for an STC chapter meeting, we needed an online mechanism to keep the discussion going. <a href="http://twitter.com/docguy" target="_blank">Doc Guy</a> set up a <a href="http://google.com/groups" target="_blank">Google Groups</a> discussion site (which includes a threaded forum and wiki) to facilitate the online discussion, and we started a few threads, but soon the discussion focused , unfortunately, only on scheduling dates for <em>in-person</em> meetings.</p>
<p>In a world of virtual tools—blogs, wikis, feeds, forums, listservs, e-mail, IM, chat, Twitter, social networks—one would think that the traditional sit-down, face-to-face meetings had been relegated to a place in a historical museum among other old, discarded traditions (like wearing cravats). But even in the 21<sup>st</sup> century, many people still believe that if you want to accomplish serious planning and discussion, you need an in-person meeting.</p>
<h3>Benefits of In-Person Meetings</h3>
<p>One argument for in-person meetings is the benefit of idea building that sometimes takes place. When you get multiple people talking together, one person begins an idea, another adds to it, and another sees another dimension to it, which triggers an unexpected thought from another, and soon a handful of people create a collective intelligence that yields more than the sum of what each individuals could come up with alone. Many feel that this dynamic idea building, which takes on a life of its own in a lively meeting, is rarely matched in the isolated, typed out threads online. <span id="more-4046"></span></p>
<p>In reality, part of the reason people feel in-person meetings are productive in generating ideas is that meetings are the <em>only</em> time people set aside to brainstorm a topic. Most participants don&#8217;t do anything before a meeting. The meeting is the time blocked out for them to actually think and discuss a topic. Until the meeting happens, they fill their time with other tasks and obligations. The meeting is nothing more than a deadline, a period set aside for exploring a topic.</p>
<p>Because meetings are the dedicated time for thinking, it&#8217;s no wonder so many people should conclude that meetings are the only way to do any real planning. Instead of going this route, however, try merely setting aside time in your own schedule to sit down and think out problems, brainstorm, and explore ideas for a prolonged period of time. Then share those ideas with others online. You&#8217;ll find the same dynamic idea building can take place in virtual environments.</p>
<h3>Double-edges of Time Independence</h3>
<p>The reason people often neglect individual preparation and contribution in virtual environments is because online discussions are not time dependent, so they never get done. Being outside time and location is of course the advantage of online discussions, but it&#8217;s also the downfall.</p>
<p>Without a hard and fast deadline for contributions, the online discussion is often put aside, procrastinated, and ignored until the threads are so anemic they famish. One person responds one day, another responds the day after next, and little by little, contributions sort of trickle in, but you never see the rushing river of thought that happens when a group exchanges in real-time.</p>
<p>This trend of increasing attrition is unfortunate, because online discussions don&#8217;t have to be divorced from timelines and boundaries. You can set deadlines for discussions and schedule blocks for virtual chats. If you let people know expectations of participation by specific times, the procrastination minimizes. As more people contribute, the interactions increase, and you soon approach the dynamic idea building of face-to-face meetings. But this activity requires a meeting organizer and champion, someone to stoke the discussion, set expectations, prod the silent participants, and keep it all going.</p>
<h3>Dealing with Silence</h3>
<p>With online discussions, lack of contributions is often interpreted as non-participation. Because Sally, Jim, and Karl aren&#8217;t chiming in to the discussion, the assumption is that they&#8217;re busy, offline, or not engaged by the ideas on the table. Seeing the lack of participation, leaders often conclude that the online format isn&#8217;t working and so they need to &#8220;get everybody together&#8221; for an in-person meeting. (The phrase &#8220;get everybody together,&#8221; by the way, always makes me cringe.)</p>
<p>However, what happens at these in-person meetings is a similar to what happens online: several people dominate the discussion, and a handful of people quietly observe. Sally, Jim, and Karl can be just as non-participatory in the face-to-face meetings as they are online. And when you confront them for their opinion, it usually turns out that they&#8217;re apathetic or in agreement with what&#8217;s already being said.</p>
<h3>Advantages in Online Environments</h3>
<p>Although some people in meetings are quiet because they agree or have little to add, another category of people are quiet for another reason: they&#8217;re shy. Here virtual environments have the upper hand, because virtual environments can give shy participants a new voice. The shy meeting participants no longer have to fight to get a word in, or stand up against a meeting tyrant to reject a prevailing idea, or bumble their ideas with an inarticulate tongue. Expression comes easier with your hands on a keyboard in a comfortable chair. Quiet mice are suddenly roaring lions.</p>
<h3>Summary</h3>
<p>With all the virtual tools are our disposal, we shouldn&#8217;t be hampered with long, burdensome meetings in distant locations that drag out over an entire afternoon, which people arrive at without having done any preparation or individual brainstorming, and which are assumed to be the only vehicle for thought and discussion among groups. The same productive output is possible through the myriad of online tools available, but it requires participants to take responsibility for engaging and exploring topics on their own.<br />
<h2>Blog Sponsors</h2>
<ul>
<li><a href="http://webworks.com">Webworks ePublisher</a></li>
<li><a href="http://scriptorium.com">Scriptorium</a></li>
<li><a href="http://www.helpgenerator.com">Help Generator help authoring software</a></li>
<li><a href="http://idc.spsu.edu">Southern Polytechnic: Information Design and Communication</a></li>
<li><a href="http://simplifiedenglish.net">Simplified English</a></li>
<li><a href="http://info.mindtouch.com/irbw/tcs-custom-tour?persona=content">MindTouch</a></li>
<li><a href="http://www.madcapsoftware.com/products/madpak/overview.aspx?utm_source=IdRatherBeWriting&#038;utm_medium=Banner&#038;utm_campaign=MadPak"</a>Madcap Software</a></li>
<li><a href="http://www.drexplain.com/">Dr.Explain</a> </li>
<li><a href="http://www.adobe.com/products/technicalcommunicationsuite/try.html?sdid=ITRSO">Adobe Technical Communication Suite</a></li>
<li><a href="http://www.congree.com/en/download-congree-personal-edition.aspx">Congree</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://idratherbewriting.com/2009/07/15/is-this-meeting-really-necessary/feed/</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
		<item>
		<title>STC’s wiki is also scheduled for demolition :: TechCommDood</title>
		<link>http://idratherbewriting.com/2009/07/12/stc%e2%80%99s-wiki-is-also-scheduled-for-demolition-techcommdood/</link>
		<comments>http://idratherbewriting.com/2009/07/12/stc%e2%80%99s-wiki-is-also-scheduled-for-demolition-techcommdood/#comments</comments>
		<pubDate>Mon, 13 Jul 2009 03:01:17 +0000</pubDate>
		<dc:creator>Tom Johnson</dc:creator>
				<category><![CDATA[forums]]></category>
		<category><![CDATA[Notes]]></category>
		<category><![CDATA[STC]]></category>

		<guid isPermaLink="false">http://writerriver.com/?p=1347</guid>
		<description><![CDATA[STC’s wiki is also scheduled for demolition :: TechCommDood. I admit that while I haven&#8217;t visited the STC Forums in at least a year, I am surprised to see them being taken down. I didn&#8217;t realize the hosting costs were so prohibitive that it was an expense that needed to be cut. Then again, I&#8217;m not sure the STC is taking them down to cut ... <a href="http://idratherbewriting.com/2009/07/12/stc%e2%80%99s-wiki-is-also-scheduled-for-demolition-techcommdood/">more &#187;</a>]]></description>
			<content:encoded><![CDATA[<p><a href="http://techcommdood.com/?p=299">STC’s wiki is also scheduled for demolition :: TechCommDood</a>. I admit that while I haven&#8217;t visited the STC Forums in at least a year, I am surprised to see them being taken down. I didn&#8217;t realize the hosting costs were so prohibitive that it was an expense that needed to be cut. Then again, I&#8217;m not sure the STC is taking them down to cut expenses. In STC&#8217;s announcement, they don&#8217;t actually say why they&#8217;re taking the forums down. Instead, the <a href="http://www.stc.org/2009/07/stc-forum-being-retired-31-july.asp" target="_blank">STC announcement</a> reads like an obituary, lauding the valuable contributions of members on the forums on a wide range of issues. Must not have been that valuable if we&#8217;re deleting them. The hint of exploring a next-generation solution, without any clear indication of what or when that solution will be implemented, seems like a soft way of removing the forums without explaining why.<br />
<h2>Blog Sponsors</h2>
<ul>
<li><a href="http://webworks.com">Webworks ePublisher</a></li>
<li><a href="http://scriptorium.com">Scriptorium</a></li>
<li><a href="http://www.helpgenerator.com">Help Generator help authoring software</a></li>
<li><a href="http://idc.spsu.edu">Southern Polytechnic: Information Design and Communication</a></li>
<li><a href="http://simplifiedenglish.net">Simplified English</a></li>
<li><a href="http://info.mindtouch.com/irbw/tcs-custom-tour?persona=content">MindTouch</a></li>
<li><a href="http://www.madcapsoftware.com/products/madpak/overview.aspx?utm_source=IdRatherBeWriting&#038;utm_medium=Banner&#038;utm_campaign=MadPak"</a>Madcap Software</a></li>
<li><a href="http://www.drexplain.com/">Dr.Explain</a> </li>
<li><a href="http://www.adobe.com/products/technicalcommunicationsuite/try.html?sdid=ITRSO">Adobe Technical Communication Suite</a></li>
<li><a href="http://www.congree.com/en/download-congree-personal-edition.aspx">Congree</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://idratherbewriting.com/2009/07/12/stc%e2%80%99s-wiki-is-also-scheduled-for-demolition-techcommdood/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

