Pages

Oct 1, 2012

Crossing the Business Process Management Chasm: Three Tips

More and more organizations are taking advantage of business process management (BPM) solutions. And yet, it is often the case that, after an initial success or two, the growth of BPM within a company stalls.

For many business users, the first foray into BPM consists of a project that might as easily be accomplished using Outlook. That’s ok: it’s important to set easy goals at first, until you are comfortable with the quirks and behaviors of the solution you’ve chosen.

But even with an early triumph under their belt, some organizations have trouble moving beyond the simple approve-and-forward workflow they created in that first round. That’s like buying a sports car and driving it to your neighbor’s house: it’s not a bad way to get moving, but you certainly need to go farther than that to get your money’s worth.

Shifting into second gear entails some risk, of course. That approve-and-forward workflow was probably constructed by a programmer, or a business analyst with some technical skills, either as an experiment or, at best, a secondary assignment. Uncovering the true value of your BPM solution however will require a more substantial investment in analysis, implementation and review.

crossing_chasm_shutterstock_74660473.jpg

That’s where companies are likely to hesitate. What before may have been a skunk-works effort to streamline a simple process now threatens to divert resources and focus from revenue-generating activities. The ROI of BPM efforts is notoriously hard to determine, making it difficult to justify taking time and attention from other projects. Defeated, business process improvement champions turn away from their hard-won BPM implementation and go back to whatever else it was they were doing.

It doesn’t have to be this way. Here are some tips to help you cross the BPM chasm in your company, enabling you to succeed in realizing the full benefits of your BPM solution over a broad array of business processes.

1. “Slow and Steady” is Overrated

Know what really happened when the hare raced the tortoise? The hare crossed the finish line and everybody went home. Nobody ever heard from the tortoise again.

Quick wins are the way to proliferate BPM throughout your organization. To begin with, beware the company-wide, top-down, seven-figure BPM implementation. Unlike ERP, CRM and other three-letter technology boondoggles, BPM doesn’t necessarily benefit from scale and centralization. Look hard at the processes you need to automate, and size your solution appropriately. Sure, you want to be able to grow, but that doesn’t always mean bigger servers and bigger databases: usually it means fast deployment anywhere in the business.

Similarly, things will go a lot faster if you don’t need custom code for every process you deploy. There are plenty of BPM vendors offering (or at least claiming to offer) solutions that don’t require developers.

Choose a product that can be configured to meet your needs by somebody without a computer science degree. Ask the vendor to demonstrate a sample process based on your requirements, and then show you how it was built, before you buy. If your unique needs do require some custom development, find out if the vendor can provide those services.

2. Start with a Winner

As I suggested above, make sure your first project is an easy one — but also make sure it has visibility. Sometimes even simple approve-and-forward processes can have real impact. One of our customers tells us that the first day their new process was in place, a user called to complain that it had failed. When the customer checked the logs, he saw that the approval had been received and the process had completed correctly. “But,” the user objected, “this takes two weeks to get approved. I just submitted it this morning — it can’t be done yet.” This kind of happy surprise goes a long way towards smoothing the path for additional projects.

 

Continue reading this article:

 
 

Source : cmswire[dot]com

No comments:

Post a Comment