<?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: How can IT reduce Firefox adoption/retention barriers?</title>
	<atom:link href="http://blog.mozilla.com/mrz/2009/03/24/how-can-it-can-reduce-firefox-adoptionretention-barriers/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mozilla.com/mrz/2009/03/24/how-can-it-can-reduce-firefox-adoptionretention-barriers/</link>
	<description>noise from a mozilla IT/Operations wrangler</description>
	<lastBuildDate>Wed, 04 Nov 2009 05:27:35 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: rdoherty</title>
		<link>http://blog.mozilla.com/mrz/2009/03/24/how-can-it-can-reduce-firefox-adoptionretention-barriers/comment-page-1/#comment-96177</link>
		<dc:creator>rdoherty</dc:creator>
		<pubDate>Mon, 30 Mar 2009 20:39:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/mrz/?p=435#comment-96177</guid>
		<description>I&#039;m all for making our websites faster, I&#039;ve been working on it for AMO and other sites. Big sites like Amazon and Google see purchases and searches (respectively) go down when latency or page load times increase.</description>
		<content:encoded><![CDATA[<p>I&#8217;m all for making our websites faster, I&#8217;ve been working on it for AMO and other sites. Big sites like Amazon and Google see purchases and searches (respectively) go down when latency or page load times increase.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kkovash</title>
		<link>http://blog.mozilla.com/mrz/2009/03/24/how-can-it-can-reduce-firefox-adoptionretention-barriers/comment-page-1/#comment-95186</link>
		<dc:creator>kkovash</dc:creator>
		<pubDate>Tue, 24 Mar 2009 22:05:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/mrz/?p=435#comment-95186</guid>
		<description>Here&#039;s a suggestion...

It looks like most of your questions are page/site specific.  Why don&#039;t we just ask people directly on those pages/sites?  There are unobtrusive survey tools, such as Kampyle (www.kampyle.com, we&#039;re using their &quot;software&quot; service for our installer survey), and then there are more comprehensive site feedback services such as 4Q (http://4q.iperceptions.com/).

It seems like asking people for feedback at the very moment they&#039;re on a page/site in question should be far more productive than leveraging the uninstall survey (or other methods casting a wide net).</description>
		<content:encoded><![CDATA[<p>Here&#8217;s a suggestion&#8230;</p>
<p>It looks like most of your questions are page/site specific.  Why don&#8217;t we just ask people directly on those pages/sites?  There are unobtrusive survey tools, such as Kampyle (www.kampyle.com, we&#8217;re using their &#8220;software&#8221; service for our installer survey), and then there are more comprehensive site feedback services such as 4Q (<a href="http://4q.iperceptions.com/)" rel="nofollow">http://4q.iperceptions.com/)</a>.</p>
<p>It seems like asking people for feedback at the very moment they&#8217;re on a page/site in question should be far more productive than leveraging the uninstall survey (or other methods casting a wide net).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sethb</title>
		<link>http://blog.mozilla.com/mrz/2009/03/24/how-can-it-can-reduce-firefox-adoptionretention-barriers/comment-page-1/#comment-95183</link>
		<dc:creator>sethb</dc:creator>
		<pubDate>Tue, 24 Mar 2009 18:49:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/mrz/?p=435#comment-95183</guid>
		<description>another thing to consider:  what is the target sample for this survey?  

if you were to only serve this to those who went through the uninstall survey, you would likely have skewed results due to an unhappiness factor.  on the flip side, if you sent this to our locales (even the smallest ones), you&#039;d likely have a sample of more happy users.  

i think you want to start in geographies where you think Mozilla infrastructure investment will help them.  then, consider offering to a sample that gets all three sets of users:  happy firefox users, unhappy users who uninstalled, and users surfing our sites for support (i.e. not unhappy, but also looking for help because something is going wrong).

maybe you can offer the survey in three ways:  
1)  specialized builds to locales of interest
2)  uninstall survey
3)  pop-up survey to those surfing SUMO or AMO</description>
		<content:encoded><![CDATA[<p>another thing to consider:  what is the target sample for this survey?  </p>
<p>if you were to only serve this to those who went through the uninstall survey, you would likely have skewed results due to an unhappiness factor.  on the flip side, if you sent this to our locales (even the smallest ones), you&#8217;d likely have a sample of more happy users.  </p>
<p>i think you want to start in geographies where you think Mozilla infrastructure investment will help them.  then, consider offering to a sample that gets all three sets of users:  happy firefox users, unhappy users who uninstalled, and users surfing our sites for support (i.e. not unhappy, but also looking for help because something is going wrong).</p>
<p>maybe you can offer the survey in three ways:<br />
1)  specialized builds to locales of interest<br />
2)  uninstall survey<br />
3)  pop-up survey to those surfing SUMO or AMO</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sethb</title>
		<link>http://blog.mozilla.com/mrz/2009/03/24/how-can-it-can-reduce-firefox-adoptionretention-barriers/comment-page-1/#comment-95181</link>
		<dc:creator>sethb</dc:creator>
		<pubDate>Tue, 24 Mar 2009 18:16:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/mrz/?p=435#comment-95181</guid>
		<description>I think you should convert the four topics above into four questions with a scale of responses that can be tested with some commonly used statistical tests. Your users can assess their experiences by rating each topic that&#039;s interesting to you.

