!Process Cafe Process Cafe

Showing posts with label workflow. Show all posts
Showing posts with label workflow. Show all posts

Simplify!

Albert Einstein during a lecture in Vienna in 1921
If I was to sum up the whole concept of process improvement in one word it would be 'Simplify'.

Too often today we get lost in the morass of detail and unnecessary detritus which detracts from the key fundamental of process design which is to keep things as straightforward as possible. After all it was the great Albert Einstein who said "Make everything as simple as possible, but not simpler." and by that I think he mean that the ideal approach to almost everything is to ensure that you have got the easiest, quickest, least complex solution to any problem that will actually solve the problem itself. That last phrase is actually critical and is often lost on people. it is very easy to make a simple solution which - when implemented- will not actually solve the problem (or - more particularly - will solve the problem in it's pure form but not in an adulterated form)

For example if I was trying to streamline an on-line ordering function the simplest it can be is to be able to buy something with 'one-click'. Our good friends at Amazon.com have mastered this level of simplicity but still there are sites around which make you go through several hoops to try and give them money. When I come across sites like that they generally don't end up received a purchase request from me. However even Amazon.com 'one-click' ordering does not work when you have 'non-standard' requests to make. These can include shipping to multiple addresses or requesting gift wrap options. This needs an alternate method of purchase. Yet again Amazon does have this purchase method included in their site. This is an example of making things as simple as they need to be but no simpler.

Recently I had cause to contact my bank to query a transaction on my account. Previously I could contact my branch directly and speak to a personal account manager who has been assigned to me. But recently the process has changed and I now contact a call centre who deal with the query. This works very well until I have a non-standard request. In this case I was asking for a refund on more than one bank charge. I was told that I couldn't request this over the phone. Despite the fact that I had answered four security questions prior to the discussion taking place they call centre employee said I would have to make a personal visit to the bank (my branch is 200 miles away) to speak to someone personally about this so they knew it was really me... I suggest this is a case where they have simplified the process BEYOND the state where it is useful.

I would imagine that if you were to think long and hard about processes you encounter on a daily basis you would find examples of both under- and over-simplification. Case in point would be a low-cost airline I have used recently who pride themselves on having the lowest fares. They was they achieve this is twofold - 1) They get the passengers to do as much of the work as possible and 2) they charge for everything they can that is not included in the ticket price. As far as getting the passengers to do as much of the work as possible is concerned, the upshot it that their processes are somewhat confused - as evidenced by the following example:

I had one bag and a set of golf clubs. The bag had been paid for as part of the check in (an additional charge over and above the original ticket price), but the golf clubs had not. The process was as follows:

* Queue up
* Give details to check-in lady
* Show passport
* Check one bag in
* Take second bag (golf clubs) round to another desk
* Queue up
* Give details to second check-in lady
* Pay for second bag
* Receive confirmation slip/receipt
* Take second bag (golf clubs) back to first desk.
* Queue up
* Give confirmation slip/receipt to first check-in lady
* Receive boarding card
* Take clubs to a third check-in area
* Show boarding card to guard behind glass screen
* Drop clubs on conveyer belt - hope they get treated well and arrive at destination.

16 steps including three queue's to check in one bag, one set of clubs and receive a boarding card. Multiply this by 180 people on a plane (although not all of them will have additional charges to pay) and pretty soon you can see the issue with the complexity of this particular process. Compare this with a similar flight I took to the US a couple of years ago:

  • Queue up
  • Hand passport to check-in lady
  • Put bags on belt
  • Select 'Aisle' or 'window'
  • Receive boarding pass
  • Drop clubs on an oversized baggage belt nearby

As you can see this was significantly less hassle and more efficient. Of course looking at this from the airline's point of view there is no efficiency to be gained by changing the process. There is no financial gain to them, merely improvement in their customer service. However the airline have made it perfectly clear that their priority is extracting the maximum amount of revenue from each customer rather than providing a quick and efficient service to them. Therefore a change to the check in procedure would not benefit them at all.

