1 Comment
In my previous post, I introduced the potential benefits that membership organisations can obtain from looking at best practice service. The ‘Systems Thinking’ work carried out by John Seddon is one of the key contributions to moving organisations towards service excellence.
The fundamental Systems Thinking concepts Professor John Seddon defines for service organisations are demand, value and flow:
Examples of these are:
Although the examples above relate to phone calls, they could equally well be emails or enquiry forms on the website.
The first step is to understand the type and frequency of demand – why are people calling and how often?
Failure demand can often form 50% or higher of the contact volume. Where there is failure demand, the organisation needs to act to turn off the causes. This will have a direct impact on costs and ability to concentrate on the value demand.
For value demand, these are the interactions the organisation wants, so the business needs to be geared to responding to these demands.
To understand these, you need to observe what happens in practice ... and measure and analyse. It is important, as part of this, to understand whether the different types of demand are predictable or not, as you can only sensibly do something about the predictable demands.
Management roles should not be concentrating on aspects such as call duration statistics as (in the first two examples above) this can lead to the desire to minimise call duration to control costs, which very often results in reductions in service quality (and increases in cost). Instead, looking at the first two examples above, management should be ensuring that these enquiries can be handled efficiently, with the correct responses being delivered as promptly, accurately and fully as possible.
As a footnote, John Seddon presented on this at the UK Lean Conference 2009:
In my next post, I'll look at the key learning points for membership organisations from the Best Service work of Bill Price and David Jaffe.
There were three excellent presentations at yesterday's seminar Business Change in the Cloud, and an interesting question and answer session. Summary notes and the presentation slides are:
Comments
14 Apr 2011 13:35
John Seddon recently wrote about Agile in the Vanguard newsletter, it contained the statement
"I tell IT developer audiences 'agile' is doing the wrong thing faster":
"Oh, and the people in Whitehall think the IT will work this time because they will be doing ‘agile’. I tell IT developer audiences ‘agile’ is doing the wrong thing faster, and I get no dissent, in fact they laugh. If you want to see for yourself, watch my presentation to 1000 techies in Malmo last year"
----------------
I wrote to him to discuss this...
I agreed that this is true if you are talking about projects where the IT part is just implementing requirements for a bad business process. However, I think that is more to do with the way IT projects are initiated, rather than anything to do with "agile".
I'd like to think that agile and systems thinking are essentially trying to achieve the same goal. To deliver the most appropriate solution to the business in the most effective way and delivering value to the business as soon as possible.
Where some "agile" projects go wrong is they don't challenge the current process sufficiently, and as you say, end up building the wrong solution faster.
However, if systems thinking and agile projects are initiated correctly, and start off with the business objectives, look at how IT can support the incremental delivery of business change, then surely systems thinking is a driver for agile implementation of IT solutions. If this is the case, then "agile" done correctly is surely the best friend of systems thinking - and not the enemy?
... in response, he agreed!
replyPost new comment