Process People: We frequently hear from Lombardi that BPM has everything to do with organizational culture.  Can you give us one concrete example that you commonly see which demonstrates this cultural shift?

Wesley Chung: Yes, it’s very much a cultural thing, and I would say that a big part of that is trusting the [BPMS] system.  Many organizations still rely on old-fashioned, manual status reports to track the success of a process because they don’t have any other way to know that people are getting their work done.  A traditional status report provides a way for them to monitor that.  Without a product like Teamworks, there’s no way to efficiently and effectively monitor that people are accomplishing their tasks in-line with the business process.  It’s how things have always been done.  Ultimately, they need to be willing to trust the tool if they want to change how they manage a process. The other major cultural challenge is that managers have to learn new concepts and completely alter their methodologies for managing processes.

Process People: So what is one example of a cultural difference between managing processes manually and managing them with a product like Teamworks?

Wesley Chung: The difference is really about managing exceptions.  An exception is an instance where a process was not followed in the normal case, where someone in the organization didn’t do what they were supposed to do and the process did not turn out as expected.  Once managers see that the process team can provide them with some automated reports and the managers realize that they can trust the system, then they can start thinking about managing the exceptions instead of managing the processes that were carried out properly.

Read the rest of this entry »

We just wanted to check in and report on the first day of our annual Driven User Conference here in sunny Austin, TX.

The day began with CEO Rod Favaron’s keynote, which was all about how we are now at “the end of the beginning.” The secret is out about BPM, attention and visibility are soaring to new heights, and we are now entering a new phase of adoption and maturity.

A big part of this progression is the move from Project to Program to Culture, as Rod put it — in the early days of course it was all about getting your first BPM project up and running successfully, and then it became all about growing that project into a full-fledged program. But the next phase that Lombardi customers and partners are moving into right now is one in which BPM begins to truly impact the culture of any and every part of the organization that it touches, indeed the organization as a whole. This is the true value proposition of BPM ultimately — the idea that BPM becomes part of your DNA, that process becomes an integral part of what your company does every day.

Read the rest of this entry »

Recently we had the pleasure of announcing that the Finnish Sales Division of the Nordic and Baltic telecommunications service provider, TeliaSonera, is deploying Teamworks and Blueprint. The news was picked up by KMWorld.

This should be a very interesting deployment that we’ll review later after their initial playback and first round of results.

The company will use Lombardi to support sales of business services in Finland, as well as its activation and provisioning and other core business processes. We expect to be able to help them increase their service levels and improve customer satisfaction by designing and automating their business processes so they can be easily controlled and managed.

Read the rest of this entry »

Ed.: This is the first in a series of Q+A sessions focusing specifically on playback session best practices, with our in-house expert, Kris Komassa.

People like to talk a lot about collaboration between business and IT, but it seems like a playback session, as a collaborative, iterative process baked into the development environment, is where the wheel finally hits the road.

When you start any engagement, any project work, the existing tendency is for business and IT to split off fairly early, but I try to keep them in lock step as much as possible, which is important in order to be successful ultimately.

That first playback session is the first formalized opportunity to get everyone back in the same room and on the same page. We try to immediately do a level-set, making sure that everyone has the right expectations coming in, and a clear understanding what is going to be covered. We ensure that there is an agenda of what is going to be accomplished, both from a business and an IT perspective, and that both sides also know their roles and the various responsibilities for the playback.

Then once the playback starts, I’m really big on having an ongoing ad dynamic back-and-forth between business and IT, and typically at first it is driven by IT because they’ve been more hands-on to date in the first parts of the project. There are also instances, though, where the business side is driving because you’re doing more process flow at the first part of the first playback, which is important to note.

Read the rest of this entry »

Last week, the BPM industry - and two Lombardi customers - gained some very nice attention in the Financial Times. Steven S. Smith, CTO of Wells Fargo Financial, talked about how he achieved adoption from the business side of the company. Another, James Thomas, IT Director at University College London Hospitals (UCLH), discussed how they are using Lombardi Teamworks to reduce the time it takes for a patient to receive medical treatment after a referral. Impressive stuff.

But I think the really interesting thing here is that people can use this article to help evangelize the value that BPM can offer their companies in terms that business people can actually understand: efficiency, effectiveness and agility.

While BPM has been covered for some time in IT-oriented publications that dive deeper into the technology, this story is fairly unique in that it talks at a business-level about some of the biggest issues companies face with getting success with BPM. It provides examples of successful approaches that other companies took to solve meaningful problems while connecting with the business - and it comes from mainstream business press source - not an IT journal.

What it doesn’t do (too much at least) is get bogged down by technical points that make business people’s heads spin. And that is the problem with a lot of the press attention that BPM has received in the past. Many articles either get totally side-tracked with technical ‘in the weeds’ points or only discuss the broad market trends.

So the point I am making is that if you need help making the case for BPM with your executives, or if you need concrete examples of the benefits companies are acheiving, have them read the FT article - it should really help. And they probably won’t even make that funny face when they read it (you all know what I mean). Let me know how it goes!

Recently we sat down with Rachel Aukes, a member of the Wells Fargo Financial Information Systems Continuous Improvement Team. Rachel, who plays an active role in the use of BPM at Wells Fargo, shared how Wells Fargo got started with BPM. In February, Wells Fargo received the Global Award for Excellence in BPM and workflow.

Process People: Describe in as much detail as possible the problem or need on a project level that first made you consider BPM and/or Lombardi as a viable solution.

Rachel Aukes: Our BPM program came about as a solution to organizational level needs - in fact we selected our BPM solution (Teamworks) and began to implement it before deciding on a specific project. We were challenged with increasingly complex, paper-intensive processes that had a large number of manual steps and handoffs. That was obviously inefficient and meant there was room for errors (such as bad typing, misplaced files, etc.). The idea of what BPM offers became prevalent in 2006 when most of our development staff was focused on maintaining our legacy systems while building our future systems of record. This effort was strategically important to our company; however, the business had immediate tactical needs that must continue to be met. We asked ourselves what we should do to best support our business partners, and we determined that BPM was a good solution for this. We haven’t looked back.

Read the rest of this entry »

I’ve been seeing a bit of blog postings lately on the reality of SaaS on Demand or SaaS BPM.

Last week, Jason Stamper at CBR included some commentary on a beta product that he had heard about through the Process Factory. And couple of weeks ago, Jack van Hoof - who writes on SOA and EDA, posted a well thought-out blog entry about the marriage of BPM and SaaS, including the possibilities and the complexities at hand.

I love seeing this kind of dialogue on the Web because SaaS BPM is extremely popular with our customers right now. However, despite the aspiration of many developers, SaaS and BPM is NOT an easy combination. Nor is it likely that the two will ever be completely married in the traditional integrated form.

We launched Lombardi Blueprint a little over a year ago. It’s a SaaS-based modeling tool that integrates with Lombardi Teamworks, which operates behind the firewall. What worked so well in this case was that anyone in an organization could access the modeling tool to help shape a BPM project during the discovery stage. It doesn’t need to be integrated into legacy systems and it doesn’t require IT to deliver company data to the hosted model outside the firewall.

Read the rest of this entry »