The amount of information on the World Wide Web is enormous beyond belief.

SOA And Mashups – What to use when
Say I am a business manager at an insurance company and my job is to recruit insurance agents. These agents in turn meet the insurance needs of their customers and build their own customer base. If an agent does well, the company does well. With a finite amount of recruiting dollars available, I need to be able to make the best decisions on where to focus my recruiting efforts.

BPMS Watch: Process Model Portability: Does Anyone Care?
Among the numerous virtues of BPMN, foremost is vendor independence, giving process modelers many tools to choose from, all describing processes using the same shapes and semantics. That’s huge, since without low-cost (or even free) tools you’ll never establish a culture of process broadly throughout the business. Occasionally, however, a student in my BPMN training will ask the embarrassing question, “So that means I can take the models I create in this class and import them into the BPMN tool we use in our company…

Integrating Testing and Training with the Process Life Cycle
Earlier this year I wrote an article outlining the critical relationship between the Process Life Cycle and the Project Life Cycle. This relationship, when treated as a partnership of equals, can improve the success of both the technical and the process improvement interests. In addition to the Project Life Cycle, there are two other important relationships that should be considered when developing or enhancing a business process.

SOA Watch: SOA and Adapters
Once upon a time, whenever we connected application A to application B, or applications A and B to an integration server, we had to interact with those applications using some sort of interface that (hopefully) the applications provided.
What is a Process?
For years my partners and I at the Performance Design Lab have defined a business process as “a sequence of steps or tasks that produce a valued output”, or words to that effect. Every definition of process I have seen in the books and articles written by others use pretty much the same verbiage. Nothing wrong with the definition – it does describe what a process consists of – but it does nothing to indicate some of the key principles of process design, nor does it do more than hint at why processes are so important (i.e., “valued output”).
So we have come to modify our definition
Questioning Innovation
A dictionary definition of innovation is “introducing something new.” But these days, with the rise of the buzzword “innovation” in the business literature, you’d be led to think that innovation itself is something new. Let’s see if we can net out what’s new about innovation by asking a few questions about this hot business topic.
What’s New About New?
Here we go again with yet another hype curve, the Innovation Hype Curve. Why all the newfound interest in innovation? In short, globalization.

Getting Started is Hard to Do
At this point, the business benefits of business process management seem clear. Virtually every sector of society, including areas that seem relatively impervious to dramatic change, such as higher education and government, are becoming much more outcome-oriented....

Governance is Key to BPM Success
If all you want to do is execute a one-time improvement to a small business process then governance issues may not be high on your agenda. But if you wish to fully leverage the power of BPM and apply the key principles and practices to your company’s large business processes, you will soon discover that governance is the cornerstone to sustainable BPM success.

Seven Deadly Sins of Business Rules
“According to CIO magazine, up to 71 percent of IT project failures are caused by an ineffective requirements process.”
Business Rules are the orphan child of the requirements process, and our failure to address this issue continues to contribute significantly to IT failure.
What follows are seven deadly sins that continue to relegate rules to a second class status. We discuss the root cause of the problem, and postulate on potential solutions.
#1: Business rules are captured during design, if at all.