<?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/"
	>

<channel>
	<title>Promises of Progress &#187; backfired</title>
	<atom:link href="http://casper.warming.com/blog/tag/backfired/feed/" rel="self" type="application/rss+xml" />
	<link>http://casper.warming.com/blog</link>
	<description>Wits - or GTFO</description>
	<lastBuildDate>Wed, 19 May 2010 11:58:29 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Good Idea, Bad Execution, Still Fail</title>
		<link>http://casper.warming.com/blog/2008/10/03/good-idea-bad-execution/</link>
		<comments>http://casper.warming.com/blog/2008/10/03/good-idea-bad-execution/#comments</comments>
		<pubDate>Thu, 02 Oct 2008 22:45:49 +0000</pubDate>
		<dc:creator>casper</dc:creator>
				<category><![CDATA[Fail]]></category>
		<category><![CDATA[backfired]]></category>
		<category><![CDATA[sas]]></category>
		<category><![CDATA[time]]></category>
		<category><![CDATA[waste]]></category>

		<guid isPermaLink="false">http://casper.warming.com/blog/?p=23</guid>
		<description><![CDATA[When travelling by air, I prefer to fly with SAS. The tickets are typically a bit more expensive, but the service level is good (and pretty consistent). A couple of days ago, I received a mailinglist newsletter from SAS, asking me to participate in a questionaire with the title &#8220;what does time mean to you&#8221;. [...]]]></description>
			<content:encoded><![CDATA[<p>When travelling by air, I prefer to fly with <a href="http://www.flysas.com">SAS</a>. The tickets are typically a bit more expensive, but the service level is good (and pretty consistent).</p>
<p>A couple of days ago, I received a mailinglist newsletter from SAS, asking me to participate in a questionaire with the title &#8220;what does time mean to you&#8221;. Among other things, the survey showcased the various special benefits that SAS offers in order to reduce wasted time while travelling.</p>
<p><a href="http://casper.warming.com/blog/wp-content/uploads/2008/10/vindtiden_mail1.jpg"><img class="alignnone size-medium wp-image-25" title="vindtiden_mail1" src="http://casper.warming.com/blog/wp-content/uploads/2008/10/vindtiden_mail1.jpg" alt="" width="248" height="282" /></a></p>
<p>So I entered the site and began answering the questions. The only problem was that the server was so bogged down that it took more than a minute after you answered, before the next question would show up.</p>
<p><a href="http://casper.warming.com/blog/wp-content/uploads/2008/10/vindtiden2.jpg"><img class="alignnone size-medium wp-image-26" title="vindtiden2" src="http://casper.warming.com/blog/wp-content/uploads/2008/10/vindtiden2.jpg" alt="" width="300" height="205" /></a></p>
<p>&#8220;What a waste of time&#8221;, I thought &#8211; and dug up the e-mail address of the VP of marketing in SAS Denmark.</p>
<p>The next day, I got the response from SAS that they certainly did not intend to waste their customers time. Excuses (&#8220;we did actually do a load test&#8221;) and promises of fixing the issue took up the biggest part of the email.</p>
<p>I just checked &#8211; and the server is now responding pretty fast &#8211; as you would expect in the first place. The only problem is that the really busy people (that the campaign probably was directed towards) has long forgotten that site that didn&#8217;t work. The email is in deleted items. Their input is lost. You fail.</p>
<p>Once you have learned from your mistake you may try again.</p>
]]></content:encoded>
			<wfw:commentRss>http://casper.warming.com/blog/2008/10/03/good-idea-bad-execution/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
