Categories: BPMSOA

Lessons Learned: Best Practices for a Successful Introduction of Business Process Management (BPM)

I have written an article for “Service Technology Magazine” regarding the following topic: Lessons Learned: Best Practices for a Successful Introduction of Business Process Management (BPM). Here is the link: http://www.servicetechmag.com/I64/0712-3. The article illustrates some rules how to do BPM correctly. These rules are very important for success of a BPM project. If you do not consider them, your next BPM project may fail too…

Here is a short summary for introducing BPM succesfully (for people who are short of time and not reading the whole article):

  • Rule 1: If you want to do BPM correctly, then be aware that your primary goal is to improve Business-IT-Alignment!
  • Rule 2: If you want to do BPM correctly, then do not try to realize it without a service-oriented Architecture!
  • Rule 3: If you want to do BPM correctly, then be aware that BPM is not just tooling, but an engineering process with a huge, iterative lifecycle!
  • Rule 4: If you want to do BPM correctly, then use it only when you really gain benefits!
  • Rule 5: If you want to do BPM correctly, then do NOT believe in BPM myths!
  • Rule 6: If you want to do BPM correctly, then use BPMN 2.0!
  • Rule 7: If you want to do BPM correctly, then choose the right BPM tool for the job!
  • Rule 8: If you want to do BPM correctly, then do NOT use it for systems integration!

Please leave feedback, if you have any other opinions or experiences.

 

Best regards,

Kai Wähner (Twitter: @KaiWaehner)

 

 

Kai Waehner

bridging the gap between technical innovation and business value for data integration, workflow orchestration, and agentic AI.

Recent Posts

Data Integration Landscape 2026: Event Streaming, API, and Batch in the Era of Agentic AI

The Data Integration Landscape 2026 maps every major vendor across three communication paradigms: request-response, event-driven,…

2 days ago

Why I Joined Kestra: Enterprise Workflow Orchestration for the Agentic AI Era

Enterprises run separate tools for IT scheduling, data pipelines, business processes, and infrastructure. None talk…

1 week ago

My Confluent Chapter: From Apache Kafka Startup to $11 Billion IBM Acquisition

Nine years at Confluent: from a Silicon Valley startup with 100 people to an $11…

2 weeks ago

YAML vs XML vs JSON: History, Trade-offs, and Where Each Wins in the Age of Agentic AI

XML, JSON, and YAML were built for different jobs in different eras. This post covers…

2 weeks ago

Why Databricks and Snowflake Speak the Kafka Protocol: Ingestion vs. Architecture

Databricks and Snowflake now speak the Kafka protocol. But using the Kafka API to feed…

2 weeks ago

Choosing an ERP for Manufacturing: How AI Is Reshaping the Vendor Landscape

ERP vendor selection for manufacturing is not a product decision. It is a strategic bet…

3 weeks ago