Here is how I would phrase each, with a scale of 1-5 where 1 is very poor and 5 is very good

1.  Please rate the Web page load time for the following Mozilla web properties/pages (if you&#039;d like to click on the links now to test, please do so and give us your rating)
--  www.mozilla.com/www.mozilla.org
--planet.mozilla.org
--bugzilla.mozilla.org
--developer.mozilla.org--labs.mozilla.com

2.  Mozilla&#039;s Firefox Support is located at http://support.mozill.com  Please tell us about your experience by rating the following
--  ease of finding support you need 
--  speed in receiving support 

3.  Mozilla&#039;s addons.mozilla.org Website is an interactive Website that provides users thousands of browser add-ons to customize their browsing experience.  
--Please rate the speed of the interactivity of the site.

4.  Add-ons that customize your browsing experience are updated through the Add-ons manager in your Firefox (link to a screen shot for reference?)
--  Please rate your experience with the performance (i.e speed) of the Add-on Manager

===================

With each of these questions created with a scale of responses, you will be able to get a sense of how your users rate performance of each element you are testing.  

You can ask a demographic question at the end (or set of questions) to assess who is taking the survey.  

Finally, it would be most helpful to make sure you have a way to collect where the surveys are being taken.  It goes without saying, but this information gathered above  is helpful, but for your purposes, it would be useless if you couldn&#039;t map it directly to a geographic location so you can then propose what can be done to improved the experience.</description>
		<content:encoded><![CDATA[<p>I think you should convert the four topics above into four questions with a scale of responses that can be tested with some commonly used statistical tests. Your users can assess their experiences by rating each topic that&#8217;s interesting to you.</p>
<p>Here is how I would phrase each, with a scale of 1-5 where 1 is very poor and 5 is very good</p>
<p>1.  Please rate the Web page load time for the following Mozilla web properties/pages (if you&#8217;d like to click on the links now to test, please do so and give us your rating)<br />
&#8211;  <a href="http://www.mozilla.com/www.mozilla.org" rel="nofollow">http://www.mozilla.com/www.mozilla.org</a><br />
&#8211;planet.mozilla.org<br />
&#8211;bugzilla.mozilla.org<br />
&#8211;developer.mozilla.org&#8211;labs.mozilla.com</p>
<p>2.  Mozilla&#8217;s Firefox Support is located at <a href="http://support.mozill.com" rel="nofollow">http://support.mozill.com</a>  Please tell us about your experience by rating the following<br />
&#8211;  ease of finding support you need<br />
&#8211;  speed in receiving support </p>
<p>3.  Mozilla&#8217;s addons.mozilla.org Website is an interactive Website that provides users thousands of browser add-ons to customize their browsing experience.<br />
&#8211;Please rate the speed of the interactivity of the site.</p>
<p>4.  Add-ons that customize your browsing experience are updated through the Add-ons manager in your Firefox (link to a screen shot for reference?)<br />
&#8211;  Please rate your experience with the performance (i.e speed) of the Add-on Manager</p>
<p>===================</p>
<p>With each of these questions created with a scale of responses, you will be able to get a sense of how your users rate performance of each element you are testing.  </p>
<p>You can ask a demographic question at the end (or set of questions) to assess who is taking the survey.  </p>
<p>Finally, it would be most helpful to make sure you have a way to collect where the surveys are being taken.  It goes without saying, but this information gathered above  is helpful, but for your purposes, it would be useless if you couldn&#8217;t map it directly to a geographic location so you can then propose what can be done to improved the experience.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
