<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for ffeathers</title>
	<atom:link href="http://ffeathers.wordpress.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://ffeathers.wordpress.com</link>
	<description>A technical writing and fiction blog by Sarah Maddox</description>
	<lastBuildDate>Tue, 18 Jun 2013 02:40:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>Comment on Workshops on effective writing &#8211; technical writers adding value by Swapnil Ogale</title>
		<link>http://ffeathers.wordpress.com/2013/06/16/workshops-on-effective-writing-technical-writers-adding-value/#comment-16314</link>
		<dc:creator><![CDATA[Swapnil Ogale]]></dc:creator>
		<pubDate>Tue, 18 Jun 2013 02:40:19 +0000</pubDate>
		<guid isPermaLink="false">http://ffeathers.wordpress.com/?p=4947#comment-16314</guid>
		<description><![CDATA[Thanks for the post Sarah. Excellent way to keep documentation throughout the organisation standardised. Would love to hear/read some of the feedback non TWs had about the value TWs added to the organisation in this manner.

Also loved this statement &quot;Sometimes we forget just how much we know&quot;. Nice.]]></description>
		<content:encoded><![CDATA[<p>Thanks for the post Sarah. Excellent way to keep documentation throughout the organisation standardised. Would love to hear/read some of the feedback non TWs had about the value TWs added to the organisation in this manner.</p>
<p>Also loved this statement &#8220;Sometimes we forget just how much we know&#8221;. Nice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Banner blindness and technical documentation by Sarah Maddox</title>
		<link>http://ffeathers.wordpress.com/2013/06/10/banner-blindness-and-technical-documentation/#comment-16302</link>
		<dc:creator><![CDATA[Sarah Maddox]]></dc:creator>
		<pubDate>Mon, 17 Jun 2013 00:24:05 +0000</pubDate>
		<guid isPermaLink="false">http://ffeathers.wordpress.com/?p=4936#comment-16302</guid>
		<description><![CDATA[Hallo Julia

Ha ha, what a great comment! It made me think of our own &quot;warning&quot; boxes, which currently have an icon of a no-entry sign. That&#039;s the default icon which Confluence wiki uses for a warning message. Sometimes it has occurred to me, when seeing a warning box at the top of a page, that it seems to tell people &quot;Don&#039;t enter here&quot;. When in actual fact, we really do want them to enter the page and read the information. It should say, &quot;Come in, there&#039;s some really important stuff for you to know&quot;.

Cheers
Sarah]]></description>
		<content:encoded><![CDATA[<p>Hallo Julia</p>
<p>Ha ha, what a great comment! It made me think of our own &#8220;warning&#8221; boxes, which currently have an icon of a no-entry sign. That&#8217;s the default icon which Confluence wiki uses for a warning message. Sometimes it has occurred to me, when seeing a warning box at the top of a page, that it seems to tell people &#8220;Don&#8217;t enter here&#8221;. When in actual fact, we really do want them to enter the page and read the information. It should say, &#8220;Come in, there&#8217;s some really important stuff for you to know&#8221;.</p>
<p>Cheers<br />
Sarah</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Banner blindness and technical documentation by Julia</title>
		<link>http://ffeathers.wordpress.com/2013/06/10/banner-blindness-and-technical-documentation/#comment-16301</link>
		<dc:creator><![CDATA[Julia]]></dc:creator>
		<pubDate>Sun, 16 Jun 2013 23:56:47 +0000</pubDate>
		<guid isPermaLink="false">http://ffeathers.wordpress.com/?p=4936#comment-16301</guid>
		<description><![CDATA[I&#039;ve also seen research that suggested that using frightening warning symbols beside cautionary text can discourage people from reading the warning.  I think there was a case where people didn&#039;t read safety notices beside a swimming pool because they were upset by the stick figure of a drowning child. 

But I also recall reading that, while people might be less likely to read pulled-out warning text, it helps to be able to point to it when you get to court.

We use lots of cautionary notes and warnings, although we also try to use inline warnings as well. I think of the inline warnings as being for the readers, and the bright red &quot;don&#039;t cut your hand off&quot; boxes with the lurid graphic as being for the lawyers.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ve also seen research that suggested that using frightening warning symbols beside cautionary text can discourage people from reading the warning.  I think there was a case where people didn&#8217;t read safety notices beside a swimming pool because they were upset by the stick figure of a drowning child. </p>
<p>But I also recall reading that, while people might be less likely to read pulled-out warning text, it helps to be able to point to it when you get to court.</p>
<p>We use lots of cautionary notes and warnings, although we also try to use inline warnings as well. I think of the inline warnings as being for the readers, and the bright red &#8220;don&#8217;t cut your hand off&#8221; boxes with the lurid graphic as being for the lawyers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Banner blindness and technical documentation by Sarah Maddox</title>
		<link>http://ffeathers.wordpress.com/2013/06/10/banner-blindness-and-technical-documentation/#comment-16284</link>
		<dc:creator><![CDATA[Sarah Maddox]]></dc:creator>
		<pubDate>Sat, 15 Jun 2013 05:18:06 +0000</pubDate>
		<guid isPermaLink="false">http://ffeathers.wordpress.com/?p=4936#comment-16284</guid>
		<description><![CDATA[Hallo Melody :)

I&#039;d love to hear the results of that user testing! Interestingly, I was running a writing workshop for a group of HR people within our company this week. We chatted a bit about banner blindness, and the responses differed from person to person. Some people say their eyes are drawn immediately to text in boxes, because they know that&#039;s likely to be the most important. Others said they read the main body of the page. Of course, what people say isn&#039;t necessarily what they do. :)

Good point about stacked boxes. We sometimes do have a number of notes on a page, but then the tech writers put them in a bullet list under a heading like &quot;notes&quot; or &quot;before you start&quot;. Other people who update our docs, such as the support engineers or developers, do tend to stack note and warning boxes merrily.

Cheers
Sarah]]></description>
		<content:encoded><![CDATA[<p>Hallo Melody <img src='http://s0.wp.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>I&#8217;d love to hear the results of that user testing! Interestingly, I was running a writing workshop for a group of HR people within our company this week. We chatted a bit about banner blindness, and the responses differed from person to person. Some people say their eyes are drawn immediately to text in boxes, because they know that&#8217;s likely to be the most important. Others said they read the main body of the page. Of course, what people say isn&#8217;t necessarily what they do. <img src='http://s0.wp.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Good point about stacked boxes. We sometimes do have a number of notes on a page, but then the tech writers put them in a bullet list under a heading like &#8220;notes&#8221; or &#8220;before you start&#8221;. Other people who update our docs, such as the support engineers or developers, do tend to stack note and warning boxes merrily.</p>
<p>Cheers<br />
Sarah</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Banner blindness and technical documentation by Melody</title>
		<link>http://ffeathers.wordpress.com/2013/06/10/banner-blindness-and-technical-documentation/#comment-16278</link>
		<dc:creator><![CDATA[Melody]]></dc:creator>
		<pubDate>Fri, 14 Jun 2013 13:51:13 +0000</pubDate>
		<guid isPermaLink="false">http://ffeathers.wordpress.com/?p=4936#comment-16278</guid>
		<description><![CDATA[Hi Sarah,

I also have banner blindness, but I don&#039;t place boxes like Notes and Warnings in the same category as ad banners. However, I think that sometimes we use Notes to present information that could be presented in a better way. I cringe whenever I see &quot;stacked&quot; Note boxes on a page.

I think that this issue would make a great user test. I&#039;ll put such a test on my list of action items and let you know if/when we run it. 

Melody]]></description>
		<content:encoded><![CDATA[<p>Hi Sarah,</p>
<p>I also have banner blindness, but I don&#8217;t place boxes like Notes and Warnings in the same category as ad banners. However, I think that sometimes we use Notes to present information that could be presented in a better way. I cringe whenever I see &#8220;stacked&#8221; Note boxes on a page.</p>
<p>I think that this issue would make a great user test. I&#8217;ll put such a test on my list of action items and let you know if/when we run it. </p>
<p>Melody</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on About me by Ellis Pratt</title>
		<link>http://ffeathers.wordpress.com/about/#comment-16239</link>
		<dc:creator><![CDATA[Ellis Pratt]]></dc:creator>
		<pubDate>Tue, 11 Jun 2013 09:10:22 +0000</pubDate>
		<guid isPermaLink="false">http://ffeathers.wordpress.com/about/#comment-16239</guid>
		<description><![CDATA[JoAnn Hackos publishes benchmarking metrics See http://www.infomanagementcenter.com/]]></description>
		<content:encoded><![CDATA[<p>JoAnn Hackos publishes benchmarking metrics See <a href="http://www.infomanagementcenter.com/" rel="nofollow">http://www.infomanagementcenter.com/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on About me by @techwriterkai</title>
		<link>http://ffeathers.wordpress.com/about/#comment-16238</link>
		<dc:creator><![CDATA[@techwriterkai]]></dc:creator>
		<pubDate>Tue, 11 Jun 2013 07:22:42 +0000</pubDate>
		<guid isPermaLink="false">http://ffeathers.wordpress.com/about/#comment-16238</guid>
		<description><![CDATA[Hi, Greg, how would you want to measure quality? 

&quot;Developing Quality Technical Information&quot; by Gretchen Hargis, et al. has several useful criteria for what makes for high-quality documents, such as task-oriented, accurate, complete, clear, concrete, well organized/structured, retrievable, visually effective. However, most of these criteria cannot be quantified easily and most cannot be automated reliably. They usually require one or several human judges which makes the whole benchmarking process quite costly.

For a more extensive discussion and resources, see my blog post http://kaiweber.wordpress.com/2011/02/14/improve-documentation-with-quality-metrics/]]></description>
		<content:encoded><![CDATA[<p>Hi, Greg, how would you want to measure quality? </p>
<p>&#8220;Developing Quality Technical Information&#8221; by Gretchen Hargis, et al. has several useful criteria for what makes for high-quality documents, such as task-oriented, accurate, complete, clear, concrete, well organized/structured, retrievable, visually effective. However, most of these criteria cannot be quantified easily and most cannot be automated reliably. They usually require one or several human judges which makes the whole benchmarking process quite costly.</p>
<p>For a more extensive discussion and resources, see my blog post <a href="http://kaiweber.wordpress.com/2011/02/14/improve-documentation-with-quality-metrics/" rel="nofollow">http://kaiweber.wordpress.com/2011/02/14/improve-documentation-with-quality-metrics/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Banner blindness and technical documentation by Sarah Maddox</title>
		<link>http://ffeathers.wordpress.com/2013/06/10/banner-blindness-and-technical-documentation/#comment-16230</link>
		<dc:creator><![CDATA[Sarah Maddox]]></dc:creator>
		<pubDate>Tue, 11 Jun 2013 02:56:30 +0000</pubDate>
		<guid isPermaLink="false">http://ffeathers.wordpress.com/?p=4936#comment-16230</guid>
		<description><![CDATA[Hallo Larry

Great points! Perhaps we also tend to increase the banner blindness in our readers, by adding side panels for navigation, top panels for menu options, bottom panels for related topics... I certainly find myself homing in on the plain, readable text. The good old bullet list, with bold words indicating the key points, are usually a good indication of the meat of a topic. :)

Cheers
Sarah]]></description>
		<content:encoded><![CDATA[<p>Hallo Larry</p>
<p>Great points! Perhaps we also tend to increase the banner blindness in our readers, by adding side panels for navigation, top panels for menu options, bottom panels for related topics&#8230; I certainly find myself homing in on the plain, readable text. The good old bullet list, with bold words indicating the key points, are usually a good indication of the meat of a topic. <img src='http://s0.wp.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Cheers<br />
Sarah</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Banner blindness and technical documentation by Sarah Maddox</title>
		<link>http://ffeathers.wordpress.com/2013/06/10/banner-blindness-and-technical-documentation/#comment-16229</link>
		<dc:creator><![CDATA[Sarah Maddox]]></dc:creator>
		<pubDate>Tue, 11 Jun 2013 02:54:15 +0000</pubDate>
		<guid isPermaLink="false">http://ffeathers.wordpress.com/?p=4936#comment-16229</guid>
		<description><![CDATA[Hallo Charles
Awesome! I&#039;m so glad you like Anne&#039;s speech bubbles. What a lovely idea, to emphasise the personal experience aspect. Your idea of using standard icons sounds great too. When you&#039;re ready, perhaps you&#039;d like to post a link to the docs?
Cheers, Sarah]]></description>
		<content:encoded><![CDATA[<p>Hallo Charles<br />
Awesome! I&#8217;m so glad you like Anne&#8217;s speech bubbles. What a lovely idea, to emphasise the personal experience aspect. Your idea of using standard icons sounds great too. When you&#8217;re ready, perhaps you&#8217;d like to post a link to the docs?<br />
Cheers, Sarah</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Banner blindness and technical documentation by Sarah Maddox</title>
		<link>http://ffeathers.wordpress.com/2013/06/10/banner-blindness-and-technical-documentation/#comment-16228</link>
		<dc:creator><![CDATA[Sarah Maddox]]></dc:creator>
		<pubDate>Tue, 11 Jun 2013 02:51:16 +0000</pubDate>
		<guid isPermaLink="false">http://ffeathers.wordpress.com/?p=4936#comment-16228</guid>
		<description><![CDATA[Hallo Sasha

That&#039;s a great point, that it&#039;s annoying when you are forced to skip over the boxes just to keep the flow of the normal text. It makes me think we should put the boxes off to one side, perhaps in a margin.

Thanks for dropping by. :)
Cheers
Sarah]]></description>
		<content:encoded><![CDATA[<p>Hallo Sasha</p>
<p>That&#8217;s a great point, that it&#8217;s annoying when you are forced to skip over the boxes just to keep the flow of the normal text. It makes me think we should put the boxes off to one side, perhaps in a margin.</p>
<p>Thanks for dropping by. <img src='http://s0.wp.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /><br />
Cheers<br />
Sarah</p>
]]></content:encoded>
	</item>
</channel>
</rss>