The Golden Moment

Short post time to set out a concept that I frequently talk about…

When a client chooses to contact a service system (#inbound) there is a good chance that they have prepared themselves for this moment1, such that they have:

  • A degree of time to talk, and the mindset to want to explore/ resolve/ move things forward;
  • secured themselves a suitable/ conducive environment in which to do this (e.g. a room with privacy); and
  • gathered (what they believe are) the necessary supporting information/ documents…or may have ready access to them.

Conversely, when a service system attempts to contact a client (#outbound), it is highly likely that we may find it difficult to get hold of them…and, if we are lucky enough to achieve a connection, very few (if any2) of the above conditions may be in place!

So what?

When a client chooses to connect3 with a service system, this is (what I refer to as) a Golden Moment. We should recognise the potential within and harvest it for every bit of (client) value that we can.

…which would include:

  • understanding the initial need (why the client is making contact);
  • discovering what’s going on (at a deeper level)
  • reflecting on what’s fundamentally needed, and what is/isn’t working
  • doing what’s required, including pivoting to alternative and/or additional paths in order to achieve the purpose of the service system.

It doesn’t matter if the contact takes a long time if value (as defined by the client) is being derived.

Just think of all the waste that is being avoided…

Such a philosophy will likely build trust between the client and those helping them – a hugely valuable state for a relationship to attain.

A common scenario

A client chooses to contact a service…and the system’s response4 is for a front-line worker to take down some information, and pass this on to somewhere else (via queues) …for another worker to then attempt to make contact with the client!!!

I often marvel at a ‘front office’ that can take a contact but can’t help and a ‘back office’ that can’t take a contact but could have helped! (ref. Front office – Back office)

Madness!

A likely riposte

“But Steve, we’d love to be able to take the time with inbound contacts, but we are just too busy to do so!”

…which leads to the question: ‘busy doing what?’

Perhaps, you are:

  • busy asking the client standardised questions and collecting (squeezing?) information into a form to pass on to somewhere else via a ‘task’ (#refer)
  • …busy managing those queues of tasks (ref. work prioritisation and allocation)
  • …busy ‘picking up a task’ and trying to understand what has been captured in that form – what it means, what is missing/ confusing, what needs clarifying
  • …busy trying to repeatedly contact those clients – including rescheduling the next attempt (#trythreetimes)
  • …(if you do connect), busy repeating the same conversation as at the start (only the situation has probably changed by now – and potentially got worse)
  • …(if you don’t connect) busy ‘closing off tasks’ as ‘unable to make contact’ (even though the need is highly likely to remain)
  • …busy adding copious notes throughout this stream of tasks (ref. Spaghetti notes phenomenon).

 

In short: Recognise and harvest every Golden Moment…which requires you to design your system to be able to do this.

Footnotes

0. I’ve chosen to use the word ‘client’ throughout this post, when I could have written the more generic ‘customer’, or more specific words like ‘patient’ etc. I made this choice because:

1. I know that I do. In fact, I’ve never chosen to attempt contact with a service without having some level of preparedness to make my attempt worthwhile!

2. Think of the client:

    • being at work, or driving a vehicle/ on public transport
    • with their children or caring for someone else
    • juggling various aspects of their life (cooking the family meal, doing the shopping, out walking the dog….)
    • …and on and on

All readers of this post will likely be able to recall when someone attempts to contact them and it’s very often highly inconvenient…and the contactor responds with “okay, so when shall I try again?”…and we think “er, I don’t know…’life’ is happening to me!”

3. This connection could be a call or face-to-face. Further, if we’ve provided them with an online front end (e.g. website or app), this could include enabling a 2-way interaction within (e.g. ‘choose to talk to a person’).

4. This response isn’t a case of ‘bad workers’ – it’s by design! (ref. the conventional thinking of centralise, specialise, and standardise).

2 thoughts on “The Golden Moment

  1. Couldn’t agree more.

    When we’ve studied service systems, the amount of waste associated with *outbound* calls to customer is unreal – from a really varied range of systems, we find that only approximately 50% of outbound calls are even answered.

    This typically involves a process flow that looks like…

    Identify client from list
    Open client record – read existing notes
    Phone client – fail to get an answer
    Record failed call in client record system
    Update list

    This achieves nothing – just burning capacity. If we absorb the variety of *inbound* calls, we can minimise it drastically.

    Like

  2. Agree, agree, agree.
    What surprises me, is surely IT can monitor the inbound queues and data analyse some models of when are the peak contact times, is it statistically similar over a day, week, month? If that knowledge is available, then how are the “customer centric” organisations not motivated to solve for it – i.e. put the right people on the phones at about the right time of the day/week/month? What is the other constraints that are stopping this “obvious” solution?
    I once looked at an area where the peak for inbound calls was 7am – 10am every Monday, and yet the organisation did not up-staff that shift. Why? Because the staff didn’t like that stressful shift, and they people leaders struggled to fill it, and also had to balance staff retention/keeping staff happy enough to stay over customer service. If I kept going, there’s another constraint after that, and another one after that.
    I’d propose that if the organisation was not committed to being 100% honest about all the associated constraints (and solving for them!), then “customer centricity” is only lip service and not worth more than the pixels on this comment.

    Like

Leave a comment