<?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 OpenRoad</title>
	<atom:link href="http://www.openroad.ca/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.openroad.ca</link>
	<description></description>
	<lastBuildDate>Mon, 08 Aug 2011 19:30:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>Comment on Gestures, Postures and Tap Errors: an observation must for Mobile Usability Testing by Selma Zafar</title>
		<link>http://www.openroad.ca/2011/08/04/gestures-postures-and-tap-errors-an-observation-must-for-mobile-usability-testing/comment-page-1/#comment-553</link>
		<dc:creator>Selma Zafar</dc:creator>
		<pubDate>Mon, 08 Aug 2011 19:30:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.openroad.ca/?p=3312#comment-553</guid>
		<description>Great question Anthony.  There are other recording methods that allow the participant to maintain a natural posture while using the mobile device.  Some options that I have used before successfully include: &lt;a href=&quot;http://www.elmousa.com/flash/P30S/ELMO_P30s.swf&quot; rel=&quot;nofollow&quot;&gt;Elmo P30s&lt;/a&gt;, and video camera on a tripod set up &#039;over the shoulder&#039; of the participant.  Both of these set-up allow the participant to interact with the device naturally, and allow adequate capturing or interface interactions.  I would not recommend having the observer in the room as this will make the participant feel uncomfortable.  The key part of any set-up for usability testing is to make the session feel as natural as possible for the participant.</description>
		<content:encoded><![CDATA[<p>Great question Anthony.  There are other recording methods that allow the participant to maintain a natural posture while using the mobile device.  Some options that I have used before successfully include: <a href="http://www.elmousa.com/flash/P30S/ELMO_P30s.swf" rel="nofollow">Elmo P30s</a>, and video camera on a tripod set up &#8216;over the shoulder&#8217; of the participant.  Both of these set-up allow the participant to interact with the device naturally, and allow adequate capturing or interface interactions.  I would not recommend having the observer in the room as this will make the participant feel uncomfortable.  The key part of any set-up for usability testing is to make the session feel as natural as possible for the participant.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Gestures, Postures and Tap Errors: an observation must for Mobile Usability Testing by Anthony Hempell</title>
		<link>http://www.openroad.ca/2011/08/04/gestures-postures-and-tap-errors-an-observation-must-for-mobile-usability-testing/comment-page-1/#comment-552</link>
		<dc:creator>Anthony Hempell</dc:creator>
		<pubDate>Mon, 08 Aug 2011 19:15:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.openroad.ca/?p=3312#comment-552</guid>
		<description>Hey Selma, interesting post.  

The &quot;fixed&quot; method is of course for testing data collection so the screen can be captured by the camera apparatus.

I&#039;m guessing having someone use the handheld in a natural way means much closer observation + note taking during the testing.  How do you facilitate this, do you use another observer in the room?  

Seems like you&#039;d need to be looking over their shoulder while taking notes?</description>
		<content:encoded><![CDATA[<p>Hey Selma, interesting post.  </p>
<p>The &#8220;fixed&#8221; method is of course for testing data collection so the screen can be captured by the camera apparatus.</p>
<p>I&#8217;m guessing having someone use the handheld in a natural way means much closer observation + note taking during the testing.  How do you facilitate this, do you use another observer in the room?  </p>
<p>Seems like you&#8217;d need to be looking over their shoulder while taking notes?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Content Migration: the iceberg of CMS projects by Bryan Robertson</title>
		<link>http://www.openroad.ca/2007/11/02/content-migration-the-iceberg-of-cms-projects/comment-page-1/#comment-539</link>
		<dc:creator>Bryan Robertson</dc:creator>
		<pubDate>Tue, 19 Apr 2011 20:43:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.openroad.ca/if/then/2007/11/02/content-migration-the-iceberg-of-cms-projects/#comment-539</guid>
		<description>Hi Denise,
My first recommendation would be, if your team already has a tracking system to keep track of content changes and enhancements, to use that with perhaps a few modifications. This way, when the content freeze is in effect you are not asking the team to use a completely new process out of the blue. For example, internally, we use a tool called &lt;a href=&quot;http://www.atlassian.com/software/jira/&quot; rel=&quot;nofollow&quot;&gt;JIRA&lt;/a&gt; to track website issues and changes.  The tool lets us identify what type of change is being made. We have two change types or components of interest. One is &quot;Content&quot; and the other is &quot;Content Migration&quot;.  &quot;Content&quot; represents regular content updates. &quot;Content Migration&quot; was used during our recent relaunch of our website for precisely these types of issues. Anything that requires follow up during a Content Freeze could be categorized as &quot;Content Migration&quot;, making it easy to produce a list, and track completion of later.

Using an existing request tool, list tool, or bug tracking software that your team is already familiar with would be the best choice. If you do not have such a system (or a team for that matter), then you could use a spreadsheet.  The columns of your spreadsheet will vary depending on your processes and how you choose to manage your content freeze. To give you some ideas, I have posted a &lt;a href=&quot;http://www.openroad.ca/wp-content/uploads/2011/04/Content-Freeze-Exception-Tracking.xlsx&quot; rel=&quot;nofollow&quot;&gt;free sample spreadsheet that is available for download&lt;/a&gt;. The key things I recommend tracking are: where is the old content, where is the new content, what change needs to be made after the freeze is over, and who to go to if there are issues. 

I hope this helps.</description>
		<content:encoded><![CDATA[<p>Hi Denise,<br />
My first recommendation would be, if your team already has a tracking system to keep track of content changes and enhancements, to use that with perhaps a few modifications. This way, when the content freeze is in effect you are not asking the team to use a completely new process out of the blue. For example, internally, we use a tool called <a href="http://www.atlassian.com/software/jira/" rel="nofollow">JIRA</a> to track website issues and changes.  The tool lets us identify what type of change is being made. We have two change types or components of interest. One is &#8220;Content&#8221; and the other is &#8220;Content Migration&#8221;.  &#8220;Content&#8221; represents regular content updates. &#8220;Content Migration&#8221; was used during our recent relaunch of our website for precisely these types of issues. Anything that requires follow up during a Content Freeze could be categorized as &#8220;Content Migration&#8221;, making it easy to produce a list, and track completion of later.</p>
<p>Using an existing request tool, list tool, or bug tracking software that your team is already familiar with would be the best choice. If you do not have such a system (or a team for that matter), then you could use a spreadsheet.  The columns of your spreadsheet will vary depending on your processes and how you choose to manage your content freeze. To give you some ideas, I have posted a <a href="http://www.openroad.ca/wp-content/uploads/2011/04/Content-Freeze-Exception-Tracking.xlsx" rel="nofollow">free sample spreadsheet that is available for download</a>. The key things I recommend tracking are: where is the old content, where is the new content, what change needs to be made after the freeze is over, and who to go to if there are issues. </p>
<p>I hope this helps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Content Migration: the iceberg of CMS projects by Denise Lindores</title>
		<link>http://www.openroad.ca/2007/11/02/content-migration-the-iceberg-of-cms-projects/comment-page-1/#comment-538</link>
		<dc:creator>Denise Lindores</dc:creator>
		<pubDate>Mon, 21 Mar 2011 13:50:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.openroad.ca/if/then/2007/11/02/content-migration-the-iceberg-of-cms-projects/#comment-538</guid>
		<description>Is there a template available that you know of for tracking content that is added to the old site during content migration. This is bound to be an issue regardless of content freeze efforts.</description>
		<content:encoded><![CDATA[<p>Is there a template available that you know of for tracking content that is added to the old site during content migration. This is bound to be an issue regardless of content freeze efforts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 2009 Interaction Design Year in Review by uberVU - social comments</title>
		<link>http://www.openroad.ca/2009/12/23/2009-interaction-design-year-in-review/comment-page-1/#comment-18</link>
		<dc:creator>uberVU - social comments</dc:creator>
		<pubDate>Thu, 24 Dec 2009 03:45:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.openroad.ca/if/then/?p=89#comment-18</guid>
		<description>&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;

This post was mentioned on Twitter by selmaz: 2009 Interaction Design Year in Review http://bit.ly/7nVcYj #UX #usability...</description>
		<content:encoded><![CDATA[<p><strong>Social comments and analytics for this post&#8230;</strong></p>
<p>This post was mentioned on Twitter by selmaz: 2009 Interaction Design Year in Review <a href="http://bit.ly/7nVcYj" rel="nofollow">http://bit.ly/7nVcYj</a> #UX #usability&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 2009 Interaction Design Year in Review by Twitter Trackbacks for if/then archive - 2009 Interaction Design Year in Review [openroad.ca] on Topsy.com</title>
		<link>http://www.openroad.ca/2009/12/23/2009-interaction-design-year-in-review/comment-page-1/#comment-17</link>
		<dc:creator>Twitter Trackbacks for if/then archive - 2009 Interaction Design Year in Review [openroad.ca] on Topsy.com</dc:creator>
		<pubDate>Wed, 23 Dec 2009 23:12:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.openroad.ca/if/then/?p=89#comment-17</guid>
		<description>[...] if/then archive - 2009 Interaction Design Year in Review  www.openroad.ca/if/then/2009/12/23/2009-interaction-design-year-in-review/ &#8211; view page &#8211; cached  With the end of the year upon us, I thought it would be appropriate to take some time to reflect on the evolution of interaction design in this last year. This year proved to be interesting with some positive advancements in the interaction design trends. Here are some of my favourites that have worked successfully to improve user experiences. [...]</description>
		<content:encoded><![CDATA[<p>[...] if/then archive &#8211; 2009 Interaction Design Year in Review  <a href="http://www.openroad.ca/if/then/2009/12/23/2009-interaction-design-year-in-review/" rel="nofollow">http://www.openroad.ca/if/then/2009/12/23/2009-interaction-design-year-in-review/</a> &ndash; view page &ndash; cached  With the end of the year upon us, I thought it would be appropriate to take some time to reflect on the evolution of interaction design in this last year. This year proved to be interesting with some positive advancements in the interaction design trends. Here are some of my favourites that have worked successfully to improve user experiences. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on VanUE: World Usability Day 2009 by uberVU - social comments</title>
		<link>http://www.openroad.ca/2009/11/18/vanue-world-usability-day-2009/comment-page-1/#comment-16</link>
		<dc:creator>uberVU - social comments</dc:creator>
		<pubDate>Wed, 18 Nov 2009 22:44:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.openroad.ca/if/then/?p=64#comment-16</guid>
		<description>&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;

This post was mentioned on Twitter by gordonr: VanUE World Usability Day blog post: http://bit.ly/2foQHy #wud2009 #vanue...</description>
		<content:encoded><![CDATA[<p><strong>Social comments and analytics for this post&#8230;</strong></p>
<p>This post was mentioned on Twitter by gordonr: VanUE World Usability Day blog post: <a href="http://bit.ly/2foQHy" rel="nofollow">http://bit.ly/2foQHy</a> #wud2009 #vanue&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on VanUE: World Usability Day 2009 by Twitter Trackbacks for if/then archive - VanUE: World Usability Day 2009 [openroad.ca] on Topsy.com</title>
		<link>http://www.openroad.ca/2009/11/18/vanue-world-usability-day-2009/comment-page-1/#comment-15</link>
		<dc:creator>Twitter Trackbacks for if/then archive - VanUE: World Usability Day 2009 [openroad.ca] on Topsy.com</dc:creator>
		<pubDate>Wed, 18 Nov 2009 19:40:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.openroad.ca/if/then/?p=64#comment-15</guid>
		<description>[...] if/then archive - VanUE: World Usability Day 2009  www.openroad.ca/if/then/2009/11/18/vanue-world-usability-day-2009 &#8211; view page &#8211; cached  World Usability Day happened on November 12, 2009 this year and a small squad of Vancouver user experience professionals got together at 8am at the Pine St Community Garden to spend the day together,... Read moreWorld Usability Day happened on November 12, 2009 this year and a small squad of Vancouver user experience professionals got together at 8am at the Pine St Community Garden to spend the day together, wondering how to best bring our professional expertise to bear on the issue of “sustainability” — the theme for WUD2009. Read less [...]</description>
		<content:encoded><![CDATA[<p>[...] if/then archive &#8211; VanUE: World Usability Day 2009  <a href="http://www.openroad.ca/if/then/2009/11/18/vanue-world-usability-day-2009" rel="nofollow">http://www.openroad.ca/if/then/2009/11/18/vanue-world-usability-day-2009</a> &ndash; view page &ndash; cached  World Usability Day happened on November 12, 2009 this year and a small squad of Vancouver user experience professionals got together at 8am at the Pine St Community Garden to spend the day together,&#8230; Read moreWorld Usability Day happened on November 12, 2009 this year and a small squad of Vancouver user experience professionals got together at 8am at the Pine St Community Garden to spend the day together, wondering how to best bring our professional expertise to bear on the issue of “sustainability” — the theme for WUD2009. Read less [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Content Migration: the iceberg of CMS projects by NetworkATS &#187; Blog Archive &#187; Content Migration</title>
		<link>http://www.openroad.ca/2007/11/02/content-migration-the-iceberg-of-cms-projects/comment-page-1/#comment-12</link>
		<dc:creator>NetworkATS &#187; Blog Archive &#187; Content Migration</dc:creator>
		<pubDate>Thu, 15 Nov 2007 20:48:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.openroad.ca/if/then/2007/11/02/content-migration-the-iceberg-of-cms-projects/#comment-12</guid>
		<description>[...] I came across this terrific article about Content Migration.  The article is especially relevant for organizations implementing a Content Management System for the first time. [...]</description>
		<content:encoded><![CDATA[<p>[...] I came across this terrific article about Content Migration.  The article is especially relevant for organizations implementing a Content Management System for the first time. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Content Migration: the iceberg of CMS projects by software management &#187; Content Migration: the iceberg of CMS projects</title>
		<link>http://www.openroad.ca/2007/11/02/content-migration-the-iceberg-of-cms-projects/comment-page-1/#comment-11</link>
		<dc:creator>software management &#187; Content Migration: the iceberg of CMS projects</dc:creator>
		<pubDate>Sat, 03 Nov 2007 10:15:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.openroad.ca/if/then/2007/11/02/content-migration-the-iceberg-of-cms-projects/#comment-11</guid>
		<description>[...] ivanckw wrote an interesting post today onHere&#8217;s a quick excerptIt lies there just over the horizon and just below the surface of any Content Management System (CMS) implementation. It is the factor that is most often forgotten or ignored as the CMS build barrels toward launch. &#8230; [...]</description>
		<content:encoded><![CDATA[<p>[...] ivanckw wrote an interesting post today onHere&#8217;s a quick excerptIt lies there just over the horizon and just below the surface of any Content Management System (CMS) implementation. It is the factor that is most often forgotten or ignored as the CMS build barrels toward launch. &#8230; [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

