Skip to main content

Developing a Distinct and Differentiated Experience Delivered through Employees to Define the Institution

Andrew McMillan used to work for John Lewis, where in 2000 he sent a report to the chairman saying that their customer experience wasn’t as good as it should be because it wasn’t consistent enough.  He was then put in charge of customer service and led the company to its current high reputation.   Nowadays he is a consultant on improving customer experience and he treated us to a high-level view of his philosophy.

Andrew has never given a training course on customer service because he argues that it is a matter of behaviour and ethos rather than training.  The institution has to value the service it gives; value the staff who give this service; and use these values to guide the institution’s recruitment, retention and reward policies.  He emphasised the point about valuing staff; if your staff do not feel valued, your customers will pick up this feeling themselves.

This presentation did not go into many details, focusing instead on the core ethos and illustrating this with several entertaining (and occasionally cheesy) video clips.  However, Andrew did make clear that the commitment to the customer experience has to be more than lip service.  If staff do not have sufficient training in the actual services on offer, if the services themselves are poor, if the support channels are unhelpful, nice words will be seen as the empty promises they are.

A good customer experience requires the actual product or service; the service channel (how easy are you to access?); clear processes (how easy are you to engage with?); and positive engagement (how did it feel?).  Leaders need to follow six steps to put this in place:  Define what you want; Measure what you deliver; Communicate the plan; Lead by example; Reward & recognise desired behaviours; Recruit and induct staff accordingly.

Although Andrew has recently worked with some universities, he didn’t attune his presentation much to the HE sector.  He did point out that the lessons could be applied either to the reputation of the university as a whole or to the reputation of the IT division within the larger institution.  One question from the audience asked how much scope middle management could have to drive such an initiative if it did not have active support from senior management.  Andrew replied that it is possible to instigate this sort of policy for your own section and that might inspire other parts of the institution but that this would be hard.

I was really enthused by this talk.  At the same time, once you look beyond the videos and adverts, it is clear that a proper commitment to customer experience is a mammoth undertaking.

Comments

Popular posts from this blog

Changing Principles

In EA, architecture principles set a framework for making architectural decisions.  They help to establish a common understanding across different groups of stakeholders, and provide guidance for portfolios and projects.  Michael Durso of the LSE gave a good introduction to the idea in a webinar last week for the UCISA EA community.

Many organisations take the TOGAF architecture principles as a starting point.  These are based on the four architectural domains of TOGAF: business, information/data, applications, technology/infrastructure.  These principles tend to describe what should be done, e.g. re-use applications, buy in software rather than build it, keep data secure.  See for example the principles adopted at Plymouth University and the University of Birmingham.

Recently though, I encountered a different way of looking at principles.  The user experience design community tend to focus more on how we should do things.  E.g. we should start with user needs, use iterative developm…

Why the UCISA Capability Model is useful

What do Universities do?

This may seem a strange question to ask and the answer may seem obvious.  Universities educate students and undertake research.  And perhaps they work with industrial partners and create spin-off companies of their worn.  And they may work with local communities, and affiliation bodies for certain degress, and they definitely report on their activities to government bodies such as HEFCE.  They provide student services and support.  The longeryou think about it, the more things you can think of that a University does.

In business, the things that an organisation does are called "capabilities", which is a slightly strange term.  I think it is linked to the HR idea of a combination of the CAPacity and ABILITY to do a task.  Whatever the name, it is a useful concept.  A capability is more basic than a process: a University may change the way it educates students but as long as it remains a University it will educate them one way or another.

A capability …

A new EA Repository

One of my goals since starting this job two years ago has always been to create a repository for architecture documents.  The idea is to have a central store where people can find information about the University's applications, data sources, business processes, and other architectural information.  This store will make it easier for us to explain our plans, to show the current state of the University's information systems, and to explain what Enterprise Architecture is all about.

It's taken a long time to reach this goal, mainly because we're often had more pressing and immediate work to be done.  The creation of a repository is one of those tasks that is very important but never quite urgent.  So I'm now very happy to say that we are in the process of deploying a repository and modelling tool.


This is the culmination of a careful process to select the most appropriate tool for our needs.  We began by organising several workshops to gather requirements from a rang…