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 »

By Rod Favaron, CEO Lombardi

I get asked about market consolidation all the time. Customers, prospects, industry analysts and investment bankers want to know how companies like Lombardi can continue to thrive in the face of the relentless consolidation drive by IBM, Oracle and SAP. The answer is simple: innovation. Markets always consolidate. That very fact creates opportunity for the companies that are able to innovate. Consolidation and innovation actually feed each other. How?

Let’s look at consolidation. How does it benefit the end customer of software? The promises are many: better integration, comprehensive functionality, simpler management and streamlined procurement. That last point - streamlined procurement - may be the only promise delivered to date.

In a recent article in CIO Magazine, Martin Veitch commented - “IBM and Oracle seem to be in a race to build up the world’s largest miscellany of enterprise software programs,” and “customers continue to have faith until the next procurement round. However, a lot of people are unimpressed by the levels of integration and R&D that follow the incessant deal-making.” Within Lombardi’s own Business Process Management market, Oracle’s acquisition of BEA and the resulting announcement of a combined BPM strategy got similarly low marks from industry observers.

The end result is that customers wait many years - and still do not get products that can solve their immediate problems. They get roadmaps for rationalization and consolidation. They get long lists of product lines and product names. Take Oracle as an example. They announced the Fusion roadmap in 2005. At that time, oil was $50 a barrel and the housing and banking sectors were clicking along at historic levels. The world market has changed dramatically since then, but Oracle is still trying to deliver the original Fusion roadmap. And now, that roadmap is muddled again by the BEA acquisition.

Read the rest of this entry »

When your organization’s products are intangible, like an investment CD or a retirement plan, it’s sometimes difficult to identify waste or inefficiencies in your business.  Today I want to discuss some of the unique attributes of financial services organizations and how to look at these businesses through the prism of process to find problems that are often overlooked.

Financial services often tend to think of themselves as very different from other types of organizations.  For example, many firms have organically grown along the lines of “functional silos” based on different types of product, reinforced by separate IT applications supporting these product categories. Yet, every organization shares similar horizontal functions such as human resources, finance or accounting.  These functions alone offer more than enough opportunity for delivering business value through a BPM initiative.  But, I promise there’s more!

Financial services companies are generally very IT-intensive, and open to new technology and approaches to problem solving.  However, it can be difficult for these organizations to determine which solutions fit their needs the best - or even which problems to address - since their products are not tangible like a car or any product that you can hold in your hand.  If you can’t see your product, it can be difficult to see your problems like “defects” and “waste”.

Furthermore, regulatory monitoring & reporting requirements such as Sarbanes Oxley and Basel 2 have weighed heavily on this industry. Combined with global economic factors such as the credit crunch, there’s huge pressure on financial services companies to increase visibility, transparency and controls whilst reducing costs and simultaneously improving customer service.

In steps BPM…

Read the rest of this entry »

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 »

The Lombardi User Experience Team is looking for customers to help us make our products even better. We have several new features under development for both our Blueprint and Teamworks products, and we’d like to know what you think. The UX team focuses on how people interact with our software, and the information we collect is translated directly in to product design improvements - so your feedback really makes a difference!

Please contact us if you are a current Blueprint or Teamworks customer and are willing to participate in a product usability study. Most sessions last between 30 and 60 minutes and can be done remotely using Web conferencing software. During the sessions, you will be shown aspects of the product and asked to provide feedback. Your comments are valuable ways we ensure we’re building tools that fit your needs.

So far on this blog we’ve had a lot of important conversations around getting started — the first 180 days, putting your BPM team together, that first playback, etc. Today I want to focus a little bit more on the optimization piece of the puzzle. What do I mean by optimization? Imagine that you’re already effectively using BPMS and you’re doing pretty well all in all, but you’re not seeing the kinds of fireworks that you did when you got that first process up and running. The question is, essentially, what are some the of the advanced topics that that come to mind in terms of things that companies can do that really optimize and take process excellence to the next level? This will continue to be a theme for me in subsequent blog posts, but I’ll share some initial high level thoughts as well as a few best practices here.

I’ll begin with where I come in as part of our Services group. It often starts with a happy customer telling us that they are slowly starting to stall. That is, they got through those first multiple iterations, but now the question is — where do we go from here, how do we know whether we should add on another process or move to an area that is totally separate?

