<?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: The dangers of &#8220;test and learn&#8221;</title>
	<atom:link href="http://www.elezea.com/2009/08/dangers-test-learn/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.elezea.com/2009/08/dangers-test-learn/</link>
	<description>A webcolumn on design &#38; technology</description>
	<lastBuildDate>Thu, 02 Feb 2012 14:20:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Designing for permanence</title>
		<link>http://www.elezea.com/2009/08/dangers-test-learn/comment-page-1/#comment-629</link>
		<dc:creator>Designing for permanence</dc:creator>
		<pubDate>Sun, 02 Oct 2011 18:28:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.elezea.com/?p=3#comment-629</guid>
		<description>[...] live in an environment where most web design is seen as variable. With A/B testing, Minimum Viable Products, and the prevalence of Content Management Systems, nothing is set in [...]</description>
		<content:encoded><![CDATA[<p>[...] live in an environment where most web design is seen as variable. With A/B testing, Minimum Viable Products, and the prevalence of Content Management Systems, nothing is set in [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Software development and product management: Part 1 (Overview)</title>
		<link>http://www.elezea.com/2009/08/dangers-test-learn/comment-page-1/#comment-85</link>
		<dc:creator>Software development and product management: Part 1 (Overview)</dc:creator>
		<pubDate>Tue, 17 Aug 2010 07:12:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.elezea.com/?p=3#comment-85</guid>
		<description>[...] QA, release, assess. After the thrill of releasing, the assessment phase is extremely important and often overlooked. It is important to define your measures of success upfront, and then follow up to see if you&#8217;ve met those goals. How do users respond to the product? Are we meeting revenue/engagement goals? What can we learn from how users interact with the product to give us ideas for new products? I&#8217;m also an advocate for using the same four sources of input we discussed earlier (market research, user experience research, site analytics, and customer support), as opposed to relying on only one methodology, like a 3-week A/B test. More on the dangers of that in one of my earlier posts. [...]</description>
		<content:encoded><![CDATA[<p>[...] QA, release, assess. After the thrill of releasing, the assessment phase is extremely important and often overlooked. It is important to define your measures of success upfront, and then follow up to see if you&#8217;ve met those goals. How do users respond to the product? Are we meeting revenue/engagement goals? What can we learn from how users interact with the product to give us ideas for new products? I&#8217;m also an advocate for using the same four sources of input we discussed earlier (market research, user experience research, site analytics, and customer support), as opposed to relying on only one methodology, like a 3-week A/B test. More on the dangers of that in one of my earlier posts. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced
Content Delivery Network via Amazon Web Services: CloudFront: cdn.elezea.com

Served from: www.elezea.com @ 2012-02-05 12:30:58 -->