Have a look around your organisation or workplace. Identify where you have overly complex processes. Would they benefit from becoming simpler?

Reblog this post [with Zemanta]

Ryanair's process issues.

The passenger cabin of a Boeing 737-7H4 (N495W...Image via Wikipedia

A couple of months ago over on the 'Flying Cafe' blog, I wrote a post about what I considered to be a misleading airline ticket pricing strategy. The airline - Ryanair - had advertised a 'free flight' which ultimately could have cost me as much as £105 including taxes and the 'additional charges' they levy.

This follows a discussion on the Linked-In Business Process Group where Steve Towers was positing that Ryanair's business model had improved as a result of a proposal to remove check-in desks at the airport. He called this the removal of a 'Moment of Truth' in the process. I argued against this saying that Ryanair may have a cost saving business model (although their profit percentage has decreased steadily over the last 3 years despite rapidly increasing revenue), but as a model for creating satisfied customers it leaves a lot to be desired.

Well this week I actually took the flight and I wanted to post a few thoughts on some of the process issues I picked up whilst flying with them.

I checked in at Bournemouth Airport for a flight to Southern Spain. I had one bag and a set of golf clubs. The bag had been paid for as part of the check in (an additional charge over and above the original ticket price), but the golf clubs had not. The process was as follows:

* Queue up
* Give details to check-in lady
* Show passport
* Check one bag in
* Take second bag (golf clubs) round to another desk
* Queue up
* Give details to second check-in lady
* Pay for second bag
* Receive confirmation slip/receipt
* Take second bag (golf clubs) back to first desk.
* Queue up
* Give confirmation slip/receipt to first check-in lady
* Receive boarding card
* Take clubs to a third check-in area
* Show boarding card to guard behind glass screen
* Drop clubs on conveyer belt - hope they get treated well and arrive at destination.


16 steps including three queue's to check in one bag, one set of clubs and receive a boarding card. Multiply this by 180 people on a plane (although not all of them will have additional charges to pay) and pretty soon you can see the issue with this particular process. Compare this with a similar flight I took to the US a couple of years ago:

  • Queue up
  • Hand passport to check-in lady
  • Put bags on belt
  • Select 'Aisle' or 'window'
  • Receive boarding pass
  • Drop clubs on an oversized baggage belt nearby

As you can see this was significantly less hassle and more efficient.

Of course looking at this from Ryanair's point of view there is no efficiency to be gained by changing the process. There is no financial gain to them, merely improvement in their customer service. However Ryanair have made it perfectly clear that their priority is extracting the maximum amount of revenue from each customer rather than providing a peaceful and efficient service to them. Therefore a change to the check in procedure would not benefit them at all.

If you would like to see my overall thoughts on 'The Ryanair Experience' then click here.

For those of you who know about these things, is this similar to the modus operandi of Southwest Airlines or do they tend to go more for customer service as well as cheap fares?

The Hole in the system

MRP vs. ERP — Manufacturing management systems...Image via Wikipedia

One of the things that people are very prone to do with processes is to leave some sort of a 'hole' in the system.

I was reading one of the multitude of blogs I read daily when I came upon an excellent post from Havi Brooks at The Fluent Self. In this post Havi was talking about 'The hole in the system'.

Basically, she explains, most people define 'systems' around themselves but leave some sort of a hole in there which causes problems later on.

Specifically she gives 3 examples:

1) "The baby-bathwater thing": Which is where systems are in place but are subverted because of some emergency situation
2) "The misguided assumption thing": Which is where systems are bypassed based on assumptions that would not have been made had the system been followed
3) "The 'not allowing for stuff going wrong' thing". Where systems only account for the ideal situation to occur and are not designed to cope with occurrences where things don't happen as designed.

What struck me about the post (and the three examples quoted) is that they are pretty universal - especially when applied to business processes. When I look at processes in place in business today they tend to be designed from the point of view of 'this is what should happen' rather than 'this is what can happen' it's a subtle difference, but very important.

