<?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"
	>
<channel>
	<title>Comments on: The Worst Website Design I Must Use Often: Southwest Airlines</title>
	<atom:link href="http://owstarr.com/2008/04/25/the-worst-website-design-i-must-use-often-southwest-airlines/feed/" rel="self" type="application/rss+xml" />
	<link>http://owstarr.com/2008/04/25/the-worst-website-design-i-must-use-often-southwest-airlines/</link>
	<description>Going Where No Blog Has Gone Before</description>
	<pubDate>Fri, 29 Aug 2008 21:16:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: admin</title>
		<link>http://owstarr.com/2008/04/25/the-worst-website-design-i-must-use-often-southwest-airlines/#comment-311</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Thu, 22 May 2008 07:42:17 +0000</pubDate>
		<guid isPermaLink="false">http://owstarr.com/2008/04/25/the-worst-website-design-i-must-use-often-southwest-airlines/#comment-311</guid>
		<description>Paula,

Hi.  I'm glad you wrote back.  Please understand that I like Southwest.  I fly your airline frequently, particularly between Los Angeles and San Francisco or Oakland and Los Angeles and Las Vegas.   

If I didn't use Southwest so often I probably wouldn't be so acutely aware of the deficiencies in the site design as it relates to buying a ticket online.  That said, I ALWAYS wonder what your developers were thinking when I use the site.

That's because there are so many problems with the purchasing process that I literally grit my teeth in frustration every time I use it.  This is especially true if I'm ever in a hurry and doubly true if I'm trying to complete a transaction using anything other than a full fledged computer (vs. Say an iPhone or Nokia N810 or N95 Smartphone).

First I have to ask, why doesn't Southwest let me store a profile so that I don't have to fill out every single field every single time?  I mean even if you didn't want the responsibility of storing credit card information you could still store my preferences including my name, address, phone number, etc.

You already have this information for all your frequent flyers anyway so why not make it possible to log into the site using your SWA FF# and have that automatically populate the rest of the data for us?  That in and of itself would probably save people five to ten minutes (and hair pulling frustration) each and every time they buy a ticket.

You could even let people choose to save their most frequently used routes so that logging in could instantiate some logic that lets a person choose the days of their flight and click "fly my regular route" and that would be enough to bring up the options available for the day the visitor specifies.

Choosing dates and times would lead to a second dialog. Payment.  If you're storing credit card information then a drop down dialog would allow the user to select which card he or she wished to use - a secondary confirmation such as requesting the CCV # from the card or the last 4 digits of the primary cardholder's social security # could be used.

This would be a vast improvement over the current workflow.

Even if there was some reason why Southwest didn't want to enable this sort of functionality (although I find it hard to imagine why not considering most other airlines do this), the current site could be dramatically improved.

First, yours is the only company I've ever encountered where the data in the dialog box requesting the credit card number persists when the user has the auto-fill feature enabled on Firefox.  In case you don't know what I mean, this feature automatically completes entries when the user enters the first digit or letter or uses the down arrow to see the full list.

The problem with your site is that most auto-fill information is not persistent, however the credit card number is.  This defeats most security for the users and makes Southwest look stupid since my email address has to be entered each time but my CC# is there for anyone's abuse.

What should happen is that with the exception of the CC# all the information should persist, especially if the user makes an error and has to back up a screen so that only the  field that needs to be corrected must be changed instead of forcing the user to re-enter all the data a second time and risk missing something else.

