Business process optimization, Part 1: Planning for sustained agility and business outcomes

This article explores commonly held concepts behind business performance and agility, and illustrates at a practical level how to extend these into new and innovative ways of measuring, achieving and sustaining business performance through business agility.


Ali Arsanjani, Ph.D. (, Distinguished Engineer and CTO, IBM

Ali Arsanjani photo

Dr. Ali Arsanjani is the Chief Technology Officer (CTO) for SOA, BPM & Emerging Technologies in IBM Global Services. He leads a team responsible for developing worldwide competency in SOA and BPM and increasing delivery excellence of SOA solutions using IBM and non-IBM tools and SOA offerings, most of which he has co-developed. He is responsible for IBM vision, strategy and execution of that strategy in the SOA and BPM space of emerging technologies and SOA and BPM offerings. He is a hands-on, sought-after architect around the world on IBM's largest accounts. To accomplish this Dr. Arsanjani works with IBM Software Group and IBM Research, as well as other parts of IBM Global Business Services to deliver SOA solutions for clients using the latest IBM tools, technologies and SOA offerings.

In his role as CTO for the SOA and Web Services Center of Excellence and the Business Process Optimization CoE in IBM Global Services, Dr. Arsanjani and his team specialize in harvesting and developing best practices for the modeling, analysis, design and implementation of SOA and web services. Dr. Arsanjani leads the internal IBM worldwide SOA & Web Services Community of Practice (6000+ members) and is the principal author of the (Service-oriented Modeling and Architecture) SOMA method for SOA, as well as other assets, offerings and tools around SOA and the IBM BPO method for business process optimization.

Dr. Arsanjani not only works on executing a global strategy for GBS, but also works to assess, integrate and develop tools to support IBM's integrated offerings. He represents IBM in standards bodies such as The Open Group and is responsible for co-chairing the SOA Reference Architecture, SOA Maturity Model, and Cloud Computing Reference Architecture standards within that body.

developerWorks Contributing author

Kerrie Holley (, IBM Fellow, IBM Global Services

Kerrie Holley photo

Kerrie Holley, IBM Fellow, is the Global CTO for Application Innovation Services in GBS. His responsibilities include technical leadership, oversight, and strategy development, consulting and software architecture for a portfolio of projects around the world. He is also CTO for IBM’s SOA and Business Process and Service Optimization Center of Excellence.

In 2006, IBM's CEO appointed Kerrie to Fellow, IBM’s highest technical leadership position. It is the highest honor a scientist, engineer, or programmer at IBM (and perhaps in the industry) can achieve. Kerrie’s expertise centers around software engineering, software architecture, application development, business architecture, service oriented architecture, and cutting-edge network-distributed solutions.

Mr. Holley is an author, IBM Master Inventor and holds several patents. He received a Bachelor of Arts degree in Mathematics and a Juris Doctorate in law degree from DePaul University.

Jean Pommier (, Distinguished Engineer and CTO, IBM China

Jean Pommier photo

Jean Pommier is a Distinguished Engineer and CTO in IBM Software Services for WebSphere Services, where he is in charge of Service Engineering (implementation methods, best practices and consulting offerings) for the WebSphere practices, including BPM, decision management, cloud, and mobile.

Prior to joining IBM in 2008, Jean was ILOG’s VP of Methodology. Jean joined ILOG upon its creation in 1987 in R&D (expert systems), moving into consulting then management in 1990. He led the Worldwide Professional Services and the US operations for ILOG's largest division, Financial Services, Transportation and E-Government. Overall, Jean has contributed to more than 400 successful customer implementations of business process and decision management systems.

Claus Torp Jensen (, Senior Technical Staff Member, IBM

Claus Jensen

Claus Torp Jensen is a Senior Technical Staff Member on the Business Process Optimization (BPO) Foundation team and Chief Architect for SOA-BPM-EA technical strategy, driving their alignment and integration both conceptually and practically. The BPO Foundation team has architectural responsibility for all of IBM's software products to ensure that they support the key principles of SOA, Business Process Management (BPM) and Business Agility from a client perspective. Prior to joining IBM in March 2008, Claus was Group Chief Architect, VP of Architecture and Business Development, in Danske Bank, a regional European bank. He was responsible for driving Danske Bank's SOA initiative and SOA center of excellence since its inception in 1999, and is known as an SOA expert and evangelist. Claus holds a PhD in Computer Science from Aarhus University, Denmark.

developerWorks Contributing author

Samuel Antoun (, Business Development Executive, BPM Tiger Team, IBM China

Samuel Antoun photoSamuel Antoun is an expert in business process management and leads IBM’s BPM Center of Excellence. He has over 17 years of experience in enterprise solution architecture, BPM, SOA, and business & IT strategy formulation. This experience encompasses enterprise-wide transaction-based solutions, e-business internet and intranet web infrastructure architecture and development, primarily in the insurance, banking, government, and manufacturing industries. Sam holds an Executive MBA from Case Western University and a Master of Science in Computer Science from Cleveland State University.

Julian Petriuc (, Executive IT Architect, IBM China

Julian Petriuc photoJulian Petriuc is widely recognized within the Retail industry and IBM technical community for his substantial technical contributions in delivery and asset creation. In his role as the Chief Architect for Retail in IBM Global Business Services, Application Innovation Services (AIS), Julian provides thought leadership in applying BPM, EAI, SOA and other innovative architectures and technologies for competitive advantage for clients. As Chief Architect, Julian is a hands-on architect and software engineer who has led the architecture, design and development of several large retail projects in the US. He is highly sought after for his expertise throughout the world.

18 April 2012

Also available in Chinese Spanish


Organizations increasingly navigate a highly volatile, complex environment in which uncertainty, change, and the rise of technology, new business models and competitive threats are the only constants. Companies seeking to out-perform in this environment require operational dexterity, and business agility is critical to being responsive to increasingly changing market conditions. The pragmatic and operational definition of business performance and business agility, that is, how to achieve and to sustain them within the context of a supporting IT environment, varies considerably. Although there is a growing congruence in the industry around the definition of business agility, often with an underlying agenda of selling software or services, an agreed upon or recognized definition of business agility remains evasive.

Stakeholders pull a variety of levers to achieve business agility. Figure 1 illustrates sample levers often leveraged to improve business agility.

Figure 1. Business agility levers
Business agility levers

(See a larger version of Figure 1.)

Focusing on a single lever or even a collection of levers may not bring about the desired business outcome. For example, a focus on improving an accounts open process may result in increasing short-term revenue and accounts. However, what if the business outcome, the strategic CEO imperative, was to become a leader in the market measured by being number one in revenue and profit in retail banking? Optimizing the account opening process resulting in increasing the number of new checking and savings accounts is good work but insufficient.

It is useful to realize the pragmatic and operational definition of business performance and business agility; specifically how to achieve and to sustain each within the context of a supporting IT environment. What supportive role should the IT infrastructure, software architecture, application development, best practices or any of the agility levers play in order to achieve business goals and maintain performance over time? In the context of business process optimization (BPO), businesses need to look beyond classical application development and agility levers to achieve business outcomes.

This article describes the practical definitions, principles and conceptual model for business agility and business performance from both a business and an IT perspective. The primary audience is business and technical leaders and architects who need to understand how to achieve business agility and drive their organizations towards innovation and continuous business improvement, while maintaining and exceeding levels of business performance.

The objectives in achieving, sustaining, and improving business performance through BPO are as follows:

  • Enable agility across multiple dimensions of business and IT in order to be able to manage and incorporate changes in business and technology.
  • Help in making trade-offs between agility and effectiveness or efficiency.
  • Gain the ability to handle and manage complexity in the face of continuous change, including predictable and unpredictable variation.
  • Optimize business architecture and service delivery under unpredictable market or business shifts.

In general, the goal is to be able to optimize the process of change as it naturally occurs in dynamically varying environments, markets and organizations.

Defining business process optimization

Business performance is ultimately measured by a comparison of track record with existing scorecards, balance sheets, or key performance indicators (KPIs). Instead of focusing on solutions design, we recommend refocusing on business design, which incorporates unanticipated and predictable variations within the business ecosystem.

BPO is a systematic approach that emphasizes repeatability and replaces heroic efforts and one-time improvements. BPO shifts the focus to business innovation or what should be different in a process (business outcomes), rather than solely requirements gathering or process modeling. The emphasis in BPO is on comprehensive change – not on incrementally improving systems or processes, but re-engineering the business to realize gains through emerging technology exploitation. BPO renders enduring structural changes in organization that are necessary for innovation, business outcome, or both.

We define business agility as the collective capabilities and constructs allowing a business to continuously transform in order to achieve its business outcomes, and to be predictive, flexible, responsive, and launch business initiatives in times of change and uncertainty. BPO makes this possible using building blocks focusing on business performance in which business agility is not only what you do but what you become.

Influences on BPO

Factors influencing business performance and agility vary. It's useful to understand a number of these factors, many of which tend to be under the control of the business and supported by IT. However, several of these factors can be put under IT scrutiny and monitoring with the correct instrumentation and interpretation of events. These factors include:

Business ecosystem

The network of organizations including partners, suppliers, customers, government agencies, or distributors involved in the delivery of goods and services through both competition and cooperation where each coevolves to some extent.

The ecosystem includes policies, rules and laws governing business providers, business consumers, and business brokers.

Business context

The environment, market, legislation and ecosystem within which the business is operating and evolving changes and varies based on forces within the business context. The business context is a business state within the business ecosystem.

The context in which a business-significant event has occurred or is occurring provides the background and conditions to be used in the evaluation of business policies and business rules as a basis of taking corrective actions for business processes and services.

It is the confluence of the factors and eight enablers (process, information, events, rules, content, analytics, collaboration and monitoring, as shown in Figure 2) that influence BPO such that changes can be made intelligently in the way businesses adapt to business environment changes and affect desirable business outcomes in a consistent and predictable fashion even in the face of generally unpredictable circumstances.

The eight enablers are described in detail in the IBM whitepaper The Language of Business Design (PDF).

Figure 2. Business enablers
Business enablers

(See a larger version of Figure 2.)

Business variations and change

There are many changes constantly occurring within the business context and most are unpredictable. Only some of these are business-significant and should be "bubbled up" or surfaced at an executive and business level, especially when business sensors detect a certain threshold above which apparently ordinary events become important enough that the business sensors should indicate that a potentially impactful variation has occurred.

Business state

A business state is the result of a significant business change that causes the parameters and qualifiers of efficiency, effectiveness, agility and performance to change. A change of state implies that business outcomes may differ as you transition from one business state to another. The business state is a snapshot in time of the key metrics and information related to the business context.

Business outcomes

Understanding and defining desired business outcomes provides clarity to initiatives and projects. It enables all stakeholders (business and IT) to fully participate and cooperate with agreed upon and clearly understood objectives. Measurable business outcomes become the central focal point of projects rather than requirements.

Business goals

A business goal denotes the business aspiration of an organization. It describes a desired state that the business intends to achieve. It can be at a high level, starting from a vision and strategy statement, or translated and decomposed into operational, actionable and measurable objectives. Typically goals are set in such a way that there is a finite time to attain these goals. Target business performance is defined in terms of a set of business goals associated with KPIs. An example of a business goal could be as high level as "Increase average revenue per customer by 20%" to something more actionable such as "Increase cross selling products in northeastern region by 5%."

Key performance indicators

A KPI is a measure of performance, or in other words, a measure of meeting the business goals. An example of a KPI for the "Increase average revenue per customer by 20%" business goal might be "Increase average revenue per customer."

Business processes

A business process describes a sequence or flow of activities or steps in an organization to carry out work to achieve a business result by achieving business goals. Business processes can be named (for example, order processing) or unnamed and known only by their operational function.

Business policies and rules

A business policy is a declaration or statement that describes principles to guide decisions to drive to desired outcomes. An example of a business policy is "Book non-refundable tickets whenever available." A business policy reflects business tactics to ensure adherence to the business goals over time. A business rule is a declarative statement that constrains some aspect of the business. It describes how a business should behave in the face of events under a certain set of circumstances. A decision could cause a transition from one entity to another in a state diagram.

Business decisions

Business decisions record and formalize the decisions that an organization makes within a business process.

Business sensors

Business sensors are instrumentation and mechanisms to monitor, track, modulate and govern business change, just as KPIs track the events and occurrences within the business context.

Business events

Business events are occurrences that represent a significant change in the state of the business. Typically these are not ad hoc or non-deterministic, and are not part of a set of repeating sequences of activities in a business process.

Business monitoring

The monitoring of business activities based on a set of KPIs. It involves looking at business events and comparing against thresholds using light algorithms and reporting.

Service-level agreements (SLAs)

A service-level agreement is a contract between two business parties formalizing a set of expectations between consumers and the provider of services. This agreement is defined in measurable terms.

BPO usage scenarios

Table 1 lists use cases in which BPO should be applied.

Table 1. BPO drivers and potential impacts
Business driverExplanationBPO impact
No agreement on process view

Different geographies or business units do not agree on a process model.

Cannot get agreement on process or on standard processes yet must improve the process or high process complexity.

High variability of process or variability is seen as competitive advantage or regional differences or geographical differences are significant and process decomposition is inadequate for gaining global consensus.

BPO focuses on the underlying business entities and how to prepare them for ongoing change.

BPO focuses on optimizing business outcomes.

BPO focuses on measurable business goals and measurable agility levers.

BPO provides process view without a focus on activities.

Desire for measurable business agility Desire to make a process or domain more responsive, more predictive, more flexible and adaptable to change and uncertainty.

Need to imbed business insight into the process.

BPO provides a business-centric engineering approach for identifying and architecting defined agility points.

BPO uses an agility model to measure and assess current and future agility needs across multiple dimensions.

Resistance to BPM and process thinking Organization does not accept process models (named processes) or process views as a way of describing their business lifecycle or operations. BPO provides the ability to support process patterns defined by business users without having to do a process model or re-engineer the process in advance.
Belief that technology can do more

Technology can do more than what is currently being achieved. Can we demonstrate how using technology can make a process better?

Desire to balance investment in IT infrastructure with equal or greater positive impact to business returns.

BPO demonstrates the "art of possibilities" with business stakeholders showing what is possible with holistic use of technology in making a business process more responsive, more measurable and more adaptable.

BPO architecturally addresses several technology levers such as analytics, business process management, rules, decision management, learning systems, SOA, mobile, cloud and others.

Unable to determine what to do next Unsure whether the next project should be custom application development, rules engine development, decision management or BPM adoption, Lean Six Sigma, analytics initiative, content management, a transformation project or some hybrid of these.

BPO focuses attention on the outcomes necessary for a process to achieve the necessary measurable results.

BPO provides an engineered approach to holistically leveraging technology and best practices to create sustained capability.

The role of variation-oriented business optimization

Increasing business agility depends to a large extent on applying variation-oriented analysis and design to identify and form a foundation for predictable, anticipated variation (that is, change) and unpredictable, unanticipated change, and pertains to types of variations and changes rather than individual instances of those variations.

There are generally four axes of variation: information (structure), processes (flow), events, and rules or policies form the axes of variation that provide an opportunity for change in a business. Additional axes of variation can be mapped to the remaining agility enablers, such as organization and collaboration. Together these enablers of agility form a set of aspects that can be defined as varying.

Variation-oriented business analysis recognizes the changing nature of the business ecosystem and seeks to optimize business processes through correct design, planning, execution monitoring and optimization. Variation-oriented business optimization helps manage and mitigate complexity in ambiguous, unpredictable and murkily evolving circumstances using business sensors in the business context to trigger the smart changes needed to adapt and to optimize the response so the business is not unnecessarily expending scarce resources or ignoring critical threats and complexities.

BPO is a green-field opportunity

If you have been working in the industry for a while, none of these three words, business, process or optimization will sound new to you. Even together, they appear to correspond to a value proposition that has been around in the media and the boardroom for decades. Indeed, through modeling, management, instrumentation, automation, and re-engineering, BPM has enabled organizations to achieve process optimization through continuous process improvement. However, while bringing value locally, the optimization of individual processes does not allow the realization of the full potential of the overall performance optimization that you can get by breaking silos and ensuring collaboration. In other words, changing modeled processes will not in most cases change business outcomes, but will only achieve the same outcomes at less cost or higher quality. The choice is whether to make the current state more efficient (BPM) or change the current state (BPO).

Let's look at an analogy: when designing a car and improving it for a certain purpose, either speed, cost or energy efficiency, you cannot succeed without a fully integrated engineering of all the components. The engine has to fit in the body, the body has to meet certain aerodynamics and appearance goals, the transmission needs to be compatible with the intended usage, and and so on with the dashboard, circuits, options and all sort of mechanical, electrical, quality and security constraints. In the same way, you can improve local business operations but you cannot optimize the performance of an entire enterprise solely by implementing BPM in the traditional meaning of the term.

As illustrated in Figure 3, a modern organization encompasses not only internal processes, but also marketing, suppliers, partners and customers, all of which need to be taken into account when optimizing business outcomes. BPO is an innovative approach to identifying elements across traditional and typical silos, which, bridged and combined, can radically improve the performance of an organization and its extended supply chain.

Figure 3. The organization and its extended supply chain
The organization and its extended supply chain

BPO doesn't eliminate the need for local performance improvement initiatives, but instead federates them and identifies those that require cross-boundary collaboration.


In order to achieve and improve business performance, you need to understand its elements and how to leverage foundational notions that must be in place, such as business agility, in order for the business performance to be realistic, sustainable and able to provide for continuous improvement.

The value proposition of BPO is twofold:

  1. Achieve and sustain business performance:
    • Change the business operational model at a rate, cost, quality and predictability consistent with strategic needs.
    • Monitor real-time business events using new combinations of information technology.
    • Provide corrective actions or organizational change as an enabler for sustaining business outcomes.
  2. Enable operational dexterity to address agility and complexity gaps identified by executives:
    • Optimize business performance based on well-defined points of agility.
    • Optimize the process of change.
    • Holistically use IT and business operational change as an enabler.
    • Achieve better business outcomes from data and processes in the business.
    • Real-time insight and monitoring to improve decision-making.
    • Liberate business from the rigidity and fragility of existing applications that hard-code processes and information utilization.

Businesses believe "we can do better" and are looking for a means of achieving higher level of performance. Business process optimization is a green-field opportunity to liberate business from the rigidity and fragility of their existing applications using a holistic approach to leveraging technology. In Part 2, we'll discuss the BPO method, an easy to use approach for making BPO real as a business-centered engineering method.


The authors would like to sincerely thank the following contributors to this article: Kishore Channabasviah, Jorge L Sanz, Kevin Daley, Rob High, Robert P Hablutzel, Ian Turton, Jerome Boyer, John G Vergo, Abdul Allam, Asit Dan, Geoffrey Hambrick, Sella Ganapathy, Tapas Som, Prabir Nandi and Shuvanker Ghosh.



developerWorks: Sign in

Required fields are indicated with an asterisk (*).

Need an IBM ID?
Forgot your IBM ID?

Forgot your password?
Change your password

By clicking Submit, you agree to the developerWorks terms of use.


The first time you sign into developerWorks, a profile is created for you. Information in your profile (your name, country/region, and company name) is displayed to the public and will accompany any content you post, unless you opt to hide your company name. You may update your IBM account at any time.

All information submitted is secure.

Choose your display name

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerWorks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

Required fields are indicated with an asterisk (*).

(Must be between 3 – 31 characters.)

By clicking Submit, you agree to the developerWorks terms of use.


All information submitted is secure.

Dig deeper into Business process management on developerWorks

Zone=Business process management, WebSphere
ArticleTitle=Business process optimization, Part 1: Planning for sustained agility and business outcomes