Last week, Tech Decisions For Insurance published a case study covering the use of Lombardi Teamworks at Xbridge, the UK’s leading online insurance and finance broker.  The article is very thorough, and covers some of the ways that BPM is helping Xbridge manage the tremendous growth that they have experienced since being founded in 2000.

In the article, you will be able to see how Xbridge has improved their processes to add value and efficiency to the business.  Specifically, CIO David Brakoniecki talks about how BPM has aided him in improving processes within Xbridge’s call center, and ultimately enables them to increase efficiency and consistency in customer service because they have much more visibility into their business. The full article can be found here.

You can read even more about what Xbridge is doing with BPM to weather the economic turmoil and maintain their market position here.

Do not be alarmed. This post is not an instruction manual on the finer points of BPMN. For those of you who wish to indulge, this should provide you with many hours of entertainment.

Rather, I want to reflect upon a few thoughts about process modeling, and share some practical hints.

And whilst Blueprint is my favorite modeling tool in existence, the following comments are equally applicable whether you’re using sticky notes, a white board, or the back of an envelope. (I’ve also seen bits of string used quite creatively!)

Process modeling is a process in itself. Therefore, like any other process, we can aim to improve its efficiency, effectiveness and flexibility. So instead of approaching modeling in an ad-hoc manner, how can we make it more repeatable, reduce the cycle time, raise quality and customer satisfaction?

To me, process modeling is fundamentally an exercise in communication. A model may be generated in order to share information between members of a project team about the way the process currently works. Or to share information between the project team and the stakeholders. Or with vendors. Or between a business expert and a business analyst. Or a business analyst and a developer. In all of these instances, the process modeling is not meant to be an end in itself, but a means to identify, verify, and inform interested parties about the way the process is, could or should be.

If we accept the model as an abstraction of reality, a visual representation of various process attributes, then the question arises not so much as to whether a process model is right or wrong, but, like a conversation between two people - is it effective or ineffective? Does it convey useful meaning to the intended audience, or not? A meaningful communication forms a sound basis for action - but a confusing, misleading or ambiguous one cannot be expected to yield a high quality outcome. Garbage in, garbage out.

How then, to create effective, clear, useful communication about a process?

Read the rest of this entry »

In today’s economic environment, it is as important as ever to be able to provide hard metrics as proof of a successful BPM project.  This is not to mention that in general, metrics are the icing on the cake when making a case for further, organization-wide process initiatives (and to executives in particular).  Today, I want to dive further into that topic and discuss some of the common metrics businesses use, as well as the tangibility issues inherent to each.  The more familiar you are with presenting the value of a BPM project, the more likely you will be able to get executive buy-in.

Efficiency - How quick can we get it done?

Reducing the cycle time on a process, whether it is a new hire process or loan origination, provides value.  You can quantify the amount of time it took before the project and quantify how long each cycle takes after the process improvements.  Efficiency has a high tangibility factor, it’s measurable, and therefore remains the strongest, or most useful selling point when trying to achieve buy-in from other units in the organization.

Read the rest of this entry »

Getting started with BPM makes many people nervous, and for good reason.  Change can bring uncertainty and fear - and hence often generates resistance.  In response to this type of internal skepticism and unrest, I frequently recommend conducting a 2×6 workshop when initially analyzing your processes to engage and excite the people who live the processes every day.

But before I tell how to run a 2×6 workshop, I would like to put it in context:

BPM is first and foremost a discipline to improve the efficiency, effectiveness and agility of a business, from a process viewpoint, to deliver real business value.  That being said, you have to do a certain amount of rewiring PEOPLE and your organization before you can start worrying about the software.

To really drive BPM in your organization, you need strategies in place to make the shift a bit easier for your workers to consume.  People don’t want change to be forced upon them.  But if you present them with an opportunity to help drive that change, then they can become fully invested as participants who help shape their own future.  So when you begin your initiative and need to take stock of where you are, you do some process analysis.  How do you get started?

Read the rest of this entry »