<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:go='http://ns.gigaom.com/'
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>GigaOM &#187; Collaboration</title>
	<atom:link href="http://gigaom.com/collaboration/tag/usability/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com</link>
	<description></description>
	<lastBuildDate>Fri, 10 Feb 2012 05:04:12 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
<cloud domain='gigaom.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<image>
		<url>http://0.gravatar.com/blavatar/0db8f6557d022075dbbf010c54d46d93?s=96&#038;d=http%3A%2F%2Fs2.wp.com%2Fi%2Fbuttonw-com.png</url>
		<title>GigaOM &#187; Collaboration</title>
		<link>http://gigaom.com</link>
	</image>
	<atom:link rel="search" type="application/opensearchdescription+xml" href="http://gigaom.com/osd.xml" title="GigaOM" />
	<atom:link rel='hub' href='http://gigaom.com/?pushpress=hub'/>
		<item>
		<title>Trailhead: Inexpensive Heat Maps for Web Designers</title>
		<link>http://gigaom.com/collaboration/trailhead-inexpensive-heat-maps-for-web-designers/</link>
		<comments>http://gigaom.com/collaboration/trailhead-inexpensive-heat-maps-for-web-designers/#comments</comments>
		<pubDate>Mon, 26 Apr 2010 16:00:42 +0000</pubDate>
		<dc:creator>Charles Hamilton</dc:creator>
				<category><![CDATA[Apps]]></category>
		<category><![CDATA[heat map]]></category>
		<category><![CDATA[trailhead]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://webworkerdaily.com/?p=31677</guid>
		<description><![CDATA[Such eye-tracking research is not cheap, however. For teams who don't have the research budget to do full usability studies, Trailhead provides a way of creating limited heat maps inexpensively. Trailhead can't track users' eye movements, so it tracks mouse movements and mouse clicks instead.<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=gigaom.com&amp;blog=14960843&amp;post=31677&amp;subd=gigaom2&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p><a href="http://gigaom2.files.wordpress.com/2010/04/trailhead-logo.png"><img title="Trailhead-logo" src="http://gigaom2.files.wordpress.com/2010/04/trailhead-logo.png?w=210&#038;h=47" alt="" width="210" height="47" class=" alignleft"></a>In large web development projects, beta sites are generally put through usability tests to ensure that users can navigate them successfully, and that important areas of the site draw attention and click-thrus. Eye-tracking tests are often conducted to see what areas of the site are viewed. The results of such tests are often represented as  “<a href="http://en.wikipedia.org/wiki/Heat_map">heat maps</a>,” which provide   graphic representations of  the areas of a website that are most frequently looked at by visitors. The results of eye-tracking tests, as displayed on heat maps, can be used by web designers to make sure that important material is placed in attractive locations.</p>
<p>Such eye-tracking research is not cheap, however. For teams who don’t have the research budget to do full usability studies, <a href="http://www.trailheadapp.com/">Trailhead</a> provides a way of creating limited heat maps inexpensively: It offers one free test, and additional tests are $1-9 each, depending on how many one buys. Trailhead can’t track users’ eye movements, so it tracks mouse movements and mouse clicks instead, via a small piece of tracking code that is added to pages being tested.</p>
<p><a href="http://gigaom2.files.wordpress.com/2010/04/clicks.jpg"><img title="Trailhead heat map" src="http://gigaom2.files.wordpress.com/2010/04/clicks.jpg?w=204&#038;h=140" alt="" width="204" height="140" class=" alignleft"></a>Trailhead users can view the heat maps for each in-progress or completed test, and can make the maps public or private. For each page being tested, the resulting heat map  begins with a static representation of the design, over which trails of mouse movements, and triangles showing  mouse clicks are superimposed. One can turn  any of these layers on or off.</p>
<p>Not surprisingly, the web design layer doesn’t display moving elements, so one won’t see how visitors interact with interactive elements that change, like drop-down menus, scrolling DIVs, IFRAMEs, Flash movies, or slide shows like the one on the <a href="http://webworkerdaily.com/">WebWorkerDaily home page</a>. Trailhead  says that one can run tests on mobile sites, although I didn’t try this feature.</p>
<p><a href="http://gigaom2.files.wordpress.com/2010/04/new_test.jpg"><img title="Trailhead new_test" src="http://gigaom2.files.wordpress.com/2010/04/new_test.jpg?w=210&#038;h=131" alt="" width="210" height="131" class=" alignleft"></a>The folks at Trailhead let me run several tests, and I found creating them to be simple. One provides some basic information about the page to be tested, including its URL,  when the test should be started, and the page’s width in pixels (Trailhead can’t run tests on sites with variable widths). Trailhead then generates a tracking code to be included on the web page. <a href="http://gigaom2.files.wordpress.com/2010/04/dashboard_thumb.jpg"><img title="dashboard_thumb" src="http://gigaom2.files.wordpress.com/2010/04/dashboard_thumb.jpg?w=210&#038;h=58" alt="" width="210" height="58" class=" alignleft"></a>The test then appears in the user’s dashboard, which shows how much data has been collected so far. Since each test covers 1,000 user sessions, it may take hours or days to complete, depending on how much traffic the tested page receives.</p>
<p>A graphic designer colleague is skeptical of the usefulness of Trailhead’s heat maps. He points out that since Trailhead can’t collect data on how users’ eyes track web content, this tool would not be able to tell whether, for example,  the click-through rate on a banner is low because the content is  not interesting, or if it’s just  not being perceived by visitors. There is also no way of separating out the behavior of new visitors from that of those who’ve been to the site previously.</p>
<p>Trailhead won’t replace full usability testing, or even traditional visit statistics from <a href="http://www.google.com/analytics/">Google Analytics</a>, <a href="http://awstats.sourceforge.net/">AWStats</a>, and the like, but for those with limited budgets, it may provide insights that complement other research.</p>
<p><em>Do you find heat maps useful?</em></p>
<p><strong>Related GigaOM Pro content (sub. req.):</strong> <a href="http://pro.gigaom.com/2010/01/report-the-real-time-enterprise/?utm_source=collaboration&amp;utm_medium=editorial&amp;utm_campaign=intext&amp;utm_term=31677+trailhead-inexpensive-heat-maps-for-web-designers&amp;utm_content=hamiltonc">Report:  The Real-Time Enterprise</a></p>
<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=gigaom.com&amp;blog=14960843&amp;post=31677&amp;subd=gigaom2&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://gigaom.com/collaboration/trailhead-inexpensive-heat-maps-for-web-designers/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
	
		<media:thumbnail url="" />
		<media:content url="" medium="image" />

		<media:content url="http://0.gravatar.com/avatar/a6fb4c6db876cbe29b4780d195449c9f?s=96&#38;d=retro&#38;r=PG" medium="image">
			<media:title type="html">hamiltonc</media:title>
		</media:content>

		<media:content url="http://gigaom2.files.wordpress.com/2010/04/trailhead-logo.png?w=210" medium="image">
			<media:title type="html">Trailhead-logo</media:title>
		</media:content>

		<media:content url="http://gigaom2.files.wordpress.com/2010/04/clicks.jpg?w=204" medium="image">
			<media:title type="html">Trailhead heat map</media:title>
		</media:content>

		<media:content url="http://gigaom2.files.wordpress.com/2010/04/new_test.jpg?w=210" medium="image">
			<media:title type="html">Trailhead new_test</media:title>
		</media:content>

		<media:content url="http://gigaom2.files.wordpress.com/2010/04/dashboard_thumb.jpg?w=210" medium="image">
			<media:title type="html">dashboard_thumb</media:title>
		</media:content>
	</item>
		<item>
		<title>Watch Your Web Site Users With Clixpy</title>
		<link>http://gigaom.com/collaboration/watch-your-web-site-users-with-clixpy/</link>
		<comments>http://gigaom.com/collaboration/watch-your-web-site-users-with-clixpy/#comments</comments>
		<pubDate>Wed, 27 May 2009 18:00:08 +0000</pubDate>
		<dc:creator>Scott Blitstein</dc:creator>
				<category><![CDATA[NYT Enterprise]]></category>
		<category><![CDATA[Software Apps]]></category>
		<category><![CDATA[SYN Feature Enterprise]]></category>
		<category><![CDATA[analytics]]></category>
		<category><![CDATA[clixpy]]></category>
		<category><![CDATA[record]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://webworkerdaily.com/?p=13324</guid>
		<description><![CDATA[Do you ever want to peek over the shoulder of your web site visitors to see how they move about and navigate? As site owners, we often make assumptions as to how people are getting to particular pages or using particular functionality. Armed with pages and [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=gigaom.com&amp;blog=14960843&amp;post=13324&amp;subd=gigaom2&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
			<content:encoded><![CDATA[<p><img  title="clixspylogo" src="http://webworkerdaily.files.wordpress.com/2009/05/clixspylogo.png?w=120&#038;h=46" alt="clixspylogo" width="120" height="46" class=" alignleft" /></p>
<p>Do you ever want to peek over the shoulder of your web site visitors to see how they move about and navigate?   As site owners, we often make assumptions as to how people are getting to particular pages or using particular functionality.  Armed with pages and pages of analytics statistics we focus on what people are viewing or searching for.</p>
<p>Sometimes, though, there is no substitute for just watching how people interact and use your site to really understand your users&#8217; behavior.  Usability and testing tool <a title="Clixpy - Home" href="http://clixpy.com">Clixpy</a> hopes to make that possible.</p>
<p><span id="more-13324"></span></p>
<p>Clixpy is a web tool that tracks and records everything that a visitor does while interacting with your web site.  Every scroll, click, text entry and hover is captured in a video for you to view at a later time.</p>
<p>A convenient dashboard displays all of your captured videos.</p>
<p><img  title="Clixpy Dashboard" src="http://webworkerdaily.files.wordpress.com/2009/05/img_clixpy_dashboard.png?w=300&#038;h=203" alt="Clixpy Dashboard" width="300" height="203" class=" alignleft" /></p>
<p>Installation is fairly straightforward. A short piece of JavaScript is provided for you to place into the HTML of your site.  The code is tied to your account and is independent of a particular web site, which is nice.  This allows you to monitor multiple sites or pool your captures using just one account.</p>
<p>Clixpy captures are purchased in groups. Your first 100 captures cost $5, with discounts being available for larger buys.  You maintain a credit pool and each capture just pulls from your available credits.</p>
<p>You do have some control of how and when your captures are taken, though.  When turning on captures you are given the opportunity to set some parameters to limit how many or how long they will run.  This allows you to target particular times of day or new feature releases.</p>
<p>The Clixpy folks provided me with a pool of credits for review purposes and I doled them out over the course of a couple of days on one of my sites.  It really was informative to watch the recordings that Clixpy gathered.  Seeing real users clicking around is interesting and challenged some assumptions I had about how people interacted with my site.</p>
<p>Since each capture pulls a credit, I was sort of irritated when I would get single page view recordings.  My initial thinking was that these captures wouldn&#8217;t tell me much, but I now realize that careful examination of these sessions could help identify issues and offer insight as to how to make my site more &#8220;sticky&#8221; and reduce its bounce rate.</p>
<p>Clixpy generally works just as advertised but I did run into some issues. For example, a capture should include every page view by a user but I can clearly identify many instances in which the same user session is split among multiple Clixpy captures.  As each capture session has a cost, it would be nice to not have them wasted like this. There were also a couple of instances where it seemed that the clicking through of pages didn&#8217;t quite match up properly and the timing of the recording was inconsistent.</p>
<p>Also, while not a function of the application or service, one irksome thing I noticed is that you need to register on the site before you are given any information on cost.  Clear pricing information should always be provided before any user data is gathered or a sign-up is processed.</p>
<p>I also have some concerns about the privacy implications of Clixpy but, in general, it is just presenting the same type of information gathered by an analytics package in a visual format.  Password fields are ignored and other form fields can also be disabled.  For long-term usage I would be sure to include information in my own privacy policy alerting users that it is in place.  Users can opt out of being tracked by any site using Clixpy by visiting the Clixpy <a title="Clixpy - Disable Tracking" href="http://clixpy.com/disable">disable page</a>.</p>
<p>Clixpy isn&#8217;t a substitute for proper focus group or usability testing but a small investment could provide useful information that can be difficult to gather otherwise. Check out a <a title="Clixpy - Demo" href="http://clixpy.com/demo">demo</a> of Clixpy or <a title="Clixpy - Register" href="http://clixpy.com/signup">register</a> for an account to get started.</p>
<p><em>How do you feel about &#8220;spying&#8221; on your site visitors with Clixpy? </em></p>
<p><strong>Related research and analysis from GigaOM Pro:</strong><br />Subscriber content. <a href="http://pro.gigaom.com/?utm_source=collaboration&utm_medium=editorial&utm_campaign=auto3&utm_term=13324+watch-your-web-site-users-with-clixpy&utm_content=scottblitz">Sign up for a free trial</a>.</p><ul><li><a href="http://pro.gigaom.com/2011/03/why-ipad-2-will-lead-consumers-into-the-post-pc-era/?utm_source=collaboration&utm_medium=editorial&utm_campaign=auto3&utm_term=13324+watch-your-web-site-users-with-clixpy&utm_content=scottblitz">Why iPad 2 Will Lead Consumers Into the Post-PC&nbsp;Era</a></li><li><a href="http://pro.gigaom.com/2011/03/the-near-term-evolution-of-social-commerce/?utm_source=collaboration&utm_medium=editorial&utm_campaign=auto3&utm_term=13324+watch-your-web-site-users-with-clixpy&utm_content=scottblitz">The Near-Term Evolution of Social&nbsp;Commerce</a></li><li><a href="http://pro.gigaom.com/2011/02/content-farms-the-players-the-benefits-the-risks/?utm_source=collaboration&utm_medium=editorial&utm_campaign=auto3&utm_term=13324+watch-your-web-site-users-with-clixpy&utm_content=scottblitz">Content Farms: The Players, The Benefits, The&nbsp;Risks</a></li></ul><img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=gigaom.com&amp;blog=14960843&amp;post=13324&amp;subd=gigaom2&amp;ref=&amp;feed=1" width="1" height="1" />]]></content:encoded>
			<wfw:commentRss>http://gigaom.com/collaboration/watch-your-web-site-users-with-clixpy/feed/</wfw:commentRss>
		<slash:comments>17</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/916644ba552abe1d9794c3e8631d493d?s=96&#38;d=retro&#38;r=PG" medium="image">
			<media:title type="html">scottblitz</media:title>
		</media:content>

		<media:content url="http:///2009/05/clixspylogo.png" medium="image">
			<media:title type="html">clixspylogo</media:title>
		</media:content>

		<media:content url="http:///2009/05/img_clixpy_dashboard.png?w=300" medium="image">
			<media:title type="html">Clixpy Dashboard</media:title>
		</media:content>
	</item>
	</channel>
</rss>
