With the wide range of available tools on the market today together with the large number of white papers, articles and books on BPM, determining the correct solution for your organization can be daunting. With so much emphasis on the effectiveness of BPM tools for improving productivity, streamlining the value chain and gaining competitive edge, it’s easy to get caught up in all the hype and end up with a much more sophisticated and expensive solution than the business really needs.

One of the most successful innovations of the BPMS vendors to date has been incorporation of process modeling within the suite. Process modeling used to be a standalone business activity, requiring expensive proprietary tools that gave little thought to any automated IT implementation.

The first time I heard the phrase business process reengineering was over ten years ago, and I was a system analyst working with a utility industry software vendor.  A California locality had purchased our product to address Y2K issues, and automate all the city services. When I arrived at my client, I found that some of the city services were automated, some were not, and I had to determine a way to fit the manual approach into the system.

I found myself wearing multiple hats, and using my journalism training, which enabled me to research and identify the right people, determine a method of relating while building trust, and eliciting the necessary information to define the current and eventual future state of the processes and impacts to workflow with the new system.

Many companies which have begun applying lean or agile practices in their work place are now finding they need to reconsider who they hire to fill the more collaborative and facilitative roles required by those methodologies. Unfortunately, most companies believe they can magically transform their firm into a highly productive and enjoyable place to work by asking traditionally trained managers to simply apply a few new practices like value mapping, iterative development and an intense focus on quality. 

Some time ago during a discussion on ITtoolbox.com, I theorized about BPMS Cloud as the last, ultimate step, providing the final means to transition to a post-IT era.

My very first BPMS Watch column, over three years ago, was titled “Without a BPMS, It’s Not Really BPM.” And to a large degree I still believe that, although today I would probably tone it down to something like “without a BPMS, you can’t realize all the benefits of BPM.” That view is certainly less radical now than it was in 2005, as both developers and developer-oriented tool vendors have increasingly embraced the BPM Suite idea.