Seriously, I am so done reading long news articles on my tiny Sony Ericsson (C702) mobile phone screen. It just don’t do it for me. I like to use the phone in a good old fashioned way; Listen to it. (for emailing I choose my Blackberry).

Sweden’s largest morning newspaper Dagens Nyheter today announced the news about the ReadSpeaker service on their mobile website mobil.dn.se.

The ReadSpeaker services are well used among groups of people that have problem accessing text all over the world. Dagens Nyheter are now targeting the Speech Enabling service towards mobile users “on the run”.  Originally developed to be a tool for web content owners to increase the accessibility to the text content for people with reading handicaps, ReadSpeaker is now going more main stream. More and more people discover the advantages of letting web pages “speak for themselves”.   I use the ReadSpeaker services, when available on the website I am visiting, for example when preparing breakfast for my kids. It enables me to catch up with the latest news while doing other stuff. You should try it out yourself!

I often use Thalys to go from our Paris office to our management meetings in our Dutch office in Huis ter Heide. So far, apart from the train being much slower on the Belgian and Dutch side and the occasional delays, the service was good but not excellent.

Yesterday I was coming back on the train that leaves Rotterdam at 19h26 and is supposed to arrive in Paris at 22h35. Due to a power failure (that was known to Thalys since 18h), the train could not go to Paris and dropped us off at Breda. From there we took buses – that took 2 hours to arrive – that drove us to the Bruxelles train station. On the way, we had been promised that hotel rooms would be reserved for the 300 to 400 of us approximately. Upon arrival, we were dismayed that the not too experienced looking Thalys team told us that they were unable to find any rooms. The only plan B they had was to have us sleep in the standstill fully lit train at the station from 1 am to the first departure this morning at 6h45. I finally got to Paris at 8h10 so 9h35 late. When arriving in Paris, the local Thalys team seemed surprised about the whole situation…

I think this is a good example of all the wrong steps a company takes when it comes to one, if not the most important, part of the building blocks of an organization namely customer support.

Error #1 : the personnel on board Thalys was uninformed on what was really going on. Companies should ensure that the employees that are in direct contact with their customers should know as much as possible in real time. Is that so difficult in 2009?

Error #2 : it shows real fast when customer support hasn’t done its uttermost to help out. I just can’t believe that it is impossible to find a couple hundred rooms in a hotel rich city like Brussels.

Error #3 : it was obvious that no real contingency planning had been carried out. This seems really strange since you would imagine that this kind of incident must be planned for. There was little or no coordination between Thalys personnel and the staff at the different train stations involved. Customer support teams need to live and breathe these worst-case scenario plans so that the day they are needed actions run more or less smoothly.

Error #4 : not listening to your customers. One traveller told the Thalys staff at the Brussels station that in these difficult economic times there must have been a bus company that would have jumped on the opportunity of bringing us all to Paris and prove to Thalys that they could cope with these kind of emergencies. The Thalys staff just discarded that option without any explanation.

Error # 5 : not escalating the decision process. The somewhat junior staff at the Brussels station didn’t “call the boss”. That would have calmed down some of the travelers and could have perhaps brought about a more experienced view on how to find a reasonable solution (since staying in a standstill train for almost 6 hours is not an option).

Error #6 : not to give more than the damage is worth on paper. Thalys’s reimbursing policy is to give compensation of 20,50 or 100% in case of delays above 30, 60 or 120 minutes. Rules are nice to have, but in some extreme cases companies need to be much better than the rules. You need to build a memorable support experience where the customer really thinks that the company has gone way beyond its duty to solve the problem at hand.

I think that Thalys could have a look at how a company like Zappos goes about customer suppport. It’s not rocket science, it is about caring as much as possible for the human beings that buy your products and services and not treating them as a somewhat abstract vision of the customer.

The Gov2.0 Summit in is on its second and last day in a warm and quite sunny Washington DC. Weather is not of great importance though since the Summit is being held three stories below ground level at the Grand Hyatt Hotel. The event is fully booked and filled with interesting presentations and panels. Expressions like “Government as a platform”, “the cloud”, “Open up the data archives” and Tim O’Reilly’s favorite “Do things that matters” are frequently used. US Government officials as well as entrepreneurs explains how they work with social media components, citizen participation and data visualization together with geodata to provide better service for the citizens as well as creating tools for internal use. The area of accessibility has however not really been touched upon as of yet.

The rest of the day will be filled with talks about policies, security, transparency, healthcare and “.gov websites that work”.

On thing that was brought up on a number of occasions yesterday was the “Apps  for America 2: The data.gov challenge” managed by the Sunlight Foundation. A number of web applications were developed on top of the data from the data.gov website. The purpose of Data.gov is to increase public access to high value, machine readable datasets generated by the Executive Branch of the Federal Government and the purpose of the challenge was to see what creative developers might come up with. The result was a very interesting and some very useful apps. Great work and great initiative!

What also came out of this was that once again stress the importance for government websites to publish all information and data in machine readable formats (i.e. NOT PDF) to make data collection and mash-ups possible.