Tag Archives: Implementation

How to transform the customer experience without a transformation programme

Welder

Make it better

In my last post, I described ten ways we can make the customer experience better.

Here they are again, framed from the customer’s point of view.

  1. You’re quick.
  2. You are easy to deal with.
  3. You get it right.
  4. You care if something isn’t right.
  5. You prove that I can trust you.
  6. You trust me.
  7. You are honest about what you can’t do.
  8. You act in my interests.
  9. You are professional.
  10. You are honourable.

*Sigh*

That’s a big list.

Let’s get real. We can’t fix everything.

But we do need to make things better.  Customers expect it. Our competitors are doing it.  We need to act quickly, sustainably and now.

And here’s the thing.  It costs very little to make each of these better. Without investing in technology. Without employing expensive consultants.

It just requires our attention.

Our people are already busy. They have to pay attention to the day job and to keep the lights on.  Most folk (and most organisations) can pay attention to no more than two or three things over and above this.

The trick is to choose the things to which we pay attention.

How?

Here is an approach I have found useful. I use it to make a difference quickly for customers. I find it especially helpful when I don’t want to wait for the promised new IT system to fix everything (which it can’t) or for the consultants to transform our processes for the better (which they don’t) or for the programme office to get its act together to deliver its big ‘transformation programme’ (which it won’t).

We talk to our customers. Better yet, we have our people (you know, the folk who actually do stuff for customers) talk to them.

We find out from our customers the things they would like us do better. We prompt them with questions drafted from the set above.  Keep the questions as open and simple as possible.  We’ll get a big list.

It’ll feel bad to see all the things we do badly for customers.

But that’s ok. Because now we can start to make things better.

We talk to our people who are responsible for the things that customers would like us to get better. Have them pick one or two or three things from the list.  No more than three.  Picking one or two is fine.

The criteria for they should use to pick out things from the list are these:

  • We can make it better.
  • We can make it better in ways that make a noticeable difference to the customer.
  • We can make it better within 30 days
  • We can make sure it stays better

Once they have made their choice,  we stand back and give our people license to do what they need to do. We help them when they need it, especially to remove sources of delay. Speed is the key, because we want to pay attention to this to make sure it gets better, and to keep paying attention is hard.

So: speed.

After thirty days, we (or better, the people doing the work) check back with customers about the difference they see.  We share this with everyone.

We test with our people that they can sustain the improvements they have made.  The only real test is this question:  if all our people changed jobs or moved on and were replaced, how do we know that our service would stay improved? If we can’t be sure, then let’s fix it so that we can be sure.

Go back to the list.  Ask customers again.

Repeat the next month. Pay attention to the new thing.

Repeat, repeat and repeat again.

Watch things get massively better for your customers. Let’s give it a go.

What I’m saying here is not original.  It’s just a version of continuous improvement, or Kaizen, or Agile or Lean.

Nor is it intellectually difficult.

And it won’t fix everything (so yes, sometimes, we do need that big IT system or a process redesign, but less often than we think).

But over (say) a year, it will make a huge difference.

And that’s what it’s all about.

So come on.  Let’s make things better for our customers.

(Image credit: USAF photo by Kurt Gibbons III) 

Advertisements

How to do customer experience: 3 ways to beat the grumps

Grump Street

Beware of the Grumps

When we want to change anything in an organisation, we will meet the Grumps. Grumps are colleagues who appear to support the project (and who may actually believe that they are acting in the project’s best interests) but whose presence is toxic to success.

The most telling sign that someone is a Grump is to note their effect on the energy of others.

If their presence adds to the energy of the team – if they are ‘radiators’* – then they are probably not Grumps.

If, however, their presence sucks the energy from the room – if they are ‘drains’ – we need to be careful.

How they speak is often a giveaway. Grumps are people on the ground who reveal themselves in meetings and emails and water-cooler conversations when they say things like:

“…I’m not saying this is a bad idea, but…”

“…We’ve tried this already and…”

“Let’s be realistic, here…”

“…we have to be careful not to throw the baby out with the bathwater…”

Or (as I have genuinely heard in more than one company):

“…we have to be careful not to trust customers too much…”

…and similar statements which have the facade of reason but really reflect fundamental antipathy.

Grump damage

Grumps slowly strangle customer experience projects.

They raise seemingly legitimate objections which are never about the intent of the project, always about the implementation.  Before long, the team is spending more time and energy managing concerns raised by Grumps and less in delivering the project.  Slowly, imperceptibly, Grumps force us to move our focus away from making things better for customers to trying to keep the Grumps happy.

And so the project fails – or more typically, fades away, as the effort needed to deliver something good gets brought down by the drag of managing the Grumps.

How to beat the Grumps

These three steps can help us beat the Grumps:

  1. Get them off the bus**  We don’t let a Grump be a member of our project team. It doesn’t matter how technically or managerially skilled they are, the drain on energy and time will not be worth it.  Much better to work with less-skilled colleagues who are radiators with the energy to succeed than let Grumps drain everyone’s momentum.
  2. Don’t give them a veto  It is a mistake to seek a buy-in from a Grump (or anyone else for that matter) unless their approval really matters to the success of the project.  For if they object, as a Grump will, we now either (a) divert resources and time to overcome their objections or (b) ignore their objections and go ahead, alienating them even more.  And if their approval is not needed, why did we seek it?  (Sigh: So many companies get this one wrong).
  3. Surround them with success  When we change to make things better for customers, the Grumps come last.  We begin by making the changes work with colleagues who are prepared to give them a go, ignoring the Grumps.  Once we have proven that the changes make a difference, then we make it work with the Grumps.  Grumps seek support for their belief that the project won’t succeed.  Proven success defuses such support.

Delivery de-Grumped

Good customer experience projects are all about leverage. They seek the places and strategies which yield maximum results in the fastest time. Grumps kill leverage, by forcing us to consider their objections instead of the customers, slow us down by distracting our attention and diverting our resources, and kill our projects by slowly sucking out our energy and momentum.

But if we can identify Grumps early and adopt the right practical strategies to prevent the damage they can cause, we remove one of the biggest barriers to customer experience project success.

Have you had the misfortune of working with Grumps?  What Grump warning signs have you seen? Let us know in the comments below.

*The idea of ‘Radiators’ and ‘Drains’ comes from Julian Fellowes in his book, Past Imperfect. I came across it cited in an article in Gretchen Rubin‘s blog, The Happiness Project.

**’Getting them off the bus’ is a CEO strategy recommended in Jim Collins’ excellent book, From Good to Great (p.56)

Image credit: David Stowell, licensed for reuse under the Creative Commons Attribution-ShareAlike 2.0 license.

Radiator image courtesy of Dan / FreeDigitalPhotos.net

Drain image courtesy of Winond / FreeDigitalPhotos.net