From an optimization perspective, we are going to go in and do a review and an assessment of what the customer has, what they are doing, and what kind of returns they are seeing. For example, is this process more customer-impacting, is it employee-impacting, and most importantly are we really understanding what the true value proposition is for each?  We decide how and where we want to focus, and determine whether we are doing a good job of tying into strategic objectives within the organization. Ultimately, optimization is all about alignment and realignment, that’s the first take-away.

Read the rest of this entry »

As noted in Dave’s Summer release post and recent product reviews, Blueprint has undergone some pretty significant UI changes in the past few months. It’s especially important to mention that the majority of these improvements are the direct result of our customer’s feedback and feature requests found in the Blueprint Community Forums. If you are an existing customer and haven’t had a chance to check out the forums yet, I invite you to do so (just click the Feedback link in the upper right-hand corner of Blueprint). There’s a wealth of information there, from tips and tricks to modeling best practices. It’s also a great way to interact directly with the Blueprint product and support teams.

A perfect example of this direct customer feedback is our new rich text editing environment found on the documentation view in Blueprint. For those of you who have been using the product for a while, you may remember that our first pass at rich text was a bit limiting - allowing users to apply simple formatting such as bold, italic or underline styles. To be honest, we weren’t entirely sure how our customers were going to use the documentation sections of the product or the types of information they’d want to store there. So we put it out there, watched, and listened to the feedback. And boy did we get a lot of feedback - in fact we quickly found that the documentation section was considered one of the most important sections of the product. Over the course of a few releases, the text editing sections evolved to support things like advanced formatting, custom font styles, lists, indenting, hyperlinks, images, and colors. We also heard from customers that they needed better integration with their existing documentation, so we included support for things like copying from Word, direct export and printing.

We’re obviously not done yet. We have big plans for improving the existing doc features and adding a few new ones (check out the forums for a few hints). We’re also looking for more feedback from you. We’re 100% committed to making Blueprint THE BEST process discovery and modeling tool available. Tell us what you need… We’re listening!

The best description of “executive level buy-in” that I know of is only 7 letters long:

F-U-N-D-I-N-G

Maybe that doesn’t help you as much as you had hoped, so I’ll provide some additional color around this one.  Funding is the absolute bottom-line when we talk about executive buy-in to a BPM initiative.  But funding has to reflect the iterative approach, which means that the project isn’t over when the process is deployed.  The project is really just getting started.

Funding has to map back to the methodology required to do the project right.  It has to reflect all three phases of a proper BPM methodology.  We’ve discussed this methodology on Process People before, and if you haven’t seen some of those posts, I recommend that you read one first!

In reality, executive buy-in also means you have to have an executive who’s willing to get up on a podium and endorse the process improvement program organization-wide.  It means that the executive has to be willing to commit funding in every manner necessary - money, people, time and so on.

Read the rest of this entry »

Scott Francis from BP-3 recently posted a great, objective review of the Blueprint Summer ‘08 release. He does a thorough and insightful job covering the entire product. For example, here’s his take on the Visio import functionality we recently introduced:

Visio importing has long been the “holy grail” for process modeling tools.  If I had a dollar for every time someone asked me if a particular BPM product could import Visio models directly I would be rich!  However, Visio import into a process execution environment isn’t always all its cracked up to be.  Visio diagrams tend to be quite unstructured, whereas BPMN is very structured, and executable BPMN is even more structured in form.  Moreover, Visio models don’t have enough information attached to them to be immediately executable.  It is possible to run into issues of “who owns this model” once you import the Visio (the business may have the expectation that they can keep making modifications and “reimport” into Teamworks, for example).  At some point, the implementors must take over the model and own it to produce something executable.  I’ve been working on some models for OMG certification and I thought they would be a fun (albeit simple) set of examples to import into Blueprint for a test drive.  Blueprint imports these easily and accurately.  I went back to the archives and tried importing some really awful process diagrams circa 2004.  The results weren’t pretty (the original wasn’t pretty), but Blueprint imported the models nicely (a visio diagram with 10 tabs and one process per tab).  Going to the Diagram View I was able to sort out the diagram into swimlanes and go from there.  Interestingly, when I imported a diagram WITH swimlanes defined, Blueprint created those swimlanes and participants for me.

