<?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 on: Looking for examples of microcopy</title>
	<atom:link href="http://bokardo.com/archives/looking-for-examples-of-microcopy/feed/" rel="self" type="application/rss+xml" />
	<link>http://bokardo.com/archives/looking-for-examples-of-microcopy/</link>
	<description>A Blog about Social Web Design</description>
	<lastBuildDate>Fri, 19 Feb 2010 06:52:26 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jordan</title>
		<link>http://bokardo.com/archives/looking-for-examples-of-microcopy/comment-page-1/#comment-296865</link>
		<dc:creator>Jordan</dc:creator>
		<pubDate>Mon, 23 Nov 2009 23:23:25 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=1564#comment-296865</guid>
		<description>Some of those have more fine print than what you would look for in a &lt;a href=&quot;http://www.thebenefitguys.ca&quot; rel=&quot;nofollow&quot;&gt;Life Insurance&lt;/a&gt; policy!</description>
		<content:encoded><![CDATA[<p>Some of those have more fine print than what you would look for in a <a href="http://www.thebenefitguys.ca" rel="nofollow">Life Insurance</a> policy!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://bokardo.com/archives/looking-for-examples-of-microcopy/comment-page-1/#comment-296853</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Fri, 20 Nov 2009 14:31:48 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=1564#comment-296853</guid>
		<description>Microcopy is a great way to make things clearer. I used to track all issues I had on my website and several of these problems were simply solved using microcopy. I also sometimes try to improve these sentences using multivariate testing.</description>
		<content:encoded><![CDATA[<p>Microcopy is a great way to make things clearer. I used to track all issues I had on my website and several of these problems were simply solved using microcopy. I also sometimes try to improve these sentences using multivariate testing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Albert</title>
		<link>http://bokardo.com/archives/looking-for-examples-of-microcopy/comment-page-1/#comment-296807</link>
		<dc:creator>Albert</dc:creator>
		<pubDate>Mon, 16 Nov 2009 11:28:22 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=1564#comment-296807</guid>
		<description>Microblogging is really so important.
An advice on webforms: Spare the text where it&#039;s not necessary in order to get the full attention on where it truly is.</description>
		<content:encoded><![CDATA[<p>Microblogging is really so important.<br />
An advice on webforms: Spare the text where it&#8217;s not necessary in order to get the full attention on where it truly is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan</title>
		<link>http://bokardo.com/archives/looking-for-examples-of-microcopy/comment-page-1/#comment-296782</link>
		<dc:creator>Jonathan</dc:creator>
		<pubDate>Sat, 14 Nov 2009 18:36:38 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=1564#comment-296782</guid>
		<description>The success or failure of micro (or indeed any) copy on the web is determined by whether it gets read. In turn, the thing that determines whether it gets read is whether the person using the system is inclined to read it at that time. And that inclination is determined primarily by three things: doubt, confusion, or fear.

If the person using the system has no doubt, confusion or fear about what they are doing or are about to do, then the chances of them reading any text in the UI is a great deal less than if they are experiencing those emotions. This is why people generally don&#039;t read warning messages unless heavily interrupted, because most people don&#039;t expect anything to be warned about.

So the skill of the UI designer is to find out whether there are any contextual cues to prompt those emotions. If there are not, then the designer must not put any text in the way of usability. 

This is why (for example), I favour only flagging optional fields in web forms, and only using text that I think people may be inclined to read as a &quot;crutch&quot; in certain contexts. 

Otherwise, I just shut the hell up.</description>
		<content:encoded><![CDATA[<p>The success or failure of micro (or indeed any) copy on the web is determined by whether it gets read. In turn, the thing that determines whether it gets read is whether the person using the system is inclined to read it at that time. And that inclination is determined primarily by three things: doubt, confusion, or fear.</p>
<p>If the person using the system has no doubt, confusion or fear about what they are doing or are about to do, then the chances of them reading any text in the UI is a great deal less than if they are experiencing those emotions. This is why people generally don&#8217;t read warning messages unless heavily interrupted, because most people don&#8217;t expect anything to be warned about.</p>
<p>So the skill of the UI designer is to find out whether there are any contextual cues to prompt those emotions. If there are not, then the designer must not put any text in the way of usability. </p>
<p>This is why (for example), I favour only flagging optional fields in web forms, and only using text that I think people may be inclined to read as a &#8220;crutch&#8221; in certain contexts. </p>
<p>Otherwise, I just shut the hell up.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
