<?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: Flow Project: GNER - Innovative booking engine, low risk project</title>
	<atom:link href="http://www.thinkflowinteractive.com/2007/11/10/flow-project-gner-innovative-booking-engine-low-risk-project/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thinkflowinteractive.com/2007/11/10/flow-project-gner-innovative-booking-engine-low-risk-project/</link>
	<description>News and ideas on user experience.</description>
	<lastBuildDate>Thu, 15 Sep 2011 15:36:34 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: murad</title>
		<link>http://www.thinkflowinteractive.com/2007/11/10/flow-project-gner-innovative-booking-engine-low-risk-project/comment-page-1/#comment-960</link>
		<dc:creator>murad</dc:creator>
		<pubDate>Sat, 16 Apr 2011 00:26:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkflowinteractive.com/2007/11/10/flow-project-gner-innovative-booking-engine-low-risk-project/#comment-960</guid>
		<description>Just a few usability questions for my own knowledge...

1) Why is the logo placed on the right. As i think its a standard practice nowadays to have it on the left. The only reason i could think of is to give more white space around booking. Or making it stand out. I still think the standard logo is on the left or center in rare cases.

2) Font to background contrasts are troubling. How did you find your tests against Old users and people with colour disability?

Wonder who designed http://www.nationalexpress.com/ it is the best and the simplest system out there along with LondonMidland.com</description>
		<content:encoded><![CDATA[<p>Just a few usability questions for my own knowledge...</p>
<p>1) Why is the logo placed on the right. As i think its a standard practice nowadays to have it on the left. The only reason i could think of is to give more white space around booking. Or making it stand out. I still think the standard logo is on the left or center in rare cases.</p>
<p>2) Font to background contrasts are troubling. How did you find your tests against Old users and people with colour disability?</p>
<p>Wonder who designed <a href="http://www.nationalexpress.com/" rel="nofollow">http://www.nationalexpress.com/</a> it is the best and the simplest system out there along with LondonMidland.com</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Flow Interactive :: The Think blog. &#187; Flow and National Express East Coast win the Information Technology Excellence of the Year Award</title>
		<link>http://www.thinkflowinteractive.com/2007/11/10/flow-project-gner-innovative-booking-engine-low-risk-project/comment-page-1/#comment-304</link>
		<dc:creator>Flow Interactive :: The Think blog. &#187; Flow and National Express East Coast win the Information Technology Excellence of the Year Award</dc:creator>
		<pubDate>Tue, 24 Feb 2009 16:54:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkflowinteractive.com/2007/11/10/flow-project-gner-innovative-booking-engine-low-risk-project/#comment-304</guid>
		<description>[...] just on National Express East Coast, but for any train in the UK.  We have blogged about the intuitive user interface and its cutting edge use of AJAX Technology as well as the positive customer feedback and improved [...]</description>
		<content:encoded><![CDATA[<p>[...] just on National Express East Coast, but for any train in the UK.  We have blogged about the intuitive user interface and its cutting edge use of AJAX Technology as well as the positive customer feedback and improved [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Flow Interactive :: The Think blog. &#187; National Express East Coast: 50% increase in conversion rate</title>
		<link>http://www.thinkflowinteractive.com/2007/11/10/flow-project-gner-innovative-booking-engine-low-risk-project/comment-page-1/#comment-251</link>
		<dc:creator>Flow Interactive :: The Think blog. &#187; National Express East Coast: 50% increase in conversion rate</dc:creator>
		<pubDate>Wed, 06 Aug 2008 12:09:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkflowinteractive.com/2007/11/10/flow-project-gner-innovative-booking-engine-low-risk-project/#comment-251</guid>
		<description>[...] Or you can read more about the design process that the team followed. [...]</description>
		<content:encoded><![CDATA[<p>[...] Or you can read more about the design process that the team followed. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: philbuk</title>
		<link>http://www.thinkflowinteractive.com/2007/11/10/flow-project-gner-innovative-booking-engine-low-risk-project/comment-page-1/#comment-188</link>
		<dc:creator>philbuk</dc:creator>
		<pubDate>Tue, 15 Apr 2008 12:55:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkflowinteractive.com/2007/11/10/flow-project-gner-innovative-booking-engine-low-risk-project/#comment-188</guid>
		<description>Thanks! Feedback helps to keep the National Express East Coast site growing and improving.

As with any new design, there are always things which can be improved, and it is our understanding that National Express, keen to provide the best possible user experience to customers, will be &quot;fine tuning&quot; the behaviour and performance of the system (back-end and front-end) over the course of the next 6-12 months.

Regarding error messages: Flow developed a standard approach and language for handling error messages. But the error messages are written and updated by National Express. So please let us know which ones you found confusing and we&#039;ll pass that information on to them. Mail them to phil at flow hyphen interactive.com, please.

Regarding speed: We agree, the service can sometimes be a bit slow.  It&#039;s a result of the connection to the 20+ year old National Rail database which supports the entire rail network - not just National Express.  We might have to resort to campaigning to get the whole national system upgraded!</description>
		<content:encoded><![CDATA[<p>Thanks! Feedback helps to keep the National Express East Coast site growing and improving.</p>
<p>As with any new design, there are always things which can be improved, and it is our understanding that National Express, keen to provide the best possible user experience to customers, will be "fine tuning" the behaviour and performance of the system (back-end and front-end) over the course of the next 6-12 months.</p>
<p>Regarding error messages: Flow developed a standard approach and language for handling error messages. But the error messages are written and updated by National Express. So please let us know which ones you found confusing and we'll pass that information on to them. Mail them to phil at flow hyphen interactive.com, please.</p>
<p>Regarding speed: We agree, the service can sometimes be a bit slow.  It's a result of the connection to the 20+ year old National Rail database which supports the entire rail network - not just National Express.  We might have to resort to campaigning to get the whole national system upgraded!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KP</title>
		<link>http://www.thinkflowinteractive.com/2007/11/10/flow-project-gner-innovative-booking-engine-low-risk-project/comment-page-1/#comment-187</link>
		<dc:creator>KP</dc:creator>
		<pubDate>Fri, 11 Apr 2008 16:02:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.thinkflowinteractive.com/2007/11/10/flow-project-gner-innovative-booking-engine-low-risk-project/#comment-187</guid>
		<description>Hey,

I like many features of the booking engine, but....

It works kind of slow... I&#039;m on a pretty fast connection.

I&#039;m also a bit confused on your error messages.</description>
		<content:encoded><![CDATA[<p>Hey,</p>
<p>I like many features of the booking engine, but....</p>
<p>It works kind of slow... I'm on a pretty fast connection.</p>
<p>I'm also a bit confused on your error messages.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

