<?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/"
	>

<channel>
	<title>Redcatco &#187; knowledge management</title>
	<atom:link href="http://redcatco.com/blog/tag/knowledge-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://redcatco.com</link>
	<description>Connecting People With Technology</description>
	<lastBuildDate>Tue, 01 Nov 2011 15:11:02 +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>Speed Reading &#8211; An Essential Survival Skill for the Knowledge Worker</title>
		<link>http://redcatco.com/blog/communication/speed-reading-an-essential-survival-skill-for-the-knowledge-worker/</link>
		<comments>http://redcatco.com/blog/communication/speed-reading-an-essential-survival-skill-for-the-knowledge-worker/#comments</comments>
		<pubDate>Fri, 18 Apr 2008 02:38:09 +0000</pubDate>
		<dc:creator>Benjamin Ellis</dc:creator>
				<category><![CDATA[communication]]></category>
		<category><![CDATA[productivity]]></category>
		<category><![CDATA[knowledge management]]></category>
		<category><![CDATA[reading]]></category>

		<guid isPermaLink="false">http://redcatco.com/blog/?p=441</guid>
		<description><![CDATA[One of the key skills for knowledge workers is good, if not superb, reading speed. Even though print media is in decline, we  have more, rather than less to get through. E-mails, wiki pages, white papers and documents all scream &#8216;read me&#8217;. Yet there is a great deal of misinformation about speed reading around. Many [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://redcatco.com/blog/wp-content/uploads/2008/04/reading_the_week.jpg"><img class="alignright size-full wp-image-442" style="float: right; border: 2px solid black; margin: 2px;" title="reading_the_week" src="http://redcatco.com/blog/wp-content/uploads/2008/04/reading_the_week.jpg" alt="" /></a>One of the key skills for knowledge workers is good, if not superb, reading speed. Even though print media is in decline, we  have more, rather than less to get through. E-mails, wiki pages, white papers and documents all scream &#8216;read me&#8217;. Yet there is a great deal of misinformation about speed reading around. Many of the methods have little or no scientific research behind them and may even do more hard than good.</p>
<p>Evelyn Wood, usually cited as the originator and pioneer of &#8220;<a title="Speed reading" href="http://en.wikipedia.org/wiki/Speed_reading">Speed Reading</a>&#8220;, developed a system called <a title="Reading Dynamics" href="http://en.wikipedia.org/wiki/Reading_Dynamics">Reading Dynamics</a>. It certainly makes some tall claims.</p>
<p>However, just as studying people with exceptional memory gives insight into how memory might work, but does not endow us with those people&#8217;s powers, studying people with exceptional reading capability is only of indirect help.</p>
<p>There are many courses on the market today. <span class="pullquote">Some courses maintain that comprehension is not important, others that it is. Some focus on eye movement and some don&#8217;t.</span> Some warn against subvocalization (reading &#8216;out loud&#8217; inside your head), and some don&#8217;t. It is a confused and confusing world out there.</p>
<p>How do you build a tool kit to deal with the volume of material that hits your retina each day? Start with the end, not the means. When thinking about reading, the first question is this: What is the reading for? Is it to get loosely familiar with some materials prior to a meeting? Is it for pleasure? For study? Each of these purposes suggests a different strategy.</p>
<p>First, a little theory, via the BPS research digest: &#8220;<a href="http://bps-research-digest.blogspot.com/2007/08/reading-is-team-effort.html">Reading is a team effort</a>&#8220;, reporting research by <a href="http://www.plosone.org/article/info%3Adoi%2F10.1371%2Fjournal.pone.0000680">Pelli and Tillman (2007)</a>. Reading includes three major levels:</p>
<ul>
<li>Letter decoding &#8211; Identifying individual letters. This can be blocked by changing letters, but keeping word shape, e.g. “Reading” becomes “Pcedirg”. Squint and you&#8217;ll get it.</li>
<li>Whole world recognition &#8211; Seeing blocks of letters as a word. This can be blocked using alternating case, e.g. “ThIs tExT AlTeRnAtEs iN CaSe”.</li>
<li>Sentence context &#8211; Predicting words based on context. This can be blocked using jumbled words, e.g. “Contribute others. The of Reading measured”.</li>
</ul>
<p>We use all three techniques to read effectively. It appears that <span class="pullquote">faster readers make more use of sentence context</span>, but the research also implies that letter decoding contributes for the bulk of reading speed, and this is also supported by other research.</p>
<p>This contradicts many speed reading courses, which focus on reading larger and larger groups of words. There is no academic research I have found to show that this is effective. Because of the way that written English works, there is no way to know what a unit of sense is until after it has been read. <strong>Even super readers seem to only read in blocks of 2-3 words.</strong> Many of the techniques taught are actually equivalent to skimming, rather than reading. This might improve apparent speed, but it does so at the cost of comprehension.</p>
<p>This leads on to the issue of eye movement efficiency. This is another big focus of many techniques, but again, it is controversial. Lazy eye movement can slow down reading, so think about the following:</p>
<ul>
<li>Avoiding eye wandering &#8211; Don&#8217;t hop around the page, unless this is a deliberate intent.</li>
<li>Avoiding back-skipping &#8211; flicking back and rereading &#8211; although this can be beneficial for tricky passages.</li>
<li>Avoiding forward-skipping &#8211; flicking ahead, again unless this is a deliberate intent.</li>
<li>Keep a good distance from the page &#8211; not too close (only reading a bit at once), or too far away.</li>
</ul>
<p>Most of <span class="pullquote">the visual processing capability of the brain is concentrated on the very middle of our vision. The resolution and brain power available outside of this area falls off very dramatically.</span> Being too close to the text limits the amount of brain power we can apply to reading &#8211; so keep a good distance and you may well see your reading speed increase.</p>
<p>There is a risk of straining at gnats and swallowing camels here. Much of our reading takes place at a computer screen. This introduces additional factors that have a large impact on reading ability. Poor font use, especially websites where font spacing is overridden, slows reading.</p>
<p>We have the modern luxury of wonderfully large monitors, which is not always a good thing. Avoid excessive line lengths, sometimes is pays to narrow the window if you have to. This makes it easier for the eyes to accurately back-skip, to find the beginning of the next line. Various pieces research have also looked at the affect of colour combinations in reading from computer screens. The key take away is to go for something that is high contrast, for example black on white, not something like red on green.</p>
<p>Many speed reading courses also feature meta-guiding. That is a very swish way of saying use a finger or pointer to read, as you did when you started reading. This can be useful for training the eyes in skim reading, but doesn&#8217;t seem to help with reading at speed. It can be used for setting yourself a target reading speed, but again this sacrifices comprehension for speed. Apart from the street-cred/image issue, meta-guiding isn&#8217;t really practicable on a computer screen and is probably unwise with most refresh rates, because of flicker.</p>
<p>Subvocalization was mentioned earlier. Stilling that inner voice &#8211; not reading out loud, moving the lips or even vocalizing inside the head &#8211; is often taught. The evidence on this is again mixed, but it does seem to have some speed benefit, although it may impact comprehension. Try to still that inner voice, try blocking the chatter by humming &#8211; it sounds odd, but it does work.</p>
<p>Breaking the link between reading and speaking makes a difference to skimming text at speed. However, this is again relative to other effects, for example, minimising attention-distractors, such as background music.</p>
<p>Returning to purpose: If we are reading to learn, then many speed reading techniques are a false economy. If I can read 25% faster, but retain only 75% of the material and have to read it twice, I have lost out. Sometimes the short cut is the longest way around.</p>
<p>There is a movement towards <a href="http://johnmiedema.ca/2008/02/16/slow-reading-is-green-reading/" rel="nofollow">slow reading</a> in philosophy study. Anyone who has to read a modern philosophy text book will understand why. You can read those things ten times and still have no idea what the author was saying.</p>
<p>To put it another way, driving at 100 miles an hour on a narrow winding road is unlikely to be sensible. If the vocabulary is unfamiliar, there are no short cuts to speed reading, other than grabbing a dictionary. When you are stuck with a piece of text, it is worth rereading and reading aloud. Hearing words allows you to apply more of your brain. Try to visualise what is being said and actively engage your imagination as well. All of this will help with comprehension and retention.</p>
<p>Note that we read and retain first and last words best, for example the beginnings and ends of paragraphs. A useful writing tip &#8211; put important things there.</p>
<p>Hopefully a three stage model for reading is starting to emerge in your mind:</p>
<ol>
<li>Do I need to read this<strong> </strong>- <strong>skim for context</strong> and relevance.</li>
<li>I need to read this &#8211; <strong>read for understanding</strong> and retention.</li>
<li>Do I understand this &#8211; <strong>review for clarification</strong> and comprehension.</li>
</ol>
<p>In some ways this is not a new idea. <a href="http://www.ucc.vt.edu/lynch/TextbookReading.htm">SQ3R</a> (Survey, Question, Read, Recite/Recall, Review) has been around for a while. It is a five step system that contains these elements. It isn&#8217;t usually presented as a speed reading method, but it is the long way round that avoids costly short cuts. If the skimming step is used to fast-fail irrelevant documents &#8211; scan and discard or scan then read &#8211; it is a very productive work flow</p>
<p>A pre-scan/skim of a document helps understand the information structure. Making yourself concious of the meta-content, what it is about and what you expect to learn &#8211; primes the brain to absorb the information and makes it ready to comprehend and remember (see <a href="http://redcatco.com/blog/productivity/learning-your-way-to-a-better-memory/">Learning your way to a better memory</a>).</p>
<p>Questioning prepares the brain and focusses on the intent of the reading. Then read, reciting key passages and practising recall. finally, review the information that has been gleaned.</p>
<p>So, essential speed reading:</p>
<ul>
<li>Skim when you are skimming &#8211; let your eyes run purposefully and silently.</li>
<li>Read purposefully &#8211; be inquisitive and don&#8217;t be afraid to pause to understand.</li>
<li>Reflect on what you read &#8211; reading and forgetting is the most inefficient reading of all.</li>
</ul>
<p>Papers and posts:</p>
<p><a href="http://www.amazon.com/Psychology-Reading-Keith-Rayner/dp/0805818723/ref=pd_bbs_1?ie=UTF8&amp;s=books&amp;qid=1208420782&amp;sr=8-1">Rayner and Pollatsek, The Psychology of Reading</a>.</p>
<p>Allyn &amp; Bacon, (1987) <em>The Psychology of Reading and Language Comprehension</em>. Boston.</p>
<p><a class="new" title="Francis Pleasant Robinson (page does not exist)" href="http://en.wikipedia.org/w/index.php?title=Francis_Pleasant_Robinson&amp;action=edit&amp;redlink=1">Francis Pleasant Robinson</a> (1946), <em>Effective Study. </em>New York.</p>
<p><a href="http://www.plosone.org/article/info%3Adoi%2F10.1371%2Fjournal.pone.0000680">Pelli DG, Tillman KA (2007) Parts, Wholes, and Context in Reading: A Triple Dissociation</a>. PLoS ONE 2(8):       e680.       doi:10.1371/journal.pone.0000680</p>
<p><a href="http://www.blackwell-synergy.com/doi/abs/10.1046/j.1365-2532.1990.720060.x">RONALD STURT (1990)            The psychology of reading: an essay in honour of Mona Going</a>.  Health Libraries Review 7 (2)</p>
<p><a href="http://tapor.ualberta.ca/Resources/e-text%20reading/Mills%20-%20Reading%20text%20-%20ACM%2019,%202,%201987.pdf">Mills ad Weldon (1987), Reading text from computer screens</a>.</p>
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li><a href="http://redcatco.com/blog/communication/twestival/" title="Twestival (updated)">Twestival (updated)</a></li><li><a href="http://redcatco.com/blog/technology/power-up-your-business-with-a-wiki/" title="Power up your business with a Wiki">Power up your business with a Wiki</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://redcatco.com/blog/communication/speed-reading-an-essential-survival-skill-for-the-knowledge-worker/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Power up your business with a Wiki</title>
		<link>http://redcatco.com/blog/technology/power-up-your-business-with-a-wiki/</link>
		<comments>http://redcatco.com/blog/technology/power-up-your-business-with-a-wiki/#comments</comments>
		<pubDate>Fri, 28 Mar 2008 20:35:57 +0000</pubDate>
		<dc:creator>Benjamin Ellis</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[business]]></category>
		<category><![CDATA[enterprise]]></category>
		<category><![CDATA[knowledge management]]></category>
		<category><![CDATA[productivity]]></category>
		<category><![CDATA[Social Computing]]></category>
		<category><![CDATA[social software]]></category>
		<category><![CDATA[wiki]]></category>

		<guid isPermaLink="false">http://redcatco.com/blog/technology/power-up-your-business-with-a-wiki/</guid>
		<description><![CDATA[Reading a recent post on David Tebbutt's blog - You calling me a consultant? - took me to: What’s the real value of social software in enterprise from Adriana Lukas, which leads us to this post...]]></description>
			<content:encoded><![CDATA[<p><a href="http://redcatco.com/blog/" title="Power Button"><img src="http://redcatco.com/blog/wp-content/uploads/2008/03/powerbutton.jpg" alt="Power Button" align="right" /></a>Reading a recent post on David Tebbutt&#8217;s blog &#8211; <a href="http://teblog.typepad.com/david_tebbutt/2008/03/you-calling-me.html">You calling me a consultant?</a> &#8211; took me to:  <a href="http://www.mediainfluencer.net/2008/03/whats-the-real-value-of-social-software-in-enterprise/">What’s the real value of social software in enterprise</a>  from Adriana Lukas, which leads us to this post&#8230;</p>
<p>My longest experience with business social software has been with <a href="http://redcatco.com/blog/tag/wiki/">wikis</a>. I first used a <a href="http://redcatco.com/blog/tag/wiki/">Wikis</a> in a businesses about ten years ago, and have now seen a number of projects across different companies. Case studies are still hard to come by, partly because introducing wikis touches on some sensitive issues. It is not just about the technology, it is about a cultural shift. In many command-and-control cultures information is (seen as) power, but social software moves people  towards sharing it. That is a big change.</p>
<h2>Be Careful What You Measure</h2>
<p>The major benefits of wiki technology are tangential ones. As such they present challenges for metrics, but I have seen multi-million dollar roll outs of &#8216;traditional&#8217; applications hit their metrics, but be a productivity disaster. Metrics cut both ways, and there is the risk of MacNamara&#8217;s fallacy:</p>
<blockquote><p>&#8220;The first step is to measure whatever can easily be measured. This is OK as far as it goes. The second step is to disregard that which can&#8217;t be easily measured or to give it an arbitrary quantitative value. This is artificial and misleading. The third step is to presume that what can&#8217;t be measured easily really isn&#8217;t important. This is blindness. The fourth step is to say that what can&#8217;t be easily measured really doesn&#8217;t exist. This is suicide.&#8221;</p></blockquote>
<p>The quote is from Charles Handy, but it came via wikipedia and I&#8217;ve already said enough about <a href="http://redcatco.com/blog/leadership/learning/wikipedia-a-means-not-an-end/">wikipedia research</a>. The Adam Curtis BBC program &#8216;The Trap&#8217; explored this topic well, if you have the chance to watch it, it is well worth it.</p>
<p>Measuring human systems, like users with a wiki, is non-trivial. You change what you measure, simply by measuring it. This is not to say that things shouldn&#8217;t be measured, but they should be measured with caution. It might sound a little trite, but there is truth in saying that the most valuable things are invaluable (or immeasurable).</p>
<p>Wikis are most successful when they are introduced while the company is still small and growing. That way they become part of the culture. Not to say that big businesses can&#8217;t be successful with wikis, but it requires a good training program around them. The only wiki-failures I have found were in very large companies, where the technology was introduced with minimal training and no clear objectives, and predictable results.</p>
<h2>What are the major benefits of a wiki to a business?</h2>
<p>These apply just as well to any form of social workgroup, not just to businesses. They also apply for groups of two to hundreds, but the scaling of wikis is a topic for another day.</p>
<h3>Knowledge Availability</h3>
<p>Wikis remove much of the chance factor in finding knowledge in the business. Most intranets contain woefully out of date information, through no fault of the intranet owners. Users are left to chance upon the right person who is &#8216;in the know&#8217;. Wikis also reduce the dependence on key knowledge workers for answers to common questions.</p>
<p>Even if the answer isn&#8217;t on the wiki, at least users can glean an idea of who to ask (based on who has been adding what to the wiki). This speeds up the business and offloads the burden on senior staff. This is especially important when you are in a hiring phase. No new hire pack? Search the wiki.</p>
<h3>Change Control</h3>
<p>Basic, but missing from so many information systems in common use. The ability to rollback and track changes is inherent in most wiki software. This can be a life saver and is why wikis are the enterprise CMS of choice for me.</p>
<h3>Knowledge Permanence</h3>
<p>Wikis are the most constructive and least disruptive way of documenting projects that I have found to date. If someone leaves, at least some of their knowledge remains within the organisation, on the wiki. The same is true for extended absence due to illness, travel or long holidays.</p>
<h3>Knowledge Creation</h3>
<p>Sparks come from striking two things together. The same is true with knowledge. I have watched brilliant ideas emerge in real-time on a wiki page, right in front of my eyes. Something new on the wiki combined with something someone already knows leads to new knowledge in the business, across multiple people.</p>
<h3>Geographic Freedom</h3>
<p>Wikis work across geographic boundaries and across time zones. That supports remote offices and remote workers on a global basis. This is key to keeping a business competitive. Water cooler chat is good, but it doesn&#8217;t scale across national boundaries.</p>
<h3>Cross Platform Portability</h3>
<p>Because wikis are web based, the only client required is a browser. That means wikis work across different operating systems and even for mobile devices like Blackberries and smart phones.</p>
<p>So, hopefully now you can see why I am a wiki fan.</p>
<h3  class="related_post_title">Related Posts</h3><ul class="related_post"><li><a href="http://redcatco.com/blog/communication/do-your-employees-dance/" title="Do Your Employees Dance?">Do Your Employees Dance?</a></li><li><a href="http://redcatco.com/blog/productivity/what-will-enterprise-20-look-like-some-thoughts-from-crystal-balls/" title="What will Enterprise 2.0 look like? Some Thoughts from Crystal Balls">What will Enterprise 2.0 look like? Some Thoughts from Crystal Balls</a></li><li><a href="http://redcatco.com/blog/leadership/learning/wikipedia-a-means-not-an-end/" title="Wikipedia &#8211; A Means not an End">Wikipedia &#8211; A Means not an End</a></li><li><a href="http://redcatco.com/blog/leadership/a-perspective-on-community/" title="A Perspective on Community">A Perspective on Community</a></li><li><a href="http://redcatco.com/blog/social-media/social-media-week-london/" title="Social Media Week London">Social Media Week London</a></li></ul>]]></content:encoded>
			<wfw:commentRss>http://redcatco.com/blog/technology/power-up-your-business-with-a-wiki/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>