Also, it is ridiculous that some fields would cause the process to error out in the first place.  Who cares if my salutation is there or not?  (this is an exaggeration but you require some fields to be completed (such as whether my number is home or office) that are so totally trivial that it is mind-numbing that it is required at all, let alone that my transaction could fail for want of selecting such a radio button in the first place.

At any rate, I'm glad you've taken the time to consider my recommendations.  If you do decide to improve upon your current site I would be pleased to be considered for usability testing as it is probably obvious that I have given this issue some thought.

While I don't do site development myself, if you need a recommendation, I am well known in the Silicon Valley and Los Angeles technology communities and could make a recommendation if you need one.

Sincerely,

Oliver Starr, Editor
GTDtimes.com
And
OWStarr.com</description>
		<content:encoded><![CDATA[<p>Paula,</p>
<p>Hi.  I&#8217;m glad you wrote back.  Please understand that I like Southwest.  I fly your airline frequently, particularly between Los Angeles and San Francisco or Oakland and Los Angeles and Las Vegas.   </p>
<p>If I didn&#8217;t use Southwest so often I probably wouldn&#8217;t be so acutely aware of the deficiencies in the site design as it relates to buying a ticket online.  That said, I ALWAYS wonder what your developers were thinking when I use the site.</p>
<p>That&#8217;s because there are so many problems with the purchasing process that I literally grit my teeth in frustration every time I use it.  This is especially true if I&#8217;m ever in a hurry and doubly true if I&#8217;m trying to complete a transaction using anything other than a full fledged computer (vs. Say an iPhone or Nokia N810 or N95 Smartphone).</p>
<p>First I have to ask, why doesn&#8217;t Southwest let me store a profile so that I don&#8217;t have to fill out every single field every single time?  I mean even if you didn&#8217;t want the responsibility of storing credit card information you could still store my preferences including my name, address, phone number, etc.</p>
<p>You already have this information for all your frequent flyers anyway so why not make it possible to log into the site using your SWA FF# and have that automatically populate the rest of the data for us?  That in and of itself would probably save people five to ten minutes (and hair pulling frustration) each and every time they buy a ticket.</p>
<p>You could even let people choose to save their most frequently used routes so that logging in could instantiate some logic that lets a person choose the days of their flight and click &#8220;fly my regular route&#8221; and that would be enough to bring up the options available for the day the visitor specifies.</p>
<p>Choosing dates and times would lead to a second dialog. Payment.  If you&#8217;re storing credit card information then a drop down dialog would allow the user to select which card he or she wished to use - a secondary confirmation such as requesting the CCV # from the card or the last 4 digits of the primary cardholder&#8217;s social security # could be used.</p>
<p>This would be a vast improvement over the current workflow.</p>
<p>Even if there was some reason why Southwest didn&#8217;t want to enable this sort of functionality (although I find it hard to imagine why not considering most other airlines do this), the current site could be dramatically improved.</p>
<p>First, yours is the only company I&#8217;ve ever encountered where the data in the dialog box requesting the credit card number persists when the user has the auto-fill feature enabled on Firefox.  In case you don&#8217;t know what I mean, this feature automatically completes entries when the user enters the first digit or letter or uses the down arrow to see the full list.</p>
<p>The problem with your site is that most auto-fill information is not persistent, however the credit card number is.  This defeats most security for the users and makes Southwest look stupid since my email address has to be entered each time but my CC# is there for anyone&#8217;s abuse.</p>
<p>What should happen is that with the exception of the CC# all the information should persist, especially if the user makes an error and has to back up a screen so that only the  field that needs to be corrected must be changed instead of forcing the user to re-enter all the data a second time and risk missing something else.</p>
<p>Also, it is ridiculous that some fields would cause the process to error out in the first place.  Who cares if my salutation is there or not?  (this is an exaggeration but you require some fields to be completed (such as whether my number is home or office) that are so totally trivial that it is mind-numbing that it is required at all, let alone that my transaction could fail for want of selecting such a radio button in the first place.</p>
<p>At any rate, I&#8217;m glad you&#8217;ve taken the time to consider my recommendations.  If you do decide to improve upon your current site I would be pleased to be considered for usability testing as it is probably obvious that I have given this issue some thought.</p>
<p>While I don&#8217;t do site development myself, if you need a recommendation, I am well known in the Silicon Valley and Los Angeles technology communities and could make a recommendation if you need one.</p>
<p>Sincerely,</p>
<p>Oliver Starr, Editor<br />
GTDtimes.com<br />
And<br />
OWStarr.com</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paula Berg - Southwest Airlines</title>
		<link>http://owstarr.com/2008/04/25/the-worst-website-design-i-must-use-often-southwest-airlines/#comment-308</link>
		<dc:creator>Paula Berg - Southwest Airlines</dc:creator>
		<pubDate>Mon, 19 May 2008 19:05:27 +0000</pubDate>
		<guid isPermaLink="false">http://owstarr.com/2008/04/25/the-worst-website-design-i-must-use-often-southwest-airlines/#comment-308</guid>
		<description>Hey Oliver - Apologies for the delayed response.  I'm sorry to hear that our website is such a thorn in your side.  Of course, we want our website to be as easy to manage as possible, and you raise some legitimate concerns.  I'll touch base with some of our folks who may be able to address your specific concerns and get back to you.  In the meantime, feel free to email me if you'd like to discuss further.   

Paula Berg
Southwest Airlines</description>
		<content:encoded><![CDATA[<p>Hey Oliver - Apologies for the delayed response.  I&#8217;m sorry to hear that our website is such a thorn in your side.  Of course, we want our website to be as easy to manage as possible, and you raise some legitimate concerns.  I&#8217;ll touch base with some of our folks who may be able to address your specific concerns and get back to you.  In the meantime, feel free to email me if you&#8217;d like to discuss further.   </p>
<p>Paula Berg<br />
Southwest Airlines</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.359 seconds -->