But my favorite quote had to be:

I actually like the diagramming portion better than Teamworks!  And collaborating on the same process isn’t just possible, its actually cool.  You almost look for an excuse to try to be logged into the same process at the same time so you can try to step on each other.  Blueprint handles all the conflicting edits really well.  I’m impressed!

We’re very proud of Blueprint’s collaboration and diagramming capabilities as well because we believe that there’s no tool that’s easier to use or can make you more productive, online or off.

Take a look at Scott’s full review when you get a chance.

I’ve had a surprisingly difficult time conveying my own definition of “Iterative Development” in the past, so I thought I’d take a stab at explanation via analogy. Let’s compare your Business Process to a trip from Austin, Texas to El Paso, Texas.

The most important aspect of my trip is arriving at my destination.  No matter what interesting things may happen on the way, if I don’t end up in El Paso, my trip has failed.

The same is true about your Business Process.  No matter what else goes on, there is an objective to your process and you have to accomplish that objective.

Read the rest of this entry »

Today I’m proud to announce the availability of the Summer ‘08 Update release of Blueprint! One of the great benefits of delivering Blueprint in SaaS model is that we’re able to stay nimble and quickly add functionality that improves the value of the product for everyone. So following shortly on the heels of our main Summer ‘08 release, we’ve added features to address some of the most common requests we hear from our customers.

Let’s take a look at them in detail:

• Microsoft Word Export: Blueprint now gives you the ability to automatically generate a Microsoft Word document containing all the details of your process. This is a great way to communicate your process to stakeholders that don’t have a Blueprint account. For example, we’ve been using this feature internally to generate “specifications” for our processes when we need to interact with outside vendors.

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 »

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 »

Ross Mayfield noted today that one of the biggest challenges with collaboration among distributed teams is actually agreeing on who is actually part of the team. Larry Irons quotes research from Distributed Work to that effect:

Of the twenty-four teams surveyed, not a single team was in complete agreement on its boundary: who was and who was not a member of the team. In fact, the average level of agreement within the sample was only 75 percent, such that any given team member was likely to disagree with the rest of his or her team on one-quarter of potential team members. 

We see this all the time in real world BPM projects. Agreeing on what the process is is often the easy part. Identifying the who is can seem nearly impossible, especially if a single team is attempting to define a process that is executed in many different locales all over the world.

A distributed, collaborative environment such as Lombardi Blueprint is key to solving this challenge. Having a structured repository to identify and maintain the players and relationships involved in a business process promotes visibility and knowledge sharing among those involved. Discovering the who in a process becomes far easier when all those that are involved can both document their own role and see how where they fit inside the grand scheme of things regardless of what office or time zone they happen to be working in at the particular moment.

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 »

We frequently get asked about the design process here at Lombardi. First off, it’s helpful to understand a little bit about our team, which consists of folks with very diverse backgrounds in user interface and visual design, human factors and engineering. Having such a broad mix of skills enables us to come at a design problem from many different angles and explore a variety of options very quickly. We practice an iterative approach that includes rapid prototyping and end user testing. Sometimes our solutions may seem obvious – but they are usually the result of multiple iterations and variations. A perfect example of this is the new insert or “+” sign that was recently added to Blueprint.

For those of you who have been using the product for a while, you’ll remember that our first design for adding items to the process diagram was very Visio-like, with drag and drop capabilities from an application menu:

Read the rest of this entry »

In this two-part Process People interview, we welcome 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.

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.

Raju Oak: At Kleinwort Benson, our organisation faced four challenges that we needed to address quickly:

• First, our reliance on ‘point applications’ to satisfy functional requirements for the business resulted in us having a large, expensive and fragmented IT landscape. It was soaking up a large percentage of our budget and it constrained our responsiveness;
• Second, the ever increasing regulation in financial services required us to have tremendous visibility across our business processes, coupled with integrated reporting on the outcomes. That in turn, required us to address the whitespaces between our various point solutions;
• Third, we needed a uniform way to integrate and manage several parts of the business that each had dissimilar infrastructures and processes (a strategy we call ‘regionalisation’).
• Finally, changing market conditions required the organisation to step up the scale and complexity of its offerings while reducing the time to market, which was difficult in the absence of a process governance framework.

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 »

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 »

