Skip to main content

Most needed BPM skills

Cross-disciplinary architecture is among crucial and often neglected factors of BPM initiatives. Compatible multi-domain modeling is rarely available or seen as priority in BPM projects in favor of local automation tasks. However, exactly transparent and scale-able process collaboration across an organization determines long term success of the digital transformation.

The ability to capture a consistent view of an organization through precise mapping of relevant notations is a cornerstone of all subsequent BPM implementation. The goal of BPM is not a replacement of existing processes and technologies but their skilled alignment, which should ensure most effective and transparent interaction of the existing corporate infrastructure at minimum cost and modification.

Unfortunately, too many BPM initiatives go as vendor driven disruptions, revolutions, breaks through and other scenarios similarly dubious in terms of attractiveness and suitability for a continuous corporate growth. BPM is merely about bringing a harmony into established business structures, which is a skill too rarely found or distinguished as a demand.

Comments

Popular posts from this blog

CaseAgile Will Show BPMN Data Exchange between Visio and Leading BPMN Tools

CaseAgile announces a new release of Enterprise Composer™ add-on for Microsoft® Visio, which supports transparent exchange of BPMN diagrams designed in Visio with leading BPMN tools. CaseAgile will demonstrate capabilities of Enterprise Composer™ on upcoming "BPMN IN ACTION" event organized by The Object Management Group (OMG) in Seattle at December 10, 2018. Enterprise Composer™ offers a seamless and efficient way for every Visio® user into the world of professional business process management (BPM) systems and process automation. By using Enterprise Composer™, Microsoft® Visio can create executable processes fully compatible with BPMN™ 2.0 standard from OMG®, which is the global de-facto etalon for modeling business processes and can be used both by businesses and IT. Every BPM practitioner working with Microsoft® Visio now can import BPM models created in most popular BPM suites directly into Visio® and can export models cre...

Agile Processes and Customer Experience

Despite all fashionable favor, agile processes are a disaster in terms of customer outcomes . Imagine that you ordered a fridge but received a dishwasher instead. It is unlikely that you will be happy on this sort of creative agility. Customer process must be as precise and reliable as a Swiss clock. It is another story that customers always do their best to break this clock's precision in every possible and impossible manner: change their mind ten times a day, disappear at the moment of delivery, break supplied goods and claim a refund etc. And yet, customers highly appreciate flexibility of a company in response to their instant whims. We must not confuse agility of customers with precision of the company in response to agile client demands. Company can achieve accuracy and flexibility in serving clients only through rigorous process approach with detailed mapping of all possible client scenarios. Naturally, this detailed work-through may yield dozens and even hundredths of co...

Difference between workflow and process

Workflow is an implementation of process. Process is a template defining structure, rules, objects and their relations in a business environment associated with certain business goal or case. Workflow is a concrete realization of process in given business context. In other words, process is a plan, while workflow is a sequence of business actions taken according to this plan. Process is an architectural project, while workflow is a building created on this architecture. Multiple buildings can be erected from the same architecture. Unlimited sequences of actions can run along the same plan. But the plan or architecture behind all these varieties of buildings and sequences is a common ground cementing their distinguished similarity as a family.