There are, of course, whole industries that have sprung up to deal with the different scenarios detailed above - things like decision management systems for example. But am I the only one who thinks that it might be a good idea to design your systems correctly in the first place? How many times have people fallen into the trap of designing a business process - for example - to match a specific piece of software functionality but then suffered when that software can't cope with a customer who comes in with an emergency (The 'baby-bathwater thing')? It happens all too often. This is not to denigrate business decisons systems at all, but merely to look at specific probems through a different prism.

I am a firm believer that processes should be designed to be tool independent. That way when you change your underlying ERP or CRM system (for example) you don't actually need to redesign your processes. Havi says:

It seems to me as though most challenges that tend to come up in these situations have two sources.

Maybe the system is flawed. There’s a spot where things get stuck, jammed, or fall through and get lost. Or a great system is already in place, but we’re just not using it. Which is the flaw.

Fundamentally Havi is speaking of the two bugbears that dog any system's implementation: Putting in a system that works but isn't used correctly or putting in a system that doesn't work correctly.

So how do we solve these two problems?

I would say we don't.

Or, more particularly, we can't. It is fundamental in human nature that we seek the easiest solution. Generally the easiest solution is that which needs the least amount of work, or that which produces the ideal result the quickest. This can be the kind of thinking that produces systems that don't work correctly. Alternatively we can spend time, money and effort in creating virtually foolproof systems only to then have the users bypass these systems when an 'emergency' arises. But let's also look at the opposite side of that equation. How many time have you rung the bank, or some other 'call centre' system and asked them to do something only to be told that 'the system won't let us do that'? This is an example of a system that has been designed to work in one way but which we now want to subvert by not following the process. The well designed system has had safeguards built in that will not allow you to do anything like this. But at the end of the day you end up as a dissatisified customer. So is the system working correctly?

Yes it is. It is working absolutely as designed. But is it working in the best way for the customer?

I don't think so.

Perhaps the solution is to make systems more flexible? Maybe we need to try and ensure that users can perform the tasks they wish (regardless of what those tasks are) and then manage the fall-out using something such as decisions or rules based systems. But somehow I can't help feeling that this is tantamount to creating another 'hole in the system'

Thanks to Havi for the original post.



Process improvement in the National Health Service

Those of you who have seen Michael Moore's film "Sicko" will, no doubt, have a rather rose-tinted view of the UK's National Health Service (NHS)

Yes. It's true, when you have a baby the government pays you to have it in a hospital. And yes it's true that you can walk in off the street without any form of health insurance and be admitted. And yes it's true that no matter what medication they put you on your prescription cost is limited to about £8 ($16).

But there is a downside to that, and I noticed it at a recent trip to 'The Blood Bank'

Following Mr Sean Bean in his UK adverts I decided to "Do something amazing. Give Blood" (Actually, full disclosure here: I decided to accompany a friend who was doing something amazing. I was the designated driver). It gave me an excellent opportunity to check out some of the process issue the NHS have (For more thoughts - of a non-process nature - around the NHS check out The Musing Cafe)

For those of you who have never given blood before here is the proposed workflow

  • Arrive and show documentation
  • Complete a separate questionnaire and take a processing number
  • Have form reviewed and answer ancillary questions
  • Give blood
  • Have Tea and Biscuits
  • Leave.

So far so good, right?

Well, lets' go through the reality of that process and see if we can identify a few failings - either in the process itself or tin the implementation of the process.

As a scene setter let me say that the blood donation centre was a hall in a local community building with a single entrance and exit. The room was nominally divided into a waiting area, a processing area, an area with 10 beds to get the blood and a place for your tea and biscuits. (For those of you outside the US, Google "Hancock" + "Blood donor" for classic comedy about this very situation)

