Hallucinating about ECM

The thoughts of my previous post on BPM and agility came on the heels of a conversation with a collegue in Australia who was looking for anyone who had implemented a comprehensive “ECM vision”, including BPM, web content management, records management and document management. It appears that most companies are implementing one large ECM-related project and some bits and pieces of the other parts; I have to admit that most of what I see is still at the hallucinatory stage rather than a full-on vision, and is neither cohesive nor comprehensive.

How many cusomter organizations really have an ECM vision, and more importantly, how many have the ability to implement it?

How agile are we?

I’m finally getting caught up on the emails, blogs and webinars that I missed while on vacation. One of the webinars that came up last week was Redefining Human-Centric BPM on eBizq. Sponsored by Adobe so very document-centric, but Beth Gold-Bernstein, the eBizq speaker, nicely categorized the benefits of human-centric BPM: improved quality, improved security, enforcement of business rules, and reduced cycle time. There’s a few others that I would add in, but this is a pretty good list to start with if you’re looking for ROI on human-centric BPM.

She also made a point early in the presentation that BPM is essential to delivering business agility, that is, the ability to change your business processes easily to meet changing conditions. I would have nodded my head right along with that one, except for this piece in Intelligent Enterprise last week about how companies implement one BPM project then consider their process work to be “done” rather than actually getting into that whole agility thing that they were sold by the vendor. It’s clear that agility is a both a key marketing point for BPM vendors and a key driver for the purchase of BPM systems — in other words, the vendors claim and the customers believe that business agility is important, and that BPM will help to deliver it — but the customer organizations may not be following through on the agility promise, and the vendors (having made the sale) have already moved on to the next prospect.

Process/business agility isn’t going to come about just by buying a hot BPM product (or any other product, for that matter): as usual, the technology is an enabler, it’s not the solution. Organizations need to embrace a philosophy of business agility at all levels, and not be squeamish when someone points out that “agility” is just “change” with good PR. Yes, jobs change, and that’s scary for some people. But customers (and their expectations) change, forcing the business to change, which forces the jobs to change. In order for an organization to be agile, the worker bees must also be willing to be agile and learn not just new tools (like BPM) but new ways of doing business. Just tell them that it will look great on their CV.

Inevitably, the vendors start to blog

While wading through a month of email and RSS feeds this week, I came across a BPM blog by CommerceQuest which is actually quite good. You have to skim by the blatant self-promotion (“I am pleased to see the market and industry experts beginning to talk more and more about the overall benefits of what we, at CommerceQuest, call Enterprise BPM”) as well as the more subtle bias towards the CQ way of life, and I could have done without the CEO’s folksy comments in his inaugural blog (“I never dreamt I’d be typing for the blogosphere when I started out more than 40 years ago at IBM” — no kidding?). However, it does contain some good reference entries that point to other blogs/articles of interest such as these ones on BPM at financial institutions, BPM and ERP, and BPM RFPs; there are also some “BPM basics” that I imagine are repurposed from their white papers or other technical marketing material. Worth a browse.

Different strokes

Coming back to the deluge of email, a slightly smaller torrent of postal mail and a soupçon of voice mail after 3-1/2 weeks in southern France and northern Italy is a bit disorienting. I’m still thinking about strolling over to the Rialto market in Venice to buy some fresh fish for dinner…

Travelling (although for vacation this time) always makes me ponder on cultural differences. Although I work primarily in Canada and the US these days, I’ve spent a great deal of time working in other countries in the past, and one of the things that I like most about business travel is seeing how different cultures do business differently. For example, only in France would a prospective client, upon meeting me, bow over my hand while shaking it and murmur “Enchanté, Madame”. And only in the Middle East would I need to wait until a man extended his hand to me before offering to shake hands, since I wouldn’t want to offend someone by suggesting that they violate their religious sanctions against touching a non-related female when I’m on their turf. [When I returned to my office in California and related this latter incident, I was asked “Doesn’t the discrimination bother you?” to which I replied “Well, at least they’re overt about it.” That resulted in a few stony glares.]

Aside from the greetings, there are other differences in how things work: I remember a BPM system that I designed in Germany several years back where the management wanted a supervisor to review each piece of work and decide who it went to, instead of using automated work assignment. With some foresight into how these things work in practice, we implemented a system configuration setting that caused that step to be either visited or bypassed, so that two days into production when the customer’s need for efficiency overcame their need for control, the supervisor review step was removed in about five minutes.

As an outsider coming into organizations and helping them to design their processes, or develop a strategy for application architecture, I’m always a bit of a foreigner, even in my own country: I have to quickly learn a new language and a new culture so that I look like less of a tourist wandering around with my camera and guidebook. In business, as on vacation, I’ve always found it best to just dive in and act like the natives.

Gartner’s BPM trends and forecasts

Another webinar going on right now, Gartner BPM Roundtable: Business Process Management Trends and Forecasts, hosted by Global 360 and featuring Jim Sinur of Gartner (yes, this turned out to be “webinar day”, I have a third one after this if I’m not burned out).

