<?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 for Knowledge Management and Communication in the Life Sciences</title>
	<atom:link href="http://brain.brainery.net/mcblog/?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://brain.brainery.net/mcblog</link>
	<description>The McCulley/Cuppan Blog on Tools and Strategies for Improving Quality of Knowledge Management and Communication in the Life Sciences</description>
	<lastBuildDate>Wed, 08 Dec 2010 18:54:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on More thoughts on the limited sophistication of documentation practices in the life sciences by Kenneth Robinson</title>
		<link>http://brain.brainery.net/mcblog/?p=898&#038;cpage=1#comment-6019</link>
		<dc:creator>Kenneth Robinson</dc:creator>
		<pubDate>Wed, 08 Dec 2010 18:54:26 +0000</pubDate>
		<guid isPermaLink="false">http://brain.brainery.net/mcblog/?p=898#comment-6019</guid>
		<description>Hello G. McC.

Good points made on all levels.  I am encountering greater acceptance of the principles articulated in the optimized set above.  It representes a big shift in total orientation to how teams and writers approach all of this.  Given that the ultimate product of research is documents, it seems amazing that all of this has not been addressed more thoroughly in the past. Even more puzzling is the fact that so few people have actually investigated the possibility of redesigning how they do all of this.   I hve jsut completed 2 Clinical Overviews for which I got high marks from the teams, and in one case from upper management.  I applied a good bit of what I learned from McCulley Cuppan, and one team leader who was sceptical about deductive writng at the beginning was actually quite pleased with the document.  Another important contributor spoke highly of how well written the CO was and wanted to learn about why it had been done as it had.   - Ken</description>
		<content:encoded><![CDATA[<p>Hello G. McC.</p>
<p>Good points made on all levels.  I am encountering greater acceptance of the principles articulated in the optimized set above.  It representes a big shift in total orientation to how teams and writers approach all of this.  Given that the ultimate product of research is documents, it seems amazing that all of this has not been addressed more thoroughly in the past. Even more puzzling is the fact that so few people have actually investigated the possibility of redesigning how they do all of this.   I hve jsut completed 2 Clinical Overviews for which I got high marks from the teams, and in one case from upper management.  I applied a good bit of what I learned from McCulley Cuppan, and one team leader who was sceptical about deductive writng at the beginning was actually quite pleased with the document.  Another important contributor spoke highly of how well written the CO was and wanted to learn about why it had been done as it had.   &#8211; Ken</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Effective argumentation often missing from clinical research reports by kirkistan</title>
		<link>http://brain.brainery.net/mcblog/?p=884&#038;cpage=1#comment-5514</link>
		<dc:creator>kirkistan</dc:creator>
		<pubDate>Wed, 10 Nov 2010 22:59:24 +0000</pubDate>
		<guid isPermaLink="false">http://brain.brainery.net/mcblog/?p=884#comment-5514</guid>
		<description>There&#039;s a lot of work involved with producing solid, well-reasoned conclusions. Can it even be accomplished as an &quot;authoring team&quot; or is it the work of an individual? Recent research about medical device companies in Minnesota suggests communication teams are chronically understaffed. So--who has time to come to the right conclusions? Thanks for the thoughtful post.</description>
		<content:encoded><![CDATA[<p>There&#8217;s a lot of work involved with producing solid, well-reasoned conclusions. Can it even be accomplished as an &#8220;authoring team&#8221; or is it the work of an individual? Recent research about medical device companies in Minnesota suggests communication teams are chronically understaffed. So&#8211;who has time to come to the right conclusions? Thanks for the thoughtful post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The importance of reviewers understanding their readers and the need to be informed by reading theory by kirkistan</title>
		<link>http://brain.brainery.net/mcblog/?p=851&#038;cpage=1#comment-5126</link>
		<dc:creator>kirkistan</dc:creator>
		<pubDate>Wed, 06 Oct 2010 15:57:14 +0000</pubDate>
		<guid isPermaLink="false">http://brain.brainery.net/mcblog/?p=851#comment-5126</guid>
		<description>Maybe you answered your own perplexity: because of the preconscious baggage each reader brings to the text, the best any of us can do is make sure the facts are right. Facts meaning the numbers, the charts, the etc. Then again, even the facts aren&#039;t exactly facts are they, because what have we left out to make our point? What was the solution you proposed?</description>
		<content:encoded><![CDATA[<p>Maybe you answered your own perplexity: because of the preconscious baggage each reader brings to the text, the best any of us can do is make sure the facts are right. Facts meaning the numbers, the charts, the etc. Then again, even the facts aren&#8217;t exactly facts are they, because what have we left out to make our point? What was the solution you proposed?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Proving Your Document Quality by gcuppan</title>
		<link>http://brain.brainery.net/mcblog/?p=832&#038;cpage=1#comment-4854</link>
		<dc:creator>gcuppan</dc:creator>
		<pubDate>Sat, 18 Sep 2010 13:18:19 +0000</pubDate>
		<guid isPermaLink="false">http://brain.brainery.net/mcblog/?p=832#comment-4854</guid>
		<description>Lili I want to build on your speculation as to why document quality standards largely receives little attention in the pharmaceutical and medical device research communities. I think part of the problem has its roots in the old natural positivists view that if you design the right study then everything else will be self-evident. So in essence, &quot;we just need good data.&quot;  
I think another factor as to why quality standards receives little attention is that documentation is seen as something &quot;that we can always fix later.&quot; The notion here is the penalty for documents that communicate poorly is not nearly as severe as the penalty for producing documents that miss announced timelines. Time is largely the only metric of concern when it comes to documents in the pharmaceutical and med device industries.</description>
		<content:encoded><![CDATA[<p>Lili I want to build on your speculation as to why document quality standards largely receives little attention in the pharmaceutical and medical device research communities. I think part of the problem has its roots in the old natural positivists view that if you design the right study then everything else will be self-evident. So in essence, &#8220;we just need good data.&#8221;<br />
I think another factor as to why quality standards receives little attention is that documentation is seen as something &#8220;that we can always fix later.&#8221; The notion here is the penalty for documents that communicate poorly is not nearly as severe as the penalty for producing documents that miss announced timelines. Time is largely the only metric of concern when it comes to documents in the pharmaceutical and med device industries.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Proving Your Document Quality by Lili Velez</title>
		<link>http://brain.brainery.net/mcblog/?p=832&#038;cpage=1#comment-4849</link>
		<dc:creator>Lili Velez</dc:creator>
		<pubDate>Sat, 18 Sep 2010 02:14:55 +0000</pubDate>
		<guid isPermaLink="false">http://brain.brainery.net/mcblog/?p=832#comment-4849</guid>
		<description>Speaking from the academic side, yes, it&#039;s important to develop rigorous, repeatable forms of assessment.... 

...but I suspect where we part ways with the business world is our desire to see those tools made widely available, so everyone could make those comparisons.  Maybe some companies do have a way to assess their document products [beyond the companies you have as clients].....but sharing those testing instruments might be seen as giving away a competitive advantage?

I&#039;m also wondering if a reason that document quality standards have gotten less attention in the past is because the feeling in the industry was &quot;as long as the data is in the right tables, our drug/medical device/etc will shine through&quot;.  Now that there are apparently fewer candidates in the pipeline, and more questions are being raised about each, companies may be more interested in new metrics for process improvement.</description>
		<content:encoded><![CDATA[<p>Speaking from the academic side, yes, it&#8217;s important to develop rigorous, repeatable forms of assessment&#8230;. </p>
<p>&#8230;but I suspect where we part ways with the business world is our desire to see those tools made widely available, so everyone could make those comparisons.  Maybe some companies do have a way to assess their document products [beyond the companies you have as clients]&#8230;..but sharing those testing instruments might be seen as giving away a competitive advantage?</p>
<p>I&#8217;m also wondering if a reason that document quality standards have gotten less attention in the past is because the feeling in the industry was &#8220;as long as the data is in the right tables, our drug/medical device/etc will shine through&#8221;.  Now that there are apparently fewer candidates in the pipeline, and more questions are being raised about each, companies may be more interested in new metrics for process improvement.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