Arrive and show documentation. Ideally this should be a quick and easy step. You show the documentation, there is a review of the content to identify if you are in the right place at the right time. If so, proceed. If not, exception process. However the people dealing with this were on the same side of the desk as the people coming in through the door, thus creating a bottleneck. In addition the administrators were also the same ones updating the computers (As a separate step...) and retrieving the completed questionnaire forms. Result: Slow processing and queues

Complete a separate questionnaire and take a processing number: To be fair the completion of the questionnaire was well handled. They had enough pens and everyone got a clipboard with some advice about the questions. Filling it in was easy enough (Tick either 'yes' or 'no' in the boxes) but then you had to go back to the same queue as before to hand the forms in. The same guy was now dealing with new arrivals and completed forms whilst standing on the same side of the table as everyone else causing a blockage at the door. Once dealt with, you received a processing number which was added to you form. The form was then dropped into a processing pile.

Have form reviewed and answer ancillary questions: There were three 'booths' in the corner where the forms were processed. In each booth was a uniformed nurse who came out, took a document from the pile, called the number and took you in for 'processing'. This consisted of checking blood type with a pin-prick sample and asking any clarifying questions about answers on the form (My friend, for example had answered 'No' to the question 'Have you taken any medication in the last 7 days', forgetting totally about the fact that she's asthmatic and is on an inhaler. This part of the process worked really well, with the exception that the forms (while apparently being taken from the form in a numerical sequence) were actually taken somewhat randomly causing my friend to miss her turn. Obviously a process flaw in the organisation of the filing system,

Give Blood: This, in theory, should have been the easiest part. Lie down, get a needle stuck in your arm. Wait for 10 minutes. In fact it did work almost that slickly. We had a venepuncturist called Leslie who was very adept and very experienced. There was minimal fuss and everything went smoothly. However, once the blood had been collected there was a call for 'Bag Check' where a third party had to come from some other part of the room and check that everything was alright with the plasma. Again this should work quite well, but with 10 beds in use and only 1 or 2 qualified checkers, it didn't quite go as slickly as required.

Have Tea and Biscuits: The far corner of the room was set out with a small table and some chairs where an old lady served steaming hot tea from a boiler and you helped yourself to biscuits. Very civilised. However once you had finished you had to pick your way back through the beds, the waiting area and the processing desk to get out. Good process, bad execution.

Lessons learned: Overall the process was reasonably slick. There were one or two small gaps (such as the filing system for forms waiting to be processed), but the main issue was with the layout of the room. Having reviewed the layout while waiting (I was in there 1 hour and 15 minutes) I believe that a few simple changes would have sped things up.

  • Have the form processes seated behind the desk to allow more folks into the room at once
  • Have two people dealing with forms - one for initial review and another for completed questionnaires
  • Either invite fewer people to give blood at a time OR add an extra person to the processing (75 minutes for a 10 minute blood giving session as too much)
  • Create a processing channel around the room that kept the people and the documents flowing in a single direction - Reception -> processing -> blood giving -> tea and biscuits -> Exit

I would be interested in thoughts and feedback from other folks who've been through this process. If they use those special mobile blood gathering units is the process any better?

Some great posts from the Enterprise Decision Management Blog


I ran across the links below at the EDMBLOG where they had posted a link to 10 of the most popular stories and entries they made during 2007.

Some of these are really good and I recommend you check out the EDMBLOG whenever you can. If you don't have it on your RSS feed, you should!

  1. Business Intelligence 2.0 and Enterprise Decision Management
  2. Why are business rules better than traditional code?
  3. Windows Workflow Foundation - rule engines and rule management
  4. The secret of business user rule maintenance
  5. Customer Segmentation to increase profits
  6. Business Rules, Business Decisions, Intelligent Processes, Enterprise Decision Management
  7. Book Review: Competing on Analytics (the only book review to make the top 10, though Execution. The Discipline of Getting Things Done came close)
  8. What's the difference between Business Rules Management Systems and Business Rules Engines?
  9. Different Perspectives
  10. Using decisioning to build the bank of the future