The usual webinar format is the “expert” talks to his slides for 30-40 minutes, then some marketing geek from the vendor talks about their product for 10 minutes. Not this one: it’s a very dynamic conversation between Mr. Sinur and Michael Crosno, President of Global 360, and both of these guys are really smart about BPM. Yes, Mr. Crosno talks about Global 360 product features, but it’s used as a springboard for Mr. Sinur to talk about the importance of specific functionality in the current and future BPM suites marketplace.

A few really great insights. The first one is was that legacy BPM deployments are more likely to have been for the purpose of reducing paper, whereas the new deployments are all about streamlining processes and improving productivity, with a new and increasingly important focus on extending the enterprise. Although this is something that we all know by gut feel, it’s good to see some real numbers behind it:

The second insight is that customer requirements are evolving from enterprise content management (ECM) to enterprise process management: a shift from information lifecycles to process lifecycles. As a “column 2” advocate, I’m really glad to see Gartner recognizing the shift in focus from content to process. Mr. Sinur showed a scale that started with image management and went all the way through to business optimization, with the crossover from ECM to EPM happening between portals and process execution. He puts “workflow” in the ECM space, that is, the subset of BPM that is used for content lifecycle management.

Another point was the trend for CRM vendors to integrate BPM with their products, usually by buying or OEM’ing in a third-party product, because they see it as an essential part of managing the customer relationship. I’ve been seeing this trend lately as well, such as with Onyx‘s acquisition of a BPM product and their current push to integrate it into their mainstream CRM product.

By far the best webinar that I’ve listened to in months. The slides and the audio playback will be available tomorrow on Global 360’s site.

BPM in compliance

I’m listening in on a Ziff Davis webinar “The State of Business Integration: An Overview of Patterns and Best Practices”, featuring Ajay Patel, VP of of Server Technology for Oracle. In the course of the webinar, they’ve been doing a few listener polls, and this one was particularly interesting:

In other words, 27% of the webinar listeners consider BPM to be the most important technology for their compliance efforts, second only to corporate reporting/BI at 33%.

BPM as part of BAM

A few more notes on today’s ebizQ webinar on BAM. Ms Gold-Bernstein talked about another topic close to my heart, namely that BPM is one of the contributing sources to BAM/performance management, rather than BAM being a part of BPM (as the BPM vendors would have you believe). The term “BAM” was originally coined by Gartner, so they’ve had first dibs at saying what is and is not BAM:

BAM defines the concept of providing real-time access to critical business performance indicators, along with the supporting information to improve the speed and effectiveness of business operations.BAM is accomplished by monitoring multiple systems, creating real-time dashboards, and using context and rules to detect the occurrence of a pre-defined set of circumstances.

They list BAM technologies as including BPM, integration middleware (arguably part of BPM under Gartner’s own definition), BI, dashboards with KPIs (which I would consider part of BI), and IT operational management (ditto). Since BAM is defined as a concept and is linked to all of these technologies, there are a lot of vendors from all different areas scrambling to get into BAM magic quadrant — not unlike what’s happening with BPM vendors ever since Gartner lumped together all process-related technologies as “BPM”.

To confuse things further, Gartner’s report on the convergence of BPM and BAM lists three main areas of overlap, and therefore potential conflict:

  • BPM acting as “BPM+BAM”
  • BPM serving as BAM’s response mechanism or recipient
  • BPM ? or business process analysis (BPA) ? serving as a passive analytic/visualization model for BAM

Prior to Gartner defining BAM, there was performance management, which is more focussed on the BI side of the equation, including technologies such as BI, dashboards and, lately, CEP (complex event processing). Although the goals of performance management are fundamentally the same as BAM (business alignment, real-time KPIs), the scope is narrower by excluding BPM and middleware technologies.

Somehow, the concept of performance management as pure business intelligence makes more sense to me than including (rather arbitrarily) some of the technologies that produce the data that feed into the performance management. If BPM is included as one of BAM’s technologies, why not databases, or CRM, or any other technology within an enterprise that produces data that may be of interest to management? In fact, if there’s a technology within an enterprise that doesn’t contribute data to performance management KPIs, why is it there?

Strategic process optimization

A webinar going on right now on BPM, BAM and SOA: Optimizing both Business and IT focussing on the ROI of process integration. Beth Gold-Bernstein contrasted the tactical versus strategic approaches to process integration:

  • Tactical approach requires defining underlying integration infrastructure
  • Strategic approach — enterprise integration architecture defines infrastructure, business defines the process

This goes back to one of the key ideas that I’ve been working with lately, namely the role of process and BPM in an enterprise architecture framework.

She also made a distinction between web services orchestration and business process management, where she sees WSO as providing a graphic way to design and control flow between web services, but without all the process governance (monitoring, analytics, management and simulation) that you would find in BPM. Given the role being assigned to BPEL, is this just another artificial distinction in the process marketplace?