<?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: Writing Microcopy</title>
	<atom:link href="http://bokardo.com/archives/writing-microcopy/feed/" rel="self" type="application/rss+xml" />
	<link>http://bokardo.com/archives/writing-microcopy/</link>
	<description>Interface Design &#38; UX by Joshua Porter</description>
	<lastBuildDate>Wed, 28 Sep 2011 20:28:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Looking for examples of microcopy - Bokardo</title>
		<link>http://bokardo.com/archives/writing-microcopy/#comment-296439</link>
		<dc:creator>Looking for examples of microcopy - Bokardo</dc:creator>
		<pubDate>Thu, 12 Nov 2009 15:23:04 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=1168#comment-296439</guid>
		<description>[...] if you&#8217;ve never heard this term before, read Writing Microcopy.  Looking for examples of microcopy &#124;  Grab the Site RSS Feed  Check out my latest project: Make [...]</description>
		<content:encoded><![CDATA[<p>[...] if you&#8217;ve never heard this term before, read Writing Microcopy.  Looking for examples of microcopy |  Grab the Site RSS Feed  Check out my latest project: Make [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rahul</title>
		<link>http://bokardo.com/archives/writing-microcopy/#comment-294578</link>
		<dc:creator>Rahul</dc:creator>
		<pubDate>Fri, 30 Oct 2009 15:39:37 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=1168#comment-294578</guid>
		<description>Came back to read this again and wanted to mention that it&#039;s still so true. Thanks again!

Offtopic: dates for comments are missing the month. It says &quot;Wed 12th, 2009&quot;.</description>
		<content:encoded><![CDATA[<p>Came back to read this again and wanted to mention that it&#8217;s still so true. Thanks again!</p>
<p>Offtopic: dates for comments are missing the month. It says &#8220;Wed 12th, 2009&#8243;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Communicating Value through Cause &#38; Effect on Fanfeedr - Bokardo</title>
		<link>http://bokardo.com/archives/writing-microcopy/#comment-291267</link>
		<dc:creator>Communicating Value through Cause &#38; Effect on Fanfeedr - Bokardo</dc:creator>
		<pubDate>Thu, 17 Sep 2009 12:50:43 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=1168#comment-291267</guid>
		<description>[...] also got an example of microcopy in the line &#8220;we won&#8217;t publish anything to Facebook without asking you first&#8221;. [...]</description>
		<content:encoded><![CDATA[<p>[...] also got an example of microcopy in the line &#8220;we won&#8217;t publish anything to Facebook without asking you first&#8221;. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: No Sign-up Necessary (the strikethrough method) - Bokardo</title>
		<link>http://bokardo.com/archives/writing-microcopy/#comment-290679</link>
		<dc:creator>No Sign-up Necessary (the strikethrough method) - Bokardo</dc:creator>
		<pubDate>Tue, 18 Aug 2009 13:59:29 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=1168#comment-290679</guid>
		<description>[...] strikethrough method is an example of microcopy done well. It serves to address a common concern and helps reduce the commitment we feel as we [...]</description>
		<content:encoded><![CDATA[<p>[...] strikethrough method is an example of microcopy done well. It serves to address a common concern and helps reduce the commitment we feel as we [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil</title>
		<link>http://bokardo.com/archives/writing-microcopy/#comment-290526</link>
		<dc:creator>Phil</dc:creator>
		<pubDate>Thu, 13 Aug 2009 00:43:21 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=1168#comment-290526</guid>
		<description>This is good stuff (I esp liked the tumblr example) but you have to be careful that you do not use microcopy as a crutch.  Sometimes, when you see microcopy, it should really be zerocopy.  For example, in the first example I would have just made a header/title on the billing address area called something like &quot;Credit Card Billing Address:&quot;  

And in the 2nd example, I would just not show the Paypal logo at all--just &quot;Pay with your credit/debit card now!&quot; and be done with it.  You don&#039;t need a crutch when the leg (the user experience) is not broken.</description>
		<content:encoded><![CDATA[<p>This is good stuff (I esp liked the tumblr example) but you have to be careful that you do not use microcopy as a crutch.  Sometimes, when you see microcopy, it should really be zerocopy.  For example, in the first example I would have just made a header/title on the billing address area called something like &#8220;Credit Card Billing Address:&#8221;  </p>
<p>And in the 2nd example, I would just not show the Paypal logo at all&#8211;just &#8220;Pay with your credit/debit card now!&#8221; and be done with it.  You don&#8217;t need a crutch when the leg (the user experience) is not broken.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://bokardo.com/archives/writing-microcopy/#comment-290481</link>
		<dc:creator>David</dc:creator>
		<pubDate>Tue, 11 Aug 2009 10:24:02 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=1168#comment-290481</guid>
		<description>Great post, thanks! Reading the comments I&#039;d also call microcopy  on forms an &quot;affordance&quot;, in usability terms. But microcopy applies to navigation and tooltips as well, I think.</description>
		<content:encoded><![CDATA[<p>Great post, thanks! Reading the comments I&#8217;d also call microcopy  on forms an &#8220;affordance&#8221;, in usability terms. But microcopy applies to navigation and tooltips as well, I think.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fluffy Links &#8211; Monday August 10th 2009 &#171; Damien Mulley</title>
		<link>http://bokardo.com/archives/writing-microcopy/#comment-290462</link>
		<dc:creator>Fluffy Links &#8211; Monday August 10th 2009 &#171; Damien Mulley</dc:creator>
		<pubDate>Mon, 10 Aug 2009 13:01:19 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=1168#comment-290462</guid>
		<description>[...] the small things. Via Ewan&#8217;s delicious, Microcopy is vital for web apps.  # When signing up for a newsletter, say â€œthis low-volume newsletterâ€ # When people add their [...]</description>
		<content:encoded><![CDATA[<p>[...] the small things. Via Ewan&#8217;s delicious, Microcopy is vital for web apps.  # When signing up for a newsletter, say â€œthis low-volume newsletterâ€ # When people add their [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rhonda</title>
		<link>http://bokardo.com/archives/writing-microcopy/#comment-289875</link>
		<dc:creator>Rhonda</dc:creator>
		<pubDate>Thu, 23 Jul 2009 03:23:32 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=1168#comment-289875</guid>
		<description>Technical writers and communicators use the term &#039;user assistance&#039; for what you term &#039;microcopy&#039;. The end result is the same -- making the experience better for the user. But it would be nice and less confusing for searchers and researchers if the technical and marketing writing communities could use a common term for these small pieces of text on user interfaces.</description>
		<content:encoded><![CDATA[<p>Technical writers and communicators use the term &#8216;user assistance&#8217; for what you term &#8216;microcopy&#8217;. The end result is the same &#8212; making the experience better for the user. But it would be nice and less confusing for searchers and researchers if the technical and marketing writing communities could use a common term for these small pieces of text on user interfaces.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex Wu</title>
		<link>http://bokardo.com/archives/writing-microcopy/#comment-289316</link>
		<dc:creator>Alex Wu</dc:creator>
		<pubDate>Sun, 28 Jun 2009 17:35:21 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=1168#comment-289316</guid>
		<description>Joshua, you are absolutely right. Even the tiniest change in microcopy text can have a huge impact on business. For example, on my site signup screen, we used to have a line, separating what is required versus option fields. But most people just ignores that line, so we had additional text telling people what is required. The day we did that, our signup rate went from 1.3% of visitors to over 5%. Then we realized what we did wrong.</description>
		<content:encoded><![CDATA[<p>Joshua, you are absolutely right. Even the tiniest change in microcopy text can have a huge impact on business. For example, on my site signup screen, we used to have a line, separating what is required versus option fields. But most people just ignores that line, so we had additional text telling people what is required. The day we did that, our signup rate went from 1.3% of visitors to over 5%. Then we realized what we did wrong.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 5 of the best and 5 of the rest: Shame on you Habitat! &#171; Qubemedia&#8217;s Weblog</title>
		<link>http://bokardo.com/archives/writing-microcopy/#comment-289048</link>
		<dc:creator>5 of the best and 5 of the rest: Shame on you Habitat! &#171; Qubemedia&#8217;s Weblog</dc:creator>
		<pubDate>Wed, 24 Jun 2009 13:31:37 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=1168#comment-289048</guid>
		<description>[...] Writing Microcopy [...]</description>
		<content:encoded><![CDATA[<p>[...] Writing Microcopy [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad&#8217;s Ramblings &#187; Links for 6/8 &#8211; 6/12</title>
		<link>http://bokardo.com/archives/writing-microcopy/#comment-288369</link>
		<dc:creator>Brad&#8217;s Ramblings &#187; Links for 6/8 &#8211; 6/12</dc:creator>
		<pubDate>Sat, 13 Jun 2009 03:10:09 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=1168#comment-288369</guid>
		<description>[...] Writing microcopy &#8211; It doesn&#8217;t take a memoir in order to help your users get the job done. [...]</description>
		<content:encoded><![CDATA[<p>[...] Writing microcopy &#8211; It doesn&#8217;t take a memoir in order to help your users get the job done. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marsh</title>
		<link>http://bokardo.com/archives/writing-microcopy/#comment-288341</link>
		<dc:creator>Marsh</dc:creator>
		<pubDate>Fri, 12 Jun 2009 14:41:51 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=1168#comment-288341</guid>
		<description>I heartily agree, but
&lt;blockquote&gt;â€œBe sure to enter the billing address associated with your credit cardâ€&lt;/blockquote&gt; could be tightened to &quot;Must match the billing address for your card.&quot; And since the name comes first, &quot;address&quot; might be &quot;information&quot; instead.

Another example is the &lt;blockquote&gt;(not published)&lt;/blockquote&gt;
microcopy note for the &quot;Mail&quot; field of this comment form.</description>
		<content:encoded><![CDATA[<p>I heartily agree, but</p>
<blockquote><p>â€œBe sure to enter the billing address associated with your credit cardâ€</p></blockquote>
<p> could be tightened to &#8220;Must match the billing address for your card.&#8221; And since the name comes first, &#8220;address&#8221; might be &#8220;information&#8221; instead.</p>
<p>Another example is the<br />
<blockquote>(not published)</p></blockquote>
<p>microcopy note for the &#8220;Mail&#8221; field of this comment form.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: One word is worth a thousand support calls â€” KnowIT</title>
		<link>http://bokardo.com/archives/writing-microcopy/#comment-288301</link>
		<dc:creator>One word is worth a thousand support calls â€” KnowIT</dc:creator>
		<pubDate>Thu, 11 Jun 2009 22:11:26 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=1168#comment-288301</guid>
		<description>[...] [Via : Writing Microcopy - Bokardo.] [...]</description>
		<content:encoded><![CDATA[<p>[...] [Via : Writing Microcopy - Bokardo.] [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jens Swelson</title>
		<link>http://bokardo.com/archives/writing-microcopy/#comment-288236</link>
		<dc:creator>Jens Swelson</dc:creator>
		<pubDate>Wed, 10 Jun 2009 18:09:40 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=1168#comment-288236</guid>
		<description>Nice article and very usefull. I think I might need to use this on my blog for the e-mailupdates function.</description>
		<content:encoded><![CDATA[<p>Nice article and very usefull. I think I might need to use this on my blog for the e-mailupdates function.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Yeiser</title>
		<link>http://bokardo.com/archives/writing-microcopy/#comment-288231</link>
		<dc:creator>David Yeiser</dc:creator>
		<pubDate>Wed, 10 Jun 2009 16:51:45 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/?p=1168#comment-288231</guid>
		<description>Like those above me said, great article and great points. 

Tumblr uses microcopy effectively on their &lt;a href=&quot;http://www.tumblr.com/&quot; rel=&quot;nofollow&quot;&gt;signup form&lt;/a&gt;. When choosing a URL for your blog there&#039;s a helpful sentence that reads &quot;(you can change this at any time).&quot; Great for those of us who would sit there and agonize over the perfect blog name.</description>
		<content:encoded><![CDATA[<p>Like those above me said, great article and great points. </p>
<p>Tumblr uses microcopy effectively on their <a href="http://www.tumblr.com/" rel="nofollow">signup form</a>. When choosing a URL for your blog there&#8217;s a helpful sentence that reads &#8220;(you can change this at any time).&#8221; Great for those of us who would sit there and agonize over the perfect blog name.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