Today I’m proud to announce the availability of the Summer ‘08 release of Blueprint! In the Spring ‘08 release, we delivered what we feel is the best process diagramming tool on the market, online or off. Over the last two months we’ve focused on improving the “other half” of process documentation — the standards and procedures, narratives, and data that make up the details that live behind the picture of the process. Let’s take a look at the improvements in depth:

• Rich Wiki Editing Of Process Documentation: Blueprint now provides a rich, wiki-style experience for filling out the details of your process. You can link to external documents, embed images, and format your documentation any way you please. Already have something written up in Microsoft Word? No problem. Just paste it in and we’ll leverage what you’ve already done.

Read the rest of this entry »

While a complete enterprise BPM roll-out is a multi-year effort, this two-part series focuses on the Pilot as the crucial first step in an enterprise initiative designed to spread throughout the organization.

On first toeing the BPM waters, there is what we call the “Startup” phase. The goal for this phase is to demonstrate that your organization can adopt and benefit from BPM on a broad scale. Your Pilot project, hopefully, is a great success – and frankly, it usually is. Why? Because you have spent months laying the groundwork, aligning the team, building the business case and acquiring the technology. Your company – at least the part working on the Pilot — is aligned, dedicated, and singularly focused on a shared and common goal.

But now, with a single successful process under your belt – what comes next?

Read the rest of this entry »

Ed.: This is the third post in a series of Q+A sessions focusing specifically on playback session best practices, with our in-house expert, Kris Komassa. See our previous coverage here and here.

Of course there is never a “finished” process. How often do you typically use a playback session to fine-tune a process that is up and running? How often do you do this, once a quarter? Twice a year? Can you give us a few examples?

We have a customer in Dallas that is unique because they have a very wide sales force who are all remote and need a number of approvals before they can close any business. We finished a project with them just a little over a year ago, and we’ve since done a number of other engagements on top of that original project, so the work is more or less constant. They’re a good example of fine-tuning and building on top of a first project.

The way that I always start off the new work with them is by having them do a playback for us to see where we are, and then have that segue into a talking session around what it is that they want to see or what new work they want to have done for them. So, we start with what we have already, instead of starting with what we ultimately want. This helps to create that delta between what they have today and what they’re looking for down the road. They’re a very active customer and good to work with for this reason - each new project flows naturally and organically from the ones that have preceded it. I’d recommend this way of working from one process to the next for everyone.

Read the rest of this entry »

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

When you run a flow during a playback session, business people can jump right in and start suggesting additions, etc. How real-time are the changes that are made, and how often do you iterate feedback on a given flow?

It’s a difficult thing, actually, and it varies by playback. The highest priority for me is to capture any and all feedback accurately, anything that anybody blurts out or cites in the playback.

Then I like to, for anything that is able to be fixed immediately, go in and change it right then and there. First, this puts the business perspective’s mind to rest to have it displayed for them, right there in real-time. And second, we don’t have to worry about that specific piece of feedback after the fact as a lingering action item.

But the trick to it is that you don’t want the real-time revisions to turn into a long discussion of what we should and should not do. If someone’s requirement is very clear, then we’ll do it immediately in the playback, but otherwise we’ll take it offline and come back to it later - you don’t want to hi-jack the entire session if there isn’t consensus or at least a clear directive in terms of what needs to be changed.

Read the rest of this entry »

Last week I talked about how you know who the right participants are with regards to a particularly complex Task Assignment and Routing implementation. I also talked about how you assign tasks and route information to them. But I finished by explaining why to a Business Process Developer, trying to implement a Task Routing rule, such as the example I gave, is a nightmare because of a lack of clarity around how to access the data necessary to implement the rule.

From the Process Developer’s point of view, the “right” answer to solve a complex routing problem like this is to develop a custom Task Routing Service to determine the list of users who should be given the opportunity to complete the task. If the conditions for eligibility are very dynamic (if they could change in a few minutes) then it’s also a good idea to develop a related service that will tell you if a specific user is eligible to claim a specific task.

When a task is ready to be performed, invoke the first service to get all of the eligible users.

When a user claims the task, call the second service to determine if they are (still) eligible, and return the task to the pool if they aren’t.

Read the rest of this entry »