Toby Cappello, Vice President of Professional Services | August 5th, 2008
If you’ve been reading the Process People blog, you might have noticed that we talk a lot about an iterative approach to deploying BPM. What we haven’t touched on as much is that the iterative approach is an element of the overarching methodology. Looking in on the methodology from the highest level you will get a view of a three-phased approach – which ultimately results in iteration. But we want to provide a big picture of how all of the different parts of our methodology tie together, and how each point of emphasis leads into or loops back to key areas of the other two phases.
I realize that in some organizations, “phase” is a four-letter word. With BPM it is a must… it is the foundational element that leads to continuous process improvement and ultimately maximum business benefit. But don’t just take our word for it, just look at the countless customers who have used this methodology and achieve enormous success because of it.
Definition Phase
The definition phase is probably the most critical portion of the entire BPM adoption lifecycle. This is where you set the expectations for the BPM project, define metrics to measure the project and create a framework so that the focus remains on delivering business value throughout all three phases.
In this phase organizations should:
- Take the broader initiative and narrow it to a specific departmental level
- Define the business milestones and associated metrics
- Develop the business case
- Ensure that there is a common thread throughout the whole project (Business value)
- Get the business to drive this phase
Read the rest of this entry »

In a previous post I said that it should go without saying that you have to showcase your initial BPM project if you want to drive adoption across the entire organization. I focused on metrics. Although other areas of the business might not understand the functional process implemented, they will find interest in how you are measuring the process for improvement. This can correlate to other areas of the business as well.
Today I want to address the folks out there who don’t feel comfortable showcasing their project because they don’t have the biggest ROI numbers yet. Maybe it has only been in production for a couple of weeks. What else can you focus on?
The Before and After
What did the process look like before the solution and how has it changed? Were there lots of manual hand-offs, faxes and emails? Did participants have to log onto four different systems just to review a work item? Was there inconsistency in the way people executed the process? How much time did managers spend building and running reports before status meetings? What does it look like now?
Read the rest of this entry »

Wayne Snell, Senior Director of Marketing | July 7th, 2008
In part one of this two-part Process People interview, we welcomed Raju Oak, head of process services at Kleinwort Benson in London. Raju is part of the transformation and systems services group within the company. Kleinwort Benson is a provider of banking and financial services to corporate and private clients in the UK and Channel Islands. In Part 2 we hear more about Raju’s key learnings from his BPM implementation.
Process People: How did Kleinwort Benson determine the metrics by which the company deems the project to be a success, both initially and on an on-going basi?
Raju Oak: It is important to note that our initial project was a pilot designed to first prove out the potential of the BPM approach. We faced several challenges during the pilot project that we had to negotiate along the way. Perhaps the biggest issue was that the pilot was being introduced through IT, and at that time IT did not have strong credibility with the business. At the same time the business did not recognize the connection between the challenges that it faced and the absence of a managed process infrastructure. We also had a strong skepticism about BPM within some parts of IT as well, based upon an earlier failed attempt to implement a workflow tool from another vendor as a point solution. There really was no experience of process engineering within the business. These challenges made it a complex and vulnerable project, with a long gestation, and its success depended upon strong leadership from the CTO.
Read the rest of this entry »

Showcasing the success of your initial BPM project is often times requested from other departments, but it’s also required to help drive adoption across the entire organization.
If showcasing your initial BPM deployment can help gain process adoption and ignite enthusiasm in other areas of the business, then you’ll get more and more value out of your overall BPM initiative. That being said, here is the first in a two part series of posts that will help you to showcase your BPM solution within your organization.
Get ‘em excited!
Everyone has had to sit in a presentation during their lunch break that seemed like a never-ending PowerPoint slide show. Now imagine watching someone explaining a process flow diagram that has no relevance to you. Then follow that with a “live” demonstration of someone clicking through a bunch of screens acting as a participant in the process that you didn’t get. Trust me, it can be very painful.
Read the rest of this entry »
Driven 2008 has come to a close, and we’re really thrilled with this year’s event. Many of the conference attendees stayed for the Lombardi golf tournament yesterday, which took place on the beautiful Fazio Canyons golf course at Barton Creek Resort and Spa. The weather was perfect and the golf was great.
On that note, I thought it might be timely to provide a quick recap of a session that Toby Cappello hosted on Wednesday. The session was called: “The Monday Morning Quarterback Discusses 10 Painful Lessons Learned.” Toby started things off with a golf analogy - one which he lived up to on the course yesterday!
The analogy went something like this: “BPM is like golf - you need to build muscle memory if you want to develop consistency and achieve success.”
In all honesty, I can’t really think of any other combinations of a technology (BPMS) and a discipline (BPM) that fits so perfectly with this analogy. It cuts to the core of Lombardi’s methodology. In fact, if you break it down even further you’ll see more uncanny parallels that help to visualize what exactly you’ll need to do to achieve success with BPM.
Read the rest of this entry »
