Too busy driving to ask why we’re going
Stepping on to the bus in Birmingham, I encounter a scene I had more expected to find whilst travelling than at home: a lady is asking, in quite clear English, how she can contact lost property, as she has lost her bag. The driver stares at her blankly, clearly not understanding a word. It seems there is no hope until eventually the lady realises he is Polish: she starts speaking Czech and the matter is swiftly resolved.
I’m all in favour of a free and open labour market (anybody who thinks that being British gives them the automatic right to a job should be deported to India), but it might be fair to expect a bus driver to have a certain level of basic proficiency in the native language of the country in which he works. And yet he has been given the job. Why? Because the company that employs him does not consider customer service to be an important part of his role.
As anyone familiar with British public transport will testify, this is well-known and deeply engrained in the culture of these organisations. But I think that many hi-tech firms are guilty of the same sin. Just like the bus driver’s job is to drive, the programmer’s job is to program.
Tackling customer problems effectively is a challenging task that should surely be the focus of everyone in the organisation, not just those in customer-facing roles. Some take this idea further by by forcing the hackers out of their cave: employing the programming team to answer technical support queries, thus making the programmers share the users’ pain. I think this is an excellent idea, which promises to make real improvements to the usability of computer systems. Of course, it changes the job specification to have a much heavier emphasis on effective communication - but perhaps that’s not such a bad thing?
Comments(0)