<?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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments on: UIEtips: Harnessing the Power of Annotations &#8211; An Interview with Dan Brown</title>
	<atom:link href="http://www.uie.com/brainsparks/2009/04/03/uietipsdanbrown/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uie.com/brainsparks/2009/04/03/uietipsdanbrown/</link>
	<description>UIE\'s latest insights on the world of design</description>
	<lastBuildDate>Sat, 25 May 2013 17:25:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: Partial Recall &#187; Links for 2009-04-09</title>
		<link>http://www.uie.com/brainsparks/2009/04/03/uietipsdanbrown/comment-page-1/#comment-146139</link>
		<dc:creator>Partial Recall &#187; Links for 2009-04-09</dc:creator>
		<pubDate>Tue, 21 Apr 2009 14:12:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=806#comment-146139</guid>
		<description>[...] UIEtips: Harnessing the Power of Annotations - An Interview with Dan Brown [...]</description>
		<content:encoded><![CDATA[<p>[...] UIEtips: Harnessing the Power of Annotations &#8211; An Interview with Dan Brown [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Brown</title>
		<link>http://www.uie.com/brainsparks/2009/04/03/uietipsdanbrown/comment-page-1/#comment-146052</link>
		<dc:creator>Dan Brown</dc:creator>
		<pubDate>Mon, 06 Apr 2009 11:06:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=806#comment-146052</guid>
		<description>@revi: Great comment. There are tons of ways to skin this cat, of course, but your story suggests (rightly so, I believe) to engage with the people who are going to use the documentation. You&#039;ve established a rhythm with your team that keeps you efficient while giving them what they need.

Designers of all stripes should do the same. We&#039;re designing for users but documenting for our colleagues. We should ask them about what in our deliverables will support their work the best.</description>
		<content:encoded><![CDATA[<p>@revi: Great comment. There are tons of ways to skin this cat, of course, but your story suggests (rightly so, I believe) to engage with the people who are going to use the documentation. You&#8217;ve established a rhythm with your team that keeps you efficient while giving them what they need.</p>
<p>Designers of all stripes should do the same. We&#8217;re designing for users but documenting for our colleagues. We should ask them about what in our deliverables will support their work the best.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Revi Körnmann</title>
		<link>http://www.uie.com/brainsparks/2009/04/03/uietipsdanbrown/comment-page-1/#comment-146049</link>
		<dc:creator>Revi Körnmann</dc:creator>
		<pubDate>Sun, 05 Apr 2009 20:58:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=806#comment-146049</guid>
		<description>Annotations are very important, yet highly time-consuming and hard to keep up to date when visual design and front end is being processed. Before wasting time on annotations I make sure my teammates get the wireframes with high level annotations, as work in progress, along with an ephemeral moment of speech. As soon as Visual Design or front end produced some work, I place the mockups as linked documents in InDesign on top of the wireframes, and finetune the annotations. This way you&#039;ll have a user experience design document which is easier (and less frustrating) to keep up to date as the source files change.. also the client gets to see the process of pouring the sauce over the interaction, which enables him to give feedback along the way in stead of coming to conclusion that he liked the grey version better..</description>
		<content:encoded><![CDATA[<p>Annotations are very important, yet highly time-consuming and hard to keep up to date when visual design and front end is being processed. Before wasting time on annotations I make sure my teammates get the wireframes with high level annotations, as work in progress, along with an ephemeral moment of speech. As soon as Visual Design or front end produced some work, I place the mockups as linked documents in InDesign on top of the wireframes, and finetune the annotations. This way you&#8217;ll have a user experience design document which is easier (and less frustrating) to keep up to date as the source files change.. also the client gets to see the process of pouring the sauce over the interaction, which enables him to give feedback along the way in stead of coming to conclusion that he liked the grey version better..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mat Atkinson</title>
		<link>http://www.uie.com/brainsparks/2009/04/03/uietipsdanbrown/comment-page-1/#comment-146047</link>
		<dc:creator>Mat Atkinson</dc:creator>
		<pubDate>Sun, 05 Apr 2009 11:39:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=806#comment-146047</guid>
		<description>Annotations can be more than just a way for a designer to add commentary to a visual design.  They can also be the starting point for full collaboration between the designer and the people reviewing the work - whether colleagues or clients.</description>
		<content:encoded><![CDATA[<p>Annotations can be more than just a way for a designer to add commentary to a visual design.  They can also be the starting point for full collaboration between the designer and the people reviewing the work &#8211; whether colleagues or clients.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
