Enquiries: +44 (0)20 7692 4832

Agile Business Change Blog Thoughts on Agile Strategic Business Change and Agile Delivery

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:

  • Demand – what services the contacts want (what they are demanding). There are two types of demand:
    • Value demand – calls / contacts that are carried out to obtain the value a person wants from their relationship with the organisation (i.e. the services or advice)
    • Failure demand – contacts/calls that result from failures, for example a failure to provide information or support that was required to fulfil demand at first contact
  • Value – what the contact wants (value) from a particular conversation with the organisation – what matters to them, the services, products (including membership) and advice.
  • Flow – how the contact flows through the organisation to get to the objective (obtain the value).

Examples of these are:

Image of Freedom from Command and Control: Rethinking Management for Lean Service
  • Someone phoning for advice on an area of professional conduct:
    • Demand: wanting the advice
    • Value: the value to the contact is the advice (accuracy is important).
    • Flow: from the contact centre to the relevant department – the contact centre has to understand that the call needs some advice that the department can provide, transfer the call if possible, or create a request for the department to call the contact back.
  • Someone who wants to upgrade their membership level:
    • Demand: wanting to upgrade
    • Value: the higher level of membership
    • Flow: the contact centre would take the call, and transfer it to the Membership department, either immediately, or as a request for the Membership department to call back.
  • Someone calling to ask why the membership self service area of the website is not available (this is an example of failure demand):
    • Demand: why is the membership self service area of the website not available?
    • Value: information about when the website is back up, or if it is an urgent issue, to do what they wanted over the phone
    • Flow: the contact centre would take the call and provide the answer

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.

Comments

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!

reply

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.

More information about formatting options

By submitting this form, you accept the Mollom privacy policy.

WHAT WE'RE SAYING

21
MAY
Cookie Legislation and your Website

We have recently changed our website privacy policy to comply with the EU Directive that will be in force in the UK from 26th May.

However, a significant proportion of organisations haven't made the necessary updates including many Government websites according to the BBC.

ABOUT US OUR SERVICES INDUSTRY SECTORS WHAT WE'RE SAYING CONTACT
How We Work Our Philosophy Management Team Our Clients Agile Change Strategy Building Agile Capability Agile Programme Delivery Financial Services Government Media Not for Profit Retail Cookie Legislation and your We...Business Change in the CloudThe Importance of Business Agi...Agile Governance - ArticleHTML5 in the HeadlinesLikes Delayed TrainsWhat's in a Story (Part 2)?