<?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: 3 Product Management lessons from Comcast&#8217;s new sign-in pages</title>
	<atom:link href="http://www.elezea.com/2009/12/3-product-management-lessons-comcast-sign-in-pages/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.elezea.com/2009/12/3-product-management-lessons-comcast-sign-in-pages/</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: JBMONCO</title>
		<link>http://www.elezea.com/2009/12/3-product-management-lessons-comcast-sign-in-pages/comment-page-1/#comment-48</link>
		<dc:creator>JBMONCO</dc:creator>
		<pubDate>Wed, 24 Feb 2010 14:14:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.elezea.com/?p=249#comment-48</guid>
		<description>To add insult to injury, comcast requires you to create and use an email address of xxx@comcast.net to use as your login to access your account information if you use their high speed internet service. Even if you use an entirely different service provider for email. A dumb corporate decision designed to alienate previously satisfied customers. http://jbmonco.wordpress.com/2010/02/07/comcast-customer-service-not/</description>
		<content:encoded><![CDATA[<p>To add insult to injury, comcast requires you to create and use an email address of <a href="mailto:xxx@comcast.net">xxx@comcast.net</a> to use as your login to access your account information if you use their high speed internet service. Even if you use an entirely different service provider for email. A dumb corporate decision designed to alienate previously satisfied customers. <a href="http://jbmonco.wordpress.com/2010/02/07/comcast-customer-service-not/" rel="nofollow">http://jbmonco.wordpress.com/2010/02/07/comcast-customer-service-not/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Twitted by RianVDM</title>
		<link>http://www.elezea.com/2009/12/3-product-management-lessons-comcast-sign-in-pages/comment-page-1/#comment-33</link>
		<dc:creator>Twitted by RianVDM</dc:creator>
		<pubDate>Mon, 14 Dec 2009 22:35:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.elezea.com/?p=249#comment-33</guid>
		<description>[...] This post was Twitted by RianVDM [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was Twitted by RianVDM [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://www.elezea.com/2009/12/3-product-management-lessons-comcast-sign-in-pages/comment-page-1/#comment-31</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Wed, 09 Dec 2009 13:25:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.elezea.com/?p=249#comment-31</guid>
		<description>Great article, Rian.

Let&#039;s hope the Comcast team is able to recover from this with an agile &quot;fail quickly&quot; approach.

Assuming they elected to have a send-receive cycle (to validate the email address) before allowing someone to enter the password, how long will it take them to refactor their implementation to do that with AJAX (or whatever) so that the user experience is seamless.  A week?  Six months?  If it is a week, then this isn&#039;t a big deal.  If it is months, then this is heinous.

Gopal - I love the &#039;lame duck release&#039; moniker.

Also - this is a great example of the importance of integration of UX and product management.  The screenshots remind me of the &quot;advanced&quot; prototypes that auto companies take to the test tracks before they are released.  Those prototypes have random body panels and weird paint patterns so that spy photos don&#039;t provide clues to the competition.  This sign-in process is like one of those prototypes showing up on the dealer&#039;s lot with a hodge podge of design elements.

Thanks again,
Scott @sehlhorst</description>
		<content:encoded><![CDATA[<p>Great article, Rian.</p>
<p>Let&#8217;s hope the Comcast team is able to recover from this with an agile &#8220;fail quickly&#8221; approach.</p>
<p>Assuming they elected to have a send-receive cycle (to validate the email address) before allowing someone to enter the password, how long will it take them to refactor their implementation to do that with AJAX (or whatever) so that the user experience is seamless.  A week?  Six months?  If it is a week, then this isn&#8217;t a big deal.  If it is months, then this is heinous.</p>
<p>Gopal &#8211; I love the &#8216;lame duck release&#8217; moniker.</p>
<p>Also &#8211; this is a great example of the importance of integration of UX and product management.  The screenshots remind me of the &#8220;advanced&#8221; prototypes that auto companies take to the test tracks before they are released.  Those prototypes have random body panels and weird paint patterns so that spy photos don&#8217;t provide clues to the competition.  This sign-in process is like one of those prototypes showing up on the dealer&#8217;s lot with a hodge podge of design elements.</p>
<p>Thanks again,<br />
Scott @sehlhorst</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rian</title>
		<link>http://www.elezea.com/2009/12/3-product-management-lessons-comcast-sign-in-pages/comment-page-1/#comment-29</link>
		<dc:creator>Rian</dc:creator>
		<pubDate>Mon, 07 Dec 2009 15:53:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.elezea.com/?p=249#comment-29</guid>
		<description>Thanks Gopal - I actually read your post this morning and RT&#039;d it!  I completely agree with your assessment and characterization of lame duck releases.</description>
		<content:encoded><![CDATA[<p>Thanks Gopal &#8211; I actually read your post this morning and RT&#8217;d it!  I completely agree with your assessment and characterization of lame duck releases.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gopal Shenoy</title>
		<link>http://www.elezea.com/2009/12/3-product-management-lessons-comcast-sign-in-pages/comment-page-1/#comment-28</link>
		<dc:creator>Gopal Shenoy</dc:creator>
		<pubDate>Mon, 07 Dec 2009 04:17:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.elezea.com/?p=249#comment-28</guid>
		<description>Great points. It just so happened that I blogged on this very same topic today - post about &quot;lame duck&quot; releases vs. well defined phased product releases. http://bit.ly/4EVguW

What you have described here is what I call a lame duck release. It is released before it is ready for prime time, very likely because someone internal promised his superiors some release date and hence what gets released is basically a pig with a lipstick on it.</description>
		<content:encoded><![CDATA[<p>Great points. It just so happened that I blogged on this very same topic today &#8211; post about &#8220;lame duck&#8221; releases vs. well defined phased product releases. <a href="http://bit.ly/4EVguW" rel="nofollow">http://bit.ly/4EVguW</a></p>
<p>What you have described here is what I call a lame duck release. It is released before it is ready for prime time, very likely because someone internal promised his superiors some release date and hence what gets released is basically a pig with a lipstick on it.</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:38:54 -->
